PWS - Rev D - 11-01-11.docx

APPENDIX A

PERFORMANCE WORK STATEMENT (PWS)

for the Defense Management System (DMS)

PURCHASE REQUEST NUMBER: FD2030-11-37101

REV. D

PREPARATION DATE: 01 November 2011

PREPARING ORGANIZATION:

OC-ALC/424th Supply Chain Management Squadron (SCMS)/GUME

TINKER AFB OK 73145

TABLE OF CONTENTS

SECTION PARAGRAPH / TITLE PAGE

SECTION I – DESCRIPTION OF SERVICES/GENERAL INFORMATION 1-7

SECTION II – SERVICE SUMMARY 8-9

SECTION III – GOVERNMENT FURNISHED PROPERTY AND SERVICES 10

ATTACHMENT 1 DEFINITIONS 11-12

ATTACHMENT 2 APPLICABLE DOCUMENTS 13-15

CAV AF CFM SOW 16-24

Overhaul of the B-2 Flight Data Recorder System

SECTION 1 – DESCRIPTION OF SERVICES/GENERAL INFORMATION

The purpose of this Performance Work Statement (PWS) defines the Firm Fixed Price type of tasks for the B-2 Overhaul Program to be accomplished by the Contractor to maximize aircraft availability. This effort will include: receipt, disassembly, inspection, overhaul, packaging, and delivery of the items. The Contractor shall furnish all parts, tooling, fixtures, and materials needed to overhaul all items specified in this contract. A total of six (6) National Stock Number(s) (NSN) will be overhauled under this effort. The following NSN’s and Part Number(s) (P/N) apply:

NSN: 5865-01-461-0044NR

P/N: 185A500-2 Receiver Countermeasure Same

NSN: 5865-01-438-4321NR

P/N: 115A800-50 Receiver Countermeasure Same

NSN: 5865-01-445-0685FW

P/N: 149D3402G22 Radio Amplifier Same

NSN: 5996-01-380-5485NR

P/N: 149D3502G22 Radio Amplifier Same

NSN: 5996-01-587-2616NR

P/N: 149D3452G23 Radio Amplifier Same

NSN: 5996-01-587-7742NR

CONTRACTOR EMPLOYEES: Contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

MISSION ESSENTIAL SERVICES N/A

1.1 Specific Work Requirements

This work specification establishes the requirements to return the end items to a serviceable condition.

NOTE: A complete Air Force Tech Order for the complete overhaul has not been developed; OEM expertise and skills will be required to perform this service.

1.1.1 Receipt and Handling

The Contractor shall perform a receiving visual inspection upon receipt for any shipping or packaging. Items received which are damaged, misidentified, misdirected, or incomplete shall be reported to the Procuring Contracting Officer (PCO) for disposition instructions.

1.1.2 Disassembly

The Contractor shall disassemble the B-2 items to the extent necessary to accomplish the required inspection, test, overhaul or replacement of the B-2 items.

1.1.3 Inspection

The Contractor shall inspect each item for serviceability/reparable condition. Contractor’s inspection and overhaul documents shall reflect all inspections/overhaul steps required for each specific part.

1.1.4 Overhaul

The Contractor shall overhaul each B-2 item to ensure that the overhaul activity returns the serviceable end item with the same form, fit and function to the Government, validated by the Special Test Equipment final acceptance test. Testing includes: initial testing, system testing, and final ATP. A CLIN will be established for Over & Above for overhaul that exceeds the negotiated overhaul cost.

A. 5996-01-380-5485 - Band 1 RFFE Hardware No Overhauls shall be attempted for the Digital Controller or Power Supply as these items will be considered BER as no STE is available to perform evaluations. The contractor will be responsible for supply replacements.

B. 5865-01-461-0044 - Receiver Processor A lean event from 08/02/2011 has determined full replacement of the Pucks would improve delivery and quality. As this action will save labor hours additional material would be required that has the possibility of adding additional cost to the end item. In accordance with the finding of this lean event all Pucks on this item shall be replaced 100% of the time.

C. Engineering Changes All class II and class II changes to any parts will be electronically sent by email to the 424 SCMS/GUME engineer Hallie Peltier and the Production Manager Larry Steine (Hallie.Peltier@tinker.af.mil & Larry.Steine@tinker.af.mil )

D. Cannibalization shall be allowed to occur between all Delivery Orders with this solicitation (PR/Contract) and across all Delivery Orders of the preceding contract: FA8119-09-D-0007.

1.1.5 Quality System

The Contractor shall develop and maintain a system that adheres to the requirements of International Standard Organization (ISO) 9001.2000/ANSI/ASQC Q92, Quality Systems Model for Quality Assurance in Design/Development, Production, Installation and Servicing and supplement requirements imposed by this contract. The Contractor shall develop and implement procedures to properly maintain measuring and test equipment in accordance with ANSI/NCSL 2340-1. The quality system shall include a clear and complete set of work documents for all maintenance required by this contract. The quality program shall be designed to promptly detect and correct conditions adverse to quality. The Contractor shall provide documentation of quality plan within five (5) business days of Government requests.

1.1.6 Deficiency Reports

The Contractor shall investigate all Deficiency Reports (DRs) submitted against defective items overhauled by the Contractor. The Contractor shall ensure each DR is processed in accordance with (IAW) T.O. 00-35D-54, USAF Deficiency Reporting and Investigating System. When the Contractor receives a DR or quality deficiency report (QDR), the Contractor shall ensure DRs include: Analysis of data to determine extent and cause of deficiencies; analysis of trends in processes or performance of work to prevent recurrence; and introduction of required improvement, corrections, and monitoring of the effectiveness of corrective action taken.

1.1.7 Packaging

The Contractor shall package the B-2 items IAW the Air Force Material Command (AFMC) Form 158 (Packaging Requirements). The Contractor shall place a serviceable tag, Department of Defense (DD) Form 1574(Serviceable Tag – Material), inside the package along with the item. The Contractor shall attach a second DD Form 1574 to the outside of the package. The contractor will be responsible for ordering tags. Information on this can be found at http://navalforms.daps.dla.mil/web/public/home Phone: 1-866-736-7010.

1.1.8 Delivery

The Contractor shall deliver overhauled items under this contract to the destination specified IAW the negotiated delivery schedule of the contract. The Contractor shall ship the serviceable end item to the highest priority mission requirement, unless directed otherwise by Government PCO. The Contractor shall annotate one of the following SRANs directly on the Government Form DD250 (Material Inspection and Receiving Report) for shipping destination; or, the Government may direct Amended Shipping Instructions by utilizing Government Form DD1149 (Requisition and Invoice/Shipping Document). Approved SRANs are: FB2039, FB4625, FB2805, FB4852, FB4503, FB5240, FB5505, & EZ7676.

1.2. Information Requests

The Contractor shall ensure responses to requests for information and data are only provided to customers with a need-to-know in the performance of official duties. All requests between the Government and the Contractor shall go through the PCO.

1.3 Reporting Requirements

The Contractor shall accomplish and furnish all reports in accordance with the reporting requirements specified in the DD Forms1423s, Contract Data Requirements List (CDRL), of this contract.

1.3.1 Asset Visibility Reporting

The Contractor shall report IAW Commercial Asset Visibility Air Force (CAV AF), (DI-MGMT-81634A, CDRL A001). The Contractor shall submit data IAW CAV AF Statement of Work, CAV AF Users Guide, and Appendix B of this contract.

1.3.2 Meetings and Conferences

The Contractor shall attend and support program reviews, technical interchange meetings and working groups as required, to meet the performance objectives for this contract. Direction for these meetings shall only come from the 424 SCMS/GUME. A weekly teleconference is required with the 424 SCMS/GUME. This may be skipped per agreement with the government Contract Repair Team members: Flight Chief, PMS or Logistics Officers with the 424 SCMS/GUME.

1.3.3 Diminishing Manufacturing Sources/Material Shortage and Obsolescence The Contractor shall participate in the DMS/MS program for all Defense Management System (DMS) items by reviewing Problem Part Requests (PPR) and DMS/MS Engineering Requirements Plans (DERP) Reports. The Contractor shall identify and provide recommendations from Original Equipment Manufacturer (OEMs) relating to these activities to support DMS/MS Management Team obsolescence resolution actions. The Contractor shall proactively identify and provide formal recommendations and guidance relating to these activities to support DMS/MS Management Team (DMT) obsolescence resolution actions. This support will include participating in DMT scheduled meetings and providing obsolescence notification to 848 SCMG/PKBC (PCO) and 424 SCMS/GUME Program Manager. The Source Data for Forecasting Diminishing Manufacturing Sources and Material Shortages (DMSMS, DI-SESS-81656A, CDRL A002). Per the CDRL this will be required once a year.

Upon receipt of a Request for Proposal and Performance Work Specification (PWS), the Contractor shall provide the price and schedule for implementing solutions (qualification of substitute parts, emulations, or redesigns) to DMS/MS problems.

1.3.4 Depot Maintenance Production

The Contractor shall develop and deliver the Depot Maintenance Production report for all CFM line items on the contract. (DI-ALSS-80728A, CDRL A007) A sample report is at the end of the CDRLs. See CDRL A002 for more information. Per the CDRL this report will be required once a week.

1.3.5 Quarterly File Maintenance Reviews

The Contractor shall support quarterly file maintenance reviews by providing overhaul projections by National Stock Number (NSN) for the next quarter and the next Government Fiscal Year (FY). The quarterly and the next Government FY projections will be a joint Government-Contractor agreement. The timing of each quarterly meeting is based upon D200/ ABCS file maintenance cycles. Twice a year this review will be at Tinker AFB and Twice a year this will be done at the contractor’s facility.

1.4 Additional Information - N/A

1.4.1 Over and Above

The Contractor shall execute Over and Above at the request of the Contracting Officer in the following areas, any overhaul identified on the B-2 Overhaul Candidate List, surge operations, additional overhauls outside of scope, and any required proposals and estimates in support of the Over and Above efforts as requested or directed by the Contracting Officer.

In addition, at the request of the Contracting Officer, the Contractor will prepare a proposal as necessary (example: includes but is not limited to over and above overhauls, catastrophic overhauls, other activities requested by the USAF and agreed to by the Contractor).

NOTE: Over and Above situations will be dealt with on a case by case basis jointly between the Government and the Contractor

1.5.0 End Item Identification and Marking

Permanently and legibly mark each overhauled end item with the contractor's identification. This identification shall include the contractor's CAGE and the date of overhaul. The identification shall be permanently affixed to the end item by stamp, stencil, or similar means.

Item Unique Identification (IUID) will be added to the end item in accordance with the following:

a. Specification requirements for IUID marking will be contained in the applicable overhaul technical order, Specific Work Requirements appendix, approved engineering drawing, or a Government provided Engineering order as applicable.

b. IUID markings are required for the end-item only, not for subcomponents to the end-item unless specifically identified in the applicable overhaul technical order, Specific Work Requirements appendix, approved engineering drawing, or a Government provided Engineering order.

c. Items that do not have IUID marking specifications as stated in paragraphs above will not be marked without them. At which time the marking specifications are developed, the IUID requirement will be negotiated and a subsequent bilateral modification will be performed.

d. IUID markings currently in place on items undergoing overhaul shall be protected from damage or removal during overhaul. Verify 2-D matrix IUID markings are readable per TO 00-25-260. Should IUID marking be rendered unreadable during overhauls, the contractor shall notify 424 SCMS engineering and the PCO/ACO for determination of how to replace the IUID mark.

e. The contractor shall submit the required and applicable contingent data for legacy items to the IUID Registry per the data submission procedures at http://www.acq.osd.mil/dpap/pdi/uid/data_submission_information.html.

SECTION II – SERVICE SUMMARY

The Contractor shall be aware that the absence of any contract threshold from the Service Summary does not detract from its enforceability nor limit the rights or remedies of the Government under any other provision of the contract. The Government will use the surveillance methods contained in Surveillance Plan to evaluate the Contractor’s performance for the performance objectives listed below. In the event the performance objective is not met, the Contractor shall be given a 45 business days after notification to correct the unacceptable performance, if such correction is possible. The Contractor shall immediately take corrective action IAW the performance threshold(s). In cases where the Contractor fails to implement corrective action, the PCO will take contracting action.

2.1 Service Summary (SS) Requirements

The Contractor shall ensure the performance objectives, performance thresholds, and support for surveillance methods are achieved as follows:

2.1.1 Performance Objectives and Thresholds

The Contractor shall achieve performance thresholds identified in Table 2-1 of this PWS.

NOTE: The performance thresholds are designed to:

NOTE: OC-ALC Tinker AFB will exercise surveillance over the performance thresholds.

2.1.2 Surveillance Methods

The Contractor shall support the surveillance methods as identified below.

c. Periodic Inspection

2.2 Contractor Performance Evaluation

The Contractor shall support periodic Government quality assurance surveillance to evaluate performance.

NOTE: In the event the performance measure is not met, Contracting Officer Representative (COR) or the PCO will issue written notification to the Contractor.

Table 2-1

SS-1. Quality Product:

The Contractor shall investigate all Deficiency Reports (DRs) submitted against defective items overhauled by the Contractor.

SS-2. Delivery Performance:

The Contractor shall deliver overhauled items under this contract to the destination specified within the negotiated delivery schedule of the contract.

PWS

Para 1.1.6

PWS

Para 1.1.8

Only one deficiency per 12 month period is acceptable.

100% of end-item shall be delivered IAW the contractual delivery schedule.

3. SECTION III - GOVERNMENT FURNISHED PROPERTY

3.1 Government Furnished Material (GFM)

This is a standalone contract, the contractor shall furnish their own material, & no GFM will be provided, except for GFM inventory in the bond room. As this material is burned down it will be the contractor’s responsibility to replenish stock as CFM. The Contractor shall retain all GFM, as Government property, in a secured storage area.

3.1.1 GFM & Bond Room Reporting

The Contractor shall provide a quarterly B-2 DMS Overhaul Production and bond room Asset Report. for end of months, 31 Dec, 31 Mar, 30 Jun and 30 Sep, no later than the 13th of January, April, July and October, respectively. The report shall contain but not be limited to, the following information: National Stock Number (NSN), part number, nomenclature, serial number, quantity received, quantity inducted, quantity shipped, CLIN/ELIN, Repair Order, Delivery Order, Location/SRAN, condition, status, Source of Repair (SOR), date received, date inducted and date shipped. The overhaul status shall be cumulative. The Contractor’s format is acceptable and all required information should be made available on one report to the Government in a Microsoft® Excel spreadsheet.

3.2 Government Furnished Equipment (GFE)

While the GFE is in the possession of the Contractor, the Contractor shall be responsible to provide routine maintenance, calibration, and minor repair of the GFE to ensure the GFE is returned to the Government in the same condition as when provided, less normal wear and tear. An annual report with the quantity, condition, PN and SN of all GFE is required.

ATTACHMENT 1 DEFINITONS

Administrative Contracting Officer (ACO): A contracting officer assigned the responsibility for the post award functions related to the administration of a government contract in the field. The ACO is normally located in the Defense Contract Management Agency (DCMA) office. The ACO is responsible for ensuring the contractor performs in accordance with the terms of the contract.

Commercial Asset Visibility Air Force (CAV AF) System: CAV AF is the system of record for providing daily status of Government owned assets located at Contractors facilities.

Contractor Furnished Material (CFM): Material provided by the contractor, as a part of the maintenance service provided. All material with an expendability, recoverability, and reparability category (ERRC) code; N or P (also known as consumables) will be CFM, regardless of the source of supply (SOS), i.e; Defense Logistics Agency (DLA), General Support Division (GSD) and AF managed items. This material is incorporated into or attached to an end item to be delivered under the contract or may be consumed in the performance of a contract.

Contract Manager: Contractor personnel who shall be responsible for the performance of the work and have full authority to act for the Contractor on all matters relating to the performance of this contract.

Government Furnished Equipment (GFE): An all-inclusive term to define all types of equipment defined in FAR, Part 45. It includes facilities, plant equipment, agency peculiar property, special tooling, and special test equipment. For the purpose of annually reporting dollar values on Department of Defense (DOD) property in the custody of contractors (DD Form 1662, DOD Property in the Custody of Contractors), items must be categorized according to the specific FAR property definitions.

