N00421-18-R-0034_-_DRAFT_RFP.docx

N0042118R0034

Section A - Solicitation/Contract Form

GENERAL INFORMATION

Contract Specialist:

Travora Levasseur

(301) 757-1943 Travora.Levasseur@navy.mil

Contracting Officer:

Christopher Pennini

(301) 757-5980 Christopher.Pennini@navy.mil

CONTRACTING OFFICER’S REPRESENTATIVE: TO BE DETERMINED AT CONTRACT AWARD

(1) This solicitation is reserved for competition among small business concerns in accordance with FAR 52.219-8 Total Small Business Set-Aside. The resultant award will be a Single Award Indefinite Delivery/Indefinite Quantity contract.

(2) The Product/Service Code (PSC) for this procurement is AC14. The NAICS code is 541715 and the small business size standard is 1,500 employees..

(3) This contract includes Cost-Plus-Fixed-Fee (CPFF) contract line item numbers (CLINs) for labor and cost reimbursable (no fee) CLINs for Other Direct Costs (travel and material).

(4) This contract is for an ordering period of five (5) years.

(5) The contractor will not be authorized to access any classified information until a final DD Form 254 is incorporated as an Attachment to this contract.

(6) The offeror’s proposal may be incorporated into the contract upon award.

(7) Task orders may be issued under this single award Indefinite Delivery Indefinite Quantity (IDIQ) contract. NAVAIR clause 5252.211-9503 Level of Effort (Cost Reimbursement) (NAVAIR) (DEC 2012) will be included in applicable task orders.

Section B - Supplies or Services and Prices

CLIN PRICING

(1) While CLINs 0002 through 0006 and 0008 through 0012 are not separately priced (NSP) at the IDIQ level, they will be priced when utilized at the task order level.

(2) All labor ceiling, inclusive of cost and fee, for CPFF CLINs 0002 through 0006 (NSP CLINs) is included in the overall ceiling for CLIN 0001.

(3) All other direct cost ceiling for COST CLINs 0008 through 0012 (NSP CLINs) is included in the overall ceiling for CLIN 0007.

CPFF Labor Ceiling for CLINs 0002-0006

CPFF

Cost Plus Fixed Fee (CPFF) Labor Ceiling for CLINs 0002-0006.

FOB: Destination

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

UNDEFINED

Labor - RDT&E Funding

Research Development Test & Evaluation (RDT&E) Labor in accordance with paragraphs 3.3.1 - 3.3.5.2 in the SOW. Not Separately Priced from CLIN 0001.

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

UNDEFINED

Labor - O&M Funding

Operations and Maintenance (O&M) Labor in accordance with paragraphs 3.3.1 - 3.3.5.2 in the SOW. Not Separately Priced from CLIN 0001.

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

UNDEFINED

Labor - NWCF Funding

Navy Working Capital Fund (NWCF) Labor in accordance with paragraphs 3.3.1 - 3.3.5.2 in the SOW. Not Separately Priced from CLIN 0001.

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

UNDEFINED

Labor - Procurement Funding

Procurement Labor in accordance with paragraphs 3.3.1 - 3.3.5.2 in the SOW. Not Separately Priced from CLIN 0001.

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

UNDEFINED

Labor - FMS Funding

Foreign Military Sales (FMS) Labor in accordance with paragraphs 3.3.1 - 3.3.5.2 in the SOW. Not Separately Priced from CLIN 0001.

MAX COST

FIXED FEE

TOTAL MAX COST + FEE

ODC Ceiling for CLINs 0008-0012

COST

Other Direct Cost (ODCs) Ceiling for CLINs 0008-0012 in accordance with paragraph 3.1.5 in the SOW. NOTE: The requirements in DFARS 252.211-7003, Item Identification and Valuation, are applicable for this line item. The contractor shall provide DoD unique identification or a DoD recognized unique identification equivalent.

MAX COST

UNDEFINED

ODC - RDT&E Funding

Research Development Test & Evaluation (RDT&E) ODC in accordance with paragraphs 3.1.5 in the SOW. Not Separately Priced from CLIN 0007.

MAX COST

UNDEFINED

ODC - O&M Funding

Operations and Maintenance (O&M) ODC in accordance with paragraphs 3.1.5 in the SOW. Not Separately Priced from CLIN 0007.

MAX COST

UNDEFINED

ODC - NWCF Funding

Navy Working Capital Fund (NWCF) ODC in accordance with paragraphs 3.1.5 in the SOW. Not Separately Priced from CLIN 0007.

MAX COST

UNDEFINED

ODC - Procurement Funding

