FD20201701531_CAVAF.pdf

CAVAF STATEMENT OF WORK

CONTRACTOR FURNISHED MATERIAL

The purpose of this Statement of Work (SoW) is to provide Contract Depot Maintenance (CDM) guidance to all repair contractors who are interested in doing a proposal for an Air Force repair contract. Information presented in this Statement of Work covers technical responsibilities and reporting requirements for the Commercial Asset Visibility Air Force (CAVAF) system. A full understanding of CAVAF and what is required of the contractor is essential to the successful completion of a repair contract with CAVAF reporting. CAVAF is the primary system of record for providing daily status of all Government owned assets located at a contractors facility as shown in attachment 1. Reporting within CAVAF shall include but is not limited to production reporting for items/assets subject to repair, and reporting of items/assets stored at an Inventory Control Point (ICP). Enhancements to the CAVAF system shall be identified on the CAVAF home web page and shall be included in the most recent CAVAF user’s Guide. Any contractor repairing items/assets on a contract for the Government (Air Force) with CAVAF reporting shall be responsible for ensuring that the current CAVAF user’s Guide is utilized at their respective facility.

CAVAF REPORTING WAIVER:

A CAVAF reporting waiver may be granted to a contractor if the waiver is applied for by the contractor, and the contractor can show adequate cause for requiring the reporting waiver. All CAVAF reporting waiver requests must be submitted through Procuring Contracting Officer (PCO) during the solicitation process and shall not be accepted and/or considered after the contract is awarded. Each CAVAF reporting waiver must explain, in detail, why the contractor cannot or will not do the CAVAF reporting. All CAVAF reporting waiver requests shall be reviewed, and scrutinized by the PCO, Contract Repair Team (CRT), and CAVAF Contract Manager (CM) assigned to the contract to be awarded. A CAVAF reporting waiver decision shall be based upon looking at “what is in the best interest of the Government (Air Force) criteria”, information presented in the waiver request by the contractor, and other factors such as past CAVAF reporting history of the contractor, company size, number of items/assets to be repaired, and total value of the contract. Once a decision has been made, the answer shall be sent back to the PCO for distribution. If a CAVAF reporting waiver is granted, the contractor shall be under full obligation to prepare and send all required production/asset repair information in an approved format to a selected Air Force CAVAF reporter under the same timelines and/or priorities as if the contractor were doing the CAVAF reporting themselves as shown in attachment 8. Under no circumstances shall a CAVAF reporting waiver be granted to a contractor currently reporting through the CAVAF system. A CAVAF reporting waiver may be granted at any time on rare occasions when unanticipated/unexpected circumstances will cause hardship on the contractor and/or the Government (Air Force).

CAVAF REPORTER REQUIREMENT:

Timely, documented, and accurate item/asset inventory reporting is crucial to Air Force operations and is a requirement mandated by Congress, the Department of Defense (DoD), and the Air Force under the Financial Improvement Audit Readiness (FIAR) Act. All contractors considering and/or preparing a solicitation for this contract must have a CAVAF reporter and CAVAF reporting capability available at the time that the contract is awarded. An exception shall be given if the contractor has applied for, received approval notification, and is awaiting the arrival of a Public Key Infrastructure (PKI) certificate. However, the PKI awaiting arrival exception must be taken care of within seven calendar days of the contract award and must be approved by the Procuring Contracting Officer (PCO) prior to the contract award. An exception shall also be given to this requirement when a CAVAF reporting waiver has been granted. However, a CAVAF reporting waiver must be obtained/approved prior to the award of the contract.

CAVAF TRAINING:

Initial CAVAF training shall be provided on all awarded contracts by the contracting Air Logistics Complex (ALC) CAVAF Contract Monitor (CM). Any follow up or additional training shall be the responsibility of the contractor who may contact the CAVAF CM to perform any additional training needed. Specific assistance, guidance or questions on contractual reporting requirements shall also be addressed to CAVAF Contract Manager (CM) for help. The names and contact information for ALC CAVAF (SA and/or CM) points of contact are found in attachments 3 and 4.

CAVAF USER ID APPLICATION PROCESS:

The CAVAF user ID application process consists of two (2) steps.

1. In the first step, there are four (4) requirements which must be accomplished and/or updated by all CAVAF users no later than seven (7) calendar days after contract award.

a. All CAVAF system users shall be required to have an active PKI certificate. Only an Identity Certificate is needed. An Encryption Certificate is not required. PKI requirements are different for contracts awarded to foreign contractor repair facilities outside the US including Alaska and Hawaii. The contractor shall determine which PKI certification is necessary for their contract. All new CAVAF users shall obtain the necessary PKI certification prior to contract award unless there is an exception as explained in the CAVAF reporter section of this document. Previous CAVAF users shall check to see if their PKI is still active or if it has expired. An expired PKI certificate must be replaced with a new PKI certificate prior to the closure of an open contract in which CAVAF reporting still needs to be done or prior to a new contract award is the current PKI has expired.

Information for PKI certificates can be found in attachment 2.

b. All new CAVAF system users shall complete the DoD Information Assurance (IA) Cyberawareness Challenge training and submit a course completion certificate. This may be accomplished while waiting for the back ground check and validation of the PKI certification. The DoD Information Assurance (IA) Cyberawareness Challenge is a yearly training requirement. Previous CAVAF users must check with the CAVAF System Administrator at the applicable Air Logistics Complex (ALC) to see if their most recent the DoD Information Assurance (IA) Cyberawareness Challenge certificate is still current and active. If the training has expired, the CAVAF user must retake the training and submit a new certificate prior to a new contract award. Information for the DoD Cyberawareness Challenge training can be found in attachment 2 of this document.

c. All first time CAVAF users shall fill out an Air Force Users Agreement Statement (AF Form 4394). This may be accomplished while waiting for the back ground check and validation of the PKI certification. Previous CAVAF users must check with the CAVAF System Administrator at the applicable ALC to see if their most recent AF Form 4394 is still current and active. If the AF Form 4394 has expired, the CAVAF user must complete and submit a new form prior to a new contract award. Information for the AF Form 4394 can be found in attachment 2 of this document.

d. All first time CAVAF users shall fill out a Department of Defense (DoD) System Authorization Access Request

(DD Form 2875). This may be accomplished while waiting for the back ground check and validation of the PKI certification. Previous CAVAF users must check with the CAVAF System Administrator at the applicable ALC to see if their most recent DD Form 2875 is still current and active. If the DD Form 2875 has expired, the CAVAF user must complete and submit a new form prior to a new contract award. Information for the DD Form 2875 can be found in attachment 2 of this document.

2. In the second step, all first time CAVAF users shall submit their Cyberawareness Challenge training certificate, a completed AF Form 4394 and a completed DD Form 2875 to the CAVAF System Administrator (SA) Point of Contact (POC) at the applicable ALC listed in attachments 2 and 3 of this document. Previous CAVAF users updating their status shall submit all certificates and/or forms in the same manner as new CAVAF users. All DD Form 2875(s) must be digitally signed. All first time CAVAF users and previous users updating their status shall also send a copy of their Cyberawareness Challenge training certificate to HQAFMCA4NL at the following web address: hqafmc.a4nl@us.af.mil to be recorded. Previous CAVAF users may skip the second step if all of requirements in the first step are current and active.

INITIAL LOG IN PROCEDURES FOR CAVAF REPORTING;

First time CAVAF users shall follow the steps shown in attachment 4 of this document to login to the CAVAF system and for a successful login to occur. Any new or previous CAVAF user shall contact the System Administrator (SA) at the applicable ALC any time that a CAVAF login is unsuccessful due to a locked account, or the need for a password re-set. Password re-set steps are shown in attachment 6. The Hill AFB ALC POC can be found in attachments 2 and 3.

CAVAF USER ID ACCOUNT MAINTAINENCE:

All CAVAF users shall perform the following CAVAF account maintenance during the duration in which they have any contract open that is subject to CAVAF inputs. A contract requiring CAVAF input is considered open until an invoice Receipt Acceptance and Property Transfer (iRAPT) Wide Area Work Flow (WAWF) submittal has been signed and processed for the CAVAF reporting.

1. The CAVAF user shall go into their CAVAF user ID account a minimum of once every 30 days or sooner to keep the account open. In the event that a CAVAF user ID account has been disabled, locked, deleted, or the User ID has expired, the CAVAF user shall be responsible for contacting the applicable ALC CAVAF SA POC found in attachments 2 and 3 for a re-set, renewal, or the re-setup of a deleted account and follow the steps as shown in attachment 6.

2. The CAVAF user shall ensure their PKI certification is active and shall not expire during the time in which any of their contracts are open and subject to CAVAF inputs. In the event that a PKI will expire during a contractual period, the CAVAF user shall be responsible for obtaining/renewing their PKI which shall be done prior to expiration of the current

PKI.

3. The CAVAF user shall ensure that their Cyberawareness Challenge Training is active and shall not expire during the time in which any of their contracts are open and subject to CAVAF inputs. All CAVAF users shall note that the Cyberawareness Challenge Training expires on a yearly basis. In the event that the Cyberawareness Challenge Training will expire during a contractual period, the CAVAF user shall be responsible for taking the Cyberawareness Challenge Training and obtaining a new certificate which shall be done prior to expiration of the current certificate. The completed Cyberawareness Challenge training certificate shall be sent to the following web address:

hqafmc.a4nl@us.af.mil to be recorded.

PLEASE NOTE Product Functionality Caution For The Cyberawareness Challenge Training: To meet technical functionality requirements, the Cyberawareness Challenge product was developed to function with Windows operating systems (Windows 7, VISTA, and correctly configured XP) using either the Internet Explorer (IE) or Firefox browsers. New or current CAVAF users employing another OS or browser may experience difficulties and may not be able to complete the training or print the certificate of completion.

CONTRACTOR FURNISHED ITEMS FOR CAVAF REPORTING;

The contractor shall be responsible for providing all necessary personnel and items required to complete and transmit the CAVAF transactions. Labor and equipment used for CAVAF reporting shall be at the discretion of the contractor. However the contractor shall provide, at a minimum, all items requested in accordance with guidance and instruction provided in attachment 3, and must ensure that all CAVAF transactions are transmitted and completed in accordance to attachment 5. All contractor personnel doing inputs into the CAVAF system must have a valid PKI certification.

CONTRACTOR REQUIRED KNOWLEDGE AND REPORTING RESPONSIBILITIES:

The following are items that the contractor shall have a general or basic knowledge of since they deal with the requirements needed to properly use and report through the CAVAF system.

1. The contractor and/or CAVAF user shall have a basic knowledge of the CAVAF system and shall have a basic understanding of how CAVAF production/maintenance transactions are input as shown in attachment 7. The contractor can contact the contracting ALC CAVAF Contract Manager (CM) as listed in the attachments 2 and 3 of this document for this information prior to doing a proposal if needed.

