Airport Operations Plan (AOP)

Ground operations

Target Off-Blocks Time (TOBT) must be updated to an accuracy of +/- 5 minutes. If your TOBT is changing please take a minute to think through the reason the time is changing and decide on a new time that is realistic. Late, small, and repeated incremental changes are to be avoided as this creeping delay creates a phantom requirement for a runway place. Please find below some key points

• If you are ready to go with less than 10 minutes left before your TOBT it is recommended that you do NOT update your time – you may still call 5 minutes before your TOBT.
• If you know that you will be unable to achieve your TOBT you should enter a new, realistic TOBT as soon as possible. Remember you have the 5 minute window before and after your TOBT – if you will exceed that window, update with a new, later TOBT: this will free up your theoretical runway slot for another movement and allow the system additional time to search for an optimal runway slot for your new TOBT.
• Never update a TOBT with a time in the past - this causes great system instability.

Flight Operations

Estimated Off-Blocks Time (EOBT) must be aligned to within +/-10 minutes of the TOBT.

Crew

Pilots should call Delivery at TOBT +/-5 minutes. If they become aware of any reason why they may be unable to meet the TOBT (+/- 5 mins) they should advise the ground handler and provide a new, realistic TOBT.

Need access to AOP?

Colleagues employed directly by Heathrow can request an AOP account through the TechHelp portal on HUB+.

TeamHeathrow colleagues who are not employed directly by Heathrow should use the following process. Please ensure you read and follow the instructions carefully.

1. Register your email address with Heathrow Digital Identity – if you already have access to the Airport Community App and/or other Heathrow systems, you may be able to skip this step.
2. Once HDI registration is completed and confirmed, then request access to AOP. Please ensure you list your organisation and your specific job role in the ‘Justification’ field. Generic responses such as ‘Needed for Job Role’ or ‘Operational Reasons’ will cause your request to be rejected.
3. The Aircraft Operations Duty Manager Team will review and approve the request electronically. You will receive an approval notification. This may take up to 48 hours depending on operational requirements.
4. You now have access to AOP and can access it at MyApps.Microsoft.com by selecting the AOP icon. Alternatively, you can use this link.
5. If you need access to the De-Icing Interface, Passenger or Freight Data (restricted to your airline or those you are contracted to) you will need to email AOP@heathrow.com after your account is created and you are able to log in. These requests are manual and can take up to a week to action; where possible please consolidate the request with other colleagues who require the same information.
6. Please note that AOP accounts need to be re-validated every 90 days. You will receive an email from Microsoft Azure/HDI and must confirm your continued need for access to AOP – this is a mandatory cyber security requirement, and failure to respond will result in your account being deleted. If your account is deleted, you will need to raise a new request as in Step 2.  
7. If you also need access to the AOP Situational Awareness Map, you will need to call the Heathrow IT Service Desk (02087455355) after your AOP account is created and you have logged in for the first time. Please ask them to use the ‘All Heathrow Maps’ form and grant you access to ‘AOP Map Live’ – this will be reviewed and approved and you will receive a separate username and password for the Map. If asked for a Heathrow Department, please list ‘APOC’ and for a Heathrow Line Manager, please list Diogene DeSouza.

Note: Heathrow Digital Identity is used to grant access to HAL IT applications for external stakeholders. For example, it is used for access to the Heathrow Airport Community app. If you are already registered with HDI you can skip the first step and go directly to Step 2.