Request for Proposal rfp-scl-3440




Yüklə 190.51 Kb.
səhifə1/8
tarix20.04.2016
ölçüsü190.51 Kb.
  1   2   3   4   5   6   7   8

RFP-SCL-3440



City of Seattle
Request for Proposal

RFP-SCL-3440

TITLE: AMI Integration and Configuration System Integrator

Closing Date & Time: 05/22/2015 @ 3:00 PM PST

TABLE 1 – SOLICITATION SCHEDULE


Solicitation Schedule

Date

RFP Issued

04/24/2015

Optional Pre-Proposal Conference

04/29/2015 @ 1:00 PM PST

Deadline for Questions

05/15/2015 @ 4:00 PM PST

Sealed Proposals Due to the City

05/22/2015 3:00 PM PST

Interviews, if conducted*

Week of June 15, 2015

Announcement of Successful Vendor*

July 3, 2015

Contract Award*

August 15, 2015

* Estimated Dates
The City reserves the right to modify this schedule at the City’s discretion. Notification of changes in the response due date would be posted on the City website or as otherwise stated herein.

All times and dates are Pacific Time.
PROPOSALS MUST BE RECEIVED ON OR BEFORE THE DUE DATE AND TIME AT THE LOCATIONS SHOWN IN SECTION 12.8 BELOW

MARK THE OUTSIDE OF YOUR MAILING PACKAGE INDICATING RFP-SCL-3440

NOTE: By responding to this RFP, the Vendor agrees that he/she has read and understands the requirements and all documents within this RFP package.

  1. INTRODUCTION


Seattle City Light (SCL) invites interested Vendors to submit their proposals for an AMI Integration and Configuration Project (AMISI) which includes the configuration and integration of Oracle’s Meter Application Suite, including MDM (Meter Data Management), SGG (Smart Grid Gateway) and ODM (Operational Device Management) solutions, with SCL’s information system landscape, that includes but is not limited to, an AMI (Advanced Metering Infrastructure) which has not yet selected, and Oracle CC&B.

Specifically, SCL is seeking from Vendors, proposals that include specifically requested information, description of services, and price quotes as they relate to SCL’s strategic technology goals of integrating an AMI solution into the enterprise which will support data collection and billing from AMI meters and enable the many benefits available from AMI. These benefits include remote disconnect, prepayment, outage management, customer data presentation, distribution grid optimization and enhanced utility processes and implementation of a meter asset system (ODM) to support the maintenance and configuration of the new AMI devices. The proposal shall include pricing for all services as described in Section 4 herein

SCL desires to partner with the most appropriate Systems Integrator within its financial means from a qualified vendor. SCL prefers to select an experienced service provider who has implemented the metering applications (MDM, SGG and ODM) integrated with an AMI technology at other similar agencies and is proven to work collaboratively and effectively.

SCL seeks a vendor that provides an effective and carefully structured approach to implement the Metering Application Suite and integrate the systems and business processes. In this context, implementation refers to all efforts required to provide a complete and functioning system and will prepare SCL to use it effectively. This includes configuration and requirements workshops, detailed design, interface development, software integration, designing minimal software modifications, testing, training, conversion assistance, end user and technical documentation, project management, change management and post-implementation warranty support.

SCL intends to award to the highest ranked vendor that will assume financial and legal responsibility for the contract. Proposals that include multiple vendors must clearly identify one vendor as the “prime contractor” and all others as subcontractors.

  1. PURPOSE


The purpose of this RFP is to solicit proposals from qualified systems integration firms to serve as the primary responsible party to provide System Implementation and Integration services to configure the Oracle Meter Application Suite (MDM, SGG and ODM) applications as well as the Oracle Utilities analytics products (Meter Data Management Analytics and Operational Device Analytics) to support AMI meters and resulting meter data and to integrate with SCL’s AMI solution (an RFP for AMI technology has recently been issued with the expectation to select an AMI vendor by April, 2015) and SCL’s meter testing systems. SCL has already initiated its “NCIS Project” to replace its current CCSS application with the Oracle CIS Solution of CC&B, MDM and SGG to support legacy meters and meter reading from Itron MV-90 and Itron FCS for water and electric meters. SCL requires the enhancement of the MDM and SGG and the implementation of ODM to utilize all of the capabilities and features of the AMI technology including AMI meter asset management, real-time meter data collection, real-time meter events and alarms, voltage measurements and alerts, outage detection, remote disconnect and remote configurability. The AMISI schedule will overlap the NCIS Project schedule and the AMISI will leverage designs and configurations implemented within the NCIS Project.

