FA9422-11-R-0001 Amend 1 25Mar11.pdf

SCHEDULE OF CHANGES

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

See Block #2

PAGE OF PAGES

2. AMENDMENT/MODIFICATION NO.

3. EFFECTIVE DATE

25 MAR 2011

4. REQUISITION/PURCHASE REQ.NO.

5. PROJECT NO. (If applicable)

6. ISSUED BY AFNWC/PKE CODE FA9422 7. ADMINISTERED BY (If other than Item 6) CODE

AFNWC/PKE

8150 F AVE SE

BLDG 20226 RM 17

KIRTLAND AFB, NM 87117-5606

CASSANDRA L. CAPUTO 505-853-1977

cassandra.caputo@kirtland.af.mil

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NO.

FA9422-11-R-0001

X 9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended, X is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER.

If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATION OF CONTRACTS/ORDERS,

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

(X )

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: ( ) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

The purpose of this amendment is to update, correct, and clarify the Statement of Work as well as Sections L and M due to industry feedback received on the initial RFP posted 1 March 2011.

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print). 16A. NAME AND TITLE OF SIGNER (Type or print)

DONNA C. HEINZ

15B. CONTRACTOR/OFFEROR 15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 16C. DATE SIGNED

(Signature of person authorized to sign)

BY________________________________________

(Signature of Contracting Officer)

NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (REV.10-83)

PREVIOUS EDITION UNUSABLE Prescribed by GSA ConWrite Version 6.13.0 FAR (48 CFR) 53.243 Created 25 Mar 2011 4:08 PM

LIST OF ATTACHMENTS

FA9422-11-R-0001 0001

DOCUMENT PGS DATE TITLE

ATTACHMENT 1 31 23 NOV 2010 INFRASTRUCTURE, ENGINEERING, AND

DEVELOPMENT (IDE) STATEMENT OF WORK

(SOW)

ATTACHMENT 4 35 23 NOV 2010 SECTION L- INSTRUCTIONS TO THE OFFERORS

ATTACHMENT 5 11 23 NOV 2010 SECTION M- EVALUATION CRITERIA

STATEMENT OF WORK

FOR THE

705 COMBAT TRAINING SQUADRON (CTS)

FOR

INFRASTRUCTURE, DEVELOPMENT, AND ENGINEERING (IDE)

Section J, Attachment 1

TABLE OF CONTENTS

1.0 SCOPE 3

1.1 BACKGROUND 3

1.2 PROGRAM CONCEPT 4

2.0 APPLICABLE DOCUMENTS 5

3.0 REQUIREMENTS 5

3.1 PROGRAM MANAGEMENT AND ADMINISTRATION 6

3.2 INFRASTRUCTURE 13

3.3 DEVELOPMENT 18

3.4 ENGINEERING: EVENT SUPPORT 21

3.5 ENGINEERING: STUDIES & ANALYSIS 24

4.0 CONTRACT MONITORING AND PERFORMANCE EVALUATIONS 25

4.1 MONITORING AND RANDOM/PERIODIC EVALUATIONS 25

4.2 CONTRACTOR PERFORMANCE ASSESSMENT REPORTING 25

5.0 CONTRACT DELIVERABLES 27

6.0 ACRONYM LIST 28

ANNEX 1: WORKLOAD ANALYSIS 32

1.0 SCOPE

The scope of this Statement of Work (SOW) consists of building and maintaining network infrastructure, developing and maintaining software & hardware solutions, and conducting Distributed Mission Operations (DMO) engineering activities for the DMOC. This acquisition supports various DMO activities including: development of new DMO systems; upgrades to existing DMO systems; engineering analysis and feasibility studies in support of development efforts; Operations and Maintenance (O&M) of system and network infrastructure; implementing video/voice/data communication links between systems and facilities; prototyping simulation systems; establishing interoperability between systems/simulators through multiple networks;

maintaining scenario and terrain database generation systems; and implementing interoperability standards. The SOW also covers the management of the DMOC Battlespace at Kirtland AFB, New Mexico, and all necessary management services, personnel, materials, components, supplies, maintenance, and documentation required to accomplish the full complement of IDE tasks.

1.1 BACKGROUND

1.1.1 The mission of the 705 CTS is to “develop, integrate, and deliver a virtual Air, Space, and Cyberspace environment for Air Force, Joint, and Coalition combat training, test, and experimentation.” This mission requires the 705 CTS to maintain a highly-qualified staff of government and contractor personnel with expertise in training, test, and experimentation development and execution, systems integration and interoperability, and DMO technology development.

1.1.2 The 705 CTS promotes the use of DMO capabilities as a realistic means to connect Command, Control, Intelligence, Surveillance, and Reconnaissance (C2ISR) assets and combat systems to train, test and experiment on modern warfighter TTPs. Furthermore, training and testing transformation initiatives within the DoD, such as Live, Virtual, Constructive Integrated Architecture (LVC-IA) will continue to have a major influence on the DMOC. The DMOC regularly connects to a large number of DMO capable resources to include, but not limited to:

1.1.2.1 Live and Virtual Simulators: A-10A, A-10C, AC-130U, Aegis, AH-64D, AOC, ASOC, B-1B, B-2A, B-52H, C-17A, CRC, DASC, DCGS, F-15C, F-15E, F-16C, F-

