Department of Information Services Perspective on redefining the enterprise during transition

1
Department of Information ServicesPerspective
on redefining the enterprise during transition
IPMA Executive Seminar September 21, 2004
2
Redefining the Enterprise

• Introduction of DIS Team
• Overview of Agenda

3
Agenda
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Enterprise Architecture - Greg Brant
• Enterprise Services - Laura Parma
• SecureAccess Washington
• Access Washington
• Questions and answers - All

4
Enterprise Architecture
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101
5
What is Enterprise Architecture?
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• A logically consistent set of principles,
  practices, policies, models, standards, and
  guidelines that are derived from business
  requirements, that guide decision-making and the
  engineering of an organizations information
  systems and technical infrastructure.

6
What is Enterprise Architecture?
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Analogous to building architecture
• Meets the needs of occupant one size doesnt
  fit all
• Provides multiple, interrelated views to maintain
  context for the contractor
• Uses engineering principles to improve the
  likelihood of successful completion

7
What is Enterprise Architecture?

• Similarities to city planning
• Ensures the common services meet residents needs
• Provides standards to improve access to common
  services
• Improves the predictability of services by
  understanding future growth needs

8
What the statewide EA isnt
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Detailed schematic/blueprint specifying all IT
  components in all agencies
• Statewide buy list for all IT components in an
  agency
• Replacement for agency EA efforts
• Magic bullet

9
Why do EA?
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Better manage 1.1 BILLION in IT investments per
  biennium
• Align technical architecture of state strategic
  IT plan and priorities of government
• Develop principles, practices, processes,
  policies, standards and guidelines to guide
  agencies in efforts to plan, design and implement
  IT systems

10
What does this have to do with Transitioning the
Enterprise?
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• EA establishes an enterprise view
• Predictive Architecture better ability to
  respond to changes, based on durable business
  needs
• Better leverage each others IT investments
• Provides a business-enabling technology
  capability
• Helps to manage complexity

11
ISB Enterprise Architecture Committee
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Christy Ridout, DSHS
• Julian Soh, DOR
• Greg Brant, DIS
• (non-voting)
• Susan Hettinger, DIS (non-voting)
• Laura Parma, DIS
• (non-voting)

• Dennis Jones, OFM (co-chair)
• Shelagh Taylor, LNI (co-chair)
• Thomas Bynum, ESD
• Tom Clarke, AOC
• Sue Fleener, WSP

12
Two objects One interface
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101
13
Four objects Six interfaces
14
Eight objects 28 interfaces
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101
15
32 objects 496 interfaces
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101
16
State of Washington EA tiers
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101
17
Tier One characteristics
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Common approach provides greater value
• Benefits outweigh cost of creating commonality
• Single enterprise view for citizens, employees
  and business partners
• Supports statewide processes
• Economies of scale
• Operating efficiencies
• Consistent/quality information

18
Statewide EA Framework
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101
19
Environmental Trends

• The Statewide EA starts with business needs that
  are durable in nature. Environmental Trends are
  major internal and external forces that impact an
  enterprise.
• Collaboration - inter-governmental data and
  information sharing
• Security - privacy and security of data and
  information
• Citizen access - government as single service
  provider, single face of government

20
Business drivers
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Business Drivers - organizations response to
  environmental trends.
• State government as a single enterprise
• Access to information regardless of source agency
• Safety and security
• Safeguard physical security and personal
  information

21
Enterprise Architecture Principles
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Should have a business-based rationale
• Guide decision-making
• Stand the test of time
• Establish a shared language for business and IT

22
Scope of EA principles
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Primary focus of the principles is for business
  processes, data, and technologies of the
  Enterprise Architecture that are shared across
  the state (Tier One).

23
EA principles
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Commonality
• Natural boundaries
• External linkages
• Scalability
• Security

• Customer viewpoint
• Business ownership
• Business continuity
• Interoperability

24
Customer Viewpoint Principle
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Should be designed around the citizens view and
  provide a consistent experience
• Rationale - Citizens view state government as a
  single enterprise.

25
Customer Viewpoint Principle

