Exemplar Series # 1 Interpretation of UPDM 1.0 SAR Diagrams in DoDAF 2.0 / DM2 Concepts. Extracts for DoD EA Conference May 2010

Transcription

1 Exemplar Series # Interpretation of UPDM.0 SAR Diagrams in DoDAF 2.0 / DM2 Concepts Extracts for DoD EA Conference May 200 DoDAF Development Team

2 Briefing Structure The OMG UPDM Team developed examples of the views as part of UPDM.0. It is called Sample Problem and is Annex C in the UPDM.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 ( Briefing format. A UPDM diagram will be shown first, in it s native form from UPDM.0 Annex C. Blue background. 2. Then DM2 annotated version of the same diagram will be shown. White background.

3 UPDM SAR OV-2 OV-2: Operational Connectivity Description Operational connectivity and resource flow needlines OV-2 [Architectural Description] Nodes «Node» Search Really s/b Search Node (SN) WO : warningorder «Needline» «Node» Place of Safety Tsk : tasking «Needline» «Needline» DS : distresssignal Stat : status «Needline» «Node» Rescue DS : distresssignal «Needline» «Node» Person in Distress «Needline» «Needline» Ctrl : control DS : distresssignal Rqst : request Tsk : tasking «Needline» «Needline» «Node» SAR Asset Controller Rqst : request «Needline» «Node» Tactical C2 TI : trackinfo «Needline» «Node» Monitoring

4 OV-2 with DM2 Markups OV-2 [Architectural Description] Organizational Interactions OV-2: Operational Connectivity Description Operational connectivity and resource flow needlines Bounding box means Resource at Location Legend: Location Type Search Org Type WO : warningorder Place of Safety PoS Org Type PersonType Organization Types Tsk : tasking Stat : status Rescue Org Type DS : distresssignal Ctrl : control DS : distresssignal Person in Distress Resource Flows Information (Resource) Consume (Activity) 2 Produce (Activity) 2 APBP Rqst : request Tsk : tasking DS : DistressSignal SAR Asset Controller Rqst : request Tactical C2 Org Type TI : trackinfo Monitoring Org Type Receive Distress Signal NOTE. Should generally not be shown in OV-2 unless an important constraint, i.e., not within the solution trade space. NOTE 2: 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.

5 Fit-for-Purpose OV-2 with SV- Composite OV-2 [Architectural Description] Organizational Interactions Bounding box means Resource at Location Legend: Location Type Search Org Type WO : warningorder Place of Safety PoS Org Type PersonType Organization Types Resource Flows Tsk : tasking Rqst : request Stat : status Rescue Org Type Tsk : tasking DS : distresssignal Boat Radio Communications System 2 DS : distresssignal Ctrl : control speak Person in Distress key DS : keydistresssignal Boat Radio2 DS : voicedistresssignal Information (Resource) Consume (Activity) Produce (Activity) System Materiel SAR Asset Controller Rqst : request Tactical C2 Org Type TI : trackinfo Monitoring Org Type

6 UPDM SAR OV-5 OV-5b: Activity Model Capabilities, activities (operational activities), relationships among activities, inputs, and outputs; overlays can show cost, performers or other pertinent information OV-5 [OperationalActivity] Search Search Reported Location Reported Condition «NodeRole» PiD: Person in Distress «OperationalActivityAction» : Send Distress Signal distresssignal «Node» : Search and Rescue «NodeRole» SN: Search «NodeRole» RN: Rescue distresssignal «OperationalActivityAction» : Receive Distress Signal distresssignal «OperationalActivityAction» : Receive Distress Signal «OperationalActivityAction» : Send Warning Order warningorder «OperationalActivityAction» : Provide Medical Assistance location «OperationalActivityAction» : Find Victim condition «OperationalActivityAction» : Recover Victim location condition «OperationalActivityAction» : Monitor Health «NodeRole» PoS: Place of Safety warningorder «OperationalActivityAction» : Process Warning Order Updated Condition Updated Location «OperationalActivityAction» : Transit to SAR Operation

7 FFP OV-5b/6c Hybrid Legend: OV-5b: Activity Model OV-6c: Event-Trace Description Organization Types Capabilities, activities (operational activities), relationships among activities, inputs, and outputs; overlays can show cost, performers or other One of pertinent three models information used to describe activity (operational activity) - traces actions in a scenario or sequence of events OV-5 [OperationalActivity] Search Search Activities Information Reported Location Reported Condition APBP Person In Distress Send Distress Signal distresssignal Part-Of Resource Flow Before-After Search Receive Distress Signal Send Warning Order Find Victim Monitor Health Search and Rescue Rescue Receive Distress Signal warningorder Provide Medical Assistance Recover Victim Place of Safety Org Type Process Warning Order Transit to SAR Operation NOTE : Do not have to be modeled Updated Condition Updated Location

8 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 [Node] Search / / Waiting for Distress Signal do : Monitor for Distress Signals receivedistresssignal/ Send Warning Order searchcancelled/ [No Assistance required]/ Searching for Victim do : Track Victim do : Find Victim [Victim Found]/ [Assistance Required]/ Monitoring Victim do : Monitor Health [Victim Stable]/ Transfer to Rescue Team do : Transport Victim [Victim Secure]/

9 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 OV-6b Search The distress event (aka near-zero duration Activity in DoDAF 2) / / Wait for Distress Signal do : Monitor for Distress Signals do: receivedistresssignal do: Send Warning Order Warning Order NOTE : Bounding boxes are temporal parts Search Cancelled/ Search for Victim do : Track Victim do : Find Victim [Victim Found]/ [No Assistance required]/ Determine if assistance is required [Assistance Required]/ Legend: Activities Monitor Victim do : Monitor Health Information Part-Of Resource Flow and Before-After [Victim Stable]/ Transfer to Rescue Team do : Transport Victim [Victim Secure]/

10 UPDM SAR DIV-2 DIV-2: Logical Data Model Documentation of the data requirements and structural business process rules (In DoDAF V.5, this was the OV-7) OV-7 [Logical Data Model] Logical Data Model representedby «InformationElement» control * location «EntityItem» Search Object name : String registration : String tonnage : Integer color : String markings : String superstructure : String characteristics : String owneroroperator : String personsonboard : Integer emergencyequipmentcarried : String objects representedby «InformationElement» warningorder representedby «InformationElement» status * * «EntityItem» Last Known Position latitude : String longitude : String time : String sourceofreport : String * * «EntityItem» Search Area waypoints : String activationtime : String duration : String driftdirection : String driftspeed : Integer commencesearchpoint : String operationalarea * «EntityItem» SAR Operation casename : String casenumber : String taskingauthority : String * «EntityItem» SearchStatus status : String * location representedby «InformationElement» trackinfo «InformationElement» distresssignal representedby «InformationElement» tasking «InformationElement» control assetassignments «EntityItem» Assignment description : String * «EntityItem» StrandedPersonInfo name : String condition : String representedby «InformationElement» request * person

11 DIV-2 with DM2 Markups DIV-2: Logical Data Model Documentation of the data requirements and structural business process rules (In DoDAF V.5, this was the OV-7)

12 UPDM SAR SV- SV- Systems Interface Description Identification of systems and system items and their interconnections

13 SV- with DM2 Markups SV- [Performer] Maritime Rescue Unit SV- Systems Interface Description Maritime Rescue Unit Identification of systems and system items and their interconnections Maritime Rescue Team Propusion and Rudder Control Equipment Boat Receive BoatInstruction BoatInstruction MRT Boat Send BoatInstruction MRT Boat Driver Lighting Device Receive BeaconInstruction BeaconInstruction Send BeaconInstruction MRT Searcher Communication Device Receive RadioInstruction RadioInstruction Send RadioInstruction MRT Communicator Life Saving Device Receive LifePreserverInstruction LifePreserverInstruction Send LifePreserverInstruction MRT Swimmer Aircraft Receive AircraftInstruction AircraftInstruction Helo Send AircraftInstruction MRT Helo Pilot Legend: Systems Activities Performer Information PersonType Organization Type ResourceFlow Whole - Part APBP

14 UPDM SAR SV-7 SV-7 Systems Performance Parameters Matrix Performance characteristics of Systems Model elements for the appropriate time frame(s) Parameter ID System/Element Performance Requirement Metric Measure H. Voice Radio Transmitter Transmission rate 2 GB Hardware H 2. Voice Radio Receiver Gain 60 db H 2.2 Signal to Noise Ratio 20 db H 3. Signal Processor Comms Channel Bandwidth Support 2 GB S.2 Status Alerting Min. status change alert accuracy 500 meters Software S.3 Min. alert response time 30 seconds

15 SV-7 with DM2 Markups SV-7 Systems Performance Parameters Matrix Performance characteristics of Systems Model elements for the appropriate time frame(s) System Measure association Measure Measure Type association Legend: Measure Types Measure Type units Measures Systems System Measure Type Measure association Name 3 H. System Measure Type Measure Measure Type units Hardware Voice Radio Transmitter Transmission rate 2 GB H 2. Voice Radio Receiver Gain 60 db H 2.2 Signal to Noise Ratio 20 db H 3. Signal Processor Comms Channel 2 GB Bandwidth Support Header means Systems below principally consist of this Materiel type Materiel (type) Software S.2 Status Alerting (component) Min. status change alert accuracy 500 meters S.3 Min. alert response time 30 seconds NOTE : 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.

16 UPDM SAR CV- CV-: Vision Overall vision for transformational endeavors, provides a strategic context for the capabilities described, and provides a high-level scope. StV- [Architectural Description] Enterprise [] goals «EnterpriseGoal» Fulfill International Obligations visions «EnterpriseVision» UK SAR Vision «WholeLifeEnterprise» Search and Rescue startdate :00:00 enddate :00:00 goals «EnterpriseGoal» Maintain UK SAR Responsibility visions «EnterpriseVision» UK SAR Vision Temporal Part Temporal Part2 «EnterprisePhase» Phase «EnterprisePhase» Phase 2 startdate :00:00 enddate :00:00 startdate :00:00 enddate :00:00 «EnterpriseVision» UK SAR Vision «EnterpriseGoal» «requirement» Fulfill International Obligations exhibits «Capability» Assistance «Capability» Recovery «Capability» Search exhibits «Capability» Assistance «Capability» Recovery «Capability» Search «EnterpriseGoal» «requirement» Maintain UK SAR Responsibility

17 Partial CV- with DM2 Markups CV- SAR Vision CV-: Vision US SAR Vision Overall vision for transformational endeavors, provides a strategic context for the capabilities described, and provides a high-level scope. International Obligations Fulfilled Search and Rescue US SAR Responsibility Maintained SAR Performer SAR Phase SAR Phase I Performer :00:00 startdate :00:00 enddate SAR Phase 2 Performer SAR Phase :00:00 startdate :00:00 enddate :00:00 startdate :00:00 enddate Assist Recover Search Legend: Visions Capabilities Resource 6 Activities Performer 2 Measures MeasureTypes Activities part of Capabilty Whole Part Temporal Whole Part Measure of Temporal boundary Capability of Performer Desired Effects NOTE : 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: Performer is probably an aggregate (wholeparts), aka Capability Configuration NOTE 3: Whole Capability lasts 54 months NOTE 4: Phase I lasts 35 months NOTE 5: Phase II lasts 9 months NOTE 6: Desired effects are states of Resources

18 UPDM SAR CV-2 CV-2: Capability Taxonomy A hierarchy of capabilities, specifies all the capabilities that are referenced throughout one or more architectures. StV-2 [Architectural Description] Capabilities «Capability» SAR actualmeasurements «ActualMeasurementSet» Required Values «Capability» Maritime SAR «Capability» Land SAR

19 Partial CV-2 with DM2 Markups CV-2: Capability Taxonomy A hierarchy of capabilities, specifies all the capabilities that are referenced throughout one or more architectures.

20 UPDM SAR CV-4 CV-4: Capability Dependencies Dependencies between planned capabilities and defines logical groupings of capabilities. StV-4 [Architectural Description] Capabilities «Capability» SAR Asst Inf MilC2 SC2 «Capability» Assistance «Capability» Inform «Capability» Military C2 «Capability» SAR C2 DSM Srch Rec «Capability» Distress Signal Monitoring «Capability» Search «Capability» Recovery

21 Partial CV-2 with DM2 Markups CV-2: Capability Taxonomy A hierarchy of capabilities, specifies all the capabilities that are referenced throughout one or more architectures. CV-2 [Architectural Description] Capabilities SAR NOTE 2: Cardinalities mean the SAR Capability has one and only one Assistance Capability and viceversa Assistance Inform Military C2 SAR C2 Distress Signal Monitoring Legend: Capabilities Search Recovery Whole-part with cardinalities (NOTE 2) NOTE : 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.

22 UPDM SAR CV-4 StV-4 [Capability] SAR Capability CV-4: Capability Dependencies Dependencies between planned capabilities and defines logical groupings of capabilities. «Capability» SAR DSM : Distress Signal Monitoring Inf : Inform MIC2 : Military C2 SC2 : SAR C2 Srch : Search Asst : Assistance Rec : Recovery

23 Partial CV-4 with DM2 Markups CV-4 [Capability] SAR Capability CV-4: Capability Dependencies Dependencies between planned capabilities and defines logical groupings of capabilities. SAR Distress Signal Monitoring Inform dependson DSM Inform (communicate) SAR C2 depends-on DSM SAR C2 SAR C2 depends-on Military C2 Military C2 depends-on Inform Military C2 Search depends-on SAR C2 Assistance depends-on SAR C2 Recovery depends-on SAR c2 Search Assistance Recovery Legend: Capabilities Whole-part (NOTE 2) Desired Effect Whole-part (NOTE 3) NOTE : 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) SAR NOTE 3: Means, the desired effect of the whole capability includes the desired effects of the parts.

