DoDAF 2.0 Exemplars UPDM 1.0 X DoDAF 2.0 X DM2 PES XML Examples 12 August 2010 DoDAF Development Team 1 1

Briefing Outline Why exemplars Method Briefing structure The 28 views X 3 Lessons learned and next steps The OMG UPDM Team developed examples of the views as part of UPDM 1.0. It is called “Sample Problem” and is Annex C in the UPDM 1.0 Spec. The UPDM Team is working on a refinement of the Sample Problem for UPDM 2.0. The DoDAF 2 development team went through the examples and interpreted in DoDAF 2 / DM2 terms. DM2 PES XML documents corresponding to each marked-up diagram are being posted on the DM2 collaboration site (www.silverbulletinc.com/dm2) Briefing format A UPDM diagram will be shown first, in it’s native form from UPDM 1.0 Annex C. Blue background. Then DM2 annotated version of the same diagram will be shown. White background. The UPDM Team has been reviewing the material as it develops.

Why exemplars DoD EA Community wanted examples of DoDAF 2 diagrams and associated DM2 PES XML Looked at many sources for material to use Simple Many views, including new DoDAF 2 ones Publicly releasable OMG UPDM 1.0 Team “Sample Problem” has 28 views, including some corresponding to new DoDAF 2 models Civilian Search and Rescue (SAR) scenario Annex C in the UPDM 1.0 Spec. on the public OMG site The DoDAF 2 development team went through the examples and interpreted in DoDAF 2 / DM2 terms. Briefing format A UPDM diagram will be shown first, in it’s native form from UPDM 1.0 Annex C. Blue background. Then DM2 annotated version of the same diagram will be shown. White background. The OMG UPDM Team developed examples of the views as part of UPDM 1.0. It is called “Sample Problem” and is Annex C in the UPDM 1.0 Spec. The UPDM Team is working on a refinement of the Sample Problem for UPDM 2.0. The DoDAF 2 development team went through the examples and interpreted in DoDAF 2 / DM2 terms. DM2 PES XML documents corresponding to each marked-up diagram are being posted on the DM2 collaboration site (www.silverbulletinc.com/dm2) Briefing format A UPDM diagram will be shown first, in it’s native form from UPDM 1.0 Annex C. Blue background. Then DM2 annotated version of the same diagram will be shown. White background. The UPDM Team has been reviewing the material as it develops.

Exemplar Development Process Discuss Candidate Datasets with Core Process Stakeholders DoDAF Journal DoDAF Outreach Brief - Views Conform Diagram to DoDAF 2 and Add Legends DoDAF Outreach Brief – DM2 Developers / Analyst / Integrator DM2 Description Document – PES DoD MDR DM2 Collaboration Site Add Additional Markups for DM2 Review With DoDAF / DM2 WG The DoDAF 2 development team went through the examples and interpreted in DoDAF 2 / DM2 terms. The UPDM Team has been reviewing the material as it develops. Enter Into DM2 Database DM2 DB PES Queries DM2 PES XML Documents

Briefing structure A UPDM diagram will be shown first, in it’s native form from UPDM 1.0 Annex C. Blue background. Then DM2 annotated version of the same diagram will be shown. White background. A snippet and summary of the associated DM2 PES XML file is shown The OMG UPDM Team developed examples of the views as part of UPDM 1.0. It is called “Sample Problem” and is Annex C in the UPDM 1.0 Spec. The UPDM Team is working on a refinement of the Sample Problem for UPDM 2.0. The DoDAF 2 development team went through the examples and interpreted in DoDAF 2 / DM2 terms. DM2 PES XML documents corresponding to each marked-up diagram are being posted on the DM2 collaboration site (www.silverbulletinc.com/dm2) Briefing format A UPDM diagram will be shown first, in it’s native form from UPDM 1.0 Annex C. Blue background. Then DM2 annotated version of the same diagram will be shown. White background. The UPDM Team has been reviewing the material as it develops.

UPDM SAR AV-1

FFP AV-1 with DM2 Markups

AV-1 Recommended Additional Information Summary of the Architecture Project Architecture Project Planning and Management Info Purpose, Usage, Analysis results, Findings Data / Views Produced Summary of the Architecture Scope & Timeframe of the SAR Architecture (e.g., all US military-involved SAR, 2010-2014), JCAs applies to, JPD, Threat Environment, Geographic Area (e.g., US Coastal only, +/- 70 deg latitude, include polar ops), Missions, Scenarios, Capability Areas Supported, Relates to OV-1