• Should be designed around the citizens view and
  provide a consistent experience
• Implications
• May require numerous systems to shift from a
  transactional model to a more customer-centric
  model.
• Will require additional understanding of customer
  usage patterns.
• May require additional look and feel standards
  and compliance.

26
Where can EA be applied?
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Product selection
• Solution design
• Services to be made common
• Methods or approach
• Project scope
• Project go/no go decision
• Prioritization

27
Accomplishments to date
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Complete and submitted to ISB
• EA Vision Mission
• EA By-laws
• EA Charter
• First Draft of Overarching Principles

28
Next steps
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Define what should be included in Tier One
• Collaborate with other groups to create Tier One
  views, models, standards and policies
• Establish ISB policies and standards for
  statewide implementation and compliance with EA

29
Transitioning to Enterprise Architecture allows
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Better information sharing
• Leveraging common IT infrastructure
• Responding to change

30
Examples of Enterprise Implementations
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101
31
Now live!

• Access Washington
• SecureAccess Washington
• Single sign-on gateway
• Formerly known as Fortress 3

32
Access Washington
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Whats new
• Partnered with LNI on study
• Usability study from the users perspective
• Usability tests with typical users
• Redesigning to meet the needs of users

33
Access Washington
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• http//access.wa.gov/

34
Access Washington
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Updated function for the portal
• Horizontal tab navigation
• Reduced page loading time
• Streamlined information architecture
• Updated user interface for Ask George
• Updated user interface for 24x7 Help Center

35
Access Washington
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Next steps
• Conduct final benchmark usability study
• Establish usability principles for Web
  presentation guidelines
• Convene cross-agency committee to review and
  update Web presentation guidelines
• Continue to share usability approach with agencies

36
SecureAccess Washington
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Challenges facing agency application deployment
• Multiple passwords
• Time demands on authentication and access control
  administration
• Administrative burden on help desks

37
SecureAccess Washington

• Recommendations
• Users inside Shared Government Network (SGN)
• Enterprise Active Directory for single sign on
  authentication
• Users outside the SGN
• Develop the next generation of Fortress to
  support single sign on authentication

38
SecureAccess Washington
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• The next generation of Fortress became know as
  SecureAccess Washington
• This launched a requirements and design project

39
SecureAccess Washington
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Development strategy
• Based upon customer requirements
• Validation workshops to review use case designs
• ISB security standards as baseline
• One gateway to support multiple agency
  applications
• Same toolset as Transact Washington and Fortress
  Anonymous

40
SecureAccess Washington
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• http//secureaccess.wa.gov

41
SecureAccess Washington
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Key benefits for Security
• Protects resources by masking the URL
• Authentication is done at the gateway
• Complies with the ISB standards
• Is regularly audited
• Only authorized users gain access to agency
  applications based on agency approvals

42
SecureAccess Washington
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Key benefits for Effectiveness
• Agencies need not build the gateway
• Less impact to agency password administration
• Single face of government to users

43
SecureAccess Washington

• Key benefits for convenience
• One user ID/password
• Users set their ID and password, can be reset
• Agency application developers have automated
  wizards to assist in development

44
SecureAccess Washington
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Early Adopters include
• Social and Health Services
• Ecology
• Labor Industries
• Licensing

45
SecureAccess Washington
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• Tools in support of SecureAccess
• Customer Support for 24x7 support
• Admin Resource Center

46
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0111 0101 0101 0101 0010 0010 0010 0101 0111
0101 0101 0101 0010 1001
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101
Policy
Governance
Infrastructure
47
Questions
0001 0001 0100 0101 0100 0100 0001 0101 0100 0010
0100 1001 0001 0010 0011 1010 0100 1010 0101 0111
0001 0001 0100 0101 0100 0100
0000 0010 0010 0011 1010 0100 1010 0000 0010
0010 0011 1010 0100 1010 0101 0111 0101

• State of Washington
• Department of Information Services
• 1110 Jefferson Street SE
• P.O. Box 42445
• Olympia WA 98504-2445
• www.wa.gov/dis