WF11: Create Mission Profiles

Pre-requisites

• Mission Parameters: Mission details including Mission phases/segments.
• FBD Model: System model containing components (see WF03-05).
• Unit Life Configurations: Model items configured to accept Unit Life input (see WF41).

Detailed Descriptions (numbered steps)

1. Open 'Mission Profile Definition' under 'Modelling' in the menu or through the Project Explorer (via right-click context menu on the System item).
2. Select New button to create a mission profile.
3. Enter mission profile details & attach documents/image files.
4. Select the Plus icon to open mission parameter dialog. Enter parameter name, unit & initial value. Selected parameters are shown in the Mission Profile graph.
5. Create Phases & Segments to show in time profile graph by clicking green cube icon or yellow cube icon respectively – require name, duration, description & parameter values.
6. Create Specialized Phases via green plus icon. Each require a name, duration, description and selection of the associated phases and segments.
7. Create Operational Conditions via green plus icon (name, description, associated phases/segments/specialized phases). Create Environmental Conditions via green plus icon (name, environment, env. characteristics, associated phases/segments/specialized phases).
8. Create Mission Events via green plus icon. Each require a name, description, type, occurrence, justification and selection of the phases and segments, specialized phases, mission conditions.
9. Create mission success metrics via green plus icon. Each require a name, success criteria and association to one or more system flow properties.
10. Associate functional profile of each system function to phases. Upper/lower flow property limits are entered, and functional importance terms are selected.
11. Configure duty cycles for each model item for a defined phase or segment.
12. Configure unit life accrual for each model item which has a unit life failure distribution selected.
13. Mission Profiles for the project, representing the use cases of the system, has been created.

Fields referenced in the diagram

• Enter MPD Details: Mission Profile Details, Documents & Images
• Create Mission Parameter(s): Parameter Name(s), Parameter Units, Initial Value(s)
• Create Mission Phases and Segments: Mission Phases, Mission Segments, Phase/Segment detail
• Create Specialized Phases: Specialized Phases, Assoc. Phases/Segments
• Create Mission Conditions: Operational Conditions, Environmental Conditions, Assoc. Phases/Segments, Assoc. Specialized Phases
• Create Mission Events: Mission Events, Assoc. Phases/Segments, Assoc. Specialized Phases, Assoc. Mission Conditions
• Create Mission Success Metric(s): Mission Objectives, Success Criteria, Assoc. Flow Properties
• Define Functional Profile: Upper & Lower Limits, Importance Ranking
• Configure Duty Cycles: Duty Cycles
• Configure Unit Life Accrual: Number of Units

Decision points

• All Mission Profiles Defined? — No → loop back to Create New Mission Profile; Yes → continue.
• Create Mission Groups? — Yes → Create Mission Profile Groups (see WF69); No → Mission Defined.

Outputs

• MEFL/Mission Profile Report: Using the MADE Report Wizard, a Mission Effective Function List (MEFL) or Mission Profile report can be generated for a selected mission profile.

Screenshot walkthrough (captions/labels extracted)

Step 1: Open Mission Profile Definition

• 'Modeling' menu: New Connection, New Item, New RBD Group, Activate Failure Diagram, Hazard Diagram, Functional Diagram, Mission Profile Definition (highlighted), Requirements, System Environment, Unit Life Parameter, System Model, Bond Graph, Failure Diagram, Functions, ABD Model, RBD Model, Maintenance Actions, System Maintenance Editor, Environment Library, Sensor Library, Annotations.
• Right-click context menu on System item in Project Explorer: New > System Model, Failure Diagram, Functions; Requirements, Functional Diagram, Mission Profiles (highlighted, tooltip "Open Mission Profile Definitions for the System"), Maintenance Actions...; Cut/Copy/Paste, Delete, End Effect Item, Response Paths, Save to Library, Advanced Properties.

Step 2: Create New Mission Profile