24 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. Organizational Resources

25 Partial CV-5 with DM2 Markups CV-5: Capability to Organizational Development Mapping The fulfillment of capability requirements, shows the planned capability deployment and interconnection for a particular Capability Phase. [Architectural Description] Capabilities [CV-5] Assistance Inform Recovery Search RNLI MRU V2 Maritime & Coastguard Agency Legend: Capabilities Performer Organizations Performer that enables / supports the Capability Organizations that perform the Activities that produce the Performers the realize the Capability Phases NOTE : 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.

26 UPDM SAR SvcV-3 SvcV-3a Systems- Services Matrix SvcV-3b Services- Services Matrix Relationships among between systems and services in a given architecture. 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. SOV-3 [Architectural Description] SAR Services [2] «Capability» Land SAR «Capability» Maritime SAR «Expose» «Expose» «ServiceInterface» Land Search and Rescue Service «ServiceInterface» Maritime Search and Rescue Service

27 CV-7 with DM2 Markups CV-7: Capability to Services Mapping Mapping between capabilities and the services that these capabilities enable. CV-7 [Architectural Description] SAR Services [2] Percent Rescued 99 Land SAR Maritime SAR Legend: Capability Desired Effect Land Victims Rescue Conduct Land SAR Land Search and Rescue Service Access Land SAR Resources Process Search Request Search Request Land SAR Capability Accessed by Service Land SAR System Maritime Search and Rescue Service Land Search and Rescue Service Port Land Search and Rescue Service Port Description Service Activity Resource Service Description Measure Measure Type Performer Information Part of Activities part of Capabilty Measure of Desired Effect Performer supports or provides Capability Describes Activity Changes Resource Resource Flow (ARO) APBP

