Reporting Department of Defense Programs to OMB Improving PEO and Local Program
description
Transcript of Reporting Department of Defense Programs to OMB Improving PEO and Local Program
DRAFT
Reporting Department of DefensePrograms to OMB
Improving PEO and Local ProgramManager Use of Exhibit 300s to ShowBusiness Value / Architecture Alignment
December 2005
DRAFT
2
Briefing Overview
• Summary of Exhibit 300 Reporting
• Strategic Alignment
• Program Progress
• Program Impact
• Architecture Alignment
• Architecture Reporting
• Program Manager Assistance
DRAFT
3
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
4
Exhibit 300 Reporting
Strategic Alignment
DOD IT Programs need to show alignment with: 1. The President’s Management Agenda 2. OMB e-Government Initiatives 3. DOD Strategic Goals and Joint Vision 2020 4. Service-specific Strategic and Warfighting Goals 5. Local Command Goals for Readiness
DRAFT
Joint Mission
Areas
Joint Mission
Areas
NEO JTF
NGA
Targeting/BDA
AFTaskForce
Operational
Sys
tem
s
Technical
Framework
DARS - Repository
CADM – Data Model
Joint Mission Areas
AFTaskForce
Targeting& BDA
TacticalInternet
MilitaryService
NEO JTF
CC
NGA
Global Information
Grid
ICNational
Theater
CJTF
Tactical
CC
TacticalInternet
Global Information
Grid
IC
MilitaryService
DOD Reference
Models (FEA)
Joint Mission
Areas
Joint Mission
Areas
NEO JTF
NGANGA
Targeting/BDA
AFTaskForce
Operational
Sys
tem
s
Technical
Framework
DARS - Repository
CADM – Data Model
Operational
Sys
tem
s
Technical
Framework
DARS - Repository
CADM – Data Model
Framework
DARS - Repository
CADM – Data Model
Joint Mission Areas
AFTaskForce
Targeting& BDA
TacticalInternet
MilitaryService
NEO JTF
CC
NGA
Global Information
Grid
ICNational
Theater
CJTF
Tactical
CCCC
TacticalInternet
Global Information
Grid
IC
MilitaryService
DOD Reference
Models (FEA)
5
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 Schedule Description of
Milestone Start Date
End Date
Duration (in days)
Planned Cost
Funding Agency
Start Date
End Date
Percent Complete
Actual Cost
1.
2.
3.
Completion date: OMB-approved baseline: Estimated completion date:
Total cost: OMB-approved baseline: Estimate at completion:
DRAFT
OMBExhibit 300
Annual Report
6
Exhibit 300 Reporting
Program Impact
DOD IT Programs need to show program impact using theFederal 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.”
VA
LU
E
InputsInputs OutputsOutputs OutcomesOutcomesCause and
Effect
Cause and
Effect
Business ResultsBusiness ResultsCustomer ResultsCustomer ResultsProcesses and Activities
Processes and ActivitiesTechnologyTechnology Strategic
Outcome s
WHAT
NICS
ATLAS
Automated Commercial Env ironment
Firearms Integrated
Technology
WHAT
NICS
ATLAS
Automated Commercial Env ironment
Firearms Integrated
Technology
HOW
Percentage of attempted sy stems
penetrations av erted
Percent system
downtime
Percent of internal users
satisfied
Maintenance costs as
percentage of total costs
HOW
Percentage of attempted sy stems
penetrations av erted
Percent system
downtime
Percent of internal users
satisfied
Maintenance costs as
percentage of total costs
HOW
Number of vehicle
searches
Number of f ood
inspections
Number of background
checks
Number of weapons checks
HOW
Number of vehicle
searches
Number of f ood
inspections
Number of background
checks
Number of weapons checks
WHAT
Vehicle searches
Food inspections
Background checks
Weapons checks
WHAT
Vehicle searches
Food inspections
Background checks
Weapons checks
WHO
Indiv iduals subject to
background checks
Individuals subject to weapons checks
Individuals wishing to enter U.S. at Border Inspection
Station
WHO
Indiv iduals subject to
background checks
Individuals subject to weapons checks
Individuals wishing to enter U.S. at Border Inspection
Station
Secure the
Home-land
Secure the
Home-land
HOW
Number of complaints
about Border Inspections
Percent satisf ied with
Border Inspections
Average wait time at
Border Inspection
Station
HOW
Number of complaints
about Border Inspections
Percent satisf ied with
Border Inspections
Average wait time at
Border Inspection
Station
WHAT
Saf er f ood
Less crime and
violence
WHAT
Saf er f ood
Less crime and
violence
HOW
Percent of health
incidents attributable to
illegally imported f ood substances
Percent of crimes
committed using
illegally imported weapons
HOW
Percent of health
incidents attributable to
illegally imported f ood substances
Percent of crimes
committed using
illegally imported weapons
Line Of
Sight
TechnologyTechnology
OUTCOMES: Mission and business-critical results aligned with the Business
Reference Model. Results measured from a customer perspective.
OUTPUTS: The direct effects of day-to-day activities and broader processes measured
as driven by desired outcomes. A ligned with the Mode of Delivery in the Business
Reference Model.
INPUTS: Key enablers measured through their contribution to outputs –
and by extension outcomes
Strategic Outcomes
Value
Customer Results
•Customer Satisfaction•Service Coverage•Timeliness & Responsiveness•Service Quality•Service Accessibility
Customer Results
•Customer Satisfaction•Service Coverage•Timeliness & Responsiveness•Service Quality•Service Accessibility
Processes and Activities•Financial•Productivity and Efficiency•Cycle and Resource Time
Processes and Activities•Financial•Productivity and Efficiency•Cycle and Resource Time
•Quality•Management & Innovation
Technology•Financial•Quality & Efficiency•Information & Data•Reliability & Availability•User Satisfaction
Technology•Financial•Quality & Efficiency•Information & Data•Reliability & Availability•User Satisfaction
Other Fixed Assets
•Financial•Quality, Maintenance, & Efficiency•Security & Safety•Utilization
Other Fixed Assets
•Financial•Quality, Maintenance, & Efficiency•Security & Safety•Utilization
People•Employee Satisfaction & Quality of Worklife•Recruitment & Retention•Employee Development•Employee Ratios
People•Employee Satisfaction & Quality of Worklife•Recruitment & Retention•Employee Development•Employee Ratios
Mission and Business Results
•Services for Citizens•Support Delivery of Services•Management of Government Resources•Financial
Mission and Business Results
•Services for Citizens•Support Delivery of Services•Management of Government Resources•Financial
DRAFT
7
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.
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
Data Reference Model (DRM)
Business -focused Data Standardization
• Cross-agency Information Exchanges
Business
- Driven A
pproach(C
itizen- Centered Focus)
Performance Reference Model (PRM)
• Government -wide Performance Measures & Outcomes
• Line of Business -specific Performance Measures & Outcomes
Federal Enterprise Architecture (FEA)
Com
ponent- B
ased Architectures
Business Reference Model (BRM)
•
•
Service Component Reference Model (SRM)
• Service Layers, Service Types
• Components, Access and Delivery Channels
Technical Reference Model (TRM)
• Technologies, Recommendations
Data Reference Model (DRM)
• -
• -
--
Performance Reference Model (PRM)
• Government -wide Performance Measures & Outcomes
• Line of Business -specific Performance Measures & Outcomes
Federal Enterprise Architecture (FEA)
Com
ponent- B
ased Architectures
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
Data Reference Model (DRM)
Business -focused Data Standardization
• Cross-agency Information Exchanges
Business
- Driven A
pproach(C
itizen- Centered Focus)
Performance Reference Model (PRM)
• Government -wide Performance Measures & Outcomes
• Line of Business -specific Performance Measures & Outcomes
Federal Enterprise Architecture (FEA)
Com
ponent- B
ased Architectures
Business Reference Model (BRM)
•
•
Service Component Reference Model (SRM)
• Service Layers, Service Types
• Components, Access and Delivery Channels
Technical Reference Model (TRM)
• Technologies, Recommendations
Data Reference Model (DRM)
• -
• -
--
Performance Reference Model (PRM)
• Government -wide Performance Measures & Outcomes
• Line of Business -specific Performance Measures & Outcomes
Federal Enterprise Architecture (FEA)
Com
ponent- B
ased Architectures
Operational
Systems Technical
DRAFT
8
Exhibit 300 Reporting
Architecture Reporting
DOD IT Program reporting and Exhibit 300 preparation isenhanced by using a “DODAF-FEA Reporting Framework”
that maps the DODAF artifacts (AV, OV, SV, and TV) to DOD-enhanced FEA Reference Models.
Operational
TechnicalSys
tem
s
DoD SecurityDoD SecurityProfileProfile
DoD TechnicalDoD TechnicalReference ModelReference Model
Data & InformationData & InformationReference ModelReference Model
Service ComponentService ComponentReference ModelReference Model
DoD BusinessDoD BusinessReference ModelReference Model
DoD Performance DoD Performance Reference ModelReference Model
Global Information GridGlobal Information Grid
DoD ArchitectureDoD ArchitectureKnowledgeKnowledge
DOD Reference ModelsDOD Reference ModelsArchitecture / Program / Budget Architecture / Program / Budget
Planning and ReportingPlanning and Reporting
DOD Architecture FrameworkDOD Architecture FrameworkArchitecture Design Architecture Design and Implementationand Implementation
Federal EA Reference ModelsProgram / Budget
Planning and Reporting
WarfighterWarfighter
IntelligenceIntelligence
BusinessBusiness
Information Information
Strategic GoalsStrategic Goalsand Outcomesand Outcomes
Operations andOperations andSustainmentSustainment
NetcentricNetcentricCommunicationsCommunications
Logistics andLogistics andSupportSupport
NetworksNetworksand Platformsand Platforms
AssuranceAssurance
MissionMissionAreasAreas FEA PerformanceFEA Performance
Reference ModelReference Model
FEA BusinessFEA BusinessReference ModelReference Model
FEA Service ComponentFEA Service ComponentReference ModelReference Model
FEA Data and InformationFEA Data and InformationReference ModelReference Model
FEA TechnicalFEA TechnicalReference ModelReference Model
FEA Security ProfileFEA Security Profile
Annual OMBAnnual OMBReportingReporting
Operational
TechnicalSys
tem
s
Operational
TechnicalSys
tem
s
DoD SecurityDoD SecurityProfileProfile
DoD TechnicalDoD TechnicalReference ModelReference Model
Data & InformationData & InformationReference ModelReference Model
Service ComponentService ComponentReference ModelReference Model
DoD BusinessDoD BusinessReference ModelReference Model
DoD Performance DoD Performance Reference ModelReference Model
Global Information GridGlobal Information Grid
DoD ArchitectureDoD ArchitectureKnowledgeKnowledge
DOD Reference ModelsDOD Reference ModelsArchitecture / Program / Budget Architecture / Program / Budget
Planning and ReportingPlanning and Reporting
DOD Architecture FrameworkDOD Architecture FrameworkArchitecture Design Architecture Design and Implementationand Implementation
Federal EA Reference ModelsProgram / Budget
Planning and Reporting
WarfighterWarfighter
IntelligenceIntelligence
BusinessBusiness
Information Information
Strategic GoalsStrategic Goalsand Outcomesand Outcomes
Operations andOperations andSustainmentSustainment
NetcentricNetcentricCommunicationsCommunications
Logistics andLogistics andSupportSupport
NetworksNetworksand Platformsand Platforms
AssuranceAssurance
MissionMissionAreasAreas FEA PerformanceFEA Performance
Reference ModelReference Model
FEA BusinessFEA BusinessReference ModelReference Model
FEA Service ComponentFEA Service ComponentReference ModelReference Model
FEA Data and InformationFEA Data and InformationReference ModelReference Model
FEA TechnicalFEA TechnicalReference ModelReference Model
FEA Security ProfileFEA Security Profile
Annual OMBAnnual OMBReportingReporting
DRAFT
9
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.
Battalion Liason Officer
Battalion Main CP
System
Battalion Section 2
Battalion Section 1
Battalion Liason Officer
Battalion Main CP
System
Battalion Section 2
Battalion Section 1
2.1.2
DetermineOrder Type
2.1.1
Provide DBlookup fororder types
Order Types
2.1.4
ValidateOrders viaPhone
2.1.3
ValidateOrders viaSecure Uplink
2.1.1
ReceiveMissionOrders
X
ValidationDecision
Peacetime
L1
Unclassified
Classified
L2
L1
Operational
Systems
Technical
High Level Operational Concept
Graphic (OV-1)
Op Node Connectivity
Description (OV-2)
X YXZ
XY
Y
Systems InterfaceDescription (SV-1)
Op Activity Model (OV-5)
Information Exchange Matrix
(OV-3)
Activity to System Function (SV-5)
System Functionality Description (SV-4)
Organizational Relationships Chart (OV-4)
Systems Data Exchange Matrix (SV-6)
Operational Activity Sequence and Timing
Descriptions(OV-6 a/b/c)
NODE A
Local Area Net
System 1 System 2
System 3 System 4
System 5
EXTERNALCONNECTION(OUTSIDE THENODES OF INTEREST)
CONNECTIONTO NODE B
CONNECTIONTO NODE B
CONNECTIONTO NODE C
Two-WayCommunicationsLinks
One-WayCommunicationsLink
Systems Communications Description (SV-2)
System - System Matrix (SV-3)
Systems Technology Forecast (SV-9)
Technical Standards Forecast (TV-2)
Technical Standards Profile (TV-1)
Systems Performance Parameters Matrix (SV-7)
••----------------------------------------------------------------
• .....• .....• .....
Logical Data Model (OV-7)
Systems Functionality Sequence and Timing
Descriptions (SV-10 a/b/c)
Systems Evolution Description (SV-8)
Physical SchemaSV-11
A B C
T1T2T3
NODESTIME
Slide concept courtesy of The MITRE Corporation
P1
Order Processing
Field OrderManagement
Mobile OrderManagement
HeadquarterOrder
Management
Mobile Staff Responsibilities
Field Staff ResponsibilitiesMission Order
Battalion Liason Officer
Battalion Main CP
System
Battalion Section 2
Battalion Section 1
Battalion Liason Officer
Battalion Main CP
System
Battalion Section 2
Battalion Section 1
2.1.2
DetermineOrder Type
2.1.1
Provide DBlookup fororder types
Order Types
2.1.4
ValidateOrders viaPhone
2.1.3
ValidateOrders viaSecure Uplink
2.1.1
ReceiveMissionOrders
X
ValidationDecision
Peacetime
L1
Unclassified
Classified
L2
L1
Operational
Systems
Technical
Operational
Systems
Technical
High Level Operational Concept
Graphic (OV-1)
Op Node Connectivity
Description (OV-2)
Op Node Connectivity
Description (OV-2)
X YXZ
XY
Y
Systems InterfaceDescription (SV-1)
X YXZ
XY
YX YX
Z
XY
Y
Systems InterfaceDescription (SV-1)
Op Activity Model (OV-5)
Information Exchange Matrix
(OV-3)
Activity to System Function (SV-5)
Activity to System Function (SV-5)
System Functionality Description (SV-4)
Organizational Relationships Chart (OV-4)
Systems Data Exchange Matrix (SV-6)
Operational Activity Sequence and Timing
Descriptions(OV-6 a/b/c)
NODE A
Local Area Net
System 1 System 2
System 3 System 4
System 5
EXTERNALCONNECTION(OUTSIDE THENODES OF INTEREST)
CONNECTIONTO NODE B
CONNECTIONTO NODE B
CONNECTIONTO NODE C
Two-WayCommunicationsLinks
One-WayCommunicationsLink
Systems Communications Description (SV-2)
System - System Matrix (SV-3)
Systems Technology Forecast (SV-9)
Technical Standards Forecast (TV-2)
Technical Standards Profile (TV-1)
Systems Performance Parameters Matrix (SV-7)
••----------------------------------------------------------------
• .....• .....• .....
••----------------------------------------------------------------
• .....• .....• .....
• .....• .....• .....
Logical Data Model (OV-7)
Systems Functionality Sequence and Timing
Descriptions (SV-10 a/b/c)
Systems Evolution Description (SV-8)
Physical SchemaSV-11
A B C
T1T2T3
NODESTIME A B C
T1T2T3
NODESTIME
Slide concept courtesy of The MITRE CorporationSlide concept courtesy of The MITRE Corporation
P1
Order Processing
Field OrderManagement
Mobile OrderManagement
HeadquarterOrder
Management
Mobile Staff Responsibilities
Field Staff ResponsibilitiesMission Order
OMB
DoD
DoD EA TRM DoD EA SRM DoD EA BRM DoD EA DRM DoD EA PRM
Global Information Grid
GIG Arch-itecture Business
MAWarfighter
MAIntelMA
Enterprise Information Environment(EA) MA
FEARMs
Exhibit300s
(TRM, SRM, BRM, DRM, PRM)
MA – Mission Area
OMB
DoD
DoD EA TRM DoD EA SRM DoD EA BRM DoD EA DRM DoD EA PRM
Global Information Grid
GIG Arch-itecture Business
MAWarfighter
MAIntelMA
Enterprise Information Environment(EA) MA
FEARMs
Exhibit300s
(TRM, SRM, BRM, DRM, PRM)
MA – Mission Area
DRAFT
10
DoD Performance Report & Plan
Leveraging DoD EA RMs
tools
WMA BMA IMA EIEMA
DoD EA RMs WorkingDocuments
BRM
SRM
TRM
DRM
PRM
DoD Data Management Strategy
DoD Information Standards Repository
DoD Net-Centric Enterprise Services
DoD GIG Architecture & NCOW RM
Intel Community Functions and Service Components
DoD Business Enterprise Architecture
Universal Joint Task Lists, Common Operational Activities Library
CADM, DoDAF, DARS
External DoD
DoD EA RM FEA RM
DoD CPIC Process
OMB CPIC Process
•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
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
Internal DoD
DoD Performance Report & Plan
Leveraging DoD EA RMs
tools
WMA BMA IMA EIEMA
DoD EA RMs WorkingDocuments
BRM
SRM
TRM
DRM
PRM
DoD Data Management Strategy
DoD Information Standards Repository
DoD Net-Centric Enterprise Services
DoD GIG Architecture & NCOW RM
Intel Community Functions and Service Components
DoD Business Enterprise Architecture
Universal Joint Task Lists, Common Operational Activities Library
CADM, DoDAF, DARS
External DoD
DoD EA RM FEA RM
DoD CPIC Process
OMB CPIC Process
•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
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
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
Internal DoD
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.
• Functional (operational) requirements• Processes and relationships• Information needs (content, form,
protection)• User functions• Performance bounds
•• Functional (operational) requirementsFunctional (operational) requirements•• Processes and relationshipsProcesses and relationships•• Information needs (content, form, Information needs (content, form,
protection)protection)•• User functionsUser functions•• Performance boundsPerformance bounds
• System functional descriptions• System interfaces and connections• Operations-to system traceability
•• System functional descriptionsSystem functional descriptions•• System interfaces and connectionsSystem interfaces and connections•• OperationsOperations--to system traceabilityto system traceability
COTSProducts• ANSI X12 ICs
• EDIFACT• HL7• XML• HTML• Proprietary (rare)
Standards
Technical ViewTechnical View
Systems ViewSystems View
CongressWarfighters
Large & SmallBusinesses
• Technical Architecture Profile• Standards and Technology
Forecast
•• Technical Architecture ProfileTechnical Architecture Profile•• Standards and Technology Standards and Technology
ForecastForecast
DOD
Services &Agencies
VPN
SmartCardFirewall
Perimeter SecurityMechanisms
DataRepositories
InfrastructureServices
Applications
EAI/ETL
JTA ITStandards
DIICOE
APIs
Operational ViewOperational View
GCSS-AF
• Functional (operational) requirements• Processes and relationships• Information needs (content, form,
protection)• User functions• Performance bounds
•• Functional (operational) requirementsFunctional (operational) requirements•• Processes and relationshipsProcesses and relationships•• Information needs (content, form, Information needs (content, form,
protection)protection)•• User functionsUser functions•• Performance boundsPerformance bounds
• System functional descriptions• System interfaces and connections• Operations-to system traceability
•• System functional descriptionsSystem functional descriptions•• System interfaces and connectionsSystem interfaces and connections•• OperationsOperations--to system traceabilityto system traceability
COTSProducts• ANSI X12 ICs
• EDIFACT• HL7• XML• HTML• Proprietary (rare)
Standards
Technical ViewTechnical View
Systems ViewSystems View
CongressWarfighters
Large & SmallBusinesses
• Technical Architecture Profile• Standards and Technology
Forecast
•• Technical Architecture ProfileTechnical Architecture Profile•• Standards and Technology Standards and Technology
ForecastForecast
DODDOD
Services &Agencies
VPNVPN
SmartCard
SmartCardFirewall
Perimeter SecurityMechanisms
DataRepositories
InfrastructureServices
Applications
EAI/ETLEAI/ETL
JTA ITStandards
DIICOE
APIs
Operational ViewOperational View
GCSS-AF
Exhibit 300IT Program
Reports
DODAF Design Work
DRAFT
11DRAFT
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
Defines
Presentation (JSP)
Business Logic (EJB)
Data Interchange (XML)
Data Management (JDBC, XBRL)
Security (LDAP, Authentication, Auditing)
Defines The Architecture
ServicePlatforms
(J2EE)
Web B
rowser
Intranet / Extranet
Records M
gmt
X. 500, TC
P/IP
Protocol Firewall (H
TTP)
Access C
ontrol List
XM
L, SOAP
FinancialMgmt System
BalancedScorecard
ReportingEngine
Portal
• 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
Performance Reference Model (PRM)
Initiative Business and Performance Drivers
Defines
Presentation (JSP)
Business Logic (EJB)
Data Interchange (XML)
Data Management (JDBC, XBRL)
Security (LDAP, Authentication, Auditing)
Defines The Architecture
ServicePlatforms
(J2EE)
Web
Bro
wse
r
Intr
anet
/ E
xtra
net
Rec
ords
Mgm
t
X. 50
0, T
CP/
IP
Prot
ocol
Firew
all (
HTTP
)
Acc
ess
Con
trol
Lis
t
XM
L, S
OAP
FinancialMgmt System
BalancedScorecard
ReportingEngine
Portal
• 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
Performance Reference Model (PRM)
Initiative Business and Performance Drivers
Defines
Presentation (JSP)
Business Logic (EJB)
Data Interchange (XML)
Data Management (JDBC, XBRL)
Security (LDAP, Authentication, Auditing)
Defines The Architecture
ServicePlatforms
(J2EE)
Web B
rowser
Intranet / Extranet
Records M
gmt
X. 500, TC
P/IP
Protocol Firewall (H
TTP)
Access C
ontrol List
XM
L, SOAP
FinancialMgmt System
BalancedScorecard
ReportingEngine
Portal
• 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
Performance Reference Model (PRM)
Initiative Business and Performance Drivers
Defines
Presentation (JSP)
Business Logic (EJB)
Data Interchange (XML)
Data Management (JDBC, XBRL)
Security (LDAP, Authentication, Auditing)
Defines The Architecture
ServicePlatforms
(J2EE)
Web
Bro
wse
r
Intr
anet
/ E
xtra
net
Rec
ords
Mgm
t
X. 50
0, T
CP/
IP
Prot
ocol
Firew
all (
HTTP
)
Acc
ess
Con
trol
Lis
t
XM
L, S
OAP
FinancialMgmt System
BalancedScorecard
ReportingEngine
Portal
• 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
12
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