Engagement
The path from a difficult unit to a document you can keep.
This is the ordinary sequence. A proposal will name which stages apply. Nothing is implemented on the live plant until you have accepted the scope in writing.
01
Initial contact
You write or call through the contact form with the unit, the symptom, and who owns the decision. We reply to confirm whether the problem sits in process control and whether we are the right practice. If it is a safety-system design or a full DCS replacement, we say so and stop.
02
Discovery
A short call covers battery limits, historian access, and what “better” would mean in operating language. If a discovery note is useful, we agree its boundary and a fixed fee in writing before work starts.
03
Preparation
You send the agreed extracts: trends, loop sheets, alarm lists, or a control narrative if one exists. We list gaps instead of guessing. Site rules, permits, and the name of the person who may change a live loop are confirmed before any test.
04
Workflow
The work follows Baseline to Setpoint. We observe, measure, and propose the smallest change. Live changes happen only with your authorization and your implementer. We do not take exclusive control of a console.
05
Delivery
You receive the document named in the proposal: a brief, tuning sheets, an alarm list, a narrative, or commissioning notes. Figures are explained in words. Open items are listed with an owner on your side.
06
Communication
One named contact on each side. Updates are written. During a site window we work to the shift pattern you set. We do not add stakeholders or copy plant data to people outside the agreed list.
07
Next steps
At the end we state what should be watched, for how long, and whether a further scope is justified. A retainer is optional. Many engagements end with the document. You can write again when the next unit needs the same attention.