19_Mar_14_SMXG_SOW.pdf

STATEMENT OF WORK (SOW)

SMXG SOFTWARE SUPPORT

19 MARCH 2014

1 DESCRIPTION OF SERVICES

This Statement Of Work (SOW) outlines the tasks and duties required of the Contractor in support of the 402 Software Maintenance Group (SMXG) for workloads at or below the top secret level. Examples include work types such as product sustainment, product development, lab support, and engineering services in support of Operational Flight Program (OFP), Test Program Set (TPS), and Mission Support (MS) business lines within the Software Maintenance Group.

1.1 Basic Services

1.1.1 The Contractor shall be responsible for the selection, recruitment, hiring, management, control, transfer and/or termination of Contractor employees in performance of this SOW. The Contractor shall provide assignment of duties and monitor status as required by the Government in a timely manner to accomplish project milestones. Accordingly, the contractor shall provide a point of contact capable of responding within four hours of being alerted by the government to any issues related to personnel or performance.

1.1.2 The Contractor shall ensure all employees possess required training, qualifications, proficiency, and security clearances and satisfy all other access requirements. The Contractor understands that any Contractor employee may be summarily removed from or denied access to any government property/facility/ installation if the Government determines such action is necessary to protect or preserve government property, safety and security, or to maintain good order and discipline.

1.1.3 A monthly activity report shall be delivered no later than the 15th of the following month and shall include a description of all activities accomplished for each month. (CDRL A001, DI- MGMT-80368A/T, Status Report)

1.1.4 The Government and the Contractor understand and agree that the services to be delivered under this contract by the Contractor to the Government are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the contract between the Government and the Contractor’s employees.

1.1.5 Contractor personnel under this contract shall not be used in administration or supervision of Government procurement activities.

1.1.6 The Contractor shall participate in process improvement to ensure the 402 SMXG and their customers are given the highest quality product at the lowest cost in the shortest amount of time per work order.

1.1.7 The 402 SMXG tracks project time through an automated time and accounting system known as Time and Accounting System (TAAS). The Contractor shall ensure that contractor personnel enter their daily project hours worked into systems such as the Single Interface for Time Entry (SITE), Earned Value Time Accounting Tool (EVTAT), and Depot Maintenance Accounting and Production System (DMAPS) prior to the end of each work day. Hours can be entered in advance to cover travel assignments and other off-site activities. This system will not be used to pay the contractor nor act as a time card for contractor personnel.

1.2 Specific Services

This is a list of SMXG business lines and work descriptions.

1.2.1.1 SMXG business lines constitute the work performed by the organization. The three business lines are:

1.2.1.1.1 Operational Flight Program (OFP) – Operational Flight Programs are specialized software programs hosted on aircraft avionics.

1.2.1.1.2 Test Program Set (TPS) – A Test Program Set consists of the hardware, software and documentation required to test and repair a unique Unit Under Test (UUT).

1.2.1.1.3 Mission Support – Products and services not considered OFP or TPS.

1.2.1.2 SMXG work types describe nature of the work performed and are used in conjunction with the business line to determine the exact business policies and process requirements. The work types are:

1.2.1.2.1 Product Sustainment - Tasks to perform the maintenance, modification, and release of products already deployed for use external to SMXG.

1.2.1.2.2 Product Development - The creation and delivery of a new product for use external to SMXG. This includes TPS rehost.

1.2.1.2.3 Lab Support - The recurring activities associated with maintaining the organic sustainment capability such as, updates to simulations, tests, documentation, other lab software and hardware upgrades, etc. as well as the daily routine operation and maintenance of the sustainment capability or system integration lab. This includes tasks in support of product development and product sustainment.

1.2.1.2.4 Engineering Service - Tasks to provide technical support to outside customers, such as System Program Offices, System Engineering and User activities.

Tasks include acquisition support, independent verification and validation (IV&V), independent test of externally acquired products, consulting, research, analysis, reverse-engineering studies, and other support tasks.

1.2.2 Various tasks will be required. Examples include software design/coding; technical documentation/drafting; systems engineering; configuration management; and information technology/system administration.

