RFO 455-26-1018

Salesforce and Tools Implementation Services and Support (STISS)

RAILROAD COMMISSION OF TEXAS

REQUEST FOR OFFER

APPLICATION MAINTENANCE & SUPPORT/APPLICATION

DEVELOPMENT FOR

SALESFORCE AND TOOLS IMPLEMENTATION SERVICES

AND SUPPORT (STISS)

Railroad Commission of Texas

1701 N. Congress Ave, Austin, TX 78701

Request for Offer (RFO) No. 455-26-1018

Solicitation Posting Date

April 6, 2026

Response Due Date:

May19, 2026

Time (Central Time):

2:00 p.m.

Salesforce and Tools Implementation Services and Support (STISS

Attachment 1

Table of Contents Part A Project Overview

A.1. Definitions and Acronyms

A.2. Introduction

A.3. Background

A.4. RRC Overview

A.5. Guiding Principles

A.6. RRC Operational Goals

A.7. Current State Challenges

A.8. Stakeholders

A.9. Multi-Vendor Solutions ( Joint Venture)

A.10. Multiple Responses

A.11. Term of Contract/Period of Performance

A.12. Description of Work

A.13. Warranty

A.14. Project Risks

A.15. Service Level Agreement and Vendor Responsibilities

A.16. Initial Workorder

A.16.1. IETRS Phase 5 Texas Damage Reporting Form (TDRF) System

Replacement

A.17. Future Workorder Possibilities

A.17.1. CASES Enhancements

A.17.2. EVENTS Enhancements

A.17.3. PIPES Enhancements

A.17.4. Critical Infrastructure Inspection System (CIIS) Enhancements

A.17.5. RRC MAP Enhancements

Attachment 1

A.17.6. MINERS Enhancements

A.17.7. Alternative Fuels Online Filing System (AFOS)

A.17.8. Gas Utility Regulatory Filings and Auditing System

A.18. Assumptions

A.19. RRC Resources

A.20. High Level Workorder Deliverable Items

A.21. Requirements for Workorder Deliverables

A.22. RRC Workorder Process

A.23. Workorder Amendments

A.24. RRC Workorder Expectations of Vendor

A.25. Deliverable Definition Process

A.26. Vendor Workplan Requirements

A.27. Key Anticipated Deliverables for Workorders

A.28. Revisions to Approved Vendor Workplan

A.29. Notice to Proceed

A.30. Deliverable Acceptance

A.31. RRC Reliance on Vendor’s Workplan and Notice of Completion

A.32. General RRC Roles and Responsibilities

A.33. General Vendor Roles and Responsibilities

A.34. Reports and Meetings

A.35. Project Management & Deliverables

A.36. Project Completion Criteria

A.37. Vendor Service Requirements

A.38. Service Change Management

A.39. Transition Plan

Attachment 1

A.40. Invoices

Part B Instructions to Vendors

B.1. Submittal Instructions

B.2. Prohibited Communications, Point of Contact

B.3. Confidential Information, Public Information Act Disclosure

B.4. Exceptions to Provisions

B.5. Organization of Response

B.5.1. Title Page (Section A)

B.5.2. Cover Letter (Section B)

B.5.3. Company Experience & Qualifications (Section C)

B.5.4. Staff Resumes & References (Section D)

B.5.5. Mandatory Disclosures (Section E)

B.5.6. Pricing (Section F)

B.6. Anticipated Schedule of Events; Response Guidelines

B.7. Questions and Answers

B.8. Response Evaluation Criteria

Part C Attachments included with Solicitation

Salesforce and Tools Implementation Services and Support (STISS)

PART A PROJECT OVERVIEW

A.1. Definitions and Acronyms When capitalized, the following terms and acronyms have the meaning set forth below in Table 1 Definitions and Acronyms. All other terms have the meaning set forth in

Webster’s II New College Dictionary

Table 1: Definitions and Acronyms

Addendum/Addenda Modification to this solicitation, issued by

RRC and posted to the Texas Comptroller of Public Accounts ESBD website

(http://www.txsmartbuy.com/esbd) prior to

Response due date.

Alternative Fuels Safety (AFS) The Alternative Fuels Safety Department operates programs related to enforcing the State statutes and Commission regulations related to alternative fuels

(LPG/CNG/LNG).

Alternative Fuels Online Filing System

(AFOS)

A system that allows users to view class and examination schedules related certification for the safe transportation, storage, distribution, and use of the alternative fuels.

Case Administration Service Electronic

System (CASES)

A system that allows users to search and view the RRC’s case information online, including processed case documents.

Compliance Check An audit of Vendor’s compliance with the

Contract may be performed by a third-party auditor, RRC’s internal audit department, RRC’s contract management http://www.txsmartbuy.com/esbd

Attachment 1 and/or purchasing staff, or RRC’s authorized designees.

Critical Infrastructure Inspection System

(CIIS)

A system that tracks infrastructure designated as critical to be inspected for weatherization, allows for penalties to be assessed and helps populate the GIS

MAP for submission to Public Utilities

Commission (PUC).

Contract The written agreement, if any, executed by the authorized representative of RRC and the Vendor, that formalizes the terms, provisions, covenants, and obligations, including but not limited to those contained in this solicitation, of the respective parties to the agreement.

Contract Documents Includes the fully executed agreement between RRC and Vendor and fully executed amendments thereto (if any), Terms and Conditions of the Contract”, specifications, solicitation documents, purchase orders, and any exhibits, appendices, and attachments thereto and incorporated therein through written reference.

Contractor The individual or entity is qualified to provide the goods and/or services sought by RRC pursuant to this solicitation and who is ultimately selected to carry out the

Attachment 1 requirements stipulated in this solicitation and any resulting contract.

Days The word “days” shall mean calendar days unless otherwise specifically noted.

Business days shall mean Monday through Friday except holidays officially listed on the State of Texas Holiday

Schedule and/or on which RRC headquarters office is closed.

EDI Electronic Data Interchange

Event and Registration Management

System (EVENTS)

A registration system for RRC conferences, seminars, webinars & other events.

Fiscal Year (FY) RRC’s FY begins September 1 of one year and concludes August 31 of the following year.

Notice to Proceed (“NTP”) The formal written authorization issued from RRC to Vendor, which indicates work under the Contract or Workorder issued thereunder is authorized to commence in accordance with the terms and conditions of the Contract and a

Workorder issued thereunder and on, but not sooner than, the date specified within the Notice to Proceed.

Mine Inspection & Enforcement Reporting

System (MINERS)

An application used to manage surface mining permits, inspections, enforcement activities, and land reclamation oversight.

Attachment 1

It supports internal regulatory workflows, public search and reporting, integrations with legacy systems, and robust document management and reporting capabilities.

MVP Minimum Viable Product

Offeror An individual or entity who submits a response to this solicitation.

Party Individually either RRC or Vendor;

collectively, “Parties”.

Pipeline Inspection, Permitting, &

Evaluation System (PIPES)

An application that allows users to search and upload records associated with the

RRC’s Pipeline Safety Program.

Purchase Order RRC’s fiscal form or format used when making a purchase (e.g., formal written

Purchase Order, Procurement Card, Electronic Purchase Order, or another authorized instrument.) An RRC

Purchase Order may be considered a

Contract or one document of a collective set of Contract Documents that comprise a Contract.

RAD Requests for additional data.

Railroad Commission of Texas (RRC) The state agency responsible for the issuance of this solicitation.

Attachment 1

Railroad Commission Access

Management Process (RAMP)

The process by which RRC will manage accounts and provide access to new RRC applications

RRC Authorized Representative The individual authorized to make decisions on behalf of RRC.

Railroad Commission Mapping

Automation Portal (RRC MAP)

The online portal that allows users to identify the regulated entities that make up the supply chain of natural gas within their assigned organization.

Response An expression of interest submitted by a

Offeror to RRC because of this solicitation that contains the Offeror’s statement of qualifications and other information evidencing the Offeror’s qualifications to perform the services and work required under the Contract

Request For Offer (RFO) This solicitation document requesting submittal of offer for the work requested.

This RFO includes all attachments, appendices and exhibits hereto and/or that are incorporated by reference as though fully set forth within, and any

Addenda that may be issued following issuance date of the original RFO document set.

Solicitation and Contract Documents Those documents identified as a component of the solicitation, including all exhibits, attachments, and appendices thereto and/or that are incorporated by

Attachment 1 reference as though fully set forth within, and any Addenda that may be issued following issuance date of the original solicitation document set, and those documents identified as a component of the Contract agreement between RRC and the Offeror awarded a contract arising from the solicitation.

State The State of Texas

TAC Texas Administrative Code

Term The period during which the Contract remains in force and effect. Extension of the Term shall occur only through written amendment to the Contract, fully executed prior to date of the Contract’s then current Term.

Texas Cyber Command (TXCC) The state agency established in TGC

2063 that is responsible for preventing and responding to cybersecurity incidents that effect governmental entities and critical infrastructure in this state.

Texas Damage Reporting Form (TDRF) An application wherein users can create, view, and edit TDRF reports.

TGC Texas Government Code

Vendor The individual or entity qualified, in RRC’s sole determination, to provide the goods and/or services sought by RRC pursuant to this solicitation and who is ultimately

Attachment 1 selected to carry out the requirements stipulated in this solicitation, and any resulting contract and Workorder issued under such contract.

Veteran Heroes United in Business

(VetHUB)

As defined within Texas Government

Code Chapter 2161 and amended by the

Texas Comptroller of Public Accounts in its emergency rules, effective December

2, 2025.

Workorder A description of a specific job or project arising under the Contract and that includes details applicable to the location(s), goods, services, and incidentals of work to be performed.

A.2. Introduction In accordance with applicable provisions of Texas Government Code (TGC) Chapters

2054, 2063, 2155, 2156, 2157 and 2261, the RRC issues this Request for Offer (RFO) to qualified entities to submit a response to provide to RRC information technology services and support as described herein and in accordance with all terms, conditions, and specifications contained within the RFO and Contract Documents. Responses must be received by the RRC, Contract Management Section, via email no later than 2:00PM

(CT), Tuesday, May 19th, 2026 for Solicitation No. 455-26-1018, Information Technology

Services: Salesforce and Tools Implementation Services and Support.

A.3. Background RRC seeks to procure implementation services from one or more Vendors in order to maintain, support, enhance, and expand RRC’s current IT systems. RRC is continuing its commitment to quickly and efficiently transition from outdated and often unsupported applications to a modernized applications suite with readily available support.

Attachment 1

The objectives of the Salesforce and Tools Implementation Services and Support RFO shall be to enable the RRC to:

• Respond to industry and leadership needs for modern technology interactions by implementing solutions in the Salesforce Platform.

• Respond to industry and leadership needs for continued modern technology interactions by enhancing existing solutions in the Salesforce Platform.

• Respond to industry, rule and regulation changes by maintaining support for the

Salesforce applications.

A.4. RRC Overview RRC is the State of Texas agency with primary regulatory jurisdiction over the oil and natural gas industry, pipeline transporters, the natural gas and hazardous liquid pipeline industry, natural gas utilities, the alternative fuels Liquefied Petroleum Gas, Compressed Natural Gas, Liquefied Natural Gas (LPG/CNG/LNG) industries, coal surface mining, and uranium exploration operations.

The RRC’s stated mission is:

“...To serve Texas by our stewardship of natural resources and the environment, our concern for personal and community safety, and our support of enhanced development and economic vitality for the benefit of Texans.”

By continuing to develop and enhance RRC’s Salesforce platforms with business processes currently supported by older frameworks, RRC will carry on with its mission of stewardship of natural resources and the environment by allowing us to maintain and enhance current systems to more quickly process user requests.

The more efficient RRC is in processing applications, the more efficient the operators can be. This will improve economic vitality for the benefit of Texans.

A.5. Guiding Principles The RRC recognizes that ensuring the efficiency and effectiveness of its programs is more than allocating and expending resources responsibly. The RRC seeks to further develop systems, workforce, and infrastructure to address complicated and evolving

Attachment 1 challenges to the state’s energy industries. Robust and secure information management systems, collaboration to develop innovative solutions, a highly skilled and diverse workforce, and a commitment to sustainability are the pillars that support the efficiency, transparency, accountability, and effectiveness of RRC programs.

A.6. RRC Operational Goals

• Protect public safety and the environment through compliance and enforcement strategies using appropriate tools that are effective, efficient, and transparent.

• Review current rules and forms to ensure relevance to current technology and industry practice in order to more effectively maximize protection of public safety and the environment while minimizing the cost of compliance for the regulated industries.

• Enhance collection of, access to, and use of data to improve RRC programs that ensure public safety and environmental protection.

• Invest in the quality and sustainability of the RRC’s employees through needs assessment and professional development creating the optimal workforce.

• Encourage public engagement and increase educational outreach to improve understanding of the RRC’s role.

A.7. Current State Challenges RRC has seen an increase in demand for RRC services to be delivered through IT assets. The RRC’s business processes are supported through a blend of methods including manual/paper-based processes, mainframe systems built in the 1960s, web based online filing systems implemented in the past twenty years, and RRC staff-supported desktop systems.

Any contract arising from this solicitation is intended to aid the RRC in its commitment to quickly and efficiently transition from outdated and often unsupported applications to

Salesforce, a modernized applications suite with readily available support.

A.8. Stakeholders The solution shall be leveraged by all divisions within the RRC as well as external operators and the general public.

Attachment 1

As of 2025, RRC employs approximately 1000 employees. The RRC is comprised of multiple divisions, each charged with specific responsibilities related to executing the

RRC’s mission, described in Table 2. RRC Business Divisions and Responsibilities below:

Table 2:RRC Business Divisions and Responsibilities

RRC Business Division

Overview of Responsibilities

Operations Operations supports The RRC in its mission through a variety of functions, including:

• Hearings Division.

• Critical Infrastructure Division (CID).

• Procurement (Contracts and Purchasing).

• Facilities/Fleet/Asset Management and Support Services.

• Safety and Continuity of Operations (COOP).,

• Ssupport to the State Operations Center when requested.

Operations also develops and coordinates internal organizational policies to improve business efficiency and ensure employees have sufficient tools and resources to perform their duties in support of the RRC’s mission.

Critical

Infrastructure

Division

RRC’s CID is committed to serving the people of Texas by ensuring the natural gas industry consistently incorporates weatherization and reliability standards and practices to achieve uninterruptible natural gas production throughout the calendar year including periods of severe weather.

The CID will vigilantly oversee and manage adherence to weatherization rules, adopted by the RRC, including ensuring companies within the natural gas supply chain register their assets as Critical Infrastructure.

Financial

Services

Division

The Financial Services Division provides financial services and support to the divisions of the RRC. The division’s policies, procedures, computing systems and structures are designed to ensure and maintain the fiscal integrity of the RRC.

Attachment 1

RRC Business Division

Overview of Responsibilities

Information

Technology

Services

Division

The Information Technology Services (ITS) Division is responsible for providing automated information management services for the RRC in the central and district offices. The ITS Division resources are dedicated to support the Commission's divisions and leadership with their computing infrastructure needs.

The ITS Division is responsible for ensuring the information resources essential to operate RRC activities including hardware, software and applications, are available and performing at optimal levels. System availability is a critical factor for enabling the RRC to meet regulatory requirements and achieve performance objectives. The ITS Division provides Customer Service and Operations, Desktop support, Network

Administration, Program and Process Management and Applications

Development and Maintenance.

Government

Relations

Division

Government Relations serves as the RRC’s liaison with state leadership and members of the Texas Legislature on matters of policy affecting the

RRC and constituent affairs. During legislative sessions, government relations identifies and monitors important issues and legislation that could affect the RRC and industries that fall under the jurisdiction of the RRC. The division also works closely with partner state agencies on issues of mutual interest or jurisdiction, when necessary.

Communications

Division

The Communications Division serves as the primary contact with the public, media and stakeholder groups to distribute information about the roles and responsibilities of the RRC in regulating exploration and production of the state’s energy resources. The division is responsible for maintaining the

RRC’s various communications platforms, including the RRC’s websites, social media channels, news releases, monthly newsletters, and annual

Year in Review reports. In addition, the division coordinates outreach to

Texas citizens, industry, domestic and foreign government officials and delegations, through speaking engagements, special event planning and

Attachment 1

RRC Business Division

Overview of Responsibilities training opportunities. The Communications Division also serves in the RRC ombudsman role and responds to inquiries from the public and industry representatives.

Office of

General

Counsel

Division

The Office of General Counsel includes the General Law Section and the

Legal Enforcement Section. The General Counsel is the RRC’s legal advisor.

The General Law Section provides legal advice to the Commissioners, the

Executive Offices, and the various Divisions of the Commission. It handles contracts, open records, records retention, personnel matters, rulemaking, open meetings, and ethics for the Commission. In addition, the General Law

Section is responsible for hearings on various matters such as permit renewal, surface mining, and other regulatory issues.

The Legal Enforcement Section’s primary responsibility is the enforcement of Commission statues, rules, and regulations concerning safety and pollution in the energy industry. The Legal Enforcement Section supports the Office of the Attorney General in lawsuits regarding Legal Enforcement matters as well as bankruptcies that may affect the Commission. The Legal

Enforcement Section also manages other types of hearings including Rule

15 hearings on P-5 renewals.

Hearings

Division

The Hearings Division is responsible for scheduling, conducting, and preparing recommendations on hearings concerning oil and gas, gas utilities, pipeline safety, AFS, and surface mining matters within the

Commission’s jurisdiction. The Commission’s hearings are presided over by eight administrative law judges and eight technical examiners.

Oil & Gas

Division

The Oil and Gas Division regulates the exploration, production, and transportation of oil and natural gas in Texas. Its statutory role is to: (1) prevent waste of the state's natural resources; (2) to protect the correlative rights of different interest owners; (3) to prevent pollution; and (4) to provide

Attachment 1

RRC Business Division

Overview of Responsibilities safety in matters such as hydrogen sulfide. The division accomplishes these goals by permitting and reporting requirements; by field inspections, testing programs and monitoring industry activities in the field; and through programs to remediate abandoned wells and sites using fees and taxes paid by industry and the public. The Oil and Gas Division is headquartered in Austin, Texas with nine district offices spread over the state.

Oversight &

Safety Division

The Oversight and Safety Division has responsibility for Alternative Fuels, Gas Services and Pipeline Safety.

The AFS department enforces both the state law and Commission regulations on the safe transportation, storage, distribution and use of alternative fuels, which includes liquefied petroleum gas (LPG) (commonly referred to as propane); compressed natural gas (CNG) and liquefied natural gas (LNG). The department conducts safety evaluations of stationary facilities and mobile equipment, licensing companies engaged in alternative fuel activities and provides training and licensing to individuals working in the alternative fuels industries.

The Gas Services department’s responsibilities include establishing and ensuring just and reasonable natural gas utility rates that promote safe, efficient, reliable, cost-based, investor-owned utility service to the citizens of

Texas. The department’s Market Oversight section participates in contested rate determinations, reviews non-contested filings, collects and publishes natural gas utility tariffs, resolves consumer complaints and informal industry complaints, enforces the Commission’s requirements for utilities to file their gas curtailment plans, and administers a communication protocol during times of potential natural gas shortages. The department’s Utility

Audit section administers the gas utility tax (both in-house and by field audit), audits natural gas utilities to ensure the proper computation and billing of authorized rates, and determines gas utility status.

Attachment 1

RRC Business Division

Overview of Responsibilities

The Pipeline Safety department ensures that the pipelines in Texas’ pipeline infrastructure (the largest in the nation) are designed, constructed, operated and maintained safely. The Commission is authorized by the

Texas Utilities Code and Texas Natural Resources Code to regulate the safety of intrastate gas, hazardous liquid and CO2 pipelines in the state.

The Commission is also certified by the U.S. Department of Transportation

Pipeline and Hazardous Materials Safety Administration for the enforcement of federal pipeline safety regulations for intrastate pipeline facilities under the federal Pipeline Safety Act. In addition, the Pipeline Safety department enforces compliance by intrastate pipeline operators with federal and state laws and regulations and promotes public safety and awareness through the pipeline damage prevention program for Texas.

Public

Engagement

Division

The Office Of Public Engagement serves as a liaison to the citizens of

Texas in addressing their questions and concerns and ensures excellent customer responses.

They educate the public on the jurisdictional authority of the RRC and the impact of the Texas energy industry to the state, U.S. and global economies, and overall benefits to everyday lives.

Additionally, they perform outreach to the public and internal and external stakeholders on state laws, RRC rules, and procedures and processes

Surface Mining

& Reclamation

Division

The Surface Mining and Reclamation Division (SMRD) is responsible for regulating surface mining for coal and uranium exploration. Companies mining coal/lignite in Texas must have an RRC permit and post a bond for each site they operate. Division personnel also make, at a minimum, monthly visits to mine sites, checking for compliance with coal mining regulations.

SMRD also administers the reclamation of dangerous or environmentally harmful abandoned mine sites that were mined prior to the implementation of the federal surface mining law in 1975. Under this program, SMRD

Attachment 1

RRC Business Division

Overview of Responsibilities ensures the safety of the public and protects the environment by eliminating these hazardous abandoned mines throughout the state.

A.9. Multi-Vendor Solutions ( Joint Venture) Multi-Vendor (e.g., joint ventures) responses will be allowed only if one party is designated as the Prime Contractor. If a Solution is proposed by more than one party, Vendor must list the parties as directed in the Response submission instructions.

Additionally, the Response must clearly identify the responsibilities of each party in the

Response. Services specified in the response may not be subcontracted without prior written approval of RRC, and approval of a request to subcontract shall not in any way relieve the Prime Contractor of responsibility for the accuracy and adequacy of the work. Additionally, any subcontracting must also be included on the Awarded Vendor's

Veteran Heroes United in Business Historically Underutilized Business (VetHUB)

Subcontracting Plan (HSP).

A.10. Multiple Responses A Offeror may not submit more than one response as a Prime Contractor in response to this Solicitation. However, sub-contracting contractors may participate in multiple responses.

A.11. Term of Contract/Period of Performance Any Contract resulting from this solicitation shall include an original term ending no later than August 31, 2028. At RRC’s discretion, the original Contract term may be extended/renewed for up to three (3) additional one-year optional renewal terms

(“Renewal Term”). Renewal Terms to any Contract shall be accomplished through a written amendment to the original Contract, fully executed prior to expiration of the

Contract, and shall incorporate all terms and conditions of the original Contract as may be amended by mutual agreement between the RRC and Vendor.

Attachment 1

A.12. Description of Work As a result of this solicitation, RRC expects to receive and evaluate Responses and subsequently enter into negotiations that may culminate in a single contract or multiple contracts with multiple Vendors for Salesforce and Tools Implementation Services and

Support (STISS) required to maintain, enhance, and expand RRC’s current Salesforce systems between RRC and the successful Vendor or Vendors (individually “Party”;

collectively, “Parties”.) Work may also be specific to building defined integrations among legacy systems, current technology systems, and future systems. Additional instructions and required information regarding a Response that includes a Prime

Contractor and Sub-Contractors are provided later in this RFO.

The implementation services include Project Management, Requirements Gathering, Business Analysis, Architecture, Data Modeling, Data Classification, Design, Integration

Testing, Systems Testing, Regression Testing, Application Development, Configuration and Customization Services, User Acceptance Testing Preparation and support, Accessibility Testing, Training, and Full Product Documentation. Integration services will include development of applications, communication, and data connectivity solutions.

These items are required to maintain, enhance, and integrate with RRC systems, built in the following platforms and frameworks. The platforms and frameworks that these systems are built in include, but are not limited to:

• Salesforce platform.

• Integration tools and other software to include, but not limited to databases, records management, and scheduling in use by RRC, including, but not limited to the following.

o MuleSoft o Informatica o GoAnywhere o Snowflake o Box o Neubus o Conga

Attachment 1 o JIRA o Copado o RunMyJobs

• Security tools and techniques in use by RRC.

• Data Classification tools and techniques in use by RRC.

o In order to meet the compliance requirements of TGC 2063, as well as TXCC standards for data security and maturity, Offeror must be able to create data models that minimize data interference between different entities while sharing common data elements when applicable. All data fields and data assets must be classified using Excel or Informatica (Cloud Data Governance and Catalog (CDGC) in accordance with TXCC data classification protocols.

Offeror must include within their response any additional statements, including any statements arising from Section B.1 Submittal Instructions of this Solicitation, or such other information Offeror deems necessary, valuable, and appropriate to fully inform

RRC of Offeror’s qualifications, expertise, and superiority in selection as Offeror for

Contract award. Vendor shall deliver Services, including but not limited to services detailed under A.16 Initial Workorder and A.17 Future Workorder Possibilities for the

RRC. Vendor shall deliver the Services in accordance with the terms and conditions of the Contract while adhering to the highest of applicable professional standards.

Offeror shall submit qualifications for any and all applicable services listed in this RFO.

Offeror must demonstrate proven experience in their response.

A.13. Warranty Please see the Warranty and Certification provisions for this RFO in the Sample

Contract (Attachment 6 Sample Contract). The selected Vendor will be responsible for providing the Warranties and Certifications in the Sample Contract.

A.14. Project Risks

• Multiple Vendors may be involved on work that overlaps or as joint solution. This will require coordination among parties and potential change management in-flight.

Attachment 1

• Funding certainty across multi-year contracts will be dependent on continued legislative approvals.

A.15. Service Level Agreement and Vendor Responsibilities Please see Attachment 11 for RRC’s Service Level Agreement.

A.16. Initial Workorder RRC is requesting that Offerors analyze the detail of work included in the Workorder items provided and submit a Workplan proposal with related costs to RRC.

A.16.1. IETRS Phase 5 Texas Damage Reporting Form (TDRF) System Replacement

The current TDRF online system is a Commission-maintained application for creating, viewing, and editing TDRF reports. The goal of this project is to implement the TDRF functionality in Salesforce. The objective is to work within the existing Inspection

Enforcement Tracking and Reporting System (IETRS) Salesforce framework and create a new TDRF Salesforce application. The TDRF Salesforce application would allow for streamlined processes that would reduce processing time and accessibility for both

RRC staff and the regulated community.

Below is the high-level scope of the project:

1. Allow external users (excavators/public- unauthenticated users and operators – authenticated users) to:

• Login through RAMP (for authenticated users).

• Submit TDRF forms online – including submitting documentation.

o System shall create an Incident Report for reports submitted by the external user and link to a parent Incident.

• Attach files (e.g. photos, proof of training course certification, etc.) when submitting a report (enhancement).

• Submit multiple incident reports/mass upload (authenticated external user) – previously referred to as “EDI Upload.”

• Submit violation payments. Implement an online payment option (enhancement).

Attachment 1

• Respond to non-compliance items.

2. Allow internal users (RRC staff) to:

• Process submitted reports and process dockets for non-compliance with the ability to email/mail notices directly within the application.

• Implement a process that connects to the CASES application for applicable non-compliant dockets (enhancement – currently this is a manual process).

• Implement an automated tool that gathers and prepares documents for monthly conference. The tool should also be able to automatically close dockets post-conference.

• Manually record payments from Therefore. - get register number which will bring in payment info into SF.

• Annotate excavator letters.

• Maintain internal dashboards for tracking and reporting on workload.

3. TDRF application connection with PIPES application, as needed, for accurate regulated community contact information.

4. Generate Letters – including but not limited to docket letters and non-compliance letters.

5. Migration of Data.

Salesforce system must support the following internal user functionalities:

1. Incident Management

• Incident and Report Creation: The system must allow for the creation of new incidents and damage reports. An incident is an online collection of one or more reports.

• Internal Report Creation: Users must be able to create an excavator report from an operator-submitted incident if the excavator report is missing.

Attachment 1

• Automated Matching: The system must be able to automatically link excavator reports to existing operator reports i.e. Find an existing incident and file a damage report that will be linked to that incident.

• Manual Matching (Re-parenting): The system needs a manual utility to link an operator report and an excavator report together if they were submitted individually. This utility should allow users to search for reports by incident date or excavator name.

• Report Deletion/Un-deletion: The system needs a utility for internal users to delete and undelete reports.

• Follow-Up and Notes: The system should have a feature for analysts to set follow-up dates and make internal, private notes for themselves on each incident.

The follow-up date should be a manual field.

• Workflows and Assignment: The system should support assigning incidents to specific reviewers.

• Report Status: The system must display the incident and report status.

2. Communication & Reporting

• Automated Letters: The system must be able to automatically generate and send out various types of letters to operators and excavators, including:

o No Report Letter o Homeowner Letter o Final Notice (another No Report letter) o Non-Jurisdictional Letter o No Penalty Letter

• Attachments: The system should allow operators to upload photos or files to their reports. Internal users must also be able to add attachments to reports, such as scanned documentation. Excavators do not have the ability to upload attachments through the public-facing system and instead email them.

• Data Queries: The system must have a robust query function for internal users to search for information.

Attachment 1

• Requests for Additional Data (RAD): The system should allow for the sending of

RADs to operators and excavators when there is conflicting data between two reports.

3. Administrative Functions

• Docket Management: The system must support the creation, withdrawal, scheduling, and closing of dockets. It should also handle related processes such as preparing docket conference materials and processing non-compliant dockets.

• Data Exports: The system needs to support the creation of documents and spreadsheets, as the current system uses Microsoft Excel, Access, and Word to manage conference data.

• User Roles and Access: The system needs to differentiate between user types, such as operators, excavators, and internal reviewers, and provide the appropriate access and functionality for each role.

• System Testing: The system should have a separate test environment for beta testing new features and training employees.

• Integrations: CASES, PIPES, payment portal, Xerox.

A.17. Future Workorder Possibilities RRC has identified additional efforts that may be implemented under the resulting contract for this RFO at a future time. These efforts are described in more detail below and are included in this RFO for Offerors to understand the type of work (both applications and integrations) that may be issued under the resulting contract. Although information is limited and binding pricing is not available at this time, the following sections describe the process that must be followed for any of these future Workorder possibilities.

A.17.1. CASES Enhancements Most items in this attachment are already operating in RRC’s existing Salesforce environment.

Attachment 1

The RRC Case Administration Service Electronic System (CASES) product is built around a Salesforce platform with additional components of Box for document storage and Conga Composer for template creation. CASES facilitates the following processes:

• Tracking violations through compliance activities until case closure.

• Historical record storage and searchability.

• Movement of internal RRC records through various stages of enforcement and hearings processes.

• Generation of correspondence and reports through templates and data merging from stored records.

The CASES product is used primarily by RRC internal staff but also has an externally facing portal accessible for public search and for authorized parties the ability to upload documents to a case.

The CASES product has integration points with RRC legacy systems to share/update information needed for RRC wide continuity of external account and business organization records, as well as payments.

In addition to the above, CASES also has considerable reporting capability of the stored information within the system for creation, storage, and sharing.

CASES was built with the premise of using low code / no code development techniques complemented by custom code where needed to achieve desired outcomes.

During development, and after production deployment, of CASES there were several product enhancements identified and backlogged for potential future functionality improvements. It is anticipated that these enhancements will individually, or in groups, be documented for handling as part of a vendor Workorder. RRC is interested in the dynamics of cost and schedule to deliver an enhancement(s) in an efficient manner.

CASES enhancements may have one or more of the following characteristics:

• Change to the existing product functionality.

• Extension to the existing product functionality.

• Creation of a new module of functionality within the product.

Attachment 1

• Architectural change or updates to the product.

• Change / creation of an integration to RRC legacy or new systems.

• Substantial product operational maintenance.

A.17.2. EVENTS Enhancements The RRC Enterprise-wide Event and Registration Management System (EVENTS) product is built around the Salesforce platform. EVENTS facilitates the following processes:

• Preparing for and performing registration.

• Fee calculation and payment submittal.

• Registration documentation and communications.

• Search capability.

• Reporting capability.

• Events administration.

The EVENTS product is used by RRC internal staff and has an externally facing portal accessible for public users to register for events.

The EVENTS product has an existing integration with the RRC internal electronic payment functionality.

EVENTS was built with the premise of using low code / no code development techniques complemented by custom code where needed to achieve desired outcomes.

During development, and after production deployment, of EVENTS there were several product enhancements identified and backlogged for potential future functionality improvements. It is anticipated that these enhancements will individually, or in groups, be documented for handling as part of a vendor Workorder. RRC is interested in the dynamics of cost and schedule to deliver an enhancement(s) in an efficient manner.

EVENTS product enhancements may have one or more of the following characteristics:

• Change to the existing product functionality.

• Extension to the existing product functionality.

• Creation of a new module of functionality within the product.

Attachment 1

• Architectural change or updates to the product.

• Change / creation of an integration to RRC legacy or new systems.

• Change to access and security for the product.

• Substantial product operational maintenance.

A.17.3. PIPES Enhancements The RRC Pipeline Inspection, Permitting, & Evaluation System (PIPES) product is built around a Salesforce platform with the additional components of Box for document storage and Conga Composer for template creation. PIPES facilitates the following processes:

• Generating Inspection Schedules for the Pipeline Safety department.

• Historical record storage and searchability.

• Collection of relevant information throughout the pipeline inspection process.

• Generation of correspondence and reports through templates and data merging from stored records.

The PIPES product is used primarily by RRC internal staff but also has an externally facing portal accessible for public search and for authorized parties to submit reporting information.

The PIPES product has integration points with RRC legacy systems to share/update information needed for RRC wide continuity of external account and business organization records as well as payments.

In addition to the above, PIPES also has considerable reporting capability of the stored information within the system for creation, storage, and sharing.

PIPES was built with the premise of using low code / no code development techniques complemented by custom code where needed to achieve desired outcomes.

During development, and after production deployment, of PIPES there were several product enhancements identified and backlogged for potential future functionality improvements. It is anticipated that these enhancements will individually, or in groups, Attachment 1 be documented for handling as part of a vendor Workorder. RRC is interested in the dynamics of cost and schedule to deliver an enhancement(s) in an efficient manner.

PIPES enhancements may have one or more of the following characteristics:

• Change to the existing product functionality.

• Extension to the existing product functionality.

• Creation of a new module of functionality within the product.

• Architectural change or updates to the product.

• Change / creation of an integration to RRC legacy or new systems.

• Substantial product operational maintenance.

A.17.4. Critical Infrastructure Inspection System (CIIS) Enhancements CID has regulatory authority for weatherization of electricity supply chain facilities.

Responsibilities of CID include:

• Tracking critical infrastructure and non-critical facilities in the electricity supply chain.

• Collaborating with other state agencies by securely sharing confidential and non-confidential data.

• Analyzing emergency operations plans developed by natural gas facility operators that produce, treat, process, pressurize, store, and transport natural gas that are included in the electricity supply chain.

• Inspecting gas supply chain and pipeline facilities for compliance with weather preparation standards.

• Tracking and comparing data submitted by operators and collected during inspections.

• Producing confidential and public reports using electricity supply chain and weatherization data.

The CIIS product is used primarily by RRC internal staff but also has an externally facing portal accessible for public search and for authorized parties to submit reporting information such as attestations for weatherization.

Attachment 1

The CIIS product has integration points with RRC legacy systems to share/update information needed for RRC wide continuity of external account and business organization records as well as payments.

In addition to the above, CIIS also has considerable reporting capability of the stored information within the system for creation, storage, and sharing.

CIIS was built with the premise of using low code / no code development techniques complemented by custom code where needed to achieve desired outcomes.

During development, and after production deployment, of CIIS there were several product enhancements identified and backlogged for potential future functionality improvements. It is anticipated that these enhancements will individually, or in groups, be documented for handling as part of a vendor Workorder. RRC is interested in the dynamics of cost and schedule to deliver an enhancement(s) in an efficient manner.

CIIS enhancements may have one or more of the following characteristics:

• Change to the existing product functionality.

• Extension to the existing product functionality.

• Creation of a new module of functionality within the product.

• Architectural change or updates to the product.

• Change / creation of an integration to RRC legacy or new systems.

• Substantial product operational maintenance.

A.17.5. RRC MAP Enhancements CID also has regulatory authority for weatherization of electricity supply chain facilities.

Responsibilities of CID include:

• Tracking critical infrastructure facilities in the electricity supply chain.

• Collaborating with other state agencies by securely sharing confidential and non-confidential data.

• Analyzing emergency operations plans developed by natural gas facility operators that produce, treat, process, pressurize, store, and transport natural gas that are included in the electricity supply chain.

Attachment 1

ClD is newly established and there is no historical data available.

The RRC MAP product is used primarily Operators to confirm their supply chain and name their suppliers. It is also used by RRC internal staff to review connections, assess disputes, and assist the Operator when needed.

The RRC MAP product has integration points with RRC legacy systems to share/update information needed for RRC wide continuity of external account and business organization records as well as payments.

In addition to the above, RRC MAP was designed to feed the CIIS system as well as the

GIS Map that provides the PUC with data for the Critical Supply Chain Map used in weather emergencies.

RRC MAP was built with the premise of using low code / no code development techniques complemented by custom code where needed to achieve desired outcomes.

During development, and after production deployment, of RRC MAP there were several product enhancements identified and backlogged for potential future functionality improvements. It is anticipated that these enhancements will individually, or in groups, be documented for handling as part of a vendor Workorder. RRC is interested in the dynamics of cost and schedule to deliver an enhancement(s) in an efficient manner.

• RRC MAP enhancements may have one or more of the following characteristics:

• Change to the existing product functionality.

• Extension to the existing product functionality.

• Creation of a new module of functionality within the product.

• Architectural change or updates to the product.

• Change / creation of an integration to RRC legacy or new systems.

• Substantial product operational maintenance.

A.17.6. MINERS Enhancements The Surface Mining and Reclamation Division (SMRD) regulates surface mining for coal or exploration. Mining companies must have a Commission permit and post a bond for each mining site they operate in the state. The SMRD division reviews proposed mining

Attachment 1 permit applications to see if the mine will impact the environment and to determine if the procedures proposed to be used in reclaiming the land after mining is finished meet regulatory requirements. Division field personnel make regular visits to mine sites, checking for compliance with Commission rules. The Commission also administers a federal program to reclaim abandoned mine sites that predate federal surface mining laws.

The RRC Mine Inspection & Enforcement Report System (MINERS) Prototype was built around a Salesforce platform with the additional component of Box for document storage or Neubus for records storage and management. The MINERS Prototype demonstrated some of the following processes:

• Scheduling regular or unique inspections.

• Reviewing inspection reports.

• Preparing and managing notifications pertaining to violations.

• Intake of complaints.

The MINERS Prototype was built with the premise of using low code / no code development techniques complemented by custom code where needed to achieve desired outcomes.

The MINERS Prototype is in queue for build-out as a full-featured product for SMRD.

MINERS build-out work will entail one or more of the following:

• Additional breadth and depth of requirements, design, and development to complete the product.

• Change to the existing prototype functionality.

• Extension to the existing prototype functionality.

• Creation of a new module of functionality within the prototype.

• Architectural change or updates to the prototype.

• Creation of an integration(s) to RRC legacy or new systems.

Attachment 1

The MINERS product is used primarily by RRC internal staff but also has an externally facing portal accessible for public search and for authorized parties to submit reporting information.

The MINERS product has integration points with RRC legacy systems to share/update information needed for RRC wide continuity of external account and business organization records as well as payments.

In addition to the above, MINERS also has considerable reporting capability of the stored information within the system for creation, storage, and sharing.

MINERS was built with the premise of using low code / no code development techniques complemented by custom code where needed to achieve desired outcomes.

During development, and after production deployment, of MINERS there were several…