Level 2 of 3 This component, complete on its own. Its files, sources and tests are the detail below. Open the detail
Simplify i3 adapter: the boundary only
Simplify i3's interface is not public. The plan carries it as an open question (Q-35). This folder holds the edge the hub calls and the contract tests for it. It names no i3 endpoint, field or status as fact.
What is known
From the RFP's requirements (sanford-twin/staging/e2-sanford/requirements.md, REQ-SFB-006, 007, 008 and 045):
Simplify i3 is the Authority's work order, safety management, inspection and partial asset management system, in the cloud. It is read first.
It holds asset records and hierarchies, locations, work requests and work orders, preventive and corrective maintenance, inspections, history, labour, condition, availability and documents.
A work request raised in the twin goes to i3 through its own interface, after a person confirms it.
The owner's systems stay the systems of record.
The research reads i3 as built on Esri (sanford-twin/docs/research/sfb-it-landscape-2026-10-30.md).
What is not known
the interface: API, webhook, file exchange or Esri feature service
every field and status name
how i3 would send events
whether it keeps an outside reference such as a Jira key
fields.json lists each Interchange field with its i3 counterpart as to_confirm.
Transports
Transport
Does
unknown (default)
Every call fails with I3InterfaceUnknown, naming Q-35. The hub parks the message with that error.
simulated
A stand-in kept in the Collector's data folder, for tests and the demo. Every answer is labelled simulated.
What is needed
The vendor's interface documents for Simplify i3, through the Authority. A transport is then written against them, and fields.json filled in, row by row.