Government Property: All property owned by or leased to the Government or acquired by the Government under the terms of the contract. It includes both Government-furnished property and Contractor-acquired property. This includes facilities, material, special tooling, special test equipment, and agency-peculiar property.

Government Furnished Material: Property that may be incorporated into or attached to a deliverable end item or that may be consumed or expended in performing a contract. This includes, assemblies, components, parts, raw materials, and small tools, and supplies that may be consumed in normal use in performing a contract.

Government Furnished Property: Property in the possession of, or directly acquired by the Government and subsequently made available to the contractor.

Procuring Contracting Officer (PCO): The person with the authority to enter into a contract on behalf of the government. The PCO will ordinarily be located at the funding ALC.

Production Management Specialist (PMS): An individual assigned by the contracting activity to act as liaison for production, supply, and transportation issues.

Quality Manager: Personnel who are responsible for managing the quality assurance system, scheduling and directing inspections and audit activities, developing and implementing corrective and preventive actions, developing and providing quality inspection and audit metrics, and for executing quality plans.

Quality Systems: Model for Quality Assurance in Production, Installation, and Servicing.

Special Test Equipment (STE): Electrical, electronic, hydraulic, pneumatic, mechanical, or other items or assemblies of equipment which are of such a specialized nature that, without modification or alteration, the use of such items (if they are to be used separately) or assemblies is limited to testing in the development or production of particular supplies or parts thereof, or in the performance of particular services. The term special test equipment includes all components of any assemblies of such equipment but does not include consumable property, special tooling, or buildings, non-serviceable structures (see FAR 45.101, except foundations and similar improvements necessary for the installation of special test equipment), general or special machine tools, or similar capital items.

Cannibalization: Authorized removals of a specific assembly, subassembly, or part from one weapon system, system, support system, or equipment end-item for installation on another end-item to meet priority mission requirements with an obligation to replace the removed item at no additional cost to the government.

File Number: OC/B2/FD2030-11-37101 13

ATTACHMENT 2 APPLICABLE DOCUMENTS

A. General Information The Contractor shall ensure requirements in this PWS are accomplished IAW the latest version of the following documentation if it does not impact cost and delivery schedules or if a conflict does not arise in implementation of the new procedures. If any of the preceding conditions occur, a written evaluation, along with specific backup data and estimated cost data for those changes which impact the Contractor’s performance shall be provided to the PCO within ten (10) workdays after receipt of an updated publication. The Contractor shall not incorporate these publication changes until approved by the PCO. In the event there are conflicts between two or more referenced documents, the Contractor shall provide written evaluation, along with specific backup data to the PCO within ten (10) workdays after knowledge of the conflict. Resolution of the conflict will be provided by the PCO. In addition, the Contractor shall immediately implement those publication changes that result in no change in contract price or delivery or have no conflicts.

GENERAL TECHNICAL ORDERS

00-5-1

15 Oct 06

AF Technical Order System

00-20-2 Change 2 15 Jun 03 15 Apr 07 Maintenance Data Collection

00-20-3 Change 1 1May 04 31 Dec 04 Maintenance Processing of Reparable Property and Repair Cycle Asset Control System

00-25-234 Change 35

1 Aug 88 12 Jul 06 General Shop Practice for the Repair Maintenance and Test of Electrical Equipment

00-35D-54

1-1-689-1

1 Mar 05

Avionic Cleaning and Corrosion Prevention/Control

00-25-203 Change 17 1 Dec 72 1 May 07 Contamination Control of Aerospace Facilities U. S. Air Force

5-1-1

OTHER PUBLICATIONS FOR GUIDANCE PURPOSES ONLY

AIR FORCE MANUALS

AFMAN 23-110

AIR FORCE MATERIAL COMMAND INSTRUCTIONS AND MANUALS

MILITARY SPECIFICATIONS, STANDARDS, HANDBOOKS, AND NON-GOVERNMENT STANDARDS

FORMS

CAV AF CFM

STATEMENT OF WORK

The purpose of this statement of work (SOW) is to provide Contract Depot Maintenance (CDM) guidance for contractor technical, responsibilities and reporting requirements of the Commercial Asset Visibility Air Force (CAV AF) system. CAV AF shall be the primary system of record for providing daily status of all Government owned assets located at contractors facilities. Reporting within CAV AF shall not be limited to end items subject to repair but are to include assets stored as an inventory control point (ICP). Equipment identified as Government Furnished Equipment (GFE) may be reported within CAVAF. Enhancements to the CAV AF system will be identified on the CAV AF home web page. Contractors are responsible for ensuring current User Guides are utilized by their respective facility.

TECHNICAL CONSIDERATIONS:

1. Contractors accessing CAV AF shall present a valid DoD PKI certificate to log into CAV AF. Contractors working at DoD facilities, who have a common access card (CAC), should already have a PKI certificate. Contractors working outside of DoD facilities can purchase a valid DoD PKI certificate through one of three External Certificate Authorities (ECAs). A listing of ECAs and additional information on purchasing a valid DoD PKI can be found at the following web site: http://iase.disa.mil/pki/eca/ . Each contractor employee accessing CAV AF will need an Identity Certificate only; an Encryption Certificate is not required.

2. Utilizing subcontractors in the repair of government assets in partnership by the awarded prime contractor shall conform to all applicable reporting requirements contained within this contract. Inherently, the awarded prime contractor shall bear sole responsibility for all reporting actions.

