User Requirements

Success of any operational system deployment is dependent on the foundational user requirements being met by technology that fits naturally with your operation room dynamics. Our experience tells us that just meeting the requirement is only part of the solution. The other part is designing the DMS or OMS user experience so that the software “acts and behaves” in a way similar to what your operators may have come to expect working with other operational tools deployed in your ecosystem. This means designing user interfaces that speak to your operators, formatting reports that are easy to comprehend, and ensuring that the system provides trusted results that operators can act on.

10ii-fresh-perspective-il

A Fresh Perspective from Your Users

In addition to gathering standard user requirements for DMS functions, we go deeper to define network modeling requirements to achieve a solution that connects with your operators. Our team conducts visual design with your team and identifies how modeling of the vast array of asset types should be performed in DMS. This includes what Transmission Stations, High Voltage Feeders, Switches, Reclosers , Fuses, Station Service Devices, Generators, Distribution Stations, and many other types of equipment must be handled and displayed in DMS. InfraGrid has also developed the requirements on integrating SCADA signals from other utility operations systems into DMS and developed best practices for aligning signals among various systems. Performing these steps makes the solution much more prone to be easily adopted and builds confidence within the program while underway. This also gives vendors a clear picture on what your expectations are and significantly reduces ambiguity between parties.

Requirements definition is the beginning junction of technical work that lies behind on data conversion, migration, remediation and enterprise integration. We take your user requirements and translate them with vendor and IT teams to data requirements and create an inventory of all data parameters required to be propagated to DMS or OMS from your entire IT ecosystem. This activity identifies also performs a gap analysis on data elements that are not captured in your data sources and we help you identify defaults or derivation rules in collaboration with your asset managers.

With data inventory established, we help you define source to target mappings followed by specific integration schemes and architecture to pull data across your data sources to build the network model.