1.2.2.1 Software Design/Coding. Tasks involve development and/or support of software used to test a variety of line replaceable units (LRUs) and shop replaceable units (SRUs) applicable to avionics equipment encompassing the latest state-of-the-art advanceSpecific tasks may include: engineering support to shop personnel engaged in test, troubleshooting, repair, and modification of LRUs or SRUs tested on automatic test equipment (ATE), engineering assistance in evaluation/correction of software applicable to ATE, participating as members of preplanning and organizational process teams, as required for the acquisition of new/replacement automatic test systems (ATS). Tasks also include web service development, web application development, the development of software used in Operational Flight Programs (OFPs) for a variety of weapon systems including but not limited to Joint STARS, F-15, C-5, SOF systems and EW systems.

Software design/coding tasks include a broad range of design, development, testing, upgrading, documentation and maintenance tasks for software in support of weapon systems.

1.2.2.2 Technical Documentation (TD)/Drafting. TD tasks include preparing accurate and complete technical documentation, technical evaluations, or white papers of the production item or process developed that is maintainable and readable.

These tasks shall include drafting services and technical writing.

1.2.2.3 Systems Engineering (SE). SE tasks require multi-discipline development of systems to meet 402 SMXG customer’s requirements. SE tasks ensure that the sub-systems (i.e. hardware, software, documentation) operate together to support 402 SMXG customer requirements and support “System Life Cycle” decisions.

SE tasks focus on 402 SMXG customer needs and required functionality. SE tasks consider all facets of implementation including concept, design, production, cost, schedule, training requirements and system support issues.

1.2.2.4 Configuration Management (CM). CM tasks include providing software, hardware, and documentation configuration management and process control support for a broad range of weapon system software and associated documentation. Specific tasks include using software package audit tools, managing weapon system baselines, and supporting organizational process teams.

1.2.2.5 Information Technology/System Administration (IT/SA). IT/SA tasks include information technology support which includes system administration, network administration, application administration, database administration, and computer security support for a broad range of UNIX, Solaris, and PC based computer systems, , and weapon system software/hardware. Specific tasks include: Solaris clustering, Solaris security, Containers/Zones, Shell scripting, Linux RedHat administration, VMware, Storage/Cloud technology, Cisco IOS, DNS/LDAP/HPOV and Active Directory tasks, Weblogic administration, Oracle DBA,and SW package installation, patching, and upgrading.

1.3 Reports/Notifications

1.3.1 The Contractor shall provide a monthly report detailing the activities accomplished per month IAW paragraph 1.1.3. The monthly report shall be provided by the 15th day of the next month.

This report shall be submitted IAW DD Form 1423, Contract Data Requirements List (CDRL) A001.

1.3.2 The Contractor shall notify the government project manager and contracting officer (CO) as specified when the Contractor determines that tasks will not be completed on time.

1.4 Travel

Travel shall be accomplished IAW Joint Travel Regulations (JTR) unless JTR requirements cannot be met (i.e. hotel will not provide government rates to contractors); under such circumstances the contractor shall make arrangements that are fair and reasonable as approved by the contracting officer. The contractor shall make their own travel arrangements. No later than ten calendar days before departure, the contractor shall submit a cost proposal for required travel to the contracting officer for evaluation. All travel must be approved by the contracting officer prior to departure.

1.5 Task Orders - Task orders will be issued which will state a period of performance and specifically the quantity/positions covered under that particular task order. Task orders shall not exceed 12 months in performance. Multiple task orders may be issued per year depending on Government requirements and availability of funds.

2 GOVERNMENT FURNISHED PROPERTY AND FACILITIES

2.1 The Government will provide access to the necessary facilities, equipment, and property as required for the specific task order. Any and all property or equipment provided to the Contractor shall be returned to the using organization after the completion of the contract. The place of performance shall be Robins Air Force Base except in cases of Temporary Duty

(TDY).

2.2 Consistent with the contractor’s exclusive right and authority to supervise and control its employees the contractor shall develop and implement all reasonable means to ensure that its performance of this contract in a government facility is fully complementary with, and does not run counter to, any written operating procedures or policies that may be provided by the government. (e.g. AFMCI 21-101)

3 GENERAL INFORMATION

3.1 Contractor Management Responsibilities

3.1.1 The prime contractor’s staff will hereafter be termed as Contractor Management Staff (CMS).

The prime Contractor retains responsibility for any teaming partner or subcontractor and shall be accountable for their performance.

