ARTICLE I: CORE- GENERAL INSTRUCTIONS AND …ARTICLE I: CORE- GENERAL INSTRUCTIONS AND PROVISIONS REQUEST FOR PROPOSAL No. 40641 FOR Grid Ops Situational Intelligence ARTICLE I: CORE-

1

ARTICLE I: CORE- GENERAL INSTRUCTIONS AND PROVISIONS

REQUEST FOR PROPOSAL No. 40641

FOR Grid Ops Situational Intelligence

ARTICLE I: CORE- GENERAL INSTRUCTIONS AND SCHEDULE

RFP Schedule Date

RFP Distributed to Bidders 5/12/2014

Last Day to Submit Written Questions to PG&E 5/19/2014

RFP Responses Due 6/6/2014

Selection of Finalists 6/20/2014

Finalist Interviews (please reserve this date) 6/23/2014

Notifications of Successful/Unsuccessful Bidder 7/11/2014

Target Date for Contract Execution 8/15/2014

New Program Commencement 9/5/2014

Article I: Core – RFP General Instructions and Provisions

1

TABLE OF CONTENTS 1.0 INTRODUCTION ............................................................................................ 1

2.0 PURPOSE OF REQUEST FOR PROPOSAL (RFP) ...................................... 1

3.0 RFP STRUCTURE ......................................................................................... 2

4.0 SUBMITTAL INSTRUCTIONS ....................................................................... 2

5.0 PROCEDURES FOR RESPONDING............................................................. 3

6.0 QUESTIONS AND REQUESTS FOR INFORMATION .................................. 3

7.0 BID PREPARATION ....................................................................................... 4

8.0 EVALUATION CRITERIA ............................................................................... 4

9.0 CONTRACT TERM ........................................................................................ 5

10.0 RESERVATION OF RIGHTS ......................................................................... 5

11.0 SUPPLIER DIVERSITY STATEMENT ........................................................... 5

12.0 SAFETY STATEMENT ................................................................................... 7

13.0 ENVIRONMENTAL STATEMENT .................................................................. 8

14.0 ETHICS STATEMENT.................................................................................... 8

15.0 PROPRIETARY INFORMATION .................................................................... 8

Request for Proposal: Articles I – IV

Article I: Core – RFP

Article I: General Instructions and Provisions

1.0 INTRODUCTION

Pacific Gas and Electric Company (PG&E), incorporated in California in 1905, is one of the largest combination natural gas and electric utilities in the United States. Based in San Francisco, the company is a wholly owned subsidiary of PG&E Corporation. There approximately 20,000 employees who carry out PG&E’s primary business—the transmission and delivery of energy. The company provides natural gas and electric service to approximately 14 million people throughout a 70,000-square-mile service area in northern and central California. Our customers include over 20,000 schools, 3,000 hospitals, 20,000 high-tech companies and 700 military facilities. As the primary natural gas and electric service provider for Central and Northern California, PG&E’s service territory stretches from Eureka in the north to Bakersfield in the south, and from the Pacific Ocean in the west to the Sierra Nevada in the east. PG&E provides electricity to over 4.9 million customers and natural gas to over 3.9 million customers. PG&E is committed to enhancing its supply base to include contractors who can contribute to PG&E’s corporate values, including diversity, safety, environmental stewardship, and corporate integrity. The RFP evaluation process is intended to provide opportunities for successful firms to expand their business with PG&E, new firms to establish business with PG&E, and for PG&E to realize reductions in costs, both internal and external, while experiencing enhanced commitment to corporate values. This will be an exciting opportunity for PG&E and its suppliers – both current and new – to reshape the way we work together and to improve PG&E’s operations.

2.0 PURPOSE OF REQUEST FOR PROPOSAL (RFP)

The purpose of this RFP is to solicit bids for Grid Ops Situational Intelligence. Specifically, PG&E is seeking bids to provide the following:

Grid Ops Situational Intelligence (GOSI) is one of several projects in the Electric Program Investment Charge (EPIC) program. The EPIC program provides funding for applied research and development, technology demonstration and deployment, and market facilitation for clean energy technologies and approaches for the benefit of ratepayers.

The GOSI project will pilot visualization technologies that integrate various data sources and display information on Distribution Control Center video walls and individual computers, as well as computers and handhelds of other distribution and field service personnel. The objective of this GOSI Pilot program is demonstration of a “real-time” data visualization platform which integrates traditionally isolated data sources and presents that information in a form that is easily digestible by end users.

PG&E will use the information submitted in response to this RFP to evaluate and to identify a company with the capabilities, quality, service, and competitive prices to provide high quality services most efficiently and at a superior economic arrangement.

PG&E’s primary objectives in issuing this RFP are to:

Develop mutually beneficial relationships with a best-in-class company,

Establish competitive pricing structures with the selected company,

Develop a multi-year relationship with agreed-upon fixed prices;

Request for Proposal: Articles I - IV

Set mutually agreeable Diverse Supplier sub-contracting goals and a subcontracting plan. The successful Bidder will agree to make good faith efforts to assist PG&E in meeting the goals set in General Order (GO) 156 of the California Public Utilities Commission through the implementation of Contractor’s subcontracting plan. Such good faith efforts will be measured through Performance Scorecard provisions of the Contract.

The parties will define performance standards, metrics, and reporting processes to generate consistent, efficient, and effective results for both PG&E and the successful Bidder. Performance measurement reporting processes will be as specified in the Performance Scorecard provisions of the Contract.

Work collaboratively with the selected company to develop value-added services and processes that focus on reducing costs for both PG&E and the successful Bidder.

PG&E’s overall objective includes implementing an integrated supplier relationship with the selected company(s), continuing the excellent service that PG&E has received to-date while also working collaboratively to reduce costs for both PG&E and the supplier. PG&E challenges each Bidder to propose innovative ideas to improve efficiencies or reduce costs. Such ideas could, for example, include cost savings or efficiency recommendations.

The responses to this RFP will serve as the basis for any agreements and represent a firm offer by the Bidder to provide services to PG&E as detailed in this RFP document.

Additionally, all bid responses will be evaluated and PG&E will conduct negotiations in order to reach final agreements with the selected company. This RFP may be subject to a Two-Step Bidding Process. See Article 8 for additional information.

3.0 RFP STRUCTURE

This RFP is structured into four Articles: This Article I, entitled “Core - General Instructions and Provisions,” provides a description of the RFP structure and bid submittal instructions that are applicable under this RFP. Article II, entitled “Specification,” describes the scope of work (specific conditions) and the General Conditions which will be included in any Contract awarded pursuant to this RFP. Article III, entitled “Questionnaire and Pricing Sheet,” includes the questionnaire to which all bidders must respond and the pricing sheets that bidders shall use in quoting prices.