2. The Contractor and/or CAVAF user shall input production/maintenance transactions (receipt, induction completion, shipment, condemnation, etc.) into CAVAF daily, within 24-hours, or as soon as possible after a production/maintenance action occurrence (see attachment 5). Accurate and timely reporting of production/maintenance transactions into CAVAF is critical to the management of repair requirements and the management of world-wide asset distribution. CAVAF transmits daily to Air Force internal data systems for financial and asset tracking.

3. The contractor and/or CAVAF user shall have knowledge of how to read and use a DD Form 1348-A1 document for CAVAF receipt and shipment transaction purposes. The contractor and/or CAVAF user shall also be responsible for knowing how to properly fill out a DD Form 1348-1A document as required on all CAVAF contractual shipments. The contractor and/or CAVAF user must assure that copies of DD Form 1348-1A’s are included in and attached to each item/asset shipment.

a. Receipt Actions: The contractor and/or CAVAF user shall use only Government issued shipment document numbers for CAVAF item/asset receipt transaction reporting which appear on the receiving DD Form 1348-1A.

The shipping document number is used in the creation of the CAVAF Record Control Document Number (RCDN) and CAVAF generates an RCDN for each unit receipted and also allows the reporter to assign a reference or serialization number for tracking purposes. Where no reference or serialization numbers are utilized for tracking purposes for a Contract Line Item Number (CLIN), the oldest RCDN, which is listed first, shall always be processed before other RCDN’s in the reporting process. Any reversal actions shall be accomplished using the last RCDN for a CLIN. In the absence of missing DD Form 1348-1A shipment document number, the contractor shall request a new document number from the contracting ALC CAVAF Contract Manager (CM) as listed in attachments 4 and 5 of the CAVAF SOW attachments. Contractors and/or CAVAF users are not authorized to generate shipment document numbers for receipt transactions and shall not attempt to do so.

b. Shipping Actions: The contractor and/or CAVAF user shall use a DD Form 1348-1A as the shipping document for all CAVAF shipment transactions of items/assets. 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. A DD Form 250 or a DD Form 1149 are not acceptable or authorized as a shipment document, and shall not accompany any material shipments on repair contracts. CAVAF provides a DD Form 1348-1A in a Portable Document Format (PDF) as a part of the CAVAF shipping transaction. It is recommended the PDF file be saved at the contractor’s facility prior to printing the two copies as required for shipping. The contractor and/or CAVAF user shall prepare a DD Form 1348-1A shipping document for each NSN shipment from contractor’s facility, regardless of destination. The contractor and/or CAVAF user shall place one copy of the DD Form 1348-1A on the outside of the shipment container and one copy inside the shipment container. For item/asset shipments the DD Form 1348-1A shipment document number shall be comprised using one of the following actions:

c. Back to Depot Shipments:

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

2) For “multiple” quantity shipments, the CAVAF RCDN of the first item of the shipment shall be used as the shipment document number. In the event that the first RCDN cannot be found or is not available, any of the other RCDN’s from the shipment may be used in its’ place.

4. The contractor shall be responsible for submitting all iRAPT/WAWF documents immediately after assets are tested or inspected (if applicable), when an asset or assets have been repaired and completed (if applicable), and when the CAVAF reporting has been completed. CAVAF reporting submissions must be sent to DoDAAC FA8250 or FB2029.

This is a “must do” to be compliant with a CAVAF repair contract. The contractor and/or CAVAF user shall note that a DD Form 250 number is required in CAVAF to do the completion transaction(s). The contractor and or CAVAF user shall ensure that the DD 250 number for the completions is the same DD 250 number used for the completion billing(s).

5. The contractor and/or CAVAF user shall ensure that the asset record of repairable assets in CAVAF is an accurate reflection of physical repairable assets that the contractor has on hand at all times and shall comply with all reporting requirements in attachment 6 of the CAVAF SOW attachments.

6. The contractor and/or CAVAF user shall have a general knowledge of what a Supply Discrepancy Report (SDR) is and shall know how one is prepared

7. The contractor and/or CAVAF user shall assure that repair assets received with missing components (Missing on Induction, (MOI)), are reported on a Supply Discrepancy Report (SDR) Standard Form 364 immediately upon discovery in accordance with AFJMAN 23-215 and shall provide a copy of the submitted MOI SDR form to the ACO within 2 days of discovery. The MOI asset or assets shall be receipted into CAVAF for tracking purposes.

8. The contractor and/or CAVAF user shall ensure that all overages or shortages of items/asset which are sent for repair on the contract are receipted into CAVAF with the actual quantity received. An SDR shall be processed and sent out in accordance with standard SDR procedures.

9. The contractor and/or CAVAF user shall assure that all misidentified assets which are sent for repair as part of the contract are receipted into CAVAF with a Not on Contract (NoC) transaction using the actual received quantity and the correct NSN as shown in the CAVAF Contractor User’s Guide. An SDR shall be processed and sent out in accordance with standard procedures.

10. Misdirected shipments of Government Furnished Property (GFP) shall be immediately reported by the contractor and/or CAVAF user through the telephone to the Property Administrator (PA) followed by written notification within three work days. The PA shall issue appropriate disposition instructions for the misdirected items. Misdirected items received by the contractor which are not part of the contract shall not be receipted into CAVAF.

11. The contractor and/or CAVAF user must have a general knowledge of how to read and interpret amended shipping instructions. Amended shipping instructions shall be used to divert material that is due-in from a contractor to a destination different than the one printed in the contract. Amended shipping instructions shall be sent to the contractor prior to any amended shipment.