16CJ, AF-18A, CF-18A, F/A-18C/D, F-22, FIRES Brigade, E-2C, E-3C, E-8C, EP-3E, JTACs, MC-130H, MOC, MQ-1, MQ-9, PATRIOT, RC-135V/W, RQ-4, TOC

1.1.2.2 Constructive Simulators: ACE-IOS, AFSERS, BigTAC, DICE, DIADS, EADSIM, JCATS, NGTS, STAGE, OneSAF

1.1.2.3 Tools: ADSI, AFATDS, AFTRS, ASSET, C2PC, CSEL, Datalinks, Adobe Connect, DIS Filter, DIS DAIDS (ASTi), DIS2GPS Emulator, DIS/TENA gateway, DMOC Digital Radio Simulator, Dr J., DTNG, Radiant Mercury, EXCIS, Fire Cue, Fire Sim, GCCS-J, Replay tool, IFF Surrogate, ISR/BDA/IWMDT, JADOCS, JDT, JRE, MAPSTAT, mIRC, Quick Draw, Redsim, TACP-CAS, TAIS, TBMCS, VoIP, VLC media player, VTC

1.1.2.4 Networks: ARCNet, DREN, DMON, JIOR, JTEN, JWICS, MDACNet, NCTE, T1s

1.2 PROGRAM CONCEPT

1.2.1 The DMOC is a DoD national asset available to USAF, Joint, Coalition, and other government agencies. The DMOC serves as the USAF’s center for DMO integration and interoperability. Military experts with operational experience in Army, Navy, Marine and Air Force Command and Control (C2) theater operations, operate the facility supported by contractor personnel. All personnel are available to assist DMOC facility users. The DMOC is primarily used for the training, testing and experimentation of tactical C2 TTPs regarding Theater Air Ground Systems (TAGS). However, the DMOC provides a rich DMO environment that can be utilized in numerous ways. The DMOC is maintained and operated by military and civil service personnel, supplemented by contractors, whom provide technical expertise concerning components of the DMOC in event planning, execution, data collection, data analysis, and overall system support. DMOC military, government service, and contractors are also responsible for ongoing modifications to the DMOC Battlespace networks, systems and simulators to ensure they represent accurate versions of the warfighting systems modeled.

1.2.2 Utilizing the DMOC and associated resources, the 705 CTS performs training, testing, and experimentation with military personnel operating live weapon systems and high fidelity simulations in a realistic virtual environment. DMOC resources include: simulations of airborne systems; surveillance systems; airborne and ground C2 communication systems; Integrated Air Defense Systems (IADS); voice communications systems, data link systems; data loggers;

network analysis and routing tools; intelligence systems; and collaboration tools.

1.2.2.1 The DMOC leverages multiple threat generators and digital terrain databases to provide a realistic virtual environment. The DMOC is currently capable of simulating up to 50,000 simultaneous air and surface entities in any single environment. The DMOC is also involved in developing standards for modeling Information Operations (IO), Electronic Warfare (EW), and DMO standards.

1.2.2.2 The DMOC is linked to a large number of military and contractor simulation facilities through Point-to-Point (P2P) connections, Local Area Networks (LANs), and Wide Area Networks (WANs). The DMOC primarily utilizes Distributed Interactive Simulation (DIS), but also uses High Level Architecture (HLA) and Test and Training Enabling Architecture (TENA) gateways and corresponding network components to interoperate with a variety of LVC simulation facilities and systems. Translators are available to allow exchange of tactical data link messages between actual field equipment and simulation models.

1.2.3 The 705 CTS executes four VIRTUAL FLAG (VF) exercises a year, multiple Warfighter Focused Events (WFEs), test, experiments, and participates in the planning, facilitation and/or execution of DMO events as directed. Current and interested partners or customers include, but are not limited to:

a. Air Combat Command (ACC)

b. Air Force Research Laboratory (AFRL)

c. Air Force Space Command (AFSPC)

d. Defense Advanced Research Projects Agency (DARPA)

e. Department of Homeland Security (DHS)

f. Headquarters Air Force (HAF)

g. Missile Defense Agency (MDA)

h. Joint Information Operations Range (JIOR)

i. Joint National Test Facility (JNTF)

j. Naval Air Warfare Center (NAWC)

k. Nevada Test and Training Range (NTTR)

l. Office of Secretary of Defense (OSD)

m. Pacific Air Force Command (PACAF)

n. Sandia National Laboratories (SNL)

o. US Army Training and Education Command (TRADOC)

p. US Army Air Defense Artillery School (USAADASCH)

q. White Sands Missile Range (WSMR)

r. Warrior Preparation Center (WPC)

s. Space and Missile Defense Command (SMDC)

2.0 APPLICABLE DOCUMENTS

The infrastructure, development and engineering work performed by the contractor shall be in accordance with applicable DoD and industry standards and policies. Primarily, IEEE 1278.1 (DIS standard) and IEEE 12207.0 (software standard) will be followed. Other applicable standards may include but are not limited to, Joint standards/policies, AF standards/policies, CAF DMO standards, security standards, industry standards (DIS, HLA, TENA, Information Technology (IT) and other IEEE standards). Additional standards to be followed will be specified for each contracting task. If standards/policies conflict, designated 705 CTS personnel will determine which to follow.

3.0 REQUIREMENTS