28 UPDM SAR SvcV-2 SvcV-2 Services Communications Description Services and service items and their related communications laydowns SOV-2 [Architectural Description] SAR Services [] «Interface» Search Interface «Interface» Maritime Rescue Interface InitiateSearch (in missingpersoninfo, out searchcaseid) RequestSearchUpdate (in searchcaseid, in status) CancelSearch (in searchcaseid, in reason) RescuePerson (in strandedpersoninfo) Search Interface Maritime Rescue Interface «Interface» Fire Service Interface RescuePerson (in trappedperson) «ServiceInterface» Search and Rescue Service «ServiceInterface» Maritime Search and Rescue Service Fire Service Interface Recue Interface Helicopter Service Interface «Interface» Rescue Interface InitiateRescue (in strandedpersoninfo, out rescuecaseid) «Interface» Helicopter Service Interface TransportCasualty (in patientinfo, in transportedto)

29 SvcV-2 with DM2 Markups SvcV-2 [Architectural Description] SAR Services [] SvcV-2 Services Communications Description Services and service items and their related communications laydowns missingpersoninfo InitiateSearch searchcaseid Search SD searchcaseid RequestSearchUpdate status searchcaseid reason CancelSearch Maritime Rescue SD strandedpersoninfo NOTE : only shows the descriptions need to link Service Descriptions to Services Makes available descriptions of how to use the S&R Service RescuePerson Uses descriptions of how to use the different S&R performer types Legend: Fire Service SD Services Search and Rescue Service Maritime Search and Rescue Service trappedperson Activities Information RescuePerson Service Descriptions Recue Interface Subtypes Rescue SD Helicopter SD Resource Flow Part of strandedpersoninfo InitiateRescue patientinfo transportedto TransportCasualty rescuecaseid

