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

Module Folders

MOCs are organized into three folders: Completed, In Process, and Voided to view current or historical data. The MOC module menu is visible to users with MOC Admin and specific company, division or account permissions.

Below are the guidelines for elements that appear on ALL MOCs

List View

  • MOCs in your company or division or account which shown in the List View. 
  • You can sort columns by clicking on column headers
  • You can apply filters 
  • Key fields in the List View are MOC title, MOC number, and originator. By default, the MOCs are ordered by Date Created, with latest MOC near the top.

MOC Details

  • Clicking on a MOC title in the list will bring you to the MOC Details page. 
  • You can click on the In Process folder again, the Details tab in the top left or the List View Button in the top right to toggle back to the List View.
  • You must be in MOC Details to edit an MOC. You can create a new MOC from either the List View or the MOC Details. 

Toolbar Buttons

  • Audit Log: The Audit Log button displays an MOC Audit log for any change that has been made to the MOC.
    • The Audit Log contains information of when a change was made, by who the change was made by what item was affected with the change, what area this change was made at, what stage was the MOC during the change, what type of change was made, and the details of the change. This information can be exported to Excel or PDF.
  • View Summary: The View Summary button displays the MOC Summary. The MOC Summary page summarizes all current MOC information.
    • This is the same summary page that is shown to Evaluators, collaborators, Approvers, Implementers and implementation manager when they click on View MOC Summary, or to people when they sign-off on MOC notice.
    • The MOC Summary is updated constantly as the MOC progresses through various stages and new comments are entered.
    • Evaluation and Implementation sections show each corresponding requirement with its status. If a link is shown for a requirement, then this requirement has a form (checklist) or a document attached. The form can be viewed by clicking on the link.
    • In the Implementation section, you can view the list of people who have been notified about this MOC via the "Send Notice" requirement and add more people to this list if permitted.
    • The MOC Summary page is frozen for MOCs in the Completed.
    • Show All Forms button is available on the top right of the MOC Summary page. Clicking on this button will show all of an MOC's Collaboration comments, evaluation / implementation forms and notice signoffs on the MOC Summary page (users can then print the MOC with all of this information)
  • Copy: The Copy button can be used if you wish to initiate an MOC identical to a previously completed MOC. The MOC is copied and placed in the In Process folder with a new MOC number in the new stage.

Tabs

  • Details Tab: The Details tab displays basic configuration information of the MOC and the MOC workflow diagram.
  • Pre-Approval Tab: The Pre-Approval tab shows pre-Approval information for the MOC, if any.
    • The pre-Approval information is shown only if the MOC request was submitted from the Frontline Desktop Shortcuts tab.
  • Evaluation Tab: The Evaluation tab shows all evaluation requirements of the selected MOC, if any.
    • Clicking on a requirement shows its order of evaluation, Evaluator, evaluation status and optional days to complete or due date. 
  • Collaboration Tab: The Collaboration tab shows collaborators for the MOC, if any.
  • Approval Tab: The Approval tab shows Approvers for the MOC.
  • Implementation Tab: The Implementation tab shows all implementation requirements of the selected MOC, if any.
    • Clicking on a requirement shows its order of implementation, Implementer, implementation status and optional days to complete or due date.
  • Attachments Tab: Any attachments added to the MOC will display who added the attachment, when it was added, and at what stage the attachment was added.
    • Attachments can be documents such as drawings or procedures. You can add or edit new attachments from this view.
  • Equipment Tab: The Equipment tab shows any equipment referenced by this MOC, if any.

About Completed MOCs

The MOC Completed folder lists all of the MOCs in your company or division or account which are closed out. You can view the details of the MOC, but you cannot change any field in a completed MOC except the attachments. The Attachments tab for a completed MOC allows you to add new attachments or update the URL of an existing attachment for a closed out MOC.

About In Process MOCs

This section explains the MOC In-Process menu item. The MOC module menu is visible only if you have the permission of MOC User, MOC Power User and/or MOC Super User and specific company, division or account level MOC access permission.

