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

DoDAF 2.0 ExemplarsUPDM 1.0 X DoDAF 2.0 X DM2 PES XML Examples

12 August 2010DoDAF Development Team

Briefing Outline• Why exemplars• Method• Briefing structure• The 28 views X 3• Lessons learned and next steps

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 format1. A UPDM diagram will be shown first, in it’s native form from UPDM 1.0 Annex C.

Blue background.2. Then DM2 annotated version of the same diagram will be shown. White

background.

Exemplar Development Process

DM2 DB

DM2 PES XML Documents

Discuss Candidate

Datasets with Core Process Stakeholders

Conform Diagram to

DoDAF 2 and Add Legends

Add Additional

Markups for DM2

Enter Into DM2

Database

1.DoDAF Journal2.DoDAF Outreach Brief - Views

1.DoDAF Journal2.DoDAF Outreach Brief - Views

1.DoDAF Outreach Brief – DM2 Developers / Analyst / Integrator

2.DM2 Description Document – PES

3.DoD MDR4.DM2 Collaboration Site

1.DoDAF Outreach Brief – DM2 Developers / Analyst / Integrator

2.DM2 Description Document – PES

3.DoD MDR4.DM2 Collaboration Site

Review With DoDAF / DM2 WG

PES Queries

Briefing structure

1. A UPDM diagram will be shown first, in it’s native form from UPDM 1.0 Annex C. Blue background.

2. Then DM2 annotated version of the same diagram will be shown. White background.

3. A snippet and summary of the associated DM2 PES XML file is shown

AV-1 [Architectural Description] Enterprise

«WholeLifeEnterprise»Search and Rescue

startDate2010-01-01 00:00:00

endDate2014-06-01 00:00:00

«EnterprisePhase»Phase 1

startDate2010-01-01 00:00:00

endDate2010-12-01 00:00:00


startDate2012-12-01 00:00:00

endDate2014-06-01 00:00:00

TPart1

TPart2

1

1

1

UPDM SAR AV-1 AV-1 Overview and Summary Information

Describes a Project's Visions, Goals, Objectives, Plans, Activities, Events, Conditions, Measures, Effects (Outcomes), and produced objects.

FFP AV-1 with DM2 Markups

Legend:

AV-1 [Architectural Description] Enterprise

Search and Rescue

startDate2010-01-01 00:00:00

endDate2014-06-01 00:00:00

Phase 1

startDate2010-01-01 00:00:00

endDate2012-12-01 00:00:00

Phase 2

startDate2012-12-01 00:00:00

endDate2014-06-01 00:00:00

11

1

Capability

NOTE: Only describes the Capability Phases of the Architecture

Measure of Temporal boundary

MeasureTypes

Temporal Whole Part

Measures

Whole part

Performer

Capability of Performer

SAR Perfomers

SAR Phase 1 Perfomers

SAR Phase 2 Perfomers

AV-1 Overview and Summary Information


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

AV-1 Overview and Summary Information


AV [Architectural Description] Measurements [Class]

«MeasurementSet»«valueType»

Standard SAR Measurements

«Measurement» areaCoverage : Coverage«Measurement» findTime : Elapsed Time«Measurement» persistence : Elapsed Time«Measurement» searchCoverage : Coverage«Measurement» weatherConditions : Weather Conditions


Maritime SAR Measurements

«Measurement» seaConditions : Sea State


Land SAR Measurements

«Measurement» terrain : Terrain Type

UPDM SAR 1st AV-2 AV-2 Integrated Dictionary

Architecture data repository with definitions of all terms used throughout the architecture data and presentations.

1st AV-2 with DM2 Markups

Standard SAR Measurements

AV [Architectural Description] Measurements [Class]

Coverage à Area CoverageElapsed Time à Find TimeElapsed Time à Persistence

Coverage à Search CoverageWeather Conditions

Maritime SAR Measurements

SeaConditions à Sea State

Land SAR Measurements

Terrain Characterization à Terrain Type

Legend:

MeasureTypes

Subtypes

NOTE 1: This line means the object above is the supertype and below are the subtypes

AV-2 Integrated Dictionary


AV [Architectural Description] Measurements [Instance]

«ActualMeasurementSet»Initial Values

seaConditions : Sea State = Sea State 6areaCoverage : Coverage = 500findTime : Elapsed Time = <8persistence : Elapsed Time = >15 hourssearchCoverage : Coverage = 400weatherConditions : Weather Conditions = Heavy Rain

«ActualMeasurementSet»Required Values

seaConditions : Sea State = Sea State 8areaCoverage : Coverage = 600 findTime : Elapsed Time = <5 persistence : Elapsed Time = >20 searchCoverage : Coverage = 500 weatherConditions : Weather Conditions = Stormy

seaConditions : Sea State = Sea State 8areaCoverage : Coverage = 650 findTime : Elapsed Time = <4 persistence : Elapsed Time = >20 searchCoverage : Coverage = 550 weatherConditions : Weather Conditions = Stormy

«ActualMeasurementSet»Final Values

UPDM SAR 2nd AV-2 AV-2 Integrated Dictionary


2nd AV-2 with DM2 Markups

Minimum Wave Height

AV [Architectural Description] Measurements [Instance]

Sea Conditions3 à Sea State, units Sea State ValueArea Coverage à Search Coverage, units sq miMaximum Elapsed Time à maxFindTime, units hrPersistence à Minimum Elapsed Time, units hoursArea Coverage à Search Coverage, units sq miWeather Conditions, units WC Summary

MeasureType Names (definitions not shown)

NOTE 1: There is a part-of for each Sea State valueNOTE 2: These will be ascribed to each Capability and providing Performer phases as “required”, “actual”, “initial” and “final”.NOTE 3: In real SAR, would also consider Sea Swell

Legend:

MeasureTypes

Subtypes

Maximum Wave Height

Part-Of



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-1OV-1: High Level Operational Concept Graphic

High-level graphical/textual description of operational concept

IDEAS Naming and Description Pattern

Thing

namedBy

IndividualType

Name Resource

Information

describedBy

SignType

Representation

- exemplar: variant

representedBy

tuple

couple

NameType

NamingScheme

RepresentationType

RepresentationScheme

typeInstance

representationSchemeInstance

namingSchemeInstance

ArchitecturalDescription

nameSpace nameInstance

1

name

description

thingDescribed

*

{subsetsplaces}

1

representation

instance

scheme

*{subsetsplaces}

1

Exemplar = “OV-1 Maritime Rescue”Exemplar = “Maritime Rescue”

IDref 001IDref 002 = graphic OV-1IDref 003 = name “OV-1 Maritime Rescue”IDref 004 = graphic repschemeIDref 005 = name nameschemeIDref 006 = name of the 001

(001, 002)(002, 003)(001, 006)

Name of RepScheme=“MIMEdGraphic”

Name of NameScheme=“AlphanumicEnglish”