12. The contractor and/or CAVAF user must have a general knowledge of how to read and interpret general disposition instructions. General Disposition Instructions (GDI) shall be used to dispose of condemned material that currently has no economical use to the Government and is in excess at the contractors’ facility. Shipping instructions shall be sent to the contractor prior to any material disposal shipment if they are not already a part of the contract.

13. If CAVAF fails or becomes inoperable when an item is to be shipped, the contractor and/or CAVAF user shall know how to do the following:

a. The contractor and/or CAVAF user shall prepare a manual (downloaded or printed) DD Form 1348-1A. The DD Form 1348-1A shall contain all of the information that one generated by CAVAF would have.

b. The contractor and/or CAVAF user shall resume with transactional reporting actions, including completing a duplicate of the manual DD Form 1348-1A in CAVAF when CAVAF is again operable.

14. Contractors and/or CAVAF users shall not under any circumstances report contractual induction of “At Risk” items/assets in CAVAF. This action is prohibited on all repair contracts.

15. The contractor and/or CAVAF user shall have a basic knowledge of what Nuclear Weapon Related Material (NWRM) is and how NWRM is handled by the Air Force.

16. The contractor and/or CAVAF user shall be required to utilize CAVAF reporting on all NSNs identified as Nuclear

Weapon Related Material (NWRM) for production management, to track and report NWRM items/assets in repair to the Serial Number level. All contractors and/or CAVAF users shall take note of, capture, and use each NWRM assets Serial Number when reparable is received. All NWRM assets received by a contractor shall be receipted into CAVAF, with the Serial Number identification within 24-hours for asset visibility and serial number tracking without exception.

The contractor 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 contractor and Government personnel associated with the storage, shipping, transshipping and receiving of all NWRM assets without exception.

17. Upon contract expiration and/or becoming production complete, the contractor and/or CAVAF user shall complete a 100% physical inspection. Any assets remaining at the facility within 30 days shall be noted and sent as an e-mail request to the PCO and PMS for disposition instructions by the Government. If disposition instructions are not provided, assets shall be returned to the contracting depot and reported within CAVAF. Assets shall be shipped to the following addresses according to each National Stock Number (NSN) Inventory Management (IM) location by Source of Supply (SOS) code:

a. FHZ – Tinker AFB, the ship to disposition address to SW3211:

TYPE/CODE: A SW3211

DEF DISTRIBUTION DEPOT OF OKLAHOMA

CEN REC 3301, F AVENUE

BLDG 506, DR 22

TINKER AFB, OK, 73145-8000

b. FGZ – Ogden AFB, the ship to disposition address to SW3210:

TYPE/CODE: A SW3210

DLA DISTRIBUTION DEPOT HILL

7537 WARDLEIGH RD

BUILDING 849 W

HILL AFB, UT 84056-5734

c. FLZ – Robins AFB, the ship for disposition address to XXXXXX:

OTHER CAVAF CONTRACTOR TRANSACTION REPORTING REQUIREMENTS:

Not on Contract (NoC) situations do, on occasion, happen and the assets that are a part of the Not on Contract process must be accounted for to keep Air Force inventory balances correct. There are two types NoC situations that the contractor and/or CAVAF user must take action on and shall account for with receipt transactions in the CAVAF system. They are Discrepancy Items (DI’s) and Inventory Control Point (ICP) items.

1. Discrepancy Items are identified as misrouted shipments, misidentified shipments or damaged items/assets. The contractor shall use an open repair contract and report the discrepancy items using the CAVAF “Not on Contract” transaction function and receipt the items at DoDAAC level only. The contractor and/or CAVAF user shall address discrepancy issues weekly with the PCO to acquire resolution to discrepancy within 30 days of the receipt transaction(s). The contractor and/or CAVAF user shall also comply with disposition instructions provided by the Government within 10 days of receiving the instructions and complete all associated CAVAF reversal reporting actions by RCDN within same period as shown in the CAVAF Contractor User’s Guide.

2. Inventory Control Point Items are identified as assets stored at contractor facility as an interim storage site and may or may not be awaiting a contract. Most ICP items/assets have been repaired and are being stored by the repairing contractor as a part of a contract or are discrepancies items. Some items are Quality Discrepancy Report (QDR) items awaiting re-work. Movement of assets from the ICP “Not on Contract” status category shall be completed by the contractor and/or CAVAF user using reversals of CAVAF receipt transactions by RCDN as shown in the CAVAF Contractor User’s Guide.

The contractor and/or CAVAF user shall always be responsible for all “Not-on-Contract” assets associated with this contract and ensuring that they are receipted and reflected in CAVAF. CAVAF reporting actions for NoC items must occur within 24 hours of the receipt or as soon as possible thereafter.

PLEASE NOTE Not-on-Contract receipt actions shall not be utilized for Quality Deficiency Report (QDR) items

SUBCONTRACTOR REPORTING REQUIREMENTS:

Utilizing subcontractors in the repair of Government assets is entirely acceptable. The subcontractor shall conform to all CAVAF reporting requirements. The prime contractor shall be required to supply the subcontractor with a copy of this document and all other items required to make the CAVAF reporting successful. The prime contractor shall also bear sole responsibility for all reporting actions and must assure that the CAVAF transactions are completed as outlined in this document.

CAUTIONARY AREAS OF CONTRACTOR CAVAF REPORTING:

