Attachment 01 - SOW.pdf

Attachment (1)

Statement of Work (SOW) for SDS -Software Definable/Reconfigurable Systems: Design, Development, Support, and Integration

Vision Statement 1 Introduction

1.1 Mission

1.2 Background

1.3 Scope

2 General Requirements

2.1 Non-Personal Services

2.2 Business Relations

2.2.1 Data Rights

2.3 Contract Administration and Management

2.3.1 Contract Management

2.3.2 Personnel Administration

2.3.3 Contract Administration

2.3.4 Contractor's Management Plan (CMP)

2.3.5 Government Quality Assurance

2.4 Contractor Furnished Equipment, Materials, Subcontracts and Supplies

2.5 Facilities and Staffing

2.6 Location and Hours of Work

2.7 Travel / Temporary Duty (TDY)

2.8 Applicable Documents

2.8.1 Military/Department of Defense Specifications and Standards

2.8.2 Other Government Documents

2.8.3 Non-Government Documents

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

2.8.3.2 Institute of Electrical and Electronic Engineers (IEEE)

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

3.1 SDS Programs Systems Engineering (SE) Support

3.2 SDS Design, Implementation, and Analysis

3.3 SDS System/Subsystem Fabrication and Assembly

3.4 SDS Payload Systems Information Assurance

3.5 RF Chamber Support

3.6 SDS Parts Engineering and Management Support

3.7 SSDD Programs/Projects Special Reporting

4 Special Requirements

4.1 Security

4.1.1 DD Forms 254

5 Deliverables

Statement of Work (SOW) SDS -Software Definable/Reconfigurable Systems: Design, Development, Support, and Integration

Vision Statement

To develop Software Definable/Reconfigurable Systems that respond to Navy, Department of Defense (DoD), and National mission requirements with improved performance, capability, reliability, efficiency, and life cycle cost.

1 Introduction The Naval Center for Space Technology (NCST), an organization within the U.S. Naval Research Laboratory (NRL) in Washington, DC, is the designated lead for Navy Space Programs. NCST has the mission to preserve and enhance a strong space technology base and provide expert capabilities in the development and acquisition of space, aerospace, and tactical Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) systems which support Naval Missions.

The Space Systems Development Department (SSDD), a department within NCST, has the primary responsibility to develop space, aerospace, and tactical C4ISR systems, and to evolve the emerging technologies that advance the capabilities of these systems to perform science and operational missions. The SSDD develops and advances technologies, defines mission needs, defines concepts of operations, defines system requirements based on mission needs, develops system architectures, designs and develops systems and subsystems based on mission needs, demonstrate their capabilities, and transition these systems to operational use. SSDD presently has programs at various stages of development and transition. In addition, 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.

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, aerospace, aviation, underwater, 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.

This work statement involves Systems Development, Support and Integration (SDSI) for Software Definable/Reconfigurable Systems (SDS) Design tasking required in support of the SSDD technology advancements, system requirements definition, architecture development, and the system and unit design, development and transition to operational use. Recent and current NRL SDS Programs include the Software Reconfigurable Payload (SRP), Furious Mercury, Rader-M, and others. These programs represent a core technology for the creation of radio transceivers/software defined payloads that are smaller, lighter and more flexible tactical systems. Advanced waveform development and porting, advanced receiver design and implementation, as well as communications security and Information Assurance (IA) functions are required.

1.3 Scope

The purpose of this contract is to provide personnel, facilities, and manufacturing capability in support of the tasks delineated in Section 3, Performance Requirements identified below. The effort will be conducted in coordination with Principal Investigator (PI) led 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/project.

3.1 SDS Programs Systems Engineering (SE) Support

3.2 SDS Design, Implementation, and Analysis

3.3 SDS System/Subsystem Fabrication and Assembly

3.4 RF Chamber Support

3.5 SDS Parts Engineering and Management Support

3.6 SSDD Programs/Projects Special Reporting

2 General Requirements The Contractor shall have its support team in place and fully functioning within 90 days of contract award and issuance of the initial task order.

During this period the contractor will transition all activities from the incumbent, as required. The Contractor must execute the scope of work in a manner that provides for high quality, timely services while incorporating the proper mix and the most effective use of personnel.

2.1 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 (CO) if any Government requested actions constitute, or are perceived to constitute personal services.

