Skip to content
Capabilities

Software, infrastructure, control systems and hardware — engineered by one group.

Most integration risk lives in the gaps between vendors. We close those gaps by keeping the disciplines on the same bench, under the same delivery process.

How the bench works

A practice is a permanent thing. A project is not.

The six practices below are staffed and funded as practices. Projects draw on them — which is what keeps a standard from being re-decided every time a new programme starts.

One bench, six practices, six places the work lands

Engineers are hired into a practice, not into a project — and the practice keeps its standards, its review gates and its platforms wherever the work goes. That is why a fix made for a flight controller shows up in an irrigation controller without anyone arranging a transfer.

PRACTICESWHERE IT LANDSEnterprise applicationsData centre & infrastructureSCADA & industrial automationEmbedded & electronicsCloud & DevOpsIoT & connected systemsVyovrinda — aerospaceSasyaveda — agricultureSavithru — energyEnterprise SoftwareSmart InfrastructureIndustrial AutomationOne engineering benchShared review gatesShared platformsShared standardsShared evidence trailThe shaded destinations are separately branded companies; the rest are divisions of P9eDifferent names on the door, the same bench behind it. That is the whole argument for the group being structured this way.

Not sure which of these your problem is?

That is usually a sign it spans more than one. Describe it and we will map it out with you.