Profiles

About MOC Profiles

A profile allows you to pre-define priority, MOC type, implementation manager, evaluation requirements, collaborators, approvers, implementation requirements, attachments, equipment and many other parameters for a category or class of MOCs. The Profiles screen allows you to create or edit MOC profiles in your division. 

A few examples of profiles are - "Procedure Change", "Rotating Equipment Change" or "Process Change". When an originator creates an MOC, he can select a profile by its name, and the system will enter all the profile parameters into the MOC automatically. This speeds up the MOC creation process, and helps maintain consistency for a given class of MOCs. Profiles thus serve as standardized MOC or workflow templates that can be applied to MOCs for consistency.

A profile also allows you to override the base evaluation and implementation requirements properties. For example, an implementation requirement "Procedure Update" can be critical (must be completed before startup) for a profile "Procedure Change", but can be non-critical for a profile "Set Point Changes - Temporary". Similarly, you can also designate any evaluation and implementation requirement as mandatory or recommended depending on the profile it is included in. You can order evaluation and implementation requirements differently within a profile, and assign them to different evaluators and implementers depending on the profile.

A profile can also mandate that one or more risk or hazard evaluation type requirements be completed prior to submitting MOC for approval. There are two options available in this case:

Create an evaluation requirement and select it under the profile's Evaluation tab. For an MOC that uses this profile, this requirement must be completed prior to the collaboration stage (if used) or the approval stage by the designated evaluator.

Create an implementation requirement and select it under the profile's Implementation tab. Check "Originator as Implementer", "Must Be Completed Before Approval" and designate its order as 1. For an MOC that uses this profile, this requirement must be completed by the originator prior to starting approval.

Within a profile, you can set a due date for an evaluation or an implementation requirement by entering a number in the optional "Days to Complete" field. When the requirement is assigned (changed to "Inbox" status), the due date will be automatically calculated by adding "Days to Complete" to "Date Assigned". This due date will appear under the Desktop's MOC tab and in the MOC e-mail notifications. You can also enforce days to approve and enforce days to collaborate differently within each profile.

Profiles can be organized by Ref Codes (discussed below). Each profile can be attached to one Ref Code, to make it easier and faster for the originator to select a profile. If you do not attach a profile to a Ref Code, it is attached to the Ref Code "_none_" by default, and becomes a generic profile. When MOC originators select a Ref Code, only the profiles attached to the selected Ref Code and the Ref Code "_none_" are shown. This allows you to have a few profiles that apply to all Ref Codes, and eliminates the need to create identical profiles for different Ref Codes.

A profile can also be attached to a pre-approval form. In this case, the originator does not have to select profile once the MOC request is approved. The pre-approvers can also review all properties of the MOC (such as approvers and requirements) in the pre-approval stage. One or more collaborators and approvers can also be designated as mandatory in a profile. Similarly, selected evaluation and implementation requirements can be designated as mandatory or recommended in a profile. All mandatory requirements are automatically added, and cannot be removed by the originator. Recommended requirements are also added, but can be removed by the originator if not applicable for an MOC. Any profile must contain at the minimum the mandatory Send Notice implementation requirement.

Only MOC power users can see and configure profiles.

Manage MOC Profiles

How to Create an MOC Profile

Step

Action

1

Navigate to Settings > Profiles in the MOC module menu.

Result: The profiles already available in the system will display.

2

Select    from the toolbar.

Result: The Profile Information form will display all available fields to complete.

3

Select Ref Code to which the new profile will be attached. If you are planning to create a lot of profiles, it is recommended that you organize profiles by Ref Codes. If you leave it at _none_, this profile will be visible under all Ref Codes.

4

Enter the profile Title (mandatory), Priority, MOC Type and Implementation Manager. Instead of naming a specific implementation manager, you may check the box Originator as Implementation Manager. This is useful in cases where profile is designed for a low impact change.

Although not common, you may also select enforce days to approve and enforce days to collaborate if the profile you are creating is for emergency MOCs.

5

Select    on the toolbar.

Result: The new profile has been added to the list and is available for users to select.

6

Enter evaluation requirements, collaborators, approvers, implementation requirements, attachments and equipment, if desired, by clicking on the appropriate tab on the top.

Note:

  • Hyperlinks above show approximate steps when these items are added to an MOC. Some steps may not apply when added to a profile.
  •  Only existing evaluation and implementation requirements can be added to a profile. You must create evaluation requirements or create implementation requirements first before they can be added to a profile.
  • Make note of step 7 - 9 below,  which shows additional options available when adding above items to profiles.

7

When adding an evaluation requirement to a profile in step 6, there are additional choices available:

  • Do you want the requirement to be mandatory or recommended for the selected profile? A mandatory requirement cannot be deleted, whereas a recommended requirement can be deleted by the originator if not applicable for the selected MOC. Check appropriate boxes to enable this feature.
  • Do you want originator to be the evaluator for a requirement? A check box is provided for this. You can optionally select a designated evaluator for the requirement.

8

When adding collaborators and approvers to a profile, you can designate one or more collaborators and approvers as mandatory. Those designated mandatory cannot be deleted from MOC when such profile is selected by originator.

9

When adding an implementation requirement to a profile in step 6, there are additional choices available:

  • Do you want the requirement to be mandatory or recommended for the selected profile? A mandatory requirement cannot be deleted, whereas a recommended requirement can be deleted by the originator if not applicable for the selected MOC. Check appropriate boxes to enable this feature.
  • Do you want originator to be the implementer for a requirement? A check box is provided for this. You can optionally select a designated implementer for the requirement.
  • Do you want one or more requirements to be completed prior to submitting the MOC for approval? Such requirements may be designed to allow you to evaluate risk, benefit or degree of change, such as MOC screening form, hazard analysis, degree and significance of change, etc.