OPERATOR PROFILE Clause Samples

OPERATOR PROFILE. 1.1 The TCP® Hourly Rate is based on the Operator Profile declared by the Operator. Any modifications to the Operator Profile or changes in geographical or operating environment must be reported promptly to P&WC and may result in an adjustment to the TCP® Hourly Rate referenced in this Agreement. 1.2 The Operator Profile under this Agreement is for Engines used in the regional airline flight profile submitted by the Operator as indicated below and which are operated within the limitations specified in the applicable section of the aircraft flight manual. 1.3 The Fleet under this Agreement shall consist of 46 installed Engines and 0 spares as referenced in Annex “A”. 1.3.1 Annual utilization of each engine of 2,088 Engine Operating Hours + / - 5 %; 1.3.2 Annual average cycle ratio of 1.2 cycle/hour + / - 5 %; 1.3.3 Overhaul interval achieved at 24,000 cycles for gas generator and 15,000 cycles for power section Modules; 1.3.4 HSI interval achieved at 6,000 cycles for the hot section, interval subject to adjustment based on ECTM® and borescope inspections results; 1.3.5 Gas Generator midlife inspection achieved at 12,000 cycles 1.3.6 Power Section — midlife inspection achieved at 7,500 cycles 1.3.7 Fuel Nozzle Kit refurbishment interval achieved at 600 hours;
View SourceView Similar (2)
OPERATOR PROFILE. 1.1 The Hourly Rate is based on the Operator Profile declared by Customer. Any modifications to the Operator Profile or changes in geographical or operating environment must be reported promptly to P&WC and may result in an adjustment to the Hourly Rate referenced in this Agreement. 1.2 The Operator Profile under this Agreement is for Engines used in the regional airline flight profile submitted by Customer as indicated below and which are operated within the limitations specified in the applicable section of the aircraft flight manual. 1.3 The Fleet under this Agreement shall consist of 60 installed Engines and two (2) spares as referenced in Annex “A”.
View Source

Related to OPERATOR PROFILE

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If WCS chooses to subtend a Verizon access Tandem, WCS’s NPA/NXX must be assigned by WCS to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 WCS shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from WCS’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office WCS utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow WCS’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Wireless Operator Data In addition to Section 20 (Information Authorization) of the General Terms, you acknowledge that we or Zelle® may use information on file with your wireless operator to further verify your identity and to protect against or prevent actual or potential fraud or unauthorized use of the Service. By using the Zelle® Payment Service, you authorize your wireless operator (AT&T, Sprint, T-Mobile, US Cellular, Verizon, or any other branded wireless operator) to disclose your mobile number, name, address, email, network status, customer type, customer role, billing type, mobile device identifiers (IMSI and IMEI) and other subscriber status and device details, if available, to us or our Service Providers solely to allow verification of your identity and to compare information you have provided to us or to Zelle® with your wireless operator account profile information for the duration of our business relationship. See Zelle®’s Privacy Policy at ▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/privacy-policy for how it treats your data. Please review our Privacy Policy in order to better understand our commitment to maintaining your privacy, as well as our use and disclosure of your information.

  • Screening The Health Plan must work with contracted providers to conduct interperiodic EPSDT screens on RIte Care and all ACA Adult Expansion Population members under age 21 (i.e. 19 and 20-year old under this Agreement) to identify health and developmental problems in conformance with ATTACHMENT ED to this Agreement. Additional screens should be provided as Medically Necessary. At a minimum, these screens must include: • A comprehensive health and developmental history, including health education, nutrition assessment, immunization history, and developmental assessment • Immunizations according to the Rhode Island EPSDT Periodicity Schedule • An unclothed physical examination • Laboratory tests including lead, TB, and newborn screenings as medically indicated • Vision testing • Hearing testing • Dental screening oral examination by PCP as part of a comprehensive examination required before age one (1) • All other medically indicated screening services • And provide EOHHS with a list of established CPT/HCPC codes used to identify all billable services included in the EPSDT schedule.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.