BoRoBORO
Operational architecture studio

Operational architecture for complex project delivery

BoRo designs how complex project-delivery companies should operate, then implements the systems required to make that model work.

Current focusSolar + BESS project deliveryFor growth-stage EPC and developer-EPC organizations where engineering, procurement, construction and commissioning have become harder to coordinate as project volume grows.
Discuss an operational constraintSee how the Architecture Sprint works
Diagram: a design change approved in engineering should propagate to procurement, project controls, construction and commissioning. Only the first handoff is defined; the rest depend on a person carrying the context, which is where delay and divergence appear.
How a decision propagatesDesign change approved
  1. EngineeringChange issued
  2. ProcurementOrder not yet revised
    Human middlewareSomeone remembers to tell procurement. Usually.
  3. Project controlsForecast still on old scope
  4. ConstructionBuilding to superseded drawing
  5. CommissioningTest plan unaware

A change approved in engineering has to reach four other functions. Where no handoff is defined, a person carries it.

The problem we work on

Your teams may be good. Your software may be good. The architecture between them can still fail.

A delivery organization that feels harder to run with every project added is rarely short of talent or short of software. It is short of an agreed architecture between the two. Three patterns come up again and again.

  1. 01

    Human Middleware

    Experienced people become the integration layer between teams, systems and decisions. The operation runs on what they remember to carry across.

  2. 02

    Coordination Latency

    A change is approved, but different parts of the operation begin acting on the new reality at different times.

  3. 03

    Fragmented Operational State

    Each function holds part of the truth, and nobody owns the complete operational lifecycle.

What BoRo does

Architecture before implementation.

Four stages. The third one only happens if the second one says it should.

  1. 01

    Diagnose

    Trace how work, decisions and information actually move, not how the process documents say they move.

  2. 02

    Architect

    Define lifecycle states, ownership, decision rights, handoffs, exceptions and system boundaries.

  3. 03

    Implement

    Configure, connect, extend or build only what the operating architecture requires.

  4. 04

    Operate and improve

    Measure how the operating model performs and keep changing it as the operation changes.

Operations OS, the implementation layer
Where it starts

Architecture Sprint

Ten business days to understand where the operating model is breaking and determine what, if anything, should be implemented.

See how the Architecture Sprint works
  • Current-state operating architecture, lifecycle states and decision rights
  • System-of-record boundaries and change propagation
  • A prioritized roadmap and an executive decision readout

It can conclude that your current systems are sufficient. That is a real outcome, and we deliver it.

Where we work

Project delivery first. The same pattern elsewhere.

Operational architecture is the category. The operations we concentrate on are growth-stage Solar + BESS project delivery companies, where experienced people have become the integration layer between engineering, procurement and construction.

Primary focus

Solar + BESS Project Delivery

Growth-stage EPCs, developer-EPCs and integrated project-delivery companies running several projects at once, where a change in one function has to reach every other one before anyone buys or builds the wrong thing.

Operational architecture for Solar + BESS project delivery
Operational areas
  • Engineering coordination
  • Procurement
  • Project controls
  • Construction execution
  • Commissioning
  • Cross-functional change propagation
Adjacent operations

Distributed operations

Operations where the lifecycle of a single job crosses several teams, systems and locations before it can be closed.

Coordinating: Customers · Dispatch · Field teams · Assets · Parts · Closeout

Operational systems

Businesses where project, field, commercial and back-office functions have to operate from the same operational reality, and currently do not.

Coordinating: Project · Field · Commercial · Back office

See where we workSee real work and example architectures

Solar + BESS project delivery is BoRo's current commercial focus, not a claim of exclusivity or of a track record in the sector. Operational architecture is the category; the focus is where we apply it first.

Architecture before implementation

Start with the constraint, not the software

Tell us what is breaking in the operation. If the answer is that you do not need to build anything, we will say so.

Discuss an operational constraint