Get in touch

Who does the work

One team, from the PLC to the plant dashboard.

Vectis Works reads the numbers your PLCs, HMIs, Kepware or OPC servers and shift spreadsheets already hold, and turns them into a live dashboard for the plant.

Controls, data and software sit with the same people, so nothing gets lost between the tag list and the screen your supervisors read.

Get in touch How an engagement runs

On the team

Four disciplines, working the same job.

  • Controls and PLC work

    Reading tags from PLCs, HMIs and OPC servers, Allen-Bradley included, without changing how the controls run.

  • Data architecture and integration

    Mapping and cleaning tags, then joining them to parts, shifts and stop reasons in one structured layer.

  • Backend and frontend development

    The services behind the dashboard, and screens a supervisor can read from across the floor.

  • ERP advisory

    Where shift calendars, part standards and cycle times live, and how they meet the machine data.

What we're known for

Most first projects start here: the numbers already on the floor, put where people can use them.

Shop-floor dashboard

Your plant's numbers, live, on one screen.

We connect the PLCs, HMIs, Kepware or OPC servers and the spreadsheets around them, and build a live dashboard for the lines and work centers you pick.

We only ever read from the controls. Nothing we install can send a value back to a PLC. Whatever gets built runs inside your environment and belongs to you, source and all. Support afterwards is optional, and it never comes with a licence.

A plain word on OEE. Status and counts come off the controls. OEE also needs the planned hours per shift and a target cycle for each part, and those normally sit in your ERP or your standards, so we pull them in with your team.

What the screen carries

  • Machine status, as it changes
  • Part counts by line and shift
  • Run rates
  • Uptime, and downtime with reasons
  • Scrap, where the data exists
  • OEE and trends over time

How an engagement runs

Four phases. Each one ends with something your own people can look at and check.

  1. 1

    Walk the floor

    We go through the lines and the tag list with your controls and IT people, and agree which line and which question come first.

  2. 2

    Tap the data

    We set up a read-only connection, tidy the tag names, and add what machines don't know: shifts, part numbers, stop reasons.

  3. 3

    Prove one line

    The first views go live for that line. Your supervisors hold them up against what they see on the floor.

  4. 4

    Widen and hand over

    We add lines, reports and the data layer, then hand over the code and the notes on how it all fits together.

How we work

Three rules we hold to on every job, on the floor and in the code.

Staged, and checked by your team

We deliver in stages. At each one, your people compare the screen with the counts and logs they already trust before the next stage starts.

You own what we build

Source code, data and systems all live in your environment, and every piece is yours to keep. Support afterwards is there if you want it.

Read-only and reversible

We read from the controls and never write to them. The connection can come out again without changing how the floor runs.

Other work we take on

The same team handles the systems around the floor, whether or not a dashboard comes first.

Spreadsheets into web apps

Critical spreadsheet workflows rebuilt as governed web apps, with an audit trail and permissions. You approve the rules before anything is rebuilt.

Automation and integrations

Hand-offs that run on their own, and the systems that should talk to each other, connected.

A structured data layer

Plant and business data in one place, with APIs your other tools can read from.

Reports that assemble themselves

The shift and weekly reports someone pieces together by hand, produced from the data instead.

Custom internal tools

Focused tools for the people who run the floor and the office work around it.

Ongoing support

Help after handover for changes, new lines and fixes, when you want it.

Based in Nashville

Vectis Works is a Tennessee firm. Its systems work goes back 20+ years, in businesses where operations do the heavy lifting.

Visit vectisworks.com

Tell us which line you'd start with.

Send a short note through the Vectis Works contact form. The people who would do the work read it.

If it isn't a fit for us, we'll say so.

It helps to mention

  • The line or work center you care about first
  • Where its data lives today: controls, an OPC server, spreadsheets
  • The question you want the screen to answer
Get in touch