API package
Manufacturing
BOMs, routings, work centers, and production execution with lot genealogy and WIP accounting.
116 APIs809 operationsBase path
/api/mfgBatch Manufacturing
Batch Deviations
Raised at the moment it happens, by the person or the machine that saw it. A deviation opened at review time is a much weaker animal.
GET2 POST3 PUT1 DELETE1
Batch Records
What a batch DID, in the order it happened, with every controlled parameter against the specification it was supposed to meet. Review by exception: the counts say whether it can be released without reading two hundred pages.
GET4 POST6 PUT2 DELETE2
Batch Signatures
Who signed what, and what the signature MEANT. The signed content is hashed, so a later edit would not match — and there is no update path, because that is what a signature is.
GET2 POST2 PUT1 DELETE1
Batch Steps
The executed phases, in sequence. A step is executed through its own route and signed; it is never edited on a grid.
GET2 POST4 PUT1 DELETE1
Master Recipes
The process industry’s counterpart of a BOM plus a routing: its steps carry parameters with specifications, and its quantities scale with batch size.
GET3 POST4 PUT2 DELETE2
Parameter Captures
Every captured value against the specification that was fixed before the batch started. A correction does not overwrite — it points at the original, because an audit trail that can be edited is not one.
GET2 POST3 PUT1 DELETE1
Recipe Parameters
What has to be measured, and what it has to be. Fixed here, BEFORE the batch — which is the property that makes an in-spec judgement a fact rather than a later opinion.
GET2 POST2 PUT1 DELETE1
Recipe Phases
The instruction as it is read on the floor. Held as text rather than as a reference because the executed copy has to be the one that was approved.
GET2 POST2 PUT1 DELETE1
Change Control
Affected Objects
What the change touches, one line each. This is what makes an ECO auditable: not "we changed the bracket" but nine objects, from this to that, each closed by somebody.
GET2 POST3 PUT1 DELETE1
Change Approvals
Who has to agree, in what order. A skipped step is recorded as skipped rather than deleted — "who did NOT review this" is the question asked after a recall.
GET2 POST3 PUT1 DELETE1
Change Board
Who signs each step of a change request’s review board: a role, an HRMS position or a named person. Given to each step when a request is submitted — never to whoever raised the request. A step nobody can be given shows “No approver assigned” until this says who.
GET2 POST2 PUT1 DELETE1
Change Orders
The decision, with an effectivity date, an affected-object list and a disposition for stock already made. Released only once every discipline has answered.
GET5 POST9 PUT3 DELETE3
Change Requests
Requests to change a product or document, reviewed and approved before a change order is made.
GET2 POST8 PUT1 DELETE1
Connected Plant
Alert Rules
A threshold, and how long it has to be true. Without the second, every rule fires on a single noisy sample and everybody turns alerting off.
GET2 POST2 PUT1 DELETE1
Alerts
What fired, with the threshold AS IT WAS. A rule changes; the alerts it already raised keep the threshold they were raised against.
GET2 POST3 PUT1 DELETE1
IoT Devices
Sensors, meters, counters, cameras and readers, each bound to the machine it measures.
GET3 POST3 PUT2 DELETE2
IoT Gateways
The box between the plant network and this platform. A gateway rather than a direct device connection because that is how it is built — sensors do not have credentials.
GET2 POST2 PUT1 DELETE1
PLC Controllers
Writes are OFF by default, and that is deliberate: a write to a running machine is a physical action, and the safest configuration is the one where a misconfigured screen cannot take one.
GET3 POST3 PUT2 DELETE2
PLC Tags
A memory address in a machine. The min and max are enforced on THIS side of the network, where the error message can say why.
GET2 POST2 PUT1 DELETE1
PLC Writes
Every value this platform sends to a machine, requested and approved separately, with the old value recorded. This is the table an auditor asks for after an incident.
GET2 POST5 PUT1 DELETE1
Readings
The series. A sensor that returns a value it does not believe is worse than one that returns nothing, which is why the quality flag is on every row.
GET2 POST2 PUT1 DELETE1
Signals
What a device measures, one row per quantity. The scaling lives here because it is a property of the measurement — applied downstream, every consumer has to know it and one of them eventually will not.
GET2 POST2 PUT1 DELETE1
Tag Bindings
What a tag MEANS, and the reason this integration is configuration rather than code. "DB10.DBW4" is meaningless; bound as "good count for PRESS-02" it feeds OEE, confirmations and kanban without anybody writing a transformation.
GET2 POST2 PUT1 DELETE1
Design & Documents
Assembly Structure
Which models sit inside which, and where. An assembly cannot contain itself at any depth.
GET2 POST2 PUT1 DELETE1
CAM / NC Programs
Tied to an item REVISION, not to a part. A program posted against revision B and run against revision C makes a thousand parts that pass every check the machine makes.
GET3 POST6 PUT2 DELETE2
Document Assignments
Where a document is used. A drawing belongs to a part, but a routing operation and an inspection plan reference it too — and "what do I have to reissue" is that list.
GET2 POST2 PUT1 DELETE1
Document Revisions
Every version, with who drew it, who checked it and who released it. A released revision is not editable — it is superseded.
GET2 POST3 PUT1 DELETE1
Engineering Documents
The drawing, the model, the specification and the work instruction — under change control, so a released revision is frozen and a superseded one is kept.
GET3 POST4 PUT2 DELETE2
Models
Geometry held as a mesh rather than a file, so it can be measured. A model that is not closed reports no volume rather than a wrong one.
GET2 POST2 PUT1 DELETE1
Program Tool Lists
Which tools a program loads, in the order it loads them.
GET2 POST2 PUT1 DELETE1
Tooling
A tool is not an item and not a machine: its life is measured in cuts, and it is reground rather than replaced.
GET2 POST2 PUT1 DELETE1
Engineering
Bills of Material
Read and maintain boms records (mfg.boms).
GET5 POST8 PUT2 DELETE2
Production Versions
Which bill of material, routing and fulfilment (make, buy, subcontract) an item is made with, chosen by the configuration attributes on the sales order line. MRP plans each order line on the version its attributes match.
GET2 POST2 PUT1 DELETE1
Routings
Read and maintain routings records (mfg.routings).
GET3 POST4 PUT2 DELETE2
Work Centers
Read and maintain work centers records (mfg.work_centers).
GET2 POST2 PUT1 DELETE1
Equipment & OEE
Andon Board
What the plant looks like right now: every machine, its state, how long it has been in it, and what it is running. The wall screen and the shift report read the same query.
GET1
Equipment
The physical machine, which is neither the work center (a scheduling object) nor the fixed asset (a ledger one). It names both.
GET3 POST4 PUT2 DELETE2
Machine States
One row per state, opened when it starts and closed when it ends. A stop with no reason is the queue a supervisor clears — and until it is cleared, the loss analysis is unreliable.
GET2 POST3 PUT1 DELETE1
OEE Periods
The computed answer per machine per shift, with every input kept beside it — because a figure recomputed against today’s nameplate rate cannot be compared with last quarter. A period is not typed in: Compute OEE works it out for a day from the machine states and counts.
GET2 POST2 PUT1 DELETE1
Inspection & Disposition
Inspections
Every inspection — incoming, in-process and final — with what was measured, what it was measured against, whether it passed, and what was decided when it did not. End-to-end quality traceability from purchased material to delivery.
GET2 POST2 PUT1 DELETE1
Usage Decisions
What was decided about each inspection lot: accepted, returned, reworked, scrapped, replaced, or accepted with an approved deviation — with the reason, the corrective action, what it raised and what it did to the stock held for the lot. A lot that passes is accepted by the system unless the company decides every lot itself.
GET2 POST2 PUT1 DELETE1
Kanban
Card Movements
Every state change, timestamped. The loop’s real cycle time is measured off these, which is what makes the sizing self-correcting rather than aspirational.
GET2 POST2 PUT1 DELETE1
Kanban Cards
The containers. Their states, summed, ARE the work in progress — there is no other number.
GET2 POST5 PUT1 DELETE1
Kanban Loops
The control cycle: what circulates between where and where, in containers of what size, and how many of them exist. The card count is the cap on the stock in the system.
GET2 POST4 PUT1 DELETE1
Loop Sizings
What the arithmetic said the card count should be, against what it is — with the inputs kept, because "why do we have eleven cards on this part" is otherwise unanswerable a month later.
GET2 POST3 PUT1 DELETE1
Maintenance
Failure Modes
How this KIND of equipment fails, with the effect and the detection method. Kept at the class rather than the machine, or the same bearing failure is entered forty times and never groups.
GET2 POST2 PUT1 DELETE1
Maintenance Orders
Preventive and breakdown work in one document, deliberately: the ratio between them is the most useful number in maintenance, and it cannot be computed across two tables.
GET4 POST6 PUT3 DELETE3
Maintenance Plans
What should be done, how often, and measured how — by calendar, by running hours, by cycles, or by a condition somebody is monitoring. The three are different strategies with different costs.
GET3 POST4 PUT2 DELETE2
Meter Readings
What turns "every 2,000 hours" into a date. A reading below the previous one is recorded as a RESET rather than as a negative — a replaced meter would otherwise poison every average built on it.
GET2 POST3 PUT1 DELETE1
Order Parts
Spares consumed, out of the same storeroom as everything else. A maintenance module with its own parallel stock is how a plant ends up with two answers to how many bearings it has.
GET2 POST2 PUT1 DELETE1
Order Tasks
The checklist as executed, with any measurement taken against its spec.
GET2 POST2 PUT1 DELETE1
Plan Task Lists
What the technician actually does. A task that records a MEASUREMENT is the basis of condition monitoring done by hand, and it needs a spec like any other measurement.
GET2 POST2 PUT1 DELETE1
Spare Parts
Which parts belong to which machine — an equipment bill of material. Not mfg.boms: a BOM says what a product is MADE of, and this says what a machine can consume.
GET2 POST2 PUT1 DELETE1
Manufacturing Intelligence
AI Capabilities
The fourteen, with the two columns that matter: what each is ALLOWED to do, and how accurate it has been measured to be. Nothing ships able to act on its own.
GET2 POST2 PUT1 DELETE1
Autonomous Actions
What the automation did, with the state before and after — which is what makes it reversible and what an auditor reads. A refusal is recorded too: a policy that quietly declines and says nothing is worse than one that does not exist.
GET2 POST3 PUT1 DELETE1
Document Intelligence
Certificates, mill reports and packing lists read into fields — and, the part that matters, CHECKED against the item’s specification. A certificate transcribed perfectly and compared with nothing has saved typing and nothing else.
GET2 POST3 PUT1 DELETE1
Exception Policies
When THIS exception appears, and it is within THESE bounds, do THAT — and tell somebody. The bounds are the difference between automation and an unattended system making commitments nobody sized.
GET2 POST2 PUT1 DELETE1
Predictions
A scored statement about ONE record, with its drivers ranked — and the outcome filled in later, because a prediction is worthless until it can be compared with what happened.
GET2 POST3 PUT1 DELETE1
Production Copilot
Ask the plant a question in your own words. Answered from a fixed set of queries over this company’s own records, with the records named — and handed to the platform assistant rather than guessed at when it falls outside them.
POST1
Recommendations
What to do, what it is worth, and what somebody decided. A recommendation nobody accepted is the most useful record in the table.
GET2 POST3 PUT1 DELETE1
Root-Cause Analyses
Ranked candidates from what actually CHANGED around the failure — material lots, machine states, batch parameters, control charts, gauge calibration. Never the last word: the accepted cause is a person’s.
GET2 POST4 PUT1 DELETE1
Vision Inspections
Surface and dimensional defects found by camera, with the sampled human verdict beside them. The disagreement rate — not the accuracy figure — is what decides whether a camera may act on its own.
GET2 POST4 PUT1 DELETE1
Workflow Adaptations
Where a standard process was tightened or relaxed for a condition, and what ends it. An adaptation with no expiry is a permanent process change made by an automation, which is exactly what this screen exists to prevent.
GET3 POST4 PUT1 DELETE1
Master Scheduling
Bills of Resources
What one unit costs in critical-resource time — deliberately coarser than the routing. The offset matters: press time for something shipped in week 14 is spent in week 11.
GET2 POST2 PUT1 DELETE1
Master Production Schedules
What the plant commits to finish, period by period. The consumption rule is the whole point: a company that adds forecast to orders builds everything twice.
GET3 POST6 PUT2 DELETE2
Rough-Cut Capacity
The load a master schedule would place on the critical resources, months before a routing is ever exploded. Kept as history so this plan can be compared with last month’s.
GET2 POST2 PUT1 DELETE1
Schedule Periods
One row per period. Forecast, orders and the carried balance are computed; the quantity and the firm flag are the decision.
GET2 POST2 PUT1 DELETE1
Material Availability
Availability · Lines
Line by line: what is on hand, what of that is already promised, what is on order, what is on a production order, and what is genuinely short. The four are kept apart because “we have none” and “it is all promised elsewhere” want different things done about them.
GET2 POST2 PUT1 DELETE1
Availability Checks
The question “can this be made”, asked of a sales order or a configuration, and the answer as it stood at that moment. Kept as a document because the shortage it found is what a requisition was raised from.
GET3 POST4 PUT1 DELETE1
Material Reservations
Stock promised to one order and no longer offered to another. Without a reservation two orders are both told the same bar is available, and the second one finds out on the shop floor.
GET2 POST3 PUT1 DELETE1
Material Planning
Low-Level Codes
The deepest level each item appears at, which is what makes a netting run process components after their parents. A circular structure is flagged rather than thrown.
GET2 POST2 PUT1 DELETE1
MRP Options
How Run MRP plans configured sales order lines: whether lines built to the same answers become one production order, and whether a bought item is one requisition line for its total. Both are on until changed.
GET1 PUT1
Planning Decisions
Why a planner firmed a proposal early, split it, or moved it. The planning table records that it was firmed; only this records the judgement, which is the whole content of a planner’s day.
GET2 POST2 PUT1 DELETE1
Measurement & Traceability
Calibration Records
As found before adjustment, as left after it. A record that only keeps as-left has thrown away the part that matters.
GET2 POST2 PUT1 DELETE1
Gauges
A measurement taken with an out-of-calibration gauge is not a measurement — and every result since the last good calibration is in question.
GET2 POST3 PUT1 DELETE1
Lot Genealogy
A lot in both directions: what went into it, everything it went into, and everywhere it left the building. A system that only walks one way sends somebody to a spreadsheet at the worst possible moment.
GET1
Order Costing & Profitability
Operation Time Variance
What the routing said each operation would take and what it took, so an estimate that is consistently wrong can be corrected rather than argued about.
GET2 POST2 PUT1 DELETE1
Order Cost Projection
What an order has cost so far and where it is heading — so an order that is going to lose money is found before it is finished rather than after.
GET2 POST2 PUT1 DELETE1
Order Profitability
Quoted against actual, for every customer order: what it was sold for, what it was estimated to cost, what it actually cost element by element, and the margin that came of it.
GET2 POST2 PUT1 DELETE1
Production Order Cost
What a production order actually consumed, from what was posted rather than from an estimate: material issued, time confirmed, outside processing received and rework done.
GET2 POST2 PUT1 DELETE1
Production
Quality
Quality Events
Audit Findings
Every finding that is not an observation has to become an action. The CAPA link is what proves it did.
GET2 POST5 PUT1 DELETE1
Audits
Internal, supplier, customer and certification audits, with the finding counts that say whether it was a good audit or a quiet one.
GET3 POST8 PUT2 DELETE2
CAPA Actions
What each CAPA actually asked somebody to do, and whether they did it.
GET2 POST2 PUT1 DELETE1
Corrective & Preventive Actions
The investigation, and — the part that is always skipped — the check that it worked. A CAPA closed without a verification date is closed on hope.
GET3 POST8 PUT2 DELETE2
Customer Complaints
The regulated half of a complaint, which a service case cannot carry: the reportability decision, its clock, and whether the product actually failed.
GET2 POST7 PUT1 DELETE1
Nonconformances
Something is wrong with identified material. Containment before analysis: what is affected, where it is, and whether any of it has already gone to a customer.
GET2 POST4 PUT1 DELETE1
Quality Planning
Characteristics
What is measured, against what, with what. A gauge whose resolution is a tenth of the tolerance cannot police it, and the gauge R&R figure is the honest statement of that.
GET2 POST2 PUT1 DELETE1
Control Charts
Limits computed FROM THE PROCESS, never from the specification — a process comfortably inside a wide tolerance can be wildly out of control and nobody would see it.
GET2 POST3 PUT1 DELETE1
Inspection Plans
An inspection with no plan is one person’s opinion of what mattered that day. A plan fixes the characteristics, the method, the gauge and the sampling before the goods arrive.
GET3 POST5 PUT2 DELETE2
Subgroups
Every subgroup with its readings, its mean and range, and which control rules it broke. A point that breaks a rule while every part is in tolerance is the whole reason the chart exists.
GET2 POST3 PUT1 DELETE1
Reachable by link
Planned Orders
What the run proposed. Firming a make proposal here creates the works order and records why — which is the one thing the planning table cannot keep.
POST1
What Is Next
The next operation on every released order, what it needs, who is responsible — and, where it cannot start, the reason in words rather than a greyed-out button.
GET2 POST2 PUT1 DELETE1
Reporting
Services and actions
Board
The board service of Manufacturing: 1 operation(s).
GET1
Component choices
The component choices service of Manufacturing: 2 operation(s).
GET2
Dispatch
The dispatch service of Manufacturing: 1 operation(s).
GET1
Exceptions
The exceptions service of Manufacturing: 1 operation(s).
POST1
Inspections
The inspections service of Manufacturing: 3 operation(s).
POST3
Intelligence
The intelligence service of Manufacturing: 1 operation(s).
POST1
Iot
The iot service of Manufacturing: 1 operation(s).
POST1
Items
The items service of Manufacturing: 2 operation(s).
GET2
Low level codes
The low level codes service of Manufacturing: 1 operation(s).
POST1
Oee
The oee service of Manufacturing: 1 operation(s).
POST1
Plc
The plc service of Manufacturing: 2 operation(s).
GET1 POST1
Receipts
The receipts service of Manufacturing: 1 operation(s).
POST1
Sales orders
The sales orders service of Manufacturing: 1 operation(s).
GET1
Viz
The viz service of Manufacturing: 7 operation(s).
GET4 POST3
Workbench
The workbench service of Manufacturing: 1 operation(s).
GET1
Shop Floor
Confirmations
What was made at each operation, by whom and on what. Good, scrap and rework are three quantities with three costs, and setup time is separated from run time.
GET2 POST3 PUT1 DELETE1
Downtime
Every stop, coded. An open row is the machine being down right now, which is what the andon board reads.
GET2 POST4 PUT1 DELETE1
Material Staging
The request to have material at the line before it is needed. A request rather than a movement: the movement is a warehouse task, and this is the manufacturing half of that conversation.
GET2 POST3 PUT1 DELETE1
Production Shifts
The buckets OEE, downtime and confirmations are summed into. Deliberately thin — HRMS owns rosters and who is actually on shift.
GET2 POST2 PUT1 DELETE1
Reason Codes
One list for stoppages, scrap and rework, because the analysis is the same analysis. The loss bucket is what lets an OEE figure be decomposed without tagging anything twice.
GET2 POST2 PUT1 DELETE1
Rework Orders
Rework is a document, not a footnote. Absorbed into the original order it is invisible, which is why plants believe their yield is better than it is.
GET2 POST2 PUT1 DELETE1