SERVICES / CONTROL SYSTEM DISCOVERY

Ground Truth.
Know what your control system actually does.

Before anyone changes it.

In the sample: four severity A hazards. Releasing the E-stop restores the pump permissive without a reset. See the findings ↓

Site photos and a program backup become as-found drawings, a control narrative, a cause and effect matrix, a live model of the real logic, a ranked findings register and training for every role.

Real process and logic. Engineering by David Landry on an industrial project; model engine, verification and tools by Landry Industrial. Client details changed. Preliminary engineering review draft — not for construction.

RUNG 2:20 · PUMP A PERMISSIVE · AS FOUND0 COMMENTS IN THE PROGRAM
DECODED FROM THE BACKUPTAGS FROM THE RECONCILED I/O LIST
LAL-V110-AXIC B9:0/5LAL-V110-BXIC B9:0/9PUMP A CMDXIC B9:0/15XS-P111AXIC B9:0/12HS-V110CXIC B9:0/2PUMP TRIPXIO B3:0/5PUMP A CMDOTE B9:0/15

E-stop released · low level made · no reset pressed

A
The permissive comes back on its own.Releasing the E-stop restores the pump permissive without a reset. Starter wiring is an open question. Finding PLC-D02.
✓ DECODED AND VERIFIED AGAINST THE PROGRAMSee the findings ↓

THE PUBLIC SAMPLE
One real control system.

11photos

Site photos in

55rungs

One program backup. Zero comments.

14findings

Latent logic findings, 4 severity A

0mismatches

In 4,012,164 bit checks against the program

35/35

Functional test cases pass

5videos

Training for every role

WHAT THE SAMPLE FOUND

Four findings that
change the decision.

The sample program holds 14 latent findings: 4 severity A, 6 B and 4 C. Here are the four severity A findings, each with its recommended correction.

APLC-D01

A broken wire gives no trip.

What happens
The low-low, high-high and external trip inputs (LALL-A/B, LAHH-A/B, LY-X130) are energize-to-trip: the PLC trips only when a contact closes. Only the high-level pair is read fail-safe. A broken wire, a blown fuse or a lost supply looks exactly like a healthy process.
Recommended correction
Make the trips de-energize-to-trip with wire-break detection, and confirm the level-switch relay failure mode on site.

Rungs 2:3, 2:5, 2:11, 2:22

APLC-D02

Releasing the E-stop restores the pump permissive.

What happens
The emergency stop acts only through the general-purpose PLC and is not latched for the pumps. When the button is released, the pump permissive returns without a reset. Whether a pump then restarts depends on the starter wiring, an open question for the field walk.
Recommended correction
Hard-wire a two-channel E-stop through a safety relay, latch the pump trip so a restart needs a deliberate reset, and alarm on circuit discrepancy.

Rungs 2:5, 2:20–21 · test cases TC-18 to TC-20

APLC-D03

The alarms are silent in the field.

What happens
The logic drives the horn and the common alarm, but their fuse carriers are open in the panel. The “truck empty” horn and every high-high, stop and external-trip alarm make no sound.
Recommended correction
Restore the horn and common alarm under MOC, after reviewing horn behavior: silence, re-sound and reset.

Panel observation O-14 · rungs 3:2, 3:3

APLC-D04

High-high level does not stop the pumps.

What happens
On high-high level the logic drops the unit trip output and alarms. The transfer pumps keep their permissive. Overfill protection depends entirely on what that one output does downstream.
Recommended correction
Stop both pumps on high-high level. If overfill protection is credited in the PHA, it belongs in a suitable independent layer, not this general-purpose path.

Rungs 2:5, 2:22 · observation O-08

ALSO FOUND · SEVERITY B AND C

  • High-level trip voted two-out-of-two, but reset one-out-of-two
  • Level-sensitive reset: a held button defeats the latch
  • Purge not interlocked with a running pump
  • One reset re-enables both pumps at once
  • No pump supervision: fail-to-start, fail-to-stop or welded contact
  • Power return re-permits the pumps without a reset

WHO IT’S FOR

One system.
Three ways to read it.

Owners, managers and engineers need different answers from the same evidence. Choose your role to see what you get.

FOR THE OWNER

See the risk before you commit capital.

For owners and plant managers who have to decide what to fix, what to fund and what to take through MOC.

