WHERE IT RUNS
One engine. Many kinds of facility.
Bishop is horizontal. If a facility has sensors, actuators, and people coordinating physical work, it is in scope. Two worlds run live today; the rest are modelled at full scale on the same engine.
2
Live worlds
5
Verticals
250k+
Devices / site
1
Engine
Immersive destinations.
The specialty controls run the effects. A separate system runs access and ticketing. Another runs food and beverage. Lighting, AV, crowd flow, and maintenance each sit in their own console, each capable, none aware of the others. Coordinating the experience and the operation has always fallen to people on radios.
What Bishop unifies here
Ride and specialty controls
Effects, motion, and safety PLCs
AV and lighting
Playback, cues, and specialty controls
Access and ticketing
Entry, capacity, and reservations
Food and beverage
Points of sale and kitchen throughput
Crowd flow
Queues, dwell, and movement across the site
Maintenance
Condition, work orders, and asset history
Cruise ships.
A floating city run by a limited crew. Engineering, staterooms, safety and muster, and entertainment all sit on different vendors and different protocols, most of them never designed to speak to each other. At sea there is no cloud to lean on, and no room for a system that only reports after the fact.
What Bishop unifies here
Engineering and plant
Propulsion, power, and machinery spaces
Staterooms
Access, climate, and in-cabin systems
Safety and muster
Life safety, drills, and headcount
AV and entertainment
Venues, shows, and specialty controls
Bridge to engine room
One state across the whole vessel
Offline at sea
Full operation with no cloud dependency
Resorts.
Hundreds of buildings, thousands of rooms, energy and grounds and guest systems, each on its own management platform. A full-scale resort is modelled at 250,000 or more devices on the same engine that runs the live worlds, so the coordination layer is proven before a single controller is fitted.
What Bishop unifies here
Buildings
Access, HVAC, and plant across the property
Energy
Metering, load, and balance of site
Access
Rooms, back of house, and perimeter
Guest systems
Ticketing, reservations, and in-room
Grounds
Irrigation, lighting, and outdoor assets
One model
Every system in a single authoritative state
Distribution centres and 3PL.
Conveyors and automation run on the controls layer. The warehouse control system and warehouse management system each hold a slice of the picture. Energy, labour, and throughput are tracked in separate tools. The coordination layer above all of it is still spreadsheets and shift leads.
What Bishop unifies here
Conveyors and automation
Sortation, robotics, and material handling
WCS and WMS
The controls and management systems, coordinated above
Energy
Load, metering, and site balance
Labour
Tasks, presence, and the workforce in hand
Throughput
Flow, bottlenecks, and site rate, live
One live model
The whole site in a single state
Power and energy.
Plant, protection, and balance of site run on control and historian systems that were installed to do exactly that and nothing more. Where determinism and a replayable record matter most, the layer that unifies them, and stands up to a regulator, has not existed as software.
What Bishop unifies here
Plant
Generation, protection, and primary equipment
Balance of site
Auxiliaries, metering, and controls
Control systems
Unified above the installed control layer
Historian
One record alongside the existing historian
Determinism
The same inputs produce the same actions
Replayable record
Evidence where it matters most
If it runs on more systems than any one person can hold, it is in scope.
The list above is where Bishop runs today, not where it stops. The engine does not know a cruise ship from a distribution centre; it knows sensors, actuators, state, and procedures. If your facility has those, we can model it. We build a working slice on the real engine, you watch it run, then you decide.
The fastest way to judge the engine is to watch it run your facility.
Share your drawings, schematics, and equipment lists. We walk the site with you, build a working slice on the real engine, and you watch it run. Then you decide.
Model your facility