durable operation2–3 hr5 stages8 code languages

Operating journey: Run a safe, punctual airport turnaround

More predictable departures with safer vehicle movement and attributable hand-offs across airport and airline teams.

The real-world moment

A delayed inbound aircraft changes stand while fuel, catering, baggage and inspection teams are already moving. The airport must publish the current approved airside network, re-plan one versioned turnaround, prevent vehicles entering restricted or closed areas, preserve each milestone hand-off, and avoid declaring departure-ready until airline, airport and safety authorities agree.

Operating contract

Make ownership visible before code.

Operate the full lifecycle with versioned state, hostile-path recovery, audit, and release evidence.

Application state: stateful
Planning calls: 0
Credentials accepted: No
Write authority: None

Capability map

directGIS & Analyticshybrid directInTouch Telematicsstateful directWorkmatestateful directMapsstateless entitlement-dependentCapture & Feedbackhybrid

Normalized operation coverage

An adjacent API is never substituted when the captured corpus has no exact contract.

GIS & Analytics0 exact · reference onlyNo exact normalized REST operation is present in the captured contract corpus for this product. Use its source guides, SDK/widget/distribution surface, and entitlement process without substituting an adjacent API.InTouch Telematics53 exact · normalized contractsExact normalized operations are linked below; account contract and entitlement still require validation.Workmate13 exact · normalized contractsExact normalized operations are linked below; account contract and entitlement still require validation.Maps3 exact · normalized contractsExact normalized operations are linked below; account contract and entitlement still require validation.Capture & Feedback0 exact · reference onlyNo exact normalized REST operation is present in the captured contract corpus for this product. Use its source guides, SDK/widget/distribution surface, and entitlement process without substituting an adjacent API.

Airport operational authority

Publish the approved airside network and restricted zones

Airport and airline systems own stands, movement permissions, flight milestones, safety zones, people, equipment and departure decisions; Mappls-derived experiences do not grant aviation or airside authority.

Supporting operation

Airside layer ↔ authority, version, effective window, sensitivity and closure state

GETStill Map Image API/{REST_KEY}/still_imageThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.

Evidence to retain

Record stage 1 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Failure drillStand changes after teams accept tasks

Create a new turnaround revision, invalidate incompatible assignments and corridor evidence, and require explicit reacceptance rather than mutating in place.

Versioned spatial operating picture

Create one versioned turnaround plan

Governed enterprise layers publish stands, service roads, closures, restricted zones and emergency access with source, steward, CRS, sensitivity and effective window.

Supporting operation

Turnaround ↔ flight/stand references, milestone graph, version and accountable coordinator

POSTTraveled Route Image API/{REST_KEY}/still_image_polylineThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.

Evidence to retain

Record stage 2 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Failure drillA vehicle appears outside its approved corridor

Preserve accuracy and network version, alert operations, stop affected automation and require safety review; never infer culpability from a point alone.

Turnaround aggregate

Track eligible vehicles and milestone hand-offs

One application-owned plan versions stand, tasks, dependencies, target milestones, responsible organizations and changes after disruption.

Stage operation

Task ↔ organization, eligibility, equipment, zone policy and evidence

GETGets the historical location events of a device./device/{deviceId}/eventsThis normalized operation matches the stage intent and remains subject to its source, lifecycle, authentication, entitlement, host, and regional gates.

Evidence to retain

Record stage 3 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Failure drillOne supplier reports complete while another dependency is open

Keep the supplier milestone complete but departure readiness blocked, showing the exact dependency and responsible authority.

Ground-team execution

Capture inspection and exception evidence

Workmate tasks and bounded vehicle observations track accepted assignments, corridor adherence, evidence, pauses and exceptions with offline-safe command identity.

Stage operation

Vehicle event ↔ device/assignment identity, event/receipt time and approved-network version

GETTo get the form's Id and their details from your account./configurations/formsThis normalized operation matches the stage intent and remains subject to its source, lifecycle, authentication, entitlement, host, and regional gates.

Evidence to retain

Record stage 4 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Failure drillStand changes after teams accept tasks

Create a new turnaround revision, invalidate incompatible assignments and corridor evidence, and require explicit reacceptance rather than mutating in place.

Readiness reconciliation

Reconcile departure readiness across authorities