3. CONTRACTOR RESPONSIBILITY OF CAV AF HARDWARE AND SYSTEM ACCESS: It is the contractor’s responsibility to ensure systemic connectivity with CAV AF system is achieved and reporting capability is successful. When contractor experiences connectivity problem after receiving initial contract delivery order they should contact the Inventory Control Point (ICP) CAV AF System Administrator (SA) within 24 hours.

CONTRACTOR RESPONSIBILITY:

1. Contractor reporting requirements to CAV AF shall be accomplished daily and/or within 24 hours of a supply or maintenance action occurrence IAW the applicable CAV AF CDRL, CAV AF version 7.2 or higher Contractor Users. Accurate and timely reporting of maintenance transactions into CAV AF is critical to the management of repair requirements and the management of world-wide asset distribution. CAV AF transmits daily to Air Force internal data systems for financial and asset tracking. Inaccurate or lack of CAV AF reporting will cause significant loss to the Air Force. Contractor shall ensure asset record in CAV AF is an accurate reflection of physical asset on hand at all times.

2. Proper usage of DD Form 1348-1A, Issue Release/Receipt Document in relation to CAVAF reporting requirements.

a. Receipt Actions: Contractor will use government issued shipment document numbers for CAV AF end item receipt transaction reporting only in the absence of missing DD Form 1348-1A or shipment document number. Contractors are not authorized to generate pseudo shipment document numbers for receipt transactions because this creates disconnects in shipment tracking within government inventory systems.

b. Shipping Actions: DD Form 1348-1A shall be used as the shipping document for shipment transactions of all end items. A DD Form 1348-1A is also applicable to all Consolidated Serviceable Inventory/Consolidated Reparable Inventory (CSI/CRI) assets regardless of tracking or reporting purposes. DD Form 250 or DD Form 1149 are not acceptable or authorized as a shipment document, and shall not accompany any material shipments on repair contracts. DD Form 1348-1A shipping documents will be prepared for each NSN shipment from contractor’s facility, regardless of destination. The entire form, complete with bar coding, will be printed on a laser printer as specified under technical considerations. Two copies of the DD Form 1348-1A are provided by CAV AF. Place one copy on the outside of the shipment container and one copy inside the shipment container. For end item shipments the DD Form 1348-1A shipment document number shall be comprised as one of the following actions:

i. Back to Depot Shipments:

(1) For a “single” unit NSN shipment, the default shipment document number will be the CAV AF record control document number (RCDN) of item being shipped.

(2) For “multiple” quantity shipments, it is recommended the CAV AF RCDN of the lead item of the shipment be used as the shipment document number.

ii. Amended Shipping Instructions (ASI): Are used to divert material that is due-in from a contractor to a requisitioner. Government disposition instructions will provide a shipment document number to the contractor to be utilized for CAV AF shipment transaction reporting and the DD Form 1348-1A.

NOTE: In the event CAV AF system is inoperable, DD Form 1348-1A shall be manually generated (printed) by contractor. When CAV AF is again operable, the contractor shall complete a DD Form 1348-1A and the shipment process in CAV AF.

3. Contract/Delivery Order Closure Level Disposition Instructions – Government will provide disposition instructions to contractor. Contractor shall comply with disposition instructions within 10 days of receipted government instructions and shall have complied no later than 30 days after receipt of instructions. Contractor shall be fully responsible to ensure all corresponding CAV AF reporting actions associated with disposition instructions occur within 24 hrs of related shipment action.

4. Contractual Induction-at-Risk of end items is prohibited on all repair contracts.

5. All NSNs identified as Nuclear Weapon Related Material (NWRM) shall require contractor reporting utilizing CAV AF for production management, to track and report NWRM end items in repair to the Serial Number level. Contractors shall capture each NWRM assets Serial Number when reparable is received. NWRM assets received shall be receipted in CAV AF, with Serial Number identification within 24 hours for asset visibility and serial number tracking. Contractors shall follow all NWRM management requirements outlined in AFI 20-110, NWRM Management, to include but not limited to packaging, marking, labeling, storage, transportation and receipt of all NWRM assets, with emphasis on positive inventory control (PIC) and records management by the contractor and government to assure compliance. The successful application of these procedures requires the full cooperation of all personnel associated with the storage, shipping, transshipping and receiving of all NWRM assets.

CAVAF CONTRACTOR TRANSACTION REPORTING REQUIREMENTS:

1. “Not-on-Contract” receipt transactions shall be utilized for assets which are not repair end items. Not-on-contract assets are associated to a contractor facility DoDAAC and not an active contract delivery order. Regardless of asset condition code status, Not-on-contract shall be used for the following reporting actions:

a. Discrepancy Items – Are identified as misrouted, shipments, misidentified shipments or damaged end items. Contractor will address discrepancy issues weekly to acquire resolution to discrepancy within 30 days of receipt transaction. The contractor shall comply with disposition instructions provided by the Government within 10 days and complete all associated reporting actions within same period. Contractor reporting actions shall be resolved using reversals of individual record document control numbers (RCDN) or may be accomplished utilizing a ‘bulk’ shipment action of RCDN.

b. Inventory Control Point Items – are identified as assets stored at contractor facility and are not repair end items or discrepancies items. Movement of assets from “Not-on-Contract” category shall be resolved using reversals of individual record document control numbers (RCDN) or may be accomplished utilizing a ‘bulk’ shipment action of RCDN.

