Selected Work in Operational Systems Engineering.

MAGIC publishes project evidence in three clearly labelled categories: Named Case Study (published with the customer’s approval), Anonymised Delivery Pattern (a real delivery described without identifying details), and Capability Pattern (how MAGIC delivers a class of system). At launch this library lists delivery and capability patterns; named case studies will be added as approvals are confirmed.

Capability Pattern

Adaptive junction control with safe fallback

Context
Signalised intersections where fixed-time plans no longer match real demand, and where the junction must keep operating safely under degraded sensor or network conditions.
MAGIC’s scope
Design and integration of controller logic, vehicle detection, communication and monitoring; configuration of adaptive vehicle-actuated control; definition and testing of fallback behaviour; field commissioning coordination and documented handover.
System components
  • Traffic controller and cabinet logic
  • Vehicle detection inputs
  • Real-time communication link
  • Adaptive control strategy
  • Monitoring and fault reporting
Result / learning
The delivery pattern proves the full chain from detection to adaptive timing — with the junction dropping to a known safe plan, visibly, when inputs degrade.

Smart Traffic & Mobility solutions

Capability Pattern

Corridor synchronisation delivery pattern

Context
A sequence of junctions along a corridor that had been timed individually, producing stop-start progression even under normal demand.
MAGIC’s scope
Coordination design across junctions, synchronised adaptive vehicle-actuated configuration, communication between junction controllers and the monitoring side, staged commissioning under live traffic.
System components
  • Multiple coordinated junction controllers
  • Inter-junction communication
  • Synchronised adaptive control strategy
  • Central monitoring and reporting
Result / learning
Demonstrates MAGIC’s ability to treat a corridor as one system: balancing local junction demand against progression along the route, with commissioning staged so traffic keeps moving.

Smart Traffic & Mobility solutions

Anonymised Delivery Pattern

Industrial monitoring delivery pattern

Context
An industrial operation needing visibility of production equipment state, with alerts reaching the responsible people rather than a screen nobody watches. Details are anonymised; the operating sector and scope are stated accurately.
MAGIC’s scope
Sensor and signal integration on existing equipment, data collection and structuring, remote alarm and reporting configuration, integration with the operator’s existing systems.
System components
  • Field sensors and signal acquisition
  • Edge data collection
  • Alerting and reporting layer
  • Integration with existing operational software
Result / learning
Reflects MAGIC’s longest-running discipline — industrial monitoring — and the practical rule learned from it: data is only operational when the right person sees it in time to act.

Operational Intelligence & IIoT solutions

Capability Pattern

Secure office architecture delivery pattern

Context
An organisation whose network, identity, telephony, storage and security systems had grown over years without a single owner or current documentation.
MAGIC’s scope
Architecture review and redesign, firewall and VPN configuration, hybrid cloud and identity setup, NAS and backup with tested restore, IP-PBX and CCTV integration, and a documented handover of ownership and support paths. Customer security topology is never published.
System components
  • Segmented enterprise network
  • Firewall / VPN
  • Hybrid cloud and identity
  • NAS and tested backup
  • IP-PBX and physical security integration
  • Handover documentation
Result / learning
Demonstrates the delivery discipline MAGIC treats as part of the product: the system works, and the customer knows what was built, who owns it and how it is supported.

Secure IT & System Integration solutions

Capability Pattern

Fleet data integration delivery pattern

Context
Fleet operations generating GPS and MDVR data that stayed locked inside vendor portals instead of supporting safety, compliance and operational decisions.
MAGIC’s scope
Analysis of GPS/MDVR data flow, design of operational data handling, reporting aligned to safety and compliance needs, API integration with the operator’s existing systems.
System components
  • GPS / MDVR data sources
  • Operational data store
  • Safety and compliance reporting
  • APIs into existing systems
Result / learning
Shows the boundary MAGIC keeps honest: not a telematics product, but the integration and software capability that makes fleet data usable where the operator already works.

Fleet & Logistics Systems solutions

Start with the Operational Challenge.

Tell us what must be connected, controlled or made visible. We will help define the practical next step.

Discuss Your Project