Procurement ODC in accordance with paragraphs 3.1.5 in the SOW. Not Separately Priced from CLIN 0007.

MAX COST

UNDEFINED

ODC - FMS Funding

Foreign Military Sales (FMS) - ODC in accordance with paragraphs 3.1.5 in the SOW. Not Separately Priced from CLIN 0007.

MAX COST

NSP

Technical Data in accordance with Exhibit A. Not Separately Priced.

CLAUSES INCORPORATED BY FULL TEXT

TO BE SPECIFIED IN INDIVIDUAL TASK ORDER

Section C - Descriptions and Specifications

STATEMENT OF WORK

1.0 Scope

The Integrated Battlespace Simulation and Test (IBST) Department, Naval Air Warfare Center- Aircraft Division (NAWCAD) 5.4, is the Naval Air Systems Command’s (NAVAIR) center of excellence for modeling and simulation of the Battlespace environment. The Simulation Division, NAWCAD 5.4.3, is one of five divisions within IBST and is responsible for simulation expertise and products for naval aviation systems and the Battlespace environment within which they operate. Battlespace, distributed simulation, and live-virtual-constructive events are used throughout the acquisition lifecycle to reduce risk and improve the quality of naval aviation systems.

The Simulation Division develops, implements, and maintains software applications and tools to support Battlespace and distributed simulations. Simulation Division products are used for requirements analysis, test and evaluation, and training applications across Department of Defense (DoD) and for Foreign Military Sales (FMS) customers. The principal Battlespace simulation product developed and maintained by the Simulation Division is the Next Generation Threat System (NGTS). NGTS is a synthetic environment generator used to support training, testing, analysis, and research and development. NGTS models threat and friendly aircraft, ground and surface platforms, and their corresponding weapons and subsystems. NGTS is currently installed in multiple DoD training systems, distributed exercise centers, as well as international military training environments. Other distributed simulation products include the Architecture Management Integration Environment (AMIE), and the Joint Integrated Mission Model (JIMM). Support is also provided for standard protocols enabling battlespace simulation that include Distributed Interactive Simulation (DIS), High Level Architecture (HLA), and the Test and Training Enabling Architecture (TENA).

The scope for this contract is for engineering and technical services in support of Battlespace simulation and distributed simulation. Support to be provided includes the development and maintenance of Battlespace simulation tools, application of battlespace simulation tools to specific customer requirements, development of warfare scenarios, development and integration of battlespace entity models and behaviors, and operation and maintenance customer support for delivered battlespace products.

2.0 Applicable Documents

The Contractor shall conform to applicable Department of Defense (DoD), Department of the Navy (DoN), and IBST procedures and standards in the performance of this contract. The Contractor shall comply with the most current version of all applicable security standards and procedures.

2.1 Department of Defense Specifications

2.1.7

2.1.8

OPNAVINST 3440.17A

OPNAV 5239.14

Navy Installation Emergency Management Program, 1 Aug 2014

System Authorization Access Request Navy (SAAR-N) Sep 2011

2.2 Department of Defense Standards

2.2.3

2.2.4

2.2.5

DOD-D-5220.22

NASPAXRIVERINST 5510.15Q

DoD Instruction 8520.2 National Industrial Security Program

Regulations Governing Admission to the Naval Air Station Patuxent River (NAS Pax River), Webster Field Annex and Navy Recreation Center (NRC) Solomons, Maryland, 7 Mar 2012

Public Key Infrastructure (PKI) and Public Key (PK), 24 May 2011

2.3 Simulation Division (5.4.3) Standards and Procedures

3.1 General Requirements

3.1.1 Compatibility.

The Contractor shall maintain the capability to prepare documents and software packages compatible with the Government Information Technology (IT) environment through the security classification of General Service (GENSER) Secret. The current operating environment required for this contract includes:

Microsoft Windows 10 Microsoft Project 2016 Microsoft Office Professional Plus 2016 Adobe Acrobat XI (reader) Internet access

Contractor owned computers for Software Developers may also require:

Visual Studio 2015 Git Repository Swift Source Tree Dynamic Object Oriented Requirements System (DOORS)

The Contractor shall maintain the ability to interface with and transfer data to and from requiring office software applications and their upgraded versions. The Contractor shall ensure that all media are virus free when delivered. The Contractor shall be capable of Internet and Local Area Network (LAN) communications with the IBST Department, NAWCAD 5.4. Contractor personnel shall be capable of maintaining real-time communications, both voice and data transfer capabilities, with IBST Department, NAWCAD 5.4 during working hours whether at Contractor work site or on travel.