2.2 Business Relations

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

2.2.1 Data Rights

Government Data right clauses are included in Section I DFARS 252.227-7013 Rights in Technical Data --Noncommercial Items (MAY 2013), DFARS 252.227-7014 Rights in Noncommercial Computer Software And Noncommercial Computer Software Documentation (MAY 2013), and DFARS 252.227- 7019 Validation of Asserted Restrictions --Computer Software (SEP 2011 ).

2.3 Contract Administration and Management

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

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

2.3.2 Personnel Administration

The Contractor shall assign a single point of contact, also known as the Program Manager (PM), who must work closely with the government Contracting Officer and Contracting Officers Representative (COR), Technical Program Manager, as set forth with each task order.

The contractor PM must ultimately be responsible for ensuring that the contractor’s performance meets all government contracting requirements within cost and schedule. PM must have the requisite authority for full control over all company resources necessary for contract performance. As appropriate, the role of PM is a full time management position.

The Contractor shall maintain the adequacy of their employees by providing initial and refresher training to meet the SOW requirements.

The Contractor shall make necessary travel arrangements for employees.

2.3.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.3.4 Contractor's Management Plan (CMP) [A001]

The Contractor must submit a Contractor's Management Plan (CMP) defining the contractor's approach to implementing the contract. 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, and subcontract management.

A draft CMP must be delivered with the contractor's proposal with a detailed narrative demonstrating how:

• The Contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this SOW.

• The Contractor shall develop and maintain an effective risk management program to ensure services are performed in accordance with this SOW.

• The Contractor shall develop and maintain an effective systems engineering program to ensure services are performed in accordance with this SOW.

• The Contractor shall develop and maintain an effective software development program to ensure services are performed in accordance with this SOW.

• The Contractor shall develop and maintain an effective configuration management program to ensure services are performed in accordance with this SOW.

• The Contractor shall develop and maintain an effective subcontract management program to ensure services are performed in accordance with this SOW.

• The Contractor shall develop and maintain an effective Integrated Master Schedule (IMS) and Contract Work Breakdown Structure (CWBS) to ensure services are performed in accordance with this SOW.

Deliverables A001 Contractor's Management Plan (CMP)

2.3.5 Government Quality Assurance

The Government will evaluate contractor’s performance under this contract by review and acceptance of applicable progress and technical reports.

2.4 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 Task Orders issued.

• 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.5 Facilities and Staffing

2.5.1 Thermal Vacuum Testing

• 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 Celsius; with minimum dimensions of 45 inches by 36 inches by 24 inches.

• The Contractor shall provide non-vacuum testing facilities for providing temperature cycling of systems and subsystems from -50 to 100 degrees Celsius with minimum dimensions of 45 x 36 x 24 inches.

• The Contractor shall provide facilities for automated surface mount printed circuit board (PCB) assembly using pick-and-place and other technology.

• The Contractor shall provide facilities/capability for PCB assembly and finishing to include a multi-zone reflow oven, water bath cleaning capability and others.

• The contractor shall provide facilities/capability for X-ray analysis of bare an assembled PCB for quality assurance purposes.

2.5.2 Surface Mount Technology

• The Contractor shall provide in-house capability or capability within 60 minutes of the primary design engineers for detailed, complex, surface mount technology assembly.

• The Contractor shall provide assembly facilities of capabilities for modern SMT devices with components as small as 0201 package with fine-pitch components as small as 15mil or smaller.

• The Contractor shall provide SMT fabrications shop for turnkey working with the board layout team and generating all necessary additional intermediate components such as stencils, solder mix-ups, kiting and loading of components.

• The Contractor shall provide SMT assembly facilities of capabilities for supporting single or dual sided placement, complex, fine-pitch ball-grid-array (BGA), and pick-and-place machines.

• The Contractor shall provide soldering facilities of capabilities for a multi-zone reflow oven or wave soldering, as required for installation.

• The Contractor shall provide an X-Ray machine with BGA analysis software for verification of installation of large ball grid arrays.

• The Contractor shall provide a limited-access secure facility IAW DoD security requirements and proper ESD protection operations for proper tracking of the assembly process.

• The Contractor shall provide conformal coating in dip, manual, and aerosol methods with silicon and urethane for SDS system protection.