• "Mission Profile Definition" tab: "Overview / Management". "Mission Profile Manager" panel with buttons New, New Group, Import, Open, Copy, Delete, and empty Type/Name/Modified table. "Mission Profile Summary" panel: Name field, checkbox "Active Mission Profile", Description text area, collapsible sections "Related Documents and Images" and "Mission Profile - Parameters Chart" (showing "No Mission Parameters have been selected to be graphed.").

Step 3: Enter MPD Details

• "Mission Profile Definition - Regular Trip" with left nav: Overview/Management, Regular Trip (Phases and Segments > Specialized Phases, Mission Conditions, Mission Events, Mission Success Metrics, Functional Profile, Duty Cycles > Unit Life Configuration). "Mission Profile Details" panel (highlighted box): Name "Regular Trip", Duration "0sec", Σ total "N/A", Mission Cycles "1.00", Description field. "Related Documents and Images": Documents and Images tables each with Attachment/Date added columns and add/remove/import/export icon buttons. "Mission Parameters" table: Graph, Σ, Name, Units, Initial Value columns (empty), with add/copy/move-up/move-down/delete icon buttons. "Mission Profile - Parameters Chart" showing "No Mission Parameters have been selected to be graphed."

Step 4: Create Mission Parameter(s)

• "Create Mission Parameter" dialog: "Enter the details of the Mission Parameter." Fields: Name "Distance", Units "Kilometers", Initial value "0.00". Checkboxes: "Include in Mission Profile Graph" (checked), "Set this Mission Parameter as the Aggregate Parameter" (checked). Buttons: OK, Cancel.
• "Mission Parameters" table populated with row: Graph (checked), Σ (radio selected), Name "Distance", Units "Kilometers", Initial Value "0.00". "Mission Profile - Parameters Chart" line graph plotting Distance (Kilometers) rising from 0.00 at "Initial (0h)" through Ignition (0.001h) 0.00, Acceleration (0.018h) 0.50, Cruise (0.268h) 10.50, Turning (0.285h) 11.00, Highway A1 (0.785h) 90.00, Highway B2 (1.035h) 100.00, Mountain Terrain (1.285h) 111.00, Deceleration (1.301h) 111.00, Shut-down (1.303h) 112.00. X-axis label "Phase or Segment (Elapsed Time)".

Step 5: Create Mission Phases and Segments

• "Time Profile Graph" showing timeline from t=0hr through t=1hr18min10sec across Phase/Segments: 1: Start-up (5sec, with segment 1.1: Ignition 5sec), 2: Acceleration (1min), 3: Cruise (15min), 4: Turning (1min), 5: Cruise 2 (1hr, with segments 5.1: Highway [45min: 5.1.1 Highway A1 30min, 5.1.2 Highway B2 15min] and 5.2: Mountain Terrain 15min), 6: Deceleration (1min), 7: Shut-down (5sec).
• "Mission Phases and Segments" table (ID/Code/Name/Duration) listing: 1 Start-up 5sec (1.1 Ignition 5sec), 2 Acceleration 1min, 3 Cruise 15min, 4 Turning 1min, 5 Cruise 2 1hr (5.1 Highway 45min [5.1.1 Highway A1 30min, 5.1.2 Highway B2 15min], 5.2 Mountain Terrain 15min), 6 Deceleration 1min, 7 Shut-down 5sec.
• "Segment Details" panel: Code, Name, Duration (hours dropdown), Description, Environment dropdown, Env. Characteristics, and "Mission Parameters" table (Name/Units/Previous Value/Current Value).

Step 6: Create Specialized Phases