Systemic data problems created by contractor’s and/or CAVAF user’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 that the contractor and/or CAVAF user should be cautious about and avoid include but are not limited to:

1. Timely reporting. This means compliance with the 24 hour requirement or a very short time thereafter for all CAVAF reporting of production/maintenance transactions. Actual date information is required for all reporting actions.

Contractors and/or CAVAF users are not authorized to report all receipt, induction, complete and ship transactions using the same date 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). Particular instructions are shown in attachment 6.

2. Not using a Government issued DD Form 1348-1A document numbers for CAVAF contractor reporting on item/asset receipt transactions. This creates a data variance disconnect with government inventory D035 Stock Control System (SCS). Contractors and/or CAVAF users are required to use DD Form 1348-1A document numbers for item/asset receipt transactions either generated from CAVAF or completed manually by the contractor.

PLEASE NOTE If the DD Form 1348-1A is missing or no shipment document number is available, the contractor and/or CAVAF user must immediately contact contracting ALC CM and acquire a Government issued shipment document number.

3. Incorrect DD Form 250 and item/asset completion dates. The DD Form 250 number and date entered into CAVAF for completion of a repair (Condition Code A) entry must be accurate and reflect the correct dates.

4. Incorrect or fabricated RCDN’s. The RCDN information shall not be duplicated or fabricated. A RCDN is produced by CAVAF upon receipt of an asset or assets and reflects information unique to the contractor and the asset or assets.

5. Taking care of items received with missing components. When repair assets are received with missing components

(Missing on Induction, (MOI)), the contractor and/or CAVAF user 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.

6. Taking care of misdirected shipments of Government Furnished Property (GFP). 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 shall issue appropriate disposition instructions for the misdirected items. Misdirected items received by the contractor and/or CAVAF user which are not part of the contract shall not be receipted into CAVAF.

7. Taking care of overages and shortages of repair assets shipped as a part of the contract. Overage and shortage of repair assets which are part of this contract and received by the contractor and/or CAVAF user shall be reported into CAVAF with the actual received quantity and with the correct NSN. An SDR shall be processed in accordance with standard procedures for these overage and shortage items.

8. Taking care of misidentified repair assets shipped as a part of the contract. Misidentified repair assets which are part of this contract and received by the contractor and/or CAVAF user shall be reported as Not on Contract into CAVAF with the actual received quantity and with the correct NSN. This is so that the assets can be tracked and returned back to their Source of Supply (SoS). An SDR shall be processed in accordance with standard procedures identified above for these misidentified items.

GENER

importan systems inventor cost sav

WHAT

Depot M issues, r by quant mandate asset ac

WHY C

capabilit

CAVAF,

requirem

RAL INFOR

nt to the Air F

s. Without su ry system, an vings.

T IS CAVA

Maintenance (C receipts, and r tity and condit ed by Congres ccountability an

CAVAF IS

ties to perform to better man ments and is vi

RMATION: T

Force and to s uccessful CAV d financial sy

F: Commerc CDM) repair re returns. CAVA tion code coun ss under the F nd requiremen

IMPORTA

m depot-level m nage contract r ital in supporti

CAV

CA

The purpose o show the rela VAF Item/Ass ystems causin ial Asset Visib equirements a AF provides 10 nt as required Financial Impro nt forecasting.

ANT: To imp maintenance. T repair workloa ng the Warfigh

VAF AT

ATTA

AVAF IN

of this attachm tionship betw et Transactio ng inventory a bility Air Force nd Governme 00% visibility o by Congress, ovement Audit rove cost effic This partnersh

ad. As such, co hters.

TTACH

CHMEN

NTRODU

ment is to prov ween timely an on Data Repo and budgeting

(CAVAF) is th ent Furnished M of all Air Force the Departme t Readiness (F ciency, the AF hip with contra ontractor repor

HMENT

T 1

UCTION

vide informat nd accurate C rting, disrupti g problems fo he contractual Material (GFM e assets at the ent of Defense FIAR) Act. Ult increasingly r actors requires rting is an ess

TS

ion on the CA CAVAF report ons occur in or the Air Forc compliance re M)/ Governmen contractor fac e (DoD), and th timately, CAVA relies on contra s the AF to pro sential compon

AVAF system ting and other the Air Force ce and a loss eporting system nt Furnished E cility during the he Secretary o AF provides re actors instead ovide a system nent in forecas

, why CAVAF r Air Force da asset pipelin of efficiency m for all Contr Equipment (GF e repair proces of the Air Force epair data for d of organic mic solution, via sting AF

F is ata ne, and ract

FE)

ss e as a

ATTACHMENT 2

CAVAF SYSTEM ACCESS REQUIREMENTS

The Commercial Asset Visibility Air Force (CAVAF) system is the primary system of record under this contract for providing status of all Government owned assets or any assets stored at an inventory control point (ICP) located at a contractor facility.

The CAVAF contractor reporter(s) for this contract must obtain access to the CAVAF system prior to or within seven days after the contract award. The CAVAF contractor reporter(s) for this contract are also required to ensure that accurate and timely reporting in the CAVAF system is accomplished.

CONTRACTOR REQUIRED DOCUMENTS AND TRAINING FOR CAVAF ACCESS:

1. The CAVAF contractor reporter(s) for this contract shall be required to have an active Public Key Infrastructure (PKI) certificate. Only an Identity Certificate is required. An Encryption Certificate is not required. The links that follow are companies that can provide the PKI certificate:

o Operational Research Consultants, Inc. (ORC) http://www.eca.orc.com/ e-mail: ecahelp@orc.com phone (800)-816-5548 o IdenTrust, Inc.

