Transcript Slide 1

Reporting Department of Defense
Programs to OMB
Improving PEO and Local Program
Manager Use of Exhibit 300s to Show
Business Value / Architecture Alignment
December 2005
DRAFT
DRAFT
Briefing Overview
• Summary of Exhibit 300 Reporting
• Strategic Alignment
• Program Progress
• Program Impact
• Architecture Alignment
• Architecture Reporting
• Program Manager Assistance
DRAFT
2
Summary of Exhibit 300 Reporting
 OMB Circular A-11 Defines the Federal Budget Development and
Reporting Process for all agencies.
 The Exhibit 300 template is used for the annual reporting of
major or mission critical information technology (IT) programs.
 DOD submitted 171 Exhibit 300 reports in FY 2004 to document:
- Strategic alignment with the PMA and DOD/Service goals.
- Program progress using Earned Value Management metrics for cost,
schedule, and performance.
- Program impact using the Federal Enterprise Architecture (FEA)
Performance Reference Model (PRM) outcome/output measures.
- DOD architecture alignment using the DOD Architecture Framework
(DODAF) and other FEA Reference Models (RMs)
 OMB scores the 300 on a 1-5 scale – impacts funding / control.
 DOD PEO and Local IT Program Manager understanding of
Exhibit 300s and the FEA RMs needs to improve.
DRAFT
3
Exhibit 300 Reporting
Strategic Alignment
DOD IT Programs need to show alignment with:
t em
s
Joint
Mission
Areas
Global
Military
Information
Service
Grid
Operational
NGA
AF
Task
Force
NEO JTF
al
IC
nic
ch
Global
Information
Grid
Te
Joint
Joint
Mission
Mission
Areas
Areas
The President’s Management Agenda
OMB e-Government Initiatives
DOD Strategic Goals and Joint Vision 2020
Service-specific Strategic and Warfighting Goals
Local Command Goals for Readiness
Sy
s
1.
2.
3.
4.
5.
Framewor
k
CADM – Data Model
National
IC
CC
Theater
DARS - Repository
CJTF
Tactical
Internet
Military
Service
Targeting/BDA
DRAFT
NGA
NEO JTF
Tactical
CC
DOD Reference
Models (FEA)
Targeting
& BDA
Tactical
Internet
AF
Task
Force
4
Exhibit 300 Reporting
Program Progress
DOD IT Programs need to show progress in the format
of Earned Value Management (EVM) which has been a DOD
best practice to reduce program risk for over 25 years.
OMB requires EVM formatted measures of cost, schedule
and performance… both the baseline and actual. 10%
variance is allowed, beyond which a Corrective Action Plan
is required to report and correct the variance.
Comparison of OMB-Approved Baseline and Actual Outcome for
Phase/Segment/Module of a Project (Investment)
OMB-Approved Baseline
Actual Outcome
Schedule
OMB
Exhibit 300
Annual Report
Description of
Milestone
Start
Date
End
Date
Duration
(in days)
Schedule
Planned
Cost
Funding
Agency
Start
Date
End
Date
Percent
Complete
Actual
Cost
1.
2.
3.
DRAFT
Completion date: OMB-approved baseline:
Estimated completion date:
Total cost: OMB-approved baseline:
Estimate at completion:
5
Exhibit 300 Reporting
Program Impact
DOD IT Programs need to show program impact using the
Federal EA Performance Reference Model (PRM).
The PRM requires the identification of inputs, outputs, and
outcomes for each business process that the IT program
is supporting. This is called a “Line-of-Sight.”
DRAFT
6
Exhibit 300 Reporting
Architecture Alignment
DOD IT Programs need to show program alignment using
the DODAF and the five Federal EA Reference Models
(RMs) and integrated Security Profile.
Federal Enterprise Architecture (FEA)
Performance Reference Model (PRM)
Business Reference Model (BRM)
• Lines of Business
• Agencies, Customers, Partners
-
Service Component Reference Model (SRM)
• Service Layers, Service Types
• Components, Access and Delivery Channels
Technical Reference Model (TRM)
• Service Component Interfaces, Interoperability
• Technologies, Recommendations
Based Architectures
Business - Driven Approach
Focus)
(CitizenCentered
-
Operational
Component
• Government -wide Performance Measures & Outcomes
• Line of Business -specific Performance Measures & Outcomes
Data Reference Model (DRM)
• Business focused
Data Standardization
• Cross --agency Information Exchanges
DRAFT
7
Exhibit 300 Reporting
Architecture Reporting
DOD IT Program reporting and Exhibit 300 preparation is
enhanced by using a “DODAF-FEA Reporting Framework”
that maps the DODAF artifacts (AV, OV, SV, and TV) to
DOD-enhanced FEA Reference Models.
DOD Architecture Framework
DOD Reference Models
Federal EA Reference Models
Architecture Design
and Implementation
Architecture / Program / Budget
Planning and Reporting
Program / Budget
Planning and Reporting
Information
Mission
Business
Areas
Intelligence
Warfighter
al
nic
ch
Te
Sy
ste
ms
DoD Architecture
Knowledge
Operational
Strategic Goals
and Outcomes
DoD Performance
Reference Model
Operations and
Sustainment
DoD Business
Reference Model
Logistics and
Support
Netcentric
Communications
Networks
and Platforms
Global Information Grid
DRAFT
Service Component
Reference Model
Assurance
Data & Information
Reference Model
DoD Technical
Reference Model
DoD Security
Profile
FEA Performance
Reference Model
FEA Business
Reference Model
Annual OMB
Reporting
FEA Service Component
Reference Model
FEA Data and Information
Reference Model
FEA Technical
Reference Model
FEA Security Profile
8
Exhibit 300 Reporting
Architecture Reporting (continued)
DOD-enhanced FEA Reference Models have incorporated
DOD-specific information on line of business subfunctions
(BRM), services and components (SRM) and technology
standards (TRM). The PRM and DRM remain the same.
Headquarter
Order
M anagem ent
Field Order
M anagem ent
P1
Order Processing
M ission Order
C
Field Staff Responsibilities
M obile Order
M anagem ent
XY
Z
X
Y
M obile Staff Responsibilities
System Functionality
Description (SV-4)
Systems Functionality
Sequence and Timing
Descriptions (SV-10 a/b/c)
Systems Interface
Description (SV-1)
NODE A
System 1
System 2
One-Way
Communications
Link
Two-Way
Communications
Links
System 4
System 3
CONNECTION
TO NODE B
Local Area Net
Sys
t
System 5
EXTERNAL
CONNECTION
(OUTSIDE THE
NODES OF INTEREST)
CONNECTION
TO NODE C
DoD EA TRM
Organizational
Relationships
Chart (OV-4)
DRAFT
GIG Architecture
High Level
Operational Concept
Graphic (OV-1)
Op Activity Model
(OV-5)
• .....
• .....
• .....
DoD
DoD EA SRM
DoD EA BRM DoD EA DRM DoD EA PRM
Operational
Systems Data Exchange
Matrix (SV-6)
Systems Performance
Parameters Matrix (SV-7)
Systems Technology
Forecast (SV-9)
OMB
l
Systems Communications
Description (SV-2)
ica
chn
Te
Systems Evolution
Description (SV-8)
Technical Standards
Forecast (TV-2)
CONNECTION
TO NODE B
Exhibit
300s
(TRM, SRM, BRM, DRM, PRM)
Technical Standards
Profile (TV-1)
Physical Schema
SV-11
Activity to System
Function (SV-5)
System - System
Matrix (SV-3)
FEA
RMs
Y
X
s
B
em
NODES
TIME A
T1
T2
T3
Battalion Main CP
Receive
M is sion
Orders
Determ ine
Order Type
Logical Data
Model (OV-7)
Warfighter
MA
Intel
MA
Validation
Decision
2.1.2
•
-
Business
MA
L1
2.1.1
Battalion Liason Officer
Op Node
Connectivity
Description (OV-2)
X
L1
Classif ied
Order Ty pes
Battalion Section 1
Validate
Orders via
Secure Uplink
2.1.3
Battalion Section 2
Unclassif ied
Validate
Orders via
Phone
2.1.4
Enterprise Information Environment(EA) MA
L2
System
Provide DB
lookup for
order types
2.1.1
Peacetime
Information
Exchange Matrix
(OV-3)
Operational Activity
Sequence and Timing
Descriptions
(OV-6 a/b/c)
Slide concept courtesy of The MITRE Corporation
Global Information Grid
MA – Mission Area
9
Exhibit 300 Reporting
Architecture Reporting (continued)
The DOD Reference Model information will be useful for
DOD planning, budgeting, and reporting, Exhibit 300
preparation, and DODAF-driven designs of IT systems.
Leveraging DoD EA RMs
DoD Performance Report & Plan
DoD Data Management Strategy
DoD Information Standards Repository
Exhibit 300
IT Program
Reports
DoD Net-Centric Enterprise Services
DoD GIG Architecture & NCOW RM
•Information is produced by the various data sources
•Information is consumed by the DoD EA RMs
•Information is produced by the DoD EA RMs
•Information is consumed by the various data sources
Intel Community Functions and Service Components
DoD Business Enterprise Architecture
Universal Joint Task Lists, Common Operational Activities Library
CADM, DoDAF, DARS
OMB CPIC Process
Internal DoD
FEA RM
DoD EA RMs Working
Documents
DoD EA RM
Operational
OperationalView
View
PRM
DRM
DOD
Warfighters
TRM
Congress
SRM
Services &
Agencies
BRM
WMA BMA IMA
EIEMA
Large & Small
Businesses
Infrastructure
Services
DoD CPIC Process
External DoD
tools
DoD Architecture Data
Abstracted and presented
in the DoD EA RMs; first,
in a set of working
documents, and second
in a set of reference
models for external
consumption. Tools are
used as much as possible
to extract and render the
data as abstract
information
• •Functional
Functional(operational)
(operational)requirements
requirements
• • Processes
Processesand
andrelationships
relationships
• • Information
Informationneeds
needs(content,
(content,form,
form,
protection)
protection)
• • User
Userfunctions
functions
• • Performance
bounds
Performance bounds
Systems
SystemsView
View
Applications
EAI/ETL
APIs
Standards
•
•
•
•
•
•
ANSI X12 ICs
EDIFACT
HL7
XML
HTML
Proprietary (rare)
Perimeter Security
Mechanisms Smart
Firewall
Data
Card
Repositories
VPN
COTS
Products
JTA IT
Standards
GCSS-AF
DII
COE
• •System
Systemfunctional
functionaldescriptions
descriptions
• •System
Systeminterfaces
interfacesand
andconnections
connections
• •Operations-to system
Operations
Operations-to
systemtraceability
traceability
Technical
TechnicalView
View
• •Technical
TechnicalArchitecture
ArchitectureProfile
Profile
• •Standards
Standardsand
andTechnology
Technology
Forecast
Forecast
DODAF Design Work
DRAFT
10
Exhibit 300 Reporting
Architecture Reporting (continued)
The DOD Reference Model information will also be useful
in DODAF-driven IT systems design work.
Performance Reference
Model (PRM)
Initiative Business and
Performance Drivers
(J2EE)
XML, SOAP
Access Control List
Protocol Firewall (HTTP)
X. 500, TCP/IP
Records Mgmt
Service
Platforms
Defines The
Architecture
Financial
Mgmt System
XML, SOAP
Intranet / Extranet
Reduce the latency of business events
Easy to adapt during mergers and acquisitions
Integration across multiple delivery channels
Minimize total cost of ownership (TCO)
Leverage existing skills
Leverage legacy investment
Maintainability
Scalability
Access Control List
Protocol Firewall (HTTP)
X. 500, TCP/IP
Records Mgmt
Intranet / Extranet
Web Browser
Web Browser
Defines
•
•
•
•
•
•
•
•
Balanced
Scorecard
Reporting
Engine
Security (LDAP, Authentication, Auditing)
Presentation (JSP)
Portal
Business Logic (EJB)
Data Interchange (XML)
Data Management (JDBC, XBRL)
DRAFT
11
Exhibit 300 Reporting
Program Manager Assistance
OMB’s scores of DOD Exhibit 300s can effect program
funding and control. Low overall scores, or low scores in
special interest areas (risk, EVM, security) can result in
program funding being cut/withheld, or additional OMB
reporting requirements being levied.
DOD PEO’s and local PMs must therefore ensure that there
is a good understanding of the purpose and design of the
Exhibit 300 report in order to be able to accurately reflect
program alignment, status, and impact, as well as to justify
the associated outyear funding request.
The DOD Office of the CIO/NII is preparing several PEO/PM
workshops on Exhibit 300 preparation in January – April to
ensure that DOD and the Services are ready for BY 2007
Exhibit 300 preparation in the May – July timeframe.
DRAFT
12