The implementation services will enable SCL to support the deployment of AMI meters, the synchronization of the AMI meter asset and installation information across the enterprise information systems and the collection, processing, storage and billing from data from each installed AMI meter.

The overall System Integration services required are outlined in requirements described herein. The final scope, cost, and timing will be defined in detail in the Statement of Work to be developed as a part of the contract negotiation process.

SCL will automate all of its electric meters and customers with an AMI Technology, and expects the configuration and integration activities covered by this RFP, to support the following functions:



  • Automated Meter Reading for Electric Meters

  • Customer Service Processes (AMI Control, Individual Meter “Pings”, etc.)

  • Meter-to-Cash Processes for Commercial and Residential Metering

  • Field Services

  • Meter Data Collection

  • Outage Management

  • Volt-Var Optimization

  • Engineering Analysis

  • Remote Turn On and Off/ Remote disconnect

  • Prepayment

  • Web Presentment of Commodity (Energy or Water) Usage Information to Customers

  1. Background

Seattle City Light is a vertically integrated, electric and water utility owned and governed by the City of Seattle serving approximately 1,000,000 people. SCL’s service territory totals about 131 square miles. It includes 387,715 residential, commercial and industrial customer accounts within Seattle city limits and adjacent suburban cities and unincorporated King County. The service territory is urban including: high density housing in apartment buildings and condominiums clustered in a number of urban cores, especially in downtown Seattle, and single family homes; high rise, high density commercial cores; and several high density technology and industrial corridors. Table 3-1 includes summary information about SCL’s service area and customer base.

Table 3-1: Current Facts about SCL (for the year ended December 31, 2013)

Item

Description

Service Area (Net Land and Water)

131.31 square miles

Cities Served – Seattle & Suburban Cities

9

Population

750,200

Total Electric Retail Customers

  • Residential

  • Non-residential

398,858

359,079


39,779

Annual kWh Sold

  • Residential

  • Non-residential

KwH’s (in 000’s)

3,073,405

6,297,591


Total Number of SCL Distribution Substations

14

Number of Electric Meter Points

~ 426,000

Total Water Meters

  • Residential

  • Non-residential

192,611

163,000


27,000

Meter Growth Rate (average)

~ 2% per year

SCL is a financially solvent department of the City of Seattle. SCL management is responsible for day-to-day operations under oversight from the Mayor and City Council.

SCL has procured the Oracle CC&B and Metering Application Suite products and system integration services to replace the current billing system (CCSS) which was implemented on April 2, 2001, and provides a customer information and billing system for electrical services (SCL) and for water, wastewater, solid waste services (SPU). The design, configuration and testing of this new system will support SCL’s ability to read and bill from the existing meters using manual meter reading functions. This system integration project (The NCIS Project) is scheduled to complete October 6, 2015.

SCL has recently completed the procurement process for AMI technology, including electric meters, communications infrastructure, an AMI HeadEnd System and professional services.

This systems integration project will enable the benefits of AMI, including, but are not limited to: increased service and billing options such as flexible billing schedules (monthly versus bi-monthly) and day of the month billed; near real-time consumption information and an ability to reduce energy closer to real-time; more accurate meter reads when opening and closing accounts; greater conservation information and tools; automated notification to the utility when there is a service outage and when service is restored; and greater opportunities for net metering, distributed generation, and support for electric vehicles.

This Request for Proposal (RFP) is intended to secure the professional services of a firm with implementation experience in the Oracle Metering Application suite and integration with any AMI technology. We seek vendor responses that meet our requirements specified in Section 4. Vendor Response Forms may be found in Section 12 to assist you in creating a consistent response to support our AMI System Integrator RFP Evaluation Team.

Single Award: With this solicitation, the City intends to award one contract to the highest ranked vendor and does not anticipate award to multiple companies. Regardless, the City reserves the right to make multiple or partial awards.

SCL reserves the right to determine and pursue the best strategy to support integration of the AMI solution with other SCL legacy solutions.