3.0.1 Under this SOW, the contractor shall provide baseline Infrastructure, Development and Engineering (IDE) support for the DMOC. Baseline contractor support will include management overhead, DMOC Battlespace sustainment, event support (VFs, WFEs, and others), Studies & Analysis (S&A) efforts, travel and other direct costs. The contractor shall support reoccurring events such as DMOC Battlespace Infrastructure, VFs and WFEs as specified in annual Task Orders (TOs). Through TOs as directed, the contractor shall support development, Test and Evaluation (T&E), and other customer funded efforts. Customer funded events include, but are not limited to: training exercises, testing, and experimentation events, technology demonstrations, and proof of concepts as specified by the 705 CTS leadership or designated government personnel. IDE work will be conducted at the unclassified, secret, and potentially Top Secret/Sensitive Compartmented Information (TS/SCI) and Special Access Program/Special

Access Required (SAP/SAR) levels.

3.0.2 This contract will primarily use RDT&E (3600) money and O&M (3400) money.

Additionally, Procurement money (3080) will be used. Multiple Contractor Line Item Numbers (CLINS) will exist for both RDT&E, O&M and Procurement money. The 705 CTS COTR will identify the appropriate type of money and CLIN prior to the start of each contracting task (i.e., TO). The contractor shall appropriately record billable hours (i.e., using the designated type of money and CLIN).

3.0.2.1 RDT&E work typically consists of scheduled and unscheduled development and integration of new DMO capabilities. Examples include, but are not limited to, integration of new DMO systems, DMOC Battlespace modifications and work performed for external customers who provide RDT&E funding.

3.0.2.2 O&M work typically consists of scheduled and unscheduled O&M of DMOC infrastructure. Examples include, but are not limited to, system maintenance, tools and utilities sustainment, general maintenance, and work performed for external customers who provide O&M funding.

3.0.2.3 Procurement money is used to purchase material/equipment directly and is typically used in conjunction with S&A activities, project related ODCs, or other project specific CLINs. Procurement money may also be assigned to perform research or design work without a specific project, which still requires purchase of equipment.

3.1 PROGRAM MANAGEMENT AND ADMINISTRATION

3.1.1 Program Management. The contractor shall establish a single program management structure for all Infrastructure, Development and Engineering (IDE) efforts, ongoing facility management, configuration management, safety, and security programs. (A001)

3.1.1.1 The contractor shall establish a Program Manager (PM) and alternate PM resident at the DMOC as the lead for the contractor work force.

3.1.1.1.1 The PM and alternate shall manage, control, and administer the effort to ensure successful performance of all tasks issued under the contract.

3.1.1.1.2 The PM and alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract.

3.1.1.1.3 The PM or alternate shall be available immediately during normal duty hours to meet on the installation to discuss problem areas. After normal duty hours, the PM or alternate shall be available within 3 hours for this purpose.

3.1.1.2 The contractor shall present quarterly Program Management Reviews (PMRs).

Each presentation will summarize efforts during the reporting period, to address, at a minimum, the following topics:

a. Contractor workload status

b. Overall resource status

c. Project budget status

d. Project schedule status

e. Contractor-identified risks and risk management plans

f. Issues requiring Government decision

g. Government and contractor furnished/purchased property and equipment

3.1.1.3 Program management shall ensure that contractor efforts do not negatively impact pre-event activities, event execution, post-event activities, or the operation of other DMOC Battlespace simulators.

3.1.2 Administration. The contractor shall provide cost, schedule, and performance tracking and forecasting of program status. (A001, A002)

3.1.2.1 The contractor shall provide administration for contractor personnel and equipment in the areas of administrative, personnel, security, safety, configuration management, quality assurance, quality control, subcontractor management, purchasing, and acquisition as required for effective management of the contract.

3.1.2.2 The contractor shall provide a representative to the 705 CTS managed DMOC scheduling shop to include alignment of contractor’s schedule with the 705 CTS master schedule.

3.1.2.3 The Contractor shall provide a monthly status report for program level cost, schedule and performance (A001, A002).

3.1.2.4 The contractor shall provide helpdesk support activities in a 705 CTS managed network operations center. These duties include computer system administration and application support, configuration, network engineering, troubleshooting, and routine maintenance of software and networking tools, and LAN connectivity administration for NIPRnet, and SIPRnet.

3.1.3 Security. The contractor shall ensure compliance with all DMOC security requirements throughout the life of this contract.

3.1.3.1 The contractor shall provide a security manager, resident at the DMOC, with a Top Secret clearance, to represent the contractor as the single point of contact to work with the 705 CTS security staff for all security plans, processes, procedures, and activities. The contractor security manager shall ensure compliance with all DMOC security requirements throughout the life of this contract.

3.1.3.2 The contractor security manager shall implement a security program to include personnel security for assigned contract personnel, documentation, and software/hardware control for items under the control of the contractor.

3.1.3.3 The contractor shall support the 705 CTS security manager(s) in all 705 CTS directed security efforts, measures, activities, and inspections.

3.1.3.4 The contractor shall interface closely with 705 CTS personnel; other contract personnel; security personnel; and others as required ensuring administration and implementation of a security program that complies with all government regulatory requirements.

3.1.3.5 Contractor personnel shall attend quarterly unit security training and additional security training as necessary.

3.1.3.6 The contractor shall accomplish the information protection tasks identified below:

3.1.3.6.1 The contractor shall perform all functions necessary to securely connect external users to the DMOC enclave, including but not limited to management of routers, firewalls, controlled interfaces (i.e., guards), and IPS/IDS systems.

3.1.3.6.2 The contractor shall assist the DMOC IAM, IAO, and the DMOC security contractor, in planning for and implementing compliance with applicable security standards and processes. References include, but are not limited to:

AFPD 33-2; AFI 131-401; AFI 33-210; DCID 6/3, JAFAN 6/3; DoDD 5200.1;

DoDD 8100-2; CJCSM 6510; CJCSI 6212.01D; and CJCSI 6510.01E.

3.1.3.6.3 The contractor shall provide certified privileged users for DMOC networks as well as additional systems as directed by the 705 CTS in accordance with DoD 8570.01, to include, e.g., system/network administrators, in order to support audits, scans, system configuration, and other Certification and Accreditation (C&A) activities conducted by the 705 CTS or the DMOC security contractor. At contract start, all personnel involved in IA functions/positions shall be required to be certified and trained IAW DoD 8570.01-M. All personnel involved in IA functions/positions in support of the certification/accreditation and maintenance of DMOC Battlespace networks and additional networks as directed by 705 CTS shall be required to comply with the following references.

References include, but are not limited to: AFPD 33-2; AFI 33-210; DoDI 8500.2; DODD 8100.2; DoDD 8500.01E; DoDI 8510.01; DoD 5220-22-M;

DoDD 5230.11; DoDD 5230.20; AFI 33-204; AFI 33-137; AFMAN 33-223; and AFI 33-115V1, DCID 6/3, and JAFAN 6/3.

3.1.3.6.5 The contractor shall perform all functions necessary to sustain the IA controls assigned to the Battlespace network. The Battlespace network is a MAC III classified network as per DoDI 8500.2. As a MAC III classified network all applicable IA controls assigned which will be maintained/sustained. All associated IA controls requiring checklists or contingency plans will be exercised at minimum yearly to determine currency. All IA controls will be exercised for an annual security review.

3.1.3.6.6 The contractor shall support the C&A of Government Furnished Equipment (GFE), Government off-the-shelf (GOTS) and Commercial off-the-shelf (COTS) as necessary to meet mission requirements.

3.1.3.6.7 The contractor shall support the application of Security Technical Implementation Guides (STIG).

3.1.3.7 The Contractor shall comply with all applicable laws and regulations regarding export-controlled items, including, but not limited to, the requirement for contractors to register with the Department of State in accordance with the ITAR. The Contractor shall consult with the Department of State regarding any questions relating to compliance with the ITAR and shall consult with the Department of Commerce regarding any questions relating to compliance with the FAR.

3.1.4 Safety. The contractor shall comply with the 705 CTS unit safety program by implementing a corporate safety program to include: regular safety briefs; safety problem reporting procedures; and reporting of safety problems/corrective actions to the 705 CTS Safety Officer.

3.1.4.1 The contractor shall attend quarterly unit safety awareness training.

3.1.4.2 The contractor shall correct safety discrepancies per 705 CTS guidance.

3.1.4.3 The contractor shall support audits of the safety program at intervals set forth by the 705 CTS Safety Officer.

3.1.5 Facility Management. The contractor shall provide a responsible person for general facility management of the classified and unclassified portions of the DMOC facility, Building 942 on Kirtland AFB. The contractor shall report all facility maintenance activities to the 705

CTS. (A003)

3.1.5.1 With 705 CTS approval, the contractor shall coordinate with the Air Force Materiel Command (AFMC), 377th Air Base Wing Mission Support Group (MSG) Facilities Division to perform maintenance and repairs of Building 942 which do not fall within the scope of the base support agreement. Repairs requiring significant modification or alteration (i.e. the closing or barricading of work areas, structural removals, add-ons) to Building 942 will require coordination with the 377th MSG Facilities Division and 705 CTS approval prior to execution.

3.1.5.2 The contractor shall store and track all documents and software materials pertaining to Building 942. Backups of current floor plans, wiring diagrams, and network diagrams will be stored in the library.

3.1.5.3 The contractor shall provide a quarterly Facilities Maintenance Report. (A003)

3.1.6 Contractor Personnel. In support of the DMOC missions outlined in the SOW, the contractor shall employ personnel in job categories as defined in Table 1 below. Throughout the life of the contract, personnel must maintain currency of experience as related to the technical requirements of the SOW. Currency is defined as experience within the last 5 years.

Table 1 Labor Category Description Program Manager Master of Science (MS) in engineering or an analytical discipline with

15 years of experience, or Bachelor of Science (BS) in engineering or related operational discipline with 20 years experience. Experience must be in engineering and/or operations management and must include 5 years of specific experience in C2 systems design, weapon air defense systems, or program management.

Senior Engineer/ Technical Director

MS (Engineering, Computer Science, or related discipline) with 10 years relevant experience, BS in the same fields with 15 years relevant experience, or no degree and 20 years relevant experience.

Engineer/Programmer/ IT Professional

MS (Engineering, Computer Science, or related discipline) with 3 years experience, BS in the same fields with 5 years relevant experience, or no degree and 10 years relevant experience.

Jr Engineer/ Programmer/ IT Professional

