Enterprise Architecture
Planning
(EAP)
Discussion
•
What is Enterprise Architecture Planning (EAP)?
•
What is an EA used for?
A comprehensive blueprint of an organization.
The structure of (Enterprise) components and their
relationships, as well as principles and guidelines governing
their evolution over time.
A common understanding by all, of the names and definitions
of an organization’s entities.
The EA is a strategic asset repository which
defines the current and target architecture
environments, including:
•the
business
,
•the
information
,
•the
technology
, and
•the
transitional processes
.
What is an Enterprise Architecture?
PERSON PLACE THING EVENT CONCEPT
CG MEMBER CG ORGANIZATION COAST GUARD ASSET MARITIME ACCIDENT REGULATION AUXILIARIST NAVIGABLE WATERS ATON COASTAL INTRUSION LAW MARINER GOVERNMENT FACILITIES COMMERCIAL VESSEL RESPONSE ACTIVITIES STANDARDS RECREATIONAL BOATERS AIR RECREATIONAL BOAT ATON DISCREPENCY DIRECTIVE CONTRACTORS BRIDGES PORT FACILITY PREVENTION ACTIVITIES PLAN GOVERNMENT CONTACTS REGULATED MANUFACTURERS ICEBERG DEFENSE OPERATIONS MISSION
REGULATED MANUFACTURERS HAZARDOUS MATERIAL ACQUISITION LEGAL REQUIREMENT CASUALTY CUSTOMER ASSET SUPPORT OPERATIONS INTERNATIONAL AGREEMENT
BUDGET BUDGET BUILD POLITICS RADIO FREQUENCY SPECTRUM CASE
SUPPORT ASSETS
TRAINING/EDUCATION PROGRAMS CASE
META DATA FUNDS
Examples - Entities
Source: U.S. Coast Guard Information Architecture
A distinguishable - person - about which information is kept.
place,
T1 Lines
HQ
FINCEN
MLCP
OSC
ISC Honolulu
D17
AR&SC ISC Boston ISC Ports TISCOM
ELC PPC ISC NOLA
ISC Mia. ISC St Louis ISC Cleve. CAA MLCA
WMEC
WPB WLB
AOR
FACILITIES
INFRASTRUCTURE
PLATFORMS
PERSONNEL
Some EAP Components
•
A standard methodology
•
A standard set of templates
•
A repository
•
A configuration management process
•
Easy access
List of Locations Important to Business
Node=Major Business Location
Data Function Network People Time Motivation
List of Things Important to Business
Entity=Class of Business Thing
List of Processes the Business Performs
Function=Class of Business Process
List of Organizations Important to Business
Agent=Major Org Unit
List of Events Significant to Business
Time=Major Business Event
List of Business Goals/Strategies
End/Means=Major Business Goal/CSF
e.g., Entity Relationship
Diagram
Ent=Business Entity Rel=Business Rule
e.g., Function Flow Diagram
Function=Business Process
e.g., Data Model
Entity=Data Entity Relationship= Data
Relationship
e.g., Structure Chart
Funct=Computer Funct Arg=Screen/Device
Formats
e.g., System Architecture
Node=Hardware/ System Software Link=Line Specification e.g., Logistics Network
Node=Business Location Link=Business
Linkage
e.g., Program
Funct=Language Stmts Arg=Control Blocks
e.g., Network Architecture
Node=Addresses Link=Protocols
e.g., Organization Chart
Agent=Org Unit Work=Work Product
e.g., Business Plan
End=Business Objectives Means=Business
Strategy
e.g., Human Interface Architecture
Agent=Role Work=Deliverable
e.g., Security Architecture
Agent=Identity Work=Transaction
e.g., Processing Structure
Time=System Event Cycle=Processing Cycle
e.g., Control Structure
Time=Execute Cycle=Component Cycle
e.g., Timing Definition
Time=Interrupt Cycle=Machine Cycle
e.g., Knowledge Architecture
End=Criterion Means=Option
e.g., Knowledge Design
End=Condition Means=Action
e.g., Knowledge Definition
End=Subcondition Means=Step e.g., Data Definition
Description
Ent=Fields Rel=Addresses e.g., Data Design
Entity=Segment/Row Relationship=Pointer/
Key
e.g., Data Flow Diagram
Funct=Appl Function Arg=User Views
Analyst Engineer Secretary
e.g., Human/ Technology Interface
Agent=User Work=Job Analyst Engineer
e.g., Master Schedule
Time= Business Event Cycle=Business Cycle
e.g., Distributed System Architecture
Node=Info Sys Funct Link=Line Char
Secretary
Zachman’s Framework for
•Acquisition
•Investment decisions
•Modeling & Simulation
•Analysis
•Requirements definition
•Plan baseline
Operational
View
Identifes Warfghter
Relationships and Information Needs
Systems
View
Relates Capabilities and Characteristics to Operational Requirements
Technical
View
Prescribes Standards and Conventions
Specifc Capabilities Identifed to Satisfy Information-Exchange Levels and Other
Operational Requirements
Technical Criteria Governing Interoperable Implementation/ Procurement of the Selected System Capabilities
Pro cessin
g a nd L
eve ls of Inform
atio n E
xch ange Req
uireme nts
Bas ic T
ech nology Sup
portab ility
and New
C apa
bilities
Syste
What is an EA used for?
•
Promote interoperable and cost-effective systems
•
Provide the rules, guidance and product descriptions
for developing and presenting architectural
descriptions
•
Ensure a common denominator for understanding,
comparing, and integrating architectures.
•
Enable architectures to contribute more effectively
to engineering interoperable and cost-effective
systems.
Information Systems Technical Architecture
COMDTINST 5230.45A Information Systems Technical Architecture
COMDTINST (USCG COE) COMDTINST (USCG COE) COMDTINST
5230.59A
Standard Workstation III Configuration Management
Policy COMDTINST
5200.16 Standard Workstation III
Configuration Management Policy
COMDTINST 5200.16
USCG C4ISR Baseline Architecture
COMDTINST 3090.6 USCG C4ISR Baseline Architecture
COMDTINST 3090.6 Planning Approval
for Automated Information Systems
(AIS) COMDTINST
5231.2 Planning Approval
for Automated Information Systems
(AIS)
Standard Terminal Application Software DeploymentCOMDTINST
5234.3 Standard Terminal Application Software DeploymentCOMDTINST
5234.3
Information Technology Life Cycle and Configuration Management
Policy COMDTINST 9999.99 Information Technology
Life Cycle and Configuration Management
Policy COMDTINST 9999.99
IT Life Cycle and CM Policy Consolidation
IT
Systems Development Plan
(DRAFT) COMDTINST
9999.99 IT
Systems Development Plan
(DRAFT) COMDTINST
9999.99
Other Policy TBD Other Policy
Benefits
Facilitates information services that provide:
flexibility,
interoperability,
reliability,
Business Benefits of EAP
• Focus on strategic use of technology for managing data as an asset
• Standard vocabulary facilitates communication and reduces inconsistency and data redundancy
• Documentation increases understanding of the business
• Models can be used to explain the business and assess the impact of business changes
• Decision making policies can be reviewed
• Integration of current systems with new systems is considered. • It allows for a comprehensive, objective and impartial approach • The long range systems plan compliments the business plan • A cost-effective long term solution considers rate of return
• It involves a feasible migration strategy with short term achievements • it is easier to assess the benefits of impact of new systems and software • it allows easier accommodation of dynamic business changes such as mergers,
acquisitions, new products, lines of business.etc.
• Management participation provides a business prospective, credibility, confidence,
and demystifies system development.
Benefits to the Business of planned systems
• More responsive to customer’s needs • Reduced data-entry costs
• Head-count is reduced
• Increased productivity of personnel permits increased level of business and containment of costs
• Improved skills raise enthusiasm and loyalty
• Efficient systems maintenance means improved service.
• Architectures eliminate complex costly interfaces incongruent systems • Management decisions in all functional areas will be based on more
accurate and timely data,
leading to various improvements and cost-saving measures • End user has direct access to shared data
• New systems are developed faster and at less cost due to common data, common code, and
a shortened requirements phase
• Easier to evaluate and select vendor SW packages • Effective use of repository and CASE products
"You may think this is too much work… Or, it takes too long
And it costs too much Or is too theoretical
Or too high risk Or too whatever.
However, if that’s your assessment… You can’t complain that
the systems aren’t “aligned” with the enterprise,or are inflexible,
or cost too much,
or that vital information is not available, or that the data you get isn’t any good, or too late,
or you can’t change anything, or that I/S is slow and unresponsive…
and, I am here to tell you
Outsourcing isn’t going to fix the problem. Packages (in themselves) won’t fix the problem.
Decentralization won’t fix the problem. And, the Internet isn’t going to fix the problem.
No amount of money, Or technology is going to fix the problem!
It is NOT a technical problem, it is an ENTERPRISE problem.
Only ACTUAL WORK is going to fix the problem, and “Someday, you are going to wish you had all those models,
Enterprise wide,
horizontally and vertically integrated, at excruciating level of detail.”
You might as well start working on them TODAY!!! John Zachman
Next Steps
•
CKO Charter an Enterprise Architecture Configuration
Control Board (EACCB)
• Identify goals, objective, principles
• Establish membership
• Identify a methodology
• Identify a framework
• Identify resources
• Define deliverables
• Establish a timeline