4. System Integration Requirements
SCL will be starting the integration and configuration of its information systems to support AMI and has identified the required services. The Integrated Solution should meet the following requirements (functional and non-functional have been identified):
4.1 Solution Architecture
SCL is implementing the Oracle ODM and Oracle Analytics products and enhancing the configuration of the MDM and SGG and requires the integration of the AMI solution with these systems as well as other existing utility systems. The Systems Integrator must have experience with the configuration of Oracle MDM, SGG and ODM and the integration of these systems with all of the systems shown. The diagram below is a tentative representation of the solution architecture for SCL:

The integration of SGG with the Oracle NMS is shown in the solution architecture, but is not within the scope of the services and requirements to be provided by the AMISI. The integration of the Meter Installation Vendor (MIV) work management system with Oracle CC&B and the configuration of CC&B to support the mass installation of AMI meters are shown in the solution architecture, but are not within the scope of the services and requirements to be provided by the AMISI.


4.2 Integration Functional Requirements
The proposed AMI System Integration (AMISI) Project must include the following:

1) implementation and configuration of Oracle’s ODM (Version 1.1) application,

2) the implementation and configuration of Oracle’s Meter Data Analytics and Operational Device Analytics applications,

3) the configuration of Oracle’s MDM (Version 2.1 SP2) and SGG applications and,



4) the integration of these applications to meet the requirements described below:


    4.2.1 Meter Asset Management Functional Requirements

    • The ODM will be the repository for all electric metering devices, including current and potential transformers (CT and PT) and AMI communication network equipment.

    • The AMISI must migrate and convert the electric metering device information presently maintained in SCL’s initial implementation of CC&B, as well as maintained in SCL’s proprietary system (CLAMS – City Light Asset Management System) into the ODM.

    • The AMISI must support the mass receipt (up to 5,000 AMI meters per day) and the update of SCL’s implementation of CC&B and MDM with the necessary asset information to complete meter reading and billing.

    • The AMISI must integrate with the AMI Meter Manufacturer to receive meter shipping and testing information for new and refurbished AMI meters.

    • The AMISI must integrate and configure ODM to receive and store the AMI meter test data and asset status as received from AMI meter manufacturer, or as captured by SCL’s meter testing systems, including the WECO test bench or SCL’s selected Meter Shop Management System.

    • The AMISI must integrate and configure ODM to receive and maintain AMI meter status as reported from SCL’s implementation of CC&B and MDM.

    • The AMISI must configure ODM to track and manage the warranty status of all AMI meters.

    • The AMISI must configure ODM to track and manage the RMA (Return Material Authorization) process as AMI meters are found defective and returned to the manufacturer for repair or replacement.

    • The AMISI must configure ODM to store, monitor and update the firmware versions and configuration of the AMI meters, including the metrology firmware, the communication firmware and the HAN firmware as is appropriate for each meter received by SCL.

    • The AMISI must configure ODM to manage SCL’s sample and periodic test program, including, but not limited to, the selection of a sample population of meters, the receipt and storage of sample test results as reported by SCL’s meter testing systems and the reporting of compliance with SCL’s testing standards for sample testing.

    • The AMISI must create queries and extracts to provide PeopleSoft with asset information necessary for financial account.

    • The AMISI must configure ODM to support tracking of meter asset location such as warehouse, storeroom, and truck by bar code scanning.

    • The AMISI must implement and configure the Operational Device Analytics application using the OBIEE framework.

    • The AMISI must create up to 5 custom reports presently provided by CLAMS, including meter retirement report.

    • The AMISI must support SCL to correctly size the servers and database for Operational Device Analytics.


