How it works

Wire it with your team, then search the log

The log keeps every message in the order it was sent, so you can follow one order across several systems in the sequence it moved. Search narrows that same log by system, event type or order number.

  • Cordyn ERP event: In Production order 11:08 480 units

Integration events

See every exchange in one log

Every message between the Singularity and a source system lands in one place, in the order it was sent. Each entry carries its system and its type, so you never guess where a record came from. The log is scoped to the site you’re looking at.

  • One entry per message, with its system and its type
  • Newest first, or ordered by the time it was sent
  • Scoped to the site you are looking at

Event search

Find the message you need

Search the log by system, by event type or by the order number the message carried. Sort the results by the time each message was sent. Follow one order across several systems in the sequence it moved.

  • Search by system, event type, or reference
  • Sort by the time the message was sent
  • Follow one order across several systems in sequence
  • Production order EVT-77455Cordyn ERP, 613 B

Event detail

Read what was actually sent

Open an event and the detail drawer shows the message body exactly as it was sent, field by field, with the system, event type and time on the same panel. That’s usually enough to settle a question with the system owner.

  • The whole message body, every field it carried
  • System, event type, and time sent on the same panel
  • Enough detail to settle a question with the system owner
  • Orders received 9
  • Exception: order not received

Inbound orders

Let orders arrive on their own

Your ERP pushes production order changes in as they happen, and maintenance and repair orders sync on their own run. Nobody keys either one in by hand. If a message doesn’t land, a sales order exception is raised so a wrong number gets caught.

  • Production order changes arrive from the ERP as events
  • Maintenance and repair orders sync with the ERP
  • Sales order exceptions are raised when a message does not land
  • Go live checklist Session handshake Tag map validation Signal dictionary Pilot run

Connection go live

Set up each connection with your team

Adding or changing a connection is implementation work, built in code and configuration, and mode40 does it with you. There’s no catalogue to browse and no self-serve screen. A new system is added the same way, as scoped work.

  • Connections are built in code and configuration during implementation
  • No catalogue to browse and no self-serve setup
  • A new system is added the same way, as scoped work
  • Retired code 41-9042X sent
  • EVT-77461, sales orderitem_code: 41-9042X

Exception triage

Settle a bad number with the log

When a number looks wrong downstream, the log says whether the message arrived, when, and what it carried. Show the system owner exactly what was sent before anyone rebuilds the number by hand. The log records what happened. It doesn’t re-send anything.

  • Confirm a message arrived before anyone rebuilds the number
  • Show the system owner exactly what was sent, field by field
  • The log records what happened. It does not re-send anything.

What an IT lead sees when a number needs checking

    • Cordyn ERP, since 06:00 Production order Cordyn ERP Logged Sales order Cordyn ERP Logged Maintenance sync Cordyn ERP Waiting
    • Site: Brantford Plant 2

    Every message lands in one searchable log.

    Each entry carries its own system and event type, in the order it was sent. Search by system, event type, or the order number it carried.

    Search the event log
    • Production order EVT-77480Cordyn ERP, sent 06:14:02
    • Fields carried: order_no qty due_date Logged

    Open one event and read the whole message.

    The detail drawer shows the message body field by field, exactly as it was sent. System, event type, and time sent all sit on the same panel.

    Open the detail drawer

FAQ

Bring the system that's still a black box.

30 minutes on your systems and the log the Integration Hub keeps of every message.