Article IV, entitled “Bid Forms,” is a collection of standard forms that must be completed and returned as part of each Bidder’s Proposal submittal. Details concerning these forms will be covered in Section 4.0 “Submittal Instructions.”

4.0 SUBMITTAL INSTRUCTIONS

Bidders shall submit their proposal(s) in accordance with the outline shown below. All proposals must be submitted in the exact order described below. REQUIRED SUBMITTALS

Transmittal Letter: Bidder shall acknowledge that the RFP was used in the preparation of its Proposal by returning one signed copy of the “Transmittal Letter.” By signing the Transmittal Letter, Bidder agrees to be bound by all elements of its Proposal should PG&E accept such Proposal (e.g. award a Contract to Bidder). This form must be signed by a person that has the authority to bind Bidder to a contract. The Transmittal Letter can be found in Article IV “Bid Forms.”


Compliance Certificate: Bidder shall complete, sign and submit one copy of the Compliance Certificate for the Injury and Illness Prevention Program as part of its proposal. The certificate can be found in Article IV “Bid Forms.” Bidder’s Primary Contact for the RFP: Bidder shall identify its primary contact person for the RFP. Bidder must provide the contact person’s name, title, mailing address, phone number, emergency number (cell), fax number and e-mail address.

Insurance Certificate: Bidder shall provide a Certificate(s) of Insurance detailing all of the relevant insurance policies that Bidder currently carries and each policy’s respective limit.

Questionnaire Responses: Bidder shall provide detailed answers to the questions posed in Article III “Questionnaire and Pricing Sheets.” Pricing Sheets: Bidder shall complete all pricing sheets. The pricing sheets can be found in Article III “Questionnaire and Pricing Sheets.” Exception Statement: Bidder shall complete, sign and submit the Exception Statement. This form indicates whether Bidder takes exception to any term or condition of Article II “Specification” (Specific or General Conditions). The Exception Statement can be found in Article IV “Bid Forms.”

Exception Sheets(s) – If Applicable: For each exception that Bidder takes to Article II “Specification”, whether the specific or general conditions, Bidder shall submit a fully completed Exception Sheet. The Exception Sheet can be found in Article IV “Bid Forms.”

5.0 PROCEDURES FOR RESPONDING

For Bidder’s Proposal to be considered for award all information requested in Section 4.0 must be submitted and the following procedures must be observed:

Quoted prices must be entered on the pricing sheet provided in Article III.

Bidder will receive an invitation to register with Power Advocate before the RFP is released. Once registered, the Bidder will be able to view and respond to the RFP. All communications regarding the RFP will be funneled through Power Advocate.

Bidder's Proposal must be posted to Power Advocate no later than 3:00PM PST on TBD (hereinafter, “Due Date”). Proposals received after that time will not be accepted. All proposals must be valid for a period of not less than one-hundred twenty (120) days from the Due Date.

PG&E WILL NOT ACCEPT PROPOSALS TRANSMITTED BY FACSIMILE (FAX) OR E-MAIL.

6.0 QUESTIONS AND REQUESTS FOR INFORMATION

If Bidder is in doubt as to the intent of any part of the RFP documents, the Bidder shall post written questions to Power Advocate with the subject clearly marked. Questions from Bidders are due no later than 3:00PM PST on TBD. Questions submitted after the question deadline may not be answered. Any explanation of the RFP will be made only by a written addendum to the RFP which PG&E will transmit to all Bidders. PG&E will not be responsible for any other explanations of the RFP documents.


If you require assistance in any diversity subcontracting efforts per Section 11, post the request to Power Advocate asking that they forward the request to a PG&E Supplier Diversity Representative. Any attempt to communicate about this RFP with any other PG&E employees or consultants may result in Bidder’s Proposal being disqualified.

7.0 BID PREPARATION

Any and all costs or expenses incurred in preparing, modifying or submitting a proposal are the responsibility of the Bidder. Under no circumstances will PG&E will be responsible for such costs and expenses. All proposals and any other materials submitted in response to this RFP will become the property of PG&E and may be returned only when requested by Bidder at PG&E's option and at Bidder's expense.

8.0 EVALUATION CRITERIA AND TWO-STEP BIDDING

Proposals submitted by Bidders will be reviewed and evaluated by a cross-functional Team. The Team may evaluate this bid based on criteria including, but not limited to;

Competitive price

Acceptance of PG&E’s terms and conditions

Completeness of the bid package

Cost reduction ideas or alternatives for performing the services

Women, Minority, Disabled Veteran Business Enterprise (WMDVBE) status and/or subcontracting plan

Safety record

Financial stability

Contractor’s ability to perform the services

Feature set

Interoperability

Scalability

Supportability

These factors are not necessarily listed in order of importance. PG&E at its sole discretion may decide to use some or all of these factors.

PG&E may use a two-step bidding process to select the successful Bidder(s). The first step will be an evaluation of each Bidder’s Proposal using the evaluation criteria described above. Those Bidders whose proposals which are technically acceptable and whose price is competitive may be invited to the second step in the selection process. The second step will be used for a more in-depth review of each proposal, and may include steps such as:

Discuss the scope of work in detail,

Identify any cost reduction ideas,

Interview key candidate personnel in person,

Visit candidate facilities

An on-site demonstration of the proposed solution

Contact client references.

In addition, negotiations over Contract price and terms would take place.


9.0 CONTRACT TERM

Any contract(s) awarded pursuant to this RFP will be for a base term of TBD years. In addition, PG&E shall have the unilateral option to extend the term on a year to year basis for a term not to exceed TBD additional years.

Any Contract awarded pursuant to this RFP will be a non-exclusive Contract and there will be no guarantee as to the volume of work.

10.0 AWARD OF CONTRACT

After consideration of price, capabilities, and other factors as a result of this RFP, Vendors will be selected in order to provide the identified requested resources herein.

PG&E will reserve the right to deal directly with Vendor via the use of PG&E’s Contract for Consulting Services or instruct the Vendor to coordinate further with PG&E’s third party resources partner, Agile1, on such award, or a combination of both options, as deemed appropriate by PG&E. An award of business may be made to any Vendor without further discussion or negotiation. The right is reserved, as the interest of PG&E may require, rejecting any or all Proposals and to waive any formality in Proposals received. Depending on the engagement model chosen by PG&E, Vendors may be required to have an executed Master Services Agreement with PG&E in order to perform the work associated with this RFP. If the engagement channel, at PG&E’s sole discretion, is deemed to be via Agile1, the Vendor will need to engage in a contract directly with Agile1 in order to be eligible to fulfill our requisitions for these roles.

PLEASE INDICATE WHETHER OR NOT YOU WILL COMPLY WITH THIS REQUIREMENT IN SECTION 4.0

