1. © 2006 The MITRE Corporation. All rights reserved Use of the FEA Reference Models for the Continuity Communications Architecture Charlie Martinez, D440 Sheila Cane, W906 7 September 2006 Approved for Public Release Distribution Unlimited Case Number: 06-1012

2. © 2006 The MITRE Corporation. All rights reserved 2 Overview n Project Background n CCA Metamodel n CCA Analytical Objectives n Toolset Design Objectives n Relationship to FEA Reference Models n Use of Reference Models in Toolset n Lessons Learned from Use of Reference Models

3. © 2006 The MITRE Corporation. All rights reserved 3 Continuity Communications Architecture (CCA) Project Background n Overall Objective –Ensure communications among Federal Executive Branch Departments and Agencies (D/As) to support the National Essential Functions (NEFs) under all types of national emergency situations n Three-Phased Approach –Document the As-Is CCA –Assess the As-Is CCA for gaps in capabilities –Propose a To-Be CCA to close the gaps n As-Is CCA Technical Approach –Develop a Metamodel for the CCA –Implement the Metamodel in a CCA Toolset n Use FEA Reference Models to the maximum extent possible –Use the CCA Toolset to document the As-Is CCA n Use “pick lists” to ensure data consistency and integrity –Use relational database to analyze gaps in capabilities

4. © 2006 The MITRE Corporation. All rights reserved 4 CCA Metamodel Three Major Components n Environment/Situation –The Scenarios under which the D/As must operate n Operations/Business –What the D/As must do in any given Scenario n Infrastructure –The facilities, communications systems, hardware/software, and other capabilities the D/As use to accomplish their priority missions Infrastructure Operations/ Business Environment/ Situation

5. © 2006 The MITRE Corporation. All rights reserved 5 Communications Computing/Storage Platforms Information Content D/As Applications Reside on Process Store Operations/Business PMEFs NEFs Support Use Perform Require/ Produce Require/ Produce * Fixed and/or Mobile Geographic Locations Reside at Information Representations Connect Described by Exchanges Scenarios Drive Define Effects Affect Other Orgs Operational Services Enable Infrastructure Other Functions Implement Perform Reside at Environment/Situation Security Restricts Protects Facilities* Are Identified With CCA Metamodel Relationships

6. © 2006 The MITRE Corporation. All rights reserved 6 CCA Analytical Objectives Operational/ Business (As-Is) Infrastructure (To-Be) Infrastructure (As-Is) Operational/ Business (To-Be) NEFs Questions that need to be answered Have the D/As identified the right set of priority functions and partner organizations to support the NEFs? Do the D/As have the existing infrastructure to support performance of their own priority functions? Do the D/As have the existing infrastructure to communicate amongst each other in support of their priority functions? Will proposed changes to priority functions and infrastructure (the To- Be) adequately address gaps in continuity communications and the ability to support the NEFs? Proposed changes to meet operational gaps Proposed changes to meet infrastructure gaps

7. © 2006 The MITRE Corporation. All rights reserved 7 Communications Information Content D/As Applications PMEFs NEFs Information Representations Scenarios Effects Security Communications Security Information Content D/As Applications PMEFs NEFs Information Representations Geographic Locations Environment/Situation Ops/Business Infrastructure Ops/Business Infrastructure Information Consumer Information Producer Framework for CCA Analysis Assessments of Connectivity, Interoperability, & Compatibility

8. © 2006 The MITRE Corporation. All rights reserved 8 Toolset Design Objectives n Ability to capture all relevant CCA information –Detailed descriptions of metamodel components –Explicit relationships among the metamodel components n Ability to support analytical objectives –Query and analysis capability –Consistency in contents n Ability to facilitate data collection –Maximum use of standardized terminology –Built-in error checking n Traceability to FEA Reference Models –Performance –Business –Data –Service Component –Technical

9. © 2006 The MITRE Corporation. All rights reserved 9 Communications Computing/Storage Platforms Information Content D/As Applications Reside on Process Store Operations/Business PMEFs NEFs Support Use Perform Require/ Produce Require/ Produce * Fixed and/or Mobile Geographic Locations Reside at Information Representations Connect Described by Exchanges Scenarios Drive Define Effects Affect Other Orgs Operational Services Enable Infrastructure Other Functions Implement Perform Reside at Environment/Situation Security Restricts Protects Facilities* Are Identified With Relationship to FEA Reference Models SRM BRM Derived From Traceable to DRM TRM Inspired by Derived From PRM