3.1.2 Work Location and Facilities.

3.1.2.1 Work Location: Approximately 25% will be performed at Government site and 75% will be performed at Contractor site. Government site is Patuxent River, Maryland. Contractors performing on-site support will be provided access to workspaces, telephones, printers, facsimile machines, copy machines, shredders, computers, and network access including web servers and applicable databases or other applications necessary to carry out assigned tasks. Off-site Contractor spaces shall be within 20 miles driving distance to Patuxent River NAS. The Contractor’s spaces shall include a GENSER Secret level laboratory space with at least 600 ft2 of space and a Contractor owned Secret level network with a minimum of 10 work-stations for the purpose of battlespace software development and testing.

3.1.2.2 Meeting and conference room support: The Contractor shall have the capability to conduct meetings at the unclassified level. The meetings shall be capable of accommodating a minimum of 10 persons and have a teleconference and videoconference capability (non-Government Furnished Equipment). The contractor shall be capable of projecting presentations during these meeting via projectors and/or TV displays; telephone(s); and computer(s) with compatible software, as required in Paragraph 3.1.1. This support shall be provided at the Contractor’s location.

3.1.2.3 Government Furnished Property (GFP): A listing of Government Furnished Property to be made available to the Contractor at contractor facilities can be found in Attachment J5. The Government shall provide Unclassified Research Development Test & Evaluation (RDT&E) computers and computer network connectivity for off-site contractors providing direct full time technical support that requires RDT&E network access.

3.1.3 Contract Status Reporting.

The Contractor shall provide the following documentation.

3.1.3.1 Monthly Program Financial Summary. The Contractor shall provide a monthly program financial summary report in accordance with Contract Data Requirements List (CDRL) A001. The monthly financial summary provides an overview of the status of the entire contracted effort.

3.1.3.2 Monthly Project Financial Summary. The Contractor shall provide a monthly project financial summary report in accordance with CDRL A002. Monthly project financial summaries provide detailed financial information for individual projects supported by the contracted effort.

3.1.3.3 Monthly Progress Report. The Contractor shall provide a monthly progress report in accordance with CDRL A003. This report shall list the monthly accomplishments and upcoming project objectives for each project. Trips and significant events shall also be addressed.

3.1.3.4 Other Reporting. The Government may require the Contractor to provide additional reporting, documentation, and schedules in accordance with deliverable requirements (CDRLs) incorporated at the task order level. Reporting should be in sufficient detail and quality to meet the requirement established in the individual task orders and shall be in compliance with the standards and guidelines in Section 3.0. Other reporting requirements may include, but are not be limited to:

· Technical reports, documentation, requirements, data, evaluations and analysis.

· Software source code and executables.

· Manufacturing drawings, data, lists, procedures, and schematics.

· Maintenance requirements, guidelines, schedules, procedures, instructions, and corrective actions.

· Agendas, minutes and presentation materials for meetings, presentations, and conferences.

3.1.4 Work Schedule to include Compressed Work Schedule (CWS), overtime, holidays, and installation closure.

3.1.4.1 Work schedule: The Contractor shall provide the required services and staffing coverage during normal working hours. Core hours are 0900-1500, Monday through Friday (except on the legal holidays specified in paragraph 3.1.4.3). Some supported Government offices have flexibility to start as early as 0500/0530 and end as late as 1900, Monday through Friday. To be specified at the task order level.

3.1.4.2 Compressed Work Schedule (CWS): If the Contractor chooses to allow its employees to work a CWS schedule in support of this contract, any additional costs associated with the implementation of the CWS schedule vice the standard schedule are unallowable costs under this contract and will not be reimbursed by the Government. Additionally, the CWS schedule shall not prevent Contractor employees from providing necessary staffing and services coverage as required by the Government to the Alternate Contracting Officer’s Representative (ACOR)/Contracting Officer’s Representative (COR).

3.1.4.3 Holidays: The Government observes the following holidays:

With the exception of the events in section 3.1.4.4, the Contractor is permitted to observe the above Holidays in accordance with its corporate policy.

3.1.4.4 Installation closure: When Federal facilities are closed by the Government, or when Federal employees are officially excused from work due to a holiday or a special event, severe weather, a security threat, or any other Government facility related problem that prevents Federal personnel from working at the Government facility, contractor personnel assigned to work at that facility in support of such Federal employees shall follow their parent company’s policies.

