Department of Public Utilities - Tacoma Power
Energy Management System (EMS) System
Integration and Implementation Support Services
RFPSelectRFBRFQRFISpecification No. PS16-0427F
QUESTIONS and ANSWERS
All interested parties had the opportunity to submit questions in writing by email by 3:00 p.m., Pacific Time, on November 8, 2016. The answers to the questions received are provided below and posted to the City’s website at Navigate to Current Contracting Opportunities / Services, and then click Questions and Answers for this Specification. This information IS NOT considered an addendum. Respondents should consider this information when submitting their proposals.
Question 1:Whether companies from OutsideUSAcan apply for this? (like,from India or Canada)
Answer 1:Tacoma will consider all proposals that meet the requirements of the RFP.
Question 2:Whether we need to come over there for meetings?
Answer 2:Yes, though it’s possible that not all meetings will require on-site attendance.
Question 3:Can we perform the tasks (related to RFP) outsideUSA? (like,from India or Canada)
Answer 3:No.
Question 4:Can we submit the proposals via email?
Answer 4:No. Submittals must be received as detailed in the Request for Proposals page and Section 3.04.
Question 5:Please confirm about the start and end dates of this project?
Answer 5:The OSI project will begin approximately Dec. 2016 and be completed July 2018. The SI will start once selection and contract work is completed.
Question 6:Please share the details of the incumbent or vendor currently providing the same services?
Answer 6:This contract is for new work; there is no incumbent.
Question 7:Please share the dial in details for the pre-submittal conference scheduled on 10/24/2016
Answer 7:Not applicable. Conference in the past.
Question 8:What consultant assisted with the selection of OSI?
Answer 8:No consultants assisted with the selection of OSI. Accenture assisted with the process and methodology of the selection.
Question 9:Reference: Section 5, B1, Custom Functionality, Requirement 1 – Please identify and describe the existing customs in order to estimate the work involved by the SI.
Answer 9:No custom functionality is anticipated.
Question 10:Reference: Section 5, B1, Custom Functionality, Requirement 6 – Please describe the functionality not delivered by the EMS Vendor that is required by Tacoma Power regarding custom configuration of power application functionality not delivered by the EMS Vendor.
Answer 10:Requirement is being removed by addendum.
Question 11:Reference: Section 5, B1, Custom Functionality, Requirement 20 – In reviewing the OSI contract, it looks like they are responsible for processing and importing the database into the new system. What is Tacoma expecting the SI to do with respect to this requirement.
Answer 11:OSI will perform the database conversion and migration of all real-time databases. The SI contractor will be responsible for conversion and migration of the PI Historian database to OSIChronus Data Historian.
Question 12:Reference: Section 5, B1, Custom Functionality, Requirement 27 – The SI RFP states there will be 4 database conversions but the OSI contract has 3 defined. Which is correct?
Answer 12:Requirement is being removed by addendum.
Question 13:Reference: Section 5, B1, Custom Functionality, Requirement 31 – The SI RFP says to Migrate/Build all target symbols, displays but the OSI contract states that OSI is responsible for building/converting the displays. Which is correct?
Answer 13:Requirement is being removed by addendum.
Question 14:A reference to a Point to Point checkout is found on Page 79 of the RFP but it is not clear who will perform this task. Requirement #18 under the database conversion and plan section says a “repeatable process for database conversion is required that does not invalidate point-to-point checkout.” The RACI table on pages 96-98 of the RFP does not explicitly call out the task as well. Will Tacoma perform the Point to Point check out if so, and what level of support is expected from the SI?
Answer 14:Tacoma and the SI will jointly perform the point to point check-out.
Question 15:Of the ~600 displays that require migration to the new OSI EMS. How many SCADA and network applications single line diagrams need to be converted?
Answer 15:Approximately 100 displays are single line diagrams.
Question 16:How many real-time calculations does Tacoma currently have that will need to be migrated?
Answer 16:Tacoma has approximately 1500 real time calculations.
Question 17:From our experience on other similar type projects, OSI performed the dataset conversions from the ABB Ranger platform to the Monarch platform and therefore already have an existing conversion tool. If the SI is responsible for this task, will OSI’s existing conversion tools be available to the SI to do the database conversions? Or, does Tacoma prefer the SI to create a new conversion tool?
Answer 17:OSI will perform the database conversion and migration of all real-time databases. The SI contractor will be responsible for conversion and migration of the PI Historian database to OSIChronus Data Historian.
Question 18:The display migration tasks calls for an automated build process to be used in the display conversion process. Just like the database conversion tasks, we understand OSI may have tools that convert displays from an ABB Ranger platform to the Monarch platform. Will these tools also be available to the SI for this task? Or, is the SI responsible for deploying processes and/or tools to accomplish the task?
Answer 18:OSI will perform the display conversion. The SI is not responsible for this task.
Question 19:On Page 79 of the RFP, Section B under Custom Functionality, the SI is expected to develop and implement all critical functionalities. Can Tacoma provide a list with a brief description of each custom application? Does Tacoma require the SI to develop and/or enhance software applications within the OSI Monarch environment?
Answer 19:No custom functionality is anticipated.
Question 20:In the OSI requirements document recently made available, the Advanced Network and DTS applications are listed as options yet based on Appendix D, it seems Tacoma Power has acquired those options and will be implementing these applications. Can you confirm?
Answer 20:Yes, Tacoma is purchasing both the Advanced Network and DTS applications.
Question 21:Regarding an Issue Tracking System: Is Tacoma going to provide any in-house portal for tracking issues? If not, can the SI utilize a tracking system of their choice including 3rd party open source systems?
Answer 21:No. SI is expected to provide as part of their PMO practice.
Question 22:On page 20 of the RFP, question 8 asks the SI to explain their approach implementing and extending integration standards such as the Common Information Model (CIM). Is Tacoma expecting the SI to describe their approach in implementing the extension of CIM/XML as it relates to CIM network model export/import functions or rather describe the integration approach of CIM/XML message pay loads as it relates to an ESB? Can you confirm and provide additional details surrounding this item?
Answer 22:Integration approach of CIM/XML using application integration middleware (ESB). SI is expected to have proficiency in standards based integration and message exchanges over a common integration layer (IEC 61968-1)
Question 23:Is Tacoma expecting the SI to develop tools that integrate EMS interfaces with the ESB or just expecting the SI to explain their approach in testing those interfaces?
Answer 23:The SI is expected to bring their methodology and implement the EMS interfaces. Also to explain approach to testing including any tools the SI utilizes for integration testing (e.g. load generators, automation scripts, etc.)
Question 24:The RFP indicates the SI will develop test plans based on standard test plans from EMS vendor. Should OSI’s testing procedures not meet Tacoma’s needs, is there an expectation that the SI will create custom test plans to mitigate the gap?
Answer 24:Yes
Question 25:On page 79 of the RFP, the term “Configure system telemetry” is used. Can Tacoma explain what is meant by this term and their expectation of the SI in performing this task?
Answer 25:Perform specific power system configurations that would be defined in the requirements phase. SI shall work with EMS vendor as part of commissioning.
Question 26:Can Tacoma list all OSI applications/products that have been procured for this project?
Answer 26:
The core application/modules include:
- OSI’s monarch Platform
- Graphical User Interface (OpenView and OpenView Lite)
- Supervisory Control and Data Acquisition (OpenSCADA)
- Advanced Alarm Management (Viewpoint)
- Communications Front-end Processor (OpenFEP)
- Inter-control Center Communications Protocol (OpenICCP)
- Calculation & Scripting Subsystem (OpenCalc)
- Historical Recording System (Chronus)
- Real-time and Historical Trending (OpenTrend)
- Automatic Generation Control & Dispatch (OpenAGC)
- Inadvertent Accounting (OpenIA)
- Transaction Management System (OpenTMS)
- Transmission Network Analysis (OpenNET)
- Common Information Model Interface (OpenCIM)
- Equipment Outage Scheduler (OpenEOS)
- Operator Training Simulator (OpenOTS)
- Data Engineering & Maintenance Subsystem (DataExplorer)
- Dynamic Tabular Display Subsystem (Advanced Tabulars)
- Display Design & Maintenance Subsystem (DesignStudio)
- Various interfaces (ODBC, SNMP, Web Services, OATI, EIDE, mapboard controller, etc.)
Question 27:Can Tacoma provide a detailed OSI project schedule that shows all deliverables, deliverable dependencies, and milestones?
Answer 27:Yes, See attached PDF
Question 28:Price Proposal Form (page 35) - Price Proposal Form, Page 35 states that Deliverable 5 is "Testing-Factory" while detailed task breakup for Section 5 Requirement # 43 in Page 82 include all test phases. Please confirm that this item should include the full scope of testing as defined in the RFP Appendix B “literal e” Test Coordination and Quality Assurance.
Answer 28:Full scope of testing.
Question 29:Section 5 B. Requirement 12 (page 78) - How is this different from requirement 7. ?
Answer 29:Requirement 7 is regarding the customized interface design and build. Requirement 12 is regarding the implementation and testing of the interfaces in the environments.
Question 30:Section 5 B. Requirement 22 (page 79) – The generation control database is not called out specifically for migration, is the SI required to configure the power applications for both generation (OpenAGC) and transmission (OpenNET)?
Answer 30:Confirmed the SI will be expected to migrate the generation control database and support the configuration of the advanced applications.
Question 31:Section 5 B. Requirement 34 (page 81) – How many new Custom Dashboards are required?
Answer 31:It is unknown at this time how many Custom Dashboards will be needed. This will be determined during design.
Question 32:Section 5 B. Requirement 40 (page 82) – What testing tool(s) will be used for this project? What experience does TPU have using these tools?
Answer 32:Tacoma Power does not use a testing tool. Tacoma does not have experience with this type of tool.
Question 33:Section 5 F. System Build (page 96) – This is an activity that is expected to be led by the EMS vendor as they own the product development, configuration and patching throughout the life of the project. The SI usually contributes to this. Please confirm that the SI is not responsible for the following vendor activities: EMS Master System, software configuration, software customization, and system configuration?
Answer 33:Confirmed as EMS product vendor scope of responsibility with SI contributing.
Question 34:Section 5 F. Hardware Infrastructure (page 97) – This is an activity that is responsibility of the EMS vendor because they own the product. The SI usually contributes. Please confirm that OSI will be responsible for system architecture
Answer 34:OSI will be responsible for this activity. The SI will contribute.
Question 35:Section 5 F. Software and Tools Installation (page 97) - This is an activity that is responsibility of the EMS vendor because they own the product. The SI usually contributes. Please confirm that OSI will be responsible for installing and configuring all OSI software for each environment.
Answer 35:Confirmed as EMS product vendor scope of responsibility with SI contributing.
Question 36:Section 5 F. Testing (page 97) - Please clarify the meaning of the activity line item under Testing in the RACI matrix “Training Execution Iterations”.
Answer 36:It is expected that training would take more than one cycle to deliver to all attendees.
Question 37:Please confirm what the requirements are regarding Current and Future State Business Process.
Answer 37:Please see the requirements of the Business Process Lead and BP Analyst.
Question 38:Regarding Appendix B, the City’s Standard Professional Services Contract and Non-Disclosure Agreement, will Tacoma provide an editable version of these documents to facilitate potential redlining?
Answer 38:Yes, a MS Word document will be provided with track changes implemented after vendor selection.
Form No. SPEC-230ARevised: 03/13/2007 rk