MS (Engineering, Computer Science, or related discipline) with no experience, BS in the same fields with 2 years relevant operational experience or no degree and 6 years relevant experience.

Systems Engineer MS (Systems Engineering, or related discipline) with 3 years experience, BS in the same fields with 5 years relevant experience, or no degree and 10 years relevant experience.

Technician BS in a relevant area with 1 year experience or no degree and 3 years related operational experience.

3.1.6.1 All contractor employees shall maintain, at a minimum, a Secret level clearance.

3.1.6.2 At least 50% of contractor employees shall maintain a Top Secret clearance. At a minimum, the Program Manager and other identified critical positions will require a Top Secret clearance.

3.1.6.3 At least 25% of contractor employees with a Top Secret clearance shall maintain Sensitive Compartmented Information (SCI) and Special Access Program/Special Access Required (SAP/SAR) eligibility (see DD 254).

3.1.6.4 The contractor shall continually pursue currency in the performance of the duties and requirements in the SOW.

3.1.6.5 The positions described below have been identified as critical/key areas that require extra consideration during the life of the contract to include transition/phase-in activities. The management of these areas covers critical mission requirements essential to the success of IDE support activities at the 705 CTS. The contractor’s transition plan shall ensure these critical/key positions are filled with qualified personnel on day 1 of the transition/phase-in period and through the life of the contract (A008).

3.1.6.5.1 Program Manager: Position is responsible for program management and the performance of all work associated with this SOW and will respond to requirements set by the contract. This position corresponds to the “Program Manager” description in Table 1.

3.1.6.5.2 Division/Group leads: These key positions are responsible for supporting the DMOC Battlespace infrastructure, development of new and upgraded system capabilities, O&M activities, and engineering DMO solutions.

These positions correspond to the “Senior Engineer/Technical Director” in Table 1.

3.1.7 Personnel Considerations. The contractor shall not employ any person who is an employee of the United States Government if the employment of that person would create a conflict of interest, nor shall the contractor employ any person who is an employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives approval in accordance with the Joint Ethics Regulation.

3.1.7.1 All contract employees assigned to the DMOC program shall be US citizens.

3.1.7.2 Contractor employees shall present a neat and professional appearance and be easily recognized as contractor employees through the wearing of company lanyards displaying any required identification.

3.1.7.2.1 Employee identification shall be visible at all times.

3.1.7.2.2 Contractor employees entering controlled areas are required to display a DMOC controlled area badge.

3.1.7.3 The contractor shall not employ persons for work on this contract if such employee is a potential threat to the health, safety, security, and general well being or operational mission of the installation and its population.

3.1.7.4 The selection, assignment, reassignment, transfer, supervision, management, and control of employees in performance of this work statement shall be the responsibility and prerogative of the contractor. 705 CTS leadership must be immediately notified in writing of any changes to critical/key personnel. Changes in critical/key personnel require at least 2-week notice before changes are made.

3.1.7.5 The contractor shall comply with the requirements set forth in this SOW, unit policies and instructions, and in Kirtland AFB regulations concerning conduct of employees as referenced herein.

3.1.8 Duty Hours. The DMOC core duty hours shall be from 0900 to 1500 on non-event periods (i.e., not exercise, training, test, or experimentation days), Monday through Friday (i.e., 5 days per week). When necessary, additional contractor support shall be provided outside core hours to support extended periods for event execution, training, test or experimentation. DMOC events may require use of intermittent, planned/unplanned overtime, or adjusted work hours (non-core duty hours).

3.1.8.1 The DMOC Battlespace shall be open from 0600-1800, Monday through Friday (i.e., 5 days per week).

3.1.8.2 The helpdesk shall be open from 0700-1700, Monday through Friday (i.e., 5 days per week). Contractor personnel shall support the 705 CTS helpdesk using a staggered schedule.

3.1.8.3 Government holidays shall be observed during non-event periods.

3.1.8.4 The contractor shall assume a requirement for event support coverage over weekends when deemed necessary by 705 CTS personnel.

3.1.9 Meetings/Conferences. The contractor shall attend and participate in staff meetings, senior steering groups, activity control boards, process reviews, program reviews, design reviews and other such meetings as required. The contractor shall support 705 CTS meetings with appropriate personnel at all times. (A006)

3.1.9.1 Following contractor led meetings at DMOC for IDE activities, the contractor shall provide meeting minutes for delivery.

3.1.9.2 Following external conferences/symposiums/meetings for DMOC supported activities, the contractor shall provide minutes for delivery.

3.1.10 Documentation. The contractor shall provide and maintain programmatic and technical documentation, to include budgetary figures, DMOC Battlespace documentation, system instructions, and additional documentation developed under this contract. (B013)

3.1.10.1 The contractor shall generate the appropriate documentation on upgrades and enhancements to current systems made during the life of this contract. All documentation updates will conform to the current format of the document.

3.1.10.2 New and updated documentation shall be developed in accordance with contractor specifications and 705 CTS approval. (B013)

3.1.11 Library Activities. The contractor shall maintain the 705 CTS library for the use by all DMOC personnel (government and contractors), customers, and others as needed. The library will be used to store system documentation, contractor generated technical documentation, media resources, non-proprietary contract deliverables, After Action Reports (AARs), lessons learned reports, history of activities, meeting minutes, and other directed documents or media.

