CAVAF.doc

CAV AF CFM

STATEMENT OF WORK

The purpose of this statement of work (SOW) is to provide general 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 Government owned assets located at Contractors facilities. Items requiring reporting in CAV AF are End Items subject to repair. Enhancements to the CAV AF system will be identified on the CAV AF home web page. Users of CAV AF shall be responsible for ensuring training manuals or User Guides being used at contractor facilities are current.

The contractor shall perform CAV AF reporting requirements in accordance with CDRL A001(DI-MGMT-81634B) of this contract.

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. Contractor’s 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.

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. Operating in such capacity requires the subcontractor to acquire a CAV AF User ID for reporting on the awarded prime contractors delivery orders.

Accurate and timely reporting of End Items 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 the lack of CAV AF reporting will cause significant loss to the Air Force. Contractor shall ensure asset record reflected in CAV AF is accurate in accordance with physical assets on hand at all times. Contractor shall use CAV AF to transmit End Item transactions within 24 hours of supply or maintenance occurrence and in accordance with the applicable CAV AF CDRL, CAV AF version 7.2 or higher Users Guide and applicable references within the contract.

Not-on-Contract receipt transactions shall be utilized for assets received at a contractor’s facility which are not an end line item number (ELIN) or contract line item number (CLIN) on the contract. This is to include AF Web Supply Deficiency Report (SDR) items, which are not limited to misrouted or misidentified shipments. In no terms shall Not-on-Contract receipt transactions be utilized for quality deficiency report (QDR) items. NOTE: Not-on-Contract receipt transactions must be resolved within 90 days and require government disposition.

All 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. For clarification, 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. Contractor’s shall follow all NWRM management requirements outlined within AFGM 20-1, Air Force Guidance Memorandum on NWRM Management (will be replaced by AFI 20-110 currently in coordination) 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 in addition to hazardous and classified 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:

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, please call applicable commodity type for training:

Whole engine and/or engine reparable part workloads, call (405) 736-3032

Whole aircraft PDM workloads, call (405) 736-3031

Accessory Commodity workloads, call (405) 736-7356

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:

1) 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. FAX DD Form 2875 to the respective ALC CAV AF System Administrator POC listed below:

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

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

c. Tinker AFB, OK, FAX (405) 736-5308

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, call (405) 736-3030

CAV AF SOW, Version 1.1 CAV AF SOW, Version 1.1

_1329995719.doc Instructions for 2875

Select Type of Request.

Input Date on Top Right block.

Fill out blocks 1-9.

Leave block 10 (IA block) blank.

Fill out blocks 11-12.

Block 13 Justification input “To Access CAV AF System”.

Block 14 check “Authorized”.

Block 15 Check “Unclassified”.

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 or Email DD Form 2875 to the respective ALC CAV AF System Administrator POC listed below:

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

b. Hill AFB, UT, FAX (801) 777-5692 OR email to sherry.anderson@hill.af.mil or mercy.jenner@hill.af.mil

c. Tinker AFB, OK, FAX (405) 736-5308

_1329995720.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 other identifiers 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. ORGANIZATION

3. OFFICE SYMBOL/DEPARTMENT

8. CITIZENSHIP

6. JOB TITLE AND GRADE/RANK

4. PHONE (DSN or Commercial)

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)

7. OFFICIAL MAILING ADDRESS

5. OFFICIAL E-MAIL ADDRESS

DD FORM 2875, AUG 2009 PREVIOUS EDITION IS OBSOLETE.

USER ID

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

9. DESIGNATION OF PERSON

OTHER

24. PHONE NUMBER

AUTHORITY:

PRINCIPAL PURPOSE:

ROUTINE USES:

DISCLOSURE:

20a. SUPERVISOR'S E-MAIL ADDRESS

US FN

OTHER

MILITARY CIVILIAN

CONTRACTOR

Adobe Professional 8.0

11. USER SIGNATURE 12. DATE (YYYYMMDD)

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

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

DD FORM 2875 (BACK), AUG 2009

PART IV - COMPLETION BY AUTHORIZED STAFF PREPARING ACCOUNT INFORMATION

PROCESSED BY (Print name and sign)DATE PROCESSED

(YYYYMMDD)

27. OPTIONAL INFORMATION (Additional information)

SYSTEM

DOMAIN

SERVER

APPLICATION

DIRECTORIES

FILES

DATASETS

TITLE: ACCOUNT CODE

REVALIDATED BY (Print name and sign)DATE REVALIDATED

(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)

