1. I n t e g r i t y - S e r v i c e - E x c e l l e n c e As of: 3/1/2016 Air Force Weather Agency CEISC Committee Focus Shift - Proposed Modification to TOR 2 December 2003 Mr. Mike Howland, AFWA

2. I n t e g r i t y - S e r v i c e - E x c e l l e n c e As of: 3/1/2016 Backup Slides

3. I n t e g r i t y - S e r v i c e - E x c e l l e n c e As of: 3/1/2016 What is an Architecture? “The structure of components, their interrelations, and the principles and guidelines governing their design and evolution over time.” (IEEE STD 610.12 as stated in the C4ISR Architecture Framework, Version 2.0)   (Greek)  Master Builder

4. I n t e g r i t y - S e r v i c e - E x c e l l e n c e As of: 3/1/2016 An Architecture has Multiple Views A view represents the whole system with focus on a set of critical constraints (i.e., from that viewpoint) Supports key stakeholders / roles Reduces perceived complexity through separation of constraints Designer (System)Builder (Technical) Family Usage (Operational) Building Code In a good architecture each view is Complete relative to that viewpoint Consistent with respect to other views

5. I n t e g r i t y - S e r v i c e - E x c e l l e n c e As of: 3/1/2016 So Why Do We Need Architecture? Architecture enables stakeholders with different views and perspectives to deal with complexity: Communicate - define and view the system from their interests Collaborate on system decisions Coordinate implementation Manage change

6. I n t e g r i t y - S e r v i c e - E x c e l l e n c e As of: 3/1/2016 Managing Change - Choices Don’t Change Trial & Error Scrap and Replace Use Architecture Drawings / Blueprints Manage Change and Risk

7. Architecture Example Data (What) Function (How) Location (Were) Org (Who) Time (When) Strategy (Why) Activities CONOPS Information Elements Ops Nodes Roles Rules Operational Views System Functions Design Strategy Data System Nodes Systems Performance System Views Technical Standards Technical Views Technical Strategy April 2003 I n t e g r i t y - S e r v i c e - E x c e l l e n c e

8. As of: 3/1/2016 Why are Architectures Necessary? Legislative Direction Requires Them Clinger-Cohen Act (CCA) of 1996 Directed that all Federal Agencies establish a comprehensive approach to manage the acquisition, use, and disposal of information technology (IT), in part to avoid past problems arising from uncontrolled and inconsistent practicesDirected that all Federal Agencies establish a comprehensive approach to manage the acquisition, use, and disposal of information technology (IT), in part to avoid past problems arising from uncontrolled and inconsistent practices Requires development and maintenance of sound (methodical) and integrated architecturesRequires development and maintenance of sound (methodical) and integrated architectures Office of Management and Budget (OMB) Circular A-130 Requires Government Agencies to develop and use Enterprise ArchitecturesRequires Government Agencies to develop and use Enterprise Architectures OMB using architectures as “grading” criteria for IT budget submissionsOMB using architectures as “grading” criteria for IT budget submissions

9. I n t e g r i t y - S e r v i c e - E x c e l l e n c e As of: 3/1/2016 Why are Architectures Necessary? DoD Direction Requires Them CJCS 3170.01C Joint Capabilities Integration and Development System (JCIDS) Joint concepts and integrated architectures provide the construct for analysis and the construct for prioritizing competing demands to improve joint warfighting capabilitiesJoint concepts and integrated architectures provide the construct for analysis and the construct for prioritizing competing demands to improve joint warfighting capabilities Initial Capabilities Documents (ICDs), Capability Development Documents (CDDs) and Capability Production Documents (CPDs) should be presented in the context of integrated architecturesInitial Capabilities Documents (ICDs), Capability Development Documents (CDDs) and Capability Production Documents (CPDs) should be presented in the context of integrated architectures New DoD 5000 Interim Guidance The requirements generation and acquisition management systems use shall integrated architectures to define desired capabilities and to guide the development of systemsThe requirements generation and acquisition management systems use shall integrated architectures to define desired capabilities and to guide the development of systems Programs that enter the acquisition process at Milestone B shall have a system architecture and an operational architecture for their relevant mission area.Programs that enter the acquisition process at Milestone B shall have a system architecture and an operational architecture for their relevant mission area.

10. I n t e g r i t y - S e r v i c e - E x c e l l e n c e As of: 3/1/2016 DoD Architectures - Why? Network Centric Warfare Platform Centric Warfare Change Complexity

11. I n t e g r i t y - S e r v i c e - E x c e l l e n c e As of: 3/1/2016 an ENTERPRISE (what is it?) an organization supporting a defined business scope and mission and comprised of interdependent resources (people, organizations, and technology) who must coordinate their functions and share information in support of a common mission (or set of related missions). [Federal CIO Council]

12. DoD Enterprise ENTERPRISE(s) (where are the boundaries?) COI: Community of Interest Service Enterprise Service Enterprise Service Enterprise Info Assurance Services Info Mgmt Services Info Transport Services GLOBAL INFO GRID ENTERPRISE SERVICES (GES) Coalition Enterprise Guard COI C2 Node IT Platform Mission Apps Allied Enterprise (e.g., NATO) Other US Enterprises (e.g., HLS) C2 Node IT Platform Mission Apps C2 Node IT Platform Mission Apps 2-6

13. I n t e g r i t y - S e r v i c e - E x c e l l e n c e As of: 3/1/2016 One DoD Architecture – Three Views Technical View Technical View Operational View Operational View The Operational View describes and interrelates the operational elements, tasks and activities, and information flows required to accomplish mission operations. The Systems View describes and interrelates the existing or postulated technologies, systems, and other resources intended to support the operational requirements. The Technical View describes the profile of rules, standards, and conventions governing systems implementation. Systems View Systems View

14. I n t e g r i t y - S e r v i c e - E x c e l l e n c e As of: 3/1/2016 DoD Architecture Framework Fulfills OMB Framework Requirements http://www.whitehouse.gov/omb/circulars/a130/a130trans4.html#1