BishopCX
Begin with
the operation.
Start with the equipment, connections and conditions that a procedure depends on. BishopCX models that part of the site so the team has somewhere to rehearse.
A model of the operation comes first.
The Bishop platform
From rehearsal
to physical operation.
I build Bishop: the runtime, the simulation and the interfaces that connect a procedure to the equipment it controls.
Runtime engineering · Simulation · Product & interface design
sulaco.ioBishopCX
Start with the equipment, connections and conditions that a procedure depends on. BishopCX models that part of the site so the team has somewhere to rehearse.
A model of the operation comes first.
Studio
Studio is where procedures, automations and productions are authored. It describes the intended actions and conditions, ready to be checked and rehearsed.
Studio authors. BishopRT executes.
BishopCX + BishopRT
Run the procedure against the model, including degraded and failure conditions. BishopRT is the execution layer used for rehearsal and for the accepted operation on site.
The rehearsal and the site share a runtime.
BishopOS + BishopRT
Once the agreed checks and approvals are met, the procedure can move to site operation. BishopOS gives people the controls and visibility. BishopRT executes to the equipment.
People authorise. The runtime acts.
BishopOS + BishopIQ
Operators follow the site and its record through BishopOS. Optional BishopIQ adds prediction, anomaly detection and questions about the operation, with read-only access.
Insight informs the work. It has no execution authority.
What I build
The work spans systems engineering and product design: connecting equipment, modelling its behaviour, writing the authoring tools and shaping what an operator sees.
The deterministic runtime. Device integration, authoritative operational state and execution of accepted procedures all meet here.
The commissioning environment. Facility models, simulated equipment and rehearsal workflows give a team a way to examine a change before accepting it for the site.
The visual authoring surface shared by BishopOS and BishopCX. Procedures, automations and productions are defined here for BishopRT to execute.
The browser interface. The command centre, topology, maintenance and operational views bring the runtime’s state into a workspace people can use.
Around the execution layer
Bishop also spans the software and hardware around that workflow, from an operator’s questions to the equipment in the field.
Insight
Optional prediction and anomaly detection. It reads the operation and helps people understand it.
Site hardware
The site box: a home for the runtime, the operational model and record, and the interface served to operator browsers.
Field hardware
Controlled field hardware that connects the platform to sensing and actuation at the equipment.
Systems engineering / Built at Sulaco
My work on Bishop went through the application, into the runtime and down to the host. This is engineering I built at Sulaco, a separate company I founded.
More of the work