DRAFT_MARK_Systems_Development__Support_and_Integration__C4ISR_Systems_Design_and_Development__PWS_R!.doc

Performance Work Statement (PWS)

Systems Development, Support and Integration (C4ISR Systems Design and Development)

7/15/2013

Version 1.0 Rev 1 5Vision Statement

1 Introduction

1.1 Mission

1.2 Background

1.2.1 Projects previously supported

1.3 Scope

2 General Requirements

2.1 Period of Performance

2.2 Non-Personal Services

2.3 Business Relations

2.3.1 Organizational Conflict of Interest

2.4 Contract Administration and Management

2.4.1 Contract Management

2.4.2 Personnel Administration

2.4.3 Contract Administration

2.4.4 Contractor's Management Plan (CMP)

2.4.5 Contractor's Quality Management System

2.4.6 Government Quality Assurance Surveillance Plan (QASP)

2.5 Contractor Furnished Equipment, Materials, Subcontracts and Supplies

2.6 Contractor Personnel, Disciplines, and Specialties

2.7 Facilities and Staffing

2.8 Travel / Temporary Duty (TDY)

2.9 Applicable Documents

2.9.1 SSDD Technical Specifications and Documents

2.9.2 Military/Department of Defense Specifications and Standards

2.9.3 Other Government Documents

2.9.4 Non-Government Documents

2.9.4.1 American National Standards Institute (ANSI)/Electronic Industries Association (EIA)

2.9.4.2 International Organization for Standardization (ISO) Standards 3 Performance Requirements

3.1 C4ISR Systems Research, Development, Engineering, and Test

3.2 Fabrication, Assembly, and Verification Testing of Systems/Subsystems/Elements

3.3 SSDD Programs Systems Engineering (SE) Support

3.4 SSDD Reliability, Maintainability, and Availability (RMA) Engineering

3.5 SSDD Parts Engineering and Management Support

3.6 SSDD Design, Fabrication, and Test Process Improvement

3.7 SSDD Systems Design Verification Engineering

3.8 SSDD Electronic Parts Procurement Management

4 Special Requirements

4.1 Security

4.1.1 DD Forms 254

4.1.3 Special Access Programs (SAPs)

4.1.4 Identification (ID) Badges and Vehicle Passes

4.2 Safety

4.3 Contractor Phase-in Transition

4.4 Government Furnished Materials

5 Deliverables 6 Definition Acronyms

Performance Work Statement (PWS) Systems Development, Support and Integration (C4ISR Systems Design and Development) Vision Statement Develop C4ISR systems that respond to Navy, Department of Defense, and national mission requirements with improved performance, capability, reliability, efficiency, and life cycle cost.

1 Introduction

The Space Systems Development Department (SSDD) is the space and ground support systems research and development (R&D) organization of the Naval Center for Space Technology (NCST), an organization within the U.S. Naval Research Laboratory (NRL) in Washington, DC, which is the designated lead for Navy Space Program technology development and acquisition of space, aerospace and Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) systems that support Naval Missions.

1.1 Mission

The mission of SSDD is to derive system requirements from mission requirements, develop architectures in response to the systems requirements, and design and develop systems, subsystems, equipment, and implementation technologies to achieve optimized, integrated operational space and ground systems.

1.2 Background

SSDD is currently involved in the concept definition and design phases on various advanced concepts studies and projects which will evolve into future space, aerospace and tactical C4ISR systems. Development responsibilities extend across the entire space/ground spectrum of hardware, software and advanced technologies including digital processing and control analog systems, power, communications, command and telemetry, radio frequency, optical, payload and electromechanical systems, as well as, systems engineering.

The SSDD operates four Space Research, Development, Test and Evaluation (RDT&E) engineering support field sites in Maryland, Virginia, and California. The department's technical programs include the following:

· Space systems engineering capability from mission concept development to on-orbit engineering and operational support

· System architecture and development of satellite payloads including optical sensors, spacecraft processors and controllers, signal processing, data management, and algorithm/software development

· Design, fabrication, test, integration, and launch support for electrical/electronic components and systems

· Development and implementation of ground stations for communications, data collection, processing and dissemination, spacecraft tracking, telemetry and control systems, and tactical communications systems

· Space surveillance, advanced satellite navigation technology, and precise time and time interval (PTTI) theory and techniques

1.2.1 Projects previously supported

1.2.1.1 Department of Defense Special Investigative Services

Objectives: Develop and integrate mission specific products to identify, exploit, and neutralize criminal, terrorist, and intelligence threats. Provide solutions to military investigative and intelligence offices including development/integration of technical products, operational concept development, systems engineering, design, evaluation, and test.

1.2.1.2 Maritime Security

Objectives: Develop and integrate mission specific products to improve maritime security in the port and coastal regions and global waterways (e.g. global shipping lanes, choke points, U.S. inland waterways, coastal waters, and coastal approaches). Provide solutions including development/integration of technical products, operational concept development, systems engineering, design, evaluation, and test.

1.2.1.3 Law Enforcement

Objectives: Develop and integrate mission specific products to identify, exploit, and neutralize criminal, terrorist, and intelligence threats. Provide solutions to federal, state, and local law enforcement agencies including development/integration of technical products, operational concept development, systems engineering, design, evaluation, and test.

1.2.1.4 Secure Communications

Objectives: Develop and integrate mission specific products for secure network, mobile, and man-portable communications. Research and vet technologies for secure mobile communications (e.g. secure tracking and display of mobile assets and forces). Provide solutions including development/integration of technical products, operational concept development, systems engineering, design, evaluation, and test.

1.2.1.5 Emergency Response Unit Support

Objectives: Develop programs and systems that (1) optimize fire fighter and paramedic scheduling and (2) track fire fighters to and from emergency events using RFID technology.

1.2.1.6 Spacecraft Operations, Integration, Test, and Technology Development

Objectives: Develop and implement command and control requirements, concepts of operations, and integration and test plans for ground support to current and new spacecraft. Develop technologies to enable and support new spacecraft capabilities, support the integration of new satellites into the NRL Blossom Point Tracking Facility command and control architecture, provide physical security and other support services as required in the operations of a satellite command and control facility.

1.2.1.7 Mobile Communication Systems

Objectives: Design, build, integrate, test, deliver, and install technologies for next generation secure mobile communications, including communications platforms and multimedia display systems for use by the President of the United States of America. Provide electrical and software engineers as well as technicians to support development and maintenance of mobile command and control systems for various DOD and other federal agencies. Provide operations and maintenance support to previously delivered systems.

1.2.1.8 Maritime Domain Awareness

Objectives: Support system engineering, program management, design, and configuration control to develop tracking and tagging algorithms for future naval capabilities. Provide software development, analysis, cloud, and security support services. Perform MONGOOSE/S2A systems engineering, software development and analysis for various security domains. This effort will sustain the development of Maritime Domain Awareness projects at NRL.

1.2.1.9 Astrodynamics

Objectives: Support system engineering, program management, design, and configuration control to (a) maintain and further develop the NRL OCEAN spacecraft orbit modeling software and (b) perform OCEAN-based analysis of various satellite and ground systems.

1.2.1.10 Infrastructure

Objective: Provide system administration, configuration management and certification and accreditation support for NRL computer systems that support multiple programs within Code 8100.

1.2.1.11 Special Intelligence, Surveillance, and Reconnaissance (ISR) System Support

Objectives: Provide engineering support related to NRL ISR systems including CPS, CPS-X, ETG, EATS, and Scorpion. Support concept development and systems engineering to extend capabilities of existing ISR systems and / or new ISR systems. Develop software architectures to implement applications identified in concept development. Develop and implement specialized algorithms to improve ISR geolocation performance and ionosphere-related error mitigation.

1.2.1.12 Modular Sensor Systems

Objectives: Support the development and deployment of persistent Intelligence, Surveillance, and Reconnaissance (ISR) Modular Sensor Systems (MSS) comprised of sensors, processing, and data dissemination components. Redesign/replace obsolete MSS technologies/prototypes, implement system protection software upgrades and system security enhancements, and perform field testing before transition to existing and/or to new MSS systems. Develop, integrate and test new MSS capabilities such as the newly developed NRL acoustic array.

1.3 Scope

The purpose of this contract is to provide personnel to perform Systems Engineering support for the Space Systems Development Department Code 8100 in the following areas:

· C4ISR Systems Research, Development, Engineering, and Test

· SSDD Fabrication and Assembly of SSDD Systems/Sub-systems

· SSDD Programs Systems Engineering (SE) Support

· Reliability, Maintainability, and Availability (RMA) Engineering

· SSDD Parts Engineering and Management Support

· SSDD Design, Fabrication, and Test Process Improvement

· SSDD Systems Design Verification Engineering

· SSDD Electronic Parts Procurement Management

Efforts in support of the tasks delineated in Section 3, Performance Requirements, below will be conducted in coordination with teams that may include Government scientists and engineers, and other Contractors. The quality and timeliness of the provider's contribution to the work will be evaluated in terms of its impact on the success of the overall programs/projects.

2 General Requirements

The Naval Research Laboratory (NRL) Requirements for On-Site Contractors (ROSC) dated 8 December 2008 provides general instructions for Contractors conducting business at/on NRL property. Compliance with specific paragraphs of the NRL ROSC cited in the Section 2 - General Requirements and Section 4 - Special Requirements is mandatory, other requirements in the NRL ROSC are provided for information purposes only.

2.1 Period of Performance

The period of performance is for 1 base year of 12 months and two 12-month options years. The period of performance reads as follows:

· Base Year 10/01/2013 to 09/30/2014

· Option Year 1 10/01/2014 to 09/30/2015

· Option Year 2 10/01/2015 to 09/30/2016

2.2 Non-Personal Services

The Government will neither supervise contractor employees nor control the method by which the contractor performs the required tasks.

The Government will not assign tasks to, or prepare work schedules for, individual contractor employees.

The Contractor shall be responsible for managing its employees and guarding against any actions that are of the nature of personal services, or give the perception of personal services as defined in FAR-Part 37, Service Contracting, dated 31 May 2011.

The Contractor shall notify the Contracting Officer (KO) if any Government requested actions constitute, or are perceived to constitute personal services.

2.3 Business Relations

The contractor shall integrate and coordinate all activity needed to execute this contract.

2.3.1 Organizational Conflict of Interest

Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5.

The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI.

The Contractor shall promptly submit a mitigation plan to the Contracting Officer to avoid or mitigate any such OCI.

The Government Contracting Officer is the sole determinant official for accepting the Contractors mitigation plan. In the event the Contracting Officer determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may effect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

2.4 Contract Administration and Management

The following subsections specify requirements for contract management and contractor personnel administration

2.4.1 Contract Management

The Contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to this contract.

The Contractor shall incorporate no proprietary hardware or software in any deliverable developed under this contract unless authorized, in writing, by the Contracting Officer.

The Contractor shall assign work effort and maintain proper and accurate time keeping records of personnel assigned to work on this contract.

The Contractor shall provide a Monthly Status Report (MSR) in compliance with SSD-D-059, NRL/SSDD Monthly Status Report Procedure, on the schedule and in the format defined in [CDRL A001].

The Contractor shall provide a monthly Contractor On-Site/Off-Site Labor Report on the schedule and in the format defined in [CDRL A012] to report the total labor hours and costs billed to each assigned task for all Contractor (and subcontractor) personnel.

The Contractor shall generate and submit (on at least a quarterly basis) schedules for each task assignment on the schedule and in the format defined in [CDRL A002].

2.4.2 Personnel Administration

The Contractor shall provide all personnel, resources and materials necessary to provide the support required to accomplish the tasks delineated in Section 3, Performance Requirements in this PWS...

The Contractor shall provide for employees during designated Government non-work days or other periods where Government offices are closed due to weather or security conditions.

The Contractor shall maintain the currency of their employees by providing initial and refresher training as required to meet the PWS requirements.

The Contractor shall make necessary travel arrangements for employees.

2.4.3 Contract Administration

The Contractor shall establish processes and assign appropriate resources to effectively administer this contract.

The Contractor shall respond to Government requests for contractual actions within five work days.

2.4.4 Contractor's Management Plan (CMP)

The CMP provides the Government insight to the systems, processes, and structure within which the contractor operates. The CMP should include, as applicable and if not defined in a separate plan: quality control, risk management, systems engineering, software development, configuration management, earned value management, and subcontract management.

The Contractor shall develop a CMP that provides the program management, control, and reporting functions necessary to manage and direct the accomplishment of the efforts required under this PWS to be delivered 30 days after contract award [CDRL A024].

The Contractor shall receive the contracting officer’s acceptance in writing of any proposed change to his management plan once the CMP has been accepted by the Government.

The Contractor shall develop a Contractor's Risk Management Plan (CRMP) in accordance with DI-MGMT-81808, Contractor's Risk Management Plan and guided by the contents of NASA/SP-2011-3422, Version 1.0, NASA Risk Management Handbook, November 2011, to be delivered 60 days after assignment of initial tasks orders under this PWS [CDRL A030].

The Contractor shall update the CRMP no more than 30 days after the addition of significant new tasks to the original task orders or when directed by the COR [CDRL A030].

2.4.5 Contractor's Quality Management System

The Contractor shall have a Quality Management System certified to AS9100 Rev. C, Aerospace Quality Management Systems.

2.4.6 Government Quality Assurance Surveillance Plan (QASP)

The Government will evaluate the contractors performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP) provided as an attachment to this proposal.

The QASP is focused on what the Government will do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

2.5 Contractor Furnished Equipment, Materials, Subcontracts and Supplies

Equipment and unexpended materials and supplies purchased by the contractor under this contract become the property of the Government at the end of the performance period, including all options.

The Contractor shall provide supplies for contractor personnel.

The Contractor shall provide any other equipment, material, and supplies, not furnished by the Government, but required to perform the work defined under Paragraph 3, Performance Requirements, below.

The Contractor shall be responsible for any subcontract management necessary for performing efforts described in Paragraph 3, Performance Requirements, below.

2.6 Contractor Personnel, Disciplines, and Specialties

The minimum education, training, and experience required by contractor personnel to perform support tasks identified in this PWS are defined in the labor category descriptions provided in Attachment (N) of the Request for Proposal (RFP).

2.7 Facilities and Staffing

The Contractor shall provide the staff and clean room facilities (controlled to 10,000 particles per cubic foot) qualified for the assembly of optics and other contamination sensitive technology systems and assemblies, and trained personnel certified to instruct and assemble to NASA-STD-8739-1, Workmanship Standard For Staking And Conformal Coating Of Wiring Boards And Electronics Assemblies, NASA-STD-8739.2, Workmanship Standard For Surface Mount Technology, NASA-STD-8739.3, Soldered Electrical Connections, and NASA-STD-8739.4, Crimping, Interconnection Cables, Harnesses and Wiring. (See Section 3.2.2, Fabrication and Assembly)

The Contractor shall provide and staff facilities for conducting powered thermal vacuum cycling at a vacuum of 1 x 10-6 Torr and over temperature extremes ranging from - 40 to + 85 degrees Centigrade; on four units simultaneously at four different temperature levels, and for single units with dimensions of 45 inches by 15 inches by 15 inches with the baseplate surface of 45 inches by 15 inches. (See Section 3.2.3, Verification Testing.)

The Contractor shall provide and staff facilities having a DCMA-approved purchasing system with the capability to process and store at least 2000 lots of parts totaling at least 100,000 parts annually for the procurement, fabrication, test, and storage of systems, subassemblies, units, and parts required to perform tasks in Section 3.6, SSDD Electronic Parts Procurement Management.

2.8 Travel / Temporary Duty (TDY)

Travel to other government facilities or contractor facilities may be required for conduct of tasks in Section 3, Performance Requirements.

The Contractor shall submit all travel requirements (including plans, agenda, itinerary and dates) for pre-approval to the Government and is on a strictly cost reimbursable basis.

The Contractor shall bill costs for travel in accordance with FAR 31.205-46 Travel Costs (subject to local policy & procedures).

2.9 Applicable Documents

The Contractor shall comply with the following specifications, standards, and publications as they apply to each task. Where specified, the exact revision level of the reference listed should be used. In some circumstances there may be additional documents required not listed below. In those circumstances, the government will inform the contractor and provide one copy as necessary. Where a revision level is not included, the latest reference to the document from the Department of Defense Index of Specifications and Standards (DODISS) apply. Nothing in this document, however, supersedes applicable laws or regulations unless a specific exemption has been obtained. In the event of conflict between the referenced documents and this PWS, the requirements of this PWS apply.

2.9.1 SSDD Technical Specifications and Documents

The above documents will be available for viewing on line at the NRL Contract Web Site or in the Contracting Office, Code 3200, Naval Research Laboratory, 4555 Overlook Ave, SW, Washington, DC 20375-5326. After contract award the documents can be obtained from the designated Contracting Officer’s Representative (COR).

2.9.2 Military/Department of Defense Specifications and Standards

2.9.3 Other Government Documents

All applicable documents can be found at: http://www.hq.nasa.gov/codeq/doctree/texttree_num.htm and https://nepp.nasa.gov/index.cfm/316

2.9.4 Non-Government Documents

2.9.4.1 American National Standards Institute (ANSI)/Electronic Industries Association (EIA)

(Applications for copies should be addressed to the American National Standards Institute, http://www.ansi.org, 1430 Broadway, New York, NY 10018.) and/or (Application for copies should be addressed to Electronic Industries Association, http://www.eia.gov, 2001 Pennsylvania Ave., NW, Washington, DC 20006.)

2.9.4.2 International Organization for Standardization (ISO) Standards

Related documents may be found at http://www.iso.org 3 Performance Requirements

General systems engineering tasks for analyzing systems, determining internal and external interfaces, performance of system definition tasks, and determination of evaluation metrics and measures of effectiveness are defined in EIA/IS-632, Systems Engineering.

The following subsections specify the specific Systems Engineering tasks, performance objectives, and performance elements required for this contract. Selection and use of electronic parts in SSDD systems/subsystems are in accordance with standards cited in the performance requirements below and are guided by requirements in DoD-E-8983C, Electronic Equipment, Aerospace, Extended Space Environment, General Specification for, DoD-HDBK-263B, Electrostatic Discharge Control Handbook for Protection of Electrical and Electronic Parts, Assemblies, and Equipment (Excluding Electrical Initiated Explosive Devices) (Metric), and MIL-HDBK-454B, General Guidelines for Electronic Equipment, as specified herein.

3.1 C4ISR Systems Research, Development, Engineering, and Test

Subtasks under this task are directed towards the development, fabrication, test and evaluation of C4ISR equipment (hardware and software) and integration of that equipment into space, airborne, sea based, and ground based vehicles by the Contractor.

Tasks for evaluating other contractor's or programs developed systems and performing general SSDD programmatic functions for which the Contractor is not fabricating equipment or integrating the Contractor's equipment/software with other systems are covered under tasks 3.2 thru 3.7 below.

3.1.1 The Contractor shall develop and implement a program management plan to provide systems engineering, logistics engineering, integration, test and evaluation, and operations support for assigned C4ISR proof-of-concept, engineering development, and operational space/aerospace and sea/ground based systems defined in the following sub-tasks.

Systems requiring support can include hardware and software for tactical internet controlled systems, satellite/aerospace RF and optical payloads, satellite/aerospace experimental and operational science instruments and payloads, satellite power systems, test systems, software defined systems (SDS)/software reconfigurable systems (SRS), SDS radios and payloads including software defined radios (SDR), software reprogrammable payloads (SRP), software reprogrammable radios (SRR), and SDS applications and infrastructure software and firmware.

The following tasks further define the specific support required.

Performance Standards

a) STD: Timely

AQL: 60 days after award of initial Task Order for specified systems;

Updated PMP 45 days after award of Task Orders adding a new system

b) STD: Addresses all program areas

AQL: Guided by EIA/IS-632 - Systems Engineering

c) STD: Compliant with SDD-D-061 - Procedure for Preparation of Program Plans

d) STD: Program tasks conform to MIL-HDBK-881C - CWBS tasks for the systems assigned

Deliverables A016 Program Management Plan

3.1.1.1 The Contractor shall provide systems engineering, software development, and logistics engineering support for design, fabrication, and transition to operations of Maritime Domain Awareness (MDA) systems.

Development of MDA systems includes tasks required to obtain DoD information assurance certification and accreditation process in accordance with DOD-INST-8510.01 - DoD Information Assurance Certification and Accreditation Process (DIACAP). Previous NRL programs supported include Comprehensive Maritime Awareness (CMA), the Vessel Tracking Program (VTP), Master, MONGOOSE and S2A.

Performance Standards

a) STD: Special support for MDA programs covered in the PMP Deliverables A016 Program Management Plan

3.1.1.2 The Contractor shall design, build, integrate, operate, and maintain C4ISR sensors and communications equipment for mobile ground and seaborne surface vehicles.

Integration of equipment into selected vehicles includes development of modifications to vehicle power systems, antennas, electronics and man-machine user interfaces needed to operate the sensors and communication equipment.

Performance Standards

a) STD: Special support for C4ISR mobile electronic systems covered in the PMP

Deliverables

A016 Program Management Plan

3.1.1.3 The Contractor shall develop, integrate, operate, and maintain Situation Awareness (SA) visualization hardware and software for C4ISR sensor systems.

Situation awareness visualization hardware and software are used to allow manipulation and display of globally or geographically filtered situation awareness data by users in real time.

Performance Standards

a) STD: Special support for SA programs covered in the PMP Deliverables A016 Program Management Plan

3.1.1.4 The Contractor shall provide systems engineering, hardware and software development, and integration for Unmanned Airborne System (UAS) payloads and radios.

These systems are capable of providing simultaneous multiple channels of tactical communications and signals intelligence within constrained size weight, and power budgets. Additionally, these systems interoperate with and may replace existing inventory payloads and radios.

Performance Standards

a) STD: Special support for UAS payload and radio programs covered in the PMP Deliverables A016 Program Management Plan

3.1.1.5 The Contractor shall develop ground stations for controlling Communications and Signals Intelligence (SIGINT) space/aerospace payloads.

These payloads operate in real time over low bandwidth RF communications links, have browser based displays for controlling the payloads and receiving real time communications/SIGINT results, provide simulation capabilities that integrate with the payload operating environment, and use laptop computer applications for development and integration.

Performance Standards

a) STD: Special support for ground station projects covered in the PMP Deliverables A016 Program Management Plan

3.1.2 C4ISR Programs/Projects Special Reporting

Some special interest Task 3.1 C4ISR programs/projects (designated by the COR), require the additional cost and schedule information tracking and reporting described in this task.

3.1.2.1 The Contractor shall develop an Earn Value Management Systems (EVMS) based structure for reporting cost and schedule progress on programs/projects designated for reporting under Task 3.1.1.

Performance Standards

a) STD: Timely

AQL: 15 days after award of Task Order requiring EVMS reporting

b) STD: Conforms to ANSI/EIA Standard 748-98 Earned Value Management Systems Deliverables A003 Program Documentation

3.1.2.2 The Contractor shall provide a monthly Contract/Schedule Status Report (C/SSR) for all programs/projects for which task 3.1.1 applies.

Performance Standards

a) STD: Timely

AQL: Initial report 90 days after a specific task is assigned;

20 days after the end of the month for which the monthly C/SSR applies thereafter

b) STD: Contractor's EVMS correctly applied

c) STD: Meets the criteria of DI-MGMT-81467 Cost/ Schedule Status Report

A001 Business Reports

3.1.2.3 The Contractor shall provide a quarterly Contract Funds Status Report (CFSR) for all programs/projects for which task 3.1.1 applies.

Performance Standards

a) STD: Timely

AQL: Initial report 90 days after a specific task is assigned;

20 days after the end of the month for which the quarterly CFSR applies thereafter

b) STD: Contractor's EVMS correctly applied

c) STD: Meets the criteria of DI-MGMT-81468 Cost Funds Status Report

A001 Business Reports

3.1.2.4 The Contractor shall develop and submit a Contract Work Breakdown Structure (CWBS) for approval by the COR prior to implementing the Contractor's EVMS on a specific program/project requiring task 3.1.1.2 and 3.1.1.3 reporting.

a) STD: Timely

AQL: 15 days after assignment of task

b) STD: Conforms to MIL-HDBK-881C for the system assigned

A011 Contract Work Breakdown Structure

3.1.3 System/Sensor/Subsystem Analysis, Definition and Planning

3.1.3.1 The Contractor shall develop and document systems architecture concept, plans, implementations, and operational analyses for current and planned C4ISR programs/projects.

Analysis efforts include development and maintenance of concept plans, white papers, and Concept of Operations (CONOPS).

Performance Standards

a) STD: In accordance with established schedule

b) STD: Identify potential areas for improvement

c) STD: Identify technologies to improve system architectures

A003 Program Documentation

3.1.3.2 The Contractor shall characterize system designs in terms of performance, weight, internal/external interfaces, specifications, and life cycle cost (LCC) objectives for C4ISR systems assigned.

A system may include a single sensor space/aerospace/ground sensor/communications element (either stand alone or for integration into a larger system) up to all major components of a large, complex multiple component space/aerospace/ground system.

Performance Standards

a) STD: In accordance with established schedule

b) STD: Provides evaluation of tradeoffs among alternative solutions including risk assessment of achieving program objectives of each alternative

c) STD: Comprehensive technical assessment

AQL: Defines modes, capabilities and interfaces, including mechanical structures, command and control, experiments, electrical power generation/distribution, data handling and distribution, communications, ground/space component distribution, orbital visualization and other system related components.

3.1.3.3 The Contractor shall perform technical assessments and engineering analyses for C4ISR programs/projects assigned.

Assessments and analyses include efforts to: identify, recommend, and implement solutions for critical design or performance deficiencies; provide system level integration test plans and procedures; identify and report deficiencies; perform hardware and software design reviews; identify, analyze or develop decision support, simulation or modeling support activities; perform short-term engineering analyses and quick reaction studies; perform system survivability analyses; and analyze/resolve LAN/WAN network protocol issues.

Performance Standards

a) STD: In accordance with established schedule

b) STD: Addresses all technical areas

c) STD: Identifies deficiencies

d) STD: Identifies corrective actions

A004 Technical Documentation

3.1.3.4 The Contractor shall analyze, evaluate, define, and develop systems applications for C4ISR programs/projects assigned.

System applications to be evaluated will be assigned by task orders and may include: bus architectures, their protocols and throughput characteristics; subsystem design implementations; fail-safe/fault-tolerant provisions; modeling and simulation of system performance using MATLAB and SIMULINK; functional interfaces among subsystems; interface circuit configurations; interface signal level requirements; and internal power distributions and revised power budgets.

Performance Standards

a) STD: In accordance with established schedule

b) STD: Comprehensive

AQL: Provides sufficient information to support make (SDSI Contractor)-buy (other contractor) procurement decisions

A005 Technical Data Package

3.1.3.5 The Contractor shall conduct pre-mission, mission, and post-mission systems performance analyses for C4ISR space and aerospace flight systems experiments/operations...

The work to be performed includes analysis and evaluation of: mission data to determine subsystem and system performance characteristics; recovery, reduction and analysis of mission data; development of systems necessary for collection, reduction and analysis of mission data; real-time problem analysis and resolution for operational missions; analysis of mission data to determine the nature of faults or performance-limiting factors; and development of recommended solutions for improving systems performance in subsequent mission experiments/operations, including flight software or hardware upgrades to maximize mission performance.

Performance Standards

a) STD: Timely

AQL: Quick-look report 15 days after the completion of each mission;

Final report 60 days after completion of each mission

b) STD: Addresses all errors and inadequacies

c) STD: Identify trends and areas of improvement

d) STD: Identifies corrective actions

e) STD: Recommended solutions and procedures are implementable

A010 Test and Analysis Reports

3.1.4 Information Assurance

3.1.4.1 The Contractor shall prepare for and conduct information assurance certification testing for C4ISR programs/projects assigned.

Performance Standards

a) STD: In accordance with established schedule

AQL: Provide test plan 10 days prior to test

b) STD: Timely

AQL: 10 days after completion of certification test.

c) STD: Complies with DoD-INST-8510.0, DOD Information Assurance Certification and Accreditation Process (DIACAP)

d) STD: Complies with NRL 5239.1A, Information Systems Security Plan

e) STD: Complies with NRL 5510.40E, Security Manual

3.1.4.2 The Contractor shall prepare information assurance accreditation documentation for C4ISR programs/projects assigned.

a) STD: In accordance with established schedule

AQL: Accepted with no changes required 98% of the time

b) STD: Complies with DoD-INST-8510.0, DOD Information Assurance Certification and Accreditation Process (DIACAP)

c) STD: Complies with NRL 5239.1A, Information Systems Security Plan

d) STD: Complies with NRL 5510.40E, Security Manual

e) STD: Returned for correction of errors or omissions

AQL: less than 2%

3.1.5 Sensor/Vehicle Integration and Installation Engineering Support

3.1.5.1 The Contractor shall develop and implement a product verification test process for sensor/communications payloads intended for use in C4ISR space-borne systems.

Performance Standards

a) STD: In accordance with established schedule

b) STD: Timely

AQL: 30 days after the completion of each test

c) STD: Complies with MIL-STD-1540D, Product Verification Requirements for Launch, Upper Stage, and Space Vehicles requirements.

Deliverables A004 Technical Documentation (a, c) A010 Test and Analysis Reports (b, c)

3.1.5.2 The Contractor shall develop, design, document, install, and test integration of space-borne/airborne sensor and communications payloads for C4ISR programs/projects assigned.

a) STD: In accordance with established schedule

b) STD: Provides integration design requirements

AQL: Integrated system meets its operational and technical requirements when installed in vehicle

c) STD: Complies with applicable sections of MIL-STD-31000, DoD Standard Practice, Technical Data Packages.

d) STD: Contains Interface Wiring List (IWL)

e) STD: Provides update of ICDs (if they already exist)

f) STD: Timely

AQL: 30 days after the completion of each test

g) STD: Meets technical specifications

h) STD: Identifies and corrects deficiencies Deliverables A005 Technical Data Package (a, b, c, d, e) A010 Test and Analysis Reports (f, g, h)

3.1.5.3 The Contractor shall develop, design, document, install, and test integration of vehicle power systems, antenna, electronics, and man-machine interface modifications for embedding C4ISR sensors/communications into ground/sea based vehicles.

Performance Standards

a) STD: In accordance with established schedule

b) STD: Provides integration design requirements

AQL: Integrated system meets its operational and technical requirements when installed in vehicle

c) STD: Complies with applicable sections of MIL-STD-31000, DoD Standard Practice, and Technical Data Packages.

d) STD: Contains Interface Wiring List (IWL)

e) STD: Provides update of ICDs (if they already exist)

f) STD: Timely

AQL: 30 days after the completion of each test

g) STD: Meets technical specifications

h) STD: Identifies and corrects deficiencies

Deliverables A005 Technical Data Package (a, b, c, d, e) A010 Test and Analysis Reports (f, g, h)

3.1.5.4 The Contractor shall develop, design, document, install, and test integration of space-borne/airborne sensor and communications payload ground station control equipment for C4ISR programs/projects assigned.

a) STD: In accordance with established schedule

b) STD: Provides integration design requirements

AQL: Integrated system meets its operational and technical requirements when installed in vehicle

c) STD: Complies with applicable sections of MIL-STD-31000, DoD Standard Practice, Technical Data Packages.

d) STD: Contains Interface Wiring List (IWL)

e) STD: Provides update of ICDs (if they already exist)

f) STD: Timely

AQL: 30 days after the completion of each test

g) STD: Meets technical specifications

h) STD: Identifies and corrects deficiencies

Deliverables A005 Technical Data Package (a, b, c, d, e) A010 Test and Analysis Reports (f, g, h)

3.1.5.5 The Contractor shall design and develop power systems that convert, condition, and distribute electric power for satellites, space payloads, and tactical airborne and ground systems.

These power systems range from low voltage and high voltage DC-to-DC power converters for space systems to high power (> 3kW) stackable power systems for C4ISR systems that automatically load share and balance input AC power.

Performance Standards

a) STD: Timely

AQL: In accordance with established schedule

b) STD: Meets technical specifications

c) STD: Complies with applicable sections of MIL-STD-31000, DoD Standard Practice, Technical Data Packages

d) STD: Timely

AQL: In accordance with established schedule

e) STD: Meets requirements of MIL-STD-461F, as tailored by the COR

3.1.5.6 The Contractor shall design, develop, and integrate software defined radio communications applications for use in C4ISR tactical communications networks.

a) STD: In accordance with established schedule

b) STD: Compliant with applicable standards

AQL: JTRS Software Communications Architecture (SCA) Specification; SSD-D-AS142, Software Development Specifications

3.1.6 Integrated Logistics Support (ILS) Engineering

Logistics engineering tasks include: (1) ILS planning, (2) Logistics Support Analysis, (3) Life Cycle Cost Analysis, (4) Reliability design, evaluation and monitoring, (5) Maintainability design, evaluation and monitoring, (6) maintenance and maintenance planning, (7) design and development of technical data, manuals and handbooks, (8) design and development of training and training documentation/ material, (9) identification of skills and manpower requirements, prerequisites and sources, (10) identifying requirements and resources to satisfy packaging, handling, storage and transportation needs, (11) identifying, quantifying, locating, purchasing and replenishing spare and repair parts, (12) minimizing need for, identifying, purchasing and replenishing support and test equipment, (13) identifying requirements, analyzing existing, and defining requirements for new facilities, and (14) identifying, examining and making recommendations concerning computer based systems for diagnostics, training, and on-line documentation.

3.1.6.1 The Contractor shall develop Integrated Logistics Support Plans (ILSP) for C4ISR systems assigned.

Performance Standards

a) STD: Timely

AQL: In accordance with established schedule

b) STD: Addresses all program areas

c) STD: Recommended solutions and procedures are implementable

d) STD: Provides cost effective support of equipment within resources available

e) STD: Meets supportability and operational objectives.

f) STD: Provides for monitoring effectiveness and appropriateness of ILSP when implemented.

3.1.6.2 The Contractor shall implement Contractor developed Integrated Logistics Support Plan (ILSP) for C4ISR systems assigned.

a) STD: Early identification of problems

b) STD: Identifies and corrects deficiencies

c) STD: Executable

d) STD: Contractor provides ILS data on schedule.

Deliverables A009 Integrated Logistics Support Data

3.1.6.3 The Contractor shall evaluate inherent and achieved Reliability, Maintainability, and Availability (RMA) characteristics for assigned C4ISR systems.

RMA evaluations include (depending on the development phase of the systems being examined) determination of system potential, comparing this potential to the RMA requirements for the system, providing recommendations for improvement of RMA characteristics where applicable, and assessment of proposed RMA trade-offs among competing design concepts.

Performance Standards

a) STD: In accordance with established schedule

AQL: Meets schedule 95% of the time measured over yearly period

b) STD: Provides in-depth technical assessment of initial and final system RMA characteristics potential to meet system RMA requirements

c) STD: Provides RMA trade-off assessment for competing designs for systems in conceptual, design, and fabrication phases of development

d) STD: Identifies unresolved RMA design/performance issues for SSDD systems in fabrication or test and evaluation stage of development

e) STD: Provides a schedule for analyses yet to be performed Deliverables A007 RMA Analysis Reports

3.1.6.4 The Contractor shall conduct Failure Mode, Effects, and Criticality Analyses (FMECA) for evaluation of their effect on the operation of the subsystem and identification of potential/actual failure modes.

Evaluations include verification of redundancy implementations, identification of single point failure modes, and preparation of design modification recommendations to lessen the impact of failure occurrence on subsystem operations; establishment of quantitative means of performing the evaluations; and providing for updating the FMECA to reflect data collected as a result of test efforts.

Performance Standards

a) STD: In accordance with established schedule

b) STD: Within 30 days of obtaining new failure test data

c) STD: Meets the intent of MIL-STD-1543B, Reliability Program Requirements for Space and Launch Vehicles, Task 204 FMECA Analysis

d) STD: Reflects data collected as a result of testing

e) STD: Reflects new failure mode(s) not previously evaluated (when they occur) Deliverables A019 FMECA Reports

3.1.6.5 The Contractor shall conduct Logistics Supportability Analysis (LSA) for C4ISR programs/projects assigned.

Documents that may be generated from a LSA include: Maintenance Planning Summary, Repair Analysis Summary, Support and Test Equipment Summary, Supply Support Summary, Manpower, Personnel and Training Summary, Facilities Summary, Packaging, Handling, Storage, and Transportation (PHS&T) Summary, and Post Production Support Summary. Since documents required vary with the phase of development of the supported system, exact documentation required will be provided in subsequent task orders under this contract.

Performance Standards

a) STD: In accordance with established schedule

b) STD: Complies with GEIA-STD-0007A, Logistics Product Data

A009 Integrated Logistics Support Data

3.1.7 Test Systems Design and Development

3.1.7.1 The Contractor shall develop automated test systems using Lab View and Lab windows for automated testing of RF and/or optical test equipment, radios, baseband testers such as Bit Error Rate Testers, and audio test analyzers.

Performance Standards

a) STD: In accordance with established schedule

b) STD: Controls target test instruments and conducts tests as required

3.1.7.2 The Contractor shall develop Waveform Development Environments (WDEs) for simulating target hardware and software operating environments.

Current WDE development programs include WDE's for Software Reconfigurable Payload (SRP) and RF/Digital Payload (RDP) projects.

Performance Standards

a) STD: In accordance with established schedule

b) STD: Accurately simulates target hardware/software environments

c) STD: Complies with SSD-D-142, Software Development Specifications, requirements

3.1.8 The Contractor shall perform packaging design engineering for implementing electronic and optical devices assigned in task 3.1 above.

a) STD: In accordance with established schedule

b) STD: Complies with MIL-STD-461F

c) STD: Complies with EIA/IS-649, Configuration Management

d) STD: Complies with SSD-D-005J, Configuration Management Plan

e) STD: Applicable program-specific Configuration Management requirements Deliverables A005…