Buttons

  • Void: The Void button allows you to void an MOC in Pre-Approval, Evaluation, Collaboration, Approval, Implementation or startup stage. It also allows voiding an MOC that has been pre-approved and is currently in the new stage. The button is only visible to MOC Power Users for all MOCs and MOC Originators for their MOCs.
  • Procedure: The Procedure button allows Originators to view company or division-specific procedures that can assist them when creating a new MOC.
  • Update: The Update button allows you to update many previously completed fields in the MOC details page and various other tabs. The Update button is visible only for the MOCs in the new, Evaluation and Collaboration stages. Once an MOC enters the Approval stage, a majority of the fields cannot be updated (update button hidden). Only the fields containing data related to the MOC processing (such as Originator, Implementation Manager, Expiration Date for temporary MOCs, Expected Completion Date, Tag and Work Order) can be updated. These fields are shown with an Update link right next to the field and can be updated after providing a reason for the update.
  • Memo: The Memo button allows you to create and start MOCs which are created specifically to notify affected people of a change using the "Send Notice" Implementation requirement. It is useful for minor changes, such as changes to procedures. For these MOCs, the Originator is the only Approver and is also the Implementation Manager. "Send Notice" is the only requirement with the Originator as its Implementers. This greatly simplifies the process of creating and starting MOCs with the sole purpose of notifying affected people and getting them to sign-off on the notice.
  • Delete: The Delete button allows you to delete an MOC in the new stage which has not gone through the Pre-Approval. Only an MOC created from the module menu in the new stage can be deleted. The Delete button will not be visible when you are not allowed to delete an MOC. When not visible, you must void the MOC.
  • New: The New button allows you to create a new MOC.
  • Send Immediate E-mails: This link allows you to send a message via e-mail immediately to any of the role players of the selected MOC.

About Voided MOCs

  • The MOC Voided module menu item lists all MOCs in your Company or Division or Account that have been voided (disapproved). Clicking any MOC title from this list you can view the details of the MOC but you cannot change any field in a voided MOC.
  • An MOC will show up in the Voided folder if one of the following occurs:
  • The MOC request is disapproved during the Pre-Approval stage. Depending upon the Pre-Approval configuration, the disapproval can be by one or all of the pre-Approvers. The person disapproving must give a reason for the disapproval.
  • The MOC is disapproved by one of the Approvers during the Approval stage. The person disapproving must give a reason for the disapproval.
  • The number of days to approve the MOC is exceeded by all Approvers during the Approval stage.

The MOC originator can decide whether to enforce days to approve. If not enforced, the MOC does not automatically move from one Approver to the next when days to approve is exceeded. It moves only when an action, either approve or disapprove, is taken by the Approver.

  • Implementation manager voids the MOC when it shows up on his system desktop to seek Approval for startup in the startup stage.
  • The MOC is administratively voided by its originator or an MOC power user from the MOC module menu using the Void button.

Buttons

  • Resubmit: The Resubmit button allows the originator of the voided MOC or a power user to resubmit the voided MOC.
    • When a voided MOC is resubmitted, the originator is required to enter a reason for this action. A copy of it is placed in the In Process folder with a new MOC number.
    • The originator or a power user can then restart the MOC after making the changes requested by the person disapproving the MOC.
    • The original voided MOC stays in the Voided folder with the original MOC number. This allows you to maintain a history of all disapproved MOCs.
    • The reason for resubmitting the voided MOC with a hyperlink to the original voided MOC is displayed on the resubmitted MOC summary page. This allows the MOC role players a convenient reference to the original MOC and the reason it was disapproved.
    • A voided MOC can be resubmitted just once; the Resubmit button is therefore visible only for the MOCs which have not been resubmitted before.

You are able to void the new, copied, MOC and resubmit the new copy if needed. But the original MOC number will no longer have the resubmit button.

    • An MOC voided during the Pre-Approval stage (first stage of the workflow) cannot be resubmitted from the Voided folder. Person submitting the MOC request must submit a revised MOC request upon receiving the e-mail denying the MOC request.