AERSHED Platform

Appearance

Emission States ​

We use a event_status field in the platform to track the current state of a emission and how it is being handled by an operator.

Internally, the event_status field is tied to the Event model, which is a 1-to-1 relationship with the detected emission (EmissionRecord model) per operator.

Currently, we have following main states in the platform:

  • NEW: new events, shortly after being matched, but not yet handled by operators.
  • WORK_IN_PROGRESS: after an event is assigned, it is marked as "In progress".
  • WAITING_APPROVAL: (conditional) if the approval workflow is enabled, this step signals that a person with reviewer permissions needs to take an action and either approve or reject the work done by the main assignee.
  • COMPLETED: signals that all work related to this emission, including investigation and follow-up are complete. This is an end state.
  • ARCHIVED: marks that this emission will not be investigated by the company. Events can only reach this state through automation or a django admin action currently. This is an end state.
  • REJECTED: when the Site field is marked as empty (Not related to my infrastructure), the event is marked as REJECTED so we can exclude it from statistics. This is an end state.
  • LINKED: this is a state that signals that this emission has been linked to another one and is not the main event. When an emission is linked, the contents of the notes and attachments sections are copied over to the main event.

Additional states:

  • CREATED: when the workflow automation is enabled, events are created with this state, so we can add rules per company and auto-archive emissions before they notify users.