Architecture. Governance

Transcription

1 Capabilities Integration Enterprise Forum Architecture Standards d and Governance UTILIZING DATA STEWARDSHIP TO MANAGE ARCHITECTURE DATA FOUO TRADOC: Victory Starts Here!

2 Army s Net centric Goals Army Directive , Army Management is a strategic asset and must be managed as such. My goal is to create and support a netenabled environment that gives decision makers access to authoritative i data in a timely and secure manner. Creates the Chief Officer Creates the Steward John M. McHugh, Secretary of the Army Architecture is Managed as 2

3 Army Governance CDO, Stewards Governance Structure (ADB/ADC) Chief Officer (CDO) Responsible for developing and implementing the Army Management Program. Stewards Responsible for developing, implementing, and enforcing data standards, processes, and procedures of their area. Army Board (ADB) Senior Army decision body for establishing Army positions on data strategy, standards, and execution. Chaired by the CDO. Army Council (ADC) Initial adjudication body on matters related to data. Works under the direction of the Army Board. 3

4 Army Management Structure Army Board -Attended d by the Steward -Chaired by the Chief Officer -Senior adjudication body for data -Develops Army positions on data -Coordinate data sharing efforts Army Council -Attended by the FDM s -Works under Army Board -Indentifies issues for resolution -Initial entry point for issues to the ADB -Unresolved issue go to Army Board 4

5 Source A Source B Master ERP Transformation Approach Accountable Authoritative Standardize Expose Register Assess CDO, Stewards Governance Structure (ADB/ADC) Master Management Authoritative Sources Source A ADS Registry Source B Source C Quality Management Standardization, Common Semantics Improve Quality Define Quality Analyze Quality Measure Quality Capture HUMAN INPUT SENSORS Provider Sources Services Warehouses Security Messaging ETL Tools Warehousing Warehouses Marts ODS & Meta Analysis BI Study Tools Area User Access Information Products Validate Register DoD Metadata Registry Army Schema Repository Army-USMC ADS Registry Management Practice Assessments Metrics Mapping Ex: Condition Based Maintenance Registry & Discovery Security Management & Quality Practices Army Governance Situation Awareness Army Enterprise Infrastructure Support Services Repository. Other Services Army Approach to Achieving Net Centric Future State

6 Architecture Management Structure Externally Federated Federated ADS Partners USAFMSA (FMS/GFM): Organizations, personnel, equipment LOGSA Logistics Integrated base: LINs, Costing per LIN, Form, Fit, Power data G 6 Army Portfolio Mgt. System (APMS): Systems and PoR with associated Joint Common System Functions ARCIC Capability Needs Analysis (CNA) Dtb base: Army Required dcapabilities (RC), RC gaps, RC DOTMLPF Solutions ASD NII Joint Net Centric Operational Capability Portfolio Mgt. (CPM): DoD PoR TRAC: Scenario and force modeling data Battle Lab Gordon: Network performance data JFCOM (JACAE): Integrated t djfhq architectures t Navy (SADIE): Similar to CADIE in construct USMC (MCCAE): Copy of JACAE for USMC OSD NII (DARS): Metadata registry; some Army JCIDS architectures in unstructured (native tool or spread sheet/pdf) formats JCA Management System (JCAMS): ADS for JCA taxonomy, lexicon, and business rules More yet to be identified Discovery Search Discovery Return Authoritative Reports / Visualizations Army Processes: Force Management Capabilities Dev. Acquisition Experimentation Capability based Architecture Development & Integration Environment DS: Vandiver AIMD Spt. Staff Army Arch. Metadata Registry Integrated Arch. DW Transactional bases ABCAS CBMe Internally Federated w/in COI GFEA Source PEO/PM Systems Source Intelligence Source CDID OA Sources Tech Standards Source AEA Dt Source FDM: DUSA FDM: ASA(ALT) (SOSSE) FDM: HQDA G2 FDM: TRADOC ARCIC (AIMD) Leads FDMs: HQDA G6 ADS = Authoritative Source DS = Steward FDM = Functional Manager DW = Warehouse = Structured Metadata = Structured = Stakeholder Interaction

