Non-Metallic Hoses

Attachment 0001 Special Provisions W31P4Q-25-Q-0009 1. 52.243-4000, ENG CHG PROPOSAL, VALUE ENG CHG PROPOSAL, REQUEST FOR DEVIATION, MAR/2011 REQUEST FOR VARIANCE, ENG RELEASE RECORDS, NOTICE OF REVISION, AND SPECIFICATION CHG NOTICE PREPARATION AND SUBMISSION INSTRUCTIONS, MAR/2011 1. Contractor initiated Engineering Change Proposals (ECPs), Value Engineering Change Proposals (VECPs), Request for Deviations (RFDs), and Request for Variance (RFVs), collectively referred to as "proposals", shall be prepared, submitted and distributed in accordance with paragraphs 2, 3 and 4 below except as specified in paragraph 5 below. 2 . Format. a. Class 1 ECPs require the "Long Form Procedure" for documenting the change and describing the effects of the change on the suitability and supportability of the Configuration Item (CI). Class I ECPs should be limited to those that are necessary or offer significant benefit to the Government. Class I ECPs are those that affect the performance, reliability, maintainability, survivability, weight, balance, moment of inertia, interface characteristics, electromagnetic characteristics, or other technical requirements in the specifications and drawings. Class I ECPs also include those changes that affect Government Furnished Equipment, safety, compatibility, retrofit, operation and maintenance manuals, interchangeability, substitutability, replaceability, source control specifications and drawings, costs, guarantees or warranties, deliveries, or schedules. Class II ECPs are those that do not affect form, fit and function, cost, or schedule of the system CI and do not meet the other criteria described above for Class I ECPs. b. Long Form Procedure: Class I changes to the CI require that RDMR Form 523, pages 1 through 7 (as applicable), be prepared. Use of this procedure assures that all effects of the change on the CI are properly addressed and documented to the necessary detail to allow proper evaluation of the proposed change. c. Short Form Procedure: ECPs and VECPs , which meet the requirements of Class II ECPs, shall be prepared using RDMR Form 523 (page 1 only). Supplemental pages may be used with the form as necessary. The responsible Contract Management Office (CMO) will enter the appropriate data in Block 5 "Class of ECP", Block 6 "Justification Codes", and Block 7 "Priority." d. The Contractor shall not manufacture items for acceptance by the Government that incorporate a known departure from requirements, unless the Government has approved an RFD. RFDs shall be prepared using RDMR Form 527 or RDMR Form 530 (Type I, see block 5 of the form.) e. The Contractor shall not submit items for acceptance by the Government that include a known departure from the requirements, unless the Government has approved a RFV. RFVs shall be prepared using RDMR Form 528. f. Each ECP, RFD or RFV shall be accompanied by a written and signed evaluation prepared by the responsible Defense Contract Management Agency (DCMA) technical representative. The DCMA written evaluation shall be considered part of the ECP/RFD/RFV proposal. g. Classification of RFDs/RFVs. (1) Major RFDs/RFVs. RFDs/RFVs written against CIs shall be designated as major when the RFD/RFV consists of acceptance of an item having a nonconformance with contract or configuration documentation involving health; performance; interchangeability; reliability; survivability; maintainability; effective use or operation; weight; appearance (when a factor); or when there is a departure from a requirement classified as major in the contractual documentation. (2) Critical RFDs/RFVs. RFDs/RFVs written against CIs shall be designated as critical when the RFD/RFV consists of acceptance of an item having a nonconformance with contract or configuration documentation involving safety or when there is a departure from a requirement classified as critical in the contractual documentation. (3) Minor RFDs/RFVs. RFDs/RFVs written against CIs shall be designated as minor when the RFD/RFV consists of acceptance of an item having a nonconformance with contract or configuration documentation which does not involve any of the factors listed above in paragraphs g(1) or g(2), or when there is a departure from a requirement classified as minor in the contractual documentation. h. Proposals shall include sufficient technical data to describe all changes from existing contract requirements. i. Proposals shall include sufficient justification for making the change, including a statement of contract impact, if the change is not authorized. j. Proposals for ECPs shall set forth a "not to exceed" price and delivery adjustment acceptable to the Contractor if the Government subsequently approves the proposal. If approved, the equitable increase shall not exceed this amount. k. Times allowed for technical decisions for ECP and RFD/RFV proposals will be worked out via mutual agreement between the Contractor and the Government. l. The Contractor shall submit, concurrent with the ECP, a separate AMSAM-RD Form 525, "Specification Change Notice" (SCN), for each specification that would require revision if the ECP were approved. m. Proposals for VECPs shall set forth a "not less than" price and delivery adjustment acceptable to the Contractor if the Government subsequently approves the proposal. If approved, the savings shall not be less than this amount. n. The Contractor shall utilize RDMR Form 526, "Engineering Release Record" (ERR) to release new or revised configuration documentation to the Government for approval. o. The Contractor shall utilize RDMR Form 524, "Notice of Revision" (NOR) to describe the exact change(s) to configuration documentation specified as a data requirement in the contract. The Contractor shall describe the change using subsections entitled "WAS" to describe the current contractual technical requirement and "IS" to describe the proposed new requirement. 3 . Submittal. The Contractor shall submit two (2) cop…