(002, 004)

(003, 005)(006, 005)

IDref 002 = graphic OV-1

OV-1 Encoding in DM2OV-1: High Level Operational Concept Graphic


[OV-1] Maritime Rescue

«ConceptRole»Aircraft : RN ASR Helo

««ConceptRole»Yacht : Boat

«ConceptRole»Monitor Unit : Monitor

«ConceptRole»C2 Center : Control Center

«ConceptRole»RNLI Lifeboat : Boat

«ConceptRole»Naval Ship : Boat

trackInfo

trackInfo

trackInfocontrol control

assistance

distressSignal

control

UPDM SAR OV-1OV-1: High Level Operational Concept Graphic


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.

OV-1: High Level Operational Concept Graphic



Thing

namedBy

IndividualType

Name Resource

Information

describedBy

SignType

Representation

- exemplar: variant

representedBy

tuple

couple

NameType

NamingScheme

RepresentationType


typeInstance





1

name

description

thingDescribed

*

{subsetsplaces}

1

representation

instance

scheme

*{subsetsplaces}

1



(001, 002)(002, 003)(001, 006)



(002, 004)

(003, 005)(006, 005)



Thing

namedBy

IndividualType

Name Resource

Information

describedBy

SignType

Representation

- exemplar: variant

representedBy

tuple

couple

NameType

NamingScheme

RepresentationType


typeInstance





1

name

description

thingDescribed

*

{subsetsplaces}

1

representation

instance

scheme

*{subsetsplaces}

1



(001, 002)(002, 003)(001, 006)



(002, 004)

(003, 005)(006, 005)


OV-2 [Architectural Description] Nodes

«Node»Place of Safety

«Node»Search

«Node»Rescue

«Node»Person in Distress

«Node»SAR Asset Controller

«Node»Tactical C2

«Node»Monitoring

WO : warningOrder

DS : distressSignal

DS : distressSignal

DS : distressSignal

Tsk : tasking

Tsk : tasking

Ctrl : control

Rqst : request TI : trackInfo

Rqst : request

Stat : status

«Needline»

«Needline»

«Needline»«Needline»

«Needline»

«Needline»

«Needline»«Needline»

«Needline» «Needline»

«Needline»

Really s/b Search Node (SN)

UPDM SAR OV-2 OV-2: Operational Connectivity Description

Operational connectivity and resource flow needlines

OV-2 with DM2 MarkupsOV-2: Operational Connectivity Description

Operational connectivity and resource flow needlines

OV-2 [Architectural Description] Organizational Interactions

WO : warningOrderPlace of Safety1

Search Org Type

Rescue Org TypePerson in Distress

SAR Asset ControllerTactical C2Org Type Monitoring

Org Type

DS : distressSignal

DS : DistressSignal

DS : distressSignal

Tsk : tasking

Tsk : tasking

Ctrl : control

Rqst : request

TI : trackInfo

Rqst : request

Stat : status

PoS Org Type

Legend:

Organization Types

Information (Resource)

Resource Flows

PersonType

Location Type

Consume (Activity)1

Produce (Activity)1

Bounding box means Resource at Location

Receive Distress Signal

APBP

NOTE 1: Implied. In DoDAF 2, “produce”, “consume”, “send”, “receive” are Activities. An OV-2 diagram need not show the implied activities but the DM2 PES XML document must, even if they are just placeholders to be completed later, e.g., during OV-5 development. This precision solves the “overspecification” problem of earlier DoDAF OV’s.

Boat Radio Communications System2

OV-2 [Architectural Description] Organizational Interactions

WO : warningOrderPlace of Safety1

Search Org Type

Rescue Org TypePerson in Distress

SAR Asset Controller

Tactical C2Org Type Monitoring

Org Type

DS : distressSignal

DS : voiceDistressSignal

DS : distressSignal

Tsk : tasking

Tsk : tasking

Ctrl : control

Rqst : request

TI : trackInfo

Rqst : request

Stat : status

PoS Org Type

speak

key

Boat Radio2

DS : keyDistressSignal

Legend:

Organization Types

Information (Resource)

Resource Flows

PersonType

Location Type1

Bounding box means Resource at Location

Materiel

System

Consume (Activity)

Produce (Activity)

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

[Architectural Description] Structure [OV-3]

Information Exchange Producer Needline Consumer

Name Conveyed Node Operational Activity Name Node Operational Activity

Ctrl «Information Element» control «Node» Tactical C2 TC2N - RN «Node» Rescue

Ctrl «Information Element» control «Node» Tactical C2 TC2N - SN «Node» Search

DS «Information Element» distressSignal «Node» Person in Distress Send Distress Signal PiD – MN «Node» Monitoring Receive Distress Signal

DS «Information Element» distressSignal «Node» Person in Distress Send Distress Signal PiD – SN «Node» Search Receive Distress Signal

DS «Information Element» distressSignal «Node» Person in Distress Send Distress Signal PiD - RN «Node» Rescue Receive Distress Signal

Rqst «Information Element» request «Node» Tactical C2 TC2N - SAR AC «Node» SAR Asset Controller

Stat «Information Element» status «Node» Search Monitor Health SN - RN «Node» Rescue Provide Medical Assistance

TI «Information Element» trackInfo «Node» Monitoring MN - TC2N «Node» Tactical C2

Tsk «Information Element» tasking «Node» SAR Asset Controller SAR AC - RN «Node» Rescue

Tsk «Information Element» tasking «Node» SAR Asset Controller SAR AC - SN «Node» Search

WO «Information Element» warningOrder «Node» Search Send Warning Order SN - PoS «Node» Place of Safety Process Warning Order

UPDM SAR OV-3OV-3: Operational Resource Flow Matrix

Information exchanged and the relevant attributes of that exchange

Organization Type that performs the Producing

ActivityProducing Activity

Info Acronym

Information Name Consuming ActivityOrganization Type that performs

the Consuming Activity

Tactical C2 Control Rescue Ctrl Controls Receive and Execute Controls Rescue

Tactical C2 Control Search Ctrl Controls Receive and Execute Controls Search

Person in Distress Send Distress Signal DS DistressSignalReceive and Respond to Distress

SignalMonitoring


SignalSearch


SignalRescue

Tactical C2 Determine and Send Request Rqst Request Receive and Respond to Request SAR Asset Controller

Search Monitor Health Stat Status Provide Medical Assistance Rescue

Monitoring Estimate and Disseminate Track

InfoTI TrackInfo

Process, Store, and Present TrackInfo

Tactical C2

SAR Asset Controller Task Tsk Tasking Receive and Execute Tasking Rescue

SAR Asset Controller Task Tsk Tasking Receive and Execute Tasking Search

Search Send Warning Order WO WarningOrder Process Warning Order Org at Place of Safety

Partial OV-3 with DM2 Markups

Legend:

NOTE 1: Some tools in current use may have additional naming conventions, e.g., for ICOMs or NeedlinesNOTE 2: OV-3 has measures and other attributes associated with resource flow, the resource, or the consuming and producing activities

Activity Performed By Performer

Activity Resource Overlap (ARO)Activities

Organization Types

Information

[Architectural Description] Structure [OV-3]

OV-3: Operational Resource Flow Matrix

Information exchanged and the relevant attributes of that exchange

OV-4 [Architectural Description] Organization

«Organization»UK SAR Operator

«Organization»UK SAR Organization

«Organization»Government Department

«Organization»SAR Government Department

«Post»UK SAR SC Member

«Post»MRT Boat Driver

«Post»MRT Helicopter Pilot

«Organization»Voluntary Organization

subOrg

1

*

1

* member

«Post»MRT Searcher

«Post»MRT Swimmer

«Post»MRT Communicator

«Person»Marine Radio Operator

«Person»Qualified Lifeguard

«Person»Qualified Helo Pilot

«Person»Qualified EMT

«Person»Qualified Lifeboat Driver

1

1

1

1

UPDM SAR OV-4OV-4: Organizational Relationships Chart

Organizational, role, or other relationships among Organizations

OV-4 with DM2 Markups

OV-4 [Architectural Description] Organization

Government Department

SAR SC Member

*

1*member

1

1

1

1

Legend:

PersonRoleTypes Subtypes

Part-Of

Skill

Measure & MT

Org Types

MRT Helicopter

Pilot

MRT Communicator

Marine Radio OperatorQualified

Lifeguard

Qualified Helo Pilot Qualified

EMT

Qualified Lifeboat Driver

S&R Organization

USCG

Voluntary Organization

Activities

Skill of Person Type

Measure of Type

100/min

Conduct CPR Pumping

80/min

5 km/hr

Swim

2 km/hr

8 L

Conduct CPR Blowing

6 L

MRT Boat DriverMRT

Searcher

Excellent CPR Pumping Rate

Good CPR Pumping Rate

Good CPR Blow Volume

Excellent CPR Blow Volume

Excellent Swim Speed

Good Swim Speed

MRT Swimmer

Organization

OV-4: Organizational Relationships Chart

Organizational, role, or other relationships among Organizations

OV-5 [Architectural Description] Activities

«Node»Search

«OperationalActivity»Search

«Performs»

«Node»Rescue

«OperationalActivity»Find Victim

«OperationalActivity»Send Warning Order

«OperationalActivity»Monitor Health

«OperationalActivity»Receive Distress Signal

«Node»«block»Search

«Node»«block»Rescue

«OperationalActivity»Rescue

«OperationalActivity»Provide Medical Assistance

«OperationalActivity»Recover Victim

«Performs»

«Performs» «Performs»

«Performs» «Performs»«Performs» «Performs»

«Performs»

UPDM SAR OV-5OV-5a: Activity Decomposition Tree

Activities and their decomposition hierarchy.

OV-5a+ with DM2 Markups

OV-5a+1 [Architectural Description] Activities

Searcher

Search

Rescuer

Find Victim

Send Warning OrderMonitor Health


SearcherRescuer

Rescue

Provide Medical Assistance

Recover Victim

NOTE 1: OV-5a’s don’t show the Performer “mechanisms”. This is actually a hybrid or “fit for purpose”.

Legend:

Activities

Part-OfAn Activity Performed by a Performer

Orgs / Org Types / Person Types

OV-5a: Activity Decomposition Tree

Activities and their decomposition hierarchy.

OV-5 [OperationalActivity] Search

«Nod

e»: S

earc

h an

d R

escu

e

«OperationalActivityAction»: Send Distress Signal

Updated Condition Updated Location

Search

Reported Location Reported Condition

«Nod

eRol

e»P

iD: P

erso

n in

Dis

tres

s«N

odeR

ole»

SN

: Sea

rch

«Nod

eRol

e»R

N: R

escu

e«N

odeR

ole»

PoS

: Pla

ce o

f Saf

ety

«OperationalActivityAction»: Receive Distress Signal

«OperationalActivityAction»: Receive Distress Signal

«OperationalActivityAction»: Send Warning Order

«OperationalActivityAction»: Find Victim

«OperationalActivityAction»: Monitor Health

«OperationalActivityAction»: Provide Medical Assistance

«OperationalActivityAction»: Recover Victim

«OperationalActivityAction»: Process Warning Order

«OperationalActivityAction»: Transit to SAR Operation

distressSignal

distressSignal

distressSignal

warningOrder

warningOrder

condition

location

location

condition

UPDM SAR OV-5OV-5b: Activity Model

Capabilities, activities (operational activities), relationships among activities, inputs, and outputs; overlays can show cost, performers or other pertinent information

FFP OV-5b/6c Hybrid

OV-5 [OperationalActivity] Search

Sea

rch

and

Res

cue

Send Distress Signal

Updated Condition Updated Location

Search


Per

son

In D

istr

ess

Sea

rch

Res

cue

Pla

ce o

f Saf

ety

Org

Typ

e


Receive Distress Signal Send Warning Order Find Victim Monitor Health

Provide Medical Assistance Recover Victim

Process Warning OrderTransit to SAR Operation

distressSignal

warningOrder

Legend:

Organization Types

APBP

Part-Of

Activities

Information

Resource Flow

Before-After

OV-5b: Activity Model

Capabilities, activities (operational activities), relationships among activities, inputs, and outputs; overlays can show cost, performers or other pertinent information

NOTE 1: Do not have to be modeled

OV-6c: Event-Trace Description

One of three models used to describe activity (operational activity) - traces actions in a scenario or sequence of events

OV-6b [Node] Search

Waiting for Distress Signal

do : Monitor for Distress Signals

Searching for Victim

do : Track Victimdo : Find Victim

Monitoring Victim

do : Monitor Health

Transfer to Rescue Team

do : Transport Victim

receiveDistressSignal/Send Warning Order

[Victim Stable]/

[Victim Secure]/

searchCancelled/

[No Assistance required]/

//

[Victim Found]/

[Assistance Required]/

UPDM SAR OV-6b OV-6b: State Transition Description

One of three models used to describe activity (operational activity) - identifies business process responses to events

OV-6b with DM2 Markups OV-6b: State Transition Description

One of three models used to describe activity (operational activity) - identifies business process responses to events

Searcher

OV-6b Searcher

Search in Wait for DistressSignal State

Searcher inSearch for Victim State

Track Victim

Search in Monitor Victim State

Monitor Health

Searcher in Transfer to Rescue Team State

[Victim Stable]/

[Victim Found]/

[Assistance Required]/

Legend:

Performer

APBP

Information

Resource Flow and Before-AfterTemporal Whole Part

Monitor for Distress Signals

Whole Part

Find Victim

Search Cancelled/

[No Assistance required]/