2.5.3 Wiring Harness / Components and Cables

• The Contractor shall provide in-house capability or capability within 60 minutes of the primary design engineers for wiring harness build-up.

• The Contractor shall maintain tooling to support a wide variety of common MIL connector, contacts, and sockets for SDS payload prototype.

• The Contractor shall maintain stock of general wire types for the aerospace industry.

• The Contractor shall provide wire-harness assembly fixtures for accurate harness building.

• The Contractor shall provide varying wire sizes for supplying 28 AWG to 8 AWG wires.

• The Contractor shall provide specialized wire types such as variety of coaxial RF cables, twisted pair, shielded cable, EMI/ESD wraps on harnesses and braiding as required, for assembly of SDS system payloads.

• The Contract shall provide facilities support for building of a flex circuit wiring harness, as required, for a flex circuit wiring harness as required.

• The Contractor shall provide specialized wire types such as variety of coaxial RF cables, twisted pair, shielded cable, EMI/ESD wraps on harnesses and braiding as required.

• The Contract shall demonstrate capability to support the building of a flex circuit wiring harness, as required, for a flex circuit wiring harness.

2.5.4 Top Level Assembly (TLA)

• The Contractor shall provide in-house capability or capability within 60 minutes of the primary design engineers for complete mechanical and electrical system or TLA assembly.

• The Contractor shall provide complete top level assembly capability for working with the mechanical shop and all others at NRL.

2.5.5 Assembly QA / Inspection / Rework

• The Contractor shall provide have in-house capability or capability within 60 minutes of the primary design engineers for assembly QA, board inspection, and board rework.

• The Contractor shall provide automated optical inspection, x-ray imaging, and other inspection means for inspection of all parts of the assembly process.

• The Contractor shall provide in-house capability for board rework.

• The Contractor shall provide modern SMT rework tools for hot-air stations, air-vac stations, micro-tweezers stations, and IR rework stations.

2.6 Location and Hours of Work

Accomplishment of the results contained in this SOW requires work at various Naval Research Laboratory facilities in the National Capital Region. Normal workdays are Monday through Friday except US Federal Holidays. NRL workers typically work eight (8) hours per day, 40 hours per week.

Flextime workers start not earlier than 0600 and not later than 1000. Core hours of work are from 1000- 1100 and 1300-1400 daily. All employees are expected to be available during core hours Additional information on work hours is provided in Section 1. (c), NRL HOURS OF OPERATION AND HOLIDAY SCHEDULE, in the NRL ROSC.

2.7 Travel / Temporary Duty (TDY)

Travel to other government facilities or contractor facilities may be required for conduct of experimental research, testing, or attendance at government reviews or scientific meetings and seminars.

• The Contractor shall maintain the capability to arrange the travel of contractor personnel to locations in CONUS/OCONUS often on short notice.

• The Contractor shall submit all travel (plans and dates) for pre-approval to the Government.

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

2.8 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 SOW, the requirements of this SOW apply.

2.8.1 Military/Department of Defense Specifications and Standards

Document Number Description

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

MIL-HDBK-217F(2) Reliability Prediction of Electronic Equipment MIL-HDBK-454(1) General Guidelines for Electronic Equipment

MIL-PRF-31032 Specification Printed Circuit Board/Printed Wiring