WHAT YOU GET

  • Latent trip and restart hazards, explained in plain language.
  • A decision-ready findings list, ranked A, B and C, each with a recommended correction.
  • Ready for management of change (MOC) and hazard-study (PHA) revalidation: the cause and effect that actually runs, not the one on paper.
  • A firm basis before anyone changes the panel, from a defined first step.
  • System knowledge that no longer lives in one retiring person’s head.
Start with one system that worries you.Discuss a system →

The guide below follows your choice. Operators and technicians: find your training videos below.

INTERACTIVE GUIDE

From evidence
to understanding.

Ten stages on one real system. See what we do, what you receive and why it matters to you. Select a screenshot to enlarge it.

STEP 01 OF 10

Evidence in

Use ← → to move between steps.

How we worked: stages and evidence register (page 4 of 20). The twelve stages and the evidence register: site photos, the program backup with its hash and one line from the plant PLC register.

STEP 01 / EVIDENCE IN

Start with what the plant already has.

Site photos, the program backup and any existing documents go into an evidence register. The backup is hashed, so every later statement points to the exact file. The confidentiality boundary is agreed first.

Sample: 11 site photos, one program backup and one line from the plant’s PLC register.

WHAT YOU RECEIVE

  • Evidence register with the backup hashXLSX

WHY IT MATTERS · OWNERS

It starts from evidence you already hold: a camera roll and a program backup.

THE MODEL, DEMONSTRATED

See the logic
in action.

Watch the recorded walkthroughs to see how the model exposes trips, resets and open questions. Arrange a guided demonstration to explore the model with us.

GROUND TRUTH / MODEL WALKTHROUGHRECORDED SAMPLE

HOW WE KNOW IT’S THE REAL LOGIC

  • 4,012,164one-scan bit checks against an independent ladder interpreter · 0 mismatches
  • 540,000word checks, interactive model against the simulator · 0 mismatches
  • 35/35as-found functional test cases pass · 100 % branch-leg coverage
  • 43/43test cases for the proposed corrections pass
  • 160,000scan equivalence check at build · the sample model’s self-check runs 40,000

This proves our documents match the program. It does not prove what the field devices do — those are the open questions for the field walk.

The customer model includes 13 narrated scenario walk-throughs, a live cause and effect view and “open question” toggles. Interactive models and native files are provided through scoped customer engagements.

TRAINING FOR EVERY ROLE

The same system.
Explained five ways.

Short narrated videos made on the sample model, captioned and ready for a learning management system. Choose the one that matches your role. Swipe for all five →

For management · 1:27

What we found and what it means

What the unloading system does, how little documentation existed, the four severity-A findings (one shown live on the model), and what the package gives you before anyone changes the panel.

For owners, plant managers and engineering managers.

For operators · 1:32

Unloading a truck, step by step

The normal as-found sequence on the CP-101 door buttons and lamps, from hook-up to purge, with the silent horn, the extra reset and the proposed high-high response.

For operators and drivers.

For technicians · 1:27

Where the signals live and how to troubleshoot

CP-101 I/O, relays and open fuse carriers, the SSR for LY-X130, the I/O and forces view, an open wire on an energize-to-trip input that gives no trip, and the event log.

For instrument and electrical technicians.

For engineers · 1:36

Inside the logic

The extracted ladder executing with live power flow, the live cause and effect, two findings on their rungs, the proposed corrections and the verification shown on the page.

For controls and process safety engineers.

Using the package · 1:30

How to use your Ground Truth package

A guided tour of the offline model (modes, inspector, tabs, walk-throughs, open questions, faults, verification) and where every other deliverable lives.

For anyone who opens the package.

MADE FOR YOUR SYSTEM

Your model. Your people. Their level.

In a Full Ground Truth engagement the videos are recorded on the model of your own system, one for each role that needs it. MP4 with WebVTT captions, ready for your learning management system.

See the engagement options ↓

WHAT YOU RECEIVE

A complete package.
In formats you already use.

Explore sample previews below. The complete package, including the interactive model and native files, is delivered as part of your engagement.

