Section 5
The Interchange The developed Interchange between the platform side and the owner's systems of record: its documents, adapters, contracts, mappings, source and tests.
17 pages in this section. Select a document or adapter for its full text and files.
Level 1 of 3 This section, complete on its own. Each page below is a component with its own data and sources. Open the components
Groups
Documents 6
No. Page What it holds 5.2 Architecture How each local part maps to its cloud design. 5.3 The Jira side of the Interchange The Jira side of the Interchange: Jira and Jira Service Management Assets as the Interchange's primary hub inside the design, the flows both ways and the state of each part. 5.4 The AI hook Where a model judgement enters the Interchange and how a person confirms it. 5.5 Document rules How the Collector reads a document and what each kind becomes. 5.6 Overview What the Interchange and the Collector are and how to run them. 5.7 Setup What each connection needs before it can run live.
Adapters 4
No. Page What it holds 5.8 Alert channels adapter The interface for sending an alert to a channel, and the stub that stands in for one. 5.9 ETL adapters Adapters for Allen-Bradley controllers, building management systems and i3 records, with a template for the next one. 5.10 Jira adapter The Jira side of the Interchange: client, Assets, issues, credentials and the fixture site. 5.11 Simplify i3 adapter The boundary to Simplify i3, the system the RFP names. The interface is to be confirmed (Q-35).
Contracts 1
No. Page What it holds 5.12 Contracts 22 contracts and 5 mapping schemas, each a JSON schema.
Mappings 2
No. Page What it holds 5.13 Mappings 5 mappings held as data: catalogue, events, rules, tags, types. 5.14 Templates 6 record templates: asset, contact_role, maintenance_policy, room, sensor_point, work_order.
Code 3
No. Page What it holds 5.15 Source modules 25 source modules in the Collector and the Interchange. 5.16 Tests 81 tests in 12 files. 81 pass at the time this site was built. 5.17 Demo runs 5 runs that print each stage and write one evidence line per stage.