In aviation, we need to do month FMS database uploads.
They come out every 28 days :
In MXI, to set up a task to track it like this, will need a different REQ for each month.
That takes a long time to manage the fleet to put a new task for every month to be able to track the FMS Database with the correct release dates and due dates.
How do other airlines who use MXI set up their FMS cycles per month?
We use One Requirement, 672 CHR, (672/ 24hours = 28days)
Set the schedule to plan high and low at 9999, this keeps the scheduling at 28days
Minor issues
-For some reason the due date creeps forward 1 min every incorp.
-Need an ADHOC or on-condition version should you need to call a cycle out of sync (chart errors)
-Ground events beyond 28 days may need to acquit twice or more.
Set the threshold at 660 to get due time of 12:00 UTC or CUSTOM start.
Our dates are set to have the AC loaded 12 hours before the effective date per the honeywell schedule
+10We use an executable requirement, same task, with more generic language related to the software part number, with a 28 day recurring schedule.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