Est Victim Pos

Resource Flow

Warning Order

Determine if assistance is required

Transport Victim

[Victim Secure]/

NOTE 4

NOTE 3

Activities

Produce or Consume Activities2

NOTE 1: An Event is a near-zero duration Activity in DoDAF 2.NOTE 2: The produce / consume activities are not shown for all Performers.NOTE 3: Start time for the Monitor for Distress Signals activityNOTE 4: Stop time for the Monitor for Distress Signals activity (e.g., max time)

Distress Event1

OV-7 [Logical Data Model] Logical Data Model

«EntityItem»Last Known Position

latitude : Stringlongitude : Stringtime : StringsourceOfReport : String

«EntityItem»Search Area

waypoints : StringactivationTime : Stringduration : StringdriftDirection : StringdriftSpeed : IntegercommenceSearchPoint : String

«EntityItem»Search Object

name : Stringregistration : Stringtonnage : Integercolor : Stringmarkings : Stringsuperstructure : Stringcharacteristics : StringownerOrOperator : StringpersonsOnBoard : IntegeremergencyEquipmentCarried : String

«EntityItem»SAR Operation

caseName : StringcaseNumber : StringtaskingAuthority : String

«EntityItem»SearchStatus

status : String

«EntityItem»Assignment

description : String

location

assetAssignmentsoperationalArea

objects

*

*

*

*

*

*

*

*

*

1

1

1

representedBy«InformationElement» control

representedBy «InformationElement» trackInfo «InformationElement» distressSignal

representedBy «InformationElement» tasking «InformationElement» control

representedBy«InformationElement» request

representedBy«InformationElement» status

representedBy«InformationElement» warningOrder

«EntityItem»StrandedPersonInfo

name : Stringcondition : String

* person1

1

location

1

UPDM SAR DIV-2 DIV-2: Logical Data Model

Documentation of the data requirements and structural business process rules (In DoDAF V1.5, this was the OV-7)

DIV-2 with DM2 Markups DIV-2: Logical Data Model

Documentation of the data requirements and structural business process rules (In DoDAF V1.5, this was the OV-7)

DIV-2 [Logical Data Model] Logical Data Model

Last Known Position

latitude : Stringlongitude : Stringtime : StringsourceOfReport : String

Search Area

waypoints : StringactivationTime : Stringduration : StringdriftDirection : StringdriftSpeed : IntegercommenceSearchPoint : String

Search Object

name : Stringregistration : Stringtonnage : Integercolor : Stringmarkings : Stringsuperstructure : Stringcharacteristics : StringownerOrOperator : StringpersonsOnBoard : IntegeremergencyEquipmentCarried : String

SAR Operation

caseName : StringcaseNumber : StringtaskingAuthority : String

SearchStatus

status : String

Assignment

description : String

location

assetAssignmentsoperationalArea

objects

*

**

*

**

*

*

*

1

1

1

control trackInfo

distressSignal

taskingcontrol

request

status

warningOrder

StrandedPersonInfo

name : Stringcondition : String

*person1

1

location

1

NOTE 1: tied to Info via activityResourceOverlapSuperSubtypeOfRule, activityResourceOverlap, Resource, and that Info is a type of ResourceNOTE 2: Data is a subtype of Information, a more formatted version.

Legend:

DataType

informationAssociation“has”“aggregates”

Rule (NOTE 1)

InformationType

Subtype (NOTE 2)

Activity

Rule

Resource (e.g,. Info or Data)

SV-1 [Capability Configuration] Maritime Rescue Unit

«CapabilityConfiguration»Maritime Rescue Unit

«HumanResource»MRT : Maritime Rescue Team

«PostRole»Driver : MRT Boat Driver

«PostRole»Searcher : MRT Searcher

«PostRole»Radio Operator : MRT Communicator

«PostRole»Rescue Swimmer : MRT Swimmer

«PostRole»Pilot : MRT Helo Pilot

«ResourceComponent»MR Boat : Boat

«ResourceComponent»Beacon : Lighting Device

«ResourceComponent»Radio : Communication Device

«ResourceComponent»LifePreserver : Life Saving Device

«ResourceComponent»MR Aircraft : Aircraft

: BoatInstruction : BoatInstruction

: BeaconInstruction : BeaconInstruction

: RadioInstruction : RadioInstruction

: LifePreserverInstruction : LifePreserverInstruction

: AircraftInstruction : AircraftInstruction

«ResourceInteraction»«ItemFlow»

: BoatInstruction


: BeaconInstruction


: RadioInstruction


: LifePreserverInstruction


: AircraftInstruction

UPDM SAR SV-1 SV-1 Systems Interface Description

Identification of systems and system items and their interconnections

SV-1 with DM2 Markups

Legend:

Maritime Rescue Unit

MRT Boat

Helo

Maritime Rescue Team

SV-1 [Performer] Maritime Rescue Unit

MRT Boat Driver

MRT Searcher

MRT Communicator

MRT Swimmer

MRT Helo Pilot

Boat

Lighting Device

Communication Device

Life Saving Device

Aircraft

Receive BoatInstruction

Send BoatInstruction

Receive BeaconInstruction

Send BeaconInstruction

Receive RadioInstruction Send

RadioInstruction

Receive LifePreserverInstruction

Send LifePreserverInstruction

Receive AircraftInstruction

Send AircraftInstruction

BoatInstruction

BeaconInstruction

RadioInstruction

LifePreserverInstruction

AircraftInstruction

Systems

Activities PersonType

ResourceFlowInformation

Organization Type

Propusion and Rudder Control

Equipment

Whole - Part

APBP

SV-1 Systems Interface Description

Identification of systems and system items and their interconnections

SV-2 [CapabilityConfiguratioin] Maritime Configuration

«CapabilityConfiguration»Maritime Configuration

«UsedConfiguration»: Yacht

«UsedConfiguration»: RN ASR Helo

«UsedConfiguration»: RNLI Lifeboat

«ResourceComponent»Signal : Distress Beacon

Transmitter

«ResourceComponent»Comms Device : Voice Radio

«ResourceComponent»Monitor : ESM System

FrequencyScanner TrackInterface

«ResourceComponent»Comms Device : Voice Radio

Transmitter

Receiver

Receiver

Transmitter

«ResourceComponent»Digital Service : Link 16

TDM ReceiverTrackInterface

TDM Transmitter

«ResourceComponent»Monitor : ESM System

TrackInterface

FrequencyScanner

«ResourceComponent»Digital Service : Link 18

TDM Receiver

TDM Transmitter TrackInterface

UPDM SAR SV-2SV-2 Systems Communications Description

Systems and system items and their related communications laydowns


Legend:

SV-2 [CapabilityConfiguratioin] Maritime Configuration

Maritime Configuration

Yacht SAR Helo SAR Lifeboat

Signal ß Distress Beacon

Transmitter

