Hidden Image

Integrated Energy Data Resource (IEDR) Solution Architect and Development Contractor Teaming Arrangements

 

Fill out the Teaming Arrangement Form to participate in the upcoming IEDR Development Team RFP

Join now 

NYSERDA is excited to inform stakeholders across New York State of the upcoming Integrated Energy Data Resource (IEDR) Solution Architect and Development Contractor Request for Proposal (IEDR Development Team RFP) and to assist interested parties, particularly Minority and Women-Owned Business Enterprises (MWBEs), identify potential teaming arrangements for bidding into the IEDR Solution Architect and Development Contractor RFP.

IEDR Teaming Facilitation Details 

While participation in teaming facilitation activities will not be a pre-requisite for participating in future funding opportunities, NYSERDA respectfully requests all stakeholders interested in the upcoming IEDR Development Team RFP fill out the IEDR Teaming Arrangement Form. This form does not require the submission of confidential or proprietary information and does not seek feedback on potential IEDR architecture or design. All responses to the IEDR Teaming Arrangement Form will be publicly posted on NYSERDA’s IEDR dashboard by January 24, 2022 to facilitate the formation of teaming arrangements. The IEDR Teaming Arrangement Form may be filled out after this time, but its inclusion on NYSERDA’s teaming facilitation list may be delayed.

If you have questions regarding the Draft RFP Outline or the teaming arrangement form, please contact iedr@nyserda.ny.gov with the subject line “Name of Organization – IEDR Development Team RFP Teaming”

A matchmaking event will be held in Q1 2022 shortly after the release of the IEDR Development Team RFP to further promote and enable teaming arrangements. NYSERDA may reach out to organizations that respond to the IEDR Teaming Arrangement Form to request further details or to discuss the submission.

Draft RFP Outline

Please note, this content is a draft, and may be updated or modified for the full IEDR Development Team RFP.

Requested Services

It is anticipated that the requested services in the IEDR Solution Architect and Development Contractor RFP will be broken up into two categories:

  • Category 1: Solution Architect Services
  • Category 2: Design, Build, and Operate and Additional Services

Requested services in the IEDR Solution Architect and Development Contractor RFP may include, but may not be limited to:

Category 1: Solution Architect Services 

  • Project Management: The activities involved in the architecture, design and development of the IEDR need to align to an ambitious schedule. To maintain both the user value-driven focus and the schedule ambition of the IEDR, the IEDR program has adopted an Agile approach. The Development Team will be responsible for extending Agile best practices throughout project management, to include:
    • Continuing the use case development approach initiated by the Program Manager, in which stakeholder engagement and feedback are central to validating user value;
    • Developing a sprint cycle for platform development that is transparent throughout the IEDR Program (from governance and coordination entities through developers), iterative (working in small batches of use cases) and focuses on frequent value delivery and rapid feedback from users.
  • The Development Team will be responsible for coordinating with NYSERDA, the Program Manager, and other entities, including the Steering Committee, Utility Data Advisor, Advisory Group, and Utility Coordination Group, as necessary. The Development Team will be responsible for integrating feedback from these groups into the IEDR’s development on an on-going basis.
  • Identify and Characterize Beneficial IEDR Use Cases: Under the direction of NYSERDA, guidance from the Program Manager, and working with stakeholders and the Advisory Group, the Development Team will develop a list of beneficial use cases, capturing use case requirements, designing preliminary use case solutions, and a feasibility assessment and prioritization of use cases. This work will be transitioned from the Program Manager, who is currently leading this work.
  • Requirements Documentation: The Development Team will document the solution architecture and detailed requirements for fully implementing the IEDR using industry best practices. Architecture and implementation requirements will be tracked and updated throughout the course of the project with input from the project team and stakeholders, and in accordance with the established change management process. This work will be transitioned from the Program Manager, who is currently leading this work.
  • Development and Integration of IEDR Detailed, Implementable Designs and Specifications: IEDR implementation comprises deployment, integration, and activation of all elements needed to address developed use cases and the IEDR solution architecture requirements. The Development Team is responsible for developing a Preliminary Implementation Plan that describes the elements, structure, timing, deliverables, and estimated cost of the implementation effort.  The Preliminary Implementation Plan will reflect approved use cases, and therefore will iteratively adapt as use cases (and any resulting solution architecture requirements changes) are approved.  Following approval of an iteration of the Preliminary Implementation Plan, the Development Team should specify the detailed requirements for fully designing the IEDR. The complete IEDR design would comprise descriptive text, specifications, tables, diagrams, configuration parameters, data definitions, data schemas, computer code, operating procedures, and other work products that describe and explain all aspects of the IEDR’s composition, configuration, and operation to address approved use cases. The complete design scope should encompass the IEDR and all the other entities (systems and people) that will interact with the IEDR. The finished design should provide all the information needed to specify, procure, and execute all necessary IEDR implementation services. The complete IEDR design/specification will be iterative to reflect the Agile development of use cases and platform functionality.