While generally contractor personnel may not perform work on-site at a Government facility without Federal personnel present, in very limited circumstances, work being performed by contractor personnel may be deemed mission essential and performance of such mission essential work may be authorized to continue at the Government facility despite the facility being otherwise closed for normal operations. The circumstances permitting work being performed by contractor personnel to be deemed mission essential are extremely limited and generally only apply to performance of efforts related to public health, safety, or matters related to national security. The cognizant Contracting Officer must concur with any determination that work being performed by contractor personnel is mission essential. Mission essential services, if any, will be identified at the task order level.

3.1.4.5 Overtime: Overtime as defined in this contract refers to hours worked by a contractor employee in excess of the employee’s normal work week. When support requirements outside of normal working hours occur, the Contractor shall ensure qualified personnel are available to support the requirements through the use of overtime. Overtime is authorized under this contract to the extent specified in individual task orders, provided COR approval is obtained in advance of each occurrence. The COR may provide concurrence for overtime on a task, event, program, project, or general function basis. The total cost for overtime over the life of the contract cannot exceed the amount specified in clause 52.222-2 Payment for Overtime Premiums unless first approved in writing by the Chief of the Contracting Office.

3.1.5 Other Direct Costs.

3.1.5.1 Travel: Travel will be allowable only when it is essential to the performance of tasks detailed in Section 3.3. Reimbursement for travel performed shall be in accordance with NAVAIR Clause 5252.232-9509 Travel Approval and Reimbursement Procedures. Invoiced travel costs may include general and administrative expenses, but shall not include profit. Temporary travel to other locations in support of program tasking is required. In accordance with NAVAIR Clause 5252.232-9509 Travel Approval and Reimbursement Procedures, travel within a 50-mile driving distance of the Contractor’s regular worksite is considered the Contractor’s official station and therefore not subject to reimbursement. Temporary travel locations may include Continental United States (CONUS) and Outside Continental United States (OCONUS) locations. Travel authorization requests shall be submitted for COR approval 30 days in advance of required travel, when possible, but no less than 15 business days prior to travel.

3.1.5.2 Material: Purchase of materials shall be in accordance with NAVAIR Clause 5252.242-9515 (Variation)(JUN 2018), Restriction on the Direct Charging of Material. Invoiced material costs may include general and administrative expenses, but shall not include profit. The costs of general purpose business expenses required for the conduct of the Contractor’s normal business operations are not an allowable direct cost in the performance of this contract. General purpose business expenses include, but are not limited to, the cost for items such as telephones and telephone charges, reproduction machines, word processing equipment, personal computers and other office equipment and office supplies.

3.1.6 Subcontractors.

Provisions stated herein shall be clearly and effectively communicated to all subcontractors providing support under this contract. All provisions of this SOW shall flow down to subcontractors providing support under this contract, as appropriate.

3.1.7 Management of Contractor Personnel.

The Government will neither supervise contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances will the Government assign tasks to, or prepare work schedules for, individual contractor employees. The Contractor shall manage its employees and guard against any actions that are of the nature of personal services, or give the perception of personal services.

3.2 Security

3.2.1 Citizenship Requirements.

Only U.S. citizens may perform under this contract, unless waived. If the Contractor cannot find qualified U.S. citizens to perform the work, the Contractor shall submit a citizenship waiver request with justification to the Government Security Office. The waiver request should include:

3.2.2 Investigative Requirements.

All Contractor personnel shall maintain a minimum security clearance eligibility of Secret throughout contract performance. Individual task orders may require additional security clearance requirements, depending on the nature of the task to be performed.

All personnel security clearances shall be obtained within 30 days of contract award. Interim clearances are acceptable. The Contractor is responsible for ensuring that all personnel receive the requisite investigation and are favorably adjudicated in accordance with DoDM 5220.22, National Industrial Security Program Operating Manual. Contractor employees who fail to meet security clearance requirements may not access classified information or perform sensitive duties. In such cases, the Contractor employee may not perform on the contract.

The Contractor shall possess and maintain Facility Security Clearance commensurate with the contract DD Form 254, Contract Security Specification.

In accordance with the contract DD Form 254 Contract Security Specification, the Contractor shall possess and maintain a Top Secret Facility Security Clearance. Individuals requiring Top Secret clearances, as identified in the table at Section 3.4, must be able to perform at the Top Secret level within 30 days of contract award.

3.2.3 Common Access Card (CAC)/Public Key Infrastructure (PKI), System Authorization Access Request (SAAR-N).