Comms Device ß Voice Radio

Monitor ß ESM System

FrequencyScanner TrackInterface

Comms Device ß Voice Radio

Transmitter

Receiver

Receiver

Transmitter

Digital Service ß Link 16

TDM Receiver

TrackInterface

TDM Transmitter

Monitor ß ESM System

TrackInterface

FrequencyScanner

Digital Service ß Link 18

TDM Receiver

TDM TransmitterTrackInterface

System (NOTE 1)

PerformerNOTE 1: Operator assumed. Otherwise there would be Materiel.NOTE 2: Implied. They are all either “send” or “receive”.NOTE 3: Implied. Resource is “information”.

Activity (NOTE 2)

Subtypes

Part-Of

APBP

ARO (NOTE 3)

SV-2 Systems Communications Description

Systems and system items and their related communications laydowns

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 dB

H 3.1 Signal Processor Comms Channel Bandwidth Support

2 GB

Software

S 1.2 Status Alerting Min. status change alert accuracy

500 meters

S 1.3 Min. alert response time 30 seconds

UPDM SAR SV-7 SV-7 Systems Performance Parameters Matrix

Performance characteristics of Systems Model elements for the appropriate time frame(s)

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 dB

H 3.1 Signal Processor Comms Channel Bandwidth Support

2 GB

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

NOTE 1: Not generally shown in SV-7NOTE 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.

Measure Types

Measures

Measure Type units

Systems

Materiel (type)1

System – Measure association

Measure – Measure Type association

SV-7 Systems Performance Parameters Matrix

Performance characteristics of Systems Model elements for the appropriate time frame(s)

«FunctionAction»: Move


«Cap

abili

tyC

onfig

urat

ion»

Mar

itim

e R

escu

e U

nit

«Pos

t»M

RT

Sea

rche

r

«FunctionAction»: Reassure Victim

«FunctionAction»: Apply First Aid

«FunctionAction»: Recover Victim

«FunctionAction»: Determine Destination

Name

Updated Condition

«FunctionAction»: Transport

Updated Location

UPDM SAR SV-10b SV-10b Systems State Transition Description

One of three models used to describe system functionality—identifies responses of a system to events

SV-10b with DM2 Markups

Move

Reported Location Reported ConditionM

ariti

me

Res

cue

Uni

tM

RT

Sea

rch

er Reassure Victim Apply First Aid Recover Victim

Determine Destination

Name

Updated Condition

Transport

Updated Location

An Event or Trigger in DoDAF 2 is akin to a near-zero duration Activity

Bounding box differentiates internal from external Performers

Legend:

Person Type

Time

Activities performed by Performer

System

Activities

Information

Consume (Activity)

Produce (Activity)

Just a diagramming shortcut

Before-After

Resource Flow

SV-10b Systems State Transition Description

One of three models used to describe system functionality—identifies responses of a system to events

StV-1 [Architectural Description] Enterprise [1]

«WholeLifeEnterprise»Search and Rescue

startDate2010-01-01 00:00:00

endDate2014-06-01 00:00:00


startDate2010-01-01 00:00:00

endDate2010-12-01 00:00:00


startDate2012-12-01 00:00:00

endDate2014-06-01 00:00:00

Temporal Part1 Temporal Part2

1

11

goals«EnterpriseGoal» Fulfill International Obligations

visions«EnterpriseVision» UK SAR Vision

goals«EnterpriseGoal» Maintain UK SAR Responsibility

visions«EnterpriseVision» UK SAR Vision

exhibits«Capability» Assistance«Capability» Recovery«Capability» Search

exhibits«Capability» Assistance«Capability» Recovery«Capability» Search

«EnterpriseGoal»«requirement»

Maintain UK SAR Responsibility

«EnterpriseVision»UK SAR Vision

«EnterpriseGoal»«requirement»

Fulfill International Obligations

UPDM SAR CV-1 CV-1: Vision Overall vision for transformational endeavors, provides a strategic context for the capabilities described, and provides a high-level scope.

Partial1 CV-1 with DM2 Markups

CV-1: Vision Overall vision for transformational endeavors, provides a strategic context for the capabilities described, and provides a high-level scope.

Legend:

CV-1 SAR Vision

US SAR Vision

Capabilities

Visions

Desired EffectsActivities

Activities part of Capabilty


Resource6MeasureTypes

Temporal Whole PartMeasures

2012-12-01 00:00:00endDate

2010-01-01 00:00:00startDate4

Assist Recover Search

NOTE 1: “Partial” because any CV should contain the structural description of the Capabilities, in terms of Desired Effects and associated measures, Activities to be performed under conditions – and associated measures.NOTE 2: The start and stop times are the min of the starts and the max of the ends of the phases that are TWPs of the the whole-life enterprise.NOTE 3: Whole Capability lasts 54 monthsNOTE 4: Phase I lasts 35 monthsNOTE 5: Phase II lasts 19 monthsNOTE 6: Desired effects are states of Resources

2014-06-01 00:00:00endDate

2012-12-01 00:00:00startDate5

International Obligations Fulfilled Search and

Rescue2

SAR Phase 1 SAR Phase 2

US SAR Responsibility Maintained

StV-2 [Architectural Description] Capabilities

«Capability»SAR

«Capability»Maritime SAR

«Capability»Land SAR

actualMeasurements«ActualMeasurementSet» Required Values

UPDM SAR CV-2 CV-2: Capability Taxonomy

A hierarchy of capabilities, specifies all the capabilities that are referenced throughout one or more architectures.


CV-2: Capability Taxonomy


Legend:

CV-2 SAR Capabilities

SAR Phase I

Maritime SAR Land SAR

response time: hr

Capabilities

Recover

Activities

Activities part of Capabilty

MeasureTypes

Super subtypeMeasures

Measure of Activity part of

Capability

1

distance from station: miles

100

NOTE 1: “Partial” because any CV should contain the structural description of the Capabilities, in terms of Desired Effects and associated measures, Activities to be performed under conditions – and associated measures.

StV-4 [Architectural Description] Capabilities

«Capability»SAR

«Capability»Assistance

«Capability»Distress Signal Monitoring

«Capability»Inform

«Capability»Search

«Capability»Military C2

«Capability»Recovery

«Capability»SAR C2

1

1

1

1

1

1

1Asst

DSM

Inf

Srch

MilC2

Rec

SC2

1

UPDM SAR CV-4CV-4: Capability Dependencies

Dependencies between planned capabilities and defines logical groupings of capabilities.


Assistance

Distress Signal Monitoring

Inform

Search

Military C2

Recovery

SAR C2

Legend:

CV-2 [Architectural Description] Capabilities

SAR

Military C2 SAR C2

1

1

1

1

1

1

1

1

CapabilitiesWhole-part with cardinalities (NOTE 2)

NOTE 2: Cardinalities mean the SAR Capability has one and only one Assistance Capability and vice-versa