30 UPDM SAR SvcV-3 SvcV-3a Systems- Services Matrix SvcV-3b Services- Services Matrix Relationships among between systems and services in a given architecture. 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. SOV-3 [Architectural Description] SAR Services [2] «Capability» Land SAR «Capability» Maritime SAR «Expose» «Expose» «ServiceInterface» Land Search and Rescue Service «ServiceInterface» Maritime Search and Rescue Service

31 SvcV-3b Services-Services Matrix with DM2 Markups SvcV-3a Systems- Services Matrix SvcV-3b Services- Services Matrix Relationships among between systems and services in a given architecture. 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. Maritime SAR Service Land SAR Service Helicopter Service Maritime Rescue Service Fire Service Maritime SAR Service 3 3 Land SAR Degree of Service 3 2 Helicopter services: Service 3 Maritime Rescue Service Fire Service interaction between 0 - none - low 2 - moderate 3 - high (symmetric matrix) Legend: Services Partial list of services

32 UPDM SAR SvcV-5 SvcV-5 Operational Activity to Services Traceability Matrix Mapping of services (activities) back to operational activities (activities) SOV-5 [ServiceFunction] Rescue Person Reported. Updated. «ServiceFunction» Rescue Person strandedpersoninfo strandedpersoninfo «UnmarshallAction» Unmarshall Stranded Person Info location name condition location name condition «ServiceFunctionAction» : Recover Victim «ServiceFunctionAction» : Reassure Victim «ServiceFunctionAction» : Apply First Aid «ServiceFunctionAction» : Transport Victim condition location object value «WriteStructuralFeatureAction» Update Condition value object «WriteStructuralFeatureAction» Update Location

