Skip to main content

4. Procedure Management

4.1 Create a SOP​

Description​

A user can create a SOP for a company (airline more specifically).

Flow​

  1. The user enters data for creating a SOP
  2. The system selects the only airline owned by user
  3. The system creates the SOP
  4. Name can be auto-generated with "Procedures" appended tp aircraft type.
  5. SOP are not public by default.

Prerequisites​

  1. An airline exists associated with user

Notes​

The airline is auto-selected for the one and only one airline created by user. Obviously, many airlines could be created by user in future and this will be required to be taken into account.

4.1 Get List of SOPs​

Description​

A user can get a list of accessibles SOPs for an airline.

Flow​

  1. The user requests a SOP list, having filters or not.
  2. The system checks an existing airline associated with the user.
  3. The system returns the SOP associated with the airline, taking into account filter

Prerequisites​

  1. An airline exists associated with user
  2. SOP exists for any aircraft type, but if none exists, an empty list is presented

4.2 Edit an SOP​

Description​

A user can edit a SOP for an airline.

Flow​

  1. The user requests a SOP list, having filters or not.
  2. The user select a SOP to Edit
  3. System displays the SOP
  4. User clicks on a edit action
  5. System display inputs to edit SOP with its current data
  6. User edit data and clicks on 'save' action when done.
  7. Systems saves data.

Prerequisites​

  1. At least one SOP already exists

4.5 Delete an SOP​

Description​

A user can delete a SOP.

Flow​

  1. The user requests a SOP list, having filters or not.
  2. The user select a SOP to Delete
  3. System displays the SOP
  4. User clicks on a delete action
  5. Systems deletes the SOP

Prerequisites​

  1. At least one SOP already exists

Notes​

  • Delete is hard delete and permanently deleted. This should change in future.

4.6 Create a Procedure for a SOP​

Description​

A user can create a Procedure for a SOP.

Flow​

  1. The user requests a SOP list, having filters or not.
  2. The user select a SOP and the system displays it
  3. User choose to add a procedure
  4. Systems displays inputs to create a Procedure
  5. User triggers a save action when done

Alternate flow​

In creation state of Procedure:

  1. User triggers a cancel action

Prerequisites​

  1. At least one SOP already exists

Notes​

  • Delete is hard delete and permanently deleted. This should change in future.