All 12 deliverables and their formats
  • Discovery report

    The whole story in one document: what the system does, what we found and what to do next.

    PDF
  • As-found record

    4 drawing sheets, the as-found workbook and a panel model.

    DXFPDFXLSXHTML
  • Program listing & address database

    Every rung and address, decoded from the backup.

    PDFCSV
  • I/O list

    Signals reconciled against wire markers and door legends, with confidence tags.

    XLSX
  • Preliminary PFD & process understanding

    Working basis, hypotheses and open questions.

    PDF
  • Control narrative

    Sequences, interlocks, alarms and power-up behavior, rung-cited.

    PDF
  • Cause & effect matrix

    Every cause and effect, traced to the logic.

    XLSXPDF
  • Logic analysis & findings register

    Findings ranked A, B and C with recommended corrections.

    PDFXLSX
  • Functional test cases

    35 cases with full branch-leg coverage, ready for FAT.

    PDF
  • Interactive model

    The real logic running offline, with 13 narrated walk-throughs.

    HTML
  • Role training videos

    Management, operator, technician, engineer and system user.

    MP4VTT
  • Holds register & field-walk checklist

    Numbered open items, each with its owner and closing evidence.

    XLSXPDF

SAMPLE PREVIEWS

Select a preview to inspect it at full size. Sample · client details changed · preliminary engineering review draft — not for construction.

Engineering: David Landry. Model engine, verification harness and document tools: Landry Industrial.

Ground Truth · David Landry · Landry Industrial

Optional follow-ons: a redesign basis (platform selection, panel drawings, bill of materials and a standards compliance review), program conversion and FAT procedures.

SAMPLE DRAWINGS & MODEL PREVIEWS

Select an image to inspect a sample drawing or panel model preview. Swipe for more →

FITS INTO YOUR SYSTEMS

Built to land
where your team works.

The package arrives on your standards and flows into the systems you already run: document control, change management, hazard studies, maintenance and training.

8 ways it fits: standards, EDMS, MOC, PHA, CMMS, LMS, offline, data
STANDARDS

Your numbering and title blocks

Drawings and documents issued on your numbering, title blocks and CAD standards.

DOCUMENT CONTROL

Into your EDMS

Delivered into SharePoint or your document control system, with an index and revision status.

CHANGE

Findings become MOC items

Each finding has a severity, the evidence and a recommended correction; most are tied to a functional test case, the rest to a FAT check or a field hold.

SAFETY STUDIES

Feeds PHA and LOPA

The as-found C&E and findings support hazard study revalidation with the behavior that actually runs.

MAINTENANCE

Device list to your CMMS

The as-found device list feeds spares, lifecycle and obsolescence planning.

TRAINING

Videos to your LMS

MP4 with captions, ready to load into your learning management system.

ACCESS

A model that runs offline

One HTML file in any browser. No install, no vendor license, no network calls.

DATA HANDLING

Your data stays controlled

NDA first. Work can stay on your machines. Nothing is published without your written approval.

PLATFORMS

  • RSLogix 500 · MicroLogix · SLC 500PROVENProven on this sample.
  • Studio 5000 · L5XNEXTNext adapter, building on LogicLens →
  • DeltaV · FHXNEXTNext adapter, building on FHX Studio →
  • Other platformsON REQUESTDiscuss your platform and export format.

HOW AN ENGAGEMENT WORKS

A defined first step.
A clear path forward.

Every engagement is scoped and priced in a written proposal before work begins. Deliverables, data handling, access and ownership are agreed there too.

01 / ONE SYSTEM

Discovery Snapshot

One system. The essential understanding.

  • Discovery report
  • Control narrative
  • Cause & effect matrix
  • Findings register
02 / ONE SYSTEM, COMPLETE

Full Ground Truth

The Snapshot, plus everything your team needs to use it.

  • As-found drawings
  • Interactive model
  • Role training videos
  • Holds register & field checklist
03 / MANY SYSTEMS

Fleet

Many systems, one method and one register.

  • A consistent package for each system
  • A cross-site findings view
  • Links to the PLC/HMI fleet-management system we are developing
  1. 01

    Walk & collect

    NDA first. We gather photos, the program backup and whatever documents exist, and agree the confidentiality boundary.

  2. 02

    Decode

    Program, as-found record and signals, each with its source and confidence.

  3. 03

    Model

    Narrative, C&E, findings and the live model of the actual logic.

  4. 04

    Review with your team

    Walk the findings on the model with operations and engineering, and resolve the holds.

  5. 05

    Hand over

    The package on your numbering, into your document control, with training videos for your LMS.

Start with one system and the evidence you already have.Scope a discovery

BEFORE YOU CHANGE IT

Which system do you
need to understand?

Bring the photos and the backup you already have.
We’ll show you what they can tell you.

Discuss a system