33 SvcV-4 Services Functionality Description with DM2 Markups SvcV-4 Services Functionality Description Functions performed by services and the service data flows among service functions (activities) SvcV-4 [ServiceFunction] Rescue Person (Reported) Maritime Search and Rescue Service strandedpersoninfo Unmarshall Stranded Person Info location name condition Recover Victim Reassure Victim Apply First Aid Transport Victim condition location Update Condition Update Location Legend: Data APBP Service Activities Resource Flows Before Afters -- Sequence strandedpersoninfo (Updated)

34 SvcV-5 with DM2 Markups SvcV-5 Operational Activity to Services Traceability Matrix Mapping of services (activities) back to operational activities (activities) Activities Peformed by Services Activities Rescue NOTE : Indentation means whole-part Unmarshall Stranded Person Info Recover Victim Reassure Victim Apply First Aid Transport Victim Update Location Recover Victim x x x x x Receive Distress Signal Provide Medical Assistance x Search Receive Distress Signal Find Victim x x Send Warning Order Monitor Health x

35 UPDM SAR SvcV-4a SvcV-4 Services Functionality Description Functions performed by services and the service data flows among service functions (activities) [Architectural Description] SAR Services [SOV-4a] Service Interface Service Policy Name Name Text Land Search and Rescue Service Maritime Search and Rescue Service Search and Rescue Service 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.