3.1.2 All personnel recruited and hired by the CMS to perform the services as described in this contract will be considered hereafter as Prime Contractor Personnel (PCP).

3.1.3 As part of providing services under this contract:

3.1.3.1 CMS shall have in place a human resources management plan to ensure qualified candidates are identified, verified, placed, monitored, trained/re-trained to fulfill the task orders issued under this contract.

3.1.3.2 The CMS shall accomplish the assigned work with qualified personnel possessing appropriate combinations of education, experience, knowledge, training, abilities and skills as well as physical capabilities. Minimum qualifications are defined in Attachment 1.

3.2 Security Requirements

3.2.1 After contact award and prior to assignment of contactor employee to contract tasks, the contractor employee shall meet the necessary security clearance eligibility requirements for work performance of the assigned task. Security clearance eligibility requirements are SECRET and TOP SECRET/Sensitive Compartmented Information (SCI). Security clearance eligibility for each contractor employee must be verified by the 402 SMXG Security Office prior to contractor employees beginning work. Access to and familiarity with Joint Personnel Adjudication System (JPAS) is necessary for processing clearance requests.

Refer to the associated DD Form 254, DoD Contract Security Classification Specification.

3.2.2 Requirements for Contractor Credentials: All Personnel requesting installation contractor credentials shall present a valid state issued identification card or driver's license and a social security card before they will be issued a credential. Persons shall present previously issued contractor identification card if applicable.

