Houston Software Development Company: A Mock Inspection for Pipeline and Offshore Records

Updated November 2026 · Written and maintained by the Progression Agency strategy team

An inspector asks for last year’s monthly alarm reviews and the handover log from a night shift fourteen months ago. If those records live in six spreadsheets and a retired engineer’s inbox, the problem is software. A Houston software development company serving pipeline and offshore operators should build for the day that request arrives. This page runs a mock inspection, request by request, and shows what each one needs from the system. It is for operations, integrity and compliance leads. Progression is headquartered in New York and handles Houston projects remotely, with on-site sessions on request. Counsel signs off anything that touches compliance.

The request arrives on a Tuesday

Picture a request list, invented for this page, that lands on a Tuesday morning. It has five lines. Nothing on it is unusual, and each line sends someone digging.

An invented example. The five cards are the five requests this page walks through. For each, the question is the same: can one system produce the answer in minutes, with the date it was recorded?

Who is this page for?

Operations, integrity and compliance leads at pipeline operators and offshore operators in the Houston area, and the vendors and in-house teams who build their records tools.

What a Houston software development company should ask first

The first question is which regime applies. Pipeline operators with controllers working in a control room are covered by 49 CFR 192.631 for gas and 49 CFR 195.446 for hazardous liquid. Offshore operators on the Outer Continental Shelf answer to 30 CFR 250.1900, which says you must develop, implement and maintain a safety and environmental management system, or SEMS, program. Some operators answer to both.

The Greater Houston Partnership calls Houston the energy capital of the world, which is why a software development company in Houston is likely to be asked about these records before almost anything else. For the marketing side of the same industry, see our oil and gas marketing agency page. The second question is which systems hold the records today.

Request 1: monthly points off scan and inhibited alarms

The gas rule says an operator using a SCADA system must have a written alarm management plan. Under 192.631(e)(2) the plan must provide to identify, at least once each calendar month, points affecting safety that have been taken off scan in the SCADA host, had alarms inhibited, generated false alarms, or had forced or manual values for longer than the maintenance or operating activity required.

A report by month, point, condition, reason and who cleared it answers the request. The hard part is getting the data out of the SCADA host and the maintenance system into one place. Start with a read-only connection, agree the field names with the controllers who use them, and store each month’s report as it was run, so a later change in the source cannot rewrite last year.

Request 2: shift handovers

Paragraph (b)(4) of the gas rule calls for a method of recording controller shift changes and any handover of responsibility between controllers. Paragraph (c)(5) adds procedures for when a different controller assumes responsibility, including the content of the information exchanged.

The record that answers a request fourteen months later is time-stamped, attributed and hard to edit quietly. Where a historian or logbook product already does this, keep it and add a way to search it; see our guide to custom software versus off-the-shelf.

Request 3: fatigue rosters

Paragraph (d)(1) says an operator must establish shift lengths and schedule rotations that provide controllers off-duty time sufficient to achieve eight hours of continuous sleep. A system cannot fix a fatigue problem. It can show the roster against that test.

• Import the roster from the scheduling system on a schedule.
• Compute off-duty time between shifts for each controller.
• Flag any rotation where the gap is shorter than the test allows.
• Keep medical information out of the system; hold only schedules.
• Store each monthly roster as it was published.

Request 4: alarm set points and the 15 month clock

Paragraph (e)(3) requires verifying the correct safety-related alarm set-point values and alarm descriptions at least once each calendar year, at intervals not to exceed 15 months. Paragraph (e)(4) sets the same interval for reviewing the alarm management plan itself, and (e)(5) for monitoring the activity directed to each controller.

Paragraph (j) says an operator must maintain for review during inspection records that demonstrate compliance with the section, and documentation that any deviation from the procedures was necessary for the safe operation of the pipeline. Whether your records meet that is a question for counsel.

Request 5: offshore records with different clocks

30 CFR 250.1928 gives offshore records several clocks. SEMS records are kept 6 years, audits are kept 6 years and available to BSEE on request, and a copy of all SEMS program documents is kept at an onshore location. Other records have shorter retention.

What is the 30 day onsite copy and the 2 year archive?

For job safety analysis records and stop work authority records, the rule keeps a copy onsite for 30 days and retains it for 2 years. A retention engine holds both dates for each record and moves it from the onsite store to the archive.

How are audits kept for six years?

Audits and the SEMS record set are kept 6 years. The system should block deletion until the date passes and log the attempt.

Paragraph (h) says records must be kept in an orderly manner, readily identifiable, retrievable and legible, and must include the date of any revisions. That sentence is the design brief for the retention engine.

Which rule sits behind each request?

The table below pairs each request with the paragraph that calls for the record and the field the system must hold. It is a design aid and not a compliance finding for any operator.

• Name one owner for each request.
• Time how long each answer takes today.
• Write the target time in minutes, not days.
• Re-run the drill every quarter.
• Keep the drill results with the other records.
• Show the target to the person who answers the phone when the inspector calls.

What a software company in Houston costs after five requests

A records platform sits in the published portal or platform band, and integration with a SCADA historian and maintenance systems sits in the internal tool band. No Houston-only figure is published here.

What do published bands say about records systems?

The table runs from the typical low to the published high. Hosting, licenses and security testing are on top.

What does it cost inside the plant fence?

Site access, historian licensing and a cyber review are scoped in writing. Progression quotes after a written scope, and those items are listed as their own lines.

Custom software development in Houston, or the product you already own

Most operators own a historian, a maintenance system and a logbook. Houston custom software development rarely replaces them. It adds a thin layer that answers the five requests by reading from what you own. Custom software development Houston TX operators ask about is mostly that layer. For connections into enterprise systems see our ERP development page, and for deciding what to keep, our software consulting services.

Software development in Houston, inside a change process

Software development Houston TX operators commission for a compliance record sits inside a change process. A change to a system that holds the records goes through management of change; offshore, management of change records are dated and retained for 2 years under 250.1928(c).

• Test every change in a copy of the system first.
• Write the rollback before the change, not after.
• Date each change and name who approved it.
• Keep the change record with the other compliance records.
• Tell the control room before anything that touches their displays.
• Record who approved the change and on what date.
• Keep the old version available for comparison.
• Confirm the records still open after the change.
• Close the change only after the next monthly review runs clean.
• File the change record with the compliance records.
• Review the change log at the annual plan review.

A records clause for Houston software development companies

Software development companies in Houston, TX will each propose their own terms, so put one clause in every contract: the buyer owns exports of every record in the five requests, in a stated format. Ask counsel to review it.

Houston software development companies, software development companies in Houston and software companies in Houston all differ in how they handle data ownership, so ask the question early. A software development company Houston operators trust will agree to the clause before the work starts. If you are weighing hiring against buying, a software developer in Houston on staff is one path; the salary table on our app development company in Houston page shows what that costs. For web work see web design in Houston.

Related services and guides

Pages that sit beside this one:

• Software development company
• ERP development
• Custom software vs off the shelf
• Software consulting services
• App development company in Houston
• Oil and gas marketing agency

Frequently asked questions