NOTE: Contractor is responsible for all “Not-on-Contract” assets ensuring physical asset balances are reflected and CAVAF reporting actions occur within 24 hr of supply action.

NOTE: Not-on-Contract receipt actions will not be utilized for quality deficiency report (QDR) items.

CAUTIONARY AREAS OF CONTRACTOR CAV AF REPORTING:

1. Systemic data problems created by contractor’s failure to report data accurately or in a timely manner are subject to immediate Program Management Review (PMR). Examples of documented system data problems include but are not limited to:

a. Timely reporting means compliance with 24 hour requirement for contractor CAV AF reporting of maintenance transactions. Contractor’s are not authorized to report all receipt, induction, complete and ship transactions the same day to ‘catch-up’ due to periodic reporting. This affects government inventory management systems and balances creating D035 Stock Control Supply System (SCSS) controlled exceptions (associated with same day reporting issue).

b. Contractors not using government issued DD Form 1348-1A document numbers on CAV AF contractor reporting on end item receipt transactions. This creates a data variance disconnect with government inventory D035 Stock Control System (SCS). Contractors are required to use DD Form 1348-1A document numbers for end item receipt transactions. NOTE: If the DD Form 1348-1A is missing or no shipment document number is available, contractors are to immediately contact Production Management Specialist (PMS) and acquire government issued shipment document number from Inventory Management Specialist (IMS).

DISCREPANCIES INCIDENT TO SHIPMENT:

1. There are transportation and item discrepancies, each having different reporting requirements. Detailed information for each report is in the pertinent service publications.

2. Discrepancies incident to shipment include misidentified items, variations in quantity, non-requisitioned items, lost or damaged parcel post, and items in dubious condition. These discrepancies shall be reported and resolved using the DoD web-based application WebSDR link located within the CAV AF system. The Web address for Online CAV AF access is: https://www.cavaf.com This system of reporting a Supply Discrepancy Report (SDR), formerly called Report of Discrepancy (ROD), has been developed in compliance with DoD regulations 4140.1-R and 4000.25-M Volume 2, which requires automated SDR processing. In those situations where the SDR initiator is unable to gain access to the AF WebSDR, continued use of manual forms is permitted. A copy of the form will be forwarded through the CAO and Quality Assurance (QA) activity for corrective action.

3. Transportation discrepancies and item transaction discrepancies shall be coordinated with the DCMA Property Administrator and ACO immediately upon discovery for corrective action in addition to AF WebSDR submittal.

4. Contract line items received with missing components (Missing On Induction, (MOI)) the contractor shall process a SDR (SF Form 364) immediately upon discovery in accordance with AFJMAN 23-215 and provide a copy of submitted MOI SDR form to the ACO within 2 days of discovery.

5. Misdirected shipments of GFP shall be immediately reported by telephone to the Property Administrator (PA) followed by written notification within three work days. The PA will issue appropriate disposition instructions for the misdirected items. Misdirected items received by the contractor which are not part of this contract will not be receipted into CAV AF.

6. Overages, shortages, and misidentified items which are part of this contract and received by the contractor shall be reported into CAV AF with the actual received quantity and with the correct NSN. An SDR shall be processed in accordance with standard procedures identified above for these overages, shortages, and misidentified items.

ATTACHMENT 1

CONTRACTOR COMMUNICATIONS NETWORK (CCN)

1. GENERAL INFORMATION:

1.1. The purpose of this attachment is to provide the specific conditions, hardware specifications, and communications interface to support contractor End Item reporting requirements and supply requisitions. Through the CCN Air Force contractors, with aircraft, engine or equipment repair contracts, have the capability to electronically process End Item transactions.

1.2. Initial CAV AF training will be provided by the contracting ALC. Any follow up training will be the responsibility of the contractor. For training and/or questions on CAV AF, please contact CAV AF Contract Manager (CM) for contract issued by respective ALC, from one of the following areas:

1. Warner Robins AFB, GA, call (478) 327-6602 or 327-6603, or send email request to: 406scms.cav.af.ar@robins.af.mil

1. Hill AFB, UT, call (801) 777-4803 or 775-6403

1. Tinker AFB, OK, send e-mail request to 428scms.cdmwork@tinker.af.mil, please ensure applicable Tinker contract number is included. A CAVAF representative will contact you for training and/or questions.

NOTE: Contractor’s guide can be accessed via CAV AF main menu at bottom of screen.

2. WEB SITE:

2.1. CAV AF web site accessed through the internet will be used to submit all End Item transactions. Each contractor user shall be required to complete a System Authorized Access Request, DD Form 2875, prior to using CAV AF.

2.2. The Web address for Online CAV AF access is: https://www.cavaf.com

2.3. The DLA/DAASC front-end computer at Wright-Patterson AFB, Ohio will act as host for GFM requisitions and MILSTRIP Status updates processed through CAV AF as batch end-of-day/beginning-of-day transactions.

3. CICA XML: Commercial vendors with XML capability on their in-house systems will be able to transmit XML batch files via a DLA/DLMSO format known as CICA XML. CAV AF XML files are transmitted via the Defense Automatic Addressing System Center (DAASC) network. DAASC receives, edits, and routes logistics transactions for the Military Services and Federal Agencies. There is only one way to access DAASC:

a. Use the services of a Value Added Network (VAN), with a current access/connectivity DAASC license agreement

3.1 Establishing an access/connectivity license agreement with a VAN/DAASC is an initial and essential action requiring execution at the earliest opportunity. Once this has been accomplished, DAASC will need to know the ISA/GS addressing id’s for each contractor so the information can be setup. Depending on the VAN selected, DAASC main ISA id is DTDN.