10. © 2006 The MITRE Corporation. All rights reserved 10 Uses of FEA Reference Models in CCA n Performance Reference Model (PRM) –Operational performance (NEFs and PMEFs) n Identify enterprise-level performance measures n E.g., timeliness of essential function startup during emergency –Programmatic performance (CCA) n Program Mgmt Plan specifies performance of the architecture toolset n Does the toolset function as intended? E.g., does it find gaps in capabilities? D/As PMEFs NEFs Support Perform Require/ Produce Enable PRM

11. © 2006 The MITRE Corporation. All rights reserved 11 Uses of FEA Reference Models in CCA n Business Reference Model (BRM) –Applies to PMEFs and functions performed by other organizations in support of PMEFs –Supports coverage of Federal Executive Branch (FEB) Business Areas n Analysis compares PMEFS with Business Areas (BA) and Lines of Business (LOB) to ensure coverage of FEB responsibilities n Simple example: All FEB Departments and Agencies (D/As) should have disaster management (BA) including disaster repair and restore (LOB) for their services to citizens D/As PMEFs Perform Require/ Produce Drive Other Orgs Other Functions Perform Reside at BRM Traceable to

12. © 2006 The MITRE Corporation. All rights reserved 12 Uses of FEA Reference Models in CCA n DRM –Used for Information Content & Information Representations –As recommended in the FEA, begins with the first two levels of the BRM and adds a 3 rd layer to describe broad types of information exchange within a line of business n Report of facts or statistics, guidance, direction, request for information, request for authority, financial transaction –Links information content with information representation n Shows which information standards meet operational information content needs Information Content Information Representations Described by Exchanges DRM Derived From

13. © 2006 The MITRE Corporation. All rights reserved 13 Uses of FEA Reference Models in CCA n SRM –Used directly as a pick list to identify operational services n Some extensions necessary –Used as reference for applications –Used to link business service needs with applications n Shows how applications meet operational needs Applications Operational Services Implement SRM Derived From

14. © 2006 The MITRE Corporation. All rights reserved 14 Uses of FEA Reference Models in CCA n TRM –Used as a reference model to develop pick lists for all infrastructure components –Via links to applications and information representation, shows how technology infrastructure meets operational needs Communications Computing/Storage Platforms Applications Reside on Process Store * Fixed and/or Mobile Reside at Information Representations Connect Exchanges Affect Infrastructure Security Restricts Protects TRM Inspired by

15. © 2006 The MITRE Corporation. All rights reserved 15 Lessons Learned from Using FEA Reference Models n FEA reference models are just that: reference models –Do not have to be used exactly as specified –They keep us from re-inventing the wheel –They help us standardize on terminology –They remind us about important aspects of a problem we may not have considered n Hierarchies in the reference models are good, but there are places where they are difficult to use –Not an easy job in the first place

16. © 2006 The MITRE Corporation. All rights reserved 16 n Performance Reference Model (PRM) –The PRM is made for problems like COOP/COG n Responsiveness and timeliness to implement services in a crisis –PRM gives categories but does not provide example metrics n Requires creativity (re-invention) on the part of the PRM user –Programmatic performance is more difficult to define at the enterprise level n Measuring system response time is useful as long as the “right” system is responsive n Financial metrics such as ROI are difficult to calculate n How do we know we have performed? ­Gaps found and resolved does not lend itself to measurement as a percentage to be tracked over time. We can however, measure this as yes or no, or as integer quantities that we would like to see increase. Lessons Learned from Using FEA Reference Models

17. © 2006 The MITRE Corporation. All rights reserved 17 n BRM –Useful for categorizing information needs and identifying relevant activities n DRM –DRM recommendation to use top 2 levels of BRM and then add detail was helpful n Provided data context n We generalized the information content across contexts –CCA is not attempting detailed data modeling across the FEB n Too complex, too much coordination required for results time- horizon n CCA models information representation standards rather than data standards Lessons Learned from Using FEA Reference Models

18. © 2006 The MITRE Corporation. All rights reserved 18 n SRM –Includes good coverage of operational services –Confusion between FEA SRM, Service Oriented Architectures (SOA), and how they relate n Includes some operational services which are hard to distinguish from application services n Can be difficult to decide which to use where n TRM –Provides ideas for technologies and standards that should be considered –Does not try to lock you into a particular set of technologies –Technology lists provides examples only, not enough detail within categories Lessons Learned from Using FEA Reference Models

19. © 2006 The MITRE Corporation. All rights reserved Backups

20. © 2006 The MITRE Corporation. All rights reserved 20 National Essential Functions (NEFs) n Preserve our Constitutional form of government n Provide visible leadership to the Nation and the world n Defend against all enemies, foreign or domestic n Maintain and foster foreign relations n Protect against threats to the homeland n Provide rapid response to emergency situations n Protect and stabilize the nation's economy n Provide critical Federal government services