Maintenance Execution supports UTC and local time zones for the server and sites. You can configure the server time zone and each site time zone independently, so timestamps are stored and displayed correctly for line and hangar maintenance operations across regions.
The server time zone is defined by the SERVER_TIME_ZONE in System Parameters page. Each site has its own time zone on the site record. When you connect a site to an airport, set the site time zone to match the local time zone of the maintenance location.
An airport can have a different time zone from its connected site. The airport time zone affects how dates and times are shown to users assigned to that airport.
Maintenance Execution displays dates and times in local time and Coordinated Universal Time (UTC) . Local time is usually shown in the time zone assigned to your airport.
When performing activities such as reviewing a turn, assigning resources, or deferring faults, line and hangar maintenance shows local date and time in the time zone assigned to your airport.
Where time appears in local time, you can click or hover over the time zone badge to see the date and time in UTC.
When viewing flights, the Flights and Planned Flights pages display date and time in the time zone assigned to the airport in the Arrival Airport and Departure Airport fields. You must enter departure and arrival dates in the time zone of the respective airport.
E-signature document pages (Task Card, Fault Deferral and Complete Work Package) display the dates and times in the server time zone.
When Maintenance Execution is integrated with CAMO, integration messages use UTC for date and time values. IFS Cloud converts incoming UTC values to the correct server or site time zone before storing them. When data is sent to CAMO, stored server or site values are converted to UTC in the outbound message.
This applies to workscope loading, task and work package completion, flight and work package updates, and supply chain messages such as material required dates.