AirfieldpathOrlando Sanford International

How it works · 5 of 6

Jira

Off the shelf, on the platform side, feeding the Interchange.

Sheet A-04, Off the shelf: Jira and Confluence on the platform side feeding the Interchange
Jira. Preview image of sheet A-04, the PNG the sheet build writes beside the PDF, centred on a white frame.
Jira is one source that feeds the Interchange
Jiraoff the shelf; work andstatusThe Interchangeours; maps, rules, evidenceThe owner's systems ofrecordi3, interface to confirm(Q-35)Jiraoff the shelf; work and statusThe Interchangeours; maps, rules, evidenceThe owner's systems of recordi3, interface to confirm (Q-35)

Jira is off the shelf and known by many teams, and its interfaces are easy to build on. On the platform side it holds the work and its status, and it feeds the Interchange. It is one source among the sources the Interchange reads. It is not the centre.

What flows: an event can open an issue linked to the asset; a person moves the issue to approved; the work order goes to i3; i3's result comes back as an event; a person accepts. Rules in a data file choose each step, and a disabled rule says why.

What is built: a credentials reader and a transport with not-configured, fixture and live modes. It also holds the JSM Assets schema and objects, and issues linked to assets. Webhooks come in and the flows run. Each is tested both ways on a fixture site that answers in Atlassian's published shapes.

State: built and tested on fixtures. No real Jira has been called. The live mode waits for a test project.

Components for Jira

9 components on this site relate to this explainer: 3 document, 2 interchange contract, 1 code and tests, 3 screen. The best 5 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.

Screen · Proof of concept · Maintenance

Work Orders

The repairs and inspections in hand, as the maintenance team sees them.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Screen
Status
partly met
Airport layer
Screens: the POC story and the spines
Airport area
not linked
System
not linked
Sensor type
not linked
SheetA-10

Open the screen · Open the detail

Picture: Headless capture of poc/index.html?v=interchange&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.

Screen · Proof of concept · Connect

Sanford Interchange

Every Authority system through one hub, each still the record of what it owns, with a work order going to Simplify i3 and its status coming back.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Screen
Status
not linked
Airport layer
Screens: the POC story and the spines
Airport area
not linked
System
not linked
Sensor type
not linked
SheetA-10

Open the screen · Open the detail

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.

Screen · Proof of concept · Prove

Workflows

How a fault becomes a repair: who is told and who approves it, and where the work is recorded.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Screen
Status
partly met, target
Airport layer
Screens: the POC story and the spines
Airport area
not linked
System
not linked
Sensor type
not linked
ScreensWorkflows

Open the screen · Open the detail

Picture: Preview image of sheet A-04, the PNG the sheet build writes beside the PDF, centred on a white frame.

Document · Documents · Sheets

A-04: Off the shelf

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.

  1. Sources
  2. Interchange
  3. Twin
  4. Screens
  5. Plan
Kind
Document
Status
not linked
Airport layer
not linked
Airport area
not linked
System
not linked
Sensor type
not linked
SheetA-04

Open the detail

See all 9 related components

All 9 related components by type

Document

Interchange contract

Code and tests

Screen

Where to see it

Screens

Sheets

Requirement rows that name these screens (19)

M-003M-011M-023M-062M-075

14 more rowsM-092M-097M-104M-111M-114M-127M-004M-009M-015M-089M-119M-121M-122M-131