Concepts

Settings

Safety Statuses and Types

Safety statuses and safety types work together. A safety provision or override incident’s safety type controls the status assigned to it when a system event occurs. For example, when a provision is created (event) and assigned the type “Overfill protection”, its status might automatically be set to “New”.

As a starting point for setting up safety statuses and types for your organization, this topic provides examples of statuses for different objects and requirements:

•	Safety Provisions using Approvals

•	Safety Provisions using Acceptance

•	Override Incidents using Approvals

Each table explains the purpose of the statuses, lists their properties, and shows the safety type events that typically use them.

Tip: APM provides default safety statuses and types. You can modify them as needed or create new ones.

Safety Provisions using Approvals

When an organization uses the APM approval process, these statuses are required: Approval requested, Approved, Redrafted, and Rejected.

Safety Status	Status Properties	Safety Type - Events
New – applied automatically or manually whenever the provision or draft needs to be set up or modified	• Properties can be updated • Can be sent for approval or marked as accepted • Set the owning object’s status to New • Can be manually set	Creation
Approval requested – applied automatically when the object is sent for approval. Prevents changes from being made to the provision and its draft.	• Set the owning object’s status to Approval requested	Sent for approval
Approved – applied automatically when the last approver on the route approves the object. Promotes the draft to the current version. A current version, if it exists, moves to history.	• Promote draft to current • Set the owning object’s status to Approved	Accepted or approved
Rejected – applied automatically when an approver rejects the provision	• Canceled • Set the owning object’s status to Rejected	Rejected
Redrafted – applied automatically when the provision is redrafted	• Properties can be updated • Can be sent for approval or marked as accepted	Redrafted
Historical – applied automatically when a version moves to history		Moved to history

Safety Provisions using Acceptance

The acceptance process requires that a reviewer examine the provision and its draft and, if satisfied, mark the draft as “Accepted”. The Approval requested, Rejected, and Redrafted statuses are optional

Safety Status	Status Properties	Safety Type - Events
New – applied automatically or manually whenever the provision or its draft needs to be set up or modified	• Properties can be updated • Can be sent for approval or marked as accepted • Set the owning object’s status to New • Can be manually set	Creation
Approval requested – applied manually to a draft to show that it is ready to be reviewed	• Can be sent for approval or marked as accepted • Set the owning object’s status to Approval requested • Can be manually set
Approved – applied automatically when the draft is marked as accepted. Promotes the draft to the current version. A current version, if it exists, moves to history.	• Promote draft version to current • Set the owning object’s status to Approved	Accepted or approved
Rejected – applied manually to the provision when the reviewer rejects the draft	• Canceled • Can be manually set
Redrafted – applied manually to the provision so that it can be revised after being rejected	• Properties can be updated • Can be sent for approval or marked as accepted • Can be manually set
Released – applied manually to the provision or draft to promote the draft to the current version Tip: You can use this status to promote a revised draft without the approval or acceptance process.	• Properties can be updated • Promote draft version to current • Can be set manually
Historical – applied automatically when a version moves to history		Moved to history

Override Incidents using Approvals

Typically, incidents are sent for approval when an extension is requested.

Safety Status	Status Properties	Safety Type - Events
New – applied automatically or manually whenever the incident needs to be set up or modified	• Properties can be updated • Can be sent for approval or marked as accepted • Can be manually set	Incident Creation
Incident in progress – applied manually to an incident to set the Incident Started date and time. At the same time, the work document is created. Alternatively, the safety type can specify that incidents are started automatically when the Update Open Override Incidents command is executed manually or by a scheduled action.	• Properties can be updated • Can be sent for approval or marked as accepted • Can be manually set • Usage – Override incidents only • Incident options: • Mark the incident as started • Create the incident’s work document	Automatically updated as started
Incident usage exceeded – applied automatically when the incident exceeds the provision version’s maximum usage duration. Notifies employees so that an extension can be requested and approved.	• Properties can be updated • Can be sent for approval or marked as accepted • Usage – Override incidents only • Incident options: • Notify employees	Usage exceeded
Approval requested – applied automatically when the incident is sent for approval		Sent for approval
Approved – applied automatically when the incident is approved. The extension is accepted.		Accepted or approved
Rejected – applied automatically when an approver rejects the incident	• Canceled	Rejected
Redrafted – applied automatically when the incident is redrafted	• Properties can be updated • Can be sent for approval or marked as accepted	Redrafted
Historical – applied manually to indicate that the incident’s life cycle is complete. Sets the Incident Ended date and time. Notifies employees.	• Can be manually set • Incident options: • Life cycle complete • Notify employees