Database Configuration Tables
The following database configuration tables are used by Web Switching Management to store configuration settings related to switching sheets and safety documents.
SWMAN_EVENT_ASSOC_TYPE
This table maps the event association types to names. Projects should only change these records if they wish to change the names of the associations.
SWMAN_SAFETY_TYPE_ACTIONS
This table maps the various types of step actions that can be associated to each safety document type. For instance CONDADD/hold actions can only be associated to HOLD documents, which DDS/OPEN operations can be associated to HOLD, CLEAR and HOT safety documents. This table controls these association rules.
SWMAN_SAFETY_TYPES
This table defines all the different types of safety documents configured for a project. Product configuration includes HOLD, Clearance, Informational, HOT, Delegated Control, and Warning safety document types. This table defines the following for each safety document type:
• The JBot tool panel and dialog that should be displayed when loading a safety document of this type.
• The numbering pool the safety document should use when generating unique document numbers. Product is configured to have each document type get their unique document numbers from separate numbering pools.
• The short description of each safety document type.
SWMAN_SHEET_CATEGORY
This table defines the list of sheet categories that every sheet type has to inherit from. Projects should not have any reason to alter the records in this table as they are pre-defined. The table should only be used to look up the description for each of the sheet categories. For instance, all sheets of category PLANNED will generate planned events when completing switching steps that impact customers. Each of the categories has pre-defined rules that define how the switching sheets should behave.
SWMAN_SHEET_CLS
This table defines the types of switching sheets configured for a project. This table defines the following for each switching sheet type:
• The sheet category the sheet type should inherit from.
• The JBot tool panel that should be displayed when loading a sheet of this type.
• The display order of the sheet types in the New Switching Sheet dialog.
• The numbering pool the sheet should use when generating unique sheet numbers. For instance Planned and Emergency sheets get their sheet numbers from the same numbering pool.
• The description of each sheet type. This description is displayed on the New Switching Sheet dialog.
SWMAN_STEP_STATE_MAPPING
This table is used by FLISR to map step state keys to a value of 0, 1, 2, or 16 where:
• 0 indicates that the step has no state
• 1 refers to any step in a completed state
• 2 is in reference to instructed states.
• 16 indicates that the step is deleted.