Ours, at the centre. It carries one work order out to the owner's system and its status back.
The Interchange. Headless capture of poc/index.html?v=interchange&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.
The Interchange between the platform and the owner
The Interchange is the developed component in the middle. The platform side feeds it. It carries work to the owner's systems of record on the far side and brings status back. The owner's systems stay the systems of record.
One work order leaves the twin for i3 and its status comes back. The twin drafts the request, a person confirms it, it goes to i3, which keeps it, and the status comes back (sheet A-05).
There are four flows. The Interchange updates the asset record and opens a linked Jira issue. A person approves the issue and the work order goes to i3. i3 reports back and Jira records the result. A person accepts, and Jira never closes itself.
It is built and tested on fixtures: 81 tests, 81 pass at the time this site was built. No real Jira and no real i3 has been called, but we will be ready. The Simplify i3 interface is to be confirmed with the Authority (Q-35).
Every hop writes an evidence line with the flow, the step and the attempt. The contracts, mappings, templates, adapters, source and tests are all listed on this site with their files.
Components for The Interchange
17 components on this site relate to this explainer: 6 document, 4 interchange contract, 3 code and tests, 4 screen. The best 6 are shown.
Picture: Headless capture of poc/index.html?v=wo&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.
Picture: Headless capture of poc/index.html?v=workflows&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale. Clip: Capture of poc/index.html?v=workflows&m=light, 4 seconds of the screen as it runs, 10 frames a second. No sound.
The Interchange is ours. Jira, off the shelf and used by most teams, feeds it from the platform side, and it carries work to the owner's systems on the other.