3.2.3 For contractors requiring access to computer networks on Robins AFB (Common Access Card (CAC)): The contractor shall electronically submit an application for Department of Defense Common Access Card-DEERS Enrollment, through the Trusted Associate Sponsorship System (TASS) (http://www.dmdc.osd.mil), if personnel require access to the base computer network (i.e. “.mil” address is required). The contractor ID card/badge authorizes unescorted entry to Robins AFB for the bearer only. Contractor personnel are required to prominently display the contractor ID card/badge on their person while visiting or performing work on Robins AFB. Contractor personnel, whether prime or subcontractor are not authorized sponsorship privileges. The prime contractor is responsible for retrieving all contractor/subcontractor ID card/badge (including restricted/controlled area badges, if applicable) upon completion or termination of the contract/order/ modification or when an employee no longer has a need for access to Robins AFB, i.e. employment has been terminated or individual transferred to another project.

3.2.4 During the performance of the contract, the Contractor shall be responsible for both (a) obtaining the required identification for newly assigned personnel, and (b) the prompt return of credentials for any employee who no longer requires access. Employees terminating employment for any reason must return Government identification cards prior to departing the base.

3.2.5 All Contractor employees shall promptly report the loss of any badge. For each lost badge, the Contractor shall submit a letter on company letterhead, including employee name, social security number and details of loss to the CO.

3.2.6 Contractor employees requiring access to Air Force systems/networks must obtain a favorable trustworthiness investigation called a National Agency Check with Inquiries (NACI). All contractor personnel requiring access to Air Force systems/networks must meet the requirements of all network and computer security regulations prior to access. (DODD 5200.2; AFI 31-501; AFI 33-115, Volume 2; AFI 33-202)

3.2.7 Contractor employees shall comply with policies regarding the official or authorized use of government-provided electronic messaging systems (email). (AFI 33-119)

3.2.8 Due to the nature of this work DD 254s shall be required for each Task Order. Please reference Air Force Federal Acquisition Regulation Supplement clause 5352.204-9000 for more information and a link to the DD 254 form.

3.2.9 Training required to obtain a network user license is standardized in the “Information Protection Training” (IPT) CBT course. Access the CBT on the current IPT training site via the Air Force Portal. Successful completion of this course satisfies the Air Force training requirement for a network user license. Additional user training may be developed locally to reflect local needs and concerns. (AFI 33-115, Volume 2)

3.2.10 Ongoing government provided security training shall be accomplished as identified by security programs involved with specific work order.

3.2.11 The contractor shall comply with all security and force protection requirements enforced at each installation or facility.

3.2.12 Contractor shall ensure contractor employees immediately report all security issues/violations to the project security manager. The incident shall also be synopsized in the next monthly report.

3.2.13 The contractor shall not have security violations of more than one occurrence per year.

3.2.14 The contractor shall report personnel who no longer require network or automated information systems access to the appropriate Government Security Manager within 3 days.

3.2.15 Visit Request (VR) will be provided to the Group Security Manager (GSM) via JPAS in the area where contract performance takes place. A VR is required for all contracts.

3.2.16 The contractor shall ensure that contractor employees are incorporated into the 402 SMXG Semi-Annual Security Self-Inspection Program.

3.3 Contractor Identification

3.3.1 The contractor shall support completion of required security access forms as provided by the 402 SMXG Security Manager.

3.3.2 All contractor management staff and personnel shall clearly be identified as such at ALL times and from a distance. Contractor identification shall include conversations, mail, email, teleconferences, video teleconferences, faxes, and/or other electronic communication whether with government personnel, other contractor personnel, or with the public when supporting this contract where their status as contractor employees might not otherwise be apparent or where they might be mistaken for civil service employees. As a minimum, contractor management staff and personnel shall clearly identify themselves using the label “contractor” in email addresses in accordance with Federal Acquisition Regulation (FAR) 37.114, Special Acquisition Requirements; opening ALL phone conversations with a statement materially the same as, [office name], I am [employee name], a [prime contractor’s company name] employee” including the employing contractor’s name in the letterhead and/or signature block of any written correspondence; and any other means necessary. Any contractor-supplied badges shall be worn by contractor management staff and personnel, will be visible at all times, and at a minimum, will state: CONTRACTOR, the employee’s full name, employing company’s name, and position (i.e., CONTRACTOR, Jane A. Doe, XYZ Company, Job Title). Air Force issued identification badges and any contractor badges shall be worn above the waistline during the individual’s duty hours.

3.3.3 All government identification shall be surrendered to 402 SMXG Security manager when no longer required.

3.4 Communications Security

3.4.1 All communications with Department of Defense (DoD) organizations are subject to Communication Security (COMSEC) and Information Security (INFOSEC) review.

3.4.2 The DoD authorizes military departments to conduct monitoring and recording of telephone calls and computer transmissions originating from, or terminating at, DoD organizations.

3.4.3 The contractor shall complete government provided Information Assurance Assessment Program (IAAP) training prior to accessing government computer networks. (See Table 1.)

3.5 Operations Security (OPSEC)

Contractors who have access to government facilities or critical information shall complete government provided OPSEC training IAW AFI 10-701.

3.6 Key/Key Card Control Contractor shall establish and implement methods of making sure all keys/key cards issued to the contractor by the government are not lost, misplaced, or used by unauthorized persons. The contractor shall not duplicate any keys/key cards issued by the government. Contractors shall immediately report to the government program manager or contracting officer any occurrences of lost or duplicated keys/key cards. Contractor shall be required, in the event contractor controlled keys/key cards are lost or duplicated, to re-key or replace the affected lock or locks without cost to the government. Contractor shall prohibit the issue of government controlled or provided keys/key cards to any persons other than the contractor employees and personnel authorized by the contracting officer in writing. Contractor shall compensate the government for any harm resulting from negligence from contractor personnel with regard to key/key cards. Key/Key cards shall be returned to the Government when no longer required.

3.7 Quality Control In compliance with the FAR clause 52.246-4 entitled “Inspection of Services”, the contractor shall provide a complete Quality Control Program (QCP) to ensure the requirements of this contract are provided as specified 15 days after contract award. The contracting officer will notify the contractor of acceptance or required modifications (at no additional costs to the government) and obtain acceptance of the plan by the contracting officer before the start of the first operational performance period. (CDRL A002, DI-QCIC-81722, Quality Program Plan)

3.8 Government Surveillance

The government shall periodically evaluate the contractor’s performance by appointing a representative(s) to monitor performance to ensure services are received. The government representative shall evaluate the contractor’s performance through intermittent on-site inspections of the contractor's quality control program and receipt of complaints from base personnel. The government may inspect each task as completed or increase the number of quality control inspections if deemed appropriate because of repeated failures discovered during quality control inspections or because of repeated customer complaints. Likewise, the government may decrease the number of quality control inspections if merited by performance. The contractor shall be responsible for initially validating customer complaints. However, the government representative shall make final determination of the validity of customer complaint(s) in cases of disagreement with customer(s). The Government has the unilateral right to inspect contractor employee qualifications up to the total number of employees on task orders issued to validate that contractor employees meet the labor category qualifications. The contractor shall comply with Government inspection efforts.

3.9 Physical Security The contractor shall be responsible for safeguarding all government property used for contractor performance.

3.10 Hours of Operation

3.10.1 Normal Hours of Operation. The Contractor shall be responsible for designating work hours for their employees but at a minimum shall be available as required by the Government. This may vary depending on location, project, or event.

3.10.2 Generally, the tasks required under this contract shall be executed with the following stipulations:

Typical Workdays shall be 8 hours long and shall be between the hours of 0600 to 1800, Monday through Friday, excluding government observed holidays, except for certain workloads which will require alternate shifts to support 24/7 operations. . The regular workday typically includes a 30 minute lunch. Any variation from the above schedule shall require prior approval of the Contracting Officer. Any work performed outside this timeframe must be coordinated and approved by the Contracting Officer prior to performing work. In the event of the closing of this office (e.g. severe weather conditions, building or base closures, etc.), the contractor cannot bill the Government for hours not performed on the task. The Contractor may work, with prior approval of the Contracting Officer, extended hours to ensure timely completion of work.

3.10.3 Recognized Holidays. Unless otherwise required by the Government, the contractor shall not have access to Government facilities to work on the following federal holidays: New Year’s Day, Martin Luther King Day, Presidents Day, Memorial Day, Independence Day, Labor Day, Columbus Day, Veterans Days, Thanksgiving Day and Christmas Day. If the holiday falls on Saturday, it is observed on Friday. If the holiday falls on a Sunday, it is observed on Monday.

3.10.4 On occasion, services may be required to support an activation or exercise of contingency plans outside the normal duty hours described above. The contractor’s responsibilities for emergency support are as described in paragraph 4.11.1.

3.11 Conservation of Utilities The contractor shall instruct employees in utilities conservation practices. The contractor shall be responsible for operating under conditions which prevent the waste of utilities which include the following:

3.11.1 Lights shall be used only in areas where and when work is actually being performed.

3.11.2 Mechanical equipment controls for heating, ventilation, and air conditioning systems shall not be adjusted by the contractor or by contractor employees unless authorized.

3.11.3 Water faucets or valves shall be turned off after the required use has been accomplished.

3.11.4 Government telephones shall be used only for official government business.

3.12 Safety Requirements

3.12.1 Safety Requirements. The contractor shall comply with safety provisions, i.e., technical specifications, technical publications, Federal Occupational Safety and Health Administration (OSHA) standards, and other nationally or locally recognized sources of safety, health, and fire prevention standards and practices. The contractor will be responsible for the safety and accountability of all their personnel and the Government facilities/property and are subject to enforcement authority by federal and state safety and health officials. The AF is not responsible for ensuring that contractors comply with "personal" safety requirements that do not present the potential to damage Government resources (hearing protection, safety shoes, AF IMT 55). The contractor shall provide all personal protective equipment (hearing protection, gloves, steel-toed shoes, safety glasses, etc.) In addition, the Government is not responsible for medical examinations, hearing testing, and substance abuse testing for contractor employees.

3.12.2 Ten (10) days after contract award, the contractor shall provide a copy of the company's Safety Plan that is required to ensure compliance with the Occupational Safety and Health Act (OSHA) (Public Law 91-596). A copy shall be provided to the CO. The CO will provide the plan to the WR-ALC Safety Office for review. The WR-ALC Safety Office will provide acceptance or non-acceptance within five workings days of receipt to the CO. (CDRL A003, Contractor’s Standard Operating Procedures, DI-MGMT-81580/T)

3.12.3 The contractor Safety Plan shall address in detail the items listed in the Contract Appendix C, Part II through Part IV as applicable. For task specific procedures identified in the Contract Appendix C, the contractor’s internal procedures for those tasks must be identifiable within the submitted Safety Plan or shall be provided in an amendment or addendum to the company’s Safety Plan. If task specific procedures identified in the Contract Appendix C, are not submitted with the contractor’s Safety Plan, the submitted Safety Plan will be returned as NOT ACCEPTED. The contractor will have 5 working days to resubmit the Safety Plan, amendment or addendum to address or correct issues identified for non-acceptance. The WR-ALC Safety Office will provide acceptance or non-acceptance of the resubmission within 5 workings days of receipt to the CO.

3.12.4 Mishap/Incident Reporting. The contractor shall report all mishaps/incidents in accordance with the contract Appendix C. The contractor shall immediately secure the mishap scene and damaged property and impound pertinent maintenance and training records until released by the Government’s Safety Office (WR-ALC/SE). Such release shall be accomplished through the CO.

The contractor shall cooperate and assist Government personnel in the investigation of the incident and submit an Accident/Incident Report within 24 hours of the accident/incident. The

Contractor shall require all subcontractors to comply with required safety, health and fire standards. (CDRL A004, Accident/Incident Report, DI-SAFT-81563/T)

3.13 Technical Orders.

Technical Order usage requirements must be adhered to by all contract personnel. No more than one (1) technical data violation (TDV) or Quality Assessment Rating-3 (QAR-3) per quarter.

3.14 Environmental Management System (EMS)

All contractors who physically perform work on Robins AFB must receive and document Environmental Management System (EMS) awareness training. All prime contractors must complete the training prior to beginning work on Robins AFB and must ensure that all subcontractors comply with this requirement. There are two avenues for contractors to complete EMS training:

(1) With CAC go to 78 CEG/CEV website and click on EMS Awareness Training, choose Option One (https://geobase.robins.af.mil/emstraining/EMSTrainingOptions.aspx).

(2) Without a CAC, request a copy of EMS training from 78 CEG/CEV Workflow Mailbox.

If a company is ISO 14000 certified, the contractor does not have to complete Robins AFB EMS Awareness Training; however, the contractor must submit documentation to the Contracting Officer stating ISO 14000 Certification.

3.15 Green Procurement Program (GPP).

The contractor shall comply with the Green Procurement Program in accordance with Federal (EO 13423) and DoD and AF (GPP) policy. Green Procurement is the purchase of environmentally preferable products and services. These products are preferred because they conserve resources, create less pollution and waste, or eliminate health and safety risks. The Green Procurement Program (GPP) includes these mandatory components:

- Recycled content products, also known as Comprehensive Procurement Guideline (CPG) Items http://www.epa.gov/cpg/products.htm

- Energy Star® and energy-efficient products; energy efficient standby power devices http://www.eere.energy.gov/

- Bio-based products http://www.biobased.oce.usda.gov/fb4p/

- Non-ozone depleting substances http://www.epa.gov/ozone/snap/lists/index.html

3.16 Continuation of Essential Services During Crisis (DFARs).

The Functional Commander/Director has determined, by placing in writing their decision, that this requirement is not Mission Essential (M-E) in accordance with DoDI 1100.22, Policy and Procedures for Determining Workforce Mix and DFARS 237.76, Continuation of Essential Contractor Services.

3.17 Employee Compliance.

The Contractor’s employees shall comply with all established policies, operating instructions, and regulations relating to the performance of assigned duties. These include environmental, health, safety, and security compliance measures (AFI 36-703).

3.18 Training

3.18.1 Any specialized training required to perform an identified task will be defined in Table 1 below.

The government may provide training to contractor personnel if required by individual projects.

The type of training referenced is not general in nature but that which is specialized or unique to the project supported.

3.18.2 The contractor shall ensure employees complete government training identified in Table 1 before performing any services requiring this training. The contractor shall also ensure that annual training is completed within three days of expiration and that new mandatory training is complete within time frames designated by the Air Force.

Table 1 - Government Provided Security Training

Course Name

Course Length

Personnel Category

Initial Quarterly Annual Type of Training

Security Briefings

0.5 hrs All Contractor Personnel

X Classroom or On-The-Spot

Security Training

1 hr All Contractor Personnel

X Classroom

Privacy Act Training

0.5 hrs All Contractor Personnel

X X Internet Web

EIMC

IAAP

Training

0.5 hrs All Contractor Personnel requiring computer access

X X Internet Web

EIMC

Controlled and Restricted Area Training

0.5 hrs All Contractor Personnel requiring access to controlled areas

X X

Internet Web

EIMC

Semi- Annual Security Training

0.5 hrs All Contractor Personnel requiring computer access

X Internet Web

EIMC

OPSEC

Training

1.0 hr All Contractor Personnel requiring computer access

X X Internet Web

EIMC

3.19 Required EIMC Training

3.19.1 First Half of the Year: WR-ALC Installation Security Training, WR-ALC Operations (OPSEC) Training WR-ALC Controlled Area Training, WR-ALC Safe Custodian Training, Secure Voice Responsibility (SVRO) and User Training.

3.19.2 Second Half of the Year: WR-ALC Information Security Training, WR-ALC Personnel Security Training, 402 SMXG Badge and Circulation Control, 402 SMXG Operating Instruction (31-401)

3.19.3 Every Two Years: WR-ALC Derivative Training

3.19.4 Every Three Years: AFOSI Counterintelligence Training AND Protection of the President Training

3.19.5 One Time Initial Training: North Atlantic Treaty Organization (NATO) Training, Initial Security Education Orientation for Cleared Personnel

3.20 Phase Out

In the event the follow-on contract is awarded to other than the incumbent, the incumbent contractor shall cooperate to the extent required to permit an orderly change over to the successful contractor.

3.21 Contract Employee Reporting System.

The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the 402nd Software Maintenance Group via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year. Contractors may direct questions to the CMRA help desk.

Reporting Period: Contractors are required to input data by 31 October of each year.

Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

User Manuals: Data for Air Force service requirements must be input at the Air Force CMRA link. However, user manuals for government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil.

3.22 Contractor Travel. The Contractor shall travel as required, to perform assigned tasks. Official travel will be performed only with the advanced approval of the government Contracting Officer.

All travel expenses will be reimbursed in accordance with the Joint Federal Travel Regulations and per diem rates (JFTR, VOL 1 and VOL 2). Receipts must be presented to the Contracting Officer with the invoice for reimbursement of actual travel costs. Incomplete reports will be returned and certification of services will be withheld until a clear, concise and complete report is received. Trip reports will be delivered no later than 5 days after completion of trip.

3.23 Contractor Data Requirements List (CDRL)

Paragraph Description CDRL Due Date

1.1.3 Monthly Status Report

DI-MGMT-80368A/T

A001 Shall be delivered no later than the 15th of the following month

3.7 Quality Program Plan A002 Shall be submitted 15 days after

DI-QCIC-81722 contract award.

3.13.2 Safety and Health Plan

DI-MGMT-81580/T

A003 NLT 10 days after award and revisions submitted NLT 5 days from receipt.

3.13.4 Mishap/Incident Reporting

DI-SAFT-81563/T

A004 Submit an Accident/Incident Report within 24 hours of the accident/ incident.

4.0 Appendices

4.1 Directives, Publications & References. Contractor shall comply with the following:

Publication Date Publication Reference

AFI 31-501,

Personnel Security Program Management

27 Jan 05 All

AFI 33-202,

Network and Computer Security

26 Sep 03 Chapter 5

AFI 33-115, Volume 2 Licensing Network Users and Certifying Network Professionals

14 Apr 04 All

AFI 33-119,

Air Force Messaging

24 Jan 05 All

AFI 36-703,

Civilian Conduct and Responsibility

1 Aug 99 Paragraphs 5.4, 5.5, 5.6, 5.8, 6, 11, 12 & 14

AFI 91-203,

Air Force Consolidated Occupational Safety Instruction

15 Jun 2012 All

AFI 91-204,

Safety Investigations and Reports

24 Sep 08 All

AFMCI 21-101

Depot Maintenance Activation Planning

14 Jun 2012 All

AFMAN 33-152

User Responsibilities and Guidance for Information Systems

1 Jun 12 All

AFMCI 91-204,

Safety Investigations and Reports

16 Mar 06 All

DODD 5200.2,

DoD Personnel Security Program

9 Apr 99 All

DOD 8570-01-M (Change 3), Information Assurance Workforce Improvement Program

4 Jan 12 Chapter 8

JFTR, Volumes 1 & 2, The Joint Travel Regulations

1 Jun 09 All

WR-ALC OI 31-2,

Security Program

14 Aug 09 Chapters 2, 3, 5 and 7

Public Law 91-596, Occupational Safety and Health Act of 1970

29 Dec 70 All

RAFBI 31-101,

Installation Security

28 Feb 08 Chapters 1, 6, 8 and 10