7 Architecture Management Structure Architecture Management Board (ADMB) Composed of Steward and Functional Managers Addresses architecture issues for discussion at the ADB Determines guidance, standards for architecture data management Meets on call Configuration Change Board Manages the change needed in the CADIE Warehouse Composed of AIMD staff and FDM or designated individual Identifies actions, priorities for change, and resources implications Uses the ADMB for unresolved issues Meets on call 7

8 Steward Program Major Objectives Provide Architecture Governance and Standards Identify Authoritative Sources Transform Army Architecture (static to dynamic) Expose Architecture Validate and Register all metadata into a Metadata Registry Define Key Performance Parameters to assess data maturity and measure success Aligns with the Army s Dt Transformation Plan and helps implement the Army s Net Centric Vision

9 Architecture t Standards Implementation

10 Standards Overview 11 Members comprised of AIMD, TRADOC, ASA (ALT), and HQDA CIO G6 with HQDA G3/5/7 oversight Living document v1.7 consists of the minimum essential data standards for organizational-based architectures Completed staffing through the Executive Architect Functional Managers and approved by Mr. Vandiver as the Steward Comprises both Project and viewpoint metadata; five Operational Viewpoints (OV-2, OV-3, OV-4, OV-6c); three System Viewpoints (SV-2, SV-6, SV-10c); and two Technical Viewpoints (TV-1 and TV-2) focused versus Process focused in order to achieve data integration Version 1.8 captures new DoDAF v2.0 viewpoints such as Capability Views and expanded data elements as required for JCIDS V1.8 is in final staffing through the Functional Managers for approval by the Architecture Steward Used to expand data warehouse schema into a fully integrated architecture data repository Incorporates other ADSs such as LIW, FMSWeb, and eventually M&S in order to enhance architecture data to support Brigade network design and COA analysis 10

11 Anatomy of a Method (DoDAF and UPDM) DoDAF 2.0 Viewpointsi UPDM2.0 and Standards 11

12 Architecture Modeling Paradigms Syntax under the hood 12

13 Development Methodology The C.A.R.P. method supports major objectives of architecture federation, the core AV-2 content for all DoDAF architecture should be focused on a central common foundation of concepts relevant to the domain of any DoDAFDAF architecture. t The starting points correspond to central key elements of the DM2: Capability ( the why ): The ability to achieve a desired effect under specified [performance] standards and conditions through combinations of ways and means [activities and resources] to perform a set of activities. Capabilities describe the desired functionality of architecture. Activity ( the how ): Work, consisting of atomic or composite steps that transform resources to achieve an objective/provide a capability. Activities describe the processes and procedures carried out to actively change an EffectObject, i.e. a target resource. Resource ( the what ):, Information, Performers, Materiel, or Personnel Types that are produced or consumed. Performer ( the who ): Any entity human, automated, or any aggregation of human and/or automated that performs an activity and provides a capability * Business Transformation Agency (17 Dec 2009). Vocabulary-Driven Enterprise Architecture Development Guidelines for DoDAF AV-2: Design and Development of the Integrated Dictionary. Found on on 08 Dec

14 Using C.A.R.P. To define DoDAF 2.0 projects AV-1 (Metadata) CV-1 CV-2 CV-3 CV-5 14 CV-6 OV-5a DIV-2 OV-5b OV-2 OV-6c OV-3 OV-6a OV-4 OV-6c Svc-1 (SV-1) Svc-2 (SV-2) Svc-4 (SV-4) Svc-5 (SV-5a) Svc-6 (SV-6)

15 EVOLUTION OF INTEGRATED DATA STANDARDS AV 1 Metadata (ArCADIE Architecture Catalog) Force Structure Authoritative Reference LIN Authoritative Reference Network BOIP Authoritative Reference Technical Standards Reference Technical Standards Reference v Organization/JCIDS V1.8 DoDAF 2.0/JCIDS Other Army Processes OV 2 OV 3 CV 1 CV 2 CV 3 OV 4 SV 2 OV 6c SV 6 CV 4 CV 5 CV 6 SV 1 SV 5a DIV 2 between data currently captured and what data is required for M&S tools SV 10c Svc 6