4.7 Complete Specialized Phases Page (Step 6)

The next step in completing the mission profile is to create specialized phases. To open this page: select the Specialized Phases tab.

The Specialized Phases page is divided into 2 sections:

Table 4: Specialized Phases page segments

Section	Description
Specialized Phases	A table divided into 8 columns: (1) Code, (2) Name, (3) Duration, (4) Description, (5) Phases and Segments — associated, (6) Mission Events — associated, (7) Operational Conditions — associated, (8) Environmental Conditions — associated.
Specialized Phase Details	Provides fields for the user to enter a Specialized Phase code, name, duration, description and checkboxes to associate them to listed Phases and Segments, Mission Events, Operational Conditions and Environmental Conditions.

To create a Specialized Phase:

• Select the Add New Specialized Phase button
• Enter the Specialized Phase name in the Name field
• Enter the Specialized Phase duration in the Duration field
• Enter the Specialized Phase description in the Description field
• Select checkboxes to associate Phases and Segments, Mission Events, Operational Conditions, Environmental Conditions with the Specialized Phase

Figure 15 ("Created and Defined Specialized Phase") shows a "SP1 — Autonomous Parking" specialized phase (Duration = 5m, associated Phases and Segments = Deceleration, associated Mission Events = Collision Avoidance, associated Operational Conditions = Parking Manoeuvre Planning): Code = SP1, Name = Autonomous Parking, Duration = 5.000 minutes, Description = "Automated system for parking a vehicle without driver intervention." The Phases and Segments association tab shows a checklist tree (1 Start-up > 1.1 Ignition, 2 Acceleration, 3 Cruise, 4 Turning, 5 Cruise 2 > 5.1 Highway > 5.1.1 Highway A1, ...) with item "3 Cruise" checked.

4.8 Complete Mission Conditions Page (Step 7)

The next step in completing the mission profile is to create mission conditions. To open this page: select the Mission Conditions tab.

The Mission Conditions page is divided into two windows: Operational Conditions and Environmental Conditions.

Operational Conditions

Table 5: Operational Conditions page segments

Section	Description
Operational Conditions	A table divided into 6 columns: (1) Code, (2) Name, (3) Description, (4) Phases and Segments — associated, (5) Specialized Phases — associated, (6) Mission Events — associated.
Operational Condition Details	Provides fields for the user to enter an Operational Condition code, name, description and checkboxes to associate them to listed Phases and Segments, Specialized Phases, and Mission Events.

To create an Operational Condition:

• Select the Add New Operational Condition button
• Enter the Operational Condition name in the Name field
• Enter the Operational Condition description in the Description field
• Select checkboxes to associate Phases and Segments, Specialized Phases, and Mission Events with the Operational Conditions

Figure 17 ("Created and Defined Operational Condition") shows "OC1 — Ignition Key Turned to 'ON'": 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." The Phases and Segments tab shows a checklist with Start/During/End columns per phase; "1.1 Ignition" checked under "During" column.

Environmental Conditions

Table 6: Environmental Conditions page segments

Section	Description
Environmental Conditions	A table divided into 7 columns: (1) Code, (2) Name, (3) Environment, (4) Env. Characteristics, (5) Phases and Segments — associated, (6) Specialized Phases — associated, (7) Mission Events — associated.
Environmental Condition Details	Provides fields for the user to enter an Environmental Condition code, name, environment, env. characteristics and check-boxes to associate them to listed Phases and Segments, Specialized Phases, and Mission Events.

To create an Environmental Condition:

• Select the Add New Environmental Condition button
• Enter the Environmental Condition name in the Name field
• Select the Environmental Condition environment from the drop-down menu
• Select the Environmental Condition env. characteristics by clicking on the Env. Characteristics field
• Select checkboxes to associate Phases and Segments, Specialized Phases, and Mission Events with the Environmental Conditions

Figure 18 ("Created and Defined Environmental Condition") shows "EC1 — Heavy Rainfall and Flooding": Code = EC1, Name = "Heavy Rainfall and Flooding", Environment = [Benign] Benign Environment, Env. Characteristics (icon field, empty in example). Associated Phases and Segments = Cruise, Cruise 2; Associated Specialized Phases = Autonomous Parking (SP1 checked in the Specialized Phases tab).

4.9 Complete Mission Events Page (Step 8)

The next step in completing the mission profile is to create mission events. To open this page: select the Mission Events tab.

The Mission Events page is divided into two sections:

Table 7: Mission Events page segments

Section	Description
Mission Events	A table divided into 8 columns: (1) Code, (2) Name, (3) Type, (4) Occurrence, (5) Phases and Segments — associated, (6) Specialized Phases — associated, (7) Operational Conditions — associated, (8) Environmental Conditions — associated.
Mission Event Details	Provides fields for the user to enter a Mission Event code, name, description, type, occurrence, justification and checkboxes to associate them to listed Phases and Segments, Specialized Phases, Operational Conditions and Environmental Conditions.

To create a Mission Event:

• Select the Add New Mission Event button
• Enter the Mission Event name in the Name field
• Enter the Mission Event description in the Description field
• Select the Mission Event type from the drop-down menu
• Enter the Mission Event occurrence in the Occurrence field
• Enter the Mission Event justification in the Justification field
• Select checkboxes to associate Phases and Segments, Specialized Phases, and Mission Events (Operational/Environmental Conditions) with the event

Figure 20 ("Created and Defined Mission Event") shows "ME1 — Collision Avoidance": Code = ME1, Name = "Collision Avoidance", Description = "Vehicle system taking evasive actions to avoid a potential collision.", Type = Operational, Occurrence = 1E-5 (slider ranging 1e-9 to 1e-0/1e2 scale markers 1e-9...1e2), Justification = "This event occurs when the vehicle system detects an imminent collision and initiates evasive actions." Associated Phases and Segments: "5 Cruise 2" checked, and its sub-segment "5.1 Highway" also shown expanded (5.1.1 Highway A1, 5.1.2... Highway B2). The mission event table shows: Code ME1 | Name Collision Avo... | Type Operational | Occurrence 1E-5 | Phases and Segments = Cruise 2 | Specialized Phases = Autonomous Parking.