Request for Proposals: Technology Consultant for the Production Tracking System (PTS)

Please note – the publishing date for questions with answers to be posted on the MassCEC website has been updated from Thursday, 4/9/26 to Wednesday, 4/15/26 to allow additional time for processing.

The Massachusetts Clean Energy Center (MassCEC) is seeking proposals from qualified individuals or firms for a three-phase engagement to evaluate, modernize, host, and support the PTS. In Phase 1, MassCEC requires a thorough diagnostic assessment of the current system, including review of codebases, deployment pipelines (e.g., Azure DevOps or other CI/CD tools), data models, security controls, and system performance. The current system is a .NET application (primarily C#) with an SQL backend, hosted in Microsoft Azure. Phase 2 will focus on implementing the approved modernization strategy and delivering a production-ready modernized system. Phase 3 will provide ongoing operations, hosting, and support.

The objective is to preserve and improve existing registration, reporting, and verification functionality. The project should also enhance security, accessibility, logging, monitoring, and program compliance. The system must ensure seamless processing for programs including Renewable Portfolio Standard (RPS) Mass Class I, Solar Renewable Energy Certificates (SREC), Renewable Thermal (RT), Alternative Energy, and Clean Peak Standard (CPS).

Deliverables are expected to include a modernization strategy, migration plan, technical documentation, automated deployment capabilities, and long-term operational support. Support must include maintenance, bug-fixing, and enhancements with a focus on maintainability, scalability, and risk mitigation. The outcome will be a modernized, functionally equivalent PTS with improved security, reliability, and performance.

Open
Application Deadline

April 27, 2026

Apply
Questions? Contact

Procurement Schedule

Process Step Timing
Release of RFP March 30, 2026
Questions due to MassCEC via email to ehines@masscec.com April 3, 2026
Questions with Answers Posted to MassCEC Website April 9, 2026
to April 15, 2026
Proposals Due April 27, 2026
Interviews of Top Applicants Mid-May, 2026
Notification of Award Early June, 2026

 

Apply

Application Process

Proposals must be submitted to Erica Hines, Senior Director, at ehines@masscec.com no later than 11:59 PM Eastern Time on Monday, April 27, 2026. The subject line must include “RFP: PTS-2026-01”. Only responses that include all required documents and address each section of the RFP will be considered.

Under no circumstances will MassCEC accept responses past the deadline.

Please include a brief summary of you or your organization’s commitment to DEI and/or EJ principles. If available, please provide or link to relevant materials and brief examples of initiatives or projects demonstrating this commitment.

Please disclose to MassCEC in your application any use of, or planned use of, generative AI either in responding to this RFP or in carrying out the scope of work required for the project or services, if awarded. MassCEC reserves the right to review submitted materials to determine whether generative AI was likely used, and reserves the right to accept or reject any proposed uses of generative AI, request supplemental non-AI generative materials, or cancel or rescind an award where generative AI has been used without MassCEC approval.

Application Materials

Frequently Asked Questions

GENERAL INFORMATION

1. What level of modernization is expected: refactor, rebuild, or functional enhancement?

The level of modernization is not predefined. Phase 1 will assess the current system and define a recommended modernization approach, which may include targeted refactoring, component‑level redesign, and/or functional enhancements. A full rebuild is not assumed and must be clearly justified if proposed. Phase 2 will be limited to the implementation of the approved approach. The selected vendor will be responsible for documenting rationale, tradeoffs, risks, and implementation planning as part of their recommendation.

2. What service levels are required for ongoing support, including response time targets, uptime expectations, and support coverage hours?

Formal service‑level agreements (SLAs) are not predefined. Respondents should propose standard support models, including response times, uptime targets, escalation paths, and coverage hours, with clear differentiation between critical and non‑critical issues. Final service levels will be negotiated and incorporated into the contract.

3. What downtime window, if any, is acceptable during system migration or cutover activities?

Acceptable downtime has not been pre-defined. Any migration or cutover activity must minimize business disruption and will be subject to advance planning, testing, rollback procedures, and MassCEC approval. Respondents should clearly document downtime assumptions and continuity measures in their proposed approach.

FAQs continues...

4. Are there specific security or compliance frameworks the system must align to (e.g., NIST, SOC 2, FedRAMP)?

The modernized system is expected to align with MassCEC and Commonwealth IT security requirements and be broadly NIST‑aligned, though formal certification is not required. Vendors must describe how their approach meets applicable security, privacy, and data‑protection expectations.

5. Which integrations require third‑party coordination, and who is responsible?

The PTS integrates with external systems, including program registries, reporting APIs, and other data exchanges. A detailed inventory will be provided during Phase 1. The selected vendor will be responsible for coordinating all technical testing, scheduling, and issue resolution with third parties. MassCEC will support initial introductions and provide business context as needed.

6. What environments currently exist, and who manages them?

The PTS currently operates across standard environments (development, test, staging, production). Additional details will be provided during Phase 1. The selected vendor will be responsible for evaluating the environment strategy and improving deployment and management processes where appropriate.

7. What criteria will be used for acceptance of deliverables?

Each phase will have documented deliverables and acceptance criteria defined at phase initiation. Acceptance is based on completeness, clarity, alignment with scope, demonstrated functionality (as applicable), and adherence to agreed service expectations. All deliverables require formal MassCEC review and written sign‑off prior to phase continuation.

8. How are ongoing enhancements distinguished from change orders during Phase 3?

Ongoing enhancements include minor feature improvements, usability refinements, and incremental changes that do not materially alter scope or architecture. Change orders are required for work that materially alters functionality, scope, technical architecture, or introduces major new features. MassCEC retains final authority in classification and prioritization through a formal intake and approval process.

9. What version of .NET is the current PTS built on?

The current PTS application is built on .NET 8 (.NET 5+ platform). The selected vendor will validate all framework versions, dependencies, and upgrade constraints during Phase 1.

AZURE INFRASTRUCTURE

10. Are there existing automated tests or known areas of technical debt? Will vendors receive code access?

Existing automated testing, test coverage, and areas of technical debt will be assessed and validated during Phase 1. Upon contract award and execution of an NDA or data‑use agreement, the selected vendor will be granted access to the PTS codebase, database schema, and available architecture documentation.

DATA & INTEGRATIONS

11. Can MassCEC share the current Azure hosting topology and CI/CD details?

High‑level information regarding Azure services, infrastructure configuration, and CI/CD pipelines will be made available during Phase 1. The selected vendor will be expected to review existing infrastructure, deployment practices, and pipelines and recommend improvements aligned with security and reliability best practices.

12. How are production and registration records stored?

The PTS utilizes a primary SQL Server database for core system data, along with a Cosmos DB data store supporting CPS program production data. Additional data architecture details will be provided during Phase 1.

13. What is the data exchange format for NEPOOL GIS and other APIs?

PTS integrations include a mix of file‑based and API‑based exchanges. Integration documentation and specifications, where available, will be provided upon contract award. The selected vendor is expected to validate, document, and modernize integrations as part of Phase 1 findings.

FUTURE STATE & MASSCEC PREFERENCES

14. Is Renewable Thermal (RT) integration fully defined?

The RT integration scope is not fully predefined. Phase 1 is expected to assess requirements, data structures, and integration approach, with implementation proceeding in Phase 2 based on approved scope and priorities.

15. Does MassCEC have a preferred modernization or hosting approach?

MassCEC does not mandate a specific modernization or hosting model. Respondents should propose solutions aligned with system longevity, maintainability, scalability, and security. Final architectural decisions will be informed by Phase 1 recommendations.

16. Are there technology standards or policies vendors must follow?

Vendors must comply with applicable MassCEC and Commonwealth IT, security, accessibility, and procurement policies. Any required standards or constraints will be shared during contract negotiation and Phase 1 execution.

ACCESSIBILITY & REGULATORY CONSTRAINTS

17. Does MassCEC prefer open‑source or commercial tools?

MassCEC has no strict preference. Solutions should be cost‑effective, secure, well‑supported, and sustainable. Vendors must clearly articulate tradeoffs, including total cost of ownership and vendor lock‑in considerations. Comprehensive documentation is a required deliverable.

18. Are there accessibility requirements beyond WCAG 2.1 AA?

The modernized PTS must meet WCAG 2.1 AA accessibility standards. Vendors should identify any additional applicable accessibility considerations and describe how compliance will be validated.

19. Are there planned regulatory changes in the next 12–24 months?

MassCEC anticipates ongoing regulatory evolution. The system architecture should be flexible and configurable to accommodate future regulatory changes without significant re‑engineering.

20. Are there deployment blackout windows?

MassCEC avoids deployments immediately before or during critical reporting windows, including the monthly 10‑day production reporting period and quarterly reporting cycles. Deployment timing will be coordinated to minimize risk.

EVALUATION & CONTRACT

21. Is there an incumbent vendor and transition support?

An incumbent vendor currently supports the PTS. MassCEC expects a structured transition and knowledge‑transfer period as part of Phase 1 onboarding.

22. Are COMMBUYS or MMARS registration required?

Vendors must comply with all Commonwealth and MassCEC contracting requirements. Any required registrations will be completed prior to contract execution.

23. Can Phase 2 pricing be finalized after Phase 1?

MassCEC recognizes that Phase 2 scope depends on Phase 1 findings. Respondents may propose an indicative Phase 2 pricing approach with final fixed‑fee pricing subject to Phase 1 deliverables, roadmap approval, and contract amendment.

24. Will MassCEC designate a technical point of contact?

MassCEC will designate appropriate business and technical points of contact during Phase 1. Strategic oversight will remain with the Senior Director, with working‑level coordination supported by designated technical staff.