Attachment 2 - SOW.doc

STATEMENT OF WORK (SOW)

Optical and RF Payloads: Systems Design, Development, Support and Integration Vision Statement To develop sensors, payloads and 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 Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) systems which support Naval Missions.

In support of this mission, the Space Systems Development Division (SSDD), a division within NCST, has the primary responsibility to develop space, aerospace and 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 and system requirements based on mission needs, develops system architectures, designs and develops systems and subsystems, demonstrates their capabilities and transitions 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.

The objective of this Statement of Work (SOW) is to define the space, aerospace, and terrestrial optical and RF payload Systems Development, Support and Integration (SDSI) tasking required in support of the SSDD technology advancements. This is to include systems requirements definition, architectures development, and the systems and units design, development and transition to operational use.

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 support the breadth of the SSDD missions. This includes, but is not limited to, support for system requirements definition, architecture development, advanced modeling and simulation, system and unit design, and development and transition of hardware and software to operational use. Recent and current SSDD Programs include free-space optical communications, the FH and Rough Rider programs, maritime domain awareness programs, small-sat concept development, and others. These programs are representative of some of the small, but potentially high impact SSDD programs.

1.3. Scope of Work

The scope of this statement of work includes required support in the areas of (1) Contract and Program Management, (2) Documentation, (3) Systems Engineering, (4) Systems Design and Development, (5) Systems Effectiveness, (6) Parts Procurement and Processing, (7) Fabrication and (8) Test and Verification.

The SDSI Contractor shall provide all personnel, resources and materials necessary to provide the support required. The Contractor shall not incorporate proprietary hardware or software in any deliverable developed under this contract unless authorized, in writing, by the Contracting Officer. Some of the tasking under the effort will be required to be performed at the Sensitive Compartmented Information (SCI) Level.

2. General Requirements

The Contractor shall have its support team in place and fully functioning within 60 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.

The Contractor’s Program Manager shall be responsible for scheduling, coordinating, and executing any necessary transition activities and immediately notifying the COR if issues arise precluding effective transitioning.

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 Procuring Contracting Officer (PCO) 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 (Feb 2014), DFARS 252.227-7014 Rights in Noncommercial Computer Software And Noncommercial Computer Software Documentation (Feb 2014), and DFARS 252.227-7019 Validation of Asserted Restrictions --Computer Software (SEP 2016).

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 PCO 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) as detailed in CDRL A001 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 is this SOW.

The Contractor shall be responsible for any subcontract management necessary for performing efforts described in SOW.

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

2.6 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.7 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 shall be used. Where a revision level is not included, the latest reference to the document from the Department of Defense Index of Specifications and Standards (DODISS) shall 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 shall apply.

2.7.1 Reserved

2.7.2 Military/Department of Defense Specifications and Standards