In either scenario outlined above, the Vendors will agree to PG&E’s Early Payment Discount term of 2% discount 15 days Net 45. PLEASE INDICATE WHETHER OR NOT YOU WILL COMPLY WITH THIS REQUIREMENT IN SECTION 4.0

11.0 RESERVATION OF RIGHTS

PG&E reserves the right to withdraw or modify this Request for Proposal (RFP) at any time before responses are due. PG&E may accept or reject any or all responses, and may accept other than the lowest price proposal. PG&E will not be liable, by reason of such withdrawal or rejection, to any Bidder submitting a Proposal to this RFP. PG&E reserves the right to waive or modify requirements under this RFP, with or without notice to Bidders, in its sole discretion.

Bidders are required to provide accurate and complete responses to the RFP documents. Incomplete responses may be subject to disqualification in PG&E’s sole discretion. PG&E may reject any response which is conditional or incomplete, or which contains any deviations from the instructions provided in these “General Instructions and Provisions.”

12.0 VENDOR PARTNERSHIP AND/OR USE OF SUB-CONTRACTORS

PG&E requests bidders propose a complete platform solution using proven off-the-shelf software, or an integrated suite of proven applications/technologies. Given the breadth of desired functionality,


PG&E recognizes that a single vendor may need to form partnerships with other vendors to develop a complete solution. Partial bids will be evaluated but given less consideration than complete responses.

PG&E will agree on the complete solution and negotiate a contract with a single lead vendor (“Prime”) who will be responsible for integrating the products provided by partnering vendors (“Sub”).

Onshore Resource Requirement

Onshore resources are the initial requirement, and local resources are preferred.

For the preferred local resources that are required, it is PG&E expectation that there will be no travel and related expenses. PG&E expects the Vendor to offer incentives and additional volume/spend based discounts throughout the engagement.

Should Vendor desire, PG&E will consider alternative pricing proposals in addition to the above expectations.

13.0 SUPPLIER DIVERSITY STATEMENT

PG&E encourages companies interested in providing services to PG&E to support Supplier Diversity Purchasing through its purchasing and subcontracting practices. In order for Pacific Gas and Electric Company to include the Woman, Minority and Disabled Veteran Business Enterprise (WMDVBE) contractor or subcontractor in the Company’s supplier diversity goals, the WMDVBE prime contractor or subcontractor must have a current verification by one of the following agencies:

* California Public Utilities Commission’s WMDVBE Clearinghouse (for woman- or minority-owned businesses); or

* Department of General Services (for disabled service veteran-owned businesses).

Verification can also be obtained from one of the following CPUC Clearinghouse comparable agencies:

* National Minority Supplier Development Council (NMSDC) or a regional affiliate

* Women’s Business Enterprise National Council (WBENC) or a regional affiliate

* Small Business Administration Supplier Diversity RFP Questions In addition to any questions included in this RFP, it is recommended that Bidders address the following relative to their Supplier Diversity program.

Is your company certified by the CPUC Supplier Clearinghouse as a woman or minority-owned business? If your company is service disabled veteran-owned, is your company certified by the Department of General Services? Please provide certification number and expiration date.

If your company is woman, minority or service disabled veteran-owned but not certified by the CPUC or Department of General Services, does your company hold a Women's Business Enterprise National Council (WBENC), National Minority Supplier Development Council (NMSDC) or SBA 8(a) certification. Please provide certification number and expiration date.

Does your company have a Supplier Diversity Program? If so describe efforts your company has made to increase business with women, minority and service disabled veteran-owned businesses (i.e. does your company have a policy statement, participate in outreach activities, promote diverse firm


subcontracting, publicize contract opportunities, provide certification assistance, etc.?) Please provide examples.

If your company has a Supplier Diversity Program, does your company mentor women, minority and service disabled veteran-owned suppliers? Please provide examples.

What percentage of your company's total contracting and procurement spend for the prior year was with women, minority and service disabled veteran-owned businesses?

Supplier Diversity Sub-contracting Plan Successful Bidders will agree to a subcontracting plan, as part of their contract, to support PG&E’s commitment to utilize Diverse Suppliers as outlined below. The term subcontractor referred to in this plan applies to subcontractors that provide a service, and sub suppliers that provide material, parts, assemblies or components. PG&E is subject to General Order (GO) 156 of the California Public Utilities Commission. GO 156 establishes goals for each utility to purchase a minimum of 21.5% of its goods and services from Women Minority and disabled Veteran Owned Business Enterprises (WMDVBEs or Diverse Suppliers). Furthermore, GO 156 sets the following sub-goals: 15% minority; 5% women, and 1.5% disabled veteran-owned business enterprises.

GO 156 requires each utility to establish and maintain a subcontracting program for the purpose of encouraging its prime contractors to utilize Diverse subcontractors. GO 156 does not authorize or permit a utility to utilize set-asides, preferences, or quotas in administration of its WMDVBE program.

As part of the Proposal, the Bidder shall include a stated goal to subcontract with Diverse Suppliers with both a total goal as well as sub-goals for each of the sub-categories, as follows:

Total Goal: %

Sub Goals: %

Minority %

Women %

Disabled Veteran %

The successful Bidder will agree to make good faith efforts to assist PG&E in meeting its goals through the implementation of Contractor’s subcontracting plan. Such good faith efforts will be measured through the Service Level Agreement and/or Performance Scorecard provisions of this Contract.

The successful Bidder will agree to submit enrollment form and utilize PG&E’s Supplier Diversity Management System (SDMS) for on-line reporting of spend with WMDVBEs for reporting periods as specified by PG&E.

To assist you in any diversity subcontracting efforts, you may contact the PG&E contact person requesting Supplier Diversity Representative’s assistance or you may conduct your own searches through the WMDVBE Clearinghouse at: http://www.cpuc.ca.gov/static/jobs_consultant/consultants/wmbe/index.htm

14.0 SAFETY STATEMENT

mailto:contact

http://www.cpuc.ca.gov/static/jobs_consultant/consultants/wmbe/index.htm


PG&E is committed to maintaining and promoting job safety and health for our employees, customers and the general public, and we expect companies interested in performing services for PG&E to do the same. We are committed to working with companies who conduct their services safely by providing adequate training and a safe work environment.

15.0 ENVIRONMENTAL STATEMENT

Environmental protection and enhancement is one of our fundamental corporate priorities as PG&E recognizes that a sound environmental policy and sound business practices go hand in hand. PG&E expects that companies interested in providing services to PG&E will contribute to the success of maintaining our leadership in the environmental arena by conducting all aspects of services in an environmentally sensitive manner which maintains and, when feasible, improves the quality of the environment.

16.0 ETHICS STATEMENT