3.2.3.1 SAAR-N: All contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR-N) Form OPNAV 5239/14 (Rev Sep 2011) on file, and complete required Annual Information Awareness Training in accordance with NAVAIR Clause 5252.204-9505. New employees must submit their SAAR-N forms within thirty (30) days before their first day of work. Instructions for processing the SAAR-N forms are available at: http://www.public.navy.mil/surfor/ccsg11/documents/CCSG11_OPNAV_5239_14SAAR_N.pdf. SAAR-N forms shall be submitted to the Contracting Officer’s Representative (COR), Government Technical Point of Contact (TPOC), or to the assigned government Trusted Associate Sponsorship System (TASS) Trusted Associate.

3.2.3.2 CAC / Local Badges: Contractor CACs and facility specific identification badges will be issued by the Government to on-site contractor personnel and shall be visible at all times while personnel are at the Government site. The Contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to NASPAXRIV Instruction 5510.15Q or the most current version of this instruction. All CACs and identification badges issued to Contractor employees shall be returned to the Government Security Department issuing the credential following completion of the contract, relocation or termination of an employee, or upon request from the Contracting Officer’s Representative. The Government will provide the Contractor access to Government facilities, as required, for performance of tasks under this contract. Contractor personnel shall comply with all applicable security procedures and regulations for these facilities.

3.2.3.3 DD-254: The Contractor shall comply with security requirements specified in the DD-254 attached to this contract. Information or data that the Contractor accesses shall be handled at the appropriate classification level. Unclassified information shall be handled in accordance with the appropriate designation (Controlled Unclassified Information; For Official Use Only; Covered Defense Information). Distribution is authorized to the Requiring Office's Organization and supported Activity only. Other requests for deliverables under this contract shall be referred to the COR of this contract for approval.

3.2.4 Information Security.

If the work is performed at the Contractor’s facility, the Contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of classified information and controlled unclassified information (CUI) and to control distribution of CUI in accordance with DoD 5220.22-M (NISPOM), and SECNAV M-5510.36. If the work is performed at the Government’s facility, the Contractor shall comply with the Department of the Navy (DON) Automated Data Processing (ADP) Security Program outlined in OPNAVINST 5239.1C, or the most current version of this instruction.

3.2.4.1 Marking: All information generated by the Contractor shall be properly marked. For Official Use Only information generated and/or provided under this contract shall be marked in accordance with DoDM 5200.01. Technical information shall also be marked with appropriate Distribution Statements and Export Control warnings in accordance with DoDD 5230.24 and program Security Classification Guidance.

3.2.4.2 Public Release: No information pertaining to this contract shall be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by the appropriate U.S. government authority. Proposed public releases shall be submitted for approval prior to release through the IBST Department, NAWCAD 5.4.

3.2.4.3 Loss, Compromise and/or Electronic Spillage of Classified or Controlled Unclassified Information: All instances of loss, compromise and electronic spillage of classified or controlled unclassified information shall be reported to the COR, TPOC, and Government Security Office within 24 hours of the incident occurring.

3.2.5 Operational Security (OPSEC).

The Contractor shall comply with activity OPSEC program instructions, guidance and contribute to organization-level OPSEC efforts. The Contractor shall include OPSEC as part of its ongoing security awareness program and take all required activity OPSEC training. The Contractor shall protect identified critical information, sensitive unclassified information and activities, which, if divulged, could further compromise classified or sensitive information or operations, or degrade the planning and execution of operations performed by the Requiring Office and contractor in support of the mission

While performing aboard NAVAIR or NAVAIR sites, the Contractor shall: (1) comply with facility OPSEC program instructions and contribute to organization-level OPSEC efforts; (2) include OPSEC as part of its ongoing security awareness program and take all required Agency training; (3) be responsive to the Supporting OPSEC Manager on a non-interference basis; and (4) protect sensitive unclassified information and activities, which could compromise classified information or operations, or degrade the planning and execution of operations performed by the Requiring Office and contractor in support of the mission.

The Contractor shall develop, implement, and maintain an OPSEC plan (CDRL A004) to protect classified and sensitive information to be used at a contractor's and subcontractor's facilities during the performance of this contract. The Contractor is responsible for subcontractor implementation of the OPSEC program requirements for this contract.

3.2.6 Anti-Terrorism Force Protection and Emergency Management.

Anti-Terrorism Force Protection and Emergency Management: The work performed on this contract is not anticipated to be Emergency Essential in accordance with OPNAVINST 3440.17A and Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans. Contractor personnel shall comply with all Government Emergency Management, Antiterrorism and/or Continuity of Operations Plans and directives. Unless otherwise approved in accordance with 3.1.4.4, Contractor personnel shall not report for work at Government facilities upon declaration of Force Protection Condition CHARLIE or in any event or emergency where Government officials direct curtailment of operations to “Mission Essential Only”. All Contractor personnel assigned to a government facility shall complete annual Antiterrorism (Level One) and Active Shooter training.

