ShowTable of Contents Description
The Work Flow Engine is used to manage the workflow of all of the forms in the system. The Work Flow engine is policy driven using rules based on Areas and Roles. The Engine needs to be able to deal with multiple role holders and groups (?)
The Workflow Engine is integrated into :
Note to File
Failure Note
Action - need to scheck this Action:SC
Terminology
The following terms will be used, these are consistent with the SHE reporting Database
Initiator
Contributer
Mandatory Contributer
Reviewer
Mandatory Reviewer
The difference between a reviewer and a contributer is that the reviewer adds comments after a document has been prepared and issued whereas a contributer adds comments as it is prepared.
Examples
Scenario 1 - Note to file with optional ad-hoc contributions ( taken from Note to File
An Engineer makes some notes about a pump but they would like to have the materials Engineer and the area Engineer from an other area to add their comments.
The Engineer creates a simple Note to File but adds the two other individuals to the document workflow ( specific to this one-off document ).
The document is sent to each person for their comments before it reaches the completed status
The initiator is made aware that the comments have been added ( email or workflow ? )
Scenario 2 : Fitness for purpose review
A fitness for purpose review is need for multiple items of equipment. The process and proformas are detailed in a PI.
The system administrator sets up a standard template which defines the workflow in terms of a policy ( i.e. using named roles rather than named people ). They also attach a standard word document that will be used.
Then the Engineer initiates a new Fitness for purpose review the standard workflow and attachment(s) will be pulled in and used.
Scenario 3 : Failure Note
In this case a fixed workflow is being applied to a dedicated form. For consistency though we want to use the same templated approach. See Failure Note for the full workflow.
Assumptions
Queries
Technical Specification
Role Phrase SubstitutionThe system will use the same <<substitution>> convention as described in Note to File.
Role Title-<<Area>>
The system will support multiple substitutions on the following attributes - note that these are the "English" Attributes and not the back end unid codes :
Plant
Area
|