Board, MIL-PRF-123 Capacitors, Fixed, Ceramic Dielectric (Temperature Stable and

MIL-PRF-55365

Capacitor, Fixed, Electrolytic (Tantalum), Chip, Non-established Reliability, Established Reliability, General Specification For

MIL-STD-461E Requirements for The Control of Electromagnetic Interference

MIL-STD-881C Work Breakdown Structures for Defense Material Items

MIL-STD-981 Design, Manufacturing and Quality Standards for Custom

MIL-STD-1540D Product Verification Requirements for Launch, Upper Stage, MIL-T-31000 General Specification for Technical Data Packages

TOR-2004 (3909)-3537-REV B

Software Development Standard for Space Systems MIL-STD-973 Configuration Management Depart of Defense Instruction 8500.2

Information Assurance (IA) Implementation

Depart of Defense Instruction 8551.1

Ports, Protocols, and Services Management (PPSM)

Department of Defense Instruction 8510.01

Risk Management Framework (RMF)

Description Version

NRL Occupational Safety and Health Manual, 5100.13C

NRL Security Manual Manual, 5510.40D

Description Version

JTRS Software Communications Architecture Specification

Version 2.2.2, 15 May 2006

JTRS Software Communications Architecture Extensions

Version 2.2.2, 22 December 2006

JPEO JTRS Standards Standardization Plan

Version 1.8, 30 April 2008

JPEO JTRS Software Standards Version 1.2.2, 01 October 2007

JTRS Unified INFOSEC Criteria Revision 2, 02 December 2005

(SECRET//NOFORN)

REDHAWK Documents Version 1.7.5 or later

2.8.2 Other Government Documents

Document Number Description

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

NASA-STD-8739.4 Crimping, Interconnection Cables, Harnesses and Wiring NASA EEE-INST-002 Instructions for EEE Parts Selection, Screening Qualification and Derating

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.8.3 Non-Government Documents

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

Document Number Description GEIA-STD-0007A Logistics Product Data EIA/IS-632 Systems Engineering EIA/IS-649 Configuration Management

(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.8.3.2 Institute of Electrical and Electronic Engineers (IEEE)

Document Number

Description

IEEE/EIA

12207.0, Standard for Information Technology – Software life cycle processes March 1998

IEEE/EIA

12207.2, Standard for Information Technology – Software life cycle processes – Implementation considerations April 1998

IEEE STD 1000.13,

POSIX Real-time Application Environment Profile (AEP)

2.8.3.3 International Organization for Standardization (ISO) Standards

Document Number

Description

AS9100, Rev C Aerospace Quality Management Systems ISO 9001:2000 Quality Management Systems – Requirements

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 SDS Programs Systems Engineering (SE) Support

Systems Engineering (SE) support involves all aspects of the SDS Payload Design and Development using engineering processes and program management to bring sponsor articulated requirements through the design process and to a manifestation that meets the majority of the requirements.

The specifications for SDS payload for the system being developed may be derived from a wide variety of sources (such as the specs listed in "Section 2.9 Applicable Documents and sponsors operational needs) and encompass the entire SDS payload ultimate performance, physical form factor, security, and other factors.

The requirements to meet this SDS Programs System Engineering (SE) Support are (3.1.1) General Process and Planning, (3.1.2) SDS Projects Programmatic and Technical Reviews and Audits, and (3.1.3) SDS programs/projects configuration control of classified and unclassified documents, all of which include explicit, implicit, and derived system security requirements as properly articulated and accounted for.

Content and delivery media (CD, Flash drive, hard copy, as attachment to the technical report, or another) of technical data, as required, will be defined at as needed.

Deliverables A004 Technical Documentations/Reports and Data

3.1.1 General Engineering Process and Planning

General engineering and planning support involves all program level efforts such as program management and technical planning for designing the SDS system payload, general engineering and planning based on sponsors requirements.

Achieving the program goals means achieving the requirements listed in sections 3.1.1.1 through 3.1.1.5.

SDS payload engineering process is iterative and involves other parts of the systems engineering processes and interaction with the other project partners either government or other contractors.

3.1.1.1 The Contractor shall develop a systems engineering management plan (SEMP) and associated technical documentation as required for the assigned SDS program.

The SEMP describes the contractors proposed efforts for planning, controlling, and conducting a fully integrated engineering effort. The Plan is used to understand and evaluate the contractors engineering work efforts as part of the contract monitoring.

Deliverables A011 Program Documentation

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

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

3.1.1.3 The Contractor shall perform decomposition and allocation of high-level requirements into lower-level and derived requirements for SDS payload design and development.

3.1.1.4 The Contractor shall perform trade-space analysis for all parts of engineering process for SDS payload systems/subsystems.

3.1.1.5 The Contractor shall provide logistical support for SDS payload software and hardware development and system RMA.

3.1.2 SDS Projects Programmatic and Technical Reviews and Audits In the following paragraphs, conducting/attending reviews means organizing the meetings, active participation in the discussions, and preparing technical/programmatic data package for required technical/programmatic reviews and audits, as required. These reviews may involve external/internal dependencies, such as interfacing with platform provider, NRL SDS team, SDS customer, and sponsoring organization. These reviews cover all aspects of the project, design and development activity, as required.

Representative reviews are systems requirements reviews (SRR), preliminary design reviews (PDR), critical design reviews (CDR), Test Readiness Reviews (TRR). The specific reviews that occur depend on the phase of development the program or project is in e.g. concept development, engineering development, or test and evaluation.

Design data includes:

• Technical Reports - system analysis reports, system requirements allocation reports, system test reports, and document lists

• Programmatic Reports - risk mitigation/management plans, integrated master schedules, program execution plan, programmatic budgets, and other tools to be used by the program managers.

Specification Trees - preparation and maintenance of all specification trees related to the program

• Parts Lists - all system parts lists.

• Design Review Reports - system design review results, action item assignments, action item resolutions and First Article Configuration Inspection (FACI) results.

• Level two technical data package that includes drawings, procedures, materials and process documents, system drawings, lists that define a specific system, subsystem or unit design, and other artifacts as required

• Parts Program Documents

• Quality Assurance Documents

• Manufacturing Documents

• Test Methods and Control Documents

Deliverables

A011 Program Documentation

3.1.2.1 The Contractor shall execute technical program management reviews for the SDS payload design and development for the assigned program.

3.1.2.2 The Contractor shall conduct and participate-in system level program reviews as required for the SDS payload design and development for the assigned program.

3.1.2.3 The Contractor shall conduct and attend the NRL systems engineering reviews as required for the SDS payload system, subsystem, and component level design.

3.1.2.4 The Contractor shall conduct and attend integration meetings and reviews with the host vehicle provider and their contractor partners for evaluating and incorporating all of the technical information necessary to support evolving software and hardware integration efforts.

3.1.2.5 The Contractor shall conduct Technical Interchange Meetings (TIM) as necessary for SDS programs/projects assigned.

3.1.3 The Contractor shall manage configuration control of classified and unclassified documents for SDS programs/projects.

Management functions include performance of: hardware and software configuration item updates, configuration change management, configuration status accounting, configuration audits and verification, and CM planning and management.

3.2 SDS Design, Implementation, and Analysis

The minimum requirements are set forth in sections addressing (3.2.1) RF waveform and SW development for reprogramming SDS payloads, (3.2.2) design, development, integration, and operation of infrastructure SW and firmware for integration, (3.2.3) SDS system/subsystem development, (3.2.4) characterization of systems designed, (3.2.5) technical assessment and engineering analyses, (3.2.6) application development, (3.2.7) pre/mission, mission, post-mission performance analysis, (3.2.8) payload HW engineering, (3.2.9) SW systems engineering, (3.2.10) packaging design engineering, (3.2.11) SW and HW subsystem integration and packaging, and (3.2.12) design improvement. All processes are iterative and involves other parts of the SDS Design and implementation process and other project partners either government or other contractors.

A003 Technical Documentations/Reports and Data

3.2.1 The Contractor shall develop RF waveform and software for reprogramming the space/aerospace payloads for new missions as required by NRL.

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.

Deliverables A004 Software, Algorithms, Executable Programs and Source Code, and Documentation and Instructions A011 Program Documentation

3.2.2 The Contractor shall design, develop, integrate, and operate infrastructure software and firmware for integration of the equipment into mobile ground, space, and naval 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.

Deliverables A005 Software, Algorithms, Executable Programs and Source Code, and Documentation and Instructions A011 Program Documentation

3.2.3 SDS System/Subsystem Development

The Contractor must develop subsystems for SDS payload.

Subsystem development includes design decomposition, and design interface definition development.

3.2.3.1 The Contractor shall decompose subsystem requirements into lower level requirements for development of software.

3.2.3.2 The Contractor shall define and design interfaces between hardware and software systems as requested for the SDS subsystems at the board or lowest subsystem level for SDS HW integration.

These interfaces may be analog, RF, digital or mixed signal interfaces, and may operate at power levels at DC to 300 GHz. Interface design may involve utilizing HW or designs generated by other program team members, whether government or contractor.

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

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

Deliverables A011 Program Documentation

3.2.5 The Contractor shall perform technical assessments and engineering analyses for SDS 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.

Deliverables A005 Software, Algorithms, Executable Programs and Source Code, and Documentation and Instructions

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

System applications to be evaluated will be assigned by task 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.

3.2.7 The Contractor shall conduct pre-mission, mission, and post-mission systems performance analyses for SDS based space, aviation, surface, ground or underwater experiments, and operations.

The work to be performed include 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.

A011 Program Documentation

3.2.8 Payload Hardware Engineering

The Contractor must perform hardware engineering required to produce prototype SDS systems for laboratory and field-testing.

The minimum requirements to achieve the HW development are HW Design Decomposition, Design and development of HW interfaces, and HW Configuration Management.

3.2.8.1 The Contractor shall convert the subsystem requirements allocated to hardware to the next level of detail for prefabrication.

Examples of next level are down the logic device, transistor, resistor, or other component levels. For RF and high-speed digital design, this design decomposition may involve performance analysis of the subsystem. These types of analysis may include RF gain, noise performance, spur analysis, phase noise analysis, jitter, and others. Digital design and mixed signal design may involve other analysis tools (e.g., SPICE and others).

3.2.8.2 The Contractor shall perform analysis of the resulting detailed layout in both the analog/RF and digital domains at the completion of the subsystem design process for SDS payload system and subsystem HW verification and validation.

Analysis may involve digital energetic analysis such as those provided by Hyperlinx, analog RF analysis such as provided by Microwave Office or EM/SYS or other performance verification and validation tools necessary to help improve the RMA of board meeting its performance requirements.

Deliverables A005 Software, Algorithms, Executable Programs and Source Code, and Documentation and Instructions A006 Test and Analysis Report(s)

3.2.8.3 The Contractor shall provide and maintain hardware configuration management process for SDS payload development.

Deliverables A005 Software, Algorithms, Executable Programs and Source Code, and Documentation and Instructions

3.2.9 Software Systems Engineering

It is expected that the Contractor's software development processes meet the intent of ISO IEC 12207- 2008(E), Standards for Information Technology - Software life cycle processes, which provides guidance on performing life cycle support for software that is part of a larger systems, as well as, stand-alone software products and services; however, compliance to this standard is not mandatory.

3.2.9.1 The Contractor shall generate and update subsystem software development specifications for SDS programs/projects.

ISO IEC 12207-2008(E), Standard for Information Technology - Software life cycle processes provides guidance on performing life cycle support for software that is part of a larger system, as well as, stand-alone software products and services.

3.2.9.2 The Contractor shall decompose the allocated software subsystem requirements for defining the next level of SW details.

Next level may include down the logical software blocks. Performing this task may involve utilizing component level data sheets and manuals to support the design of the subsystem at this level of detail, operating system information, operating environment interfaces, SCA and REDHAWK documentation, and other data such as security requirements to assist in this process. The design decomposition may include analysis to ensure the performance of the subsystem by determining corresponding data throughput, processing speed in operations per second, security analysis on the design, and others.

3.2.9.3 The Contractor shall develop software for interfacing SDS payload to the systems/subsystems external to the payload.

These interfaces may involve socket, TC/IP, and UDP library calls, CORBA IDL interfaces, XML standards for the passing of data, service-oriented-architecture (SOA) interfaces, standard socket-based interfaces, and others.

Deliverables A005 Software, Algorithms, Executable Programs and Source Code, and Documentation and Instructions

3.2.9.4 The Contractor shall develop software for implementing the SDS payload in accordance with the requirements delegated to software in SDS system/subsystem development above.

Software may be in VHDL, Verilog, C, C++, JavaScript, OpenCPI, OpenCL, CUDA, or JAVA.

VHDL/Verilog may be used for any system developed to be installed on hardware such as Field Programmable Gate Array (FPGA). Other languages are suitable for other systematic efforts include scripting languages such as BASH, PERL, and PYTHON.

Software systems may be written with a makefile construct to include both the compilation of the code as well as running verification tests for that software module.

Deliverables A005 Software, Algorithms, Executable Programs and Source Code, and Documentation and Instructions

3.2.9.5 The Contractor shall conduct performance evaluation for assessing the performance of the SW implemented for the SDS payload.

Certain firmware requirements may need to be written in other languages such as assembly code or even limited microcode/machine code.

Deliverables A006 Test and Analysis Report(s)

3.2.9.6 The Contractor shall conduct unit level testing of the SW for SDS system/subsystems.

Unit-level testing is for any SW function and subroutine developed under the SDS program for any high level programming language.

Deliverables A006 Test and Analysis Report(s)

3.2.9.7 The Contractor shall develop and provide test benches for any software developed in any hardware programming languages for SW verification/testing.

A test bench is a template of inputs and expected outputs and the software harness to hold it together.

Deliverables A005 Software, Algorithms, Executable Programs and Source Code, and Documentation and Instructions A006 Test and Analysis Report(s)

3.2.9.8 The Contractor shall provide and maintain software configuration management system for SDS payload development.

3.2.9.9 The Contractor shall conduct performance evaluation for verification and validation of the SW developed under this effort.

This subpart applies to external and internal SW including interfaces/protocols developed for operation of the entire SDS payload.

Deliverables A006 Test and Analysis Report(s)

3.2.9.10 The Contractor shall perform mean time failure analyses for assessing the RMA performance of software developed for the SDS payload systems and sub-systems for quality assurance.

Software reliability is typically measured in mean-time-between-failure (MTBF). In the SDS effort, the focus of RMA testing will be on features tests, to ensure that the feature set desired is meeting its requirements, as well as regression testing, ensuring that previous functionality continues to work as intended. Loading testing will occur as well, as required.

A006 Test and Analysis Report(s)

3.2.10 Packaging Design Engineering

This subparagraph involves packaging design engineering as specified below for implementing electronic devices assigned in task 3.1 above. Packaging engineering refers to design, analysis, and manufacturing of the sub-system and system level packaging for the operating environment, physical connections, and mounting in accordance with the SDS payload platform packaging requirements. Packaging involves thermal management, tamper protection / security requirements, and mechanical performance/vibration resistance, as addressed in the subtasks below.

Deliverables A006 Test and Analysis Report(s)

3.2.10.1 The Contractor shall verify that EMI/EMC requirements of MIL-STD-461E are met for electronic package designs.

3.2.10.2 The Contractor shall conduct analysis of structures, housings, and printed wiring board (PWB) designs for evaluating electronic/optical packaging designs conformance with NRL dynamic environment design margins.

3.2.10.3 The Contractor shall assembly contamination sensitive technology systems and assemblies for evaluation of electronic packaging designs conformance with NRL thermal environment design margins.

Assembles may require to be in accordance with 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.

3.2.10.4 The Contractor shall design, manufacture, and analyze the SDS sub-system and system level packaging in accordance with thermal requirements for operating in a variety of challenging environments.

Thermal management systems may include forced air cooling at ambient or conditioned air temperatures, chilled water/fluid baseplate in a conduction cooling atmosphere, and others.

3.2.10.5 The Contractor shall design, manufacture, and analyze the SDS sub-system and system level packaging in accordance with thermal requirements for physical security.

Physical security requirements may involve tamper protection and others as required and in accordance with COMSEC, classification level, and others service-imposed standards as required.

3.2.10.6 The Contractor shall design, manufacture, and analyze the SDS sub-system and system level packaging for operating in various vibrational environments.

3.2.11 Software and Hardware Subsystem Integration and Packaging

This section involves integration and packaging of the hardware developed in 3.2.8 and the software developed in 3.2.9 with packaging designed and tested in 3.2.9 for SDS payload prototype development.

Deliverables A006 Test and Analysis Report(s)

3.2.11.1 The Contractor shall develop test fixtures, SW, HW, and harnesses for validating the SDS prototype operation.

In this particular task, test fixtures refer to hardware devices as well as software interfaces that are utilized in testing the end-to-end system SDS payload prototype. One example of a test fixture may be a "test rack that is utilized in stimulating the RF transmissions, receiving the stimulation, and generating automated test reports.

3.2.11.2 The Contractor shall maintain configuration management for the SDS payload prototype HW/SW system(s) developed under this effort.

3.2.11.3 The Contractor shall perform integration and packaging of the hardware developed in 3.2.8 and the software developed in 3.2.9 by utilizing the results of subtasks

3.2.10 for SDS payload prototype development.

3.2.12 Design Improvement

Deliverables A006 Test and Analysis Report(s)

3.2.12.1 The Contractor shall evaluate and document the performance of the SDS system/subsystems/components developed in accordance with the analytical methods as required for determining design improvement options.

Documentation includes lessons learned such as what worked, what did not work, and areas of improvements for the entire system/subsystem/components, and payload assembly and integration.

3.2.12.2 The Contractor shall provide mitigation and improvement options based on trade space analysis and lessons learned for SDS payload prototype system/subsystem/components.

3.2.12.3 The Contractor shall implement and execute the mitigation and improvement options approved by COR for the SDS payload prototype modifications.

3.3 SDS System/Subsystem Fabrication and Assembly

Fabrication and assembly involves all parts of fabrication and assembly of software defined systems.

Deliverables A009 Other Data Deliverables

3.3.1 Material Acquisition and Control

Material acquisition and control means acquiring components in accordance with supply chain management practices for the construction of SDS hardware configuration items and control of those parts. Supply chain management involves working with SDS payload design and test engineers to ensure that the items to be purchased as custom-made or manufactured for the SDS project are delivered in accordance with the schedules as approved.

This subtask includes parts engineering, inventory and lot management, and parts quality assurance engineering.

3.3.1.1 The Contractor shall procure the parts as required for constructing the SDS payload system/subsystem/components through its purchasing department in accordance with the system design requirements as approved.

This subtask includes purchasing all parts and components, as required and approved by COR, for fabricating and assembling SDS payload system/subsystems/components and apparatus, interfaces, flight harnesses, integration, bench/component/field testing, and others. The involved parts may include specialized material, HW, printed wiring boards, fabricated items, and chassis.

3.3.1.2 The Contractor shall provide kitting, packaging, and shipment of individual material items and material lots for delivery to other entities as directed by the COR.

3.3.1.3 The Contractor shall provide inventory and lot management for the SDS parts and fabrication components.

Inventory and lot management involves maintaining the storage of on-hand components, tracking the lots of critical components, providing an inventory of the available parts in-stock at any point within the program, and working with the fabrication shop for kitting assemblies from component stock.

3.3.1.4 The Contractor shall conduct quality assurance (QA) engineering and management on the parts acquired/procured and received, materials, and parts and components for SDS payload implementation materiel.

Parts QA process includes verifying that components are not damaged during shipping and handling and ensuring that the proper quantities, packages, and part numbers are received. This may involve coordination and working with the cognizant design engineer to ensure that the proper QA processes are put in place at the time of the purchasing effort and that the process is ready to execute when the parts or material arrive.

Some fabricated components may need additional QA processes applied; PCBs and other components may need X-ray inspection to verify that they were manufactured appropriately. Mechanical pieces may need inspection or testing to ensure that they meet the coating, material or tolerance requirements.

3.3.2 Fabrication and Assembly

Fabrication and assembly operations include operation of automated pick-and-place, surface mount technology (SMT) assembly; ball grid array (BGA) assembly; column grid array (CGA) assembly for space, aviation, surface, ground, or underwater environments; and real time radiographic inspection capabilities for the inspection of parts, printed wiring boards (PWBs) and completed assemblies.

3.3.2.1 The Contractor shall fabricate, assemble, and deliver qualified (as required) hardware and software for use in SDS based SSDD space, aviation, surface, ground, or underwater systems.

3.3.2.2 The Contractor shall provide configuration control and document fabrication and assembly processes for producing SSDD space and aerospace C4ISR systems.

3.3.3 Verification Testing

Test activities include: development testing (DT) including Limited User Evaluations (LUE) ; design verification testing (DVT); Qualification Testing; and Acceptance Testing at the part, software, hardware module, subassembly, unit and system levels.

Deliverables A011 Program Documentation

3.3.3.1 The Contractor shall conduct and develop test and verification programs for Contractor developed SDS based systems/subsystems/elements.

Test activities include: development testing (DT) including Limited User Evaluations (LUE) ; design verification testing (DVT); Qualification Testing; and Acceptance Testing at the part, software, hardware module, subassembly, unit and system levels.

3.3.4 SDS/Platform Integration and Installation Engineering Support

This paragraph involves services for integration and installation of the SDS systems for testing in host platforms.

Deliverables A011 Program Documentation

3.3.4.1 The Contractor shall develop and implement a product verification test process for SDS communications payloads intended for use in SDS based space, aviation, surface, ground, or underwater systems.

Deliverables A006 Test and Analysis Report(s)

3.3.4.2 The Contractor shall develop, design,…