Geometric requirements Sample Clauses

Geometric requirements. As paragraphs 5.3.3.1.1. and 5.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Geometric requirements. The brake discs or drums shall be identical to the original brake disc or drum in respect to all dimensions, geometric features, tolerances and basic design."
Sample 1Sample 2
Geometric requirements. The brake discs or drums shall be identical to the original brake disc or drum in respect to all dimensions, geometric features and basic design. 5.3.3.1.1. For discs the following maximum values shall be met: M1, N1, O1, O2 M2, M3, N2, N3, O3, O4 Thickness variation 0.015 mm 0.030 xx Xxxxx thickness variation (for ventilated disc only) 1.5 mm 2.0 mm Lateral run-out friction surface 0.050 mm* 0.15 mm* Location bore variation H9 H9 "Top hat" parallelism 0.100 mm 0.100 mm Location face flatness 0.050 mm 0.050 mm Friction surface roughness** 3.2 µm 3.2 µm * n/a in the case of a floating disc. ** Ra-value according to ISO 1302:2002. 5.3.3.1.2. For drums the following maximum values shall be met: M1, N1, O1, O2 M2, M3, N2, N3, O3, O4 Radial run-out friction surface 0.050 mm 0.100 mm Location bore variation H9 H9 Ovality 0.040 mm 0.150 mm Location face flatness 0.050 mm 0.050 mm Friction surface roughness* 3.5 µm 3.5 µm * Ra-value according to ISO 1302:2002.
Sample 1
Geometric requirements. The brake discs or drums shall be identical to the original brake disc or drum in respect to all dimensions, geometric features and basic design. 5.3.3.1.1. For discs the following maximum values shall be met: X0, X0, X0, X0 X0, X0, X0, X0, O3, O4 Thickness variation 0.015 mm 0.030 xx Xxxxx thickness variation (for ventilated disc only) 1.5 mm 2.0 mm Lateral run-out friction surface 0.050 mm* 0.15 mm* Location bore variation H9 H9 "Top hat" parallelism 0.100 mm 0.100 mm Location face flatness 0.050 mm 0.050 mm Friction surface roughness** 3.2 µm 3.2 µm 5.3.3.1.2. For drums the following maximum values shall be met: X0, X0, X0, X0 X0, X0, X0, X0, O3, O4 Radial run-out friction surface 0.050 mm 0.100 mm Location bore variation H9 H9 Ovality 0.040 mm 0.150 mm Location face flatness 0.050 mm 0.050 mm Friction surface roughness* 3.5 µm 3.5 µm
Sample 1
Geometric requirements. As paragraphs 5.3.3.1.1. and 5.3.3.1.2. plus the same interface dimensions. An interchangeable replacement disc or drum may differ from the original part disc in design features such as: (a) Type and geometry of ventilation (for vented discs); (b) Integral or composite disc or drum; (c) Surface finish (e.g. holes, slots etc.).
Sample 1
Geometric requirements. Refer to the attached sketches for the geometric requirements (Drawing No. 2) of acoustical panels. 1. The standards overall dimensions of each acoustical panel is 5’-2” (height) x 4” (thickness) x 4’ (width). (Note: Bid price for standard dimension shall be offer per each acoustical panel). 2. Panel sizes may vary for special applications at the ends of the girders due to the variance in length of the girder. (Note: Bid price for special applications acoustical panel shall be offer per linear feet). 3. The spacing of the vertical posts supporting the acoustical panels shall be based on the spacing of the existing attachment holes in the guide way deck, as indicated in Section
Sample 1
Geometric requirements. The brake discs or drums shall be identical to the original brake disc or drum in respect to all dimensions, geometric features, tolerances and basic design[R90.02S3-35]. 5.3.3.1.1. For discs the following maximum values shall be met: X0, X0, X0, X0 X0, X0, X0, X0, O3, O4 L1, L2, L3, L4, L5 Thickness variation 0.015 mm 0.030 mm 0.020 xx Xxxxx thickness variation (for ventilated disc only) 1.5 mm 2.0 mm (****) Lateral run-out friction surface 0.050 mm* 0.15 mm* 0.150 mm*** Location bore variation H9 X0 X00 or H11 ***** "Top hat" parallelism 0.100 mm 0.100 mm --- Location face flatness 0.050 mm 0.050 mm 0.100 mm Friction surface roughness** 3.2 µm 3.2 µm 1.6 µm * n / a in the case of a floating disc ** Ra-value according to ISO 1302:2002. *** 0.100 mm for maximum straightness for "full floating" disc (without elastic constraints between xxxx and braking ring) **** n/a for vehicles categories L1, L2, L3, L4, L5 ***** Location bore variation where applicable, related to manufacturing process. 5.3.3.1.2. For drums the following maximum values shall be met: X0, X0, X0, X0 X0, X0, X0, X0, O3, O4 Radial run-out friction surface 0.050 mm 0.100 mm Location bore variation H9 H9 Ovality 0.040 mm 0.150 mm Location face flatness 0.050 mm 0.050 mm Friction surface roughness 3.5 µm 3.5 µm * Ra-value according to ISO 1302:2002
Sample 1
AutoNDA by SimpleDocs
Geometric requirements. As paragraphs 5.3.4.1.1 and 5.3.4.1.2 plus the same interface dimensions. An interchangeable replacement … 5.3.4.1.1. For discs, the following maximum values shall be met: X0, X0, X0, X0 X0, X0, X0, X0, O3, O4 Thickness variation 0.015 mm 0.030 mm 0.040 xx Xxxxx thickness variation (for ventilated disc only) 1.5 mm 2.0 mm 2.0 mm Lateral run-out friction surface 0.050 mm* 0.15 mm* 0.15 mm* Location bore variation H9 H9 H9 "Top hat" parallelism 0.100 mm 0.100 mm 0.100 mm Location face flatness 0.050 mm 0.050 mm 0.050 mm Friction surface roughness** 3.2 µm 3.2 µm 3.2 µm X0, X0, X0, X0 X0, X0, X0, X0, O3, O4
Sample 1

Related to Geometric requirements

  • Basic Requirements To be eligible for PayPal’s Seller Protection program, all of the following basic requirements must be met, as well as any applicable additional requirements: • The primary address for your PayPal account must be in the United States. • The item must be a physical, tangible good that can be shipped, except for items subject to the Intangible Goods Additional Requirements. Transactions involving items that you deliver in person in connection with payment made in your physical store, may also be eligible for PayPal’s Seller Protection program so long as the buyer paid for the transaction in person by using a PayPal goods and services QR code. • You must ship the item to the shipping address on the Transaction Details page in your PayPal account for the transaction. If you originally ship the item to the recipient’s shipping address on the Transaction Details page but the item is later redirected to a different address, you will not be eligible for PayPal’s Seller Protection program. We therefore recommend not using a shipping service that is arranged by the buyer, so that you will be able to provide valid proof of shipping and delivery. • The shipping requirement does not apply to eligible transactions involving items that you deliver in person; provided, however, that you agree to provide us with alternative evidence of delivery or such additional documentation or information relating to the transaction that we may request. • You must respond to PayPal’s requests for documentation and other information in a timely manner as requested in our email correspondence with you or in our correspondence with you through the Resolution Center. If you do not respond to PayPal’s request for documentation and other information in the time requested, you may not be eligible for PayPal’s Seller Protection program. • If the sale involves pre-ordered or made-to-order goods, you must ship within the timeframe you specified in the listing. Otherwise, it is recommended that you ship all items within 7 days after receipt of payment. • You provide us with valid proof of shipment or delivery. • The payment must be marked “eligible” or “partially eligible” in the case of Unauthorized Transaction claims, or “eligible” in the case of Item Not Received claims, for PayPal’s Seller Protection program on the Transaction Details page. • In the case of an Unauthorized Transaction claim, you must provide valid proof of shipment or proof of delivery that demonstrates that the item was shipped or provided to the buyer no later than two days after PayPal notified you of the dispute or reversal. For example, if PayPal notifies you of an Unauthorized Transaction claim on September 1, the valid proof of shipment must indicate that the item was shipped to the buyer no later than September 3 to be eligible for PayPal’s Seller Protection program. PayPal determines, in its sole discretion, whether your claim is eligible for PayPal’s Seller Protection program. PayPal will make a decision, in its sole discretion, based on the eligibility requirements, any information or documentation provided during the resolution process, or any other information PayPal deems relevant and appropriate under the circumstances. To be eligible for PayPal’s Seller Protection program for a buyer’s Item Not Received claim, you must meet both the basic requirements and the additional requirements listed below: • Where a buyer files a chargeback with the issuer for a card-funded transaction, the payment must be marked “eligible” for PayPal’s Seller Protection on the Transaction Details page. • You must provide proof of delivery as described below.

  • Specific Requirements compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • Health Requirements A. Provider shall remain in compliance with all applicable federal, state, county, and municipal, statutes, laws, ordinances, regulations, and guidelines, as well as any Board guidelines, policies, and rules in effect now or later, and as amended from time to time related to COVID-19. B. Provider shall comply with evolving requirements to protect the health and safety of Student Participants and staff, as expressed in local, and state guidance from various government agencies. This includes, but is not limited to, adhering to all health and safety guidelines issued by CPS, IDPH, and CDPH related to COVID-19. Provider acknowledges these health and safety guidelines are subject to change. C. Required health and safety practices may vary across age groups and settings. Provider shall comply, at a minimum, with all health and safety mandates issued by the State of Illinois and the City of Chicago and guidance from the Illinois State Board of Education (“ISBE”). D. Under Chicago’s March 19 Public Health Order, congregate facilities (such as long-term care facilities, childcare settings, correctional facilities, etc.) must immediately report to CDPH clusters of COVID-19 patients, defined as two or more confirmed cases of COVID-19 occurring within 14 calendar days of each other at a facility. To report positive cases, Provider must complete the COVID-19 Online Case Report Form found at the following website: xxxxx://xxxxxx.xxx.xxxxxxxx.xxx/surveys/?s=FR7MAJAY84. A copy of the current COVID-19 Online Case Report Form is attached and incorporated into this Supplemental Scope as Attachment A. Provider must also comply with additional operational, reporting and tracing requirements established by CPS. E. As of July 13, 2020, interim guidance issued by CDPH encourages notification for every COVID-19 case. For more information, see CDPH Interim Guidance on Management of COVID 19 Cases in Childcare Settings (“CDPH Guidance”) at the following link: https://xxx.xxxxxxx.xxx/content/dam/city/depts/cdph/HealthProtectionandResponse/Interim% 20Guidance%20on%20Management%20of%20COVID 19%20Cases%20in%20Childcare%20Settings%2007.13.

  • Network Requirements Customer shall be responsible for ensuring that all aspects of the applicable network environment(s) adhere to the applicable standards and requirements specified in the Documentation and are configured appropriately to its proposed use of Ordered SaaS Services.

  • Screening Requirements Practitioner shall ensure that all prospective and current Covered Persons are not Ineligible Persons, by implementing the following screening requirements. a. Practitioner shall screen all prospective Covered Persons against the Exclusion List prior to engaging their services and, as part of the hiring or contracting process, shall require such Covered Persons to disclose whether they are Ineligible Persons.‌ b. Practitioner shall screen all current Covered Persons against the Exclusion List within 30 days after the Effective Date and on a monthly basis thereafter.‌ c. Practitioner shall require all Covered Persons to disclose immediately if they become an Ineligible Person.‌ Practitioner shall maintain documentation in order to demonstrate that Practitioner: (1) has checked the Exclusion List (i.e., a print screen of the search results) and determined that its Covered Persons are not Ineligible Persons; and (2) has required its Covered Persons to disclose if they are an Ineligible Person. Nothing in this Section III.D affects Practitioner’s responsibility to refrain from (and liability for) billing Federal health care programs for items or services furnished, ordered, or prescribed by an excluded person. Practitioner understands that items or services furnished by excluded persons are not payable by Federal health care programs and that Practitioner may be liable for overpayments and/or criminal, civil, and administrative sanctions for employing or contracting with an excluded person regardless of whether Practitioner meets the requirements of Section III.D.

  • Data Requirements ‌ • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.

  • Interface Requirements 2.4.5.1 The NID shall be equal to or better than all of the requirements for NIDs set forth in the applicable industry standard technical references.

  • Compliance Requirements A. Nondiscrimination. The Contractor agrees to comply, and to require its subcontractor(s) to comply, with the nondiscrimination provisions of MCL 37.2209. The Contractor further agrees to comply with the provisions of Section 9:158 of Chapter 112 of the Xxx Arbor City Code and to assure that applicants are employed and that employees are treated during employment in a manner which provides equal employment opportunity.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!