For plants that already have controls, IT and ERP help

We work alongside the people you already have. You keep everything we build.

Vectis Works connects the data your machines already hold into a live dashboard for the plant. Nobody gets replaced. Your integrator, your IT team and your ERP consultant keep their work. We add the layer between them, then hand it over.

Stays with them

What your people keep doing

  • Your controls integrator keeps the PLC programs, the HMI screens and every change to the machines.
  • Your IT team keeps the network, the servers, the accounts and the rules for who gets access.
  • Your ERP consultant keeps orders, routings, standards and the shift calendar.
  • Your supervisors keep running the floor the way they run it today.
Comes from us

What we add

  • A read-only connection to your PLCs, HMIs, Kepware or OPC server and the spreadsheets around them. It can only listen; nothing travels back to a machine.
  • An organized data layer, set up inside your environment and reachable over APIs.
  • A live plant dashboard with machine status, part counts, run rates, downtime reasons and OEE.
  • A clean handover of the code, the documentation and the accounts.

Where we fit

Your controls people look after the machines. Your IT team looks after the network and the accounts. We build in the space between them.

The connection to the controls is read-only. There is no write path to a PLC. It runs on your network, under accounts your IT team sets up and can switch off.

Your ERP consultant stays in the picture too. Some of the numbers depend on data they already keep.

Where Vectis Works fits Two boxes at the top, your controls people and your IT team. Below them a Vectis Works box holds the data layer and the dashboard. A read-only arrow runs from the controls to the data layer. A dashed line from IT shows it all runs on your network, under your accounts. Your controlspeople Your ITteam PLCs and HMIsKepware or OPCMachine changes Network, serversAccounts, accessSecurity rules Read-only Your network, your accounts Data layer Tags, context and APIs Dashboard Status, counts, downtime, OEE Vectis Works Built inside your environment
Illustrative diagram. Every connection in it is written down for your people to check.

What we hand over

When the build is done, it belongs to you. Your people get all of it, written down, so whoever you choose can make the next change.

From the first day, every piece lives inside your environment. None of the code, data or systems sits on a server of ours.

  • Documented connections and accountsEvery data source, tag list and account we set up, written out for your IT and controls people.
  • The codeStored where you choose, and readable by any developer you bring in later.
  • The dashboardsRunning on your systems, with the definition of each number written down.
  • The data layerStructured tables and APIs that your other tools and teams can use.

What the dashboard shows

Data from PLCs, HMIs, Kepware or OPC servers and the spreadsheets around them, on one live screen for the plant.

Machine status

Which machines are running, idle or stopped right now.

Part counts

Counted at the machine, by line and by shift.

Run rates

How fast each line is running against its ideal pace.

Uptime and downtime

Time running, time stopped, and the reason for each stop.

Scrap

Shown where the data exists in the controls or quality records.

OEE and trends

The overall picture, and how it moves from week to week.

An honest note on OEE. The machines give you counts and running time. The rest of the math, meaning the shift calendar and each part's ideal cycle time, normally lives in ERP or in your standards. The controls rarely hold it. That is one more place your ERP consultant already helps.

Capabilities

The dashboard is often where the work starts. The same team takes on the work around it. Between us we handle PLC programming, Allen-Bradley included; data design and system integration; frontend and backend builds; and advice on ERP.

More than 20 years of systems work inside businesses where operations come first.

Spreadsheet workflows as governed web apps

The workbook everyone depends on becomes a web app with an audit trail and permissions. You approve the rules before anything is rebuilt.

Workflow automation and integrations

Handoffs that run on email and retyping move between your systems without someone carrying them.

One organized home for data, open by API

Plant and business data in one structured place, open to the tools you pick.

Reporting that assembles itself

Reports build from the data layer, so nobody copies numbers across by hand.

Custom internal tools

Small, focused apps for the jobs no package fits.

Ongoing support

There if you want it. The next section says how it works.

Support if you want it

Support is an option, not a licence. Keep us on or not, you still own the systems, their data and every line of code.

You can run what we built with your own people. You can also ask us to stay and extend it. The handover is the same either way.

Run it with your team

Your controls people and IT team hold the documentation, the code and the accounts. They can maintain it without us.

Keep us on

We add lines and views, adjust when the floor changes, and look after the data layer beside your own people.

Tell us who is already on your team.

Say who looks after your controls, your network and your ERP. We will tell you where a plant dashboard fits around them, or say plainly that it does not.