PG&E stresses the importance of integrity, honesty, professionalism and ethical business conduct to all of its employees and it contractors. PG&E expects that companies interested in providing services to PG&E will conduct business with the same emphasis on integrity, honesty, professionalism and ethical business conduct. 17.0 PERFORMANCE SCORECARD STATEMENT The successful Bidder will agree that its performance on key Contract requirements be evaluated on the scorecard measures specified in Exhibit XX of the Contract. The process and frequency of measurement, as well as the consequences of measurement results, will be as specified in the scorecard.

18.0 PROPRIETARY INFORMATION

This RFP, and other data appended or related to it, are the property of PG&E and are delivered only for the purpose of enabling each potential Bidder to prepare and submit a Proposal in response thereto. The information contained or referred to in these specifications or appended to them is confidential and proprietary to PG&E and shall be returned to PG&E if requested by PG&E. Bidders shall not disclose or release any information contained in this RFP for any other use or purpose without the prior written approval by PG&E.


Article II: Specification

REQUEST FOR PROPOSAL No. 40641

FOR Grid Ops Situational Intelligence ARTICLE II: SPECIFICATION

TABLE OF CONTENTS

PAGE

1.0 INFORMATION TO VENDORS .............................................................................................. 12

2.0 STANDARD TECHNOLOGIES ............................................................................................... 17

3.0 PILOT REQUIREMENTS ........................................................................................................ 18

4.0 GENERAL CONDITIONS ........................................................................................................ 25


I. SPECIFIC CONDITIONS

1.0 INFORMATION TO VENDORS

1.1 Background, Scope and Objective Grid Ops Situational Intelligence (GOSI) is one of several projects in the Electric Program Investment Charge (EPIC) program. The EPIC program provides funding for applied research and development, technology demonstration and deployment, and market facilitation for clean energy technologies and approaches for the benefit of ratepayers. The GOSI project will pilot visualization technologies that integrate various data sources and display information on Distribution Control Center video walls and individual computers, as well as computers and handhelds of other distribution and field service personnel. The objective of this GOSI Pilot program is demonstration of a “real-time” data visualization platform which integrates traditionally isolated data sources and presents that information in a form that is easily digestible by end users. In developing the functional and technical requirements for the GOSI Pilot it became apparent that the platform that would be required to support the GOSI objectives could form the basis for a much broader capability not only within Electric Distribution, but across multiple PG&E Business Units. Therefore, PG&E decided to collect related use cases and requirements across all relevant Business Units and create a comprehensive and consolidated set of functional and technical requirements that would define a foundational platform for Enterprise Operational and Situational Intelligence (EOSI). The objective of this RFP is two-fold: to identify vendors and solutions that can meet the immediate scope and requirements of the GOSI Pilot and to understand and evaluate the capabilities of vendors and solutions to support the requirements of an enterprise level platform. It is expected that successful delivery of the GOSI Pilot could lead to a production implementation of the EOSI platform. The GOSI Pilot use cases and related functional/technical requirements are specified in Section 3 and in the Requirements Addendum. Additional use cases that have been identified are also included, as are a full set of functional/technical requirements that have been identified to support the EOSI platform. Vendors are expected to provide a response to all requirements and uses cases, with an understanding that this initial contract award is to deliver the GOSI Pilot.

1.2 EOSI Platform Description and Requirements PG&E currently has many systems, tools and data sources that are used to support its business capabilities and related processes, from power generation and natural gas sourcing, through transmission and distribution, to customer care, service and support. Safety, reliability and efficiency are PG&E’s primary objectives, and fundamental to these are the implementation and ongoing evolution of the Smart Grid. The Smart Grid is enabled by data collected from sensors throughout the system, including one of the nation’s largest deployments of Smart Meters, combined with data from external sources, including weather, market and emergency services, and overlaid on the geo-spatial physical network. As the number of sensors and measurement points grows, so does the need to collect manage, analyze and act on the data. Most current analytics systems are designed to operate on historical data, providing reports and analysis that are batch processed. These approaches do not


support new requirements that are related to near real-time processes needed to enable the Smart Grid, such as Volt/VAR Optimization, Fault Detection, and integration/optimization of Distributed Generation. Further, as more information is available, it has become more difficult for operators to sort through alerts and alarms, and visualize the effect of these on their respective territories and assets. Newer technologies have been developed that are designed to handle the collection and processing of streaming time series data in near real-time, combining different data sources, performing analysis and Complex Event Processing (CEP), and allowing advanced visualization for human processing. The EOSI Platform is envisioned as a foundational structure to support these requirements and will become a key component of PG&E’s Smart Grid.

Figure 1: High Level Conceptual Architecture and Key Attributes of the EOSI Platform

1.2.1 Key Platform Attributes

Integration: Integration with existing data sources is one of the most critical aspects of this platform. Connection to streaming time series SCADA data originating on the Utility Data Network (UDN), along with more static GIS, customer and asset data is critical. Integration of external data sources will also be important. SOA and standards based integration approaches are expected, and source systems include SAP, Silver Springs Networks Utility IQ, OSIsoft PI, and Esri ArcGIS. Direct connection with existing data warehouses (Teradata and SAP BW) is also expected in order to limit the need to data replication.


Data models: use of or mapping to industry data models is also seen as an important aspect to improve efficiency and integration. The CIM data model for transmission and distribution entities is recommended. Support for industry data models such as Teradata ULDM, ADRM, and Oracle OUDM is of interest.

Operational Data Store: While in general best practice is to limit the replication of data and access it from the system of record when possible through SOA data service connectors, factors such as database system ability to handle queries without overload and the velocity required to drive some processes will require the ability to process and persist data within the platform. This should be elastic in nature, with the ability to scale dynamically to adapt to loads, for example in the case of an emergency or natural disaster.

Application layer: this needs to be flexible and provide support for the integration or “plug-in” of functional modules from existing applications as well as external 3

rd party

applications. The fabric should support communication across active applications within the context of a user. This also needs to support a Complex Event Processing (CEP) engine to provide automation based on business logic, pattern matching and machine learning. As our confidence builds in our ability to automate response signals based on real-time data streams (closed loop sense and respond), we can display visualizations of what the systems are doing and allow operators to focus on real exceptions that require intervention. A key challenge here is the current separation of the Operational Data Network (ODN) and Utility Data Network (UDN or corporate network). While this exists for security and risk reasons, it does present complexity and potential latency.

Visualization and User Workbench: this layer comprises how the user interacts with the system and must support multiple user types/profiles, from Control Center video walls to mobile field service workers. It is expected that the user can configure their own workspace, choosing from a pre-configured listing of available apps/views that are based on the user type/profile and security access rights. Each app/view should be able to be re-sized by the user and tiled based on preference. The system should store these preferences and load onto whatever display the user logs in from. For certain users, e.g. operators, the system should be able to automatically change the views displayed based on events, alerts and alarms. For example, if a device or subsystem fails, or circuit goes down, the system should present screens to provide visualization of the related data and affected area, allowing them to quickly address the problem.

