Case studies • Work items
Test and evaluation activities
Verification of requirements usually involves some kind of test and evaluation.
Creating Activity work item type
Following the instructions for creating a new work item type use the following parameters.
- Prefix: any
- Type name: Activity
- Type description: Test and evaluation activity
- Fleet: optional
- Scheduling: Date and time
- Enabled: enabled
Attach the verification procedure
Follow the instructions for attaching a document template to a work item to attach the verification procedure to the work item.
FRACAS
Work items can form the basis of a effective failure reporting and corrective action system (FRACAS).
Creating FRACAS work item type
Following the instructions for creating a new work item type use the following parameters.
- Prefix: any
- Type name: FRACAS
- Type description: Failure reporting and corrective action system
- Fleet: optional
- Scheduling: Unscheduled
- Enabled: enabled
Creating FRACAS sub types
Depending on your project you may want to have different types of FRACAS. You can create as many sub types as your organisation has for FRACAS types.
Custom fields
V-Raptor has a default field for categorising work items by system, however you can add as custom fields to suit your organisation's standard operating procedures.
Aircraft flights
V-Raptor's extensible work item system can be used to map flight planning to V-Raptor work items.
Creating flight work item type
Following the instructions for creating a new work item type use the following parameters.
- Prefix: any
- Type name: Flight
- Type description: Aircraft flight
- Fleet: optional
- Scheduling: Date, time, and finish location
- Enabled: enabled
Creating flight sub types
Flights may have different uses. V-Raptor's sub-types feature can be used to categorise the different types of flights.
Following the instructions for ceating new work item sub types, create new sub types for the following.
- Unclassified
- Delivery
- Type test
- Routine test
Customise the list for your project requirements.
Train runs
V-Raptor's extensible work item system can be used to map train run planning to V-Raptor work items.
Creating train run work item type
Following the instructions for creating a new work item type use the following parameters.
- Prefix: any
- Type name: Train run
- Type description: Dynamic train runs
- Fleet: optional
- Scheduling: Date, time, and finish location
- Enabled: enabled
Creating train run sub types
Train runs may have different uses. V-Raptor's sub-types feature can be used to categorise the different types of train runs.
Following the instructions for ceating new work item sub types, create new sub types for the following.
- Unclassified
- Transfer
- Type test
- Routine test
Customise the list for your project requirements.
Adding custom fields
There may be useful information that you want to include or capture during the event.
Following the instructions for creating work item fields, create fields for the following.
-
Name: Approval number
Description: The number provided by the rail infrastructure manager giving approval
Field type: String
Units: blank
Multi-line: disabled
Default value: blank
Required: No
Include in report: Include in head
-
Name: Conclusion
Description: Concluding statements provided at the end of the event
Field type: String
Units: blank
Multi-line: enabled
Default value: blank
Required: On closed
Include in report: Include in foot
Map the custom work item fields to the custom work item type.
Adding custom actions
Work item actions can be used to create a work flow for managing the operation of an event.