NDE test methods for production monitoring Sample Clauses

NDE test methods for production monitoring. In Hycomp it has been investigated the capability of a method for quality control by Acoustic Emission Testing (AT), designed and patented to be used in a simple and easily imple- mentable manner under normal production conditions. This methodology can be used for Type 3 cylinders as well as for Type 4 cylinders, which have not been pressurized before the procedure. The Acoustic Emission (AE) measurement can be performed during the autofret- tage process of Type 3 cylinders or the proof test of Type 4 cylinders. These tests are man- datory for every manufactured cylinder. Therefore the AE measurement can be performed without an additional effort of a further test procedure.
Sample 1
AutoNDA by SimpleDocs

Related to NDE test methods for production monitoring

  • Drug Testing (A) The state and the PBA agree to drug testing of employees in accordance with section 112.0455, F.S., the Drug-Free Workplace Act. (B) All classes covered by this Agreement are designated special risk classes for drug testing purposes. Special risk means employees who are required as a condition of employment to be certified under Chapter 633 or Chapter 943, F.S. (C) An employee shall have the right to grieve any disciplinary action taken under section 112.0455, the Drug-Free Workplace Act, subject to the limitations on the grievability of disciplinary actions in Article 10. If an employee is not disciplined but is denied a demotion, reassignment, or promotion as a result of a positive confirmed drug test, the employee shall have the right to grieve such action in accordance with Article 6.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Laboratory Testing All laboratories selected by UPS Freight for analyzing Controlled Substances Testing will be HHS certified.

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.

  • Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.

  • Performance Testing 7.2.1 The Design-Builder shall direct and supervise the tests and, if necessary, the retests of the Plant using Design-Builder’s supervisory personnel and the Air Emissions Tester shall conduct the air emissions test, in each case, in accordance with the testing procedures set forth in Exhibit A (the “Performance Tests”), to demonstrate, at a minimum, compliance with the Performance Guarantee Criteria. Owner is responsible for obtaining Air Emissions Tester and for ensuring Air Emissions Tester’s timely performance. Design-Builder shall cooperate with the Air Emissions Tester to facilitate performance of all air emissions tests. Design-Builder shall not be held responsible for the actions of Owner’s employees and third parties involved in the Performance Testing, including but not limited to Air Emissions Tester. 7.2.2 No later than thirty (30) Days prior to the earlier of the Scheduled Substantial Completion Date or Substantial Completion, Design-Builder shall provide to Owner for review a detailed testing plan for the Performance Tests (other than for air emissions). Owner and Design-Builder shall agree upon a testing plan that shall be consistent with the Performance Test Protocol contained in Exhibit A hereto. After such agreement has been reached, Design-Builder shall notify the Owner five (5) business days prior to the date Design-Builder intends to commence the Performance Tests and shall notify the Owner upon commencement of the Performance Tests. Owner and Independent Engineer each have the right to witness all testing, including the Performance Tests and any equipment testing, whether at the Site or at the Subcontractor’s or equipment supplier’s premises during the course of this Agreement. Notwithstanding the foregoing sentence, Owner shall bear the costs of providing a witness to any such testing and all such witnesses shall comply at all times with Design-Builder’s, Subcontractor’s or equipment supplier’s safety and security procedures and other reasonable requirements, and otherwise conduct themselves in a manner that does not interfere with Design-Builder’s, Subcontractor’s or equipment supplier’s activities or operations. 7.2.3 Design-Builder shall provide to Owner a Performance Test report (excluding results from air emissions testing), including all applicable test data, calculations and certificates indicating the results of the Performance Tests and, within five (5) business days of Owner’s receipt of such results, Owner, Independent Engineer and Design-Builder will jointly inspect such Work and review the results of the Performance Tests to verify that the Performance Guarantee Criteria have been met. If Owner or Independent Engineer reasonably determines that the Performance Guarantee Criteria have not been met, Owner shall notify Design-Builder the reasons why Owner determined that the Performance Guarantee Criteria have not been met and Design-Builder shall promptly take such action or perform such additional work as will achieve the Performance Guarantee Criteria and shall issue to the Owner another notice in accordance with Section 7.2.2; provided however that if the notice relates to a retest, the notice may be provided no less than two (2) business days prior to the Performance Tests. Such procedure shall be repeated as necessary until Owner and Independent Engineer verifies that the Performance Guarantee Criteria have been met. 7.2.4 If Owner, for whatever reason, prevents Design-Builder from demonstrating the Performance Guarantee Criteria within thirty (30) Days of Design-Builder’s notice that the Plant is ready for Performance Testing, then Design-Builder shall be excused from demonstrating compliance with the Performance Guarantee Criteria during such period of time that Design-Builder is prevented from demonstrating compliance with the Performance Guarantee Criteria; provided however that Design-Builder will be deemed to have fulfilled all of its obligations to demonstrate that the Plant meets the Performance Guarantee Criteria should such period of time during which Design-Builder is prevented from demonstrating the Performance Criteria exceed thirty (30) Days or extend beyond the Final Completion Date.

  • Solicitations for Subcontracts, Including Procurement of Materials and Equipment In all solicitations either by competitive bidding or negotiation made by the Local Government for work to be performed under a subcontract, including procurement of materials or leases of equipment, each potential subcontractor or supplier will be notified by the Local Government of the Local Government’s obligations under this Agreement and the Acts and Regulations relative to Nondiscrimination on the grounds of race, color, or national origin.

  • 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.

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