Enterprise Architecture: Focus on Alignment for Government to Government Interoperability: Business - PowerPoint PPT Presentation

1 / 26
About This Presentation
Title:

Enterprise Architecture: Focus on Alignment for Government to Government Interoperability: Business

Description:

EA is needed for more than just Budget: Active Living Blueprint! ... standards with active Government Domain Task Forces within OASIS,OMG, W3C, and IETF. ... – PowerPoint PPT presentation

Number of Views:79
Avg rating:3.0/5.0
Slides: 27
Provided by: booz180
Category:

less

Transcript and Presenter's Notes

Title: Enterprise Architecture: Focus on Alignment for Government to Government Interoperability: Business


1
Enterprise Architecture Focus on Alignment for
Government to Government Interoperability
Business Line Driven Information Sharing
  • Enterprise Architecture Shared Interest Group
  • October 31,2002

2
Agenda
  • Summary of Challenges-Goals-Context Diagram of
    Papers.
  • Grouping papers in clusters
  • Provide Overview and Concepts of
    Interoperability-Information Sharing Papers.
  • Plan more early introduction of concepts and
    feedback
  • Plans for November 14th
  • Possible follow-on on December 16th- HLS

3
Emerging Set of Common Goals
Business Operational View Domain aspects of
business transactions
  • Business Goal Driven Framework
  • Leverage Inherent Features of Enabling
    Technologies Use Mature and Be Ready for
    Emerging Technologies(eg. Web Services)
  • Implement Business Process Models and Federated
    Information Models with Model/Meta Data
    Approaches
  • Establish Cross-Government Interoperable Centric
    Concept of Information Supply Chain and
    Integration Points
  • Services-based Infrastructure(s) Everything a
    Service including Security Service Framework

Technology Service View IT aspects of business
transactions
4
Goals
  • Propose a seamless government process
  • And business- technical architecture that
    provides
  • Business Process Focused Enterprise and Business
    Line Architecture
  • Maps the BRM to a Standard Business
  • Process Modeling- Vocabulary and Modeling
  • Federated Information Model based on
  • Diverse Set of Common Data
  • Business Process Driven Integration
  • Common Interoperability Framework between
  • G2G, G2B, G2C Access Channels within Business
    Line
  • Components from Business to Technical
  • Secure User Services.

5
Challenges Faced
  • Enterprise Architecture must become business
    driven
  • EA is needed for more than just Budget Active
    Living Blueprint!
  • Must link closely with the Mission of the
    Organization
  • Must map to the Strategic Direction and fit with
    the Performance Reference Model
  • Strategy Maps can be used for Goals to
    Performance Linking but is a change
  • Agency must align with or make recommendations to
    improve the OMB BRM
  • The Business Process must fit with the way
    operations are done today or assume a significant
    change will occur- organization change level must
    be assessed early.
  • Operations Concepts- Context diagrams showing
    people involvement level- level of automation,
    skills, etc
  • Translating the Business Process Models- must use
    a common language and set of Models
  • Business- Process must drive all aspects of EA/BLA

6
Overall Context Diagram Ideas built around
FEA/RM and FEAF
EA Governance Technology Management
Process Changes
Model Usage
  • BRM in Conceptual Strategy Stage
  • Service Component Model
  • Cross-cutting Security
  • Architecture
  • Successful EA Activities

Framework
Reference Models
Human EA Element
Business
Business
Architecture
Architecture
Transition
FEAF
Data Reference Model Using Federated Approach
Information
2.0
Information
PLAN
Data Architecture
Data Architecture
Applications Architecture
Applications Architecture
Security Service Framework
Technology Architecture
Technology Architecture
  • Interfaces,
  • Interoperability,
  • Integration
  • TRM
  • Mgmt

First gov
Access Channels
Channel X AAAA
IT Investment
PRM-Business Case -Value
Channel 1 XXX
Management
Management
Virtual Enterprises Connecting
Goal Select

Plan

Business Segments

Change
Evaluate
Next Phase
7
Interoperability and Information Exchange Focus
EA Governance Technology Management
Process Changes
Model Usage
  • BRM in Conceptual Strategy Stage
  • Service Component Model
  • Cross-cutting Security
  • Architecture
  • Successful EA Activities

