Higher productive haulage with fewer route conflicts, stale-map movements, and unexplained cycle losses.
A blast changes the active pit and closes a ramp midway through a shift. Dispatch must publish the newly approved road and exclusion-zone version, reassign compatible trucks and loaders, guide offline-capable cycles, distinguish telemetry delay from a stopped vehicle, preserve safety interventions, and reconcile production only from accepted load and dump evidence.
Compose multiple capabilities while the application owns user intent, policy, and continuity.
The mine system of record owns surveyed geometry, blast areas, geotechnical restrictions, road classes, equipment compatibility and operating authorization.
Mine map package ↔ survey/version, region, signature, compatibility and approval
GETGets The List Of Alarm Config(s)/alarm/alarmLog/This 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.Record stage 1 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Block the changed operating zone, retain the compatible prior slot for recovery, and require a qualified signed update before dispatch.
Approved pit, road, zone and configuration manifests move through signed dual-slot qualification and rollback before vehicles activate them.
Assignment ↔ equipment/operator capability, shift, plan version and expected aggregate version
GETTo get the list of tasks and their details/tasksThis 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.Record stage 2 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Separate freshness from motion state, show last verified evidence, and ask dispatch to reconcile rather than charging productive-time loss automatically.
Application state owns shift, equipment/operator assignments, load/dump targets, priorities, expected versions and deliberate cancellation.
Cycle event ↔ source/content identity, event/receipt time, map version and stage
GETTo get the list of tasks and their details/tasksThis 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.Record stage 3 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Deduplicate by source/content and cycle identity, reject conflicting replays, and reconcile against the authoritative scale record.
InTouch observations and offline commands derive travel, queue, load and dump stages by event time while keeping raw source identity and freshness.
Safety exception ↔ zone/rule version, accuracy, intervention and reviewer decision
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.Record stage 4 with the application identity, source fingerprint, request or aggregate identity, timestamp, and observable outcome.
Block the changed operating zone, retain the compatible prior slot for recovery, and require a qualified signed update before dispatch.
The recipe starts from the normalized GET /alarm/alarmLog/ contract. Execute six deterministic fixture outcomes before an issued account is involved.
https://intouch.mapmyindia.com/iot/api/alarm/alarmLog/?deviceId=1909%2C2545&alarmType=21%2C26&startTime=1700000000000&endTime=1700000000000curl --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.
These controls are required at this operating depth; deeper recipes add durable truth rather than merely more API calls.
Every capability has one owner, bounded input, explicit timeout, and useful unavailable state.
Application intent survives refresh, back navigation, duplicate callbacks, and partial capability failure.
Provider identities, source fingerprints, request identities, and application decisions remain attributable.
Accessibility, privacy, quota, observability, support, and rollback evidence cover the complete user flow.
/alarm/alarmLog/GETTo get the list of tasks and their details/tasksGETThis API will get all the alarm configurations for a user./alarmGETTo get all your client details/clientsGETGets The List Of Alarm Config(s)/alarms/alarmlogs/GETTo get the list of client category in an account/configurations/categoriesGETThis API will get all the alarm configurations for a user./alarmsGETTo get the form's Id and their details from your account./configurations/formsCoordinate a revision-safe aircraft turnaround, pause for airside exceptions, preserve four service milestones, and require independent airline, airport, and safety readiness decisions.
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.