UPDM SAR 1st AV-2

1st AV-2 with DM2 Markups

UPDM SAR 2nd AV-2

2nd AV-2 with DM2 Markups

AV-2 Additional Information Recommended Dictionary (with definitions*) of all objects that show up in the architectural description Activity Agreement Capability Condition Data DesiredEffect Guidance Information Location Materiel Measure MeasureType Organization PersonType Project Rule Service Skill Standard System Vision *possibly whole-part and super-subtype relations

UPDM SAR OV-1

OV-1 Encoding in DM2 IDref 001 IDref 002 = graphic OV-1 IDref 003 = name “OV-1 Maritime Rescue” IDref 004 = graphic repscheme IDref 005 = name namescheme IDref 006 = name of the 001 (001, 002) (002, 003) (001, 006) Name of RepScheme=“MIMEdGraphic” (002, 004) (003, 005) (006, 005) Name of NameScheme=“AlphanumicEnglish” Exemplar = “OV-1 Maritime Rescue” Exemplar = “Maritime Rescue” IDref 002 = graphic OV-1

UPDM SAR OV-1 Vol I: The high-level graphical or textual description of the operational concept, pg 23 Vol II: Pictorial representation of the written content of the AV-1, sec 3.1.4.2.1. AV-1: Purpose, Scope, Tools Used, Analysis Results, Organizations Involved

OV-1 Encoding in DM2 Same as before. Even though it looks like it has structure, by definition, an OV-1 is a graphic only. If you need to convey something structural, use a DoDAF pre-defined model or create your own fit-for-purpose.

UPDM SAR OV-2 Really s/b Search Node (SN)

OV-2 with DM2 Markups

Fit-for-Purpose OV-2 with SV-1 Composite

UPDM SAR OV-3 [Architectural Description] Structure [OV-3] Information Exchange Producer Needline Consumer Name Conveyed Node Operational Activity Ctrl «Information Element» control «Node» Tactical C2   TC2N - RN «Node» Rescue TC2N - SN «Node» Search DS «Information Element» distressSignal «Node» Person in Distress Send Distress Signal PiD – MN «Node» Monitoring Receive Distress Signal PiD – SN PiD - RN Rqst «Information Element» request TC2N - SAR AC «Node» SAR Asset Controller Stat «Information Element» status Monitor Health SN - RN Provide Medical Assistance TI «Information Element» trackInfo MN - TC2N Tsk «Information Element» tasking SAR AC - RN SAR AC - SN WO «Information Element» warningOrder Send Warning Order SN - PoS «Node» Place of Safety Process Warning Order

Partial OV-3 with DM2 Markups [Architectural Description] Structure [OV-3] Organization Type that performs the Producing Activity Producing Activity Info Acronym Information Name Consuming Activity Organization Type that performs the Consuming Activity Tactical C2 Control Rescue  Ctrl Controls Receive and Execute Controls  Rescue  Control Search  Receive and Execute Controls Search Person in Distress Send Distress Signal DS DistressSignal Receive and Respond to Distress Signal Monitoring Determine and Send Request  Rqst Request  Receive and Respond to Request SAR Asset Controller Monitor Health Stat Status Provide Medical Assistance  Estimate and Disseminate Track Info TI TrackInfo  Process, Store, and Present TrackInfo  Task Tsk Tasking  Receive and Execute Tasking Send Warning Order WO WarningOrder Process Warning Order Org at Place of Safety Legend: Activity Resource Overlap (ARO) Activities NOTE 1: Some tools in current use may have additional naming conventions, e.g., for ICOMs or Needlines NOTE 2: OV-3 has measures and other attributes associated with resource flow, the resource, or the consuming and producing activities Organization Types Information Activity Performed By Performer

UPDM SAR OV-4

OV-4 with DM2 Markups

UPDM SAR OV-5

OV-5a+ with DM2 Markups

UPDM SAR OV-5

FFP OV-5b/6c Hybrid NOTE 1: Do not have to be modeled

UPDM SAR OV-6b

OV-6b with DM2 Markups

UPDM SAR DIV-2

DIV-2 with DM2 Markups

Rule Activity Resource (e.g,. Info or Data)

UPDM SAR SV-1

SV-1 with DM2 Markups

UPDM SAR SV-2

SV-2 with DM2 Markups