1.

1.

1.

1.

3.3 Detailed Support Requirement

1.

0.

0.

0.

3.3.1 General Requirements (RDT&E, WCF, O&M, Procurement, FMS)

0.2.1.1 Software language and tool requirements for each project shall be in accordance with the current Simulation Division standards, or as otherwise specified in individual task orders.

The Contractor shall:

0.2.1.2 Support technical tours of Simulation Division facilities and demonstration of Battlespace and distributed simulation products and capabilities.

0.2.1.3 Provide visitor escort support in classified Simulation Division spaces as required when supporting contract requirements. Escorting of visitors shall be in accordance with the IBST security SOPs listed in paragraph 2.3, current NAVAIR and NAWCAD instructions, and NAS Patuxent River directives.

0.2.1.4 Documentation. Develop and maintain engineering documentation to support the development, operation, accreditation, maintenance, and modification of Simulation Division products and events. Documentation includes, but is not limited to, diagrams, schematics, concepts of operations, source code, technical manuals, test procedures, test results and reports, and user’s manuals.

0.2.1.5 Test and Training Support. Provide technical support for scheduled test, training, and demonstration events, to include system operation, trouble-shooting, event setup, and debriefing.

0.2.1.6 Technical Support. Provide on-site and off-site technical support to other organizations, including Simulation Division customers and collaborators.

0.2.1.7 Technical Research Studies. Perform technical research and design studies to define performance, operational or user requirements, evaluate new technologies, or improve the capability, efficiency, or reliability of Simulation Division products and activities.

0.2.1.8 Technical Exchanges. Attend user group meetings, symposia as, approved by the COR, technical meetings and exchanges, working groups, and System Engineering Technical Reviews (SETR) events to meet program objectives. Develop presentation materials to support technical reviews and meetings.

0.2.1.9 Training. Provide technical support for training on simulation technologies and methodologies, the Simulation Division and IBST capabilities and practices, and related subjects. Tasks include the development of training manuals, preparation of classroom and facilities, curriculum development, and class instruction.

0.2.1.10 Event Support. Provide support to prepare for and conduct simulation-based testing and training events to include distributed battlespace simulations and Live, Virtual, Constructive (LVC) exercises.

0.2.2 Program and Project Management Support (RDT&E, WCF, O&M, Procurement, FMS)

Note: For the purpose of this work statement, “Program” is defined as the entire contract effort, managed, administered and operated by the Contractor. A “Project” is defined as an effort performed within the Program to meet specific technical and operational requirements for the Simulation Division and its customers executed by Integrated Product Teams (IPTs) consisting of contractors, government and military employees.

The Contractor shall:

0.2.2.1 Program Management. Manage the contracted effort by providing best-value program performance within cost objectives. Ensure effective management of contracted program and project resources as well as the financial and administrative aspects of the program with respect to the contract. General and Operations Manager shall serve as the primary point of contact with the COR for the contract and oversee the production of deliverables. General and Operations Manager shall review and recommend the development and/or modification of program management plans, strategies, schedules and milestones.

0.2.2.2 Program Support. Administer and provide financial tracking for the contracted effort. Produce monthly financial reports in accordance with contract reporting requirements (See Section 3.1.3). Analyze financial program performance to project funding issues. Coordinate with Business Financial Manager (BFM) on the allocation and expenditure of funds committed to contract. Support program and project managers with management and tracking of financial and contract administrative data.

0.2.2.3 Project Management Support. Develop, analyze, modify, and monitor the implementation of processes, standards, plans, and requirements for Simulation Division operations and projects. Tasks include, but are not limited to:

· Reviewing, revising, analyzing and recommending changes to project management plans and strategies.

· Ensuring project controls and applicable standards are adhered to.

· Defining, developing, tracking, managing, and reporting project requirements.

· Managing cost and schedule to ensure the timely delivery of products to the customer.

· Meeting with customers.

· Issue resolution efforts.

· Develop and update documentation/presentation materials such as view graphs, brochures, display booths and other briefing materials to support program/project objectives and business development.

· Providing support for product-user community meetings and conferences.

0.2.2.4 Requirements Tracking. Collect, track, establish traceability, communicate and report project requirements. Collect and organize requirements using customer specifications and assist Simulation Division IPT’s with development and tracking of derived requirements.

