Business Line Challenges: Strategic Approach and Business Line Implementation

1
Business Line Challenges Strategic Approach
and Business Line Implementation

• John Dodd - CSC

2
Why We Focus on E-governmentBusiness Lines-We
Live in a Web of Interdependencies
Vision of How It Should Work?
Intra-agency
Agency to business
Inter- and Intra-governmental
Agency to the public
76 of on-line Americans visited government
online in 2001
3
Objective

• Breaking the Functional Stovepipes

• Business Line Focus Areas
• Business Line Implementation Process
• Using Enabling Technology
• Technology Alone Wont Do it! Government
  Enterprise Architecture Framework (GEAF)

4
Expanding the Transformation by Modernizing
Across Agencies from Budget- IAC key concepts

• Establish targets for consolidation of IT
  initiatives to achieve substantial cost and
  citizen service gains
• Business Line Architecture- Business Communities
• Analyze IT redundancies and gaps in order to
  achieve citizen outcome goals
• Strategy and Business Community Agreements
• Business Line Owners in agencies are identified
  and provided with the authority and resources to
  lead cross-agency consolidation efforts.
• Beyond Cross-agency to Cross Government
  Federal-State-Local along with Industry Partners

5
Expanding the Transformation by Modernizing
Across Agencies from Budget- IAC key
concepts(cont.)

• Resources and committed by both the business line
  owners and the involved agencies.
• Obligation and Master Business Line Schedule and
  Achievement Goals are defined and updated on
  Annual Basis.
• OMB oversees uses FEA
• Work with NASCIO, etc and defines Enterprise
  Architecture Alignment for Government Enterprise
  Architecture Framework and Alignment Steps and
  Business Line Status Report
• Communicate with key Congressional Stakeholders..
• Business Line Communication to Government,
  Mayors, Counties along with Federal Stakeholders

6
Current Business Line Focus

• Financial Management
• Data and Statistics
• Human Resources
• Monetary Benefits
• Criminal Investigations
• Public Health Monitoring

7
Learning and Extending to Business Line
Architecture- Development and Integration Approach

• Learn from portions of the Government that have
  a Business Line approach
• Factor in best-practices in netmarkets, supply
  chain and extensive review of e-government,
  technologies.
• Define a High Level Process and Architecture
  Framework that extends FEA Reference Models that
  can be built with COTS or selected components and
  uses Model Driven Architecture and Integration
• Take one or two of the areas and test the
  concepts on papermini-Red team..
• Use Justice Global Network and Small Business as
  models..

8

CASE-Based Collaborative Network Common
Information Model and Pub-Sub Alerts
State(s) Investigators
Local Police
Special Task Force
Gateway
Business Line Hub
Partner Tailored Content Deployment Templates
Federal Investigators
Evidence Models
9
Business Line ArchitectureBusiness Services for
Value Achievement integrating Government Services
Providers SBA One Stop Example
Service Value Network (SVN)

• Business Line Architecture with Outcomes
• Targeted Customers Small Business
• Business Line Leader SBA
• Business Compliance One Stop
• Service Provider Business CommunityFederal,
  State, Local
• Outcome Reduce Cost, improved access, etc

Business Line Federated Service-Information Int
egration Plan
Functional Services
10

Business Line Implementation Cycle
Business Line Gateway(s)
Governance
Discovery
Define
Business Line Architecture Repository
Business Line Integration Hub(s)
Deployment Files
Statistics
Integrate
Deploy Adapt
Integration Time-boxes Releases
11
Categorizing Business Line needs by
Characteristics
Autonomy and Connection
Often Called
E-Science Business grid
Data Process Sharing
Different Functions-Common Data
Cases-Case Networks
Common Function- Different Data
Service Network
Solution Frameworks For Each Block?
12
Business Service Framework The 4Cs
Commitments Obligations Responsibilities Measures
Community Organization Collaborative Agreements
Accountability Roles
Business Line Implementation Agreement
Content Information Service Resources
Service Assets
Conduct Policies Procedures Rules of
Service Performance
13
Common Infostructure- Process Emergence of
Business Service Network
Network as a Service Delivery Platform
Firewalls- enforcement points
Lead Agency X
Support Agency y
Integration Point
Business Line A Architecture
Common Infostructure Framework
Context
IntegrationZone
Business Line B
Business Line C
14
Business Line Implementation Environment
Business Line Analyst and Technical Analyst
Business Line Integration Development Environment

Repository
Operational BL Hub and Business Partner Gateways
Management Business Line Community Policy
Platform Independent Models
Platform Specific Models
Change Management Statistics
Core Model Driven-XML Infostructure
15
Business Line Integration Hub Architecture Data
Interchange Analysis Portal- Declaratively
Adapting to changing Needs
Data Sources
User Interfaces
Analysis Services
Virtual Data Integration
Virtual Query And Trigger Setting Analysis
Review
Federal
Pattern of Interest
XML
State
Content Semantic Analysis
XML
Information Routing and Business Process
XML
XML
Alert Condition
Zone Storage
Information Ingest and Translate
Data Mart
16
One-Stop Exchange
Web services
Web services Integration Platform
Execution Engine
Document Processing
Business Document
Legacy
Service Oriented Interfaces
Adapters
Simple Web service
XML Message
COTS
Database
Combined Business Processes
Portal And Display Services
Service Definition Descriptions
Application Server Platform
Other Devices
GUI Interfaces
17
Technology Management Business Line Architecture
Readiness- 80-90 Mainstream- Selective New
Technologies
Visionaries
Chasm

• XML-SOAP
• Model-Driven Architecture
• Services to Components
• Virtual Views- Metadata Modeling
• Community Trust
• Visual-Business Model Driven
• Languages

Pragmatists
High Value Capability
Mainstream Market

• Early Market

Innovators and Early Adopters
Pragmatists
18
Beyond Technology

• Policies are needed
• Business Line Solution Frameworks- Proof of
  concepts- Actions Needed
• Government involvement in Standards Organizations
  with Government Contractor Support- refine the
  standards to meet use cases
• Strong Focus on Security- Privacy- Trust
• Defining Competency Centers with government and
  contractor personnel that can share the knowledge
  and support Cross-Agency and Cross-government
  projects

19
Summary

• Need to have a strategy for Business Line
  Implementation and Information Management
• Architecture alone does not provide
  interoperability we need to think strategically
  and differently to Break the Functional
  Stovepipes
• We need to build Business Communities that cross
  organizational boundaries by first creating
  Conversations around the topic
• Business Lines will differ but a few and not
  100s or 1000s alternatives are needed.
• Fixed single approaches dont work we need to
  develop for choice

20
Contact Information

• For more information about IAC, go to
• www.iaconline.org
• For more information about the IAC EA SIG, please
• contact Kay Cederoth at
• Kay.Cederoth_at_CA.com
• For more information on each of the IAC EA SIG
• White Papers, go to
• http//www.ichnet.org/IAC_EA.htm