How to enable alarming new samples in SPC chart node?
Article ID: KB0082496
Updated On:
| Products | Versions |
|---|---|
| Spotfire Statistica | 13.1 and higher |
Description
If the SPC charts with alarming node is configured to check control limits (Note: This also applies to check other types of limits or run rules violation), an alarm will be raised whenever there is a sample out of the range of control limits while running the analysis. Alarming new samples only is the default setting in the node, so samples that triggered an alarm previously will not raise an alarm again. In addition, this also requires a CSCustomAlarm table present in the Statistica database. CSCustomAlarm table is automatically created with version 13.1 and higher installer. If you are upgrading from an earlier version, you will need to create it in the database.
If alarming emails are not received as expected, check the following:
1. Whether the node is configured properly to check any type of limits or run rules violations.
2. Whether the Alarm Management tab is configured properly.
3. Whether a proper CSCustomAlarm has been created in Statistica database.
If alarming emails are not received as expected, check the following:
1. Whether the node is configured properly to check any type of limits or run rules violations.
2. Whether the Alarm Management tab is configured properly.
3. Whether a proper CSCustomAlarm has been created in Statistica database.
Resolution
Under Alarm Management, "Log alarm information" and "New alarms only" are both selected by default. More information about those options can be found by hovering over the checkbox. Other configurations about the alarm email are also under this tab including email address, subject and ect.
To log alarm information, this also requires that an administrator has created a CSCustomAlarm table and a valid Sample ID variable is defined.
The following shows column specifications of an example CSCustomAlarm table in the SQL database.
[ID] [int] NOT NULL,
[ANALYSIS_ID] [int] NULL,
[ANALYSIS_NAME] [nvarchar](254) NOT NULL,
[ANALYSIS_NODE] [nvarchar](254) NULL,
[DATA_NAME] [nvarchar](254) NULL,
[CHARACTERISTIC] [nvarchar](254) NOT NULL,
[SAMPLE_ID] [nvarchar](254) NOT NULL,
[ALARM_TYPE] [nvarchar](254) NULL,
[DETAILS] [nvarchar](254) NULL,
[LOG_TIME] [datetime] NOT NULL
To log alarm information, this also requires that an administrator has created a CSCustomAlarm table and a valid Sample ID variable is defined.
The following shows column specifications of an example CSCustomAlarm table in the SQL database.
[ID] [int] NOT NULL,
[ANALYSIS_ID] [int] NULL,
[ANALYSIS_NAME] [nvarchar](254) NOT NULL,
[ANALYSIS_NODE] [nvarchar](254) NULL,
[DATA_NAME] [nvarchar](254) NULL,
[CHARACTERISTIC] [nvarchar](254) NOT NULL,
[SAMPLE_ID] [nvarchar](254) NOT NULL,
[ALARM_TYPE] [nvarchar](254) NULL,
[DETAILS] [nvarchar](254) NULL,
[LOG_TIME] [datetime] NOT NULL
Issue/Introduction
This article talks about how to enable alarming new samples in SPC chart with Alarming node.
Feedback
Yes
No
Powered by
