Solutions
...
Litmus Production Record Datab...
Interacting with Litmus Produc...
Adding or Modifying an Event definition
7 min
use cases litmus production record database is capable of monitoring tag data for production events and then record these events this does require to setup an event definition which includes what trigger to monitor and what to collect first user can do this either by using applications such as microsoft sql server management studio mssql cli this can also be used for building custom solutions based on applications which allow for an odbc connection such as excel c# net python litmus does provide such as custom solution which can be downloaded from our central portal method execute stored procedure prorec event processeventconfiguration note do learn more about the event monitoring concept and how to define it, please read the document input variables 155,141,239,219,133,114 false true false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type how to use to insert an event, call the stored procedure prorec event processeventconfiguration using the t sql exec or execute keyword and provide the input variables below is an example using t sql in sql server management studio execute \[le productionrecord] \[dbo] \[prorec event processeventconfiguration] @eventnodename = n'downtime', @eventname = n'downtimel1m2', @eventdescription = n'down time recording for asset l1m2', @triggerconditionname = n'startdowntimel1m2', @triggertag = n'l1 machine2 1 mb|isrunning|process value', @condition = n'equalto', @conditionvalue = n'1', @eventprorecitem = n'downtime|main classification|sub classification|faultcode', @isidentifier = 1, @atstart = 1, @itemvaluesource = n'isconstant', @itemvalue = n'unclassified', @calculationtype = null, @timeframestartitem = null, @timeframeenditem = null; result the stored procedure will verify that the provided values are correctly formatted and then create any new node, levels and items or modify existing items the result can be read back from the log table prorec misc log below is an example using t sql in sql server management studio select top (100) \[logid] ,\[logtype] ,\[logprocedure] ,\[logentry] ,\[logtime] from \[le productionrecord] \[dbo] \[prorec misc log] where \[logprocedure] = 'prorec event processeventconfiguration' order by logid desc with the result returned