36 SvcV-0a Services Rules Model with DM2 Markups SvcV-0a 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

37 UPDM SAR PV- PV-: Project Portfolio Relationships Organizational structures needed to manage a portfolio of projects and shows dependency relationships between the organizations and projects. AcV- [Architectural Description] Enterprise [2] «ActualProject» SAR Project startdate :00:00 enddate :00:00 «IncrementMilestone» Rescue Unit Config enddate :00:00 resource «CapabilityConfiguration» Maritime Rescue Unit «IncrementMilestone» Rescue Unit Config 2 enddate :00:00 resource «CapabilityConfiguration» Maritime Rescue Unit V2 «OutOfServiceMilestone» Rescue Unit Config OOS enddate :00:00 resource «CapabilityConfiguration» Maritime Rescue Unit «OutOfServiceMilestone» Rescue Unit Config 2 OOS enddate :00:00 resource «CapabilityConfiguration» Maritime Rescue Unit V2

38 PV-2 with DM2 Markups PV-2: Project Timelines A timeline perspective on programs or projects, with the key milestones and interdependencies PV-2 [Architectural Description] Enterprise [2] SAR Project startdate :00:00 Individual Project Temporal Boundaries System Performers Measures Measure Type enddate :00:00 Bounding box means the temporal boundaries are temporal parts of the Project Rescue Unit Config IncrementMilestoneDate :00:00 Upper part of bounding box means the temporal boundaries is a temporal part of the System, Lower part of bounding box means the System??? Performer (aka capability configuration ) that enables / supports the SAR sub-capabilities: Assistance, Recovery, etc. Maritime Rescue Unit Temporal parts of the Systems (Resources) that are produced by the Activities that are part of the Project Rescue Unit Config OutOfServiceMilestoneDate :00:00 Maritime Rescue Unit Rescue Unit Config 2 IncrementMilestoneDate :00:00 Maritime Rescue Unit V2 Rescue Unit Config 2 OutOfServiceDate :00:00 Maritime Rescue Unit V2 SAR Project Partial Interpretation as GANNT IOC? Rescue Unit Config Rescue Unit Config Rescue Unit Config 2

39 UPDM SAR PV- PV-: Project Portfolio Relationships Organizational structures needed to manage a portfolio of projects and shows dependency relationships between the organizations and projects.

40 PV- with DM2 Markups PV-: Project Portfolio Relationships Organizational structures needed to manage a portfolio of projects and shows dependency relationships between the organizations and projects. Department of Transportion Legend: Development Project responsiblefor Activity Individual Organization Be Responsible for SAR Project Project Subtypes SAR Project Activity Performed by Performer Activity part of Project

41 UPDM SAR PV- PV-: Project Portfolio Relationships Organizational structures needed to manage a portfolio of projects and shows dependency relationships between the organizations and projects.

42 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 FFP PV-2 Fusion [Architectural Description] Projects Enhance Emergency Response startdate :00:00 enddate :00:00 Legend: Individual Project Measures MeasureTypes Execute SAR Project Flood Response Temporal Boundary Measure of Temporal boundary Temporal Whole Part Start Project Complete Project Assess Capability Develop Requirements Conduct Phase Conduct Phase 2 enddate :00:00 enddate :00:00 Complete Capability Assessment Requirements Complete Start Phase Start Phase 2 enddate :00:00 enddate :00:00 enddate :00:00 enddate :00:00