RFP ATT 001-CLS STATEMENT OF WORK(08162012)Track Changes.doc
DOC document 97 KB Posted
- Solicitation number
- N68335-12-R-0112
About this file
RFP ATT 001 provided here for reference with Q As.
View the file
Other files
Show all 20
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
ATTACHMENT 001 RTCASS CLS STATEMENT OF WORK
STATEMENT OF WORK FOR
CONTRACTOR LOGISTICS SUPPORT (CLS)
FOR
AN/USM-702, Reconfigurable Transportable Consolidated Automated Support System (RTCASS), AN/USM-725, Reconfigurable Transportable Consolidated Automated Support System, High Power (RTCASS-HP) and ON-640/USM-702, Self-Maintenance Automatic Test/ Calibration (SMAT/CAL) Operational Test Program Set (OTPS)
TABLE OF CONTENTS
41.0
SCOPE
2.0
GENERAL REQUIREMENTS
2.1 Subcontractor Management 2.2 Program Reviews and Reports 2.3 Component Availability 2.4 Provisioning Changes 2.5 Configuration Management 2.6 Logistics Documentation 2.7 Obsolescence and Diminishing Manufacturing Sources/Material Shortages (DMSMS) Management 2.8 Reliability and Failure Management Program 2.9 Problem Identification Reports (PIRs)
2.10 Sustaining Engineering & Logistics Support……………………………………………………
3.0
FLEET SPECIFIC REQUIREMENTS
3.1 Component Availability 4.0
NON-FLEET SPECIFIC REQUIREMENTS
4.1 Component Availability 4.2 Calibration Services 5.0
FOREIGN MILITARY SALES (FMS) SPECIFIC REQUIREMENTS
5.1 Component Availability 5.2 Calibration Services 5.3 Technical Support 6.0
EXIT CRITERIA
7.0
DATA DELIVERABLES
8.0
APPLICABLE DOCUMENTS AND REFERENCES
9.0
ACRONYMS
SOW APPENDICES
SOW APPENDIX A. WEBCAV STATEMENT OF WORK
SOW APPENDIX B. TECHNICAL MANUAL SOURCE DATA RECORD (TMSDR)
SOW APPENDIX C. LOGISTICS REQUIREMENTS CHANGE REQUEST (LRCR)
SOW APPENDIX D. CUSTOMER PRODUCT QUALITY DEFICIENCY REPORTS
1.0 SCOPE
The Contractor shall provide all services and materials necessary to provide logistics support for the Reconfigurable Transportable Consolidated Automated Support System (RTCASS) in accordance with this Statement of Work. This shall be accomplished in accordance with the applicable Technical Data Packages (TDPs) and various other processes and procedures described herein. All CDRLS referenced in this SOW are listed in Section 7.0 Data Deliverables.
2.0 GENERAL REQUIREMENTS
This section states general requirements applicable to this Contract. More detailed requirements for specific activities/customers may be found in Sections 3.0 - 5.0.
2.1 Subcontractor Management
The Contractor shall be solely responsible for performance and quality workmanship of all subcontractor work performed in response to the requirements of this SOW.
2.2 Program Reviews and Reports
2.2.1 Integrated Product Team (IPT) Reviews
IPT Reviews will consist of Government and Contractor representatives. Reviews will be held quarterly at the Contractor’s facility or via TeleConference or Video TeleConference (VTC) as agreed to by the Government. The Contractor will prepare and provide meeting minutes in accordance with CDRL A001.
2.2.2 Progress Status and Management Report
The Contractor shall develop and update a monthly Progress, Status and Management Report showing all progress made in execution of the contract, significant events and changes to the Contractor's organization/processes and other pertinent data IAW CDRL A001.
2.2.3 Performance and Cost Report
The Contractor shall develop and update a Performance and Cost Report showing expenditures for all repair actions, procurements and prerequisite events. The report must also detail costs for work completed that has not yet been billed. Total amounts must be separated by Contract Line Item Number (CLIN). The Contractor shall submit this report to the Government IAW CDRL A001.
2.2.4 Failure Review Boards (FRBs)
The Contractor shall hold Failure Review Boards (FRBs) with the Government for classifications of failures and a review of any failure analysis performed. FRBs will be held quarterly at the Contractor’s facility or via TeleConference or Video TeleConference (VTC) as agreed to by the Government.
2.3 Component Availability
The Contractor shall provide replacement RTCASS assets in a ready-for-issue condition in accordance with the requirements of this section. RTCASS assets are identified in Attachment 003.
2.3.1 Contractor Furnished Facilities
The Contractor shall provide storage facilities to store, manage and issue Government Furnished Property (GFP). The Contractor's facilities shall be fully prepared to provide proper environmental and security for the GFP. Since property may be owned by different Government organizations, all property shall be segregated into separate supply pools by ownership. Any Contractor owned property shall be segregated at all times.
Facilities used by the Contractor to store, manage and issue Government Furnished Property (GFP) applicable to the execution of this contract shall be referred to as the RTCASS Fleet and Industrial Support Center (FISC).
2.3.2 Repairable Material
The contractor will repair or replace RTCASS repairable assets within 30 days of receipt. The turn-around-time for repaired/replaced assets will be measured from the date that the retrograde asset is made available to the Contractor to the date that the RFI asset is made available to the respective originating Government activity.
Upon receipt of an end-user's requisition for an RTCASS asset, if the asset is available in the appropriate supply pool, the Contractor shall issue a suitable replacement within 24 hours. If the requisition is received on a weekend day, federal holiday or during non-standard business hours (4:01 PM - 06:59 AM), the Contractor shall issue a suitable replacement within 24 hours of 7:00 AM the next standard business day. All Broad-Arrow (BA) requisitions received before 1:00 PM during standard business hours will be issued the same day.
Fleet requisitions identified as Broad-Arrow (BA) identify an item of inoperative support equipment where there is no redundancy. Broad-Arrow requisitions will be completed at a higher priority than other requisitions without regard to the order in which requisitions are received.
2.3.3 Material Delivery
2.3.3.1 Contiguous United States (CONUS)
All requisitions shall be processed to arrive at CONUS destinations within 72 hours of issuance. Broad-Arrow (BA) requisitions shall be processed to arrive at CONUS destinations within 24 hours of issuance.
2.3.3.2 Outside the Contiguous United States (OCONUS)
All OCONUS requisitions shall be processed and ready for Government disposition within 72 hours of issuance. OCONUS Broad-Arrow (BA) requisitions shall be processed and ready for Government disposition within 24 hours of issuance.
OCONUS requisitions will utilize DCMA’s Government Freight Management (GFM) system and/or US Custom’s Automated Export System (AES) to provide required export information. When AES systems are not available, the Contractor can hold the shipment until the system is available. If an OCONUS asset is International Traffic in Arms Regulations (ITAR) material (anything other than DEMIL Code A) then a time allowance will be made for filling and obtaining a release through the US Custom’s Automated Export System (AES).
All OCONUS shipments will be determined by addresses obtained from the Cargo Routing Indicator File (CRIF) located in the Financial Air Clearance Transportation System (FACTS).
2.3.4 Repair
The Contractor shall ensure all repaired assets meet configuration requirements in accordance with the RTCASS Technical Data Package (TDP).
Upon completion of any component repair and/or functional inspection, items may be subject to final test and inspection by DCMA at the Contractor's facility. The Contractor shall maintain and provide upon request repair and calibration records for each item that has been repaired and/or calibrated.
All calibration performed must be traceable to the National Institute of Standards and Technology (NIST).
Items with calibration expiration dates shall not be issued to the Government unless at least 75% un-expired time remains.
2.3.5 Product Quality Deficiency Reports (PQDRs)
PQDRs shall be addressed by the Contractor per the COMNAVAIRFORINST 4790 series and SECNAVINST 4855.5A. Attachment 001 SOW Appendix D contains an example of the information found in a PQDR.
2.3.6 Material Management
To meet or exceed contract requirements, the Contractor may use its own assets to satisfy Government requisitions ("title out"). In this event, the asset will become Government property. The Government’s next available asset in a ready-for-issue (RFI) condition shall become the property of the Contractor (“title in”).
2.3.7 Status Reporting
The Contractor shall provide tracking and asset management for all requisitions and for the Contractor managed inventory. Reporting for each item shall begin on the day an asset/requisition is received by the Contractor. The Contractor shall report transactions (receipt, condition code changes, shipments, and proof-of-shipments) accurately by the end of the next regular business day after the occurrence of a reportable event. The Contractor shall maintain and provide Government access to an asset tracking database and maintain no less than 99% accuracy.
2.4 Provisioning Changes
Consumable assets re-coded to repairable shall be supported under this contract. When an SM&R code changes, the item is to be treated as a new part. The Government, at its sole discretion, may change SM&R codes due to future availability, high attrition rate or replacement cost of items under consideration. The Contractor is encouraged to recommend SM&R code changes for like rationale. The Contractor shall provide full support for new repairables within 60 days of Government notice.
2.5 Configuration Management
The Contractor shall maintain configuration control of all RTCASS sub-assemblies and components maintained under this contract in accordance with the RTCASS Technical Data Package (TDP) and PMA260 Configuration Management Plan.
2.5.1 Engineering Change Proposals (ECPs)
The need for a Class I or Class II change or redesign shall be documented in a Problem Identification Report (PIR). The PIR shall include a recommended solution and estimated costs.
After receiving the PIR with a cost estimate, Class II ECPs will be approved/disapproved by the CASS APML or designated DAPML. Costs related to Class I ECPs will be segregated for separate, case-by-case funding via a PCO issued modification to the contract.
A Notice of Revision (NOR) shall be used to define revisions to drawings, associated lists, or other referenced documents which require revision after a Class I or II ECP approval. The Contractor shall deliver NORs in accordance with CDRL A002.
2.5.2 Requests for Deviation (RFD)
The Contractor shall not provide items for acceptance by the Government that incorporate a known departure from the approved configuration, unless a Request for Deviation (RFD) has been processed, classified (critical, major, or minor), and approved in accordance with the PMA260 Configuration Management Plan. Deviations are a temporary departure from requirements and do not constitute a change to the RTCASS system baseline as defined by the RTCASS Technical Data Package (TDP). Classification disagreements shall be referred to the PMA-260 Configuration Manager for decision. The Contractor shall deliver RFDs in accordance with CDRL A003.
2.5.3 Configuration Upgrades
The Contractor shall upgrade any spares that are out of configuration as defined by the RTCASS Technical Data Package (TDP). The Contractor will provide an estimate to the Government and will wait for disposition/approval from the COR before processing any material to be upgraded.
2.6 Logistics Documentation
The Contractor shall maintain and update logistics documentation as required. Completed changes shall be reviewed/approved by the Government team quarterly. The Contractor shall submit changes/updates to the Government in accordance with CDRL A004.
2.6.1 Technical Manual Updates
The Contractor shall update the RTCASS Technical Manuals as required. Each technical manual change request shall be identified to the Contractor via a Technical Manual Source Data Record (TMSDR). Attachment 001, SOW Appendix B contains an example of a TMSDR.
2.6.2 Logistic Support Analysis Record (LSAR) Updates
The Contractor shall update the Logistics Support Analysis Record (LSAR) Database as required. Each LSAR change shall be identified to the Contractor via a Logistics Requirements Change Request (LRCR). Attachment 001, SOW Appendix C contains an example of an LRCR.
2.7 Obsolescence and Diminishing Manufacturing Sources/Material Shortages (DMSMS) Management
The contractor shall develop an Obsolescence and DMSMS management plan, which shall define the methodologies to minimize the adverse affects of Obsolescence and DMSMS on system and contract performance, as well as, minimize additional costs to be incurred by the Government due to parts obsolescence. The contractor shall deliver the DMSMS management plan in accordance with CDRL A007 within 90 days after contract award.
The Contractor is responsible for managing obsolescence over the entire period of the contract as well as planning/providing information for a 5 year post contract period. This obsolescence management responsibility includes an ongoing review and identification of actual and potential obsolescence and DMSMS issues, including but not limited to obsolescence of components, assemblies, sub-assemblies, piece parts, and material.
Any configuration changes due to obsolescence/DMSMS shall be approved in accordance with the configuration management requirements of this SOW. The Contractor shall provide the Government with obsolescence/DMSMS status briefs, as part of scheduled IPT reviews.
2.8 Reliability and Failure Management Program
The Contractor shall develop and implement a Reliability and Failure Management Program to document failures, perform root cause analyses and to identify cases for reliability improvement.
2.8.1 Failure Reporting and Corrective Action System (FRACAS)
The Contractor shall implement a closed loop system that collects, analyzes, and records failures that occur for specified levels (System and WRA) of assembly.
Procedures for initiating failure reports, the analysis of failures, feedback of corrective action into the manufacturing, repair and test processes shall be identified. Flow diagram(s) depicting failed hardware and data flow shall also be documented. The analysis of failures shall establish and categorize the cause of failure. All analysis shall be performed to the lowest level of inspection and repair.
The closed loop system shall include provisions to assure that effective corrective actions are taken on a timely basis by a follow-up audit that reviews all open failure reports, failure analysis, and corrective action suspense dates, and the reporting of delinquencies to management. The failure and root cause for each failure shall be clearly stated and the method of establishing and recording operating time shall be clearly defined.
Subcontractors/vendors shall be included in the process to facilitate adequate/efficient execution of the FRACAS. The FRACAS shall provide visibility and traceability of all reported failures from discovery to closeout to ensure reliability growth. The Contractor shall ensure failure report closeout within sixty (60) calendar days after an asset's induction for repair, with the failure report for this item commencing within five (5) calendar days of receipt of the failed item. The Contractor shall evaluate the effectiveness of the corrective action(s) using continual tracking and process improvement techniques.
2.8.2 FRACAS Database
The Contractor shall prepare FRACAS reports of all failures or nonconformance conditions during the performance of the contract. The Contractor shall maintain a failure reporting database to document the failures and related analysis and corrective actions. The FRACAS database shall be made available for Government access/review as requested at any time during the performance of the contract.
This database shall include, but not be limited to, the following data:
· failure report number
· failure number
· part number
· serial number
· item name
· site from where asset came (Location)
· received date
· missing on induction (MOI)
· repair responsibility
· estimated date of return
· date shipped
· location shipped to
· supplier’s cost of repair
· description of failure (from Activity)
· description of failure and root cause (from Contractor after evaluation)
· repair action/corrective action performed
· readiness degraders
· maintenance induced failures
· TPS induced failures
· A799
· training issues
· troubleshooting issues
The following data items shall be included if the applicable information is available:
· station serial number
· station elapsed time indicator (ETI)
· maintenance action form (MAF) number
· operator name
FRACAS reports shall be submitted to the Government IAW CDRL A005.
2.8.3 Failure Analysis
The Contractor shall perform detailed analyses on all failures that are determined to be a trend through the joint Contractor/Government Failure Review Board process. Each analysis must be to the depth required to determine the root cause of the failure and to develop corrective actions to prevent their recurrence. The Contractor shall record the result of each analysis in the FRACAS database IAW CDRL A005 and shall make detailed records available at Government request.
2.8.4 Corrective Actions
The Contractor shall develop corrective actions to eliminate recurrence of the failure mechanism and its effects. Corrective actions may consist of changes in repair processes, parts, materials, vendors, or any other appropriate areas or hardware/software design. The Government shall review corrective actions for all faults and failures and provide approval/disapproval as part of the FRB process. Any proposed change that would impact an item's approved configuration shall then be submitted by the Contractor as a PIR IAW CDRL A006.
2.9 Problem Identification Reports (PIRs)
The Contractor will inform the Government of technical data/process abnormalities and suggest configuration changes through the use of a Problem Identification Report (PIR). PIRs will be used to identify and recommend solutions to problems pertaining to technical data, hardware, software, and any combination of issues. Problem Identification Reports will be submitted to Government IAW CDRL A006.
2.10 Sustaining Engineering and Logistics Support
The Contractor shall provide additional sustaining engineering and logistics support for the RTCASS System including RTCASS HPDTS and SMAT/CAL, under a separate CLIN, as requested by the Government.
The Contractor shall provide sustaining engineering and logistics support and investigations when authorized by the Procuring Contracting Officer (PCO). The PCO, in conjunction with the Contracting Officer’s Representative (COR), will provide a SOO, and the PCO will request task sizing from the Contractor. The Contractor has ten (10) working days to respond. The proposal will include detailed labor, materials, schedule and supporting assumptions and rational used in formulation of level of effort. The PCO will review and authorize the tasks via FFP or CPFF delivery order upon mutual agreement of both parties. The Contractor shall provide a Report of Completion at the completion of each tasking.
The contractor will provide support to the RTCASS CLS program, to include, but not limited to the following areas, as directed in writing by the PCO:
(1) Provide Integrated Logistics Support (ILS) to include preparing, reviewing, tracking and implementing ECPs, participating in ILS meetings, providing training and updates to training materials; producing technical manual data, provisioning/Logistics Support Analysis (LSA) data; updating affected spares/NAVICP assets.
(2) Provide trade-off analyses in addition to producing all costing information; and implement, upon PCO approval, change in production baseline and retrofitting changes into fielded system.
(3) Provide engineering support for Class I ECP development as required.
(4) Provide technical support for the Installation teams, Technical Working Group (TWG), Readiness Reliability Team (RRT), and other related meetings as required.
(5) Provide product design/redesign and integration of components (integrated circuits), printed wiring boards and mechanical enclosures to include demonstration modeling, documentation, testing and manufacturing.
(6) Perform market surveys and analysis data as required.
(7) Provide recommendations on spares and repair parts as required.
(8) Technical Studies involving RTCASS and automatic test equipment variants.
For purposes of this solicitation, the offeror shall propose support by a Senior Sustaining Engineer and a Senior Logistics Manager.
3.0 FLEET SPECIFIC REQUIREMENTS
3.1 Component Availability
The Contractor shall provide component availability in accordance with these specific requirements and Attachment 001 Appendix A, WEBCAV Statement of Work, when providing service for Fleet designated sites.
3.1.1 Service Performance
On the day an asset is received at the Contractor’s facility, it is entered into the WEBCAV system and managed IAW the WEBCAV Statement of Work (see Attachment 001, Appendix A). Government owned “A” condition wholesale level assets will be held at the RTCASS FISC in a segregated stockroom and Transaction Item Reported (TIR’d) via WEBCAV to NAVICP. ****
3.1.2 Broad-Arrow Requisitions
Requisitions identified by project codes 0F7, 9XX series and Air Force MICAP shall be processed under the same conditions applicable to Broad-Arrow requisitions.
3.1.3 Missing-On-Induction (MOI)
The Contractor will notify the NAVICP Inventory Manager via email of any Missing-On-Induction (MOI) items within 24 hours of discovery. The Government will attempt to obtain any MOI assets from the end-user. The requisition will be placed in “G” condition until MOI parts are received. If the Contractor determines that it would be economical to purchase a replacement asset, the retrograde asset will be considered BER. The Contractor will notify the NAVICP Inventory Manager for disposition instructions.
3.1.4 Beyond Economical Repair (BER)
The Contractor is responsible to determine whether an item is Beyond Economical Repair (BER) with DCMA concurrence. BER is defined as 75% of the current purchase price of an identical new asset.
Refer to Attachment 001, Appendix A for Fleet specific BER instructions.
3.1.5 Reporting Requirements
The Contractor will provide tracking/asset management of condition of assets using WEBCAV and the following conditions codes: “F” (unserviceable, non-RFI), “M” (suspended; in-work), “G” (unserviceable; incomplete), “H” (unserviceable; condemned) and “A” (serviceable, issuable without qualification).
3.1.6 Material Management
When a Contractor’s asset is used to satisfy a requisition, the asset shall be supplied from the Contractor owned inventory and Transaction Item Reported (TIR’d) to “A” condition (“title out”). The asset will then be placed with the Fleet supply pool in the FISC stockroom located within the Contractor’s facility. The Government’s next available ‘A’ condition asset shall become the property of the Contractor (“title in”). Contractor shall record the serial number of each asset that changes title from Government-owned to Contractor-owned or vice versa. All titling transactions shall be recorded in WEBCAV database.
3.1.7 Packaging and Marking
3.1.7.1 Reusable Containers
If available, items assigned to reusable shipping and storage containers shall be shipped in containers provided by the Navy. The Contractor may request containers to meet quarterly requirements thirty days prior to the start of the quarter. The Contractor may request containers online via the Container Request Form (CRF) on the Technical Assistance for Repairables (TARP) website (https://www.tarp.navicp.navy.mil). Alternatively, the Contractor may request containers in writing from the NAVICP Container Manager, via the Contracting Officer. In the event reusable containers are unavailable, the Contractor shall package the items in accordance with standard commercial practice, as defined in ASTM D-3951. Under no circumstances shall the unavailability of reusable containers be the basis for relief from the requirements of this contract or the basis for a claim of excusable delay.
3.1.7.2 Packaging for Items Not Assigned Reusable Containers
For those items not assigned reusable containers, the Contractor shall be responsible to package those items in accordance with standard commercial practice, as defined in ASTM D-3951. In addition to the requirements of ASTM D-3951, the following unique requirements shall also apply:
a. Unit packs shall be designed to conserve weight and cube while retaining the protection required and enhancing standardization.
b. Use of plastics shall be reduced in preservation and packing operations. All packaging methods and materials shall be reusable/recyclable and shall minimize the quantity of solid waste generated at the time of disposal.
c. Any shelf-life items shall be identified to NAVICP Code M0772, P.O. Box 2020, 5450 Carlisle Pike, Mechanicsburg, Pa 17955-0788 and the Contracting Officer. Records of cure/assembly date shall be compiled and maintained, and the Contractor shall ensure a minimum of 85% of the shelf life remaining at time of receipt at destination.
d. If FAR 23.3, FAR 52.223-3, Hazardous Material Identification and Material Safety Data, and DFARS Subpart 223.3 and DFARS 252.223-7001, Hazard Warning Labels, are applicable to this contract, Material Safety Data Sheets (MSDS) must be provided in accordance with these provisions to the contracting officer and the Navy Environmental Health Center, 2510 Walmer Ave., Norfolk, VA 23513-2617, Attn: Industrial Hygiene Directorate for inclusion in the Hazardous Materials Information System (HMIS). Copies shall also be provided to NAVICP Code M0772, P.O. Box 2020, 5450 Carlisle Pike, Mechanicsburg, PA 17955-0788.
e. Electrostatic sensitive circuit card assemblies, modules and electronic modules containing electronic components such as resistors, transistors, diodes, integrated circuits, etc., shall be provided protection from damage caused by electrostatic discharge (ESD). Electrostatic discharge sensitive (ESDS) and electromagnetic interference (EMI) material shall have wraps, cushioning and bags or pouches which are electrostatic protective, electrostatic dissipative and magnetic shielding. Markings shall include: “Items susceptible to ESD/EMI damage. Open/Handle at approved stations only." Equipment susceptible to damage from ESD and/or EMI forces shall be handled in accordance with MIL-STD-1686C.
f. Shredded paper, excelsior (wood shaving), polystyrene loose-fill and other loose-fill materials are prohibited for cushioning/dunnage.
g. Reporting of improperly packaged retrograde material received by the Contractor shall be accomplished through Contractor input into the Technical Assistance for Repairables (TARP) Web Site (https://www.tarp.navicp.navy.mil).
3.1.7.3 Restrictions Regarding Wood Packaging Material (WPM)
All shipment material utilizing coniferous and non-coniferous wood pallets, wood containers and dunnage constructed from non-manufactured wood shall be in accordance with the International Plant Protection Commission's (IPPC) ISPM No. 15, Restrictions Regarding Wood Packaging Material (WPM).
3.1.8 Marking
All unit, intermediate and shipping containers shall be marked in accordance with the requirements of MIL-STD-129P.
3.1.9 Shipping
Asset shipment transportation to the requesting UIC Activities shall be provided by contracted services of third party logistics carriers. For asset shipments destined to UIC Activities that are located CONUS, addresses shall be obtained from the Defense Automatic Addressing System (DAAS).
All OCONUS shipments will be determined by addresses obtained from the Cargo Routing Indicator File (CRIF) located in the Financial Air Clearance Transportation System (FACTS).
3.1.10 Status Reporting
The Contractor shall provide tracking and asset management in accordance with Attachment 001 Appendix A, Web-Based Commercial Asset Visibility (CAV) Statement of Work (SOW).
4.0 NON-FLEET SPECIFIC REQUIREMENTS
4.1 Component Availability
The Contractor shall provide component availability in accordance with these specific requirements when providing service for Non-Fleet designated sites (refer to Attachment 006, RTCASS Fielding Profile Rev C).
4.1.1 Consumable Material
The Contractor shall provide consumable parts as required to support Non-Fleet/FMS activities. The Contractor shall provide or place an order to purchase the requested consumable part within seven (7) days of receiving a requisition. The Contractor shall select procurement sources based on the ability to provide the most cost effective and timely order.
4.1.2 Missing-On-Induction (MOI)
The Contractor will notify the originator of any Missing-On-Induction (MOI) item within 24 hours of discovery. MOI status includes any assets that cannot be repaired/serviced due to missing parts. The Government will attempt to obtain any MOI assets from the end-user. The Contractor will notify the Government for disposition instructions.
4.1.3 Beyond Economical Repair (BER)
The Contractor is responsible to determine whether an item is Beyond Economical Repair (BER) with DCMA concurrence. BER is defined as 75% of the current purchase price of an identical new asset. Notification to the Government is required within ten (10) working days of determination.
4.1.4 Packaging and Marking
Packaging, packing and marking of all material shipped from the Contractor in accordance with Standard Commercial Practice, IAW ASTM D-3951. If an item is returned to the Contractor in a Reusable Container, the Reusable Container may be reused if the container is in Ready For Use (RFU) Condition. No effort will be made by the Contractor to repair or replace a Reusable Container that is not (RFU).
4.1.5 Shipping
The Contractor shall ship items after completion of inspection and acceptance. Items shall be packaged with the applicable shipping documents and sent to the requisition’s respective activity. Items shall be shipped using best traceable commercial practices.
4.2 Calibration Services
As required by specific Non-Fleet users, the Contractor shall provide calibration services for standards used to maintain RTCASS. Upon turn-in of a standard requiring repair/calibration the Contractor shall provide the same configuration item to the Government within 30 days. Standards calibrated under this service shall not be issued to the Government unless at least 90% un-expired time remains. A List of RTCASS calibration items are contained in Attachment 011.
5.0 FOREIGN MILITARY SALES (FMS) SPECIFIC REQUIREMENTS
5.1 Component Availability
All Non-Fleet Specific Requirements for Component Availability apply.
5.2 Calibration Services
All Non-Fleet Specific Requirements for Calibration Services apply.
5.3 Technical Support
When added by an equitable adjustment to the contract, the Contractor shall provide full-service on-site technical support as required by the specific FMS customer as a separately priced CLIN.. The Contractor shall be responsible for all station maintenance, calibration, periodic and preventive maintenance and tracking the system's hardware and software configuration. The Contractor shall guarantee less than 24 hours Repair Downtime (Rdt) for each RTCASS covered by service support.
Repair Downtime (Rdt) shall be measured, as defined by the Department of Defense (DOD) Reliability and Maintainability (RAM) Guide, from the time the Contractor is notified of an RTCASS problem to the time the problem is resolved excluding any Logistics Delay Time (LDT).
The Contractor shall keep a detailed maintenance log available to the customer upon request.
6.0 EXIT CRITERIA
Prior to completion of the contract, the Contractor shall assist in the orderly transition of the integral aspects of the program to Government control.
7.0 DATA DELIVERABLES
CDRL A001
Program Reporting
- Meeting Minutes
- Progress, Status and Management Report
- Performance and Cost Report
CDRL A002
Notice of Revisions (NORs)
CDRL A003
Requests for Deviation (RFD)
CDRL A004
Logistics Documentation
CDRL A005
FRACAS Reports
CDRL A006
Problem Identification Reports
CDRL A007
DMSMS management Plan
8.0 APPLICABLE DOCUMENTS AND REFERENCES
ASTM D-3951, Commercial Packaging
COMNAVAIRFORINST 4790 series Naval Aviation Maintenance Plan (NAMP)
Defense Automatic Addressing System (DAAS)
Defense Federal Acquisition Regulations (DFAR)
DOD Reliability and Maintainability (RAM) Guide
Federal Acquisition Regulations (FAR)
Financial Air Clearance Transportation System (FACTS)
International Plant Protection Commission's (IPPC) ISPM No. 15
MIL-STD-129P
, Military Marking
MIL-STD-1686C, Electrostatic Discharge Control Program
PMA260 Configuration Management Plan
RTCASS LSAR Database
RTCASS Technical Data Package (TDP)
RTCASS Technical Manuals
SECNAVINST 4855.5A, Product Quality Deficiency Report Program
Technical Assistance for Repairables Web Site (https://www.tarp.navicp.navy.mil)
9.0 ACRONYMS
AES
Automated Export System
BA
Broad-Arrow
BER
Beyond Economical Repair
CDRL
Contract Data Requirements List
CONUS
Contiguous United States
COR
Contracting Officer Representative
CRIF
Cargo Routing Indicator File
DCMA
Defense Contract Management Agency
DEMIL
Demilitarization
DLR
Depot Level Repairable
DMSMS
Diminishing Manufacturing Sources/Material Shortages
ECP
Engineering Change Proposal
FACTS
Financial Air Clearance Transportation System
FISC
Fleet and Industrial Support Center
FRACAS
Failure Reporting and Corrective Action System
FRB
Failure Review Board
FST
Fleet Support Team
GFM
Government Freight Management
GFP
Government Furnished Property
IPT
Integrated Product Team
ITAR
International Traffic in Arms Regulations
MICAP
Mission Impaired Capability Awaiting Parts
MOI
Missing on Induction
NIST
National Institute Of Standards Technology
NOR
Notice of Revision
OCONUS
Outside the Contiguous United States
PCO
Procurement Contracting Officer
PIR
Problem Identification Report
PQDR
Product Quality Deficiency Report
RFI
Ready for Issue
RFU
Ready For Use
RTCASS
Reconfigurable Transportable Consolidated Automated Support System RTCASS assets
Components of RTCASS, RTCASS High Power(HP) & SMAT/CAL OTPS
SMAT/CAL OTPS
Self-Maintenance Automatic Test/Calibration Operational Test Program Sets
SM&R
Source, Maintenance, and Recoverability
SOW
Statement of Work
TDP
Technical Data Package
TIR
Transaction Item Reported
TPS
Test Program Set
WEBCAV
Web-Based Commercial Asset Visibility
WRA
Weapons Replaceable Assembly
File details come from the government source that posted it. Updated .