Skip to content
English
Customer portal
Go to fldata.com
  • There are no suggestions because the search field is empty.

Implementation Requirements

Implementation requirements are standard, generic tasks for MOC implementation, such as hazard review, drawing or procedure update, Pre-Startup Safety Review (PSSR) that can be assigned to people.

Below are the guidelines for Implementation Requirements

  • Only MOC Power Users and Super Users can see and configure implementation requirements
  • The Settings > Requirements > Implementation screen allows you to create requirements. Once implementation requirements are created, you can populate them in profiles and on In Process MOCs.
  • Implementation requirements can be either division specific or company-wide (this is done by leaving the division as "None").
  • An implementation requirement can have an attached online form or a checklist, such as a Pre-Startup Safety Review (PSSR) checklist, created using Settings > Forms.
  • When you attach a form to an implementation requirement, the Implementer must complete all of the required fields of the attached form in order to close out the requirement. Alternately, an implementation requirement can be linked to a document on your network via an URL.

You cannot link an implementation requirement to both an online form and a document simultaneously. The linked form or document is displayed to the Implementer in the Requirement

  • Implementation requirements can be set up as critical or non-critical by default (by itself or within a profile). Critical implementation requirements are tasks that must be completed prior to startup of an MOC. An originator can change the default setting of an implementation requirement when selecting it for his MOC.
  • It can be assigned to an individual or a job*. If assigned to an individual, it can be transferred by the assignee to another individual.
  • It can have a default Implementer (by itself or within a profile). This is useful when a designated person must always complete certain tasks for all MOCs in a category.
    • For example, if you have a certain draftsman who always updates all drawings in Plant A (set up as a Ref Code), you can set him up as the default Implementer of a requirement named "Update Drawings" in all profiles in Plant A. You can also set the MOC originator as the default Implementer of a requirement.
  • It can have a verifier. Following completion, the requirement is transferred to the verifier's Frontline Desktop. The verifier can then either complete (close out) the requirement or transfer it back to the Implementer.
  • By selecting "Must be completed before Approval" on requirements you can mandate they be completed before submitting MOC for Approval.

This option is only selectable if the Originator is set as the Implementer of that requirement.

  • It can have a due date (appears under the desktop's MOC tab and in MOC e-mail notifications). To set a due date for an MOC requirement, enter a number in the requirement's Days to Complete field in MOC > In Process > Implementation. When the requirement is assigned (changed to "Inbox" status), the due date will be automatically calculated by adding "Days to Complete" to "Date Assigned". Administrators can also enter default values for "Days to Complete" in MOC profiles.
  • For complex MOCs which demand tracking a lot of implementation requirements, it is recommended that you pre-populate implementation requirements in profiles. An implementation requirement setting in a profile (critical/non-critical and default Implementer) takes precedence over the base settings discussed above. This allows you to set certain implementation requirements as critical and have designated Implementers, depending on the profiles they are included in.
  • All requirements have a button "Action Items" which is added automatically. This button allows creating and assigning action items manually from the requirement.

How to Create MOC Implementation Requirements

  1. Navigate to Settings > Requirements > Implementation in the MOC module menu. The implementation requirements already available in the system will display.
  2. Select New from the toolbar.
  3. Enter the title of the route in the Title field.
  4. Description is an optional field that can be used to further describe the implementation requirement. Enter a description, if necessary.
  5. Select whether the implementation requirement is critical or non-critical.
    1. If you add an implementation requirement to a profile, you can select it to be critical or non-critical in that profile. It overrides the default characteristics you select here.
  6. If you want to attach this implementation requirement to a form, select the name of the Form from the drop-down box. Select View to make sure correct form has been selected.
  7. If you want to link this implementation requirement to a document on your network via an URL, select the Choose File to browse for the document and select Open. Upon saving, you will see a View link that allows you to confirm the URL.
  8. If you select Create MOC choose one of the two options to determine how the task will behave:
    1. Requirement can be completed after creating MOC: This option will allow for the requirement task to be completed and removed from the assignee's desktop once the MOC is submitted, and MOC can proceed to close-out.
    2. Requirement to remain open until MOC is closed out: This option will keep the requirement task on the assignee's desktop with an In Progress status after the MOC has been submitted. The requirement task will remain on the assignee's desktop until the associated MOC has been closed-out.
      1. The task will be displayed on the assignee's desktop as a requirement task with a Create MOC requirement display in the Requirement Completion form. This feature can only be used when the Individual radio button has been selected in the Assigned: field.
  9. Select the Require Attachment checkbox to require the assignee to add an attachment to the requirement before they are able to complete their task.
  10. If you want to designate a default Implementer, do you want the Implementer to be the originator?
    1. If YES, select the Implementer Type: Originator from the drop-down options.
    2. If NO, select the Implementer Type: Individual or Job, enter search criteria in the Implementer field and click ellipses. A list of names or job titles matching the search criteria is displayed then select "OK".
      1. If you want to select a specific user within a job: once you have selected the job from the available options, select the group icon to display a list of users assigned to that job. Select a user from the list and select "OK".
  11. Ensure Company, and Division are correct.
  12. If you want to make the requirement division specific, select the Division.
    1. If you want to make the requirement company-wide, leave the Division field blank.
    2. This is typically done for standardized requirements that are to be used across all Divisions.
  13. Select Save on the toolbar. The new implementation requirement has been added to the list and is available for users to select.
When building your requirement, if you have not created a form that you want to attach to, you can save the implementation requirement, leaving the form field as _none_. Create the form and edit the implementation requirement to attach it to the new form.
You cannot attach an implementation requirement to both a form and a document.

If adding an attachment is required, only one attachment is allowed when selecting Complete. However, assignees can add as many attachments as needed (10 at a time) by entering progress multiple times.

If the requirement is made to be company-wide, it is recommended to leave the Implementer field blank until the requirement is added to a division specific profile.

About Send Notice Implementation Requirement

  • Send Notice is a mandatory implementation requirement that is automatically added to all MOCs and all profiles.
  • This implementation requirement is designed to allow you to conveniently notify people affected by the MOC.

It is mandatory because of the industry-standard practice of notifying one or more people about changes.

  • Send Notice implementation requirement creates and assigns an MOC training item to the people who have been selected to receive notices. The content for the training item is the MOC summary, with instructions at top and Sign-off button at bottom.
It shows up under the Training tab of their Frontline Desktops, and they must click sign-off at the bottom of the MOC summary page to get credit for reading the notice.
  • A completion record is kept for each person signing-off, for regulatory reasons. People can re-review this sign-off or any past sign-offs by clicking on the MOC Sign-offs link on their Frontline Desktops. This is useful in cases where the process documentation has not been updated for the changes prior to startup.
  • If you need to notify affected people a second time about an MOC, use Send Second Notice. An example of where you may have a need to notify people two times about an MOC is when the implementation is expected to take long (such as for a capital project MOC), and you need to notify people as soon as it is approved, and then again before the actual startup of the project.
  • Send Second Notice works same as the mandatory Send Notice requirement, with following exceptions:
    • It is also configured in each division, but it is optional and it does not have to be used in a profile or in an MOC.
    • If you want to make Send Second Notice mandatory for some categories of MOCs, use it in a profile (such as Capital Projects) and make it mandatory within the profile.
    • The Implementer of the Send Second Notice requirement is required to enter comments explaining why people are being notified a second time. These comments are displayed to the affected people in the MOC summary page above the sign-off link.