Model 304
Model 304 determines if there is waste, and also the location, fault, type, and measurement of the waste.
To detect waste on a single location
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.
On the Configured Models tab, select Waste from the Model Type list and click Add New Model. The General tabbed page appears along with the Reason Tree Configuration, Identify Input(s), and Scripts tabbed pages.
Click the General tab to select the event type and to set the electronic signature requirements.
Choose the mode by which the waste event will occur.
Time based waste: Waste event is not tied to an event.
Event based waste (Exact time): A production event must exist at the exact time of the waste event to create the waste record. Waste record Event_Id is populated.
Event based waste (Exact time – create timed waste if event not found): A production event must exist at the exact time of the waste event to create the waste record. If there is no production event then a time-based waste record will be created.
Event based waste (Next closest event): The waste record will be linked to the next closest production event on the unit.
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).
optional: Type the group number in the Model Processing Group box. The Model Processing Group number can be up to six digits.
optional: In the Extended Information box, type additional information that may be useful. This is not used on any reports or displays.
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.
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.
optional: Select Automatically Add Missing Faults to add faults if the fault from the fault tag does not exist in the Plant Applications database.
Click the Reason Tree Configuration tab to associate reason trees and faults to the waste event, and create waste measurement conversions.
Click the Waste Locations tab to associate reasons to the waste event.
Select the production unit. A message box appears asking if the waste event is time-based.
Click Yes or No. The type of waste event is automatically entered under the Association Type column. The Tree Selection dialog box appears and three buttons are displayed on the toolbar:
Assign Cause Tree,
Assign Action Tree, and
Enable Research.
Select a reason tree and click OK. The selected reason tree is listed under the Cause Reason Tree column.
Click
Assign Action Tree to assign an action reason tree. The Tree Selection dialog box appears.
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.
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 waste events. Enabling research allows the user to identify a site user as the person responsible for researching the waste event and to set the research as closed or open.
Click the Fault Translation tab to associate a fault to the waste event.
Click Add. A new row is added under Fault Translation For Detection Model Output.
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.
In the Fault Name column, type a name for the new fault. Fault names must be unique on this production unit.
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.
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.
Click the Conversion/Types tab to add units and conversion factors to the waste events.
Click Constant, type a description in the Name box and type a conversion value in the Value box. The conversion value is used to convert the waste value to the correct unit of measure used for waste events for a specific production unit.
– OR –
Click Specification, to assign a specification variable value as the Value entry. This allows for the use of different conversion factors on a product-specific basis for a given name.Under Waste Types, type a new waste type. Waste types describe the various types of waste that can occur and can be selected or automatically used to define the type of waste that is being measured or calculated for a waste event.
Click the Reason Shortcuts tab to create a shortcut for use on the Waste display.
Click
Insert Input. A new row is added.
Under Shortcut Name, type the name of the shortcut. This name will be displayed on the right-click menu in the waste display.
Under Time, type the duration, in minutes, of the waste event. When the shortcut is applied to a waste event in a waste display, this will become the amount of waste for the event.
Under Location, select the production unit.
Under Reason Level 1 – 4, select the reason levels to apply to the waste event in a waste display. The available reasons are determined by the cause reason tree selected in step 4a.
Click the Identify Input(s) tab to select historian tags for waste inputs.
Under Waste Input Types, select the checkbox next to one or more of the waste input types. A new row is added for each input type selected.
If the tag is to be set as a trigger, select the Trigger check box. A minimum of one trigger tag is required.
Click the
Browse button (located next to the Tag box). The Tag Search dialog box appears. Click Search (you can enter search criteria prior to clicking the button if necessary). Select the tag and click OK.
From the Attribute list, select either Value or Timestamp, depending on whether you want the value or time of the tag to be passed.
From the Sampling Type list, select the type of sampling that is applied to the tag. For more information on sampling types, see Sampling Types.
In the Time Offset box, enter the number of seconds backward from the trigger time that the next value will be retrieved.
For example:
If you have trigger tag A in the list and you also have another tag B that is used as an input in the VB Script, you can specify what the time offset will be for tag B. This would be the amount of time backward from the trigger time that the EventMgr would attempt to get the ’r;Last Good Value’ for tag B. So if tag A changed at 9/28/07 7:00, and you specified a 10 second offset for tag B, then the EventMgr would attempt to retrieve the Last Good Value for tag B starting at 9/28/07 6:59:50.In the Precision box, enter the number of decimal places to keep when reading the Historian tag.
Click the
Insert Input button to add a new input.
Click the Scripts tab to edit sample scripts or write script logic. On each tab, a sample script is provided, which you can use or you can click to write script logic.
The following functionality is available on each tab.Click
. The Script Builder dialog box appears where you can edit the existing script or to write script logic.
In the Script Builder dialog box:
Click
. The Select Alias dialog box appears. Select the Alias and click OK. The Alias letter appears in the Script box.
Click
Check Syntax to ensure you have entered the VB Script correctly.
Click the Waste Logic tab to define waste amounts. "Amount" is the required keyword. Click here for an example.
Amount = Null is used to signify that there was no waste event – exit model.
Click the Location Logic tab to define the waste location using VB Script. "Location" is the required keyword. Click here for an example.
Click the Fault Logic tab to define the fault logic using VB Script. "Fault" is the required keyword. Click here for an example.
Click the Type Logic tab to define waste type logic using VB Script. "WasteType" is the required keyword. Click here for an example.
Click the Measurement Logic tab to define unit of measure logic using VB Script. "Measure" is the required keyword. Click here for an example.
Click
to activate the model.