Integrations
1 of 4 not answering
Standard and predecessor-compatible adapters: IPC-CFX over AMQP, ISA-95 B2MML, the predecessor’s rack-service adapters, a UDP event channel, SQL statements that change data, and sending past movements to a new interface.
- Not in R1
- B2MML, IPC-CFX and a UDP event channel are adapters built only when a customer needs them (0032 §19–20; for UDP, once a consumer is found); a statement that changes data can’t be a lookup (J18-F05); a changed payload or target is a later corrective delivery (0048 §4).
- R1 instead
- The native API with signed webhooks (CloudEvents, EPCIS body), read-only parameterised SQL lookups and feeds, file codecs, and a CSV file per event through a file definition. Open Integrations
Integrations
Ready-made presets
Your systems
- SAP S/4 goods receiptHTTPS POST · SAP gateway · Reel put in · SAP OData goods movement v1
- MES adapter work-order intakeMicrosoft SQL · read on a schedule · Update work order · Janus MES v1
- IMS ReelSaveInpredecessor-compatibleHTTPS POST · https://<ims-host>:9443/api/rackservice/Service · Reel put in
- Counter ReelSavepredecessor-compatibleHTTPS POST · https://<counter-host>:9443/api/rackservice/Service · Reel taken out
Standard formats
- IPC-CFX line messagesIPC-2591Available as an adapter
Sends reels put in and taken out as materials loaded and unloaded; a move between racks is both. Receives reels installed on the line’s feeders.
Reel = material package (its reel ID) · part = internal part number · bay = storage location · each rack speaks as one CFX endpoint.
Usually asked for by the SMT line’s MES or the placement-machine vendor · AMQP 1.0 to the line’s CFX broker
- ISA-95 · B2MMLIEC 62264Available as an adapter
Sends every reel and movement to the plant MES or ERP; answers requests for the plant layout (Export hierarchy).
Reel = material sublot · part = material definition · bay = storage location · movement = material transaction with its evidence · site › area › line › rack = equipment hierarchy.
Usually asked for by the plant MES or ERP team · B2MML XML over HTTPS
- Line counter eventsHTTPNot answeringConnection refused since Mon 22:10 · 3 140 deliveries waiting
Checked from this server 14:31Name · 10.20.0.5Connection · refused on 9443Secure link · not reachedSign-in · not reached
Every take-out is recorded in Janus. Its delivery to the line counter waits.
Technical details
- Request
- POST https://10.20.0.5:9443/janus/events · signed webhook · CloudEvents
- Automation
- Take-outs to the line counter
- Owner
- Line counter vendor · IT on-call +36 96 555 0142
- Last delivery
- Mon 22:10
- MES work-order feedSQL · read onlyLimited3 rows waiting · part PN-0805-4K7 is not in Parts
Details
The rows apply once the part is imported and they are approved. Import parts
Technical details
- Source
- mes-sql01 / MES_PROD · new rows every 60 s, by cursor
- Version
- On · version 3
- Last run
- 14:31 · 41 rows recorded today
- Owner
- Danutek IT · MES team
- SAP S/4 goods receiptHTTPWorkingLast delivery 14:31 · 1 184 delivered today
Technical details
- Request
- POST https://sap-gw.danutek.local/sap/opu/odata/…/GoodsMovement
- Version
- On · version 4
- Automation
- Put-ins to SAP
- Owner
- Danutek IT · SAP team
- MES item lookupSQL · read onlyWorkingAt scan time · 1 miss today at 11:58
Details
Operators see the MES values marked “(from MES)”. When it doesn’t answer, the station says “MES did not answer; using label data.” and nothing waits.
Technical details
- Scope
- Put in · rack intake stations SMT-1, SMT-2
- Answers within
- 1.5 s · a policy value
- Version
- On · version 2
- Last miss
- 11:58: 2 reels got Enrichment pending
- Owner
- Danutek IT · MES team
- IMS ReelSaveInpredecessor-compatibleOffNot testedPOST https://<ims-host>:9443/api/rackservice/Service
Never runfrom preset · offNo owner yet
Before it can be onAddress · placeholderOwner · not namedTest · not runParts · imported
How data flows
Sent outan automation turns a recorded movement into a delivery
Taken ineach request is recorded or refused