Security: access security to be based on the user login ID (LDAP integration) and extend down to the data level.

1.2.2 Primary Data Sources and Existing Systems It is expected that there will be in excess of 200 data ”channels” to be processed, originating from multiple systems and data sources. The following table provides a summary of the primary data sources by high level category.

Data Type Source

Customer and meter interval/usage data Teradata

GIS and map data ESRI ArcGIS

Asset data SAP AM

SCADA data OSIsoft PI

Electric Meter data SSN UIQ

Electric Distribution and Outage data Ventyx ABB DMS/OMS


It is our objective to utilize and leverage existing foundational systems to the greatest extent possible and preference will be given to solution architectures that take this approach. While the preceding table highlights the key data sources, the following systems are considered foundational at PG&E within the context of this project:

System Solution

Enterprise Data Warehouse (EDW) - for non-SAP data and integration of non-SAP data with SAP data

Teradata

Analytics for advanced data analysis, data mining and predictive models

SAS

Data visualization for data exploration and ad-hoc analysis

Tableau

GIS, base maps ESRI ArcGIS

If a vendor has a different technology for any of these categories that they are recommending as part of their solution, it is requested that they identify the benefits and value that are provided. Vendors should recognize that implementing different technologies here will likely add cost, for licensing, implementation and support.

1.3 Proposal Deliverables PG&E is soliciting Proposals from Vendors to include the following:

1.3.1 Proposal Response Document The Response Document should contain a complete response to the RFP and addresses all sections and questions. The Excel Questionnaire is an integral part of the response.

Platform Approach and Solution Architecture o Identification of the high level architecture of the proposed platform o Clear indication of what would be included to deliver the GOSI Pilot and what would

be included to extend it to support the EOSI platform.

Functional and Technical Capabilities o These will be assessed primarily through the Questionnaire, but the Vendor may

provide additional documentation and technical specifications. o PG&E understands that any given vendor may not have products and/or services to

support the full scope and deliverables of the RFP (GOSI and EOSI). In that case, PG&E asks that the vendor clearly identify where it does not provide the products and/or services identified; and where applicable, identify other providers the vendor has worked with to provide the functionality.

Product Specification (Captured in the “Vendor Summary” tab of the Questionnaire) o Identification of all product(s) required to satisfy both GOSI Pilot and full EOSI platform

requirements o Clear indication of vendor and version of each product.

Pricing (Captured in the “Cost of Ownership” tab of the Questionnaire)


o Cost of Ownership tab: This includes two pricing tables and questions around warranties, support, services and training. Please complete all sections.

NOTE: The GOSI Pilot Pricing table is for the immediate work defining by this RFP in support of the GOSI Pilot project and is expected to be completed by 12/31/2015. This is expected to be an all-inclusive Fixed Bid price from the vendor, including any required 3rd party software and/or services. This amount is to be binding under the terms of the RFP and subsequent award. The "Cost of Ownership (EOSI Platform)" table is for comparison and budgetary planning purposes. While not binding, cost of ownership will be part of PG&E’s selection criteria. A subsequent extension of the GOSI solution and implementation as an enterprise EOSI platform would be accomplished through a subsequent negotiation and contract.

Pricing information for all products identified in the Product Specification. Pricing information should include: o License(s) for all server software required to satisfy pilot requirements o License(s) for any interface and/or interoperability software required to satisfy pilot

requirements o License(s) for any client software required to satisfy pilot requirements

Product pricing should be structured as follows: o Pricing for duration of the Pilot project (pilot licenses) o Post-project pricing; permanent licenses o Listing of all Professional Services required to satisfy the Pilot requirements.

1.3.2 Technical Implementation Specification Provide the following details for the hardware and related infrastructure requirements for both the GOSI Pilot and Enterprise level implementations. Also explain the basis for the required infrastructure specification, e.g. implementation experience at another utility of similar size, performance/scalability testing at similar scale, etc.

Installation requirements for all server software; processor size and speed, memory, storage, operating system, etc.

Installation requirements for all client software; connectivity, processor size and speed, memory, operating system, etc.

Overview of proposed installation.

1.3.3 Functional Specification

Detailed description of how Product and Professional Services will satisfy pilot requirements

Description to provide information for each PG&E Use Case.

1.3.4 Pilot Project Plan

Schedule: Detailed schedule describing major tasks, deliverables, dependencies, and responsible resource for implementation of the GOSI Pilot

Risks: Identification of known and/or anticipated risks

Constraints: Identification of known and/or anticipated constraints

Dependencies: Identification of pilot project dependencies

1.3.5 Training Plan

Recommendation for training of pilot project core team


Recommendation for training pilot project end users

1.4 Work Location PG&E expects the Vendor to be on-site at PG&E facilities as required to develop the Functional Specification. PG&E will make Subject Matter Experts and Business Analysts available to the Vendor to provide information required to complete the Functional Specification deliverable and all other deliverables. PG&E expects the Vendor to be on-site at PG&E facilities for all prototype demonstration sessions. PG&E expects the Vendor to be available to support User Acceptance Testing and deployment to PG&E’s production environment. This may require the Vendor to be on-site at PG&E facilities.


2.0 PG&E Standard Technologies

Enterprise Integration

B2B Oracle SOA Suite B2B EDI

ETL Informatica version 9.1.0 Hotfix 1

File Transfer Axway ESFT 4.9.2 (current). 5.2 (Q2 2014)

Real-time Stateless Oracle Service Bus 11g

Real-time Stateless or Stateful

WebLogic 12c JEE , JMS, JDBC, ODBC, SMTP

Standard SOA protocols: HTTP, HTTPS, REST, SOAP, SOAP with attachments, SOAP with WS-Security, WS-ReliableMessaging, WS-Transaction

External facing gateway Layer 7, OAuth 2.0

Data Warehouse/Business Intelligence

Data warehouse SAP Business Warehouse, Teradata

Data Base Oracle, SQL Server

ETL Informatica, SAP Data Services

Business Intelligence Tools

Business Objects (Web Intelligence, Crystal, Xcelsius, Design Studio, Business Objects Explorer, Lumira)

SAS

Tableau

Operating Systems

Windows Windows 2008 R2

Unix Unix - Aix 6.1

Red Hat Enterprise Linux 6.4


3.0 Pilot Requirements