Every required authority submits attributable milestone evidence; the coordinator derives readiness but never overwrites an authority's source record.

Supporting operation

Readiness ↔ required authority decisions, unresolved exceptions and final revision

GETTo get the form's Id and their details from your account./configurations/formsThis is a supporting operation from the selected product stack, not proof of an exact provider contract for this stage. Resolve the stage through its product source or adapter boundary before live implementation.

Evidence to retain

Record stage 5 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.

Failure drillA vehicle appears outside its approved corridor

Preserve accuracy and network version, alert operations, stop affected automation and require safety review; never infer culpability from a point alone.

Interactive contract lab

Edit once. Generate eight trusted-runtime implementations.

The recipe starts from the normalized GET /alarm/alarmLog/ contract. Execute six deterministic fixture outcomes before an issued account is involved.

Local request composerCode stays local · fixtures are explicit

GETRequest inputs

4 editable · 0 protected

deviceIdqueryNot Mandatory field. This is the ID of the device for which the alarm log need to be fetched. You can pass single device ID or multiple device IDs separated by commaalarmTypequeryNot Mandatory field. This is the type of alarm for which the alarm log need to be fetched. You can pass single alarm type or multiple device IDs separated by comma. Type of alarm to create. Following are the alarm types & their corresponding IDs. IGNITION: 21, OVERSPEED: 22, UNPLUGGED: 23, PANIC: 24, GEOFENCE: 26, STOPPAGE: 27, IDLE: 28, TOWING: 29, GPRS CONNECTIVITY: 126, VEHICLE BATTERY: 129, MILEAGE: 133, GPS CONNECTIVITY: 146, DISTANCE COVERED: 151, INTERNAL BATTERY VOLTAGE:161startTimerequiredqueryMandatory field. This is start timestamp in secondsendTimerequiredqueryMandatory field. This is end timestamp in seconds

Generated in eight languages

Environment-backed credentials

GET

https://intouch.mapmyindia.com/iot/api/alarm/alarmLog/?deviceId=1909%2C2545&alarmType=21%2C26&startTime=1700000000000&endTime=1700000000000

Credential-free sandboxExecute this contract without a provider call

How fixtures work

Generated from your inputs

curl --request GET \
  --url 'https://intouch.mapmyindia.com/iot/api/alarm/alarmLog/?deviceId=1909%2C2545&alarmType=21%2C26&startTime=1700000000000&endTime=1700000000000' \
  --header "Accept: application/json" \
  --header "Authorization: Bearer ${MAPPLS_INTOUCH_TOKEN}"

Credential-safe by constructionSet MAPPLS_INTOUCH_TOKEN only in your trusted runtime. Code generation stays local. Sandbox execution sends only bounded fixture inputs to this developer platform and never reads a credential or calls Mappls.

Reliability contract

Break the journey before customers do.

These controls are required at this operating depth; deeper recipes add durable truth rather than merely more API calls.

Idempotent commandsOptimistic aggregate versionsEvent and receipt timeTransactional outboxUnknown-outcome reconciliationIndependent human decisionsRestart recoveryImmutable audit evidence

Definition of done

Every aggregate has an invariant, expected version, stable command identity, and attributable actor.

Duplicate, late, reordered, invalid, stale, timed-out, and restarted execution preserve one durable truth.

Unknown provider outcomes reconcile by original identity before replay or compensation.

Terminal decisions, human review, audit, outbox delivery, privacy, retention, and rollback remain independently evidenced.

Continue with canonical evidence

Contracts, tutorials, and journeys stay linked.

Maintained capstone

Airside Turnaround Desk

Coordinate a revision-safe aircraft turnaround, pause for airside exceptions, preserve four service milestones, and require independent airline, airport, and safety readiness decisions.

Inspect 22 verified tests Download full application

Source-grounded, not authority-granting

This recipe composes source-derived contracts, application architecture, fixtures, and maintained learning evidence. It does not prove package availability, provider payload shape, account entitlement, regional behavior, production compatibility, or release approval.

Make ownership visible before code.

Edit once. Generate eight trusted-runtime implementations.

Break the journey before customers do.

Definition of done

Contracts, tutorials, and journeys stay linked.

Contract set

Progressive tutorials

Durable state machines

Airside Turnaround Desk