NOTE 1: “Partial” because any CV should contain the structural description of the Capabilities, in terms of Desired Effects and associated measures, Activities to be performed under conditions – and associated measures.

CV-2: Capability Taxonomy


StV-4 [Capability] SAR Capability

«Capability»SAR

Inf : Inform

MIC2 : Military C2

DSM : Distress Signal Monitoring

SC2 : SAR C2

Srch : Search Asst : Assistance Rec : Recovery

UPDM SAR CV-4 CV-4: Capability Dependencies



CV-4 [Capability] SAR Capability

Legend:

Capabilities Whole-part (NOTE 2)

Desired Effect Whole-part (NOTE 3)

NOTE 1: “Partial” because any CV should contain the structural description of the Capabilities, in terms of Desired Effects and associated measures, Activities to be performed under conditions – and associated measures.NOTE 2: Bounding box shows DSM, SC2, Inf, MIC2, Srch, Asst, Rec are “grouped under” (part-of or overlap-with) SARNOTE 3: Means, the desired effect of the “whole” capability includes the desired effects of the “parts”.

SAR

Inform (communicate)

Military C2

Distress Signal Monitoring

SAR C2

Search Assistance Recovery

SAR C2 depends-on Military C2

Inform depends-on DSM

Military C2 depends-on

Inform

Search depends-on

SAR C2

Assistance depends-on

SAR C2

Recovery depends-on

SAR c2

SAR C2 depends-on

DSM

CV-4: Capability Dependencies


[Architectural Description] Capabilities [StV-5]

Maritime Rescue UnitMaritime Rescue Unit V2












«ActualOrganization»RNLI

«ActualOrganization»Maritime & Coastguard Agency

Capabilities

Org

aniz

atio

nal

Res

ou

rces

UPDM SAR CV-5 CV-5: Capability to Organizational Development Mapping

The fulfillment of capability requirements, shows the planned capability deployment and interconnection for a particular Capability Phase.


Legend:

[Architectural Description] Capabilities [CV-5]

MRU V2

Assistance Inform Recovery Search

RNLI

Maritime & Coastguard

Agency

CapabilitiesPerformer that enables / supports

the Capability

Performer

Organizations

APBP NOTE 1: “Partial” because any CV should contain the structural description of the Capabilities, in terms of Desired Effects and associated measures, Activities to be performed under conditions – and associated measures.NOTE 2: Implied but not explicitly described

Activities

Produce

Produce

ConsumeNOTE 2

ARO

CV-5: Capability to Organizational Development Mapping

The fulfillment of capability requirements, shows the planned capability deployment and interconnection for a particular Capability Phase.

StV-6 [Architectural Description] Capabilities [1]


«StandardOperationalActivity»Monitor Health



«StandardOperationalActivity»Find Victim

«StandardOperationalActivity»Track Victim

«StandardOperationalActivity»Transit to SAR Operation

«StandardOperationalActivity»Recover Victim

«StandardOperationalActivity»Provide Medical Assistance

«StandardOperationalActivity»Assist Victim

«MapsToCapability»





«MapsToCapability»«MapsToCapability»




UPDM SAR CV-6CV-6: Capability to Operational Activities Mapping

Mapping between the capabilities required and the operational activities that those capabilities support.

CV-6 with DM2 Markups

Legend:

Assistance

Monitor Health

Search Inform

Track Victim

Transit to SAR Operation

Recover Victim

Provide Medical Assistance

Assist Victim

Recovery

CV-6 [Architectural Description] Capabilities [1]

Find Victim

Capabilities

Whole-part

Activities

CV-6: Capability to Operational Activities Mapping

Mapping between the capabilities required and the operational activities that those capabilities support.

SOV-3 [Architectural Description] SAR Services [2]



«ServiceInterface»Land Search and Rescue Service

«ServiceInterface»Maritime Search and Rescue Service

«Expose» «Expose»

UPDM SAR SvcV-3 SvcV-3a Systems-Services Matrix

Relationships among between systems and services in a given architecture.

SvcV-3b Services-Services Matrix

Relationships among services in a given architecture; can be designed to show relationships of interest, e.g., service-type interfaces, planned vs. existing interfaces, etc.

CV-7 with DM2 Markups CV-7: Capability to Services Mapping

Mapping between capabilities and the services that these capabilities enable.

Land SAR System

Land SAR “Capability” Accessed by Service

Legend:

Capability

Performer supports or provides Capability

Service

Service Description

Part of

Describes

CV-7 [Architectural Description] SAR Services [2]

Land SAR

Maritime SAR

Land Search and Rescue Service

Maritime Search and Rescue

Service

Land Search and Rescue Service Port

Land Search and Rescue Service Port Description

Activities part of CapabiltyActivity

Resource

Conduct Land SAR

Access Land SAR Resources

Land Victims

Measure

Measure Type

99

Percent Rescued

Desired Effect

Activity Changes Resource

PerformerProcess Search

Request Information

Search Request

Rescue

Measure of Desired Effect

Resource Flow (ARO)

APBP

SOV-1 [Architectural Description] SAR Services

«ServiceInterface»Search and Rescue Service



UPDM SAR SvcV-1SvcV-1 Services Interface Description

Identification of services and service items and their interconnections

SvcV-1 (partial) with DM2 Markups

Partial SvcV-1 [Architectural Description] SAR Services

Search and Rescue Service

Maritime Search and Rescue ServiceLand Search and Rescue Service

NOTE 1: A full SvcV-1 would also show, 1) Performers accessed, 2) service and, if necessary, Performer composition, 3) service access and related Performer interfaces and related interface standards and metrics.

Legend:

Services

Subtypes

SvcV-1 Services Interface Description

Identification of services and service items and their interconnections


«Interface»Search Interface


«ServiceInterface»Search and Rescue Service

InitiateSearch (in missingPersonInfo, out searchCaseID)RequestSearchUpdate (in searchCaseID, in status)CancelSearch (in searchCaseID, in reason)

«Interface»Maritime Rescue Interface

RescuePerson (in strandedPersonInfo)

«Interface»Fire Service Interface

RescuePerson (in trappedPerson)

«Interface»Helicopter Service Interface

TransportCasualty (in patientInfo, in transportedTo)

«Interface»Rescue Interface

InitiateRescue (in strandedPersonInfo, out rescueCaseID)

Search Interface

Recue Interface

Maritime Rescue Interface

Helicopter Service Interface

Fire Service Interface

UPDM SAR SvcV-2SvcV-2 Services Communications Description

Services and service items and their related communications laydowns

SvcV-2 with DM2 MarkupsSvcV-2 Services Communications Description

Services and service items and their related communications laydowns

SvcV-2 [Architectural Description] SAR Services [1]

Search SD

Maritime Search and Rescue Service


InitiateSearch

Maritime Rescue SD

RescuePerson

Fire Service SD