• "Specialized Phases" table: Code "SP1", Name "Autonomous Parking", Duration "5m", Phases and Segments "Deceleration", Mission Events "Collision Avoidance", Operational Conditions "Parking Manoeuvre Planning", Environmental Conditions (empty).
• "Specialized Phase Details": Code "SP1", Name "Autonomous Parking", Duration "5.000 minutes", Description "Automated system for parking a vehicle without driver intervention." Tabs: Phases and Segments (selected), Mission Events, Operational Conditions, Environmental Conditions — showing checkbox tree of all phases/segments (1 Start-up, 1.1 Ignition, 2 Acceleration, 3 Cruise, 4 Turning, 5 Cruise 2, 5.1 Highway, 5.1.1 Highway A1, 5.1.2 Highway B2, 5.2 Mountain Terrain, 6 Deceleration [checked], 7 Shut-down).

Step 7: Create Mission Conditions

• "Mission Conditions" tab "Operational Conditions" (selected) / "Environmental Conditions". Operational Conditions table: OC1 "Ignition Key Turned to 'ON'" (Phases and Segments: Ignition), OC2 "Engine Coolant Temperature" (Start-up), OC3 "Throttle Input", OC4 "Engine Load" (Acceleration), OC5 "Parking Manoeuvre Planning" (Specialized Phases: Autonomous Parking; Mission Events: Collision Avoidance). "Operational Condition Details": Code "OC1", Name "Ignition Key Turned to 'ON'", Description "When the driver turns the ignition key to the 'ON' position, activating the electrical system, but before starting the engine." Right panel tabs Phases and Segments / Specialized Phases / Mission Events with Start/During/End checkbox columns per phase.
• "Environmental Conditions" tab table: EC1 "Heavy Rainfall and Flooding", Environment "Benign Environment", Phases and Segments "Cruise, Cruise 2". "Environmental Condition Details": Code "EC1", Name "Heavy Rainfall and Flooding", Environment dropdown "[Benign] Benign Environment", Env. Characteristics list.

Step 8: Create Mission Events

• "Mission Events" table: ME1 "Collision Avoidance" (Type "Operational", Occurrence "1E-5", Phases and Segments "Cruise 2", Specialized Phases "Autonomous Parking"); ME2 "Heavy Rainfall and Flooding" (Type "Environmental", Occurrence "1E-2", Phases and Segments "Acceleration, Cruise"). "Mission Event Details": Code "ME1", Name "Collision Avoidance", Description "Vehicle system taking evasive actions to avoid a potential collision.", Type dropdown "Operational", Occurrence slider "1E-5" (range 1E-9 to 1E0), Justification "This event occurs when the vehicle system detects an imminent collision and initiates evasive actions." Tabs on right: Phases and Segments, Specialized Phases, Operational Conditions, Environmental Conditions, each showing a checkbox tree of phases/segments.

Step 9: Create Mission Success Metric(s)

• "Mission Success Metrics" table: ID 1, Name "Transport Personnel", Success Criteria "5 people and luggage", Minimum Success Criteria "2 people and luggage". "Mission Success Metrics Details": Name "Transport Personnel", Success Criteria "5 people and luggage", Minimum Success Criteria "2 people and luggage", "System Flow Properties" checklist: "To Convert the Mechanical - rotational Angular velocity" (x2, both checked/included).

Step 10: Define Functional Profile

• "Functional Profile Definition": instructions "Enter the acceptable limits for the output flows of each function." and "Assign an Importance Ranking to each Mission Success Metric associated with the output flows of each function. The Importance Ranking assigned to a function will automatically be applied to subsequent Mission Phases." Table columns: Name, 1: Start-up, 2: Acceleration, 3: Cruise, 4: Turning, 5: Cruise 2, 6: Deceleration, 7: Shut-down. Rows for "To Convert the Mechanical - rotational Angular velocity" (x2): Acceptable upper limit (rad/s) 0.00/25.00/25.00/—/30.00/—/0.00; Acceptable lower limit (rad/s) 0.00/5.00/5.00/—/10.00/—/0.00; "1: Transport Personnel - Importance to mission" Low/Very High/Very High/Moderate/Very High/Very High/Low.

Step 11: Configure Duty Cycles

