Systems
Software subcontracting for controls integrators: above the historian
Where a software subcontractor's work ends and yours begins, and what the platform you already deploy can and can't give a client.
Computing America. Applications, integrations, data analysis and AI/ML engineering.
Send the scope
In short
- Integrators can build browser-facing applications, and platform tooling ships exactly that. The seam is what a platform can't give.
- Many platforms limit four properties however skilled the engineer: a current language and dependency stack, automated test and release discipline, identity and audit trails that satisfy an external reviewer, and a failure domain separate from the OT network.
- Consolidation work is the clearest case. Welding several plants' historians together produces an application-layer and data-modeling problem on a board deadline, which is a different discipline from the controls work that created it.
- The teaming shape that works is subcontract, with the integrator holding the client relationship. We'll work under your name, and we won't approach your client.
We take the software above the historian as your subcontractor, and we have no ambition to move down into controls work. If a client has asked you for something above it, the figure shows where the line falls, and the rest of this note covers what we would take and how the work runs.
Cross-plant reporting and portals
Applications, data models, audit evidence
Within: We build, as your subcontractor.Historians
Interface
Within: Shared: you expose it, we read it.HMI and SCADA configuration
Within: Yours. We never quote it..PLC programming and safety systems
Within: Yours. We never quote it..Panels, wiring and commissioning
Site acceptance testing and startup
Within: Yours. We never quote it..
Our work sits above the historian and yours below it, and the historian is the only interface between them.
SourceThe scope this firm states in this article; a statement of boundary, not measured data.
Why the line stays at the historian¶
The layers below it rest on certifications and years in specific vendor ecosystems. They also rest on being the firm that answers when a line is down at two in the morning, and we are not that firm.
What the seam actually is¶
Integrators can build applications, and anyone who has shipped an Ignition Perspective project knows it. Modern platform tooling builds browser-facing operational applications, mobile-first.
So where is the seam? It's what a platform can provide. An application built inside a platform inherits that platform's answers to four properties. Platforms differ, so for each row check what yours does today and what only its vendor's roadmap can change. For a long time the answers are fine, and then a predictable trigger arrives:
| Property | What it looks like when it starts to matter |
|---|---|
| A current language and dependency stack | The application needs a library, protocol or cryptographic primitive the embedded runtime lacks, and the roadmap for getting it belongs to the vendor. |
| Automated test and release discipline | Changing the application has become frightening, and there is no test suite, staged environment or pipeline to make it less so. |
| Identity and audit trails | Someone outside the plant (a customer, auditor, regulator or corporate) needs access or evidence, and the platform's user model may not extend to people outside the plant, or to the audit evidence they need. |
| A separate failure domain | People who should never touch the OT network can now reach the application, so the application's exposure and the control system's availability need to stop being tied together. |
None of this means the platform work was wrong. One capability may have outgrown the platform while the rest of the system stays where it is.
Where this comes up¶
Consolidation is the clearest case. When several plants come under one owner, their systems were specified independently, and the request that follows is reporting across the plants on a deadline set in a board meeting. Getting data out of each site is your controls work. What sits on top is an application and data-modeling problem: reconciling models that disagree about what a unit of production is, giving people outside each plant a way to see it, and showing where a number came from.
The other cases match the triggers in the table. A client wants a customer portal onto plant data. An audit needs an access and change trail for the application itself (who saw or changed what), which the platform's user model may not provide. Or an operator application has quietly become the system of record for something and now has to behave like one.
How teaming works¶
- You hold the client relationship. We subcontract to you and we're content to be invisible, working under your name and project management if the account needs that.
- We don't approach your client. Not during the work, not afterwards.
- The scope boundary is written down before anything starts, in both directions: what runs on your side, what runs on ours, and the interface between them.
- We'll say when the work doesn't need us. If it belongs inside the platform you already deploy, that's the right answer for your client, and we'd rather give it than win a bad project.
- Whatever we build is handed over with its source, tests and deployment path, so you or anyone you choose can maintain it.
What to send first¶
- The client's request, in the client's words, so we can see which part sits above the historian.
- The historian: product, version, and how other applications read from it today. That interface is the first thing written down.
- The access arrangement: how we would reach the data, through which network path and accounts, and who on your side and the client's approves it.
Next step
Send us the scope you would rather not quote.
If a plant is asking you for the half above the historian, send that part of the scope. We will tell you what we would take, what we would decline, and what it looks like as a subcontract under your paper.
- Phone
- (214) 723-2510
- Reply
- A person replies, not a sequence: within one business day, from someone who would be on the engagement.
Packages
Start with a package
Four packages, each with its price on the page. Pick one and buy it online.
$199/month
Billed monthly
$182.42/month
Billed yearly
$499/month
Billed monthly
$457.42/month
Billed yearly
- Scammers stopped from sending email as you
- Your website and systems scanned every week
- Your email settings checked every week
- Everything in the 1 to 10 plan
- Covers up to 50 people
$199/month
after a one-time setup fee
- A site planned, designed and built for you
- Hosting and updates every month
$499/month
Billed monthly
$457.42/month
Billed yearly
$999/month
Billed monthly
$915.75/month
Billed yearly
- Your Google profile, fully set up
- A Google post every week
- 2 social posts a week
- Everything in Get found
- 4 social posts a week
- Your top 10 Google searches tracked
from$500/month
after a one-time setup fee
- Your data gathered from the tools you use
- A first analysis that answers your questions
- New findings every month
Related reading
Strategy3 min readLow-code limits: where the ceiling is, and the signs you are near it
Four constraints set a low-code platform's ceiling, and the signs you are near it are visible.
Strategy3 min readShould your ERP partner build your custom software?
What an ERP partner takes on, what they decline, and how to read the shape of the answer before you brief anyone else.
