Portech

Method

Four principles. They decide what we will not do as much as what we will.

Vendor-neutrality is a structural position, not a promise. It shows in how the work is sequenced.

01

Start from the operation, not the product catalogue.

Work begins on site: shift patterns, peak gate hours, where the paperwork actually gets re-keyed. The specification follows from that. A system that suits the operation on paper and not at 03:00 has not been specified.

02

Vendor-neutral in sourcing.

We say plainly where off-the-shelf beats a build, and where it does not. Because we hold no platform of our own, the comparison can be written down and defended in front of a tender committee.

03

Integrate with what is already on site.

A clean slate is rarely available and rarely necessary. Equipment, sensors and legacy platforms stay where they are unless there is an operational reason to move them. Replacement is a last resort, costed as such.

04

Hand over a running system, or manage it.

Commissioning includes documentation, configuration control and the operator's own staff trained on it. If the operator would rather not carry it, we manage the estate instead. Nothing is left half-owned.

Terminal control room operator at a bank of monitors overlooking the container yard

Delivery model

Five stages, a constant offset, no connecting stem.

Each stage is a separate engagement and can be bought alone. The offset between them is fixed: what one stage hands to the next is defined before either begins.

01

Specify

A written requirement and acceptance criteria, drawn from the operation and agreed before anything is bought.

02

Source

A comparable bid set, a weighted evaluation and a recommendation you can put to committee.

03

Integrate

Systems connected to the equipment and platforms already on site, with the interfaces documented.

04

Commission

Staged cutover in live operation with rollback per stage, then sign-off against the criteria set in stage one.

05

Manage

Support under defined response times, or a trained operator team and a lifecycle schedule if you take it in-house.

Position

01

No platform of our own to defend.

Vendor-neutrality is structural, not a promise. The recommendation can be written down, compared and audited.

02

Specification starts at the operation.

Requirements are written from shift reality and site constraints, then held as the acceptance criteria at commissioning.

03

We integrate rather than replace.

What is already on site stays unless there is an operational reason to move it. Continuity is the deliverable.

Tell us what is already running.

Send the constraint, not the requirement. We will tell you what integrates and what does not.

Contact What we do→