Enterprise Solution Architecture

1

• Unification Simplification Through
• Cooperation
• Innovation
• Opportunity

Linking CPIC to Solution Architecture CPIC
BriefingUSGS, January 25, 2005 Daud
SantosaChief Technology Officer
2
Todays DOI Business Challenges

• Do more with less increase efficiency
• Worldwide collaboration to protect lives with
  reduce cycle time
• Requirement for agency collaboration as well as
  global collaboration,
• Changes in administration, direction and
  priorities
• eGovernment transformation

3
DOI IT Challenges

• System inter-dependencies
• Application redundancy (Based on EA Blueprint)
• Data base proliferation and data redundancy
• Legacy systems and environments
• Insertion of new technology
• Stovepipe system-focus
• Long waterfall development cycles
• Paper-based artifacts
• External mandate-driven
• Fewer and uncertain resources, workforce
  competency gaps, engrained legacy culture

4
Reason For Change

• The problems we face today cannot be solved on
  the same level of thinking we were at when we
  created themAlbert Einstein
• "You are today where your thoughts have brought
  you, you will be tomorrow where your thoughts
  take you" James Allen

5
The Evolution of Business and Architecture
N-Tier
Distributed Object
Components
Services
Monolithic
Structure
Client Server
3-Tier

• In order to alleviate the problems of
  heterogeneity, interoperability and ever changing
  requirements, such an architecture should provide
  a platform for building application services with
  the following characteristics
• Loosely coupled
• Location transparent
• Protocol independent
• Source IBM Redbook Patterns Service Oriented
  Architecture and Web Services

6
Example Architecture Process Overview
Target IT App.Port / Infra. Initiatives
Aligned per IT Strategy
Assess Business Alignment
Respond to Business Change
(SELECT)
Proposed Concept
1
Develop Business Case
Unacceptable Alignment
Assess Business Case Proposal
Acceptable Alignment
(CONTROL)
Enterprise Solution Architecture (Apply Patterns)
2

• Define
• Build
• Implement
• Operate

TRM Standards
(SELECT)
Assess Technology Compliance
Project Authorization
3
Evaluate Architecture Compliance
Acceptable Compliance
Unacceptable Compliance
4
Disapproved
Unacceptable Conformance
Report
Compliance Assessment
5
ARB Report
Architecture Roles
Audit Reports
Assess Waiver/ Exception Request
Architecture Process
Process -
7
Strategic Initiative 1Customer Service That
Differentiates
Purpose
Technology Product and Service Solutions That
Differentiates the DOI from the Others
Goals (What)
Key Elements
1. Empower DOI customers/citizens to help
themselves 2. Improve the quality of our products
and services 3. Make information timely,
consistent, and easy for customers to
obtain 4. Remove sources of customer/citizens
frustration 5. Present an integrated customer
contact environment
5
Customer Self-Service
4
Personalization
Strategies (How)
3
Integration
Increased Customer Satisfaction
1. Prioritize self-service opportunities and get
support 2.a) Baseline customer satisfaction and
quality perceptions 2.b) Reduce duplication of
information 2.c) Link customer satisfaction and
quality goals with OCIO strategies,
plans, and performance metrics 3. Manage
customer complaints via a closed-loop system
that includes automatic escalation 5. Match
availability of support to customer needs
2
Transactions
1
Data
Increased Value

• Improves customer satisfaction
• Reduces costs to service customers
• Increases stakeholder confidence

• Provides intangible benefits
• Aligns supports with E-Gov needs

Benefits (Why)
6
8
Example of Enterprise IT Roadmap
9
Example of Enterprise IT Roadmap - continue
10
What are the Solution Architecture consists of

• Solution Objectives and Scope
• High Level Business Requirement
• Solution Overview Diagram
• Use Case Model (Diagram and Text)
• Non-functional Requirements
• Component Model
• Deployment / Operational Model
• Architectural Decisions

11
IMARS High Level Business Services

• Depicts Business Services for eGovernment
• Establishes Solution Scope
• Includes Enterprise Service Oriented Architecture

12
Solution Overview Diagram Identify Application
Pattern and Service Reference Model
Digital Asset ServicesDocument Management,
Record Management
Process Automation ServicesTracking
Workflow, Routing Scheduling
Incident LE Services
Self Service
Extended Enterprise
NIBRS
Case Management Services
Emergency Management Services
Application Decomposition Tier
Access Integration Role Based Personalization
Security Services
Central Violation Bureau (CVB)
Back Office Services Integration
IMARS Users
Inquire Update Services
I N T R A N E T
I N T E R N E T
Consolidated Imars View
Enterprise Integration Hub
Authentication Authorization Services
Watch Office (DHS)
Other Users
Field Interview Services
Record Management Services
Customer ServicesCustomer Initiated
AssistanceSelf Service
Other Agencies
Track Evident and Property Services
Back Office ServicesIntegration
Customer ServicesCustomer Initiated
AssistanceSelf Service
Information Aggregation
CRM Services
Messaging Collaboration
Collaboration
Crime Pattern Predictive Analysis Services
GIS Services
Administration Services
13
This view depicts the logical run-time topology
(J2EE), which provides a High Level solution
architecture that adheres to the composite
patterns for IMARS.
14
This view depicts the logical run-time topology
(.NET), which provides a High Level solution
architecture that adheres to the composite
patterns for IMARS.
15
Enterprise Projects and DOI processes
16
Enterprise Integration Activities
17

• Q A

18
My Information

• Daud Santosa
• Chief Technology Officer
• Department of the Interior
• Office 202-208-5064
• daud_santosa_at_ios.doi.gov