Framework
Reference Models
Human EA Element
Business
Business
Architecture
Architecture
Transition
FEAF
Data Reference Model Using Federated Approach
Information
2.0
Information
PLAN
Data Architecture
Data Architecture
Applications Architecture
Applications Architecture
Security Service Framework
Technology Architecture
Technology Architecture
  • Interfaces,
  • Interoperability,
  • Integration
  • TRM
  • Mgmt

First gov
Access Channels
Channel X AAAA
IT Investment
PRM-Business Case -Value
Channel 1 XXX
Management
Management
Virtual Enterprises Connecting
Goal Select

Plan

Business Segments

Change
Evaluate
Next Phase
8
Using Business Reference Model Conceptual and
Strategic Stage
Strategy-Vision- Concept of Operations
Services to Citizens
Grants Research
Development Education
Loans Legal Financial Support Services
Business Process Specification and Design
OMB BRM
Department BRM
Support Delivery of Services
Public Affairs Internal Risk Mang. Business Mang
of Ingo IT Management
  • Federal Financial Service
  • Grants Assistance
  • Loans Assistance

Business Process Improvements
Achievement Goals (PRM)
Internal Operations/Infrastructure
Human Resources Supply Chain Manag.
Administration Resource Management
Access Channel Opportunity Analysis Matrix G2G,
G2B, G2E,G2C,IEE
Business Case Budget Formulation
Access ChannelLines of Business
Channel 1
Channel 2
Channel 3
9
Business Line Architecture
  • Adapt practices for information supply chain and
    trading community efforts along with research on
    Virtual Enterprises.
  • Focus on people to people defining and aligning
    around shared concepts, information that needs to
    be shared, with look at end to end information
    flow.
  • Virtual Communication Channels and Communities
    that form Virtual Enterprises based on agreed
    policies and principles.

10
BRM Conceptual Stage Process.Department/Agency
and Related Business Line Segment
Responsibilities to Business Communities
Strategic Department Plan PMA-Mandates, etc
EA Blueprint with Business Cases- Budget-
Performance Plan
Department/Agency Enterprise Architecture
Access Channels
Business Line Segment Responsibility
Business Line Segment Responsibility
Business Line Segment Responsibility
Business Line Segment Responsibility
Access Channels Mapping
Business Community
Business Community
Business Community
Business Community
11
Business Process Driven Integration Business
Process Leadership
Conceptual and Strategic Interface Alignment
Technical Interface Development
12
Information Modeling Process
13
FIMS Vision
meta-metamodel boxes are meta-meta-metadata
Object Metamodel
Relational Metamodel
Datatype Metamodel
XML Metamodel
metamodel boxes are meta-metadata (meta-entities)
model boxes are metadata (entities, instances)
data
OODBMS
RDBMS
Data Dictionary
XML Document
14
Federated Information Model Meta Data Management
15
Methods of Representing Information and Data
during different Phases Focus Conceptual
  • Conceptual Phase Macro Level- define with
    Templates the information needs and sources and
    group them into type categories structured,
    semi-structured, and unstructured- is proposed
    but the key is to connect the information as-is
    and the to-be or needs to be and to define a
    contractor and descriptive and quality
    information assertions very-very high level
    meta data including what goes in the Federated
    Information Model and what is managed by member
    of the Business Community.
  • Logical Phase Schemas should be represented in
    common way and be able to integrated into
    Federated Information Meta Model with XMI
    exchange and use of Meta Object Facility and
    RDF/RSS as they mature
  • Physical Phase Virtual Views with Security
    Access and no-ad-hoc queries except with high
    level Conceptual Query Languages unless
    specific Security authorization- data quality
    assertions and data quality checkpoints and
    exception handling

