When an external platform or customer portal queries the engine for open appointments, incoming unstructured request attributes must be mapped to operational calendars. This section describes the validation rules, parameters, and deductive processes used to filter the scheduling grid.
Inbound Search Parameters
The system evaluates availability arrays by matching the unique dimensions of each appointment request against active grid simulations until available capacity is fully consumed. Inbound requests must supply the following parameters:
-
Requested Activity Type: The specific class of order or field activity to be performed (maps directly to the system Work Order Type).
-
Address / Supply Address: The physical location where the task will take place (typically linked to a unique point of delivery/service identifier, like a PDR).
-
Service Expiration Date (SED): The hard business deadline set by external ordering systems based on commercial guarantees.
Deductive Sub-Zone Resolution Workflow
To map coordinates to a localized calendar, the slot discovery engine executes three internal steps:
-
Work Order & Capability Mapping: The requested Work Order (WO) Type identifies the correct active scheduling grid and simulation schema. This evaluation automatically determines the First Date Cut-off parameters, rescheduling/cancellation window restrictions, Over1/Over2 availability spans, standard work cycles, execution timeframes, and required team sizes.
-
Geographic Resolution via Coordinates: The physical address is geocoded using internal calls to Google Services to extract spatial coordinates. The platform uses these coordinates to pinpoint the corresponding Micro-Cluster (MC) and map the request to a specific corporate Zone and Sub-zone.
-
Calendar Extraction: Using the resolved Sub-zone context, the engine isolates the correct calendar configuration along with its associated
ORD,OV1, andOV2availability balances.
Based on these details, the booking engine runs a slot saturation analysis to find and suggest the first available slot for that sub-zone relative to the requested date.
System Behavior: Once a specific slot is chosen and a temporary appointment is reserved, the core engine automatically generates an accompanying Work Order in an OPEN status.