1. Bill Piazza Architecture Federation Branch Chief JS J6 DD C2I
WMA Architecture Federation and Integration Project WG Meeting 23 May 2013 (Draft)
Bill Piazza
Architecture Federation Branch Chief
JS J6 DD C2I

2. Agenda Phase 4/Sprint 11 Wrap-up and Demo
JIE/JTSO architecture support updates
Portal improvements
WMA Architecture Governance Update
Initial WMA Architecture Data Standards (Army/ArCADIE Issues/Comments)
Phase 4/Sprint 12 outline
Partner Updates

3. Phase 4 Key Focus Areas JIE/JTSO Support
Automated structured data handling
Data-Enabled Standardized Views
WMA Architecture Federation Formal Guidance
Currently an ad-hoc WG w/o formal charter
No formal governance to use what is being developed
Partner Support
Intelligence and Business Mission Area outreach
Requirements for key federation touch points

4. Automated Structured Data Handling
Objective: Streamline and automate the accessibility and reusability of structured WMA (and JIE) architecture data sets using web services (when feasible)
From*:
WMA internal databases (JAR, JMTs)
External Web Services (ArCADIE, AFEAR, NEAR, MARS)
External COTS exports (JIE/JTSO SA XML, MagicDraw XMI)
Excel Templates (i.e. USNORTHCOM)
Establish Requirements for sharing to: JS J6 Capability Analysis tools, T&E, M&S, DTIC, GTG-F (E-ISP)
*FEDERATION to these authoritative sources, not managing a “master data repository”

5. Data-Enabled Standardized Views
Objective: Display structured architecture data, regardless of source, in a standardized template to support analysis processes (including validation and verification) and reuse
For Phase 4 the focus will be on:
Taxonomies CV-2 and AV-2
Capability Views
CV-4, CV-6
Operational Views
OV-2, OV-3, OV-4, OV-5a, OV-6a
System Views
SV-1, SV-2, SV-4, SV-5, SV-6
Service Views
SvcV-1, SvcV-2, SvcV-4, SvcV-5, SvcV-6
Standards View (StdV-1)
Hybrid views to support NR-KPP analysis process
Bold/Underline indicates work started in Phase 3

6. WMA Architecture Federation Formal Guidance
Need formal guidance to ensure continued partner and stakeholder engagement. Guidance for WMA architectures will be formalized under upcoming JS Charters/CJCSI to support JS J6 processes.
Objectives: Establish formal guidance for following areas:
WMA Architecture Discovery and Accessibility (coordinated with DoD CIO processes)
Structured data formats for delivery of WMA architectures to support JCIDS, Operational and Capability Analysis Processes (Needs to be lock step with DoD CIO, partner, and JMT efforts)
Processes for delivery of structured architecture data sets, including Configuration Management/Lifecycle maintenance of WMA architectures

7. Intelligence and Business Mission Area Outreach
WMA processes now mature enough to start engagement with other mission areas
Objectives:
Establish requirements for horizontal architecture federation to Business and Intelligence Mission Area
Focus on support to DoD CIO goal of building the the DoD EA as a federation.

8. Requirements for Key Federation Touch Points
Now that WMA architecture data (and JIE related data) is becoming available, there is ramping up demand
Objectives:
Identify requirements for sharing WMA (and JIE) architecture data and architecture-based analysis with other critical DoD processes
S&T (DTIC)
T&E (foundational work done by Visense)
M&S (J7)
GTG-F

9. Partner Support Objectives:
Expand Stakeholder and partner engagement to support WMA and DoD CIO architecture federation goals and objectives (including other JS J2/J3/J7/J8 architecture efforts)
Continue to work partner repository discovery and accessibility using enterprise services
Make available for reuse all WMA already established processes and technical solutions* to mature partner repositories and save valuable resources
Develop capability to subscribe to portal/project updates
*Non-COTS/proprietary

10. Sprint 11 Deliverables: April 29 – May 17
Standardized Data-Enabled Views on Portal:
Along with required data sets from JAR, Sparx EA, DM2 XML, MagicDraw XMI, System Architect XML, Army XML, Excel Template
Continue to work data section of implementation guide (to support Bullet 1)
Improve capability to search by view type
Update/Improve WMA Dictionary functionality and search
Looking at Ontology/Lexicon tools
Capability to subscribe to notifications about updates
Create enterprise collection for JCPAT legacy and DARS SIPR Legacy Catalogs
Outreach J7/J3/J8, GTG-F, AF, INTEL/Business MA
Role Management