3.1.11.1 The contractor shall store and track all documents and software materials classified SECRET and below; maintenance of classified documents shall comply with current security regulations.

3.1.11.2 All library information shall be made available to 705 CTS personnel upon request for audits or reviews.

3.1.11.3 The contractor shall capture, catalog, index and maintain the consolidated reference library.

3.1.11.4 The library shall use a documented 705 CTS approved check-in/check-out procedure.

3.1.11.5 The contractor shall maintain hardware/software documentation within the library, including both hard copies and digital media.

3.1.12 Audits. The contractor shall participate as needed in all audits (functional and physical) conducted by or on behalf of the 705 CTS for the software and documentation associated with each audit. The contractor shall ensure that appropriate contractor configuration management and test manager personnel are adequately represented at configuration boards, as needed. The contractor shall submit for review and written approval the minutes to all Configuration Boards.

3.1.14 Travel. The contractor shall support working, technical, and interchange trips as directed by the 705 CTS. Such travel, include but are not limited to: conferences, symposiums, trade shows, users groups, and working groups. Following all trips, the contractor shall provide trip reports or meeting minutes (whichever is appropriate) for delivery, in addition, to the presented information (if a 705 CTS representative is not in attendance). (A006)

3.1.15 Process Improvement. The contractor should actively provide recommendations for process improvements to DMOC operations for all efforts conducted under the life of this contract to designated 705 CTS personnel for an implementation decision.

3.1.16 Transition. It is anticipated that mission essential work will be in progress through the transition or phase-in/phase-out period of this contract. Therefore it is essential that attention be given to minimizing any interruption. The contract must provide for maximum cooperation between successor and incumbent contractors while ensuring no work receives inadequate attention during the phase-in/phase-out period. The contractor must plan for the transfer of work control delineating the method for processing and assigning tasks during the phase-in/phase-out period. (A008)

3.1.16.1 The contractor shall develop a transition plan describing how program success will be ensured, including: how phase-in requirements will be met, workload estimates, priority allocations of personnel and resources, scheduled completion dates of key events, and plans for mitigating risk factors. The plan must identify key positions, including why they are considered key, and provide resumes for key positions. The plan must also address the need to train and certify new contractors if the incumbents are not retained.

The contractor shall ensure uninterrupted service and mission continuity of the 705 CTS requirements during the phase-in process, including providing all necessary qualified personnel. (A008)

3.1.16.2 The contractor shall ensure a smooth transition with the successor during the phase-out period, prior to completion of contractual performance. The contractor shall work with the successor during a 30-day phase-out period beginning no earlier than 30 days prior to scheduled contract completion. The contractor shall aid the successor in the development of plans, procedures and methods for assumption of all on-going work. The contractor shall provide an orderly transition of work acceptance and accomplishment so that full control by the successor is achieved by the end of the phase-out period.

3.2 INFRASTRUCTURE

3.2.1 Operations and Maintenance. The contractor shall perform Operations & Maintenance (O&M) activities for all 705 CTS owned/leased/loaned assets in the DMOC Battlespace.

Additionally, the contractor shall support vendor owned systems (e.g., AWACS) in the DMOC Battlespace. O&M of DMOC Battlespace infrastructure includes activities that must be performed whether or not an event is scheduled. The contractor shall perform O&M activities consistent with the contractor Configuration Management Plan (CMP), Configuration Review Board (CRB) and applicable industry standards as approved by the 705 CTS. The contractor shall operate, troubleshoot, track, and maintain DMOC Battlespace assets (i.e., systems, simulators, computers, servers, and network resources). The contractors shall suggest improvements to DMOC Battlespace assets. (A003, A004, A007, B001, B002, B012, B013)

3.2.1.1 The contractor shall schedule and perform preventive and routine maintenance, as established by industry best practices and 705 CTS direction. All maintenance will be performed on a non-interference basis with pre-event, event, and post-event execution and 705 CTS approval.

3.2.1.1.1 The contractor shall coordinate all maintenance activities that impact facility availability with the 705 CTS.

3.2.1.1.2 The contractor shall test computer and node systems daily for necessary functionality and perform system checkout runs of the entire Battlespace and deliver reports to the 705 CTS on all hardware, software and procedural problems encountered. (B012)

3.2.1.1.3 The contractor shall document maintenance functions, including, but not limited to: system; database; network administrative functions; security posture of all Battlespace assets (hardware/software); integration of new operating software/system versions; and problem resolution for all Battlespace systems.

3.2.1.2 The contractor shall anticipate, identify, troubleshoot and correct problems/errors with DMOC Battlespace assets. The contractor shall document and report to the 705 CTS all identified problems/errors. The contractor shall suggest corrective actions for all reported problems/errors. (B012)

3.2.1.2.1 Problem/error correction responsibility includes resolution of problems in DMOC Battlespace software, hardware resources, and supporting documentation which exist at contract inception or are developed under this contract. Responsibility also includes correction of software/hardware and computer/network interfaces to 705 CTS maintained equipment.

3.2.1.2.2 The contractor shall correct problems on a priority basis as determined by the 705 CTS.

3.2.1.2.3 The contractor shall report vendor/COTS problems on a priority basis as determined by the 705 CTS to the respective company for repair and include the submission into their problem reporting.