• "Duty Cycle Details": "The table represents the Duty Cycle of each item (rows) in each Phase or Segment of the mission (columns). To set a Duty Cycle for an item, enter the Duty Cycle as a percentage in the table cells. The Duty Cycle may be entered as a fractional number, e.g. 0.5 (50%) or as a whole percentage, e.g. 50 (50%). The Duty Cycle assigned to an item in a particular Phase or Segment is automatically applied to the subsequent Phases and Segments." Table with columns Start-up/Acceleration/Cruise/Turning/Highway A1/Highway B2/Mountain Terrain/Deceleration/Shut-down (with sub-column Ignition under Start-up) and rows for Vehicle System, Driveline (with Differential 0% at Start-up, Driveline 100% elsewhere), Power Generation (50%/100%/.../50%), Control Unit, Diesel Engine and its sub-items (Air Filter, Coupling 1, Engine, Governor, Injector Pump) all mostly at 100%.

Step 12: Configure Unit Life Accrual

• "Unit Life Parameter Configuration": instructions explaining the table represents units of each Unit Life item accumulated per Phase/Segment, requiring a Unit Life Parameter selected on the item (Reliability editor or Exponential (Unit Life) tab). Table columns: Item, Duration (h), Parameter, Total, then per-phase columns Start-up/Ignition, Acceleration, Cruise, Turning, Cruise 2/Highway A1/Highway B2/Mountain Terrain, Deceleration, Shut-down. Example rows: Air Filter Total 100.0 (100.0 at Cruise); Coupling 1 Total 5000.0 (5000.0 at Turning); Engine Total 0.1 (0.1 at Cruise 2); Injector Pump Total 0.2 (0.2 at Highway B2); Lift Pump Total 0.02 (0.02 at Mountain Terrain); Primary Fuel Filter Total 550.0 (50.0 at Start-up, 500.0 at Deceleration); Secondary Fuel Filter Total 100.0 (100.0 at Acceleration).

Step 13: Mission Defined

• Generated "Mission Profile Definition" report: "Mission Profile Summary" table (Name "Regular Trip", Duration "1.303h", Mission Cycles "1.00", Description "A short duration trip for the vehicle, assuming a benign environment and low operational loading.") with full phase/segment breakdown (IDs 1 through 7 with sub-segments 1.1, 5.1, 5.1.1, 5.1.2, 5.2, durations and elapsed times, and descriptions e.g. "A mission phase for actions required to start-up the vehicle for use." / "A mission segment for igniting the engine.").
• "Mission Parameters" table: Distance (Kilometers) value progression matching the earlier chart (0.00 → 112.00 Kilometers) against each phase/segment ID/name/duration/elapsed time.
• "Mission Parameters Graph": same Distance (Kilometers) line chart as Step 4.
• "Mission Success Metrics" table: 1: Transport Personnel, Success Criteria "5 people and luggage", Minimum Success Criteria "2 people and luggage", Relevant Flow Properties listing the two "To Convert the Mechanical - rotational Angular velocity" properties.
• "Importance Ranking" table: Mission Success Metric "1: Transport Personnel", Function & Flow Property "To Convert the Mechanical - rotational Angular velocity", per-Mission-Phase Importance to Mission: 2: Acceleration = Very High, 5: Cruise 2 = Very High, 6: Deceleration = Very High, 7: Shut-down = Low, 1: Start-up = Low, 4: Turning = Moderate.
• "Acceptable Limits Per Function" table: Function & Flow Property "To Convert the Mechanical - rotational Angular velocity" (x2), per Phase/Segment (Start-up through Shut-down) Acceptable Lower Limit and Acceptable Upper Limit in rad/s, matching the Step 10 values.

Related workflows

• WF41 – Entering Cycle Based Reliability Values (unit life configuration)
• WF69 – Create Mission Profile Groups
• WF12 – Conduct Reliability Allocations (uses Mission Profile duration)