INTERFACING DMS/OMS/SCADA SYSTEMS WITH ENTERPRISE BUSINESS IT SYSTEMS FOR IT/OT INTEGRATION IN SMART GRID.

Transcription

1 CEATI International Inc. (CEATI) 1010 Sherbrooke Street West, Suite 2500 Montreal, Quebec, Canada H3A 2R7 Website: SMART GRID TASK FORCE (SGTF) CEATI PROJECT No. SGTF RFP INTERFACING DMS/OMS/SCADA SYSTEMS WITH ENTERPRISE BUSINESS IT SYSTEMS FOR IT/OT INTEGRATION IN SMART GRID.

2 CEATI International Inc. (CEATI) invites the submission of proposals to perform research work on the following topic: TITLE Interfacing DMS/OMS/SCADA Systems with Enterprise Business IT Systems for IT/OT Integration in Smart Grid. INTRODUCTION Some leading electric utilities are increasingly interfacing DMS/SCADA Systems with Enterprise Business IT Systems. It would be tremendously beneficial to CEATI member utilities to know the state-of-the-art for such integration. In particular, utilities would like to know the system architecture, applications, databases, information flows among applications, and business intelligence outputs used in executing the utility business. This is especially true when customer choices and services are involved. Quality of Service should also be considered. DMS/SCADA Systems support a number of applications in Smart Grid, including the following: Fault location, isolation and service restoration (FLISR) Integrated volt/var control (IVVC) Advanced Distributed Resource Management (ADRM) or Integrated Dispatch of DER (IDDER) Asset Management & Condition-Based Maintenance Switch Order Management Load & Renewable Resource Forecasting Dispatcher Training Simulator Almost invariably these applications require interfacing with applications and databases at the Enterprise Business IT Systems to realize the full benefit of the real-time applications. For instance, the DMS/SCADA Systems under the FLISR application might have identified a sustained fault at a certain section of a feeder circuit. The applications might have tried different switching operation schemes, but the fault remains. The sustained service interruption calls for a crew to be quickly dispatched to resolve the fault. The DMS/SCADA System would send the location and ID information of the faulted device to the Enterprise Business IT System s Work Order Management System (WMS). The WMS would in turn generate a work order, accessing the Geographical Information System (GIS) to extract the detailed data sheet on the device in question. The WMS would send this work order to the Mobile Workforce Management System (MWFMS), which would determine the most appropriate crew to handle this order. The MWFMS would send that work order, together with a vector map of the feeder topology, to the mobile data terminal on that crew s truck over a wireless data network. Upon arriving at the faulted device, the crew would investigate the root cause of the problem, develop remedial measures, estimate the time to restore services, and send that information to the Customer Support System at the Enterprise Business IT System. Upon the completion of the work order, the crew would send a message that the job has been completed. The crew might also send back to the GIS a revised map of what has been done to resolve the fault. This updated

3 information should be immediately sent to the DMS/SCADA System to provide the most current display of the feeder circuit diagram that is overlaid on the GIS. This is one simplified example of a Use Case showing how a DMS/SCADA System would interface with an Enterprise Business IT System for a particular application. Utilities would like to know the major Use Cases for all major DMS/SCADA System applications and how they interface with an Enterprise Business IT System. Utilities would also like to know what the system architecture should be (e.g., System of Systems, Service-Oriented Architecture) and the use of cloud computing technology. Of course, associated with all these studies, utilities also want to know how the interfaced system architecture can ensure interoperability, modularity (for future additional interfaces) and cybersecurity. In addition, utilities would also want to know the type of data model needed to support such integration, frequency of data updates, and effective processes or governance for such a model. PROJECT OBJECTIVES The objectives of this project are (a) to present a thorough understanding of the interface requirements between DMS/SCADA Systems and Enterprise Business IT Systems for the major DMS applications, (b) to define the most appropriate system interface architecture between the two systems, delineating the associated data flow, the impacted databases, and what and how the associated work flow process might be modified, while taking into account interoperability, modularity, cybersecurity and quality-of-service considerations. SCOPE OF THE STUDY The scope of the study will include the following: Define the major Use Cases for interfacing DMS/SCADA Systems with Enterprise Business IT Systems for the major DMS applications Define the most appropriate system interface architecture between the two systems Define the associated data flow, the impacted databases, and what and how the associated work flow process might be modified Ascertain that the defined system interface architecture accounts for interoperability, modularity, cybersecurity and quality-of-service requirements. POTENTIAL BENEFITS This project would help utilities develop the appropriate system architecture for interface between DMS/SCADA Systems and Enterprise Business IT Systems. This IT/OT (Information Technology/Operations Technology) integration would result in high efficiency and performance gains for electric utilities, both in the operations and in the investment economics aspects. PROJECT STAGING The following tasks should be performed to accomplish the objectives of this project. 1) Define with supporting rationale the major applications supported by DMS/SCADA Systems under Smart Grid, using the list defined in Introduction as a start.