3.2.1.2.4 The contractor shall perform trend analysis of the number and cause of DMOC Battlespace asset problems/errors.

3.2.1.2.5 The contractor shall recommended improvements to alleviate negative trends and mitigate future failures.

3.2.1.3 The contractor shall implement and follow 705 CTS approved procedures for reporting and tracking all Battlespace changes in accordance with 705 CTS approved processes (i.e., the CRB and the CMP).

3.2.1.3.1 The contractor shall record and document all DMOC Battlespace and facility maintenance activities in accordance with the 705 CTS processes. (A003, B013)

3.2.1.3.2 All maintenance and repair records shall be made available within 24 hours of 705 CTS request.

3.2.1.3.3 The contractor shall maintain a record of Engineering Change Requests (ECRs) for the duration of the contract, including all final dispositions.

3.2.1.3.4 The contractor shall report the status of all open ECRs weekly.

3.2.1.3.5 The contractor shall not execute or close ECRs without 705 CTS approval.

3.2.1.3.6 After the ECR is incorporated in the Battlespace, it will be covered by the O&M activities.

3.2.1.4 The contractor shall track and inventory all DMOC Battlespace assets and support equipment (i.e., maintain and provide a Bill of Materials (BOM) or Equipment Inventory Records (EIRS)). All equipment purchased under this contract is owned by the

705 CTS. (A007)

3.2.1.4.1 The contractor shall maintain and deliver the BOM/EIRS semi-annually or upon request.

3.2.4.1.2 The contractor shall update the BOM/EIRS within 24 hours of receiving new equipment.

3.2.4.1.3 The contractor shall request, secure, and track all accountable Battlespace COMSEC keying material and maintenance manuals.

3.2.4.1.4 The contractor shall also order, ship, receive, courier, and secure required cryptographic equipment.

3.2.1.5 The contractor shall build and document network configurations for DMOC Battlespace assets as required (i.e., LAN and WAN connectivity). This includes network, data communications equipment and COMSEC equipment. (B002)

3.2.1.5.1 The contractor shall provide network documentation as required.

Updated network maps of the LAN and WAN will be delivered by the contractor as required.

3.2.1.5.2 The contractor shall provide support for all agreements with outside agencies desiring to establish internal or external connectivity with the DMOC.

3.2.1.6 The contractor shall operate, maintain, and document DMOC audio-visual equipment. This includes instruction on the operation of DMOC audio-visual equipment, which includes VTC equipment, collaboration software/hardware, and voice equipment.

The contractor shall configure the VTC, collaboration, and voice systems to meet the user’s requirements within the design limitations of the systems.

3.2.1.7 The contractor shall provide O&M for tactical data link equipment.

3.2.1.8 The contractor will maintain an inventory of critical spare parts (i.e., those with a high failure rate or of critical importance) for the DMOC Battlespace. (A004)

3.2.1.9 The contractor shall provide support (i.e., installation, operation, configuration management, shipping, receiving, equipment tracking, network modification, and facility planning) for equipment provided by DMOC customers (to include the 705 CTS).

3.2.1.10 The contractor shall operate and maintain Multi-Level Security (MLS), Cross Domain Solutions (CDS), and Multi-National Information Sharing (MNIS) solutions in support of training, test, and experimentation events, including all integration and testing periods as necessary. These duties and tasks include: system administration; file and account management; support of ruleset updates; support of ruleset regression testing;

database maintenance activities; installing software updates and patches; coordinating application error correction; problem reporting, backups, network configurations; and support of system security auditing requirements.

3.2.1.11 The contractor shall perform routine tasks in support of DMOC Battlespace O&M, including, but not limited to: maintaining necessary levels of computer supplies;

loading and unloading computer paper; changing printer cartridges; keeping computer rooms clean; and cleaning console screens.

3.2.2 Configuration Management. The contractor shall establish, document, maintain, and comply with a Configuration Management Plan (CMP) for the DMOC Battlespace as approved by the 705 CTS. All DMOC Battlespace systems, hardware, software, and equipment including COTS, GOTS and GFE shall be placed under the contractor's internal configuration control. The CMP will provide approved procedures for identifying and correcting DMOC Battlespace deficiencies. The CMP will discuss plans for configuration control of DMOC Battlespace assets (e.g., software, hardware, interfaces, etc.). (B001, B002)

3.2.2.1 The contractor’s CMP shall be implemented within 15 days of contract award.

3.2.2.2 The contractor shall update the CMP within 72 hours of modifications to the DMOC Battlespace.

3.2.2.3 The contractor shall control all COTS, GOTS and GFE hardware/software used and/or developed under this contract under an approved CMP. This includes pre-event and post-event system software, event specific software, and software for all remote sites developed or furnished by DMOC.

3.2.2.4 The contractor shall provide documentation control functions for all DMOC documentation, to include the initial DMOC baseline, changes to the baseline, and all new documentation developed under this contract.

3.2.2.4.1 The contractor shall make all documentation control changes to applicable hard and/or electronic copies/digital media.

3.2.2.4.2 The contractor shall include correction of documentation errors, the capability to produce and control documentation changes, and the generation and maintenance of new documentation. (B013)

3.2.2.5 The contractor shall ensure that appropriate contractor configuration management and O&M personnel are adequately represented at configuration boards.