(https://www.esda.org)

TOR-2004 (3909)-3537-REV B REV-B,

11 March 2005 Software Development Standard for Space Systems

Unless otherwise noted, these documents can be obtained from the ASSIST Online database at https://assist.dla.mil.

2.7.3 Other Government Documents

All applicable documents can be found at: https://standards.nasa.gov/nasa-technical-standards and https://nepp.nasa.gov/index.cfm/316

2.7.4 Non-Government Documents

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

(Applications for copies should be addressed to the American Nation Standard Institute, 1430 Broadway, New York, NY 10018.) and/or (Application for copies should be addressed to Electronic Industries Association, 2001 Pennsylvania Ave., NW, Washington, DC 20006.)

2.7.4.2 Institute of Electrical and Electronic Engineers (IEEE)

(Applications for copies should be addressed to the Institute of Electrical and Electronic Engineers Inc., 345 East 47th Street, New York, NY 10017. Online IEEE standards may be obtained at http://standards.ieee.org/catalog/olis/index.html.)

2.7.4.3 International Organization for Standardization (ISO) Standards

Related documents may be found at https://www.iso.org/home.html

3 MANAGEMENT REQUIREMENTS

The Contractor shall accomplish this tasking using the requirements in this contract, supplemented by the supporting documents referenced in Section 2.0, entitled Applicable Documents.

3.1 Program Management

The Contractor shall provide the program management, control, and reporting functions necessary to manage and direct the accomplishment of the efforts required under this SOW. The Contractor’s management, design, development, production, test and quality assurance systems shall be certified to AS9100 Rev. B, Aerospace Quality Management Systems, and ISO 9001:2000, Quality Management Systems Requirements.

3.1.1 Program Manager

The Contractor shall designate a Program Manager (PM) who shall have responsibility for the SDSI Programs, and act as the primary technical point of contact with NRL for all matters pertaining to this contract. The Program Manager shall keep the COR informed of the status of the technical and management efforts and expenditures on the contract by means of written monthly reports, in accordance with CRDL A001, by telephone conversations, and by meetings at the Contractor’s facility and at NRL

3.1.2 Program Control

The Contractor shall establish and maintain a management system for control and reporting of the program and contract efforts, including cost, schedule, and technical performance, for the life of the contract. The management system shall provide the Contractor with the ability to access technical achievement, to measure progress and to determine and accrue costs accurately for all activities under the contract.

3.1.2.1 Contract Work Breakdown Structure.

The Contractor shall implement a management system structured using a Contract Work Breakdown Structure (CWBS), compliant with MIL-STD-881 and approved by the COR in accordance with CDRL A011. A direct correlation shall exist between the CWBS developed by the Contractor and the WBS employed by the SSDD for its control and reporting purposes. Revisions to the CWBS and the attendant CWBS Dictionary shall be submitted in accordance with CDRL A011.

3.1.2.2 Program Technical, Cost and Schedule Control

The Contractor shall maintain program technical, cost and schedule control of all activities under the contract. On significant tasking and/or programs, when directed by the COR, the Contractor shall implement a formal Earned Value Measurement System (EVMS) that fully complies with the EVMS guidelines of ANSI/EIA Standard 748-98, Earned Value Management Systems. The Contractor shall employ this EVMS to measure the actual cost and schedule of accomplishments and compare these to the planned cost and schedule baseline to determine variances in cost and schedule from the established baseline. The Contractor shall employ these measurements to evaluate and report earned value and variances, and to enact/recommend measures to resolve any significant variances. The Contractor shall submit a monthly EVMS Report in accordance with CDRL A001 on those programs directed by the COR.

On significant tasking and/or programs, when directed by the COR, the Contractor shall also implement a formal risk management system (RMS) with which the Contractor shall continually assess technical, cost and schedule risk and implement/recommend and report on measures planned and implemented to mitigate high and medium risks.

3.1.2.3 Project Plans/Schedules

The Contractor shall generate and maintain schedules for each task assignment in an appropriately designated scheduling format. The Contractor shall ensure that adequate resources are assigned to the tasks to be accomplished, and shall report on any deficiencies. These schedules shall be submitted under CDRL A002, Schedules.

The Contractor shall also generate, update and maintain program schedules for ongoing SSDD space/aerospace systems development programs in accordance with CDRL A002, Schedules. This task shall include the integration of all subsystem schedules into a master program schedule, and verification of schedule compatibility with the master development schedule. The program schedules shall consist of a master schedule, separate subsystem schedules, and a test and integration schedule for use by the SSDD. The Contractor shall revise and submit schedules on a quarterly basis. More frequent submissions may be required by the COR if the program progress or risk dictates.

3.1.3 Monthly Status Reporting

The Contractor shall provide SSDD with a Monthly Status Report (MSR) in accordance with CDRL A001. Additionally, the contractor shall provide a report of the monthly on-site labor hours in accordance with CDRL A012. The following paragraphs define the information that the Contractor shall include in the MSR. The MSR shall be submitted under CDRL A001. The Contractor shall schedule a MSR Meeting with the COR to go over the contents and format of the MSR.

On tasking and/or programs in which the Contractor implements a formal risk management system (RMS), the Contractor shall report the results and status of these systems in the MSR, including the risk assessment results and the recommended and/or implemented mitigation measures.

The Contractor shall provide highlights of actions that occurred during the reporting period relative to contract performance. Significant actions include any that will impact, or have impacted, the projected performance, cost or schedule of the SDSI Contract efforts.

The Contractor shall provide information on deliveries, meetings and on schedules versus actual work performed. Actual and projected slippages and ahead of schedule accomplishments shall be reported along with their actual and projected impact on overall contract performance.

The Contractor shall report on the status of all materials, Government Furnished Equipment (GFE), data items and travel. The Contractor shall include an update of any previously reported unresolved issues. The Contractor shall maintain an accurate inventory of all GFE in accordance with the Federal Acquisition Regulation Part 45. A complete listing describing all GFE and its location shall be prepared and made available to the COR on an as needed basis.

The Contractor shall also provide a monthly total of all on-site/off-site labor hours (which shall include subcontractor labor hours) broken down by task assignment.

3.1.4 Financial Reporting

The contract financial status shall be reported monthly in accordance with Department of Defense (DoD) Data Item Description (DID), DI-F-6010A, Cost/Schedule Status Report (C/SSR), tailored to the SSDD requirements to include current month, as well as cumulative month cost data in accordance with CDRL A001. The cost data shall be correlated to the CWBS elements. A narrative explanation shall accompany the charts. The Contractor shall provide SSDD with a Contract Funding Status Report (CFSR) monthly with the C/SSR. The C/SSR and CFSR shall be submitted as part of the Monthly Status Report. The Contractor shall also provide more detailed financial and staffing level information on individual tasks and programs when requested by the COR.

3.1.5 Security and Safety Compliance

The Contractor shall comply with the NRL Occupational Safety and Health Manual, 5100.13C, and the NRL Security Manual, 5510.40D with respect to all Contractor employees located at NRL. The Contractor shall assist SSDD in its on-going safety program, which entails taking a proactive approach towards providing a safe and healthy workplace. The Contractor shall provide expertise and support with respect to: compliance with Government safety provisions, on-site identification and elimination of safety and environmental hazards, facilitating the correction of safety and environmental deficiencies reported by building monitors and/or identified during the annual NRL Safety and Environmental Inspection(s), and to otherwise provide supplementary safety training and educational support, as needed.

4 DOCUMENTATION REQUIREMENTS

The Contractor shall provide the personnel, equipment and facility necessary to perform the documentation efforts required that includes support in the following areas: (a) generating and preparing program planning documents and briefings, (b) performing configuration management functions, (c) performing data management functions, (d) generating technical documentation, and (e) documentation review and evaluation.

The documentation provided under this task shall be compatible with Microsoft Office and Adobe Products. All documentation developed under this contract shall be delivered specified in the CDRL and SHALL NOT contain any proprietary markings.

4.1 Program Plans and Briefings

The Contractor shall assist the COR in generating program plans and briefings on assigned programs.

(a) Program Planning Documents - The Contractor shall generate and update program plans and generate and provide updates to other SSDD planning documents which may include, but may not be limited to, program implementation, system development, and test plans for existing and new space/aerospace programs, in accordance with CDRL A003, Program Documentation.

(b) Program Briefings - The Contractor shall prepare program status and technical briefings for the SSDD in accordance with CDRL A003, Program Documentation.

4.2 Configuration Management

The Contractor shall maintain configuration control of both the classified and unclassified SSDD space/aerospace programs in accordance with EIA/IS-649, entitled Configuration Management. The work required includes: (a) establishing hardware and software configuration items, (b) performing configuration change management, (c) performing configuration status accounting, (d) performing configuration audits and verification, and (e) performing CM planning and management.

4.3 Data Management

The Contractor shall ensure that deliverable data items are delivered in accordance with the schedule, that the items are tracked as they are being reviewed and that the proper approvals are received for each deliverable in accordance with its applicable CDRL. The Contractor shall also employ an automated system to organize, catalog, distribute, control and store documents and drawings. As part of this effort, the Contractor shall provide status reports on drawings and conduct regular periodic inventories to ascertain item availability, legibility and reproducibility in accordance with CDRL A001. All files shall be backed up to ensure document retention in event of equipment failure.

4.4 Technical Documentation

The Contractor shall generate technical documentation for assigned required support which includes: (a) system development specifications, (b) interface control documents, (c) system schedules, (d) system test documentation, (e) subsystem/equipment type B2 specifications, (f) general subsystem development specification and contents, (g) subsystem software development specifications, and (h) other system technical documentation. This technical documentation shall be submitted in accordance with CDRL A004, Technical Documentation.

(a) System Development Specifications - The Contractor shall maintain and update the existing system development specifications for various SSDD space/aerospace development programs. These specifications define the system level performance requirements and verification methods. The Contractor shall revise these specifications to reflect requirements/verification changes as the systems evolve. All specification revisions shall be approved through the SSDD system design process.

(b) Interface Control Documents - The Contractor shall develop, update and maintain internal and external Interface Control Documents (ICDs) which specify interface requirements for SSDD space/aerospace systems. The required documents shall reflect the results of applicable design reviews. The Contractor shall also develop, update and maintain the Interface Wire Lists (IWL) for individual systems to enable integration and test planning and performance. The IWLs shall define the interconnections of subsystems/equipment with each other as well as with other systems. The IWLs shall be referenced to the ICDs to assure conformance with specification requirements.

(c) System Test Documentation - The Contractor shall develop, update and maintain the system test documentation required to implement approved program test plan requirements.

(d) Subsystem/Equipment Specifications - The Contractor shall update the existing subsystem/equipment specifications and prepare new subsystem/equipment specifications for spacecraft and aerospace/C4ISR equipment. During performance of the qualification phase design and development required support of each development program, the Contractor may be required to prepare additional lower level equipment specifications to properly identify and control equipment configuration and performance. The Contractor shall prepare these additional specifications in accordance with CDRL A003. The Contractor shall submit preliminary copies of each subsystem/equipment specification to SSDD for review and approval in accordance with the CDRL. The Contractor shall review the preliminary copies and submit final copies for COR approval. The Contractor shall update subsystem specifications after each system design review in accordance with CDRL A013.

(f) General Subsystem Development Specifications and Contents - The Contractor shall update and maintain the general specifications containing the common requirements to be used in each subsystem Type B2 specification. The Contractor shall use this document to assure that consistence or format and terminology is maintained throughout the specification generation and overall documentation effort.

(g) Subsystem Software Development Specifications - The Contractor shall update and maintain the existing subsystem software development specifications and generate new software development specifications based on program management requirements.

(h) Design Data - The Contractor shall prepare, update and maintain the design data for all designs developed under this SOW. This design data shall be submitted in accordance with CDRL A005, Design Data, and shall include:

(i) Technical Reports - which shall include, but may not be limited to, system analysis reports, system requirements allocation reports, system test reports, and document lists and similar.

(ii) Specification Trees - which shall include the preparation and maintenance of all specification trees related to the program documentation task.

(iii) Parts Lists - which shall include all system parts lists.

(iv) Design Review Reports - which shall include, but be limited to, system design review results, action item assignments, action item resolutions and First Article Configuration Inspection (FACI) results.

(v) Technical Data Packages - which shall include, but be limited to, drawings, procedures, materials and process documents, system drawings, and lists that define a specific system, subsystem or unit design. The Contractor shall generate and maintain a level two technical data package that completely describes the design as described in MIL-T-31000, General Specification for Technical Data packages.

(vi) Parts Program Documents.

(vii) Quality Assurance Documents.

(viii) Construction Documents - which shall be in accordance with SSD D manufacturing procedures.

(ix) Test Methods and Control Documents.

4.5 CAD/CAM Support

The Contractor shall employ computer-aided design and computer aided manufacturing (CAD/CAM) technologies, techniques, methods and systems in the design, design analysis, modeling and simulation in the development and documentation of space/aerospace system and units under this SOW.

The Contractor shall design and produce printed wiring board designs for high density, high reliability space, aerospace and terrestrial optical and RF payload systems, including high density flat pack, ball grid array and column grid array device package technologies, and those designs requiring impedance matching, thermal coefficient of expansion (CTE) matching and those designs with thermal/power dissipation design challenges. The resultant printed wiring boards shall be compliant with MIL-PRF-31032. The Contractor shall design and develop housings and detailed fabrication items for space, aerospace and terrestrial optical and RF payload systems featuring high density, small size and light weight, which shall be submitted in accordance with CDRL A005.

4.6 Graphics and Illustrations

The Contractor shall prepare presentation-quality graphics and illustrations in black and white, as well as color, depicting satellites, antennas, ground stations, test equipment, and various other aspects of space, aerospace and terrestrial optical and RF payload programs as required in support of requirements such as presentation of concepts, technical reports, and meetings.

4.7 On-Line Resource Service

The Contractor shall design, develop host, and maintain websites for optical and RF payload programs. These websites shall be password protected, and provide pertinent program documentation, schedules, calendar of events, and other related information for access and downloading by approved program personnel.

4.8 Documentation Review and Evaluation

The Contractor shall participate in requirements and design reviews and technical interchange meetings planned for each development program. The Contractor shall critique the design documentation for completeness and compatibility with SSDD-established documentation requirements, and shall present the results of these critiques to the COR in accordance with CDRL A013.

The Contractor shall review documentation generated by SSDD and other participating Contractors, evaluate its compliance with the established SSDD criteria, and assess its impact on the content of the design specifications and other system and subsystem technical documentation. The Contractor shall inform SSDD via CDRL A018 of its assessment of the impact and recommend changes to the program documentation. Documentation to be reviewed shall minimally include: technical reports, schedules, analysis reports, design specifications, briefings, design review data packages, drawing packages, design review minutes and action item responses, test plans and procedures, test reports and similar.

5 ENGINEERING REQUIREMENTS

5.1 Systems Engineering

The Contractor shall analyze SSDD space, aerospace and terrestrial optical and RF payload systems, perform evaluations of systems interfaces, participate in system definition and development, and generate metrics and measures of effectiveness for each system in accordance with EIA/IS-632, Systems Engineering.

5.1.1 System Definition

The Contractor shall identify and characterize (in terms of performance, weight, internal/external interfaces, specifications, etc.) any element of and/or all major components of a system design. This shall include key specifications defining modes, capabilities and interfaces. Specifically, this shall include 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. This shall be accomplished using an explicit, documented evaluation of the tradeoffs among alternatives involving the degree of assurance of achieving all program objectives (including performance and reliability/lifetime) and system acquisition cost.

5.1.2 System Analyses and Planning

The Contractor shall analyze current and planned system architectural concepts, plans, implementations, and operational analyses. Any potential areas for improvement shall be identified. The Contractor shall also identify technologies that should be pursued to improve the system architectures. The Contractor shall assist in the development and maintenance of applicable concept plans, white papers, external concept development studies, Concept of Operations (CONOPS), and standard operating procedures. The results of these system analysis and planning efforts shall be reported under CDRL A004.

5.1.3 Technical Assessments

The Contractor shall prepare technical assessments and engineering analyses to identify, recommend, and implement resolutions of critical design or performance deficiencies. The Contractor shall provide system level integration test plans and procedures; identify and report deficiencies; support hardware and software design reviews; identify, analyze or develop decision support, simulation or modeling support activities; and provide short-term engineering analyses and quick reaction studies. The Contractor shall also assist in system survivability analyses and in analyzing and resolving protocol issues. These analyses shall be submitted under CDRL A004.

5.1.4 Independent Verification and Validation (IV&V)

The Contractor shall participate in the Independent Verification and Validation (IV&V) of space and ground SSDD system hardware and software. The IV&V efforts will ensure that the requirements levied on the system have been fully satisfied by the design and that no additional functionality has crept into the system. The IV&V effort will focus on all areas of the design, including: requirements traceability, maintainability, testability, interface analysis, stress testing, software design and software process Additionally, the IV&V efforts will validate system and subsystem performance and functionality. The results of these IV&V efforts shall be documented and submitted under the CDRL A004.

5.1.5 Technical Reviews

The Contractor shall participate in, or provide technical or other support toward various technical reviews. Examples of these reviews are:

· Systems Requirements Review (SRR)

· System Design Review (SDR)

· Software Specification Review (SSR)

· Preliminary Design Review (PDR)

· Critical Design Review (CDR)

· Technical Interchange Meetings (TIMs).

5.1.6 Systems Engineering Support To Integration and Test

The Contractor shall have the demonstrated capability to and shall provide systems engineering support to integration and test programs for SSDD. This systems engineering support shall provide systems engineering support to requirements and verification method definition, integration and test concepts, approaches and architectures, integration and test systems hardware/software technologies selection and integration and test programs implementation.

5.1.7 Systems Application Engineering

The Contractor shall have the demonstrated capability to and shall perform systems applications engineering efforts for existing and advanced spacecraft and aerospace optical and RF payload systems. Engineering efforts to be performed under this subtask shall include, but may not be limited to, analyzing, defining, developing, evaluating, and controlling (a) bus architectures, their protocols and throughput characteristics, (b) subsystem design implementations, (c) fail-safe/fault-tolerant provisions, (d) modeling and simulation of system performance using modeling software such as MATLAB and SIMULINK, (e) functional interfaces among subsystems, (f) interface circuit configurations, (g) interface signal level requirements, and (h) internal power distributions and revised power budgets.

Deliverables under this subtask shall include formal reports in the form of design packages which shall be submitted in accordance with CDRL A005.

5.1.8 Performance Analysis

The Contractor shall conduct performance analyses as well as troubleshooting and data analysis for both space, aerospace and terrestrial optical and RF payload systems and subsystems. Analysis of performance may include pre-operational, operational, and post-operational mission phases. The work to be performed under this subtask shall include, but may not be limited to, (a) analysis of mission data to determine subsystem and system performance characteristics, (b) recovery, reduction and analysis of mission data, (c) development of systems necessary for collection, reduction and analysis of mission data, (d) provision of real-time problem analysis and resolution for operational missions, (e) analysis of mission data to determine the nature of faults or performance-limiting factors, and (f) development of solutions, including flight software or hardware upgrades to maximize mission performance.

5.2 Systems Design and Development

The Contractor shall have the demonstrated capability to and shall design, develop, and fabricate selected proof-of-concept, engineering models, and operational systems for NRL space, aerospace and terrestrial optical and RF payload systems applications. The engineering expertise required to accomplish this development shall be from employees of the Contractor unless otherwise approved by the COR. These systems shall include, but not be limited to, RF and Optical Payloads. In addition, the Contractor shall accomplish the modeling and simulation necessary to verify the maturity and performance margins of the system designs. All systems development efforts shall be guided by DOD-E-8983C, DOD-HDBK-263 and MIL-HDBK-454(1), and as specified herein.

5.2.1 RF and Optical Payloads Design and Development

5.2.1.1 Optical Payloads

The Contractor shall have the demonstrated capability to and shall support NRL in the development, design, manufacturing, laboratory testing and field testing of optical imaging payloads for airborne and space deployment. Ongoing efforts include the Lakewood and MISSE7 Programs. The Contractor shall provide the program management, system engineering, design, manufacturing, and testing of the hardware and software as well as management of major subcontracts for space qualified optical telescopes and visible and infrared electro-optical focal planes.

The Contractor shall have the demonstrated capability to and shall support NRL with engineering for the development of advanced optical sensor systems for deployment on balloon and airborne platforms for the purpose of field testing and subsequent application development including areas of data archiving, processing, and exploitation. Examples of recent and current programs in this area include the SSE and Harbor-Mist Programs. The Contractor shall also have the demonstrated capability to and shall measure and analyze the dynamics of vehicles and the sensor platforms and their impact on optics systems.

The Contractor shall provide NRL with engineering expertise for the development of large, deployable, space optical systems. A recent example is the NRL Revolutionary Imaging Technology (RIT) Program. The Contractor shall have the capability to formulate large space optics concepts which requires expertise in optical engineering, structural metrology and control systems, and large area, video rate focal planes. The Contractor shall have the demonstrated capability to develop space qualified actuator drivers for deformable optical systems.

The Contractor shall have expertise in the use of modeling and simulation software such as MATLAB/Simulink, Mathematica, IDL/ENVI, FRED, CODE V and ZEMAX design tools in support of these programs.

The Contractor shall also have the demonstrated capability and provide electro-optical system engineering expertise in support of the NRL advanced star tracker and 3D, real time imaging sensor programs.

5.2.1.2 RF Payloads

The Contractor shall have the demonstrated capability to and shall support NRL in the development, design, manufacturing, and testing of RF payloads for airborne and space deployment. Ongoing efforts include the RDP space payload and the SRP UAS payload.

The Contractor shall have the demonstrated capability to and shall design and develop Radar Warning Receiver (RWR) space payloads capable of instantaneous frequency and parameter measurement and characterization in the 2 to 4 GHz frequency range. The Contractor shall have the demonstrated capability to accomplish instantaneous frequency measurement in a small form factor as part of this capability.

The Contractor shall have the demonstrated capability to and shall support NRL in the development, design, manufacturing, and testing of RF antennas, sensors and communications devices for ground, airborne and space deployment. Ongoing efforts include the MRC Feed Collage Upgrade Program and several space/UAS sensor and communications systems in the VHF to EHF and higher frequency range. The Contractor shall provide the system engineering, design, manufacturing, and testing of the hardware and software and the network appliances to control the feed selection in the feed collage. The Contractor shall provide quick prototyping capability in support of these systems.

5.2.2 Power Systems Design and Development

The Contractor shall design and develop systems that convert condition and distribute electric power within satellites, space payloads, and tactical airborne and ground systems. These systems shall range from low voltage and high voltage DC to DC power converters for space systems to and high power (>3KW) stackable power systems for C4ISR systems that automatically load share and balance input AC power. These power systems shall meet the EMI/EMC requirements of MIL-STD-461E as tailored by the COR to each design.

5.2.3 Test Systems Design and Development

The Contractor shall develop automated test systems using Lab View or Lab Windows that automate tests with RF an/or optical test equipment, radios, baseband testers such as Bit Error Rate Testers and audio analyzers as required for complex NRL programs.

The Contractor shall also develop Waveform Development Environments (WDEs) for simulating target hardware and software operating environments to develop and test baseband operation of software SIGINT, Communications, and Processing applications. Current programs include the SRP and RDP WDEs.

5.2.4 Packaging Design

The Contractor shall have the demonstrated capability to and shall provide the packaging design efforts necessary to implement the electronic and optical systems discussed in this section. The Contractor shall place special emphasis on packaging design considerations directed toward achievement of stringent EMI/EMC objectives. The Contractor generated design documentation (including assembly drawings and machined items detailed drawings) shall conform to engineering drawing practices per ANSI standards and applicable program-specific CM requirements.

The Contractor shall have the demonstrated capability and shall provide the analysis of the structures, housings and printed wiring board (PWB) designs to verify conformance with NRL specified thermal and dynamic environments and design margin criteria. The Contractor shall have demonstrated capability using ALGOR finite element modeling and analysis for structural modeling and analysis, and ALGOR and Thermal Desktop/SINDA for thermal modeling and analysis.

6 SYSTEMS EFFECTIVENESS

The Contractor shall have the demonstrated capability to and shall provide the necessary resources to perform the following systems effectiveness efforts:

6.1 Reliability, Maintainability and Availability Engineering The Contractor shall evaluate the inherent and achieved reliability, maintainability and availability (RMA) characteristics of the various space, aerospace and terrestrial optical and RF payload systems developed by the SSDD. The Contractor shall evaluate overall system RMA potential, compare this potential to the RMA requirements, and recommend RMA enhancement efforts where applicable. The Contractor shall also conduct RMA trade-offs among competing design concepts. The required analyses shall be performed in accordance with established SSDD procedures. The Contractor shall provide briefings, results summaries and detailed analysis reports documenting the analysis results on an interim and final basis with identification of unresolved design issues and the schedule for analyses yet to be performed. The analysis reports shall be submitted in accordance with CDRL A006, RMA Analysis Reports. Where previous analysis reports exist, the Contractor shall revise and refine the previous reports when directed by the COR.

6.1.1 Subsystem And Unit Reliability Engineering

The Contractor shall conduct reliability engineering analyses of the SSDD subsystem and unit designs in accordance with STC-D-001. The reliability analyses to be performed shall include, but may not be limited to (a) Failure Modes, Effects and Criticality Analyses; (b) Electrical Stress Analyses; (c) Reliability Models and Predictions; and (d) Failure Rate Calculations. The Contractor shall identify areas where subsystem reliability may be improved and provide a description of the means available to achieve this improvement. The results of these analyses shall be documented in formal reports and shall be submitted under CDRL A006.

6.1.1.1 Subsystem Failure Mode, Effects and Criticality Analyses (FMECA) The Contractor shall prepare subsystem FMECAs to identify potential failure modes and evaluate their effect on the operation of the subsystem. The Contractor shall verify redundancy implementations, identify any single point failure modes and prepare design modification recommendations that would lessen the impact of failure occurrence on subsystem operation. The criticality of each failure mode shall be derived to provide a quantitative means of evaluation. The Contractor shall also modify these analyses to reflect data collected as a result of testing. The Contractor shall assure that subsystem level FMECAs are capable of integration into the system level FMECA with minimal effort.

6.1.1.2 Electrical Stress Analyses

The Contractor shall perform subsystem circuit stress analyses based on the available design and test data. These analyses shall identify any parts where individual part electrical/thermal stresses may approach or exceed the maximum levels allowed by SSDD high reliability derating criteria contained in STC-D-001. The Contractor shall also perform a detailed stress analysis on each part and prepare recommendations for resolving part applications where the high reliability derating criteria are exceeded.

6.1.1.3 Subsystem Reliability Models and Predictions

The Contractor shall prepare subsystem level reliability block diagrams and mathematical models to reflect the subsystem design baselines, mission success criteria and FMECA information. The Contractor shall modify reliability predictions through the application of functional subassembly failure rates and operating/nonoperating mission times in the mathematical models. The subsystem level reliability block diagrams and mathematical models shall be functionally and operationally compatible with appropriate system level reliability model to permit maximum integration and use of the subsystem level diagrams and math models in the system level reliability models.

6.1.1.4 Failure Rate Calculations

The Contractor shall derive subassembly failure rates employing MIL-HDBK-217 augmented by direct applicable test data, when available. The Contractor shall modify subassembly failure rates as necessary to reflect the results of both the applicable stress analysis and the applicable FMECA. The Contractor shall also derive subassembly operating/non-operating times to reflect mission operational time lines.

6.1.2 System Level Reliability Engineering

The Contractor shall generate, refine and maintain system block diagrams and mathematical models that reflect system level redundancy implementations, system success criteria and mission operating time lines. The Contractor shall conduct system level reliability analyses employing the system level reliability mathematical models and the subsystem reliability analysis results described in Section 6.1.1.