Optrix Documentation

The checklist file format is an XML format that specifies the steps required to complete a single job.

Let's imagine we have an simple isolation procedure for shutting off a drive.

It's broken into four steps…

• Confirm asset identity
• Check the drive enclosure for warnings or notices before proceeding.
• Turn the rotary switch handle
• Lock the switch.

To create a checklist for this job, we first create a Isolation Checklist.checklist file in your choice of text editor (we suggest Notepad++ on Windows, or JED on Linux).

Now, we fill in the basic XML elements….

<job>
  <name>Isolate [NAME]</name>
</job>

The 'job' element is our XML document - it describes a single job.

The 'name' attribute gives this particular checklist a name. Here, we are using property substitution so that [NAME] is automatically replaced with the name of the asset.

Now we can map out our three steps, inside the 'job' element…

<step>
	<name>Confirm Identity</name>		
	<desc>Confirm the nameplate shows the correct ID - [ERN].</desc>
</step>
<step>
	<name>Check for Warnings</name>		
	<desc>Check the [ERN] drive enclosure for any details or notices about problems with the drive.</desc>
</step>
<step>
	<name>Open VSD Circuit Breaker</name>		
	<desc>Shut off the large rotary switch on the drive cabinet.</desc>				
</step>
<step>
	<name>Lock Off</name>		
	<desc>Lock off the circuit breaker to ensure your safety when working in the apartment. Remember to remove your lock at the end of the job.</desc>				
</step>

We've now created steps that the user can go through - each has a name and a description.

However, we can do more with these checklist steps.

Some steps will require the user to interact with other, nearby assets. This is very common in isolations.

By adding an asset element, we can specify which asset a step refers to.

<asset>Elevator Drive</asset>

You can use an asset name or ERN to specify the relationship.

This will allow users to see what the asset is, where it is and what it's currently doing.

ARDI has access to live information.

This means that we can prevent users from checking off items when we have live measurements that indicate the system status is not where it should be.

For example, we can ensure pressure drops to zero on a pressure transmitter before we allow users to confirm that they have turned the isolation valve.

We can also make a 'wait' step and ensure that the system is in a stable state before allowing users to proceed, which may be required for complex manual startup procedures.

<confirm>
	<asset>Elevator Drive</asset>
	<property>Power Usage</property>
	<safezone comparison="less" value="0.1"/>
</confirm>

The Confirm element lets the checklist system know you'd like to confirm the state of an asset before proceeding.

You need to specify three things for a confirmation…

• The name or ERN of the asset,
• The property you want to monitor (property element), or the name of the alert you want to check (alert element), and
• The target values (or 'safe zone') you are looking for.

So the combination of the three confirm properties above indicates that we aren't able to proceed unless the Power Usage of the Elevator Drive is less than 0.1.

You might want the user to contribute photographic evidence that a task has been completely successfully - this can be extremely handy when you need to confirm that a safety-critical step has been done.

Adding the photolock property to a step requests that the user submits a photograph from their mobile device, proving the step has been done.

In this case, we are going to add a photolock to the 'Lock Off' step. This way the users must send a photograph (which will also include timestamp and rough location information) to confirm that they have successfully locked off the power supply.

<job>
	<name>Isolate Power to [NAME]</name>
	<step>
		<name>Confirm Identity</name>		
		<desc>Confirm the nameplate shows the correct ID - [ERN].</desc>
	</step>
        <step>
		<name>Check for Warnings</name>		
		<desc>Check the [ERN] drive enclosure for any details or notices about problems with the drive.</desc>
	</step>
	<step>
		<name>Open VSD Circuit Breaker</name>
		<asset>Elevator Drive</asset>
		<desc>Shut off the large rotary switch on the drive cabinet.</desc>		
		<confirm>
			<asset>Elevator Drive</asset>
			<property>Power Usage</property>
			<safezone comparison="less" value="0.1"/>
		</confirm>
	</step>
	<step>
		<name>Lock Off and Photograph</name>		
		<desc>Lock off the circuit breaker to ensure your safety when working in the apartment. Remember to remove your lock at the end of the job.</desc>		
		<photolock/>
	</step>
</job>