11. Sprint-11 Data Enabled Views
Created data templates most DoDAF views:
Working pages on how data should be represented in a standardized fashion
Working federation methodology to show relationships between data from multiple sources
Wiki page lays out templates
Comments and Discussion
AV1
OV3
SvcV3b
SV2
AV2
OV4
SvcV4
SV3
CV1
OV5a
SvcV5
SV4
CV2
OV5b
SvcV6
SV5a
CV3
OV6a
SvcV7
SV5b
CV4
OV6b
SvcV8
SV6
CV5
OV6c
SvcV9
SV7
CV6
PV1
SvcV10a
SV8
CV7
PV2
SvcV10b
SV9
DIV1
PV3
SvcV10c
SV10a
DIV2
SvcV1
StdV1
SV10b
DIV3
SvcV2
StdV2
SV10c
OV2
SvcV3a
SV1
Ready
for Review
In Work
No Sample
Data Sets

12. General comment on Architecture Data (1)
List number and parent list number are explicit parent - child relationship. We always map from child up to parent, to simplify data tables (i.e. you would require a separate table to maintain all the child relationships for each parent vice just including a parent id on the child entry)
We map all our objects to their authoritative sources through our definitions table (foundation is in the AV-2). Do not need to map multiple times if mapped in the AV-2 to the AS
Fully understand some vendors may not support some properties (i.e. most do not have the capability to meta-data tag with classification markings). This is a shortfall that will require architects to do additional work in some cases.

13. General comment on Architecture Data (2)
For things like "sort order" those are to ensure that the objects are listed in an order identified by the user. For example if activities are numbered 1.1, 1.2, 1.3, etc., without the sort order, 1.1 , 1.10, and would be first in the list. It is a data property we can usually extract if not provided.
As part of our WMA EA concept it is planned to ensure that all activities are mapped at the top level to Services Tasks or UJTs, Capabilities to JCA's just like functions are required to be mapped to JCSFL in 6212.
Relationship types (i.e. OV-4) are required to define the line as an object type. Almost all OV-4/OV-2 etc... type views have definitions or types for the connectors and we needed a way to represent that connection type (i.e. command relationship, operational control, admin control)
SV-4s do not normally include performers since the SV-4 is a hierarchy of functions for the entire capability (Product Name)

14. Army Comments Architecture Data standards: issues and lessons learned

15. Sprint 12: May 27 – June 21
WMA Architecture Data Standards out for review
Architecture data sets populated for DoD CIO RA’s, JTSO, WMA (JS J6) developed architectures
WMA Enterprise Architecture Foundation (JCAs, UJTs, JCSFL)
Legacy DISR TV-1 traceability
DoD CIO Governance Support
WMA Governance
NR-KPP Module (Legacy CDTM) Assessment
Search Capability
Dictionary improvements
Partner Support

16. Sprint Schedule Phase 5: 8 July – Sep 27 Sprint 12: May 28 – June 21
Cleanup Jun
Federation WG Meeting 27 Jun
Phase 5: 8 July – Sep 27

17. Status Updates DoD JS CCMDs Services CIO AT&L J6 J2 J3 J7 J8/JIAMDO
Governance
DM2 WG
DISA
AT&L
Interoperability IPT JS J6
NR/KPP, JCIDS
JMT
JC2 J2 J3 J7
J8/JIAMDO
CCMDs
SOCOM
NORTHCOM
EUCOM
CENTCOM
PACOM
STRATCOM
CYBERCOM
AFRICOM
SOUTHCOM
Services
Army G6
SMDC
AIMD
Navy
DASN RDT&E
CIO
CYBERCOM AF
SAF/A6
USMC HQ
MCSC
MCCDC
11/11/2018

18. Links WMA-AFIP NIPR Production Portal
WMA-AFIP SIPR Portal (Development)
Community Forge
Used for group collaboration
Software Forge
Used for technical development