4.2.2 AMI Meter Reading

    • The AMISI must integrate and configure the SGG AMI Productized Adapter, and if required, extend the SGG AMI Productized Adapter or develop the SGG ADK, with the AMI HeadEnd System (AMI HES) to support all existing interfaces and functionality, including, but not limited to:

      • Provisioning of the AMI HES for new, removed and changed AMI meters

      • Provisioning of configuration change requests

      • Receipt of register, or scalar, reads

      • Receipt of interval, or load profile, data

      • Receipt of voltage measurements

      • Request for register reads and interval data

      • Receipt of real-time and historical events and alarms

      • Request for power status (e.g. Meter Ping)

      • Request for integrated disconnect switch status

      • Request for demand reset

      • Validation of successful demand reset

    • The AMISI must configure MDM/SGG to identify new AMI meters and provision the AMI HES with the necessary information to allow the AMI HES to configure the meter and communications as required for each electric meter type and application.

    • The AMISI must configure MDM/SGG to identify removed AMI meters and provision the AMI HES with the necessary information to allow the AMI HES to remove the AMI meter from its network management.

    • The AMISI must configure MDM/SGG to identify retired or archived AMI meters and provision the AMI HES with the necessary information to allow the AMI HES to archive the AMI meter from its system.

    • The AMISI must configure MDM/SGG to identify necessary configuration changes to the AMI meter, as requested by CC&B, MDM, ODM or other SCL systems and provision the AMI HES with the necessary information for the AMI HES to update the configuration of the AMI meter as necessary to capture and deliver the required metering data and events.

    • The AMISI must configure MDM/SGG to validate the correct provisioning of the AMI meter by verifying the AMI HES is delivering the proper measurements and data and, based on configurable rules and validations, notify CC&B and MDM that the AMI meter is commissioned and suitable for AMI billing.

    • The AMISI must configure MDM/SGG to identify metering data and events from AMI meters which are not yet provisioned (unknown meters) and store such data until the meter is known to MDM and provisioned at which time the AMISI will reprocess the meter data.

    • Newly installed AMI meters will be manually read using SCL’s legacy processes, configurations and integrations until such time as the MDM validates the meter, or groups of meters, are suitable for AMI billing and should be cutover. The AMISI must work with the SCL NCIS project team to ensure that CC&B and MDM are configured to seamlessly transition the meter, or groups of meters, to AMI billing.

    • The AMISI must report on the installation, provisioning and commissioning process to support the deployment of AMI meters to show AMI meters, by Route, that are installed, successfully provisioned and successfully commissioned (cutover to AMI billing) and identify any exceptions as an AMI meter fails to transition this process.

    • The AMISI must configure MDM/SGG to identify meter data and meter events from meters not yet provisioned (unknown meters) and store this data until such time as the AMI meter is known to the MDM through synchronization with CC&B and the meter is provisioned, and then the AMISI must automatically process and validate the meter data and events.

    • The AMISI must develop and apply a tool, if not supplied by Oracle, for the validation of data synchronization between CC&B, MDM, ODM and AMI HES.

    • The AMISI must configure new VEE rules for the validation and estimation of scalar reads from the AMI meters.

    • The AMISI must configure new VEE rules for the validation and estimation of interval data from the AMI meters.

    • The AMISI must configure new VEE rules to identify all supplied scalar and interval status flags to ensure that estimates utilize all available data to estimate correctly and do not rely on events.

    • The AMISI must configure new VEE rules to minimize the number of ToDos and manual interaction with the MDM.

    • The AMISI must configure the MDM to validate scalar reads and interval data upon receipt from the AMI HES.

    • The AMISI must configure the MDM to estimate missing or invalid scalar reads as soon as the missing reads are identified and no less often than daily.

    • The AMISI must configure the MDM to estimate missing or invalid interval data as soon as the missing data is identified and no less often than daily.

    • The AMISI must configure the MDM to receive and process all metering data supplied by the AMI HES.

    • The AMISI must configure the MDM and SGG to request scalar reads and/or interval data from the AMI HES or the AMI Meter as requested by CC&B for the purposes of display of the measurements and reads to the Call Center representatives.

    • The AMISI must configure a report or dashboard to summarize AMI meter reading performance, real-time status and issues.

    • The AMISI must configure a report or dashboard to summarize AMI meter data VEE status and issues.

    • The AMISI must implement and configure the Meter Data Analytics application under the OBIEE framework.

    • The AMISI must support SCL to correctly size the servers and database for Meter Data Analytics.

    • The AMISI must configure the MDM and SGG and verify the server and database sizing to support the receipt, processing and storage of:

      • Hourly retrieval and delivery of 15-minute intervals for 3 load profile channels with a granularity of 1Wh and 0.1Volts from 390,000 electric meters

      • Hourly retrieval and delivery of 5-minute intervals for 7 load profile channels with a granularity of 1Wh, 1varh, 1VAh and 0.1Volts from 50,000 electric meters

      • Capture and deliver of outage and restoration events from 100,000 electric meters within 30 minutes


