Trust and security
Each customer's data lives in its own schema on AWS, with its own database user and storage bucket. Traffic is encrypted, and every change names a person and a time.
Plant 1
Plant 2
Planning
Distribution
TLS 1.2+
Other customers
Your organization
Helpful information
No two customers share a schema, a database user, a storage bucket or a machine-data table.
Plant Toolbox runs serverless inside a private AWS network, so there are no servers for your IT team to look after.
Every connection is encrypted, and nothing in storage is public.
Each access level sets what its people can do in each sub-module.
People sign in with a password and a time-based code, or with Microsoft single sign-on.
Each write by a signed-in user adds a row to the system log, with a name and a time.
Data path
Signals, entries and the shift's work all land in your own database schema on AWS, then reach people in the browser and on Line Remote Displays. Pick a path to follow it step by step.
Machine signal · L1 and L2 · 9 steps
On the line
Line sensorscounts, run state
Count units and see each stop at the machine.
Line 4 · Filler stops at 08:52
At the edge
Plant Toolbox collectorL1 single · L2 multi-sensor
Publishes each change to AWS IoT Core.
Filler · L2 multi-sensor collector
AWS · private networkKept apart for each customer
AWS IoT Coredevice messages
Receives the device message.
AWS · private network
Machine-data tableone per customerKept apart for each customer
Holds it in your own table, apart from every other customer.
Harbor Point Plant only
Counts readabout every 10 s
About every 10 s it updates counts and rate, opens and closes downtime, and Chase Logic names the machine that caused the stop.
08:52 Filler · Bottle infeed · Jam
Database schemaown database userKept apart for each customer
Stores the event, the counts and the hourly OEE in your schema.
Stops 6 · 08 h OEE 79%
AppAWS Lambda · checks access
Builds each screen for the signed-in user, within that user's access.
Production Dashboard · Line 4
CloudFrontTLS 1.2+ · HTTPS only
Serves it over TLS 1.2 or higher.
HTTPS only
Where it shows
Browser and Line Remote Displaysdesktop, tablet, phone · Remote Displays paired by one-time code
The stop shows in Downtime Events and on the Line 4 Remote Display.
0:07:30 · scrap 22
PLC tags · L3 · 9 steps
On the line
PLCtags per unit op
The machine's controller already holds counts, states and faults as tags.
Line 4 · Palletizer
At the edge
Middlewaretag map · L3
Reads the tags through a tag map set per unit op in the onboarding hub.
tag map · per unit op
AWS · private networkKept apart for each customer
AWS IoT Coredevice messages
The middleware publishes to AWS IoT Core with its own certificate, on the same path as a collector.
AWS · private network
Machine-data tableone per customerKept apart for each customer
Holds it in your own table, apart from every other customer.
From here, the same path as a machine signal
Counts readabout every 10 s
About every 10 s it updates counts and rate, opens and closes downtime, and Chase Logic names the machine that caused the stop.
From here, the same path as a machine signal
Database schemaown database userKept apart for each customer
Stores the event, the counts and the hourly OEE in your schema.
From here, the same path as a machine signal
AppAWS Lambda · checks access
Builds each screen for the signed-in user, within that user's access.
From here, the same path as a machine signal
CloudFrontTLS 1.2+ · HTTPS only
Serves it over TLS 1.2 or higher.
From here, the same path as a machine signal
Where it shows
Browser and Line Remote Displaysdesktop, tablet, phone · Remote Displays paired by one-time code
The same screens, whichever way the counts arrive.
Production Dashboard · Line 4
Manual entry · L0 · skips the edge · 6 steps
On the line
Tablet or browsercounts, stops, checks
A signed-in person enters a count, a stop or a check.
07:14 Case Packer · Fault · Glue temp low
AWS · private networkKept apart for each customer
CloudFrontTLS 1.2+ · HTTPS only
Carries it over TLS 1.2 or higher.
HTTPS only
AppAWS Lambda · checks access
Checks that person's access for the sub-module, then saves.
needs Add on the sub-module
Database schemaown database userKept apart for each customer
Stores the entry in your schema and adds a log row: user, time, table, record.
logged, see System logs
Storage bucketprivate · files, photosKept apart for each customer
Photos and files go to your private bucket.
no public access
Where it shows
Browser and Line Remote Displaysdesktop, tablet, phone · Remote Displays paired by one-time code
Boards and Remote Displays show the entry on their next refresh.
Production Dashboard · Line 4
Shift work · about every 5 minutes · starts inside AWS · 6 steps
AWS · private networkKept apart for each customer
Shift workabout every 5 minutes
About every 5 minutes, for each plant, it reads shift definitions and schedules from your schema.
Shift A · 06:00–14:00
Database schemaown database userKept apart for each customer
Receives the shift's work: CIL events, Process Confirmation events and PM work orders. Missed checks and late tasks are marked.
10:30 Conveyor chain lube · WO-5521 13:00
AppAWS Lambda · checks access
Shows each item on its own screen for the people who can see it.
CIL Event Execution · Maintenance Work Orders
CloudFrontTLS 1.2+ · HTTPS only
Serves it over TLS 1.2 or higher.
HTTPS only
Where it shows
Browser and Line Remote Displaysdesktop, tablet, phone · Remote Displays paired by one-time code
The work is on the board before anyone asks for it.
Quick Actions: Centerlines 3 · CILs 4 · Defects 1
Emailnotifications
The same pass sends queued email notifications.
Amazon SES
Identity and access
Five permissions per sub-module: Read, Add, Edit, Delete and Approve. Each step up includes the ones before it.
OperatorLine leadMaintenancePlant admin
BackRequire 2FA : onoff
Your systems
The questions a buyer's checklist asks, answered row by row, then how Plant Toolbox works beside your ERP.
Plant Toolbox runs beside the systems you already have, one source at a time.