Category 2:  Design, Build, and Operate and Additional Services

  • IEDR Core Build and Configuration: Based on the solution architecture, requirements, and designs, the Development Team is responsible for building and configuring the IEDR Core platform to support IEDR milestones.

    If utilizing commercial off-the-shelf technology solutions, the Development Team will be responsible for configuring the software to meet the project requirements. If building custom software, the Development Team will be responsible for planning, writing, commenting, compiling, and testing all relevant code to meet the project requirements. 

    The IEDR core should:
    • Be constructed using industry best practices
    • Be constructed in a modular and flexible manner
    • Be technology agnostic and leverage proven commercial off-the-shelf solutions, when practical and feasible
    • Allow for upgrades and expansion of the system without significant rework or downtime
    • Keep pace with technical and market changes and best practices over time

    The IEDR core will need to include, at minimum, the following components:
    • All data connections, including data connections and parsers, required to receive and/or pull data from the appropriate data sources as specified by the prioritized use cases
    • All data connections required to connect with the Data Ready Certificate platform to confirm and enforce appropriately user permissions
    • Data Tier, including all data warehouses, data lakes, relational databases, and storage containers required for long- and short-term storage of data required to meet the prioritized use cases
    • Logic Tier, including all business logic required to request and manipulate the data to meet the prioritized use cases
    • Presentation Tier, including all user interfaces and web applications required to receive user inputs and display or otherwise make accessible information (i.e., via download API, or other methods) to meet the prioritized use cases
    • Appropriate data access controls to restrict access to data where applicable as documented in the requirements
  • Deployment and Integration of Components and Services: With guidance and assistance provided as needed by NYSERDA and the Program Manager, the Development Team will acquire, deploy and integrate all components and services of the IEDR platform to support IEDR milestones. IEDR implementation comprises full deployment, integration, and activation of all elements needed to fully implement the IEDR. (See Section 5.8 of the IEDR Whitepaper for more detailed information on this professional service area).
  • Testing and Commissioning of the IEDR’s Capabilities: The Development Team is responsible for testing and commissioning all IEDR platform capabilities to support IEDR milestones. Before any IEDR capability is commissioned for use, acceptance testing would be developed, performed, and the results documented for each related IEDR operating function. The Solution Architect and Development Team will perform all appropriate unit, system, string, end-to-end, stress, and all similar testing as appropriate utilizing industry best practice and as overseen by the Program Manager (See Section 5.9 of the IEDR Whitepaper for more detailed information on this professional service area).
  • System Administration and Operations: Administration and Operations of the IEDR would commence and evolve as IEDR capabilities are released for testing, commissioning, management, and support. Once an IEDR capability is activated, the Development Team should perform all the operating functions needed to achieve the functionality and performance specified for that capability, with guidance and oversight from NYSERDA and Program Manager. Operating functions performed by the Development Team should include, but not be limited to planning, scheduling, system administration, process control, performance monitoring, system maintenance, access control, problem detection, problem resolution, change management, user support (including the maintenance of a customer help desk, up to date training materials, version documentation, and other user-oriented services), and reporting. 

    The Development Team will be responsible for engaging with the Advisory Group and obtaining operations-related inputs from the utilities, third-party data sources, providers of system services, and IEDR users.  

Solicitation Requirements

NYSERDA anticipates awarding one contract through the upcoming RFP that covers all services requested in Categories 1 and 2 for Phases 1 and 2 of the program. Proposers may be a single company or team of companies but must, in their response, clearly identify the key employees, subcontractors, or relevant affiliates of all entities who are proposed to fulfill the requirements of this RFP. If a proposer includes a partnering arrangement with third parties in their proposal, the proposer will retain sole responsibility for successful completion of the work under a resulting contract. Teaming arrangements that include MWBEs will be favored in proposal evaluations.

If a team of companies submit a proposal, the prime contractor or team lead may only submit one proposal with one teaming arrangement. There are no limitations or restrictions on appearing as a subcontractor in teaming arrangements for multiple proposals.    

Evaluation Criteria 

It is anticipated that proposals that meet solicitation requirements will be reviewed by a Scoring Committee using the Evaluation Criteria below:

  • Project Management and Requirements Gathering Approach and Capabilities
  • Solution Architecture Design, Planning, and Development Approach and Capabilities
  • IEDR Design-Build-Operate and Additional Services Approach and Capabilities
  • Proposer Qualifications and Past Experience
  • Schedule/Work Plan and ability to deploy acceleration strategies to meet Phase 1 deadlines
  • Proposal Cost and Value of proposed services
  • Program Policy Factors, including institutional and proposed project team diversity and/or teaming arrangements that include MWBEs