Skip to main content

Process

How We Work

One method. From data to done.

Most projects do not get sideways because the technology is wrong. They get sideways because expectations are not aligned, and because there is no shared discipline to the process. Our method was built to fix both — from the first data pull through the final go-live.

At every step, everyone knows where we are, what is happening now, and what comes next — you, your team, us, the vendors, the executive sponsor. That shared orientation is what keeps a big project moving in the same direction, through design and through delivery.

Two halves of one engagement. FORGE is how we design. Execution is how we deliver. Both run the same playbook, every time. Nothing hidden.

FORGE-
HOW WE DESIGN

 

F — Foundation (Phase 1)

Know the operation. Understand the priorities. Before evaluating any solution.

Every engagement starts on the floor and in the data. We spend time understanding what your operation actually does, what you are solving for, and what “success” looks like — from the executive sponsor to the operations team.

The output is a shared baseline that everyone agrees describes the current state. Every recommendation in the next four phases traces back to it.

O — Options (Phase 2)

Break down a crowded market. Score every viable technology. Narrow to a real short list.

The automation market is crowded and getting more crowded. Options is where we bring structure to it — evaluating which technology categories fit your operation and which do not. Non-viable categories are eliminated up front, with the reason documented so the disqualification is defensible.

Within relevant categories, every viable technology gets scored against your operational constraints and priorities. Multiple solutions will usually pass the numbers. The right choice comes down to what we are solving for qualitatively.

R — Return (Phase 3)

Model the numbers. Turn a shortlist into a comparison you can defend to your CFO.

Cost narrows the field. We build operating concepts for the leading options from Phase 2 and run each through a forward-looking financial model — total investment, payback, and cash flow over time.

The output is not just “which option has the best ROI.” It is a defensible comparison across the shortlist, with the assumptions on the page and the sensitivities named.

G — Ground (Phase 4)

Take the leading concept off the spreadsheet. Test it in the space. Refine what needs refining.

By this point, the recommendation exists on paper. Ground is where we take it into your facility — testing whether it fits, physically and operationally.

If something can be improved, we iterate. Layouts, equipment selection, workflow, build sequencing. The point of Ground is not to defend the Phase 3 recommendation — it is to make sure the recommendation delivers the best possible outcome.

E — Execute (Phase 5)

A final recommendation. A defensible business case. The artifacts your team needs to act.

Execute is where everything from the previous four phases gets consolidated into the deliverables your organization can act on — presentation deck for the executive audience, business case for the internal approval process, and the recommendation memo behind them.

Every recommendation traces back to Foundation. Every option was scored in Options. Every dollar is modeled in Return. Every layout was tested in Ground. Execute is where that chain gets presented as one integrated argument.

All of it delivered by a partner who can help you build it.

Know the operation. Understand the priorities. Before evaluating any solution.

Every engagement starts on the floor and in the data. We spend time understanding what your operation actually does, what you are solving for, and what “success” looks like — from the executive sponsor to the operations team.

The output is a shared baseline that everyone agrees describes the current state. Every recommendation in the next four phases traces back to it.

Break down a crowded market. Score every viable technology. Narrow to a real short list.

The automation market is crowded and getting more crowded. Options is where we bring structure to it — evaluating which technology categories fit your operation and which do not. Non-viable categories are eliminated up front, with the reason documented so the disqualification is defensible.

Within relevant categories, every viable technology gets scored against your operational constraints and priorities. Multiple solutions will usually pass the numbers. The right choice comes down to what we are solving for qualitatively.

Model the numbers. Turn a shortlist into a comparison you can defend to your CFO.

Cost narrows the field. We build operating concepts for the leading options from Phase 2 and run each through a forward-looking financial model — total investment, payback, and cash flow over time.

The output is not just “which option has the best ROI.” It is a defensible comparison across the shortlist, with the assumptions on the page and the sensitivities named.

Take the leading concept off the spreadsheet. Test it in the space. Refine what needs refining.

By this point, the recommendation exists on paper. Ground is where we take it into your facility — testing whether it fits, physically and operationally.

If something can be improved, we iterate. Layouts, equipment selection, workflow, build sequencing. The point of Ground is not to defend the Phase 3 recommendation — it is to make sure the recommendation delivers the best possible outcome.

A final recommendation. A defensible business case. The artifacts your team needs to act.

Execute is where everything from the previous four phases gets consolidated into the deliverables your organization can act on — presentation deck for the executive audience, business case for the internal approval process, and the recommendation memo behind them.

Every recommendation traces back to Foundation. Every option was scored in Options. Every dollar is modeled in Return. Every layout was tested in Ground. Execute is where that chain gets presented as one integrated argument.

All of it delivered by a partner who can help you build it.

Execution-
How we deliver

 

The first step of every project. It aligns you, us, our partners, and the trades on a shared view of what needs to happen, and when. Changes are expected as phases progress, but the baseline is set, and every downstream phase measures against it.

When technology needs to be sourced, we run a structured RFQ process. Requirements get defined, a qualified list of partners is engaged, and responses get scored on factors like technical fit, experience, and cost. The result is a value-based selection, documented and defensible — partners chosen because they are the right ones for your problem and your business.

Once partners are selected and their pricing is firm, the budget and schedule get finalized — the design-phase estimate becomes a commitment. This is the signoff moment for you, your finance team, and your executive sponsor: everyone sees the same numbers and the same timeline before capital moves. If something changes later, it changes against a documented baseline.

The design moves from concept into the drawings the trades and permitting authorities can actually build from. Layouts, elevations, structural details, mechanical and electrical requirements, life safety, tie-ins to existing systems — all worked out at engineering detail. The full package gets reviewed by you, the vendors, and where required, the authorities having jurisdiction. Nothing gets ordered, permitted, or installed until it is approved.

Every automation system runs on rules. The Software and Controls Specifications capture those rules in writing before code is written — WMS integration points, PLC logic, HMI screen behavior, alarm handling, and how the system handles exceptions. This is where “the system should do X” becomes precise enough for a controls engineer or software developer to implement, and where mismatches between what you expect and what the vendors are building tend to surface. Catching them here, on paper, is much better than catching them on go-live day.

This is where the design moves off the drawings and into the facility. Trades get coordinated, mechanical checkout happens, controls get wired, software gets deployed. Commissioning is the final gate before turnover — every component verified, every interface tested, and the system running for the first time under controlled conditions. The purpose is to prove it is ready to run under real conditions, before it has to.

Testing is where users get their hands on the system for the first time — end-user acceptance, integration, and performance testing. Anything that does not work as expected gets fixed here, before it becomes a go-live problem. Training runs in parallel: operators, supervisors, and maintenance teams learn the system before they need to run it under peak volume. A spares inventory gets ordered and shelved in the same window, so day-one problems do not stop the operation.

Go-live is not the finish line. We stay onsite through go-live and into stabilization — watching the system run, closing punch-list items, and making the small adjustments every automation system needs in its first weeks. Stabilization ends when the system is hitting design rates, the operators are running it without our support, and the maintenance team is handling it on their own. The handoff happens when the operation is running the way it was designed to, not simply when the first order ships.

Secret Link