4.2.3 AMI Billing

    • The AMISI must configure the MDM to identify and deliver the appropriate scalar read to CC&B for the purposes of scheduled, or periodic, billing.

    • The AMISI must configure the MDM to identify and deliver the appropriate scalar read to CC&B for the purposes of move-in, move-out and other off-cycle billing.

    • The AMISI must configure the MDM to, based on configurable rules, prioritize the use of actual scalar reads over estimated scalar reads for the purpose of billing.

    • The AMISI must configure the MDM and SGG to reset the demand register of the AMI meter on the required cycle read day and ensure that the demand scalar read represents the demand peak for the customer.

    • The AMISI must configure the MDM to calculate and deliver billing determinants calculated from interval data, including, but not limited to, Total KWH, Peak KW (30 minute rolling demand with 5 minute subintervals), TOU, Total kVARh.

    • The AMISI must work with the SCL NCIS project team to configure CC&B and MDM to seamlessly change the configuration of one or more service points to transition from billing from scalar reads to billing determinants calculated from interval data.


4.2.3 AMI Event and Alarm Management

    • The AMISI must configure the MDM to receive, process and store all electric metering events supplied by the AMI HES.

    • The AMISI must configure the MDM to identify specific meter events, or combination of events, and create emails or ToDos for follow up and resolution.

    • The AMISI must configure the MDM to identify specific meter events and automatically generate a request for Field Activity to CC&B.

    • The AMISI must configure reports or dashboard to view event status and issues.

    • The AMISI must configure SGG to identify and forward, via standard MultiSpeak interface, outage and restoration alarms in preparation for integration with the Oracle NMS.

    • The AMISI must configure SGG to receive requests for power status, via standard MultiSpeak interface, initiate a request for Meter Ping to the AMI HES and response to the requesting application with the results.


4.2.4 AMI Disconnect

    • The AMISI must configure the MDM and SGG to receive requests for disconnect or connect requests from CC&B

    • The AMISI must configure the MDM and SGG to execute and validate the operation of the disconnect switch of the AMI meter through the AMI HES.

    • The AMISI must configure the MDM and SGG to retrieve the status of the disconnect switch of the AMI meter through the AMI HES.

    • The AMISI must create reports or dashboard to review the performance of the disconnect and reconnect operation of the AMI meters.


4.3 AMI Non-Functional Requirements


  • The AMISI must, where appropriate, utilize IEC 61968-9 / MultiSpeak 3.0 standards for integration with external systems.

  • The AMISI must validate and demonstrate the implemented configurations and integrations meet the performance requirements of SCL’s business processes.

  • The AMISI Project must be executed in parallel with and in coordination with the ongoing NCIS project.

  • The AMISI must configure and enable the MDM and ODM to allow easy integration with engineering and distribution applications, such as TLM (Transformer Load Management) and Load Analysis, for the purpose of extraction in support of the distribution network analytics for the purpose of planning and operations.

  • The AMISI must provide a suggested Best Practices methodology for operation of the MDM, SGG and ODM based upon their operational experience.


