The loop manager is designed to house analog and discrete loop testing tasks. A loop is comprised of several instruments that work together to control a process control loop. Analog loops are typically comprised of elements, transmitters, controllers and alarms. Discrete loops are typically comprised of switches that are run in an on-off state. Most Planned Tasks assign a specific checksheet to a specific asset. Loops, by definition, are a collection of devices/assets. Therefore, you must create the loops and assign devices to them before creating the Loop Tasks. The tasks will appear in the Planned Task Manager. They are also accessible from the Tasks by Loops manager.
Most Loops will be imported in two separate files. First, the loop Names/IDs and project data will be imported. A second import will assign devices to the existing Loops. You may also manually create Loops.
The secondary panel in the Manager displays any tasks assigned to a given loop, any Forms attached, Devices/Assets, Punchlists, and Documents.
The purpose of the colored bubbles is to provide a quick status on the "readiness" and "completion" of a loop. Loops with a RED status bubble means that either the loop is not completed, or that one of the components within the loop does not have their individual checklist or test forms completed. All individual tests must be completed before the loop can be tested. When the loop has a GREEN status bubble, it means the Loop is READY to test. When the loop has a DARK BLUE status bubble it means the loop is completed and has no pending Punch list items