Model 210

Model 210 detects downtime on a single location only. The location is either running or not running, depending on the VBScript that you enter. To use this model you must have only one location defined.

To detect downtime on a single location

  1. In the Plant Model, right-click the production unit where you want to detect events and click Configure Events on <production unit>. The Event Detection wizard appears.

  2. On the Configured Models tab, select Downtime from the Model Type list and click Add New Model. The General, Reason Tree Configuration, Identify Input(s), and Scripts tabbed pages appear.

  3. Click the General tab and do the following:

  1. Select Fault on a Single Location (210).

  2. optional: In the Maximum Run Time (Seconds) box, type the number of seconds you want the model to run. The default is 0 (zero), which means the model will not time out. Typically, you will want to limit the run time of the model only if troubleshooting the model (for example, one of the stored procedures is in an infinite loop).

  3. optional: Type the group number in the Model Processing Group box. The Model Processing Group number can be up to six digits.

  4. optional: In the Extended Information box, type additional information that may be useful. This is not used on any reports or displays.

  5. optional: In the Exclusions box, type the values this model is to ignore and not use to trigger the model. Use a comma to separate values.

  6. To require an electronic signature, select the level of authorization from the Esignature Level list. For more information on electronic signatures, please see Using Electronic Signatures.

  7. From the FaultMode list, select one of the following fault modes.

  8. Assign fault at start change = split: The fault is assigned immediately when a new downtime record is opened. If a new fault is passed while the initial downtime record is still open, the downtime records are chained together and the assigned fault is passed in as a split.

  9. Assign Fault @ Start: Assign the fault code when the downtime record is opened.

  10. Assign Fault @ End: Assign the fault code when the downtime record is closed.

  11. Overwrite fault at End Time: Assign the fault code at the beginning of the downtime event when opened and if the fault code changes when the record is closed, the downtime record will be updated to reflect the new fault code.

  1. Select Automatically Add Missing Faults to add faults if the fault from the fault tag does not exist in the Plant Applications database.

  1. Click the Reason Tree Configuration tab and do the following:

  1. Click the Downtime Locations tab to assign reason trees to the downtime event.

  2. Select the production unit. The Tree Selection dialog box appears and three buttons are displayed on the toolbar: Assign Cause Tree, Assign Action Tree, and Enable Research.

  3. Select a reason tree and click OK. The selected reason tree is listed under the Cause Reason Tree column.

  4. Click Assign Action Tree to assign an action reason tree. The Tree Selection dialog box appears.

  5. Select a reason tree and click OK. The selected reason tree is listed under the Action Reason Tree column

NOTE: If you need to create a new action or cause reason tree, click Manage Trees. The Tree Builder dialog box appears where you can create new reason trees.

  1. optional: Click Enable Research. Enabled is displayed under the Enable Research column. Enable Research will enable the Research tab in the Sequence of Events display for downtime events. Enabling research allows the user to identify a site user as the person responsible for researching the downtime event and to set the research as closed or open.

  1. Click the Fault Translation tab to create and assign a fault to the downtime event.

  2. Click Add. A new row is added under Fault Translation For Detection Model Output.

  3. In the Fault column, type a fault value. The fault value must match a value that will be returned by an historian tag (if using model 200) or a fault value identified in a script (if using model 210 or 211). Fault values must be unique on this production unit.

  4. In the Fault Name column, type a name for the new fault. Fault names must be unique on this production unit.

  5. Select the production unit from the Location list. If the production unit has child units configured, the production unit and its child units will be available in the Location list.

  6. In the Reason1 column select a reason from the list. The contents on the list will depend on the reason tree selected on the Cause Reason Trees tab. Depending on how the reason tree is configured, you may select subsequent reasons for Reason2 through Reason4.

  1. Click the Reason Shortcuts tab to create a shortcut that will be available in the downtime display. When the reason shortcut is selected in the downtime display, reasons are automatically added to the downtime event.

  2. Click Insert Input. A new row is added.

  3. Under Shortcut Name, type the name of the shortcut. This name will be displayed on the right-click menu in the downtime display.

  4. Under Time, type the duration, in minutes, of the downtime event. When the shortcut is applied to a downtime event in a downtime display, this will become the amount of downtime for the event.

  5. Under Location, select the production unit.

  6. Under Reason Level 1 – 4, select the reason levels to apply to the downtime event in a downtime display. The available reasons are determined by the selected cause reason tree.

  1. Click the Status Translation Table tab to create a list that is displayed for selection in the downtime display.

  2. Click Insert Input. A new row is added.

  3. Under Status Name, type the name of the status. This will be available from the Status list in the downtime display.

  4. Under Status Value, type a numeric value for the status. The status value acts as an index value for the status and can be used in custom stored procedures; it is not displayed anywhere.

  1. Click the Identify Input(s) tab to identify and select the historian tags used for input.

  1. To determine if the unit is down select an historian tag for the RunTag Tag box.

  2. To determine the location of the downtime select Set Downtime Location. The LocTag row appears.

  3. To determine the fault or root cause, select Set Downtime Fault. The FaultTag row appears.

  4. For each row, click or . The Tag Search dialog box appears.

  5. Select a tag and click OK.

NOTE: You must select at least one tag as the trigger tag. For more information, see Input tags.

  1. Click the Scripts tab to modify the sample scripts, or click and type your own scripts.

  2. For more information and to view two examples of running logic, see Running Logic.

  3. For more information and to view two examples of fault logic, see Fault Logic.

  1. Click to activate the model.

See Also