RescuePerson

Helicopter SD

TransportCasualty

Rescue SD

strandedPersonInfo

Recue Interface

Makes available descriptions of how to use the S&R Service

missingPersonInfo

searchCaseID

RequestSearchUpdate CancelSearch

searchCaseID searchCaseIDreason

InitiateRescue

rescueCaseID

patientInfotransportedTo

strandedPersonInfo

trappedPerson

Uses descriptions of how to use the different S&R performer types

status

NOTE 1: only shows the descriptions need to link Service Descriptions to Services

Legend:

Services

Subtypes

Activities

Information

Service Descriptions

Resource Flow

Part of






«Expose» «Expose»

UPDM SAR SvcV-3SvcV-3a Systems-Services Matrix




SvcV-3b Services-Services Matrix with DM2 Markups

"depends on" Mar

itim

e SA

R Se

rvic

e

Land

SAR

Ser

vice

Hel

icop

ter

Serv

ice

Mar

itim

e Re

scue

Se

rvic

e

Fire

Ser

vice

Maritime SAR Service 1 2 3 1

Land SAR Service 2 2 1 2

Helicopter Service 2 2 2 1Maritime Rescue Service

3 0 1 1

Fire Service 1 2 1 0

"this"

Degree of dependency of the row services on the column services:0 - none1 - low2 - moderate3 - high

Partial list of services

Legend:

Services

SvcV-3a Systems-Services Matrix




SOV-5 [ServiceFunction] Rescue Person

«ServiceFunction»Rescue Person

«UnmarshallAction»Unmarshall Stranded Person Info

strandedPersonInfo

Reported.

strandedPersonInfo

«ServiceFunctionAction»: Recover Victim

«ServiceFunctionAction»: Reassure Victim

location name

location name

«ServiceFunctionAction»: Apply First Aid

condition

condition

«ServiceFunctionAction»: Transport Victim

locationcondition

«WriteStructuralFeatureAction»Update Condition

objectvalue

«WriteStructuralFeatureAction»Update Location

value object

Updated.

UPDM SAR SvcV-5SvcV-5 Operational Activity to Services Traceability Matrix

Mapping of services (activities) back to operational activities (activities)

SvcV-4 Services Functionality Description with DM2 Markups

SvcV-4 [ServiceFunction] Rescue Person

Unmarshall Stranded Person Info

strandedPersonInfo

(Reported)

strandedPersonInfo

Recover Victim Reassure Victim

namelocation

Apply First AidApply First Aid

condition

Transport Victim

locationcondition

Update Condition Update Location

Legend:

ActivitiesDataAPBP

Service


Resource Flows

Before Afters -- Sequence

(Updated)

SvcV-4 Services Functionality Description

Functions performed by services and the service data flows among service functions (activities)

SvcV-5 with DM2 Markups

Activities Peformed by Services

Activities

Rescue

Recover Victim x x x x x


Provide Medical Assistance x

Search


Find Victim x x

Send Warning Order

Monitor Health x

NOTE 1: Indentation means whole-part

SvcV-5 Operational Activity to Services Traceability Matrix

Mapping of services (activities) back to operational activities (activities)

[Architectural Description] SAR Services [SOV-4a]

Name




Name Text

Driving Record

Swim

First Aid

Danger

Any member involved in the operation of road vehicles must have a clean driving record.

All members of the rescue team must be able to swim.

All members of the rescue team must be able to perform basic first aid.

No member of the search and rescue team should put themselves in unnecessary danger.

Service Interface Service Policy

UPDM SAR SvcV-4a SvcV-4 Services Functionality Description

Functions performed by services and the service data flows among service functions (activities)

SvcV-10a Services Rules Model with DM2 Markups

SAR Description2

Maritime SAR Description2

Land SAR3

Maritime SAR3

Land SAR Description2

Land SAR3

Legend:

Driving RecordAny member involved in the operation of road vehicles must have a clean driving record.

SwimAll members of the rescue team must be able to swim.

First AidAll members of the rescue team must be able to perform basic first aid.

DangerNo member of the search and rescue team should put themselves in unnecessary danger.

SvcV-10a [Architectural Description] SAR Services




Rule constrains the Activities performed by Performers1

Services

Rules

Drive

Swim

Activity Performed By Performer (APBP)1

NOTE 1: A Service is a type of PerformerNOTE 2: The Service Description includes the Rules that will be adhered to. NOTE 3: Means, any Performer that is accessed by the Service.

Provide First Aid

Provide First Aid

Provide First Aid

Avoid Danger

Avoid Danger

Avoid Danger

Performer

Service Description

Activities

Land Search and Rescue Service Port

Whole Part

Maritime Search and Rescue Service Port

Search and Rescue Service Port

SvcV-10a Services Rules Model

One of three models used to describe service functionality - identifies constraints that are imposed on systems functionality due to some aspect of systems design or implementation

AcV-1 [Architectural Description] Enterprise [2]

«ActualProject»SAR Project

startDate2009-09-01 00:00:00

endDate2014-06-01 00:00:00

«IncrementMilestone»Rescue Unit Config 1

endDate2010-01-01 00:00:00

resource«CapabilityConfiguration» Maritime Rescue Unit

«IncrementMilestone»Rescue Unit Config 2

endDate2012-01-01 00:00:00

resource«CapabilityConfiguration» Maritime Rescue Unit V2

«OutOfServiceMilestone»Rescue Unit Config 1 OOS

endDate2012-01-01 00:00:00

resource«CapabilityConfiguration» Maritime Rescue Unit

«OutOfServiceMilestone»Rescue Unit Config 2 OOS

endDate2014-06-01 00:00:00

resource«CapabilityConfiguration» Maritime Rescue Unit V2

UPDM SAR PV-1 PV-1: Project Portfolio Relationships

Organizational structures needed to manage a portfolio of projects and shows dependency relationships between the organizations and projects.

PV-2 with DM2 Markups

PV-2 [Architectural Description] Enterprise [2]

SAR Project

Individual Project

Activities

Performers (Resource)

Resource Produced By Activity (ARO)

Develop MRU

Co

nd

uct

IO

C f

or

MR

U

Sustain MRU

Pla

ce M

RU

Ou

t o

f S

ervi

ce

Develop MRU V2

Co

nd

uct

IO

C f

or

MR

U V

2

Sustain MRU V2

Pla

ce M

RU

V2

Ou

t o

f S

ervi

ce

Maritime Rescue Unit V2

Maritime Rescue Unit

2009-09-01 00:00:00

2014-06-01 00:00:00


MeasureTypes

Temporal Whole Part

Measures

startDate

endDate

Temporal Boundary

2010-01-01 00:00:00

IncrementMilestoneDate

2012-01-01 00:00:00

OutOfServiceMilestoneDate

2014-06-01 00:00:00

OutOfServiceMilestoneDate

2012-01-01 00:00:00