Performance Requirement UPDM SAR SV-7 Parameter ID System/Element Performance Requirement Metric Measure Hardware H 1.1 Voice Radio Transmitter Transmission rate 2 GB H 2.1 Voice Radio Receiver Gain 60 dB H 2.2 Signal to Noise Ratio 20 H 3.1 Signal Processor Comms Channel Bandwidth Support Software S 1.2 Status Alerting Min. status change alert accuracy 500 meters S 1.3 Min. alert response time 30 seconds

SV-7 with DM2 Markups Legend: Measure Types Measure Type units System – Measure association Measure – Measure Type association System – Measure Type – Measure association Name3 System Measure Type Measure Measure Type units Hardware1 H 1.1 Voice Radio Transmitter Transmission rate 2 GB H 2.1 Voice Radio Receiver Gain 60 dB H 2.2 Signal to Noise Ratio 20 H 3.1 Signal Processor Comms Channel Bandwidth Support Software1 S 1.2 Status Alerting (component) Min. status change alert accuracy 500 meters S 1.3 Min. alert response time 30 seconds Legend: Header means Systems below principally consist of this Materiel type Measure Types Measure Type units Measures Systems Materiel (type)1 NOTE 1: Not generally shown in SV-7 NOTE 2: Often it is necessary to relate the Activity (aka System Function) to which the metric applies within the System. Many, often most, System metrics relate to some Activity performed by the System. NOTE 3: Not necessary.

UPDM SAR SV-10b

SV-10b with DM2 Markups

UPDM SAR CV-1

Partial1 CV-1 with DM2 Markups

UPDM SAR CV-2

Partial1 CV-2 with DM2 Markups

UPDM SAR CV-4

Partial1 CV-2 with DM2 Markups

UPDM SAR CV-4

Partial1 CV-4 with DM2 Markups

UPDM SAR CV-5

Partial1 CV-5 with DM2 Markups

UPDM SAR CV-6

CV-6 with DM2 Markups

UPDM SAR SvcV-3

CV-7 with DM2 Markups

UPDM SAR SvcV-1

SvcV-1 (partial) with DM2 Markups

UPDM SAR SvcV-2

SvcV-2 with DM2 Markups

UPDM SAR SvcV-3

SvcV-3b Services-Services Matrix with DM2 Markups Legend: Services

UPDM SAR SvcV-5

SvcV-4 Services Functionality Description with DM2 Markups

SvcV-5 with DM2 Markups NOTE 1: Indentation means whole-part

UPDM SAR SvcV-4a

SvcV-10a Services Rules Model with DM2 Markups

UPDM SAR PV-1

PV-2 with DM2 Markups time PV-2: Project Timelines A timeline perspective on programs or projects, with the key milestones and interdependencies time SAR Project Develop MRU Partial Interpretation as GANNT Sustain MRU Develop MRU V2 Sustain MRU V2

UPDM SAR PV-1

PV-1 with DM2 Markups

UPDM SAR PV-1

PV-1 with DM2 Markups

UPDM SAR PV-1

FFP PV-2 Fusion with Systems Engineering Plan (SEP) with DM2 Markups PV-2: Project Timelines A timeline perspective on programs or projects, with the key milestones and interdependencies

Lessons Learned & Next Steps UML translates to DoDAF/DM2 fairly straightforwardly Some UPDM MODAF concepts are not obvious, e.g., Enterprise Phase Services, Service Descriptions, etc. are still work-in-progress as OASIS, OMG, and the SoA community continue to evolve A DM2 database was indispensible Validate on input (compared to XML document validation) More tractable Some input tools would be nice The DM2 DB DDL and PES generator scripts are free GFI for vendors, repository developers, etc. A CJCSI 6212 example is next

Extra Variants

UPDM SAR metrics

UPDM SAR Conditions and metrics

Actual Measurement Set UPDM SAR SV-7 [Architectural Description] System View [SV-7] Resource Actual Measurement Set Type Name Measurement Actual Value Unit Dimension «CapabilityConfiguration» Maritime Configuration Initial Values seaConditions Sea State 6 Meter Wave Height areaCoverage 500 SquareKilometers Area findTime <8 Hours Time persistence >15 searchCoverage 400 weatherConditions Heavy Rain Weather Severity Index   Maritime Configuration V2 Final Values sea state 8 650 <4 >20 550 Stormy Maritime Rescue Unit Maritime Rescue Unit V2

UPDM SAR SV-7

Roles X Functions

Markup Standards Measure NOTE 1: Legend: Subtypes Subtypes Part-Of