3.1 Background Within PG&E’s Electric Distribution Operations organization, the Grid Operations Situational Intelligence Project is born out of the need for operators, engineers and construction foremen to access a variety real-time and historical data from one platform to support immediate outages and long term planning. Examples of data include SCADA, SmartMeter, Weather, Fire, Construction work sites, etc. The project is seeking to develop and pilot a prototypical real-time data visualization platform for operational usage in two (2) Divisions, out of a total of nineteen (19) Divisions within PG&E’s territory. During the pilot, this platform will be used by day-to-day operators, engineers and construction workers in the two (2) Divisions in order to validate and measure the benefits of the platform. The use cases enabled by this platform are expected to provide measurable benefits in the following areas:

Safety

Reliability

Affordability

While this pilot is focused on data integration and data visualization, it is expected that the platform will be able to support future analytics and machine learning use cases with extensions through iterative development. A successful project will be considered according to the following categories:

Validated and measured benefits for the use cases impacting operators, engineers and construction foremen

Platform that can support future use cases developed by PG&E.

3.2 Project Phases The development of the project will be executed in the following five (5) Phases. Dates are estimated and will be refined as appropriate.

Phase Start End

Planning 1/1/2014 3/15/2014

Design/Engineering 3/15/2014 5/9/2014

RFP Responses and Vendor Selection 5/12/2014 7/11/2014

Vendor and PG&E Development 7/14/2014 12/31/2014

PG&E Development 1/1/2015 08/31/2015

Evaluation and Closeout 9/1/2015 12/31/2015

The Design/Engineering & Staging Phases are currently underway. This work will be completed by PG&E resources to produce use cases, design requirements, benefit measurement/validation plans and technology infrastructure approaches. There is no Vendor involvement during this Phase. The RFP Responses and Vendor Selection Phase will start following publication of this RFP. During this phase, contact between PG&E and Vendors will be limited per PG&E Sourcing guidelines. The Vendor and PG&E Development Phase will consist of joint development between the selected Vendor and PG&E. Vendor and PG&E will develop the first use cases together in sprints according


to the Agile methodology. It is expected that the Vendor will help PG&E developers gain skills and develop expertise in the use of the Vendor’s product and tools during this phase. In the PG&E Development Phase, PG&E staff will develop additional use cases. It is expected that the Vendor will support PG&E developers as they continue to gain skills and develop expertise in the use of the Vendor’s product and tools. In the Evaluation and Closeout Phase, PG&E will assess the benefits, costs and results of the pilot project, and make a determination for a potential full-scale deployment of the platform across all the entire Electric Distribution Operations organization.

3.3 GOSI - Use Cases There are four (4) major use cases that this Project plans to develop. Each use case consists of data integration with multiple data sources and visual geospatial layers for categories of information from each data source.

Use Case #1 Visualize Construction Work

Description PG&E construction supervisors require the use of a geospatial view to plan their construction work seven (7) weeks into the future. This helps them allocate resources and materials in advance of construction projects or reallocate crews to deploy to unexpected emergencies. Operators do not have a full view of all construction work, which could create safety issues when they write switch logs without knowing if construction crews are performing hot work on circuits.

Examples of Data Layers

Geospatial layer

Electric distribution network model with field assets

SmartMeter assets

SCADA loading

SmartMeter loading

Circuit line capabilities from GIS

GPS locations of field crews

Real time outages

Construction work sites

Safety hazards

Picture and video integration from mobile devices

Line Sensor Data

Primary Actor: Construction Supervisor Operator

Scope: GOSI (Grid Ops Situational Intelligence) platform

Level: User goals

Stakeholders and Interests:

Construction Supervisors - allocate resources and materials for construction project Construction Estimators - build work packages for each construction job Emergency Management Specialists - monitor scope and severity of disasters Construction Crews - perform construction work Operator - wants to know where the construction work is happening

Trigger: Construction Supervisor - Weekly construction planning or notification from Emergency Management Specialist Operator - Switch log research


Main Success Scenario:

1. Construction Supervisor or Operator opens the GOSI (Grid Ops Situational Intelligence) application from his browser.

2. GOSI detects the user's LAN ID (Company employee username to login to the company laptop from Windows bootup screen) and determines the user profile of the LAN ID

3. GOSI zooms to the geographical area linked to the user's jurisdiction

4. GOSI displays the satellite layers, network model layers, and construction project layers

5. GOSI displays pins for each construction project out to 7 weeks on the construction project layer

6. User clicks on each pin to view a pop-up menu, showing the description of the project, links to associated AFW (Application For Work - a website built by PG&E that handles construction clearance requests from construction crews) clearances, link to the work package in SAP and link to a scheduling application (called Click)

7. User clicks on the link to AFW, which brings up AFW webpage with associated clearances

8. User clicks on the link to SAP, which brings up the work packager prepared by the estimator

9. User clicks the link to a scheduling application (called Click), which shows the resources and schedule of the project

10. User clicks on future build layer to see how the circuit will change from as-built to the future state. This information is created by mappers into the ESRI GIS platform.

11. Construction Supervisor can then make a decisions to move crews to support existing projects or existing emergency scenarios

12. Operators can make sure that switch logs written do not create safety concerns for construction crews.

Use Case #2 Anticipate outages to prepare mitigation plans

Description Operators currently receive overloaded alarms through the SCADA alarm screen. However there is no direct link of overloaded information to a geospatial layer, nor is there an interface to continually monitor trending. For major storm events, PG&E’s Emergency Management organization will provide advanced warnings of storms and mobilize operational and field resources to manage the storm, however there also no direct link of weather or fire information to specific distribution circuits. Operators need one interface to anticipate field conditions before they can anticipate outages and create mitigation plans.


Geospatial layer


SmartMeter assets

SCADA loading (accessible through OSIsoft PI)

SmartMeter loading

Circuit line capabilities from GIS

Fire data

Weather data


Primary Actor: Operators and Operating Engineers

Scope: GOSI

Level: User goals


Operators and Operating Engineers - troubleshoot outages and write switch logs Emergency Management Specialists - monitor scope and severity of disasters

Trigger Continual monitoring


1. Operator or Operating Engineer opens the GOSI application

2. GOSI detects LAN ID and determines the user profile of the LAN ID

3. GOSI displays a menu of frequently visited layer options

4. Operator selects the "impending outage awareness" option. GOSI will run continuously on a video wall, 24 hours a day and 7 days a week.

5. GOSI zooms to the geographical area linked to the Operator's jurisdiction

6. GOSI brings up a map layer, network model layer, equipment loading layer, weather layer, and fire layer

7. The weather layer will show current and forecasted weather patterns as produced by national weather services.

8. The fire layer will show current and forecasted fire patterns as produced by national fire services.

9. The equipment loading layer will mark equipment that are near overloaded (for example, 85% of capacity) with a yellow pin, and overloaded equipment (for example, 101% of capacity) with a red pin, and extremely overloaded equipment (for example, 150% of capacity) with a red/black striped pin. This includes both SCADA and non-SCADA equipment such as service transformers, fuses, switches, line reclosers, circuit breakers.

