Failure Reporting, Analysis, and Corrective Action System (FRACAS) Sample Clauses

Failure Reporting, Analysis, and Corrective Action System (FRACAS). The Contractor shall utilize a closed-loop FRACAS in accordance with ANSI/GEIA-STD-0009, as its mechanism for monitoring and communicating throughout the organization descriptions of: test and field failures, analyses of failure modes and root cause failure mechanisms, the status of design and/or process corrective actions, risk-mitigation decisions, the effectiveness of corrective actions, and lessons learned. The Contractor shall address failure modes in a timely manner, consistent with their impact on safety, reliability, performance, and total life cycle cost.
Sample 1Sample 2
AutoNDA by SimpleDocs
Failure Reporting, Analysis, and Corrective Action System (FRACAS). The contractor shall establish and maintain a FRACAS program. Failure reporting, failure analysis, corrective action analysis/implementation and required data collection shall be conducted by the contractor for all failures during both Government and contractor testing. During Government conducted testing, Test Incident Reports along with failed test items will be provided to the contractor for failures related to the component described in this contract. The contractor shall investigate and analyze each report to the level necessary to identify causes, mechanisms and potential effects of the failure. The contractor shall submit a Failed Item Analysis Report for each failure in accordance with CDRL A670. The Government shall be notified by the contractor of any failures that occur during qualification testing within forty-eight (48) hours of occurrence. The contractor shall perform internal audits to ensure that corrective actions are effectively implemented.
Sample 1Sample 2
Failure Reporting, Analysis, and Corrective Action System (FRACAS). The Contractor shall have, and shall require subcontractors to have, a closed loop system for collecting and recording all failures (both critical and non- critical) which occur during all test and inspection procedures, conducted from the initial testing of parts through and including final delivery to the Government. The Contractor shall create and maintain a Failure Summary and Analysis Report (CDRL A032). Individual failure records shall include, as a minimum, the failure record number, part number, name, manufacturer, date of failure, operating hours, problem description, investigation procedures, corrective action status, and the corresponding Engineering Change Proposal (ECP) number when applicable. All failures shall be analyzed and corrective actions implemented to preclude recurrence of the failure. The effectiveness of the corrective action shall be evaluated by the continued review of failure records. The Contractor's program shall include follow-up audits to review all open failure records to ensure timely closure and identification of problem areas. Investigations shall be performed to establish root cause of failure and corrective action for R&M problems and failure trends and failure analysis reports shall be provided detailing root cause of failure trend. Deliverable Data Item (See DD-1423): CDRL A032: “Failure Summary and Analysis Report”
Sample 1

Related to Failure Reporting, Analysis, and Corrective Action System (FRACAS)

  • REGULATORY FILINGS AND CAISO TARIFF COMPLIANCE 3.1 Filing

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • CHILD ABUSE REPORTING CONTRACTOR hereby agrees to annually train all staff members, including volunteers, so that they are familiar with and agree to adhere to its own child and dependent adult abuse reporting obligations and procedures as specified in California Penal Code section 11165.7, AB 1432, and Education Code 44691. To protect the privacy rights of all parties involved (i.e., reporter, child and alleged abuser), reports will remain confidential as required by law and professional ethical mandates. A written statement acknowledging the legal requirements of such reporting and verification of staff adherence to such reporting shall be submitted to the LEA.

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • Financial Viability and Regulatory Compliance 4.6.1 The Contractor warrants and represents that its corporate entity is in good standing with all applicable federal, state, and local licensing authorities and that it possesses all requisite licenses to perform the services required by this contract. The Contractor further warrants and represents that it owes no outstanding delinquent federal, state, or local taxes or business assessments.

  • Incident Reporting and Client Risk Prevention An incident report shall be created and maintained at the AGENCY for the following: in the event the AGENCY’S staff or subcontractor becomes aware of an occurrence of any incident of injury to a client receiving program services through the COUNTY, requiring medical treatment by a licensed physician; any lawsuit entered into or against the AGENCY, all allegations of any kind of abuse, neglect, or exploitation of the AGENCY’S clients with the exception of those AGENCIES whose primary function is working with those that have been abused, neglected or exploited unless the allegation is against an AGENCY staff member; media coverage relating to the media expressing an interest in a case or issue concerning a client of the AGENCY or an employee on the AGENCY premises, a fire, hostage situation, bomb threat, epidemic or any circumstance which may impact the service provision. All occurrences shall be verbally communicated directly to COUNTY staff no later than 10:00 a.m. the following business day via telephone to the COUNTY. All incident reports shall be made available to the COUNTY upon request and maintained at the AGENCY. These reporting requirements shall in no way supersede the requirements for notification of allegations of abuse/neglect/exploitations to the State of Florida Abuse Hotline, as mandated in Chapter(s) 39 and 415, Florida Statutes.

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse.

  • Testing/Trouble Reporting 1.15.1 TWTC will be responsible for testing and isolating troubles on Network Elements. TWTC must test and isolate trouble to the AT&T network before reporting the trouble to the Network Elements Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from AT&T at the time of the trouble report, TWTC will be required to provide the results of the TWTC test which indicate a problem on the AT&T network. Version: 4Q06 Standard ICA 11/30/06

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 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, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

Time is Money Join Law Insider Premium to draft better contracts faster.