http://www.identrust.com/certificates/eca/index.html e-mail: helpdesk@identrust.com phone (888)-882-1104

2. The CAVAF contractor reporter(s) for this contract are required to complete and digitally sign a System Authorization

Access Request (DD Form 2875) to maintain contractual compliance authorization to report in the CAVAF system. In blocks 28 and 28a on the DD Form 2875, the CAVAF contractor reporter(s) for this contract shall identify the PKI certification supplier and supply date of the investigation.

Instructions.docx

Blank DD2875.pdf

3. The CAVAF contractor reporter(s) for this contract shall be required to complete the Department of Defense (DoD)

Information Assurance (IA) Cyber Awareness Challenge training located on the following website:

http://iase.disa.mil/eta/cyberchallenge/launchPage.htm . Under the DoD Employees section, click the hyperlink;

“Launch New Cyber Awareness Challenge Department of Defense Version”. After completing the test, the CAVAF contractor reporter(s) for this contract shall print the Certificate of completion to send with their initial CAVAF requirements package. Not all computer software will work with the Cyber Awareness Challenge program as noted below.

o Product Functionality Caution: To meet technical functionality requirements, this Cyber Awareness Challenge product was developed to function with Windows operating systems (Windows 10, Windows 7, VISTA, and XP, when configured correctly) using Internet Explorer (IE) or Firefox browsers. Users employing another OS or browser may experience difficulties and may not be able to complete the training or print the certificate of completion. If this occurs, please send an e-mail to the applicable workflow e-mail box as shown below.

4. The CAVAF contractor reporter(s) for this contract must sign and date the AF Form 4394 User Agreement Statement.

By signing this document, each CAVAF contractor reporter acknowledges and consents that they are accessing a Department of Defense (DoD) information system and must protect that access in accordance to applicable Government laws and regulations.

AF Form 4394.pdf

5. The CAVAF contractor reporter(s) for this contract shall ensure that all CAVAF access forms have been completed and signed and that the training certificate has been printed. The initial package should contain the following:

o Completed DD Form 2875 with PKI information listed in box 28 and 28A.

o Cyber Awareness Challenge Course completion Certificate.

o AF Form 4394 User Agreement Statement with signature and date.

6. All CAVAF access forms and the training certificate for this contract shall be sent to the workflow e-mail box listed below:

o Hill AFB, Utah - 420scms.cdm@us.af.mil

7. Please note that the CAVAF contractor reporter(s) for this contract must notify the Point of Contact (PoC) listed below if any asset(s) arrive prior to CAVAF access being granted. The PoC for the 415 Supply Chain Management Squadron (415 SCMS) for Hill AFB Ogden Air Logistics Complex (OO-ALC) is as follows:

o M. Claude Speth ( Phone: 801-777-8127 ) ( E-mail: morris.speth@us.af.mil )

8. Please also note that CAVAF contractor reporter(s) for this contract shall ensure that access to the CAVAF system shall be maintained for the duration of the contract. This includes but is not limited to keeping the CAVAF USER ID active, renewing the PKI certificate, and taking the annual Cyber Awareness Challenge training.

9. Listed below are WEB sites where forms and the CAVAF WEB page can be found:

o Air Force Forms (AF Form 4394): http://www.e-publishing.af.mil/ (Click on “Forms” then click on “Departmental” then click on “4300 – 4399” then scroll down to the form and click on the form. Follow the instructions and fill out the form.)

o DoD Forms (DD Form 2875): http://www.dtic.mil/whs/directives/infomgt/forms/index.htm (Move mouse to “DoD Forms” then move mouse to “Department of Defense (DD) Forms” then move the mouse to “Department of Defense (DD) Forms 2500 - 2999“ then scroll down to the form and click on the form. Follow the instruction for filling out the DD Form 2875 that appear below. All of the appropriate boxes and information must be filled in or the form cannot be processed. The CAVAF user ID coordinator shall contact the contractor when a CAVAF user ID has been assigned.)

o CAVAF WEB Site: https://www.cavaf.com/ (Click on this web site once you have a CAVAF user ID and follow the instructions for first time users below)

10. To ensure connectivity to Government websites including CAVAF, the CAVAF reporting contractor must allow ports 443 and 4443 of their network to be open in both directions. If the CAVAF reporting contractor is running a proxy server on their network, the CAVAF contractor must also include all the Government websites as trusted sites, and may need to activate SSL 2.0 and de-activate TLS 1.2 in the Internet Advanced Options. Make sure that this is accomplished before attempting to login to a Government web site.

ATTACHMENT 3

CONTRACTOR COMMUNICATIONS NETWORK (CCN)

GENERAL INFORMATION: The purpose of this attachment is to provide the specific conditions, hardware specifications, communications interface, and personnel needed to support contractor Item/Asset reporting requirements and supply requisitions.

TRAINING: Initial CAVAF training shall be provided by the contracting ALC. Any follow up training shall be the responsibility of the contractor. For training and/or questions on CAVAF reporting, please contact the CAVAF Representative for contracts issued by each respective ALC, from one of the following areas:

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

b. Hill AFB, UT, call (801) 777-8127, Morris (Claude) Speth, e-mail: morris.speth@us.af.mil .

c. Tinker AFB, OK, call (405) 739-3229, a CAVAF representative shall contact you for training. Assistance, guidance or questions specific to suppliers of contractual data reporting requirements may be addressed to the CAVAF contract monitor (CM). For Tinker AFB the contracts as follow:

1) Contractor Furnished Material (CFM) contracts call; (405) 736-7171 or (405) 736-2041

2) Government Furnished Material (GFM) contracts call (405) 739-7329 or (405) 736-7362

PLEASE NOTE The Contractor User’s Guide can be accessed via the CAVAF main menu at the bottom of screen.

CAVAF TRANSACTION FLOW: There are two (2) ways in which CAVAF transactions shall flow electronically to their destination systems. One involves using the standard Internet and the other involves using and XML format. Both are fully acceptable for the contractor to use as long as the transactions are sent in the correct format, time frame and are properly transmitted to the receiving Air Force Systems without error.

INTERNET REPORTING: The contractor must provide the following, at a minimum, to have adequate input ability/capability and connections for CAVAF Internet reporting:

a. The contractor must provide at least one IBM compatible Personal Computer (PC) and monitor for the input of CAVAF data. The PC and monitor must be in good working condition. The PC must have an operating system, software, and web browser tool capable of accessing and processing transactions over the internet through the web address listed in this attachment. The contractor shall be responsible for the maintenance of the PC and monitor and shall make sure they are operational and compatible with the host server and web site. The PC and monitor do not have to be a “stand alone” set up for CAVAF reporting only.

b. The contractor must provide a printer connected to the PC for printing CAVAF documents as needed. The printer must be in good working condition. The contractor must also provide all supplies (paper, ink, printer cartridges, etc.)

associated with the operation of the printer. The contractor shall also be responsible for the maintenance of the printer.

The printer does not have to be a “stand alone” printer for printing CAVAF reports only.

c. The contractor must provide a phone line or compatible access to connect the PC setup to the internet. The contractor must also provide a connection to the internet capable of sending and/or receiving CAVAF transactions through the internet address provided in this attachment. The contractor shall be responsible for maintaining an internet connection until all of the CAVAF reporting has been completed and all reports have been submitted. The internet connection does not need to be “dedicated only to” CAVAF reporting.

d. The contractor or CAVAF user must be familiar with and capable of using the internet and connecting to internet sites and/or programs. The contractor can use a subcontractor to do CAVAF reporting. However, the subcontractor must have the ability/capability to ensure CAVAF reporting transactions are input according to contractual terms which includes but is not limited to timeliness, and accuracy. The Prime contractor shall be under obligation to oversee all time lines, asset tracking, and CAVAF reporting of their subcontractor and must have the ability/capability to make sure that these are all maintained and up to date at all times. Contractor and subcontractor personnel used for CAVAF reporting do not have to be “fully dedicated to” CAVAF reporting only.

e. The contractor or CAVAF user shall input CAVAF transactions through the Internet using the following address:

https://www.cavaf.com/. Each contractor and/or CAVAF user using CAVAF shall be required to complete a System Authorized Access Request, DD Form 2875, and other items as requested and shown in attachments 2 and 3 prior to using CAVAF system.

XML REPORTING: The contractor must provide the following, at a minimum, to have adequate input ability/capability and connections for CAVAF XML reporting:

a. All CAVAF XML batch files shall be sent via a DLA/DLMSO format known as CICA XML, and must be transmitted via the Defense Logistics Agency (DLA) Transaction Services Network (TSN) Defense Automatic Addressing System (DAAS) network which has the ability to receive, edit, and route logistics transactions for the Military Services and Federal Agencies.

b. The contractor must use the services of a Value Added Network (VAN), with a current access/connectivity to a DLA TSN DAAS license agreement. There are no exceptions.

c. The contractor shall take care of establishing an access/connectivity license agreement with a VAN and the DLA TSN

DAAS at the earliest opportunity since it is an essential action. Once this has been accomplished, the contractor shall provide DLA TSN DAAS with the ISA/GS addressing id’s so the information can be setup. Depending on the VAN selected, DLA TSN DAAS main ISA id is DTDN.

1) VAN: https://www.transactionservices.dla.mil/daashome/edi-vanlist-dla.asp

2) DAASC: https://www.transactionservices.dla.mil/daashome/edi-dialin-filenameing.asp

d. The contractor shall use the Air Logistics Complex CDM personnel for assistance in gaining access to the VAN site since the VAN connectivity related information is located on a DLA dot mil domain. This coordinated effort is required with either the VAN or DLA TSN DAAS access the contractor pursues. Contractor sponsorship requirements exist where contractors requesting DLA TSN DAAS access must be sponsored by their U.S. Government Contracting Officer or Contracting Officer's Representative. Close coordination between the Air Logistics Complex's (ALC) CAVAF System Administrator (SA) and the contractor's programmer is required.

PLEASE NOTE Contractors shall input their repair transactions to CAVAF either by CAVAF Internet or CAVAF XML. Both methods cannot be utilized at the same time. When the ALC's CAVAF System Administrator loads the Contractor's Profile into CAVAF, a reporting decision is made whether a contractor uses CAVAF Internet or CAVAF XML reporting.

TECHNICAL CONSIDERATIONS: All contractors and/or CAVAF users accessing CAVAF shall have a valid DoD PKI certificate to log into CAVAF. Contractors can purchase a valid DoD PKI certificate through one of two External Certificate Authorities (ECAs). A listing of ECAs and additional information on purchasing a valid DoD PKI can be found in attachment 2.

Contractors accessing CAVAF shall need an Identity Certificate only. An Encryption Certificate is not required.

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

a. For CAVAF login problems, please contact the CAVAF System Administrator at Hill AFB:

(E-mail: 420scms.cdm@us.af.mil )

b. For CAVAF technical assistance, please contact CAVAF Technical Support at Wright-Patterson AFB:

(E-mail: cavaf.tech.sup@us.af.mil ) (Phone: 937-656-1506)

c. For CAVAF reporting problems and/or training, please contact the CAVAF Contract Manager Point of Contact (POC) at

Hill AFB: Morris (Claude ) Speth (E-mail: morris.speth@us.af.mil ) (Phone: 801-777-8127)

1. Make into the

2. To en both dire website Options

3. Use a

4. The W

Pleas with no click on

CAVAF

5. Selec

6. Click

7. The A

8. Enter

9. Click e sure that the CAVAF web nsure connec ections. If the as one of the

s. Make sure a WEB brows

Windows Sec se Note: If an information in “CANCEL” to production re ct and click on on “OK”.

ActiveClient L r an ECA/PKI on “OK”.

CAV

e PKI certifica site.

tivity to the C e contractor is eir trusted site that this is ac ser to access curity “Select a n ECA/PKI cer n the box (i.e.

o return to the eporting inform n any recogni

Login ActivIde designated p

VAF FIR

ate is loaded i

AVAF websit s running a pr es, and may n ccomplished b the Commerc a Certificate” rtificate has n ., no Name or e WEB brows mation system zed or loaded entity ActiveCl pin number pr

ATTA

RST TIM

nto the comp te, the contrac roxy server on need to activa before attemp cial Asset Vis screen will ap not been loade r Issuer). Wh

er. All users m.

d DOD ECA/P lient “Please rovided with a

CHMEN

E LOGIN

puter that will ctor must allo n their networ ate SSL 2.0 a pting to login t ibility Air Forc ppear with an ed or is not re hen an ECA/P must acquire

PKI certificate enter your PI any DoD reco

T 4

N PROCE

be used to ac ow ports 443 a rk, they must and de-activat to the CAVAF ce (CAVAF) w ny DoD recog ecognized, th PKI certificate e and load an e(s).

N” screen wil ognized or loa

EDURES

ccess CAVAF and 4443 of t also include t te TLS 1.2 in F web site.

website at http nized or load e “Select a C has not been ECA/PKI cer ll appear.

aded ECA/PK

S

F before attem heir network the https://ww the Internet A ps://www.cav ed ECA/PKI c

Certificate” scr n loaded or is rtification prio

KI certificate.

mpting to ente to be open in ww.cavaf.com Advanced vaf.com certificate(s).

reen will appe s not recogniz or to using the er m ear zed, e

10. The

11. Click

12. The by a “Me respons

12a. Cli

12b. Cli

Commercial k on the “Log

Commercia essage from w sibility of the u ck on “Cance ck on “OK” to

Asset Visibili

In” button to l Asset Visib webpage” Th user when us el” to not acce o accept the te ty 8.0.1.2 Log continue.

bility 8.0.1.2d he message i ing the system ept the terms erms and con gin screen wil d (Production s warning tha m.

and return to ntinue.

ll then appear n System)(EA at this is a US the previous r.

AS 6.3.1/PB1

S Government page

12.5 Edition)

t information screen will a system and s ppear followe shows the ed

13. The

14. Cho

15. Ente contract

16. Ente

17. Click

18. The here to

19. Follo number must be

Commercia oose the appli

OOALC (FD2

OCALC (FD2

WRALC (FD

NWRM (FDN

CPSG (FD70

er a valid CAV t to reported o er an ( * ) aste k on the “Ente next screen proceed to th ow all of the i r of upper cas e reentered fo l Asset Visib cable ICP.

2020) = Ogde 2030) = Oklah 2060) = Warn

NWRM) = Nuc

030) = Crypto

VAF user ID.

on was award erisk the initia er” button to c to appear is t he CAVAF Pro nstructions on se letters, num or verification.

bility 8.0.1.2d en Air Logistic homa City Air ner Robins Ai clear Weapon ologic System

(CAVAF use ded.)

al password.

continue the “Establish oduction Infor n the screen mber lower ca d (Production cs Complex C r Logistics Co ir Logistics Co n Rated Mate ms Group Con er ID’s are ass h New Passwo rmation Repo and enter a n ase letters, nu n System) (E

Contract Repa omplex Contra omplex Contr erial Contract tract Repair ( signed by the ord”. A passw orting System new password umerical chara

EAS 6.3.1/PB1

air (Hill AFB, act Repair (Ti ract Repair (R Repair (Wrigh (Lackland AF e CAVAF Syst word that can d taking note acters, and sp

12.5 Edition)

UT)

inker AFB, O

Robins AFB, G ht-Patterson A

B, TX)

tem Manager n be remembe of the require pecial charac

) screen will a

K)

GA)

AFB, OH)

r at the locatio ered must be ements for pa cters. Your ne appear again on where the established assword lengt ew password h,

20. Click

20a. A s producti

20b. An

21. The appear

For CAV

For CAV (E-mail:

For CAV AFB: Mo k on “Submit” successful pa ion reporting unsuccessfu re are only th on the screen

VAF login pro

VAF technica cavaf.tech.s

VAF reporting orris (Claude

” to continue.

assword chan transactions w ul password c hree attempts n that indicate oblems, pleas l assistance, up@us.af.mil g problems an ) Speth (E-m ge brings up will begin and hange brings to successfu es that the ac e contact the please conta ) (Phone: 93 nd/or training, mail: morris.sp the Main CAV d end.

up and error lly change the count is locke

C…