4 2) Conduct a survey of at least three leading utilities to find out how they interface their DMS/SCADA Systems with Enterprise Business IT Systems for their distribution system operations. Ascertain the associated data flow, databases, outputs from different applications, system interface architecture, work flow processes and quality-of- service. 3) Develop the Use Cases associated with how the DMS/SCADA Systems interfaces with Enterprise Business IT Systems in each of the major applications defined in Task 1. 4) Design the system architecture for implementing those Use Cases, taking into account the appropriate data flow from the DMS/SCADA System to the Enterprise Business IT System, the databases involved, the outputs from the applications of each of the two Systems. Evaluate the merits of technologies such as System of Systems, Service- Oriented Architecture Bus, cloud computing. Ensure that the design incorporates interoperability, modularity, cybersecurity and quality-of-service considerations. Define the data model needed,frequency for updating such data, and the governance for such a data model. 5) Identify other likely Smart Grid applications to be supported by the architected system, and revise the design of the system infrastructure accordingly. 6) Determine the appropriate work process changes associated with the architected system. 7) Prepare and give a PowerPoint presentation on the results of all preceding tasks to get comments from the Project Sponsors. 8) Prepare a draft final report on the results of all preceding tasks for review and comment by the Project Sponsors. 9) Prepare a revised final report to reflect comments on the draft from the Project Sponsors. DELIVERABLES The successful proponent is expected to prepare a ready-to-publish report on the results of the investigation and present the results to funding consortium members. The completed report must be submitted for CEATI approval in editable, electronic format (Microsoft Word). In addition, the platform and version should be specified for any software or programs to be developed. Progress reports will also be required on either a quarterly or milestone basis - normally these are scheduled to coincide with the completion of the identified tasks. The successful proponent is also expected to provide the following: - A ten to fifteen (10-15) slide Power Point Presentation. This should be composed of three main sections: 1. The factors motivating the initiation of the work; 2. A description of the main findings; 3. Summary of the conclusions and recommendations for future research. - Contents for the Project s Technical Brief. This is a summary of the report (between 1,250 and 1,750 words), which is published separately by CEATI. Proponents are not responsible for the preparation of a ready-to-print Technical Brief, but solely to provide the contents for the following 4 sections: Background, Summary, Conclusions and Recommendations and 2 figures. 1. The Report Background section should be short (approximately 250 words) and should detail the reasons the work was conducted.

5 2. The Summary section should be approximately 850 words. It must provide a general description of the work program. 3. The Conclusions section should be about 300 words and should provide a general outline of the key results (do not include specifics). 4. The Recommendations section should be about 200 words and should include a description of the potential applications of the results. 5. Contractor should provide at least 2 figures to be included. Please note that all reporting must be submitted in English. If written English is not the author s strong suit, it is recommended that a technical writer be hired to review the document prior to submission. BUDGET AND SCHEDULE The proposal must contain a schedule and a quote of required remuneration for the work in US or Canadian dollars. All prices shall be presumed to be in Canadian dollars (CAD) unless explicitly specified otherwise in the proposal. Proponents responses to this section must include a full breakdown of the budget and schedule, including an indication of rates and hours and the task allocation for the key personnel by task and must correspond to any phases or milestones outlined above. (Please refer to the Proposal Template for more information). It is expected that this project can be completed (draft final report submitted for review and approval) within 6 months of initiation. The proposal must include the names and qualifications of the key individuals who will be involved, as well as the name of the accountable manager. STANDARD AGREEMENT The successful proponent will be required to sign the CEATI Standard Agreement upon project initiation. Submissions must include either pre-approval to the terms, available for download at or identify any specific issues in the submitted proposal. Proponents may also contact CEATI in advance of the proposal submission deadline at projects@ceati.com to discuss any questions or concerns regarding these terms. SIGNING AUTHORITY Proponents shall specify the name, title, and coordinates of their Standard Agreement signing authority. ALTERNATIVE WORKS Proponents shall generally follow the above description of work, but are encouraged to offer alternative works if these alternatives will meet the objectives and provide a better end product to the utilities sponsoring this work. Alternatives shall be fully described including logistics explaining why the alternate works are being offered and the benefits to be realized by the

6 funding utilities. Where alternatives are proposed, separate budgets shall be calculated for each alternative. SUBMISSION OF PROPOSALS The consideration of proposals received will be limited to those who indicate their intent to employ a suitable experienced project team and who possess proper facilities to perform the work. Receipt of this RFP does not necessarily constitute a prior determination by CEATI that your organization has the requisite experience and facilities. The proposal must be properly completed and executed in accordance with the CEATI guidelines available at and shall be submitted to CEATI as an attachment in Microsoft Word at the following website: Be sure to indicate project number SGTF RFP on the submission form. For assistance, please contact us at CEATI is not bound to accept any proposal but any selection will take into account technical merit, qualifications, price and schedule. A proposal may be accepted in whole or in part. A commitment to proceed with the first phase of a multi-phase project does not automatically imply that the work of the subsequent phases will be undertaken. CLOSING DATE FOR RECEIPT OF PROPOSALS Thursday, September 17, 2015, 4:00 pm EST/EDT