EMS Change Management System Requirements

            In general a change management system required for the EMS group will be capable of tracking any type of issue or problem related to EMS functions. 

The necessary features will be:

• Preferably Windows based and interface with SQL Server database. 
• Web based client
• Configurable email notification base on issue submission (i.e. issue requires management approval)   
• Customizable
  • Configurable Forms to track different types of issues such as Hardware, OS, Software, Database
  • EMS records can be utilized when creating issues ( this would be useful for tracking database changes )
  • Critical Cyber Asset Lists can be utilized when creating issues
  • User roles to track/define routing and approval requirements
• Reporting
• Search Tools
• Bug Tracking
  • Management of Customer issues
  • Internal problems / issues
• Capable of adding attachments

Desirable by not required features:

• Interface with VSS
• Interface with Areva(Allen’s) transaction logger
• Interface with EMS to monitor system changes for
  • Selcop fields
  • Databases maintained outside of eTerra-Modeler (such as CTGS and Monitored Elements)