0.2.2.5 Scheduling/EVM. Develop and maintain project schedules and Earned Value Management (EVM) data for projects based on project and customer requirements. Develop and maintain Integrated Master Schedules (IMS) with work breakdown structures and resource-loaded schedules using Microsoft Project with inputs from Project Managers and team members. Identify and communicate schedule conflicts and irregularities and work with project teams to mitigate schedule issues. Track project costs, cost estimates, and cost projections. Work with project managers to communicate schedule and cost information to customers.

0.2.3 Project Support (RDT&E, WCF, O&M, Procurement, FMS)

The Contractor shall:

0.2.3.1 Configuration Management. Maintain a Configuration Management (CM) program for documents, software, commercial off the shelf (COTS), and government off the shelf (GOTS) documentation in support of Simulation Division projects and operations in accordance with established procedures. Maintain a Government owned multimedia technical data library that consists of technical documents, technical data and reports, software, and product user licenses. Tasks include:

· Tracking and reporting on the status of project documentation, change documentation (discrepancy reports, change requests, etc.), and deliverable items.

· Supporting design reviews and Configuration Control Board (CCB) meetings. Tracking action items from CCB meetings.

· Assuring approved configuration management standards and procedures are adhered to.

· Working with project IPTs to determine the schedule, content, and delivery of project base-lines and releases. Supporting the creation, verification, documentation and distribution, and tracking of data package releases.

· Verifying proper use of the approval process for the release of hardware engineering drawings and data lists to manufacturing.

· Maintaining government-owned physical and computer data libraries. Implementing procedures to ensure the restoration of software products and digital data in the event of a system failure or disaster.

· Assisting with the definition and improvement of CM-related processes and procedures. Documenting, maintaining and implementing project-level CM plans.

0.2.3.2 Technical Writing Support. Provide technical writing support to develop product documentation (user manuals, technical manuals, and logistics reports), project documentation (project standards, status reports, meeting minutes, and action items), test definition and results reports, and organization policy and procedure documentation. Support includes researching, writing, editing, and proofreading deliverable logistical and project support documentation in accordance with applicable customer specifications and Simulation Division standards. Communicate with project team members to develop, collect, and process information required for writing assignments.

0.2.3.3 Testing Support. Develop materials for verification, validation, and acceptance of developed software and systems. Coordinate and facilitate government-run system evaluations. Monitor and report on compliance with product requirements for performance, compliance with standard testing processes and procedures, and compliance with system level hardware and software plans. Tasks include, but are not limited to:

· Analyzing, evaluating, and extrapolating system and project requirements.

· Developing, maintaining, and implementing test plans, procedures, and mission scenarios.

· Working with the project IPT and the customer(s) to refine and obtain approval of test plans.

· Supporting informal and formal System Engineering Technical Review (SETR) events and meetings.

· Generating test result reports and creating discrepancy reports to document and communicate test results and the level of system maturity.

0.2.4 Software Development and Engineering Support (RDT&E, WCF, O&M, Procurement, FMS)

The Contractor shall:

0.2.4.1 Aerospace Engineering. Assist in the design, development, testing, modification and maintenance of simulation models of air vehicles, air vehicle interactions, and air vehicle sub-systems. Tasks include, but are not limited to:

· Researching and analyzing aircraft flight test data and system documentation to collect the information needed to develop airframe models.

· Developing air vehicle simulation models using a prescribed program language and/or Matrix Laboratory (MATLAB). Modeling includes, but is not limited to, flight performance characteristics, engine modeling, controls, landing gear, electrical and hydraulic sub-systems, and engine control units.

· Interfacing airframe models with other simulation assets, such as shared memory systems, avionics, simulation systems, and distributed simulations

· Developing tools to run, analyze and test air vehicle simulation models.

0.2.4.2 Avionics Modeling. Assist in the design, development, integration, and testing of simulation models of sensor systems, communications systems, identification systems, and weapons systems. Tasks include, but are not limited to:

· Model development, modification, and integration into a battlespace environment.

· Integrating and interfacing with third party models, systems, and servers.

· Support interfacing, stimulating, and testing aircraft avionics.

· Model testing and evaluation.

· Development of operator physical and graphical user interfaces.

0.2.4.3 Battlespace Modeling. Assist with the design, development, modification, testing and operation of Battlespace simulation modeling, including Battlespace entity models, environments, and software. Tasks include, but are not limited to:

· Developing, interfacing and operating warfare simulation environments including Next Generation Threat System (NGTS), the Joint Integrated Mission Model (JIMM), Interactive Warfare Simulation (IWARS), and Joint Semi-Automated Forces (JSAF).

· Developing Battlespace simulation entity and environment models by collecting and analyzing data from sources such as the Electronic Warfare Integrated Reprogramming Database (EWIRDB).

