Emergency response flow - recalibrate phase

This is the first step in the emergency response. To ensure urgent activities are assigned to the most appropriate resources, the system updates technician schedules based on real-time data.

Choose execution mode

In your optimization model, use the Simulated Recalibrated parameter to choose between two modes and control the behavior:

Mode	Priority	Locking Logic	Integrity Check
Simulation	Flexibility	No resources are locked during calculation.	To ensure there were no manual changes during the process, there is a final check before assignment.
Non-Simulation	Data consistency	All identified resources are locked immediately.	Resources are locked until the assignment is complete. No manual operations can be performed.

Understand field technicians exclusion logic

To filter out unavailable or irrelevant technicians, the system performs these checks on technicians:

Shift and unavailability: These controls are based on Model and Company parameters.
- Shift start: They are included only if the time until shift start is less than the Max time interval before shift start.
- Unavailability: They are included only if the time until unavailability ends is less than the Max time interval before shift start.
- Shift end: They are excluded if the shift time left is less than the Min time interval before shift end.
Maximum distance from start point: They are excluded if the activities too far, in linear distance, from their daily start point.
Offline and synchronization: They are excluded if they haven't synced within the Max time interval since last feedback.
- Set to -1 to disable.
Skill: They are excluded if they don’t have the required skills for the activities.
- This control is not configurable.
Clock-in (Stamping): They are excluded if they are not on shift based on their individual clocking management settings.
- This control is based on a Resource Configuration.
Crew shell: They are excluded if they are part of a crew shell for the day.
- The crew shell control is not configurable.
Scheduling checks: They are excluded if they are working in a team or assigned to multi-day activities.
- The scheduling checks control is not configurable.

Note: In the processing archive, the excluded field technicians and the reason they were excluded are logged in automatically

Recalibrate core logic

The system follows five core principles to maintain schedule continuity and accuracy.

Activity prioritization

Activities are ordered based on current markers or sequences, such as:

In-execution: Activities marked In Charge or Under Execution are moved to the first slot of the day.
Prefix sequences: Pre-ordered sequences for other activities are respected.
Scheduling slots: Appointment slots or non-schedulable blocks are ignored if they are in the past or involve active tasks.

Start displacement point (departure location)

To determine a technician’s location and travel time, the system checks:

In execution: The location of the current activity.
GPS: The technician's last known GPS coordinates.
Completed work: The coordinates of the intervention that just ended.
Active unavailability: The location of a finishing unavailability (if coordinates exist).
Fallback: The predefined start point for the day, resource, or team.

Start time and availability

The system determines a technician’s availability to work based on the following:

Active tasks: The start time matches the current activity start.
Temporal hierarchy: The latest data from GPS or the end time of a finished task.
Unavailability: The scheduled end time of the current unavailability.
Workday context: The official calendar start time if the day hasn't begun.
Fallback: The current time plus a configurable Restart Time Interval.

Activity duration

The system determines how long an activity will take based on:

Source of truth: The system uses durations declared by the technician via the mobile app rather than standard estimates.
Overdue activities: If an activity is open past its planned end time, the duration is extended to Now + a default duration.

Unavailability and breaks

The system determines when technicians are unavailable based on:

Unavailability: Time windows are reduced if an unavailability is in progress at the start or end of the day.
- Note: Future unavailable times are treated as specific slots.
Lunch breaks: The system tracks if a break is complete, in progress, or needs planning.
- Note: If a break's end time passes while in progress, a default duration is added to the current time.

What’s next?

SeeEmergency response flow - assignment of response activities.