VAN https://www.daas.dla.mil/daashome/edi-vanlist-dla.asp DAASC https://www.daas.dla.mil/sar/gex_sar.asp

VAN/DAASC connectivity related information is located on a DLA dot mil domain and contractors will require Air Logistic Center CDM personnel assistance to gain access to the site. This coordinated effort is required with either VAN or DAASC access the contractor pursues. Contractor sponsorship requirements exist where contractors requesting DAASC access must be sponsored by their U.S. Government Contracting Officer or Contracting Officer's Representative. Close coordination between the Air Logistics Center's (ALC) CAV AF System Administrator (SA) and the contractor's programmer is required.

NOTE: Contractors will report their repair transactions to CAV AF either by CAV Web or CAV XML. Both methods cannot be utilized at the same time. When the Air Logistics Center's (ALC) CAV AF System Administrator loads the Contractor's Profile into CAV AF a reporting decision is made whether a contractor uses CAV Web or CAV XML reporting.

3.2. Contractor shall contact CAV AF CM (listed above; para 1.2.) to obtain most recent XML lessons learned document. Document contains recorded issues/problems and may alleviate anticipated problem areas associated to XML.

4. TECHNICAL CONSIDERATIONS:

4.1. Contractors accessing CAV AF shall present a valid DoD PKI certificate to log into CAV AF. Contractor’s working at DoD facilities who have a common access card (CAC), should already have a PKI certificate. Contractors working outside of DoD facilities can purchase a valid DoD PKI certificate through one of three External Certificate Authorities (ECAs). A listing of ECAs and additional information on purchasing a valid DoD PKI can be found at the following web site: http://iase.disa.mil/pki/eca/ . Each contractor employee accessing CAV AF will need an Identity Certificate only; an Encryption Certificate is not required.

4.2. The CAV AF program is designed to be accessible using Microsoft Internet Explorer (IE6) v6.0 or higher or Netscape 4.75 or higher on a Windows 2000 or newer platform. IE6 is suggested and contains the required 128-bit encryption capability, and DoD certification. The following hardware is suggested as a minimum to adequately support CAV AF reporting with a minimum system requirement using Windows 2000 or newer platform: IBM compatible PC (1.5 GHZ Pentium), 512 MB RAM, 20 GB hard drive, 56 K BPS or faster data transmission modem, or connection to WAN/LAN, Laser Printer with 300 DPI resolution, (must support true type font).

4.3. The following software is required to accomplish CAV AF Web-based reporting: Operating System: Windows 2000 or Windows XP, Web Browser: Internet Explorer, version 6.0 (preferred), or Netscape version 4.75 (or higher) is also compatible.

4.4. CAV AF Web-based software will reside on the AF mid-tier server. CAV AF software changes will be made at the mid-tier server and they will be available to the repair vendor upon log-on to the CAV AF system. Changes to CAV AF software by the commercial repair vendors are not authorized.

5. CONTRACTOR RESPONSIBILITY:

5.1. The contractor shall be responsible for the maintenance of the hardware and supplies (paper, ink, ribbons, extra disks, etc) to keep the PC system operational and compatible with the host computer.

5.2. The contractor shall use the CCN/CAV AF Reporting System to report all end item transactions. These transactions shall be entered into CAV AF on a real time basis or as changes generate, but not later than 24 hours from the date of occurrence.

5.3. System failures that cannot be corrected within 24 hours shall be reported to the contracting ALC by fastest means possible.

6. SYSTEM AUTHORIZED ACCESS REQUEST (SAAR):

6.1. The SAAR, DD Form 2875, shall be completed by the contractor and submitted to the managing ALC CAV AF POC. A blank SAAR, DD Form 2875, and instructions on how to complete the form are identified below in the WORD document instruction.

6.2. Send DD Form 2875 to the respective ALC CAV AF System Administrator POC listed below:

1. Warner Robins AFB, GA, FAX (478) 926-4241

1. Hill AFB, UT, FAX (801) 777-5692

1. Tinker AFB, OK, send e-mail request to 428scms.cdmwork@tinker.af.mil, please ensure applicable Tinker contract number is included. A CAVAF representative will contact you for training and/or questions.

6.3. CAV AF user IDs will be in a standard format for all users. The user ID and initial password normally will be emailed. Users will be required to change password following system entry. Users requiring password resets should contact the System Administrator POC listed below:

a. Warner Robins AFB, GA, call (478) 327-6602 or 926-2760

b. Hill AFB, UT, call (801) 777-4803 or 775-6403

c. Tinker AFB, OK, send e-mail request to 428scms.cdmwork@tinker.af.mil, please ensure applicable Tinker contract number is included. A CAVAF representative will contact you for training and/or questions.

File Number: OC/B2/FD2030-11-37101 25 image1.emf

Instructions for 2875 Instructions for 2875

Input Date on Top Right block

Fill out blocks 1-6, 8-10 (Block 2 should be last 4 of SSN only)

Leave IA block blank.

Fill out blocks 11-12.

Check block 16

Block 16a – Company Name and DODAAC (EZXXXX) – we need both – if they don’t fit in this block, put them in block 27.

Fill out blocks 17-20b

In block 27, put “User” if you will be inputting to the system and “View Only” if you will only be viewing the data in the system.

In block 27, applicant must indicate which ALC issued repair contract they are applying access for and contract number, if available.

Supervisor/Security Manager fills out 28-28b and 29-32 if info is available – Should be either investigation for security clearance or background investigation