10. With the equipment loading layer, there will be side panel display not utilizing the geospatial layer, showing multiple lists of overloaded equipment in a jurisdiction. By default, there is a list for SCADA equipment: switches, line reclosers, circuit breakers and banks. This information is based on real-time SCADA reads. These lists will dynamically re-sort every 5 minutes as equipment loading changes.

10a. This information will also be filterable for historical data. Historical data will include SmartMeter loading for the following SCADA and non-SCADA equipment: service transformers, fuses, switches, line reclosers, circuit breakers and banks.

11. With the equipment loading layer, there will be a second side panel display not utilizing the geospatial layer, showing multiple trend charts, each dedicated to one type of overloaded SCADA equipment (switches, line reclosers, circuit breakers and banks) in the jurisdiction. The worst offending equipment will be at the top. The trend chart contains four lines, a flat line showing load capability, and three lines for amps a, b and c. These trend charts will dynamically re-sort for worst-offenders every 5 minutes as equipment loading changes.

11a. This information will also be filterable for historical data. Historical data will include SmartMeter loading for the following SCADA and non-SCADA equipment: service transformers, fuses, switches, line reclosers, circuit breakers and banks.


12. The operator looks at these layers to understand which portions of the distribution circuits are in danger of overloading, as well as which distribution circuits will be impacted by weather and fire patterns.

Use Case #3 Write switchlogs for planned and unplanned outages from circuit loading research.

Description Electric outages fall into two categories, planned and unplanned. Planned outages often originate from clearance requests that construction foremen submit prior to a construction job. Unplanned outages can occur as a result of weather patterns, equipment failure, and interference from vegetation and other factors. Operators and operating engineers look for ways to clear or restore a section of line and supply power to customers through alternative circuit paths. This involves researching circuit capabilities and historical loading, assessing potential interference from other work and preparing switchlogs to reconfigure the circuit. Data layers are needed to visualize the circuit, understand loading history and capabilities of the circuits, and identify nearby hazards or events that can impact the preparation of switchlogs. Distribution grid operators will then identify circuits that could be potentially impacted by the storms and prepare mitigation plans for each circuit.


Geospatial layer


Construction work sites

Fire data

Weather data


Scope: GOSI

Level: User goals


Operators and Operating Engineers - troubleshoot outages and write switch logs Troublemen - execute switch logs in the field

Success Guarantees:

Operators and Operating Engineers can find loading information

Trigger: Request for construction work occurs or unplanned outage occurs



2. GOSI detects LAN ID (Company username to login to the company laptop from Windows bootup screen) and determines the user profile of the LAN ID


4. Operator selects the "research loading" option


6. GOSI brings up a map layer, network model layer, equipment loading layer


7. Operator will type in an equipment name and the geospatial layer will zoom in and center on that equipment.

8. Operator will click once on a device in the GIS layer, which will display a pop-up overlaid on the geospatial layer, showing the 24 loading (amps a, b and c) for SCADA loading (if applicable) and SmartMeter loading (for all SCADA and non-SCADA equipment: service transformers, fuses, switches, line reclosers, circuit breakers, banks).

9. If the operator clicks on the geospatial layer, the pop-up goes away

10. If the operator clicks on the SCADA or SmartMeter trend, it will open a separate HTML interface where the operator can filter by dates, other data points, etc.

11. Based on the load research, the operator will calculate how much spare capacity is available to transfer load from a neighboring circuit.

Use Case #4 Reduce real-time loading on distribution circuits through Demand Reponse

Description Distribution grid operators have traditionally managed overloaded circuits by transferring line sections from one circuit to another. In severely overloaded situations, load transfers could cascade through multiple distribution circuits to support customer loading. Load transfers typically involve the need to write more switch logs and dispatch troublemen to the field to assist with the switching. A concurrent EPIC project (DSM for T&D Cost Reduction – EPIC 24) will work with customers to manage customer loads during high load scenarios and provide Distribution grid operators with quantifiable reserve of potential load reductions (measured in watts )that can be called upon to reduce peak load. Examples include the SmartAC program – where customers sign up for a rebate and allow their air conditioning units to cycle power, reducing peak load and the need to transfer circuits at the grid level. The EPIC 24 project will create a product that performs analysis of the potential load reductions available at each node and line section of the distribution circuits, for different time segments of the day. This data will be provided to the GOSI system for visualization on a geospatial and network model layer. These load resources will need to be integrated into the GOSI pilot as another visual layer, where distribution grid operators and operating engineers will have the ability to see the resources that can be called upon at the line section and field asset level to reduce peak load at targeted sections of the distribution circuit. In these high load scenarios, the operating engineers will determine the peak load of the circuit prior to Demand Response considerations and research how much of the peak load can be shaved using Demand Resources. The result is that a switch log will contain steps to call Demand Response Resources, with potentially fewer load transfers at the circuit level, or even no load transfers at all. From this geospatial layer, there should be the ability for an operating engineer to click a link to an external DR product web interface, which is external to the GOSI product and out of scope for this GOSI pilot. This


external DR product web interface will contain a control panel to allow an operating engineer to send control signals.


Geospatial layer


Demand Response resources available at field assets and line sections


Scope: GOSI

Level: User goals


Operators and Operating Engineers - troubleshoot outages and write switch logs

Success Guarantees: Operators and Operating Engineers can reduce load on a circuit

Trigger: Request for construction work occurs or unplanned outage occurs



2. GOSI detects LAN ID (Company username to login to the company laptop from Windows bootup screen) and determines the user profile of the LAN ID


4. Operator selects the "research loading" option


6. GOSI brings up a map layer, network model layer, equipment loading layer

7. Operator will type in an equipment name and the geospatial layer will zoom in and center on that equipment.

8. Operator will click once on a node in the GIS layer, which will display a pop-up overlaid on the geospatial layer, showing a numerical number for how much load (in kilowatts) can be reduced downstream on the circuit from that node, also known as Demand Response resources. This node can be equipment or just a line section on the circuit. If the node selected is a piece of equipment, then the Demand Response resources will be displayed in the same window, below the 24 loading (amps a, b and c) for SCADA loading (if applicable) and SmartMeter loading from the use case GOSI-V3.

9. If the operator clicks on the geospatial layer, the pop-up goes away

10. If the operator clicks on the numerical value for Demand Response resources, it will lead to another website containing a control panel will allow the operator to trigger a Demand Response request to reduce load. This control panel is not part of the scope of the GOSI project, but part of a separate PG&E project specifically focused on Demand Response. It is expected that the vendor working on the Demand Response project will develop the control panel in web-based form.