26. NAME (Last, First, Middle Initial)

LEVEL I LEVEL II LEVEL III

30. SECURITY MANAGER

TELEPHONE NUMBER

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) Organization. The user's current organization (i.e. DISA, SDI, DoD and government agency or commercial firm).

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

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

(5)Official E-mail Address. The user's official e-mail address.

(6) Job Title/Grade/Rank. The civilian job title (Example: Systems Analyst, GS-14, Pay Clerk, GS-5)/military rank (COL, United States Army, CMSgt, USAF) or "CONT" if user is a contractor.

(7) Official Mailing Address. The user's official mailing address.

(8) Citizenship (US, Foreign National, or Other).

(9) Designation of Person (Military, Civilian, Contractor).

(10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date.

(11) User's Signature. User must sign the DD Form 2875 with the understanding that they are responsible and accountable for their password and access to the system(s).

(12) Date. The date that the user signs the form.

B. PART II: The information below requires the endorsement from the user's Supervisor or the Government Sponsor.

(13). Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Provide appropriate information if the USER ID or access to the current USER ID is modified.

(14) Type of Access Required: Place an "X" in the appropriate box.

(Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configuration, parameters, or settings.)

(15) User Requires Access To: Place an "X" in the appropriate box.

Specify category.

(16) Verification of Need to Know. To verify that the user requires access as requested.

(16a) Expiration Date for Access. The user must specify expiration date if less than 1 year.

(17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required.

(18) Supervisor's Signature. Supervisor's signature is required by the endorser or his/her representative.

(19) Date. Date supervisor signs the form.

(20) Supervisor's Organization/Department. Supervisor's organization and department.

(20a) E-mail Address. Supervisor's e-mail address.

(20b) Phone Number. Supervisor's telephone number.

DD FORM 2875 INSTRUCTIONS, AUG 2009

INSTRUCTIONS

The prescribing document is as issued by using DoD Component.

(21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested.

(21a) Phone Number. Functional appointee telephone number.

(21b) Date. The date the functional appointee signs the DD Form 2875.

(22) Signature of Information Assurance Officer (IAO) or Appointee.

Signature of the IAO or Appointee of the office responsible for approving access to the system being requested.

(23) Organization/Department. IAO's organization and department.

(24) Phone Number. IAO's telephone number.

(25) Date. The date IAO signs the DD Form 2875.

(27) Optional Information. This item is intended to add additional information, as required.

C. PART III: Certification of Background Investigation or Clearance.

(28) Type of Investigation. The user's last type of background investigation (i.e., NAC, NACI, or SSBI).

(28a) Date of Investigation. Date of last investigation.

(28b) Clearance Level. The user's current security clearance level (Secret or Top Secret).

(28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III).

(29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified.

(30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative.

(31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified.

(32) Date. The date that the form was signed by the Security Manager or his/her representative.

D. PART IV: This information is site specific and can be customized by either the DoD, functional activity, or the customer with approval of the DoD. This information will specifically identify the access required by the user.

E. DISPOSITION OF FORM:

TRANSMISSION: Form may be electronically transmitted, faxed, or mailed. Adding a password to this form makes it a minimum of "FOR OFFICIAL USE ONLY" and must be protected as such.

FILING: Original SAAR, with original signatures in Parts I, II, and III, must be maintained on file for one year after termination of user's account. File may be maintained by the DoD or by the Customer's IAO. Recommend file be maintained by IAO adding the user to the system.

xtype: Off userid:

reqdate:

syst_name:

location:

reqorg:

reqsymb:

reqphone:

reqemail:

reqtitle:

reqaddr:

xcitizen: Off xdesignation: Off xia: Off trngdate:

user_name:

userdate:

justify:

xauth: Off xpriv: Off xunclass: Off xclass: Off classcat:

xotheracc: Off other_acc:

xverif: Off acc_exp:

supvdate:

supvorg:

supvname:

supvemail:

supvphone:

ownerphone:

ownerdate:

iaoorg:

iaophone:

iaodate:

name:

optinfo:

typeinv:

xit_lvl: Off verifname:

sec_mgr_phone:

sec_mgr_date:

title1:

system:

acctcode1:

title2:

domain:

acctcode2:

title3:

server:

acctcode3:

title4:

applic:

acctcode4:

title5:

direc:

acctcode5:

title6:

files:

acctcode6:

title7:

datasets:

acctcode7:

dateproc:

procname:

procdate:

datereval:

revalname:

revaldate:

Reset:

expdate:

invest_date:

clr_level: