RFI27007142 Agency Specifications.pdf

PDF 227 KB Posted

Attached to
DPUC Custom Software System for Gas Pipeline Safety Program
Solicitation number
RFI27007142
Issued by
Providence County, Rhode Island

About this file

This is a Request for Information (RFI) issued by the State of Rhode Island, Division of Public Utilities & Carriers (DPUC), seeking information from qualified vendors regarding a custom or heavily configurable software system to support the State's Gas Pipeline Safety Program. The RFI is exploratory in nature and does not obligate the state to issue a subsequent Request for Proposals or commit to procuring any goods or services. The DPUC administers Rhode Island's federally certified pipeline safety program under partnership with the U.S. Department of Transportation's Pipeline and Hazardous Materials Safety Administration (PHMSA) and is responsible for inspecting and auditing approximately 3,220 miles of distribution mains, 204,057 service lines, three Liquefied Natural Gas facilities, transmission lines, master meter systems, and jurisdictional commercial propane systems. The Division currently relies on a combination of PHMSA inspection forms, internal checklists, electronic file storage, and spreadsheets, and seeks a dedicated system to serve as the system of record for inspections, findings, enforcement, documents, and photographs. No cost proposals are requested or will be considered as part of this RFI response.

Vendors are requested to provide information addressing company background and relevant experience, proposed approach and architecture, core functional capabilities, security and compliance with Enterprise Technology Strategy and Services (ETSS) policies, integration considerations, data migration and implementation strategy, and any additional relevant information. The proposed solution must comply with all applicable ETSS policies, including security, accessibility, multi-factor authentication, and cloud requirements. Key capabilities sought include configurable inspection forms mapped to federal pipeline safety regulations, mobile and tablet field support with offline functionality, high-volume photo and document storage, automated letter and document generation, role-based access controls, inspector training tracking, incident investigation management, and comprehensive reporting capabilities to support PHMSA grant reporting and state program performance metrics. The file specifies no specific response deadline or contract award date, as this RFI is information-gathering only.

View the file

Other files

File Type Posted
RFI27007142_Nov_20_26_solicitation_doc.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

2018-1 Page 1 of 4 Revised 06/10/2022

RFI 27007142 - REQUEST FOR INFORMATION

TITLE: DPUC Custom Inspection and Audit Management System for Gas Pipeline Safety Program

SECTION A. INTRODUCTION

The State of Rhode Island, through the Division of Public Utilities & Carriers (DPUC), is issuing this Request for Information (RFI) to gather information from qualified vendors regarding a custom or heavily configurable software system to support the State’s Gas Pipeline Safety Program.

This RFI is exploratory in nature. It does not obligate the State to issue a subsequent Request for Proposals (RFP) or any other solicitation, nor does it constitute a commitment to procure any goods or services. Responses to this RFI will not preclude any vendor from participating in a future solicitation. No cost proposals are requested or will be considered.

The DPUC administers Rhode Island’s federally certified pipeline safety program under R.I.G.L. §39-3-40 and the partnership with the U.S. Department of Transportation’s Pipeline and Hazardous Materials Safety Administration (PHMSA).

The program is responsible for inspecting and auditing the construction, operation, and maintenance of intrastate natural gas pipelines (approximately 3,220 miles of distribution mains and 204,057 service lines), three Liquefied Natural Gas (LNG) facilities, 2000-foot transmission line, master meter systems, and jurisdictional commercial propane systems. Activities include comprehensive standard inspections, construction and maintenance observations, specialized inspections (DIMP, OQ, public awareness, drug and alcohol, control room management, etc.), incident investigation, and enforcement.

The Division currently relies on a combination of PHMSA inspection forms, internal checklists, electronic file storage, and spreadsheets. It seeks a dedicated system that becomes the system of record for inspections, findings, enforcement, documents, and photographs. The Division does not intend to use or replace PHMSA’s Inspection Assistant (IA) as its primary system.

Any proposed solution must comply with all applicable Enterprise Technology Strategy and Services (ETSS) policies (formerly DoIT), including security, accessibility, multi-factor authentication, and cloud requirements. Policies are available at https://www.ri.gov/app/doa/policies.

SECTION B: REQUEST FOR INFORMATION

https://www.ri.gov/app/doa/policies

2018-1 Page 2 of 4 Revised 06/10/2022

This RFI outlines the type of information being solicited and response structure requested from potential respondents.

A. Background