11. Based on the load research, the operator will calculate how much spare capacity can be added to the line, and determine how much load can be transferred from a neighboring circuit.


II. GENERAL CONDITIONS

Consulting Long

Sensitive Data Clean Final (00131218-2).docx


II. GENERAL CONDITIONS


Article III: Questionnaire and Pricing Sheet REQUEST FOR PROPOSAL No. 40641

FOR Grid Ops Situational Intelligence ARTICLE III: QUESTIONNAIRE AND PRICING SHEET

QUESTIONNAIRE

GOSI_RFP_Questionn

aire.xlsx PRICING SHEETS (Tab 3 “Cost of Ownership” of GOSI_RFP_Questionnaire)

1.0 Vendor Proposal Structure

Proposals should provide two distinct bids:

1. Fixed Bid for the Pilot Engagement as described in this document.

2. Fixed Bid for a Full Operational Implementation of the proposed platform. It is understood that this is for planning and comparison purposes and therefore not binding.

1.2 Fixed Bid for Pilot Engagement

PG&E expects all bidders to provide a comprehensive solution architecture that covers the overall application landscape and supporting infrastructure. The response should also describe the project delivery method, including recommendations on releases, and time frames to complete. PG&E expects the Vendor to provide pricing of the following components:

Software licenses and maintenance, Specialized hardware and infrastructure costs, Implementation services, including deployment and training, and On-going application support.


Article IV: Bid Forms REQUEST FOR PROPOSAL No. 40641

FOR Grid Ops Situational Intelligence ARTICLE IV: BID FORMS

Article IV – Bid Forms

TRANSMITTAL LETTER _______________________

(Date) PROPOSAL FOR ____________________________________________________, hereinafter, “Bidder”.

(Bidder’s Company Name) [Portfolio Team Name – Lead Negotiator] Sourcing Department Pacific Gas and Electric Company 245 Market Street, N5D San Francisco, CA 94105

Subject: PG&E Request for Proposal No. TBD: For TBD Dear [Name]: The Undersigned, as an official authorized to solicit business and enter into a Contract on behalf of the Bidder and having carefully read and examined the RFP for the above designated services, does hereby propose to provide the services set forth in this Proposal and agrees to execute a Contract with PG&E to perform the Work set forth in the RFP and any applicable Contract Change Order. Project costs include all taxes incurred in the performance thereof. All prices stated herein are firm and shall not be subject to adjustment provided this Proposal is accepted within 120 days after the time set for receipt of proposals. THE UNDERSIGNED UNDERSTANDS THAT (A) PG&E RESERVES THE RIGHT TO REJECT ANY AND ALL BIDS AND TO ACCEPT OTHER THAN THE LOWEST COST PROPOSAL; (B) ANY CONTRACT WHICH MAY ISSUE FROM THIS RFP SHALL NOT BE AN EXCLUSIVE CONTRACT; AND (C) ANY CONTRACT WHICH MAY ISSUE FROM THIS RFP SHALL NOT GUARANTEE CONTRACTOR ANY WORK, NOR SHALL THERE BE ANY GUARANTEE AS TO THE VOLUME OR DURATION OF WORK. The undersigned declares that Bidder has familiarized itself with the conditions affecting the Work. Further, the undersigned certifies and represents that Bidder has thoroughly reviewed the RFP and used it in preparing its proposal. The undersigned hereby declares that only the persons or firms interested in the Proposal as principles are named herein, and that no other persons or firms that


are herein mentioned have any interest in this Proposal or in the Contract to be entered into; that this Proposal is made without connection with any other person, company, or parties likewise submitting a bid or proposal; and that it is in all respects for and in good faith, without collusion or fraud. _______________________

(Signature) _______________________ (Printed or Typed) __________________ (Title) _______________________ (Company)


Waiver to Opt-Out of Receiving EPIC Annual Reports

PG&E is required to serve PG&E’s EPIC annual reports to each successful and

unsuccessful bidder for an EPIC funding award.

Please indicate below if you would like to opt-out of receiving PG&E’s EPIC

annual report:

Yes, I would like to opt-out of receiving PG&E’s EPIC annual report

No, I would like to receive PG&E’s EPIC annual report. In order to receive

PG&E’s EPIC annual report, bidders must be added to a CPUC service

list. To be added to the CPUC service list, bidder must complete and

submit the Addition/Change to Service List Form on the CPUC website

located here. The proceeding number is R.11-10-003.

http://www.cpuc.ca.gov/service_lists/


COMPLIANCE CERTIFICATE

INJURY AND ILLNESS PREVENTION PROGRAM Compliance Certificate

I, the undersigned of (Title) , hereby certify to PG&E as follows: (Bidder Company Name)

1. That Bidder has an effective Injury and Illness Prevention Program which meets the requirements of all applicable laws and regulations, including but not limited to Section 6401.7 of the California Labor Code and that any subcontractor hired by Bidder to perform any portion of the Work (if awarded) has an effective Injury and Illness Prevention Program; and

2. That you are the person with the authority and responsibility for

implementing and administering Bidder’s Injury and Illness Prevention Program.

IN WITNESS WHEREOF, the undersigned has executed this Compliance Certificate on . (Date) (Signature) (Print Name)


EXCEPTION STATEMENT _______________________

(Date) PROPOSAL FOR: ________________________________________________

(Bidder’s Company Name)

If Bidder takes exception to any term or condition of Article II “Specification” (Specific or General Conditions), each exception shall be identified and detailed on a separate Exception Sheet (provided below). Does Bidder take exception to any term or condition of Article II “Specification?”

Yes ___ No ___

If Bidder has answered “No” to the above question, no Exception Sheet(s) needs to be completed. Further, if Bidder answered “No,” please read and sign the following statement: If no exceptions are taken to the terms and conditions of the RFP and / or the General Conditions or the attachments thereto, Bidder’s authorized representative shall confirm acceptance of these same, as written, by entering his / her signature, title and the date, hereunder:

Signature of Bidder’s Authorized Representative

Title Date


EXCEPTION SHEET

Bidder shall fully complete this sheet for each exception taken to Article II “Specification”. Exception Number: __________ ________________________________________________________________ Statement of Requirement: Reference: Module: ______________

Section: _____________ Paragraph: ___________ ________________________________________________________________ Proposed Language Change: _______________________________________________________________ Reason for Exception:

Please Describe the Impact on Price of this exception (e.g. if PG&E agreed to this exception, how would this effect price?): ____________________________________________________________

Documents

ARTICLE I: CORE- GENERAL INSTRUCTIONS AND …ARTICLE I: CORE- GENERAL INSTRUCTIONS AND PROVISIONS REQUEST FOR PROPOSAL No. 40641 FOR Grid Ops Situational Intelligence ARTICLE I: CORE-