Gate Review Under a Fixed-Price Deadline
Northgate Water is a regional utility serving 310,000 customers. Its 14-month, EUR 9.2 million programme will replace ageing telemetry and SCADA across 62 pumping stations. At the concept gate, four months in, the systems engineering lead reviews the evidence pack. Stakeholder needs were gathered in three workshops attended only by control-room operations staff. The concept of operations was written by the preferred vendor. No measures of effectiveness have been agreed. Architecture sketches already name the SCADA product and radio vendor. The regulator requires 99.5% telemetry availability and outage notification within 15 minutes, but this has not been decomposed. Maintenance crews and the regulator's cyber-security team were never consulted. A fixed-price tender must be issued in six weeks. The programme board wants to approve entry into preliminary design next week. The SE lead believes the gate evidence is incomplete but is under pressure to keep the schedule.
1. What should the SE lead recommend at the gate, and how should the recommendation be framed so the board can accept it?
Read the worked answer
Recommend a conditional gate: close concept definition before entering preliminary design, and re-gate before tender release. Frame it as protecting the fixed-price decision, not as delaying the programme.
The board is being asked to approve a design phase on the basis of a vendor-authored ConOps, an incomplete stakeholder set and no agreed measures of effectiveness. Those are concept-definition outputs. Entering preliminary design without them means the tender package, not the stakeholder need, will lock the architecture. A fixed-price tender issued on an unstable need baseline transfers ambiguity into supplier risk premiums and later change claims.
Evidence to table: a stakeholder coverage matrix showing operations, maintenance and the regulator's cyber team; a ConOps ownership statement; a draft MOE set covering availability and notification time; a traceability gap list from the regulator requirement to design elements; and a risk register entry estimating post-tender change cost. Propose a three-week closure sprint with named owners and a 60-minute re-gate. If the board still proceeds, record the decision as 'approve with actions', name the accountable owner, and log the assumptions the bid will rest on.
2. How should the 99.5% availability and 15-minute notification requirements be handled before the tender is issued?
Read the worked answer
Treat 99.5% as a stakeholder requirement that must be bounded before it becomes a design requirement. Define the measurand: availability of what (end-to-end telemetry from each station, or the central system?), over what period, with what exclusions, and measured how. Operational availability Ao = MTBF/(MTBF + MTTR) brings maintenance and spares into the requirement, so maintenance crews must be consulted.
Decompose the 15-minute notification into detection, transmission and presentation time budgets. Allocate the availability target to communications redundancy, local buffering at stations, monitoring and response procedures. Involve the cyber team because a cyber incident consumes availability. State a verification method for each derived requirement: analysis for the allocation, test for notification latency, and field trial or operational data for availability.
Do not name a radio vendor in the requirement; that is a design choice. The decomposition gives suppliers a measurable acceptance regime instead of one percentage they will each interpret differently.
3. The board decides to proceed regardless. What should the SE lead do to limit the damage without becoming obstructive?
Read the worked answer
Move from objection to controlled risk. Record the dissent and the basis for it in the gate decision record, including which stakeholder groups and MOEs are missing. Create an assumptions register that states what the tender assumes about availability, stakeholder needs and architecture, with owners and expiry dates. Add a priced contingency or a qualified tender instruction so bidders price the open items explicitly rather than hiding them.
Negotiate a post-tender baseline review before contract award, and hold requirements change control from that point. Brief the regulator's cyber team now, even if informally, so a late security requirement does not arrive as a surprise. Plan the first preliminary-design iteration to close the concept gaps, and report their status at every progress review. The aim is to keep the SE lead's technical position visible and auditable, so that if the risk materialises the organisation can trace the decision and respond.