16
Information Categories Bottom of Stack
17
Federated Information Model Virtual Information
Integration Across the Business Line(s)
Departments and Agencies will Lead or participate
in many Business Lines and Business Communities
Department/Agency Enterprise Architecture
BL Federated Information Integration Plan
Access Channels
Business Line Segment Responsibility
BL- Federated Information Meta Model
BL- Federated Information Connect and
Access Services
Access Channels Mapping
Partner Connect and Access Services
Business Community
Other FED
State Partner
.
Local Partner
Semi-structured Information as-is to-be
Structured Data as-is to-be
Unstructured Cataloged information
18
Information Flow Model
19
Information Flow with Templates
20
Define Principles to Guide Boundary Crossing and
Collaboration
  • Identify the Boundaries(Divide Business Line into
    Segments) and understand what is exchanged now
  • Why are other information not exchanged
    Roadblock List
  • How can we promote Organized and Efficient
    CollaborationIncentives
  • Who are the key Stakeholders and Leaders? Get
    agreement on principles and turn over to the
    doers Interoperability Management Agreements
  • Define a cross-governance structure to
    Maximizes Freedom to Participate by the doers
    Business Line Interface Control Board
  • Provide a structure that allows for Equal
    Participation Independent of Organizational
    Level
  • Provide for sharing and Equal Participation
    Independent of Integration Maturity
  • Provide an Integration Process and Proven
    Integration Architecture and Evaluation and
    Readiness Assessment Integration Readiness
    Scorecard
  • When possible Preserve Autonomy of each
    group-segment but Harmonize, Provide Baseline and
    translate to common format when necessary.

21
Design Concepts for Alignment Common Mental
Model
  • Decentralization and Federation Messaging with
    agreed syntax and Semantics of messages
  • Modularity with Minimalist Protocol Stack
    extensibility
  • XML-based Data Model Metadata
  • Transport Neutrality
  • Application Domain Neutrality
  • Use Standards Mature Today and provide options
    for the Future.

22
Business Line Performance MetricsBusiness
Services for Value Achievement
Service Value Network (SVN)
  • Business Service Definition
  • Targeted Customers
  • Service definition (Scope, timing)
  • Source (Provider)
  • Value Exchange
  • POVs
  • Cost
  • Connect and Access Services Content/KM

BL Federated Information Integration Plan
23
Infostructure Competency Center More than
Technology Needed for Success!
  • NSA- Infostructure Project lead by Karen Brown
    at NSA
  • Is a Competency Center
  • Selects new enabling middleware technology
  • Keeps tracks of trends-especially around open
    standards
  • Develops Prototypes
  • Provides middleware platforms
  • Provides training and in-depth consulting support
  • Internal CRM function to track the support and
    trouble ticket requests
  • Consultants rotate between projects within the
    Center and sitting with the customers
  • Has Acquisition expertise coupled with strong
    knowledge of the mission of the agency
  • Has made a strong Business Case for the value of
    Infostructure with Rick Turner- NSA CIO but
    most importantly 20 projects that are using their
    services.

24
Infostructure Competency Center More than
Technology Needed for Success!
  • Vision
  • Strengthening the Data and Information Modeling
    with the use of Metadata (tools such as those
    from Metamatrix)
  • Share Strong knowledge of the latest tools and
    trends( Opsware, BEA-WLI/Security, Web
    Services-trends, etc, etc.)
  • Obtain Wider Recognition that skills in these
    vital infostructure commercial products are
    critical to transforming an organization and a
    broader business line community
  • Maintain a competency center with a mixture of
    government and contractor personnel- convincing
    procurement of the business value
  • Get industry-contractor community to recognize
    the importance of these new skill areas.
  • Share the experiences with the e-gov, HLS
    security communitiescurrently working with DISA
  • Find others in taking the Middleware competency
    center approach and network.

25
Recommend Infostructure Competency Center(s)
and Research Support
  • Infostructure not just Infrastructure is the
    value glue and knowledge that is needed.
  • NSA Infostructure Competency Center is a model
    that can be duplicated in departments or business
    lines- HLS
  • Strong link and involvement with the Vendor
    community and standards with active Government
    Domain Task Forces within OASIS,OMG, W3C, and
    IETF.
  • Encourage the NSF Digital Government to address
    key issues defined by Emerging Technology Working
    Group
  • Link to other research initiatives such as
    Grid, Web Service Component Architecture lead by
    DOE/NASA in the Science community, and Internet2.

26
Ongoing Activities
  • BRM-PRM and EA Maturity Presentation
  • Component-Based Approach
  • Security Architecture
  • Complete Initial Drafts of Concept Level Papers
    with many ideas at the technical level- draft
    templates, etc
  • Document Infostructure Competency Center
  • Provide early draft material
  • Work on edit material and consistency. Preface
    and Executive Summary.
  • Conduct and IAC-Government Review Day in November
    14, 2002- Falls Church Va with plans for HLS
    focused follow-up December 16th-(tentative)
Write a Comment
User Comments (0)
About PowerShow.com