4.4 AMI System Integrator Services Requirements
SCL requires the following professional services to be provided in addition to the implementation of the AMISI:


  • Program Management and Administration

    • Develop and maintain a detailed project plan and controls for the implementation and acceptance of the AMISI Project and all integration necessary to fully integrate with the AMI technology after award. This includes implementing procedures for project control, project tracking and reporting of progress

    • Scope and change management

    • Issue and problem management, including escalation as necessary

    • Cost and budget managements

    • Risk management

    • Manage project resources and identify external resource requirements and issues.

    • Project meetings and reporting to review overall project status, milestones, issues, problems, accomplishments, schedule, resources, action items, and provide other relevant observations and advice regarding critical milestones.

    • Assist in the ordering and sizing of any applicable servers and databases required to support SCL’s AMISI Project requirements. Recommend configuration, and provide acceptance of the proposed server environment and associated networking and storage systems as provided by the City. This includes all hardware and system software required to support the development, test, training, production (high availability), and possible disaster recovery environments within specified service levels and a schedule of upgrades to the environment to support various stages of the development effort leading up to production operation.

  • ODM Installation. Installation training and documentation services, which focus on implementation of the database, design configuration of the application environments, and certification of the proper baseline application(s) installations for all environments and associated customization and upgrades to the baseline applications.

  • OUA for MDM (Meter Data Analytics) and OUA for ODM (Operational Device Analytics) Installation. Installation training and documentation services, which focus on implementation of the database, design configuration of the application environments, and certification of the proper baseline application(s) installations for all environments and associated customization and upgrades to the baseline applications

  • Requirements Workshops and documentation: Vendor should conduct workshops with SCL lines of business to establish detailed functional, integration and architecture requirements for the ODM, MDM and SGG and its implementation and document these requirements and configurations. These workshops should include an assessment and recommendation for upgrades and service packs which are required to the ODM, MDM and SGG products to support the required functionality. These workshops should include fit/gap Analysis of Systems and Business Processes, Best Practices recommendations, Possible KPIs and desktop analytics, To Be Processes, and Prototyping utilizing Oracle URM’s where possible.

  • Assist in setup and configuration of Test and Production environments. SCL requires the creation of a test environment of the hardware client and server software configuration at SCL’s facilities. The QC environments will emulate the ultimate production system. The respondent must be able to assist SCL in specification and creation of the test and QC environments. SCL will acquire and configure these environments.

  • Testing. SCL requires on-site system and acceptance test conducted on the Test environment. The objective of these tests will be to validate that the AMISI integrations and configurations meet the defined SCL requirements. All SCL systems will utilize High Availability configurations and the testing should support this configuration. The Vendor must provide and support the performance of test procedures, any applicable simulation and monitoring methods to demonstrate proper functioning of the MDM, ODM and SGG with SCL’s systems through both QA testing and actual live production. Such support will include the development of the test plans and test scripts, supply of any test harnesses and test data sets, regular testing status reports, final test report, defect tracking and resolution, on-site assistance during the testing to ensure troubleshooting and knowledge transfer that occurs in a timely and efficient manner.

    • Release Management: SCL will be responsible for release management and Vendor will support, as necessary, SCL with Release Management. Vendor will be responsible for coordination of releases and upgrade with the parallel NCIS project.

    • Component testing: Vendor must create and submit a test strategy for conducting component level testing to validate the proper configuration and integration of the systems. Vendor must develop all test scripts and test data and execute all component testing. Vendor must document test results and review the testing and test results with SCL.

    • Integration testing: Vendor must create and submit for approval a test strategy for conducting integration testing. Vendor must develop all test scripts and incorporate additional test scripts requested by SCL after review of the test strategy and test scripts. Vendor must develop the test data sets and conduct, with cooperation of SCL, the integration tests. Vendor must document all test results and review the testing and test results with SCL.

    • Acceptance testing: Vendor must create and submit for approval a test strategy for conducting acceptance testing. Vendor must submit suggested test scripts to SCL for inclusion into SCL’s overall test strategy. SCL will conduct user acceptance testing with support from Vendor as necessary to complete the testing.

    • Performance testing: Vendor must develop all test scripts and incorporate additional test scripts requested by SCL after review of the test strategy and test scripts. Vendor must develop the test data sets and conduct, with cooperation of SCL, the performance tests. Vendor must document all test results and review the testing and test results with SCL.

  • Training and documentation. Vendor must provide appropriate “As Built” documentation for the configurations and integrations. Vendor must provide a plan to properly train specified utility internal personnel how to maintain and operate the ODM, MDM and SGG. Vendor should include a description and syllabus for all available and future training courses. A training and education program (the training plan) will be developed and delivered to SCL for approval. The approved education program shall be delivered to all users of the system, including primary, secondary, and casual users. Vendor staff delivering training must be very knowledgeable with the pertinent AMI solution products (ODM, MDM, SGG, etc.). A trainer with no prior product expertise to deliver this training is not acceptable. This may be accomplished using a combination of delivery methods, including classroom training courses, computer based training, personal practice time, Internet based training, etc. Additional training shall address training needs during and immediately following Production Cutover to the new system for “refresher” training as needed.

  • Business Readiness. These services focus on an assessment of SCL’s readiness to implement and operate the AMI solution successfully in support of the meter life-cycle, which includes the ability to install and exchange meters, conduct service work, read meters, process consumption, produce bills, disconnect service and validate power status. Business readiness will focus on assessing the AMI System Integration Project to ensure that it has the required business processes, organizational structure, staffing levels and operational rules in place to support SCL’s business environment.

  • Organizational change management. Vendor must lead workshops to redesign and document the “to be” business processes, using BPM2.0, associated with managing AMI meters and AMI meter data using the core capabilities of the MDM and ODM. Vendor must be responsible for the knowledge transfer by training SCL personnel in the new business processes and assisting SCL with identifying and implementing the organizational changes necessary for the new business processes and systems. Expected deliverables include identification and documentation of current business processes that will not change as well as the “to be” business processes, all to be implemented with the new AMI capabilities. The business process documentation shall include detailed process flows organized by operational functions and identification of benchmarks to measure business process improvements and process design recommendations.

  • Go Live Support. Vendor must develop and submit a work plan and schedule covering the go-live weekend and subsequent support activities to support the rollout shall be developed. This plan/schedule identifies all of the business and technical activities that must occur leading up to Production Cutover and all of the business and technical activities that must occur after Production Cutover. The plan identifies dependent tasks and assigns responsible resources and shall be verified by the vendor utilizing a desk walkthrough process. This activity focuses on executing the go-live plan/schedule, which moves the City to the new ODM, analytics solutions and enhanced MDM and SGG applications. This Production Cutover can occur over a long 3-day weekend or any other similar scheduled downtime

  • Warranty Support. A stabilization period of 6 months is anticipated. During this stabilization period, the system is in production operation. The Vendor shall be focused on fixing production problems with the AMI Integration and Configuration Project. Monitoring system use and how well the new business processes are executed is also expected during this period. A successful stabilization period shall occur prior to Final System Acceptance.


