The Master Control System Database (MCSD) module provides a central source for pre-approved, approved and historical control system parameter settings including alarm system design (rationalization) results. The MCSD is used to configure several modules of AgileOps - Dynamic Management (DM); Event KPI (EKPI) and List Management (LM) modules. The MCSD greatly enhances your ability to audit, rationalize and control by giving you a unified view of all control system settings.
- Multi-user interface
- Role-based security
- View multiple control systems
- Alarm rationalization data collection
- View and modify dynamically managed parameters
- View and modify audited, notifi ed and enforced parameters
- View history of modifications
- Nomination and acceptance of control changes with proper authority
- Boundary management
After AutoDiscovery is installed and implemented on the control system, it will automatically run a comprehensive scan of the entire database and catalog all of the information in AgileOps. After the initial sync with the control system, AutoDiscovery can be set to run on a periodic basis in order to verify that no more points have been added. If it fi nds any changes, it will update the AgileOps database to match what is on the control system. This greatly cuts down on user errors when transferring all of the points on the control system to AgileOps.
In addition to finding new points and tags that have been added to the control system, AutoDiscovery will also document any changes that have been made to existing tags. If these modifications are different than what is already in the database, AutoDiscovery will flag them. A controls engineer can then access the log of changes to the database to ensure that important work has not been overwritten.
Branch and Boundary Management
After gathering all of the tags from the control system, AgileOps offers a user-friendly interface that allows you to view and manage each tag and edit any of its parameters. This allows a user to view any module in AgileOps for a single point. The user can edit any of the alarm parameters through an intuitive interface and add in any comments such as causes, consequences, actions and other alarm data. Any suggested revisions appear in a separate list than the existing database. Before any suggested revisions are implemented, they have to be approved by a user that has permission.
While configuring each branch, the respective boundaries can also be defined. A safety engineer may input a maximum pump safety limit, while the process engineer would input a maximum operating speed. MCSD would catalogue all of these inputted boundary layers and display them in an intuitive format for alarm rationalization members to understand. Once all the boundaries are in place, determining alarm set points, priorities and corrective responses becomes easier to understand and implement.
Each branch in MCSD can also be assigned to a system. These systems are usually designed around pieces of equipment that operate together such as a furnace, a compressor or a pair of towers that run in tandem. These systems can then be dynamically managed individually through the Dynamic Management (DM) module.