A concrete example

One brief, built from three years of proposals

Here’s what a Living Brief shows a systems integrator picking up a project that looks like ones they’ve already done. The firm, the project, and every document named below are invented for this example.

14Source documents

2Comparable projects

1Open question

The firm

Fenwick Automation Group

Fenwick designs, builds, and commissions industrial control and SCADA systems for water utilities, food and beverage plants, and mid-size manufacturers across the Pacific Northwest. Like most firms this size, they have thirteen years of proposals, spec sheets, vendor correspondence, and decisions on file, and no one whose job it is to keep track of all of it.

Headcount
42
Offices
Portland, OR · Boise, ID
Work
Controls and SCADA integration, panel builds, commissioning, ongoing support
Archive
13 years of proposals and decisions, no dedicated knowledge role

The moment

A proposal deadline, and a familiar-looking job

Cedar Valley Water District has put a lift-station SCADA upgrade out to bid. Marcus Ondera, a senior controls engineer, is writing the technical proposal. He opens the project in Piko and asks the obvious question.

“We’re bidding on a lift-station SCADA upgrade for Cedar Valley Water District. What have we already learned from a job like this?”

What comes back isn’t a list of files with the word “lift station” in them. It’s a brief.

Inside the brief

Cedar Valley Water District — Lift Station SCADA Upgrade

Six parts, each answering a different question, each leading back to a real document.

Cedar Valley Water District — Lift Station SCADA Upgrade

Assembled from Fenwick’s project archive · RFP response due 15 October

Current understanding

SCADA and telemetry upgrade for four remote lift stations. RFP posted 3 September, response due 15 October. No prior Fenwick relationship with this client on file.

Cedar Valley Water District — RFP 2026-14.pdf

Relevant history

Willamette Regional Water Authority — Lift Station Telemetry Retrofit (2023). Four lift stations, similar rural connectivity constraints. Fenwick’s largest comparable project by station count.

Grange County Water District — SCADA Modernization, Phase 2 (2022). Different RTU vendor; its alarm escalation design carries forward below.

Willamette Regional Water Authority — Final Proposal, Rev C.pdf · Grange County — Closeout Report.pdf

Decisions and rationale

Standardize on licensed 900 MHz radio telemetry over cellular modems for rural lift stations. Approved 2 September 2023, after cellular dropouts caused two missed alarms during Willamette commissioning. Applies to sites without reliable carrier coverage.

Use a tiered alarm escalation ladder — operator, then on-call lead, then district supervisor — instead of a flat broadcast list. Approved 2022 on Grange County; cut after-hours callouts by roughly a third.

Decision D-114 · Site Survey, Willamette Station 3.pdf, p. 4 · Grange County — Closeout Report.pdf, §5

Reusable work

Reusable. The 900 MHz radio architecture and the tiered alarm ladder both transfer directly. Willamette’s panel labeling and terminal numbering standard is a usable starting template.

Needs checking. Willamette’s proposal assumed the same rural connectivity profile Cedar Valley may or may not have — no site survey yet. The radio model specified at Willamette has since been discontinued.

Willamette Regional Water Authority — Final Proposal, Rev C.pdf

Open questions and changes

Recent change. Redline Telemetry issued an end-of-life notice for the RT‑900X radio on 28 August, three weeks before this RFP was posted. It’s the radio in the reusable Willamette architecture above. Two prior decisions reference it.

Cedar Valley’s RFP doesn’t specify a cybersecurity framework. Grange County required a self-attestation against AWWA guidance; Willamette required none. Worth confirming before the proposal goes out.

Redline Telemetry — Product End-of-Life Notice, RT-900X.pdf

Evidence and coverage

Built from 14 documents across 2 prior projects: proposals, decision records, a closeout report, and vendor correspondence. Cedar Valley’s own site hasn’t been surveyed yet, so the connectivity assumption above is flagged, not confirmed.

Why a brief, not just an answer

You can open this without knowing what to ask.

A chat box still needs someone to know what to type. Marcus didn’t know the radio vendor had discontinued the RT-900X until the brief told him. He didn’t ask about a cybersecurity framework; the open question surfaced anyway, because Grange County had one and this RFP is silent on it.

That’s the point of a brief over an answer. It shows what you didn’t know to look for, and it says plainly what it isn’t sure about — a site survey that hasn’t happened, an assumption carried from a different client. Inventing a confident answer instead would be worse than showing the gap.

See how this fits with what Piko already does

The Living Brief sits on top of evidence-checked claims, session-bound approval, and decisions that carry their dependencies. Every line in it leads back to a document.