FREQUENCY AND COVERAGE 3.1 All MI Reports must be completed by the Supplier using the MI Reporting Template and returned to the Authority on or prior to the Reporting Date every Month during the Framework Period and thereafter, until all transactions relating to Call Off Agreements have permanently ceased. 3.2 The MI Report should be used (among other things) to report Orders received and transactions occurring during the Month to which the MI Report relates, regardless of when the work was actually completed. For example, if an invoice is raised for October but the work was actually completed in September, the Supplier must report the invoice in October's MI Report and not September's. Each Order received by the Supplier must be reported only once when the Order is received. 3.3 The Supplier must return the MI Report for each Month even where there are no transactions to report in the relevant Month (a "Nil Return"). 3.4 The Supplier must inform the Authority of any errors or corrections to the Management Information: 3.4.1 in the next MI Report due immediately following discovery of the error by the Supplier; or 3.4.2 as a result of the Authority querying any data contained in an MI Report.
FREQUENCY AND CAPACITY LEVELS No restriction on frequency, capacity or aircraft types
Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).
Business Continuity Registry Operator shall maintain a business continuity plan, which will provide for the maintenance of Registry Services in the event of an extraordinary event beyond the control of the Registry Operator or business failure of Registry Operator, and may include the designation of a Registry Services continuity provider. If such plan includes the designation of a Registry Services continuity provider, Registry Operator shall provide the name and contact information for such Registry Services continuity provider to ICANN. In the case of an extraordinary event beyond the control of the Registry Operator where the Registry Operator cannot be contacted, Registry Operator consents that ICANN may contact the designated Registry Services continuity provider, if one exists. Registry Operator shall conduct Registry Services Continuity testing at least once per year.
Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following: