SOW_-_Engineering_Services.docx

SECTION C DESCRIPTIONS AND SPECIFICATIONS

1.0 INTRODUCTION

1.1 Background

The Naval Air Systems Command (NAVAIR), headquartered at Patuxent River NAS, provides products and full life-cycle support for naval aviation weapons systems, including research, design, development, test and evaluation, training, and in-service engineering. The Naval Air Warfare Center Aircraft Division (NAWCAD) is a product center within NAVAIR that is the steward of the ranges, test facilities, laboratories, and aircraft necessary to support the Fleets requirements.

The Integrated Battlespace Simulation and Test (IBST) Department, NAWCAD 5.4, is the Naval Air Systems Command’s (NAVAIR) center of excellence for modeling and simulation of the Battlespace environment. The Department is NAVAIR’s lead for the development and creation of synthetic and virtual Battlespace environments in support of research, development, testing, training, and system evaluation. IBST operates, maintains, and manages a number of test facilities to support test and evaluation events using simulated environments, physical environments to stimulate aircraft systems, and combinations of physical and simulated environments.

This statement of work describes technical support services required by the Simulation Division (SD), NAWCAD 5.4.3, which is one of three divisions within IBST and is responsible for simulation expertise and products for naval aviation systems and the Battlespace environment within which they operate. Simulation is used throughout the acquisition lifecycle to reduce risk and improve the quality of naval aviation systems.

Simulation Division aircraft and aircraft system simulation activities includes the operation of man-in-the loop simulation facilities and the development of simulation software, simulation systems, hardware-in-the-loop test benches and prototype training systems. Typical applications for aircraft and system simulations include:

· Flight test planning, coordination, and rehearsal.

· Aircrew proficiency training

· Hardware-in-the-loop systems and integration testing.

· Human factors evaluations.

· Flying qualities and performance evaluations.

· Mission effectiveness and concept of operations.

· Accident and incident investigations.

Simulation Division Battlespace modeling and simulation provides credible, repeatable models of highly complex, interactive and reactive environments in support of the warfighter. Battlespace modeling and simulation products are used across the DoD and NAVAIR for RDT&E, analysis and training. The Division also provides national leadership in distributed modeling and simulation, scenario development, and verification and validation.

Simulation Division labs also process, reduce, analyze and evaluate aircraft flight test data.

Facilities and laboratory spaces operated by the SD include the Manned Flight Simulator (MFS) facility, E-2C System Test and Evaluation Lab (ESTEL), the P-8 System Integration Lab (PAX-SIL), Warfare Simulation Lab, UAS Integration Lab, H-60 Data Reduction Lab (DRL), and executive helicopter SIL and ADAPT labs. The SD also provides support for IBST’s classified network and unclassified RDT&E network assets.

The SD works closely with other teams and laboratories within IBST to support aircraft and system simulation and stimulation testing, including:

· Air Combat Environments Test and Evaluation Facility (ACETEF)

· Integrated Battlespace Arena (IBAR)

· Electromagnetic Environmental Effects (E3)

· Surface/Aviation Interoperability Laboratory (SAIL)

· Radar Reflectivity Lab (RRL)

1.2 Organizational Layout

The Simulation Division (5.4.3) is composed of 10 branches:

1.2.1 Enterprise Operations Branch (5.4.3.1). Provides the resources for the operation, maintenance, and development of Simulation Divisions Laboratories and Facilities. Provides network administration, architecture, maintenance, and information assurance support for IBST classified networks and unclassified RDT&E network assets. Develops and manages simulation environment visual and sensor databases and heads-down display interfaces.

1.2.2 Mission Systems Branch (5.4.3.2). Provides resources to simulate, integrate, and test avionics and mission systems. Applies expertise in sensors (radar, EO/IR, acoustic, etc.), electronic support measures (ESM), Communication / Navigation / Identification systems and technical data links to fulfill the requirements of simulation development projects and RDT&E test activities.

1.2.3 Flight Simulation Technologies Branch (5.4.3.3). Provides resources for the design, development, fabrication, integration, testing, and installation of air vehicle simulation systems to support RDT&E and Training requirements. Resources include project management, hardware engineering, fabrication and wiring, project support services, computer science, and software engineering support.

1.2.4 Simulation Prototyping Branch (5.4.3.4). Provides resources for the design, development, integration, testing, and installation of air vehicle simulation systems to support RDT&E and Training requirements. Resources include project management, hardware engineering, project support services, computer science, and software engineering support.

1.2.5 Modeling and Interface Branch (5.4.3.5). Provides the resources required for the development of simulation models, integration architectures, and distributed simulation execution. Competencies include creating representative behavioral models of both friendly and threat warfare systems, the creation of simulated or stimulated environments into which behavior models are inserted, and providing expertise in large-scale simulations and distributed simulation events.

1.2.6 Battlespace Applications Branch (5.4.3.6). Provides the resources required for management and execution of test, training and other support involving integrated Battlespace modeling and digital simulation models, rapid display prototyping, training support operations and software, scenario development, scenario design and creation of validated and repeatable scenarios, ranging from theater to unit level scenarios.

1.2.7 Battlespace Modeling V&V Branch (5.4.3.7). Provides the Division and DOD Modeling and Simulation (M&S) community a cost effective means of defining and meeting simulation credibility requirements. This branch oversees related processes as they apply to verification, validation and/or accreditation to establish a documented pedigree of simulation and models.

1.2.8 Mission Systems T&E Support and Analysis Branch (5.4.3.8). Provides the engineering personnel, processes and facilities to provide specialized mission systems laboratories/test facilities and analysis tools to support the life cycle test and evaluation of integrated mission computers, controls and displays, and associated software systems.

1.2.9 Cyber Simulation Branch (5.4.3.9). Provides the engineering and technical personnel, processes and facilities for life cycle Test and Evaluation (T&E) and demonstration of integrated and interoperable system-of-systems and systems as installed on all manned and unmanned platforms and weapons systems.

1.2.10 Battlespace Training Applications Branch (5.4.3.10/543J00) (ORL). Provides resources required for management and execution of tests, training, and other support involving test and integration of digital simulation models, rapid display prototyping, training support operations and software, scenario development and design, and integrated Battlespace modeling. Interacts with test teams, external customers, and other organizational entities for the design and creation of validated and repeatable test environments and scenarios. This branch is located in Orlando Florida.

1.3 Scope

The scope for this contract is for uninterrupted engineering and technical services in support of Simulation Division teams, facilities, and supported projects. Support includes management, design, development, integration, upgrade, analysis, and documentation for the Simulation Division and its supported facilities and projects. Specific functions to be accomplished are outlined in Section 3.0.

The Division operates within Integrated Product Teams and Enterprise Teams for all aspects of performance, and the contractor shall be required to work in a highly integrated team environment with civil servants, military personnel, and other contractors.

2.0 APPLICABLE DOCUMENTS

The contractor shall conform to the most current versions of all Simulation Division Quality Management System (QMS) processes, standards, and procedures in the performance of this contract. SD standards and processes are expected to evolve and be expanded over the period of performance of this contract, but these changes will not affect the scope of the work of this contract.

The contractor shall conform to applicable IBST, DoN and DoD 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 Simulation Division (5.4.3) Standards and Procedures

Document ID Number

Applicability

Project Management

Project Support

General Engineering

Hardware Engineering

Software Engineering

Information Technology

2.2 Integrated Battlespace Simulation and Tests (5.4) Standards and Procedures Document ID Number

Applicability

2.3 DOD, DON, and NAVAIR Standards

Applicability

Joint Travel Regulations

3.0 PERFORMANCE REQUIREMENTS

3.1 General

3.1.1 Applicable documents in Section 2.0 may be used as guidance to comply with minimum acceptable performance criteria outlined in the QASP.

3.1.2 The contractor’s objective shall be to support the development and improvement of new and existing assets, provide testing and training support, and increase the utilization of test assets.

3.1.3 For the purpose of this Performance Based Statement of Work (PBSOW), “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.

3.1.4 Software language and tool requirements for each project shall be in accordance with the current SD standards, or otherwise shall be specified in a Task Order or directed by the Integrated Project Team depending on the scope of the effort.

3.1.5 To meet emerging requirements, the contractor shall have the ability to rapidly enter into partnerships/or contractual agreements with other organizations and business entities to enable the support or acquisition of unique talents or items.

3.1.6 The contractor and subcontractors shall provide a management structure that ensures they maintain supervisory, administrative, technical, and developmental oversight of their employees while working in teams with civil servants and military personnel.

3.1.7 Use of any software, hardware or documentation developed by the contractor or a sub-contractor financed in part or in whole at private expense and offered without full government purpose rights shall be subject to COR approval prior to use in support of a Simulation Division project or incorporation into Simulation Division infrastructure.

3.2 Program and Project Management Support

The Contractor Shall:

3.2.1 Program Management. Provide program management support for the contracted support effort. Provide best-value program performance within cost objectives. Manage contracted program/project resources as well as the financial and administrative aspects of the program with respect to the contract. Serve as the primary point of contact with the Contract Officer Representative (COR) and Technical Point of Contact (TPOC) for the contract and oversee the production of deliverables. Review and recommend the development and/or modification of program management plans, strategies, schedules and milestones.

3.2.2 Program Support. Provide program administration and contract financial support. Produce monthly financial reports in accordance with contract reporting requirements (See Section 4.1). 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.

3.2.3 Project Management Support. Provide project management and project coordination support for Simulation Division projects. Project management support includes, but is not limited to:

· Reviewing, revising, analyzing and recommending changes to Simulation Division policy and standards, project management plans and strategies. Prepare draft revisions of such documents.

· Applying experience of ISO9001:2000 Quality Management System requirements to Simulation Division standards and procedures.

· 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.

· Developing and/or reviewing, analyzing, and modifying program management and technical reports, presentations, brochures, white papers and deliverable documentation to support project objectives.

· Meeting with customers.

· Issue resolution efforts.

3.2.4 Business Development. Produce and update documentation/presentation materials such as view graphs, brochures, display booths and other briefing materials to support program/project objectives and business development as required. Support the development of project proposals and promote the capabilities of the Simulation Division and IBST as required.

3.3 Facility and Operations Support

The contractor shall:

3.3.1 Technical Tours. Provide technical tours of Simulation Division facilities and provide capability presentations to potential customers and tour groups. All tours and capability briefs must have prior approval of the SD Management or the COR.

3.3.2 Visitor Escorting. Provide visitor escort support to individuals who have an official requirement to be in Simulation Division supported restricted spaces but do not have the appropriate security clearance. Escorting of visitors shall be in accordance with the IBST SOP and current NAVAIR, NAWC-AD and NAS Patuxent River directives.

3.4 Project Support

The Contractor shall:

3.4.1 Configuration Management. Provide support for the Configuration Management (CM) of documents, software, hardware, and COTS/GOTS documentation in support of SD projects, operations, and facilities 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. Configuration Management support activities include, but is not limited to:

· 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 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. Document, maintain and implement project-level CM plans.

3.4.2 Logistics Support. Provide logistics support for the development of deliverable data packages, reports, lists, and manuals. Logistics support activities include, but are not limited to:

· Gathering data for the development of required project documents.

· Coordinating with product teams, manufacturers, vendors and sub-contractors to develop and refine logistics data.

· Collecting, calculating, analyzing, and communicating component and system-level reliability and maintainability data.

· Developing recommended spare parts lists.

· Developing and maintaining system equipment inventory records.

· Obtaining, registering and verifying that Item Unique Identification (IUID) bar codes are applied.

· Researching alternate parts and part cost data.

· Coordinating and facilitating Physical Configuration Audits (PCA).

· Developing and presenting project logistics information at formal design reviews.

· Managing COTS/GOTS documentation.

· Developing logistical CDRL deliverable documentation.

3.4.3 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.

3.4.4 Scheduling / EVM. Provide scheduling and Earned Value Management support to 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.

3.4.5 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.

3.4.6 Testing Support. Provide product testing support for verification, validation, and acceptance of developed software and systems. Ensure that product requirements for performance, reliability and maintainability are met, that standard testing processes and procedures are adhered to, and that the system level hardware and software plans have been adhered to. Product testing support activities include, but are not limited to:

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

· Identifying critical system components and establishing test criteria for developed systems, delivered systems, and COTS components. Determining the scope of testing required.

· Developing, maintaining and obtaining approval for documented test plans, procedures, and mission scenarios.

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

· Supporting informal and formal SETR events and meetings.

· Scheduling, supporting, directing, and performing test events, including unit testing, integration testing, systems testing, customer acceptance testing, and regression testing.

· Performing software testing using manual and automated software tools, such as Automated Test and Re-Test (ATRT) tool.

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

3.4.7 Project Technical Support. Provide technical support for the setup, operation, trouble-shooting, and maintenance of simulation systems under development and of deployed systems requiring simulation division follow-on support. Technical support activities include, but are not limited to:

· Assisting system operators and customers with technical questions, troubleshooting technical problems, and coordinating engineering support as required.

· Performing system periodic performance testing and calibrations on simulation systems, including control loading systems, motion systems, and visual display systems.

· Loading new visual and sensor databases.

· Pushing new software loads and cold-starting computer systems.

· Short-term system operation support.

3.5 General Engineering Support Requirements

The contractor shall:

3.5.1 Systems Engineering. Provide system-engineering technical support in the research and development of technical project and program plans. Engineer assigned projects utilizing approved processes that have been developed utilizing a systems engineering approach to project design and development.

3.5.2 Documentation. Provide engineering documentation to support the development, operation, accreditation, maintenance, and modification of Simulation Division projects. Documentation includes, but is not limited to, diagrams, schematics, concepts of operations, source code, three-dimensional mechanical CAD models, drawings, parts lists, technical manuals, test procedures, test results and reports, operator and user manuals, and maintenance manuals.

3.5.3 RDT&E Test and Training Support. Provide engineering support for scheduled RDT&E test and training events, including system operation, trouble-shooting, event setup, and debriefing.

3.5.4 Technical Support. Provide on-site and off-site technical support to other teams, organizations, and facilities both internal and external to the Simulation Division in support of project objectives.

3.5.5 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, projects, infrastructure, operations and facilities.

3.5.6 Technical Exchanges. Attend user group meetings, symposia, technical meetings and exchanges, working groups, and System Engineering Technical Reviews (SETR) such as required SRR, PDR, and CDR to meet program objectives and represent the Simulation Division. Develop presentation materials to support technical reviews and meetings.

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

3.6 Hardware Engineering Support

The contractor shall:

3.6.1 Electrical Engineering. Provide electrical engineering planning, analysis, design, drafting and technical-documentation support for the development, maintenance, repair, and upgrade of Simulation Division supported systems, projects, and facilities. Applications include training systems, RDT&E test and evaluation assets and laboratories, hardware-in-the-loop racks and test-benches. Electrical engineering support activities include, but are not limited to:

· Analysis of aircraft systems.

· Power distribution design.

· System inputs/outputs design.

· Integration of aircraft avionics into hardware-in-the-loop systems.

· Real-time audio and video systems.

· Real-time digital data networks design and interfacing.

· Interconnections between systems, laboratories, and facilities worldwide.

3.6.2 Mechanical Engineering. Provide mechanical engineering planning, analysis, design, and technical documentation support for the development, maintenance, repair, and upgrade of Simulation Division supported systems, projects, and facilities. Applications include training systems, RDT&E test and evaluation systems and laboratories, and hardware-in-the-loop racks and test-benches. Mechanical engineering activities include, but are not limited to:

· Aircraft and aircraft system replication.

· Support structure design.

· Analysis of aircraft structures and systems.

· Control loading and visual display system integration and design.

· Electronic rack design.

· Instructor / operator station design.

· Mobile simulator enclosures integration.

3.6.3 Drafting. Provide drafting support for mechanical and electrical design activities. Drafting is in accordance with AMSE Y14.1 and applicable Simulation Division standards. Develop 3D mechanical models and detailed designs.

3.7 Software Development and Engineering Support

The contractor shall:

3.7.1 Aerospace Engineering. Provide aerospace engineering support for the design, development, testing, modification and maintenance of simulation models of air vehicles, air vehicle interactions, and air vehicle sub-systems. Aerospace engineering support includes, but is 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 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.

3.7.2 Avionics Modeling. Provide support for the design, development, testing, modification and maintenance of simulation models of air vehicle avionics, mission systems, and weapons systems. Provide support to interface, integrate and stimulate and test aircraft avionics. Avionics modeling support includes, but is not limited to:

· Applying expertise and researching sensors (radar, EO/IR, acoustic), mission computers, electronic support measures (ESM), communication, navigation, identification systems, data links, and weapons systems.

· Designing and programming avionics models using a prescribed programming language.

· Interface models with simulation components and aircraft R&D equipment, including shared memory systems, simulation systems software, distributed simulations interfaces, and data links to aircraft and test equipment.

· Develop prototype simulated displays.

· Develop tools to run, analyze, and test avionics models and related simulation systems.

3.7.3 Battlespace Modeling. Provide computer science and engineering support for the design, development, modification, testing and operation of Battlespace simulation modeling, including Battlespace entity models, environments, and software. Support includes, but is not limited to:

· Developing, interfacing and operating warfare simulation environments including the Joint Integrated Mission Model (JIMM), Next Generation Thread System (NGTS), 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 scenario development.

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

3.7.4 Simulation Systems Software Development. Provide computer science and engineering support for the design, development, modification, integration, interfacing, and testing of real-time simulation and stimulation systems in support of RDT&E test and training activities. Simulation Systems support includes, but is not limited to:

· Interfacing to simulation hardware systems including image generators, visual display systems, aural cueing systems, control loading systems, shared memory systems, motion platform and cueing systems, video switchers, operator stations, and networking equipment.

· Developing software to interface, operate, monitor, and test simulation and stimulation systems, such as simulation operator software, control executives, runtime tools, environment controllers, and data bus traffic monitors.

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

· Developing interfaces to aircraft systems using military and commercial data bus standards.

· 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 SD systems and facilities and other live, virtual and constructive systems, labs and facilities.

3.7.5 Flight Test Data Analysis and Processing. Provide computer science and engineering support for the design, development, modification, testing and operation of software tools to collect, process, reduce, analyze, format and display air vehicle flight and ground test data. Software operation may include may include all steps between collection of raw flight test data and final delivery of data products for test reports.

3.7.6 RDT&E Software Development. Provide computer science support for the design, development, integration, testing and operation of RDT&E government software efforts in support of Simulation Division projects. Support includes, but is not limited to:

· Development of software to interface flight test data into simulation and analysis systems.

· Creating software interfaces to RDT&E systems and military hardware.

· Providing support of NAVAIR/DoN software standardization, process and open architecture initiatives.

· Development of software to support NAVAIR RDT&E infrastructure, connectivity, and processes.

· Analysis, evaluation, and testing of software in support of RDT&E programs.

3.8 Specialized Technical Support

The contractor shall:

3.8.1 Subject Matter 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. SME activities include, but are not limited to:

· Development of requirements 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, directing, and/or operating simulation and test events in support of test and training objectives.

· Operating model entities in distributed simulation events.

· Represent the Simulation Division and Simulation Division supported customers at Working Group meetings.

· Providing subject matter expertise to Simulation Division Customers.

3.8.2 Warfighting Scenario Development. Research, design, develop, implement, maintain, test, evaluate, and execute engineering level, engagement-level, mission-level, and campaign-level warfighting scenarios in an LVC simulation of operational and test environments. Scenario development activities include:

· 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 the cognizant government agency.

3.8.3 Verification, Validation and Accreditation (VV&A). Provide support and technical expertise to apply VV&A policies and guidance in the demonstration and documentation of the credibility of models, simulations, laboratories and test facilities. VV&A support includes:

· Reviewing, developing, and updating accreditation materials, including: intended use statements, requirements, acceptance criteria, accreditation methodology, draft Accreditation Plans, Accreditation Reports, Accreditation Support Packages (ASP), and Accreditation Letters.

· Collecting and reviewing modeling and simulation data.

· Conducting and documenting assumptions, limitations, capabilities and risk assessments.

· Reviewing V&V related documentation, requirements and acceptance criteria, and assessing any gaps in the information available to support an accreditation decision.

· Recommending and documenting final acceptance criteria.

· Conducting M&S verification efforts in accordance with accreditation and/or V&V plans. This may include use of CASE tools or other software testing tools or procedures.

· Conducting M&S validation efforts in accordance with accreditation and/or V&V plans. This may include planning and participation in testing of the system being simulated, benchmarking against other M&S, and subject matter expert review of M&S results.

· Documenting verification and validation results in V&V reports and/or the ASP format.

· Facilitating and documenting the results of subject matter expert reviews.

· Providing audit, validation, and verification review of simulation resources, products and processes in accordance with Simulation Division VV&A processes.

3.8.4 Visual and Sensor Database Development. Design, develop, publish, modify and maintain visual out-the-window image generator, sensor image generator, moving models, and warfare simulation (JSAF, OneSAF) databases. Support includes, but is not limited to:

· Developing three dimensional geo-specific dimensionally accurate building models with photo-realistic textures and positioning accurately within a large environment database.

· Developing three-dimensional dimensionally-accurate moving entity models with photo-realistic textures and accurate articulations that can be used in immersive simulated environments.

· Develop and process terrain maps, satellite imagery, shape files, and models to create seamless and accurate simulated representations of the surface of the earth.

· Modifying visual and multispectral satellite imagery and aerial photography to provide appropriate resolution imagery of visual data to project on terrain models.

· Populating large geographical areas of simulation environment databases with representative generic features and trees.

· Developing Geographic Information System (GIS) data to portray point, linear, and aerial features.

· Using configuration management tools and quality control and peer review procedures to verify and validate models, and manage product configuration, workflow, tasking, and documentation.

3.9 Information Technology

The contractor shall:

3.9.1 System Administration. Provide system and network administration and maintenance support for non-Navy Marine Corps (NMCI) classified and unclassified computer systems in support of stand-alone systems, deployable developed systems, and for small laboratory environments. Maintain the functionality, efficiency, integrity, and security of servers and systems. Typical responsibilities include, but are not limited to:

· Researching, installing, updating and trouble-shooting software and IT hardware.

· Performing scans to verify STIG compliance and mitigates issues identified.

· Applying patches to computer networks and systems and re-verifying system functionality.

· Creating and administering system user accounts.

· Investigating and mitigating system performance issues.

· Providing technical support to system users.

· Maintain system documentation to support system certification and accreditation.

3.9.2 Information Assurance. Provide Information Assurance (IA) support for Simulation Division operated computer systems and networks by applying knowledge of DOD, DON and NAVAIR security policies and procedures to protect information. Monitor and manage the security posture of IT resources and their interconnections across classified and unclassified RDT&E networks. Individuals supporting this requirement must be trained and accredited according to DoD 8570 standards. Information Assurance support include, but is not limited to:

· Developing and maintaining documentation to support system certification and accreditation, including the DIACAP and PIT processes.

· Developing risk mitigation and action plans to address the results of security audits, reviews, and scans. Work with NAWC-AD 7.2.6 to communicate results and resolve issues.

· Maintaining knowledge in current security policies and procedures.

· Communicating security policies to simulation division personnel.

· Approving modifications to the configuration of IT resources.

· Support tracking and validation of all Information Assurance Vulnerability Alerts (IAVA) and Information Assurance Vulnerability Bulletins (IAVB).

· Support a portfolio for software applications in the DON Applications and Database Management System (DADMS).

· Reviewing and approval/disproval of the use of new software on Simulation Division supported networks. Applying for additions and modifications to Simulation Division’s approved profile through the DONs FAM process.

3.9.3 Enterprise Software Programing. Develop, maintain, and upgrade enterprise tracking, planning, and management databases, programs and web-based tools to maximize the efficiency of the operation and management of the IBST organization and supported activities. Support includes, but is not limited to, the development of:

· Material purchasing, shipping, inventory and tracking tools.

· Workforce and workload tracking and analysis systems.

· Test asset scheduling systems.

· Workflow tracking tools.

· Requirements definition and tracking tools.

· Financial management tools.

4.0 REPORTING

4.1 Monthly Financial Report

4.1.1 The contractor shall track funding and costs incurred for each project supported by this contract. Large development projects and efforts will be initiated through the issue of a Task Order. Small RDT&E projects will be grouped onto larger task orders and will be initiated by the COR. Each project will be assigned a project number and primary Point of Contact(s) (POC). The POC(s) for each project will be a Civil Servant(s) who is/are responsible for the funding and performance of the effort..

4.1.2 Monthly Financial Summary. The contractor shall provide a monthly financial summary report in accordance with CDRL A001. For each project supported by this contract, the financial summary report shall include:

· Funding (labor/material/travel) for the current contract year, including the SLIN(s) and ACRN(s) for each project supported by this project.

· Total expenditures (labor/material/travel) for the current contract year thru the reporting month.

· Balances (labor/material/travel) for the current contract year at the end of the reporting month.

· Total labor hours charged during the current contract year.

· Total Overtime / Compensatory Time hours charged during the current contract year.

Total funding, expenditures and balance values (labor/material/travel) for this contract shall also be shown.

4.1.3 Monthly Project Financial Summaries. The contractor shall provide a monthly financial summary report to the identified project POC for each project supported by this contract. This is a subset of the Monthly Financial Summary report The monthly project reports shall include:

· Total funding (labor/material/travel) for the project on the current contract year.

· Hours expended by each prime contractor employee and sub-contractor supporting the project for the reporting month.

· Total hours expended by each prime contractor employee and sub-contractor supporting the project in the current contract year.

· Overtime hours expended by each prime contractor employee and sub-contractor employee supporting the project in the current contract year (a sub-set of the total hours charged).

· Total labor costs for the reporting month and for the current contract year. Labor costs for individual contractors should not be given on this report.

· Total material funding expended and remaining in the current contract year.

· Travel expended in the reporting month, total travel expended in the current contract year and total travel funding remaining.

4.1.4 Monthly Burn Rate Report. The contractor shall provide a monthly funding burn rate report in accordance with CDRL A001. The burn rate report shall consist of graphs for labor, material, and travel that plot the total contract funding and expenditures over the course of the current contract year. The graphs will have sufficient resolution to predict potential future funding deficiencies in a timely manner.

4.2 Monthly Progress Report

The contractor shall provide a monthly progress report in accordance with CDRL A002. This report shall list the monthly accomplishments and upcoming project objectives for each project, or groups of projects as deemed appropriate by the COR. Trips and significant event shall also be addressed. The report shall be delivered by the 15th day of the following month.

4.3 Other Reporting

As requisites to the various task activities of the contract, the contractor shall provide additional reporting, documentation, and schedules in accordance with CDRL A005. Deliverable requirements shall be determined during task definition. Reporting should be in sufficient detail and quality to meet the requirement established at task definition and shall be in compliance with the standards and guidelines in Section 2.0. Other reporting requirements could include, but are not be limited to:

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

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

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

· Supporting documentation for material procurements.

4.4 Enterprise-Wide Contractor Manpower Reporting Application (ECMRA) The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Naval Air Systems Command, Office of Naval Research, Army PM-Cargo and United States Air Force via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address:

https://doncmra.nmci.navy.mil.

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

4.5 Incurred Cost Progress Reporting

In order to support invoice reviews conducted as part of proper surveillance, the Contractor shall report incurred cost and progress in accordance with NAVAIR clause 5252.232-9529, “Incurred cost and Progress Reporting for Services,” CDRL A003, and contract Attachment xx.

5.0 TRAVEL

5.1 The Contractor will be required to travel in performance of this contract. Costs associated with travel are subject to NAVAIR clause 5252.232-9509 Reimbursement of Travel, Per Diem, and Special Material Costs and/or NAVSEA clause HQ B-2-0020 Travel Costs - Alternate I.

5.2 The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements.

5.3 All contractor travel in support of this contract shall be subject to approved in advance in accordance with the most recent NAVY, NAVAIR, and IBST travel review and approval processes.

5.4 Travel may include, but is not limited to, various Contractor facilities, Navy facilities, DoD facilities, other government agency facilities, OCONUS DoD installations, and other activities as required.

5.5 Extended periods of travel will be periodically required to support the installation, setup, testing, and initial operation of new simulation systems or re-deployment of mobile simulation systems. Off-site operation support of new simulation systems for no more than 1 year is possible until official operation and maintenance activities are in place.

6.0 SECURITY

6.1 All Contractor personnel will comply with the IBST Security Standard Operating Procedures and all applicable NAVY and DoD security instructions.

6.2 Only United States citizens may perform under this contract. The contractor shall conform to the provisions of DOD-D-5220.22, “National Industrial Security Program,” and shall obtain security clearances for contractor employees requiring access to classified information and/or entry to controlled areas.

6.3 All Contractor personnel supporting tasks under this order must be eligible for a SECRET security clearance. The highest level of security required for performance of the tasks in Section 3.0 is TOP SECRET. Interim clearance is acceptable.

6.4 In accordance with Attachment X (DD Form 254), Top Secret Facility Clearance must be obtained within 30 days of contract award. Individuals requiring Top Secret clearances as identified in attachment 4 must be able to perform at the Top Secret level at the same time that Top Secret Facility Clearance is required.

6.5 Identification Badges. Contractor identification badges will be issued by the Government to on-site Contractor personnel. In accordance with NASPAXRIV Instruction 5510.15Q or the most current version of this instruction, identification badges must be displayed at all times. The Contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to all applicable regulations concerning their use and possession. Identification badges are U.S. Government property and shall be surrendered to the Pass and ID Office (22268 Cedar Point Rd, BLDG 409, NAS Patuxent River, MD 20670) upon expiration of the contract or termination of employment. The Government will not check out Contractor personnel unless all media, including Common Access Cards (CAC), are returned in accordance with the instruction identified previously in this paragraph.

6.6 Contractor Affiliation Identification. Contractor Personnel Identification shall be in accordance with clause 5252.211-9510 Contractor Employees (NAVAIR) (MAY 2011).

6.7 Information Technology Security. The Department of the Navy (DON) Automated Data Processing (ADP) Security Program outlined in OPNAVINST 5239.1B, or the most current version of this instruction, applies to all efforts under this contract.

6.8 OPSEC Plan (CDRL A004).