3.2.3 Software Environments. The contractor shall perform O&M of DMOC software environments, including, but not limited to: development environments for the programmers to develop and test code; a test environment to verify software form, fit, and functionality; and an operational environment to be used for reliability and user testing.

3.2.4 Backups. The contractor shall make daily, weekly, and monthly backups of DMOC system software in accordance with documented and 705 CTS approved procedures defined in the contractor's CMP. (A001)

3.2.4.1 The contractor shall provide monthly full system backups, to include all software, to be stored off-site at Government furnished facilities.

3.2.4.2 The contractor shall provide reports to the 705 CTS describing backup actions taken, status of backups, items backed up, and any problems encountered.

3.2.5 License Control. The contractor shall maintain all commercial software licenses; to include documentation, upgrades, and software versions for Battlespace systems. At the conclusion of the contract, all commercial software licenses and documentation shall be transferred to the 705 CTS.

3.2.5.1 The contractor shall maintain a current log of all software licenses used for operation, development, or maintenance of the DMOC Battlespace. The log will contain the name of the software, version, expiration date, quantity, function, and cost of renewal.

3.2.5.2 The contractor shall report the status of DMOC’s software licenses as requested by the 705 CTS.

3.2.6 Audits. The contractor shall support audits conducted by the 705 CTS.

3.2.7 Requirements. The contractor shall analyze submitted requirements and develop cost, schedule, performance, and technical impact studies for DMOC requirements. The contractor shall use event AARs or other reports/reviews to examine the feasibility of new user requirements, upgrades, or DMOC Battlespace enhancements.

3.3 DEVELOPMENT

3.3.1 System Development. The DMOC Battlespace frequently requires the modification of existing systems/software and/or the addition of new systems/software to enhance training, testing and experimentation capability. Development requirements may include modifications to environment generators, constructive simulations, integration of new weapon platforms, modifications to an existing weapon platform, upgrading subsystems, currency upgrades of existing performance features, and upgrades to hardware, software, or firmware to improve system operation, connectivity, and/or interoperability. All development requirements will be approved by 705 CTS personnel for performance, schedule and cost consideration. (B003, B004, B005, B006, B007, B010, B011)

3.3.1.1 The contractor shall develop software in accordance with industry best practices tailored to meet 705 CTS requirements.

3.3.1.2 The contractor shall establish, document, maintain and comply with 705 CTS approved Software Development Plans (SDPs). The SDP shall include documented and approved procedures which comply with industry standards for structured design, development, integration, and testing of all application, interface and system software upgrades, and enhancements implemented during the life of this contract. Each SDP must support the widely varying requirements for engineering processes, software development and documentation of 705 CTS projects. SDPs shall be written as defined by the 705 CTS development approval process. Existing SDPs shall be modified as necessary. (B003)

3.3.1.2.1 All hardware/software developed under this contract, including that developed for temporary or permanent remote sites, is required to be in compliance with applicable industry standards and the SDP.

3.3.1.2.2 The contractor shall develop software for each project in accordance with the project’s requirements as approved by the 705 CTS.

3.3.1.2.3 The contractor shall fabricate hardware and code software consistent with the design developed under the SDP and approved by the 705 CTS.

3.3.1.3 The contractor shall develop and follow the applicable SDP for all system software developed, modified or upgraded during the life of this contract. The contractor shall comply with applicable industry standards for the structured design, development, integration, and testing of all software developed, modified or upgraded during the life of this contract.

3.3.1.3.1 The contractor shall use documented and approved procedures to ensure software quality, version control, and integrity throughout the software development life cycle.

3.3.1.3.2 The contractor shall establish and implement procedures and processes for upgrading the DMOC Battlespace baseline software in accordance with applicable industry standards and/or 705 CTS approved SDPs when upgrades are required. This includes all current, allocated, functional, and operational baselines used by DMOC Battlespace, in addition to all customer baselined software.

3.3.1.3.3 The contractor shall establish and implement methods and procedures to ensure software quality and integrity are addressed throughout the software development life cycle in accordance with applicable industry standards and the

SDP. (B003, B004, B005, B006, B007, B010, B011)

3.3.1.3.4 The contractor shall design and develop software in accordance with industry standards.

3.3.1.4 All software written, including routine software maintenance, shall be compatible with existing DMOC software/systems.

3.3.1.5 In all system development, the contractor shall comply with applicable STIGs, as specified by the 705 CTS IAO or IAM.

3.3.1.6 The contractor shall document users manuals for software/hardware systems or features of system for which no users manuals exist. (B011)

3.3.2 Design. The contractor shall design and modify hardware/software to meet development requirements of the 705 CTS. This includes requirements analysis and design recommendations for GFE/GOTS/COTS/Custom items, interfaces, and system integration into the DMOC Battlespace. (B005, B006, B007)

3.3.2.1 The contractor shall utilize industry standards or other 705 CTS approved specific software engineering processes to design, document, and integrate new systems/software into the DMOC Battlespace..

3.3.2.2 When effective to do so, the contractor shall use GFE, GOTS or COTS equipment to meet requirements. GFE or GOTS products shall be considered before other options

3.3.2.3 The contractor shall ensure computer and software resources are compatible with all necessary interfaces and do not degrade performance of existing systems.

3.3.2.4 The contractor shall generate design documentation for developed or modified systems during the life of this contract; all documentation shall conform to applicable industry standards, the SDP,…