· Developing Battlespace simulation operation and visualization graphical user interfaces.

· Designing, using, and maintaining simulation database development and manipulation tools.

· Supporting and operating multi-site mission level simulation exercises.

· Developing and maintaining simulation generation processes that permit user scenario development.

· Testing, analysis, evaluation, and reporting on Battlespace simulation software, models and test events.

0.2.4.4 Simulation Systems Software Development. Assist with the design, development, modification, integration, interfacing, testing, operation, and maintenance of simulation systems. Tasks include, but are not limited to:

· Interfacing to simulation hardware systems including image generators, visual display systems, aural cueing systems, shared memory systems, operator stations, and networking equipment.

· Developing software to interface, operate, monitor, and test simulation and stimulation systems, such as simulation operator software, control executives, and runtime tools.

· Developing software and interfaces for recording, playback, presentation and post-execution analysis.

· Developing interfaces and tools to support distributed simulations using Distributed Interactive Simulation (DIS), High Level Architecture (HLA), Test-Training Enabling Architecture (TENA) and Battlespace modeling.

· Database development and manipulation tools.

· Software to establish connectivity and interoperability between Simulation Division systems and facilities and other live, virtual and constructive systems, labs and facilities.

0.2.5 Specialized Technical Support (RDT&E, WCF, O&M, Procurement, FMS)

The Contractor shall:

0.2.5.1 Technical Expertise. Provide subject matter expertise (SME) for a broad range of military matters including air-vehicles, sensors systems (RADAR, SONAR, etc.), weapons systems, communication systems, air-vehicle simulation and training, Live, Virtual and Constructive (LVC) simulations, aircraft and aircraft system testing, and M&S Verification Validation and Accreditation. Tasks include, but are not limited to:

· Assist with the development of technical specifications based on an in-depth knowledge of the fleets operations and requirements.

· Communicating requirements for simulation models and LVC environment scenarios to software developers and/or participating in model development.

· Evaluating and testing simulation models and LVC scenarios.

· Evaluating and analyzing flight test data.

· Interfacing with customers and system operators.

· Supporting, planning, and/or operating simulation and test events in support of test and training objectives.

· Operating model entities in distributed simulation events.

0.2.5.2 Warfighting Scenario Development. Research, design, develop, implement, maintain, test, analyze, and execute engineering level, engagement-level, mission-level, and campaign-level warfighting scenarios in an LVC simulation of operational and test environments. Tasks include, but are not limited to:

· Conducting research of command and control environments, doctrines, tactics, techniques, and procedures, as well as other operational factors and tactical applications to ensure realism of selected LVC simulations.

· Establishing and updating orders of battle, signal densities, operational systems, environmental conditions, adversary action, and other factors required to accurately simulate selected warfighting LVC environments.

· Operating post-test analytical tools relating to warfighting scenario execution.

· Identifying, reporting, and taking and/or directing corrective actions to resolve deficiencies with warfighting scenarios.

· Supporting research and technical design studies in support of the warfighting simulation technical library and scenario development. Studies include the use of operational, doctrinal, technical, parametric, and other databases generated and maintained by a cognizant government agency.

0.3 Labor Category Definitions

The Contractor shall be responsible for employing personnel with the qualifications and skills required to successfully accomplish the tasking outlined in the SOW. Additionally the contractor shall be responsible for ensuring that the personnel employed for each labor category in the table below, possess and maintain a Top Secret security clearance throughout the performance of this contract. All other personnel not listed below must possess and maintain a Secret security clearance throughout the performance of this contract.

*Denotes Key Personnel

3.4.1 Professional Labor Categories

The following defines the Bureau of Labor and Statistics Standard Occupational Classification (BLS SOC) Code, minimum labor category education, experience, and functional description for each professional labor category.

3.4.1.1 Professional Labor Categories, Levels and BLS SOC Codes

3.4.1.2 Experience and Education Level Definitions

The professional labor category experience and education requirements corresponding to the three levels specified above (i.e., Junior, Journeyman and Senior) are as follows:

JUNIOR: A Junior level person within a labor category generally has less than 3 “years’ experience” performing work related to the labor category functional description and a BA/BS degree (or a qualifying substitution as identified in this section). A Junior level person is responsible for assisting more senior positions and/or performing functional duties under the oversight of more senior positions.

JOURNEYMAN: A Journeyman level person within a labor category has 3 or more years of experience performing work related to the labor category functional description and a BA/BS degree or a qualifying substitution as identified in this section. A Journeyman level person typically performs all functional duties independently.

SENIOR: A Senior level person within a labor category has at least 10 years of experience performing…