IncrementMilestoneDate

Develop MRU

SAR Project

Partial Interpretation as

GANNT

PV-2: Project Timelines

A timeline perspective on programs or projects, with the key milestones and interdependencies

Sustain MRU

Develop MRU V2

Sustain MRU V2

time

responsibleFor«Project» SAR Project : Development Project

«ActualOrganization»Department of Transport




Legend:

SAR Project

Department of Transportion

Development Project

Activity

Individual Organization

“responsibleFor”

Project

Subtypes

Activity Performed by Performer

Activity part of Project

Be Responsible for SAR Project

PV-1: Project Portfolio Relationships


AcV-1 [Architectural Description] Acquisition View

«Project»Development

«ProjectMilestone»Development Milestone

themesDoctrine : DOTMLPFOrganization : DOTMLPFTraining : DOTMLPFMateriel : DOTMLPFLogistics : DOTMLPF

1

* milestone

0..1

* subProject




Legend:

PV-1 [Architectural Description] Acquisition View

Development Project

Conduct Development MS A Review

Review Doctrine @ MS AReview Organization @ MS AReview Training @ MS AReview Materiel @ MS AReview Leadership & Edu @ MS AReview Personnel @ MS AReview Facilities @ MS A

Activities

Project

Conduct Project

Milestone Review

NOTE 1: The UPDM “subproject” aggregation was metadata, saying a Development Project has parts. It is not view data.NOTE 2: A PV-1 should show the milestones, not just say there are many.

Subtype of

Part-Of

Pre-MS A Phase Pre-MS B Phase Pre-MS C Phase

Conduct Development MS B Review

Review Doctrine @ MS BReview Organization @ MS BReview Training @ MS BReview Materiel @ MS BReview Leadership & Edu @ MS BReview Personnel @ MS BReview Facilities @ MS B

Conduct Development MS C Review

Review Doctrine @ MS CReview Organization @ MS CReview Training @ MS CReview Materiel @ MS CReview Leadership & Edu @ MS CReview Personnel @ MS CReview Facilities @ MS C

Temporal whole-part

Before-after

PV-1: Project Portfolio Relationships


AcV-1 [Architectural Description] Projects

«ActualProject»Emergency Response Enhancement

startDate2009-05-15 00:00:00

endDate2015-05-15 00:00:00

«ActualProjectMilestone»Project Start

endDate2009-09-01 00:00:00

«ActualProjectMilestone»Capability Assessment Complete

endDate2009-10-01 00:00:00

«ActualProjectMilestone»Requirements Complete

endDate2009-12-01 00:00:00

«ActualProjectMilestone»Start Phase 1

endDate2010-01-01 00:00:00

«ActualProjectMilestone»Start Phase 2

endDate2012-12-01 00:00:00

«ActualProjectMilestone»Project Complete

endDate2014-06-01 00:00:00

«ActualProject»SAR Project

startDate2009-09-01 00:00:00

endDate2014-06-01 00:00:00

«ActualProject»Flood Response

subProject

subProject



Legend:FFP PV-2 Fusion [Architectural Description] Projects

Enhance Emergency Response

2009-05-15 00:00:00

2015-05-15 00:00:00

Start Project

endDate2009-09-01 00:00:00

Complete Capability Assessment

endDate2009-10-01 00:00:00

Requirements Complete

endDate2009-12-01 00:00:00

Start Phase 1

endDate2010-01-01 00:00:00

Start Phase 2

endDate2012-12-01 00:00:00

CompleteProject

endDate2014-06-01 00:00:00

Execute SAR Project

Flood Response


Individual Project

MeasureTypes

Temporal Whole Part

Measures

startDate

endDate

Assess Capability Develop Requirements Conduct Phase 1 Conduct Phase 2

Temporal Boundary

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

bdd [Package] SysML Value Type Definitions

«valueType»Coverage

dimensionArea

unitSquareKilometers

«valueType»Weather Conditions

unitWeather Severity Index

«valueType»Elapsed Time

dimensionTime

unitHours

«unit»SquareKilometers

«unit»Weather Severity Index

«unit»Hours

«dimension»Wave Height

«unit»Terrain Index

«valueType»Sea State

dimensionWave Height

unitMeter

«valueType»Terrain Type

unitTerrain Index

UPDM SAR metrics

UPDM SAR Conditions and metricspar [block] Maritime SAR

MaritimeSAR.targetMetrics.-

SeaConditions : Sea State


findTime :Elapsed Time


persistence : Elapsed Time

MaritimeSAR.targetMetrics.-weatherConditions : WeatherConditions

MaritimeSAR.targetMetrics.-searchCoverage :

Coverage

area : Coverage findTime : Elapsed Time

seaConditions : Sea State

persistence : Elapsed Time

weatherConditions : WeatherConditions

searchCoverage : Coverage

MaritimeSAR.targetMetrics.area

Coverage: Coverage

[Architectural Description] System View [SV-7]

Resource Actual Measurement Set

Type Name 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 Hours Time

searchCoverage 400 SquareKilometers Area

weatherConditions Heavy Rain Weather Severity Index

«CapabilityConfiguration» Maritime Configuration V2 Final Values

seaConditions sea state 8 Meter Wave Height





weatherConditions Stormy Weather Severity Index

«CapabilityConfiguration» Maritime Rescue Unit Initial Values

seaConditions Sea State 6 Meter Wave Height





weatherConditions Heavy Rain Weather Severity Index

«CapabilityConfiguration» Maritime Rescue Unit V2 Final Values

seaConditions sea state 8 Meter Wave Height





weatherConditions Stormy Weather Severity Index

UPDM SAR SV-7

SV-7 [Architectural Description] System View

«CapabilityConfiguration»Maritime Configuration

actualMeasurements«ActualMeasurementSet» Initial Values

«CapabilityConfiguration»Maritime Rescue Unit

actualMeasurements«ActualMeasurementSet» Initial Values

«CapabilityConfiguration»Maritime Configuration V2

actualMeasurements«ActualMeasurementSet» Final Values

«CapabilityConfiguration»Maritime Configuration V2

actualMeasurements«ActualMeasurementSet» Final Values

UPDM SAR SV-7

«Organization»Maritime Rescue Team

usedFunctions«Function» SendMessage«Function» ReceiveMessage«Function» BroadcastMessage

usedFunctions«Function» RecoverVictim

«PostRole»Rescue Swimmer : MRT Swimmer

«PostRole»Radio Operator : MRT Communicator

Roles X Functions

Markup Standards

MeasureType Names (definitions not shown)

NOTE 1: There is a part-of for each Sea State valueNOTE 2: These will be ascribed to each Capability and providing Performer phases as “required”, “actual”, “initial” and “final”.

Legend:

MeasureTypes

Subtypes

Part-Of

Legend:

Measure

NOTE 1:

Subtypes

Part-Of

Subtypes