Fax to our office at (405) 736-5308 image2.emf dd2875 Blank.pdf

SYSTEM AUTHORIZATION ACCESS REQUEST (SAAR)

PRIVACY ACT STATEMENT

Executive Order 10450, 9397; and Public Law 99-474, the Computer Fraud and Abuse Act.

To record names, signatures, and Social Security Numbers for the purpose of validating the trustworthiness of individuals requesting access to Department of Defense (DoD) systems and information. NOTE: Records may be maintained in both electronic and/or paper form.

None.

Disclosure of this information is voluntary; however, failure to provide the requested information may impede, delay or prevent further processing of this request.

TYPE OF REQUEST

INITIAL MODIFICATION DEACTIVATE

DATE (YYYYMMDD)

PART I (To be completed by Requestor)

1. NAME (Last, First, Middle Initial) 2. SOCIAL SECURITY NUMBER

3. ORGANIZATION 4. OFFICE SYMBOL/DEPARTMENT

9. CITIZENSHIP

7. JOB TITLE AND GRADE/RANK

5. PHONE (DSN or Commercial)

I accept the responsibility for the information and DoD system to which I am granted access and will not exceed my authorized level of system access. I understand that my access may be revoked or terminated for non-compliance with DoD security policies. I accept responsibility to safeguard the information contained in these systems from unauthorized or inadvertent modification, disclosure, destruction, and use. I understand and accept that my use of the system may be monitored as part of managing the system, protecting against unauthorized access and verifying security problems. I agree to notify the appropriate organization that issued my account(s) when access is no longer required.

11. USER SIGNATURE 12. DATE (YYYYMMDD)

PART II - ENDORSEMENT OF ACCESS BY INFORMATION OWNER, USER SUPERVISOR OR GOVERNMENT SPONSOR (If individual is a contractor - provide company name, contract number, and date of contract expiration in Block 16.)

16a. ACCESS EXPIRATION DATE (Contractors must specify Company Name, Contract Number, Expiration Date. Use Block 27 if needed.)

18. SUPERVISOR'S SIGNATURE17. SUPERVISOR'S NAME (Print Name) 19. DATE (YYYYMMDD)

14. TYPE OF ACCESS REQUIRED:

AUTHORIZED PRIVILEGED

15. USER REQUIRES ACCESS TO: UNCLASSIFIED CLASSIFIED (Specify category)

13. JUSTIFICATION FOR ACCESS

16. VERIFICATION OF NEED TO KNOW

I certify that this user requires access as requested.

22. SIGNATURE OF IAO OR APPOINTEE

20. SUPERVISOR'S ORGANIZATION/DEPARTMENT 20b. PHONE NUMBER

25. DATE (YYYYMMDD)

21. SIGNATURE OF INFORMATION OWNER/OPR

23. ORGANIZATION/DEPARTMENT

21a. PHONE NUMBER 21b. DATE (YYYYMMDD)

8. OFFICIAL MAILING ADDRESS

6. OFFICIAL E-MAIL ADDRESS

DD FORM 2875, APR 2005 PREVIOUS EDITION IS OBSOLETE.

USER ID

SYSTEM NAME (Platform or Applications) LOCATION (Physical Location of System)

10. DESIGNATION OF PERSON

OTHER

24. PHONE NUMBER

AUTHORITY:

PRINCIPAL PURPOSE:

ROUTINE USES:

DISCLOSURE:

USER AGREEMENT

IA TRAINING AND AWARENESS CERTIFICATION REQUIREMENTS (Complete as required for user or functional level access.)

I have completed Annual Information Awareness Training. DATE (YYYYMMDD)

20a. SUPERVISOR'S E-MAIL ADDRESS

US FN

OTHER

MILITARY CIVILIAN

CONTRACTOR

Adobe Designer 7.0

DD FORM 2875 (BACK), APR 2005

PART IV - COMPLETION BY AUTHORIZED STAFF PREPARING ACCOUNT INFORMATION

PROCESSED BY (Print name and sign) DATE PROCESSED

(YYYYMMDD)

DATE (YYYYMMDD)

27. OPTIONAL INFORMATION (Additional information)

SYSTEM

DOMAIN

SERVER

APPLICATION

DIRECTORIES

FILES

DATASETS

TITLE: ACCOUNT CODE

REVALIDATED BY (Print name and sign) DATE (YYYYMMDD)

28b. CLEARANCE LEVEL

28. TYPE OF INVESTIGATION

PART III - SECURITY MANAGER VALIDATES THE BACKGROUND INVESTIGATION OR CLEARANCE INFORMATION 28a. DATE OF INVESTIGATION (YYYYMMDD)

28c. IT LEVEL DESIGNATION

31. SECURITY MANAGER SIGNATURE29. VERIFIED BY (Print name) 32. DATE (YYYYMMDD)

26a. NAME (Last, First, Middle Initial) 26b. SOCIAL SECURITY NUMBER

LEVEL I LEVEL II LEVEL III

30. SECURITY MANAGER

TELEPHONE NUMBER

DATE REVALIDATED

A. PART I: The following information is provided by the user when establishing or modifying their USER ID.

(1) Name. The last name, first name, and middle initial of the user.

(2) Social Security Number. The social security number of user.

(3) Organization. The user's current organization (i.e. DISA, SDI, DoD and government agency or commercial firm).

(4) Office Symbol/Department. The office symbol within the current organization (i.e. SDI).

(5) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, indicate commercial number

(6)Official…