Implementation

Implementation requirements are assigned to individuals or jobs in sequential or simultaneous order with optional due dates and can be classified as critical (pre-startup) or non-critical (post-startup). Once an MOC has been approved, the MOC appears on the Frontline Desktops in the MOC tab with a task of Implement for all users who are listed as Implementers. A requirement assigned to an individual can be transferred to another individual and can be verified upon completion by a different individual.

Custom web-based forms can be created using the built-in form designer and attached to implementation requirements. If a form is attached to the requirement, the Implementer must complete all required fields of the form before completing the requirement. Any deficiencies discovered while completing the forms can also be documented with critical or non-critical action items. Users with Report permissions can run reports on populated forms.

Below are the guidelines for MOC's in the Implementation Stage

• Implementation requirements are assigned to the Implementers based on their order and may display an optional due date if entered by the originator.
• If the Implementer is a job, rather than an individual, any person assigned to that job can work on the requirement.
• The Implementer can complete the requirement immediately, enter progress or transfer it to another user. All transfers are recorded in the requirement history viewable by selecting the History link.
• A requirement assigned to a job cannot be transferred.
• The Implementer can attach documents as evidence of progress or for information.
• Any requirement that is ready to be worked on (possibly based on the order) shows Complete Now under the action column.
• If the action column shows Pending, the requirement is assigned to someone else or has a higher order.
• If enter progress is selected, the requirement remains on the Implementer's Frontline Desktop in the MOC tab and the MOC Summary displays the status or the requirement with a Progress link to view any progress that has been made.
• A critical requirement cannot be completed if another critical requirement of a lower order is not complete.
• A non-critical requirement cannot be completed if another non-critical requirement of a lower order is not complete.
• A critical requirement can be completed if a non-critical requirement of a lower order is not complete, this prevents non-critical requirements from delaying the completion of critical requirements.
• If a requirement has a verifier, the Implementer can only transfer the requirement to the verifier for completion. The verifier can then complete the requirement of send it back for additional work.
• The Send Notice implementation task is a required requirement designed to notify anyone who will be impacted by the MOC and cannot have a verifier.
• The Send Second Notice is an optional implementation task designed to notify anyone who will be impacted by the MOC after changes have been made since the original Send Notice and cannot have a verifier.
• All critical requirements must be completed before the MOC can move to the Startup stage.
• All non-critical requirements must be completed before the MOC can be completed (closed-out).
• The originator or power user can change the Implementer or verifier of any incomplete implementation requirement and/or complete the requirement on behalf of the Implementer or a verifier.
• An Implementer can track the status of the MOCs worked on by them by selecting the MOC Participation link from their Frontline Desktop Quick Links section.

How to Complete an Implementation Requirement Task

The instructions below provide detailed steps on how to complete an implementation requirement.

1. Select the MOC title from the MOC tab located on the Frontline Desktop.
2. Select View MOC Summary and review the summary carefully before completing task.
3. Select Close to exit the MOC Summary.
   
   1. If the requirement is Send Notice or Send Second Notice, see the MOC Send Notice Process article for more information.
4. If the requirement is not a Send Notice or Send Second Notice, select Complete Now to begin working on the requirement.
   1. The Requirement Completion form is displayed with details of the requirement and any implementation instructions from the originator. If a form (checklist) or network document is attached to the requirement, a link will be displayed.
5. A user can choose to complete the requirement, enter progress and attach a document.
6. If a user chooses to enter progress on a requirement, the requirement remains on their desktop until completed and all prior progress can be viewed by selecting History.
7. If the requirement is attached to a form (checklist), select the form link and complete all of the required fields (marked with a red asterisk).  
   1. Some fields many have a pre-defined action item, if selected, complete details necessary to assign the populated action items.
8. If the requirement is attached to a network document, complete the requirement as instructed. If necessary, print the document, fill out requirement fields then upload the completed version by selecting Choose File.
9. Once the requirement has been completed, enter any comments (optional) in the Comments field and select OK. The MOC will be moved to the next Implementer.
   1. If the requirement has a verifier, the option to send the completed requirement to the verifier will appear. The verifier can complete the requirement or send it back to the Implementer for additional work.
10. Select the Frontline Desktop icon.