TRANXACT.AI Help

API package

Manufacturing

BOMs, routings, work centers, and production execution with lot genealogy and WIP accounting.

116 APIs809 operationsBase path /api/mfg

Batch 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. /api/mfg/batch-deviations 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. /api/mfg/batch-records 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. /api/mfg/batch-signatures 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. /api/mfg/batch-steps 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. /api/mfg/recipes 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. /api/mfg/batch-parameters 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. /api/mfg/recipe-parameters 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. /api/mfg/recipe-phases GET2 POST2 PUT1 DELETE1

Change Control

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. /api/mfg/iot-alert-rules 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. /api/mfg/iot-alerts GET2 POST3 PUT1 DELETE1 IoT Devices Sensors, meters, counters, cameras and readers, each bound to the machine it measures. /api/mfg/iot-devices 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. /api/mfg/iot-gateways 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. /api/mfg/plc-controllers 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. /api/mfg/plc-tags 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. /api/mfg/plc-commands 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. /api/mfg/iot-readings 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. /api/mfg/iot-signals 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. /api/mfg/plc-bindings GET2 POST2 PUT1 DELETE1

Design & Documents

Assembly Structure Which models sit inside which, and where. An assembly cannot contain itself at any depth. /api/mfg/model-components 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. /api/mfg/cam-programs 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. /api/mfg/document-links 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. /api/mfg/document-revisions 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. /api/mfg/engineering-documents 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. /api/mfg/models GET2 POST2 PUT1 DELETE1 Program Tool Lists Which tools a program loads, in the order it loads them. /api/mfg/cam-program-tools 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. /api/mfg/tools GET2 POST2 PUT1 DELETE1

Engineering

Equipment & OEE

Inspection & Disposition

Kanban

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. /api/mfg/failure-modes 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. /api/mfg/maintenance-orders 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. /api/mfg/maintenance-plans 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. /api/mfg/meter-readings 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. /api/mfg/maintenance-parts GET2 POST2 PUT1 DELETE1 Order Tasks The checklist as executed, with any measurement taken against its spec. /api/mfg/maintenance-tasks 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. /api/mfg/maintenance-plan-tasks 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. /api/mfg/spare-parts 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. /api/mfg/ai-capabilities 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. /api/mfg/exception-actions 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. /api/mfg/document-extractions 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. /api/mfg/exception-policies 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. /api/mfg/ai-predictions 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. /api/mfg/copilot 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. /api/mfg/ai-recommendations 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. /api/mfg/root-cause-analyses 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. /api/mfg/vision-inspections 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. /api/mfg/workflow-adaptations GET3 POST4 PUT1 DELETE1

Master Scheduling

Material Availability

Material Planning

Measurement & Traceability

Order Costing & Profitability

Production

Quality

Quality Events

Quality Planning

Reporting

Services and actions

Shop Floor