4.5 AMI Services Pricing
This project will be performed in two phases. Vendors shall provide initial pricing for each phase.
The City’s intent is to have the selected Vendor provide both Phase I and Phase II work. However, should the Price Proposal for Phase II be unacceptable to the City for any reason, the City reserves the right to explore other alternatives for Phase II such as: bidding Phase II as an independent body of work utilizing Phase I deliverables or rebidding the entire requirement (Phase I and II).
Phase I will consist of the following:


  • The Vendor will provide the City with an initial pricing quote and a clear statement of work to be performed to ascertain the time and materials costs required to perform the requirements definition. The selected Vendor will work with the SCL AMI Project team and the NCIS team to define the business and technical requirements for the AMI System Integration project. The Vendor will also, with support from the SCL IT organization, build a parallel development environment, including the new ODM, Meter Data Analytics and Operational Device Analytics applications work.

Phase II will consist of the following:




  • The Vendor will provide the City with an initial pricing quote for Phase II. Upon completion of the requirements and business process definition work (Phase I), Vendor will develop and submit a final fixed cost proposal to accomplish the full requirements for the AMI System Integration Project (Phase II).

The total price for the System Integration work (Phase I + Phase II) shall not exceed the initially proposed pricing by more than 20%, unless such variance can be associated with a change in scope or significant requirements change identified during the Requirements Definition and is approved by the City. The City will, at this point make a determination as to whether to accept the Contractor’s proposal for Phase II.


Should the City accept Contractor’s proposal for Phase II Integration Services, City and Contractor will execute Work Order 2 for the integration and develop a mutually acceptable payment and deliverable schedule. The mutually agreed-upon Work Order 2 shall serve as Contractor’s notice to proceed with the AMI integration described in the specifications.

5. MINIMUM QUALIFICATIONS

The following are minimum qualifications and licensing requirements that the vendor must meet in order for the proposal submittal to be eligible for evaluation. The City requests a one-page or appropriate-length document as part of the proposal response, to clearly show compliance to the minimum qualifications. The RFP Coordinator may choose to determine minimum qualifications by reading the single document alone, so the submittal should be sufficiently detailed to clearly show how the minimum qualifications are met without reviewing any other material. Those that are not clearly responsive to the following minimum qualifications shall be rejected by the City without further consideration:




  1. Vendor must have been in the business of configuring and integrating MDM and Asset Management systems with AMI technology, including all requested services and variations thereof, for at least 3 years.




  1. Vendor must have at least two (2) successful implementations of the Oracle MDM (Version 2 or higher) and SGG where the solution is fully integrated with an AMI technology (full integration with an AMI technology includes support for all AMI provisioning and cutover, AMI billing, connect and disconnect, AMI event management) and more than 50,000 AMI meters. Vendor should include a brief description of the AMI technology integrated with the solution and how the MDM solution required enhancement or configuration to address specific shortcomings or benefits of the AMI technology.




  1. Vendor must have at least one (1) implementation of the Oracle ODM application. In recognition of the newness of the Oracle ODM application, Vendor may submit relevant information and experience gained from training and internal implementation of the ODM product. Vendor should include a brief description of the AMI technology integrated with the solution and how the ODM solution required enhancement or configuration to address specific shortcomings or benefits of the AMI technology.



  1   2   3   4   5   6   7   8


Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©www.azrefs.org 2016
rəhbərliyinə müraciət

    Ana səhifə