Respondents are requested to address the following topics. Please structure responses clearly so they can be compared across vendors. Do not include pricing.

1. Company and Relevant Experience

• Brief overview of the company.

• Experience developing or configuring inspection, audit, case management, or regulatory compliance systems for state pipeline safety programs, public utility commissions, or similar regulatory agencies.

• Specific experience with high-volume photo and document storage for critical infrastructure or regulated industries.

• References (if available) for comparable systems.

2. Proposed Approach and Architecture

• Recommended platform or architecture (custom application, low-code/configurable platform such as Salesforce or similar, hybrid, etc.).

• Hosting model (cloud preferred if it meets ETSS requirements; describe security controls).

• Approach to building or configuring the Division’s existing inspection forms for each inspection type into the system.

• Ability to support tablet/mobile use in the field, including offline data entry and photo capture with later synchronization.

• Print-friendly formatting of completed forms, reports, letters, and packages.

3. Core Functional Capabilities

• Describe how the proposed solution would address the following:

• Configurable inspection forms/checklists mapped to 49 CFR Parts 191, 192, 193, and 199 and Part 40 (and state rules).

• Scheduling and tracking of inspections by type, operator, and inspector.

• Findings, probable violations, and enforcement workflow (NOPVs, notices of concern, letters of concern, warning letters, operator response tracking, and closure).

• Built-in letter and document templates (NOPV, NOC, LOC, Warning, and other correspondence) that automatically pull relevant data from the inspection or enforcement record and produce print-ready output.

• Operator and inspection-unit history view (prior inspections, findings, documents, and photos).

• High-volume photo and document storage and retrieval linked to specific inspections, with full audit trail.

• Advanced reporting and dashboards (by inspector, by month, by inspection type, coverage, open items, etc.).

• Reporting or data export that supports PHMSA grant reporting and state program performance metrics.

2018-1 Page 3 of 4 Revised 06/10/2022

• Document generation (exit summaries, letters, reports) using templates that pull data from the inspection record.

• Search capabilities across operators, inspections, findings, and documents.

• Role-based access and comprehensive audit logging.

• Incident and accident investigation tracking (opening, documenting, linking to operators or related inspections, and closing investigations).

• Inspector training and qualification tracking (recording completed PHMSA

T&Q courses, expiration dates, and inspection types an inspector is qualified to perform).

• Operator inventory and inspection-unit list management.

• Simple review or approval workflow (e.g., inspector completes form or letter draft, supervisor reviews before finalization).

• Version history on forms and letter templates.

• Notifications and reminders (upcoming inspection cycles, overdue operator responses, approaching deadlines, training expirations, etc.).

• Records retention and disposition support (ability to apply retention schedules and support export or archival).

• Basic location tagging or GIS reference on inspections and photos (even if full mapping is not required).

• Bulk export and reporting tools.

4. Security, Compliance, and ETSS Requirements

• Approach to meeting applicable ETSS policies (security controls aligned with NIST frameworks, MFA, encryption, access control, audit and accountability, contingency planning, etc.).

• Accessibility compliance (WCAG 2.1 AA) for web and mobile interfaces.

• Security measures specifically for storing and protecting inspection records, operator data, and photographs related to critical infrastructure.

• Evidence of compliance certifications or attestations (e.g., SOC 2, FedRAMP, StateRAMP, ISO 27001, or equivalent) that would support ETSS review.

5. Integration Considerations

• Any capabilities or experience integrating with or exchanging data with state

ERP systems (such as Workday), particularly for single sign-on, user provisioning, or optional export of activity data.

• Other potential integrations (email, document management, etc.).

6. Data Migration and Implementation

• Approach to migrating or making searchable existing historical inspection records, spreadsheets, and document libraries.

• Typical implementation approach and timeline for a system of this scope.

• Training and knowledge transfer model so Division staff can manage forms, letter templates, users, and other configurable elements.

• Ongoing support and maintenance model.

• Approach to future form, letter template, or regulatory changes without major custom development.

2018-1 Page 4 of 4 Revised 06/10/2022

7. Additional Information

• Any other capabilities, risks, or recommendations the vendor believes are relevant.

• Examples of dashboards, mobile interfaces, letter templates, or printed outputs from similar systems (descriptions or links are acceptable).

SECTION A. INTRODUCTION
SECTION B: REQUEST FOR INFORMATION
A. Background

File details come from the government source that posted it. Updated .