14RJT81_0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to address technical questions, amend the Statement of Work (SOW), amend Section L and M and to extend the closing date and time of the solicitation. The required response date/time has changed from 07-Jul-2014 02:00 PM EST to 18-Jul-2014 02:00 PM EST.

See pages 2-32.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 32

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 18-Jun-2014

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N00164-14-R-JT81

X 9B. DATED (SEE ITEM 11)

01-May-2014

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

18-Jun-2014

CODE

NAVAL SURFACE WARFARE CENTER CRANE DIV

D. BRIGHT (812-854-2938)

BLDG 3422

300 HIGHWAY 361

CRANE IN 47522-5001

N00164 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N00164-14-R-JT81

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

The following items are applicable to this modification:

TECHNICAL QUESTIONS

1. Q: Where is the Statement of Work posted?

A: The SOW is included in Section C. An amended version of the SOW is included in Section C of this amendment.

2. Q: Please provide clarification on the Past Performance submission limits. Is the page limitation for each contract submitted one page or five pages?

A: One page per contract, five pages total.

3. Q: With respect to the Price Proposal instructions, can the government please provide additional explanation pertaining to the expected subcontract pass through rates (element 6) (e.g.

breakdown of Prime Contractor burdens applied to subcontractor costs)? Is this amount to be inclusive of the Prime Contractor’s fee?

A: The purpose of requesting this information is so the offeror can provide the Government sample pricing and rate information. For element 6, if your rate structure includes multiple burdens applied to subcontractor costs – please provide a breakdown and include a narrative of how each of these rates are applied. The Prime Contractor’s profit should be shown separately in Element 5.

4. Q: Can appropriate subcontractors be added to a subsequent job order as necessary? Will the addition of new vendors (for procuring materials) be allowed on subsequent job orders though they are not yet identified and will not be included in the proposal response for the BOA award?

A: Each job order will be a competition within itself. Once delivery orders are issued, addition of subcontractors will have to be approved under cost‐type orders.

5. In CNIN‐L‐0002, Volume II, paragraph (d) SUBFACTOR C: MANAGEMENT APPROACH C 1:

Engineering Process, the second bullet ends with an "and". Is there additional information forthcoming?

No additional information is forthcoming. The "and" is hereby removed.

6. Q: The CDRLs provided in 14RJT81 sol att zip do not align with the CDRLs specified in the section C (SOW) of the solicitation. Will there be an amendment to the CDRLS?

A: The SOW is hereby amended to align with the CDRLS. Please reference the SOW contained in this amendment.

7. Quality Requirements – Does the offeror must have certified quality programs in place? Or could we address those issues in plans developed specifically for job orders?

A: The solicitation requires compliant processes but not certification. The offeror shall demonstrate in their technical proposal that their processes and procedures are robust enough to meet the ISO levels.

8. Q: Is there a requirement for the Prime Contractor to hold a TS Facility Clearance or if a sub for the Prime could carry it for the Prime is one was required?

A: Facility clearance requirements will vary by job order and is not a requirement for the BOA but TS is anticipated for many of the requirements. At the JO level a prime would be required to hold a TS facility clearance but a safeguarding requirement could be performed at another location such as a subs location.

9. Q: In addition to the Small Business Participation Plan required under Subfactor D (pg 112 of 120), are Offerors required to submit a Small Business Subcontracting Plan per section 52.219‐9, with a minimum of 21.35% to small businesses in accordance with the DOD Subcontracting goals? If no, will a proposal be deemed “unacceptable” for Volume II SUBFACTOR D if it does not incorporate the use of Subcontractors?

A: A Small Business Subcontracting Plan (FAR 52.219‐9) is not a proposal requirement for the BOA award evaluation. This clause applies at the Job Order level. In the event that a Job Order requirement is expected to exceed $650,000, a small business subcontracting plan will be required. This clause does not apply to small business concerns.

10. Q: Under the discussion of past performance references, the RFP requires that past performance references be recent and relevant. No criteria has been established for the term “recent”. Under subparagraph (e) “current” contracts are defined as “those on which performance occurred during the last three (3) years, but there is similar no definition of “recent”. Request the Government define the term “recent” for past performance references.

A: Recent is defined as those on which performance occurred during the last three (3) years.

11. For contracts with CPARs, is it mandatory that the Contracting Officer Representative’s or their delegates complete the questionnaires? If it is not mandatory, and the cite contract does not have CPARs, will there be any discounting of the contract because a questionnaire was not completed?

A: The offeror is required to send a Past Performance Questionnaire (PPQ) to each reference cited in their proposal, regardless if a CPARS report is available for the particular contract. If the reference does not/will not respond (i.e. the questionnaire is not completed) and no information pertaining to the reference is readily available to the Contracting Officer (via CPARS or any other reasonable means), this will result in a neutral rating (neither favorable nor unfavorable).

12. Large business prime contractors should be able to adhere to the intentions of Section L.

However, based on the statements contained in Section M, it appears they may be penalized by discussing their experience and capability in using subcontractors including small business concerns. Please clarify how offerors should address their capabilities and intentions regarding utilization of subcontractors.

Offerors will not be penalized for discussing their experience and capability in using subcontractors, including small business concerns. Offeror’s shall demonstrate both their prime contractor technical capability AND their subcontractor management processes. Offeror’s will not be penalized for strengths in both areas.

The intent is not to prohibit subcontractors. The intent is for the prime contractor to peform more than management of subcontractors.

13. Will only FFP and CPFF contracts be considered relevant to this solicitation?

No – other prior contract types are acceptable.

14. CNIN–L‐0002, Volume III, Subparagraph (e) states “The offeror should also consider the level or amount of effort” Nowhere under Volume III – Past Performance Proposals is there defined a “level or amount of effort” that is considered relevant with respect to this solicitation. Request the Government define “level or amount” that is relevant to this solicitation.

A: No, there is not a formal defined “level or amount of effort” that is considered relevant with respect to this solicitation. Past performance dealing with design, development, testing, and production of special surveillance and reconnaissance systems, subsystems, and components will be considered relevant.

Therefore, this statement is has been removed. Please see the amended paragraph in CNIN-L-0002.

15. CNIN–L‐0002, Volume III – Subparagraph (f) requires the offeror to submit present and past performance information. Please confirm that the Government desires at least some of the contracts cited for past performance to be those that are being currently worked, and if so, cite the number so required. If this is not the Government’s intention, please edit to present OR past performance information.

A: Requirement is for either present or recent past performance efforts. Subparagraph (f) is hereby amended to state “present or past performance information”. Please see the amended paragraph in CNIN- L-0002

16. CNIN–L‐0002, Volume III – Subparagraph (f) – Requires offeror’s to provide past performance for efforts of “similar size, scope and complexity”. Please define what will qualify as relevant experience with respect to “size, scope, or complexity”

A: There is no formal definition of what is considered relevant with respect to size, scope or complexity.

Past performance dealing with design, development, testing, and production of special surveillance and reconnaissance systems, subsystems, and components will be considered relevant. Therefore, this statement has been removed. Please see the amended paragraph in CNIN-L-0002.

17. Q: CNIN–L‐0002 limits the page count for the Software Development Plan (SDP) to fifteen (15) pages. If it is the Government’s desire to have the opportunity to review an actual SDP, please eliminate the page limit for the SDP.

A: The page limit for the SDP is hereby removed.

18. Q: The seven CLIN descriptions only list FFP yet under Clauses Incorporated by Full Text on page 5 states that Cost Plus Fixed Fee (FAR 16.306) contracts are authorized under the BOA. Please clarify.

A: Both Firm Fixed Price (FFP) and Cost Plus Fixed Fee (CPFF) contracts are authorized under the BOA.

19. Clause CNIN‐M‐0002, Factor III Cost/Price states “Proposals which are unrealistic in terms of technical or schedule commitments, or unrealistically high or low in terms of cost/price, may be deemed reflective of an inherent lack of technical competence, or indicative of a failure to comprehend the complexity of risks of the proposed work and may be grounds for rejection of the proposal”

Can the Government explain how this will be assessed during evaluation?

A: This language is removed, as this type of evaluation will be conducted at the job order level.

Please see the amended version of CNIN‐M‐0002 included in Amendment 1.

20. Section L requires submittal of labor rates for seven (7) categories. Can the Government provide additional details on how the supplied labor rates will be fairly assessed for cost realism?

A cost realism analysis is not applicable to the price evaluation for a BOA award. The purpose of requesting this information is to give the Government sample pricing for general labor categories anticipated to be utilized under the BOA. The Government will review BLS and other labor databases to determine whether rates are realistic. Specific cost/price evaluations (including cost realism, as appropriate) will be conducted at the Job Order level.

21. The RFP does not specifically state how Section B is to be completed. Will the Government clarify if/how Section B is to be completed in order to submit a compliant proposal?

All proposal requirements are identified in Section L. There are no submissions required for Section B.

22. Will the Government consider providing specific labor descriptions in addition to the generic experience requirements provided?

No specific labor descriptions will be provided. The purpose of requesting this information is so the offeror can provide the Government sample pricing for general labor categories anticipated to be utilized under the BOA.

23. Based on the language specified in Section L and Att 2, it is the Offeror’s understanding that the Government only wants a list of direct and indirect rates, specific fee percentages, and total subcontractor pass thru rates. Will the Government confirm that no hours, fully burdened labor rates, nor total cost/prices are required during submission of this BOA?

A: No hours, fully burdened labor rates, nor total cost/prices are required in the price proposal.

24. Please confirm that the offeror’s are required to submit pricing information for calendar year 2014 only, instead of each calendar year pertaining to the BOA timeframe of 5 years.

A: Pricing information is only required for Calendar Year 2014.

25. How should Offeror’s complete Att 02, Table 1 when direct/indirect rates and escalation factors vary from one calendar year to the next.

A: Direct/Indirect rate information is required only for Calendar Year 2014. Per Attachment 2, Offeror’s shall provide a labor escalation rate within #2 of Table 1. The escalation rate shall be based on recent historical actual information.

Please note that the intent of requesting this information is not to “lock” offerors into pricing arrangements. The Government recognizes that fluctuation will occur. The intent is to provide current information for the Government to evaluate.

26. Q: Please explain the language on page 60 and page 118. Does NSWC Crane only wish for a singular Prime and are discouraging larger companies to bring aboard small businesses?

A: No, this is not the intent. As stated on page 118, the Government acknowledges that some teaming is anticipated (which may include large businesses utilizing small businesses). Page 60 includes a required clause, FAR 52.219‐8 – Utilization of Small Business Concerns. This clause is required in any contract or subcontract that offers subcontracting opportunities.

Therefore, subcontracting is anticipated and the appropriate clauses are included in the solicitation. However, as stated on page 118, subcontracting teaming arrangements should be minimal. The prime contractor should not simply be a pass thru only performing program management functions.

27. Q: Requesting clarification on Solicitation page 111, Software Development Plan. Is the offeror expected to create our own sample task using one of the proposed technology areas?

A: No. The proposal requirement is for a Software Development Plan. You may submit a generic example or one from a past project.

28. One of our key contracts that provides past performance of interest to this solicitation is classified where the sponsor is prohibited to provide the contract number. All other information, including the government technical representative phone number, can be provided. Will it be acceptable to provide a past performance questionnaire without our government sponsor filling in the contract number?

A: Yes, this is acceptable.

29. In terms of the price proposal, are we to submit only labor category rates, i.e no other cost data?

A: Please see Attachment 2, Table 1. All of the information requested in Table 1 is required.

30. Are we to assume that work is to be done at the Contractor site?

A: Yes, all work is done at the Contractor site.

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The required response date/time has changed from 07-Jul-2014 02:00 PM to 18-Jul-2014 02:00 PM.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

Section C: Description and Specification

STATEMENT OF WORK

1.0 SCOPE

This Statement of Work (SOW) defines the effort required for the design, engineering, fabrication, and test of intelligence, surveillance, and reconnaissance components and systems that have met TRL level 6 maturity. The scope of this effort shall include provision of engineering development models (EDM), pre-production units (PPU), and low rate initial production (LRIP). System EDMs, PPUs, and LRIPs shall be designed, engineered, fabricated, and tested to satisfy the individual Job Order statements of work. It is not expected that all Job Orders will require the end to end development described in the contract level SOW due to variations in product maturity and required timelines for development at the Job Order level. Job Orders where end items are intended for combat evaluations or quick reaction capability may have abbreviated testing and schedule requirements. For all Job Orders, final product acceptance will be conduct by the Government Technical Design Agent. The requirement for associated program management is also included in this SOW.

1.1 BACKGROUND

NSWC Crane, Surveillance and Reconnaissance Systems Division (SRSD) provides full spectrum life cycle support for systems engaged in the intelligence, surveillance, and reconnaissance enterprise. SRSD subject matter experts identify emerging Warfighter sensor and collection requirements utilizing a technology surveillance process that identifies opportunities for transition, innovative application, and commercial application in-sourcing. Through close relationships with the requirement managers, resource sponsors, and end user operators, SRSD successfully fields solutions that close technology gaps rapidly and with great effectiveness.

1.2 TECHNOLOGY AREA DESCRIPTIONS

SRSD supports the engineering and development of Intelligence, Surveillance, and Reconnaissance (ISR) enterprise systems and the application development of integrated technology solutions and knowledge management systems to maximize utilization of intelligence data and PED (processing, exploitation, and dissemination) to special operations and intelligence community members. The SRSD portfolio addressed in this SOW includes:

1.2.1 – Technology Area 1 Tagging, tracking, and locating (TTL) systems and their associated situation awareness components that are employed for both friendly, red force, and hostile force tracking. Devices may operate on either commercial or DOD data architectures.

1.2.2 - Technology Area 2 PED systems that are interoperable, fusion capable, and contain cross domain solution innovations that considers Department of Defense (DOD), Other Government Agencies (OGAs), and coalition partner implications. Emphasis on the fusion of all source data, multiple ISR sensor data inputs, open architecture backbone, and advanced algorithm implementations.

1.2.3 - Technology Area 3 Special communications enterprise solutions which are interoperable within the ISR enterprise

1.2.4 - Technology Area 4 Mobile SIGINT solutions including software defined radio, antenna development, precision geo and direction finding technologies across a variety of threats, SIGINT fusion with other intelligence collection systems such as TTL, Special Communications, and Unattended Ground Sensors (UGS); improved system network capabilities.

1.2.5 - Technology Area 5 Sensitive site exploitation technologies for forensic analysis of information technology, mobile communication devices, documents and media exploitation (DOMEX), biometric collections and identification, and physical characterization of site materials/debris.

1.2.6 - Technology Area 6 Persistent surveillance systems including UGS, activity sensors and active sensors, UGS controller devices, data infiltration/exfiltration devices, and device network capability.

1.2.2 Representative Customers

The following list depicts the representative customers for the projects and programs: USSOCOM HQ, TSOCs, and Service Special Operations Components, Technical Support Working Group, US Navy, US Marine Corps, US Army, US Air Force, OSD, and COCOMS (CENTCOM, PACOM, AFRICOM, SOUTHCOM, EUCOM), and Other Government Agencies.

2.0 APPLICABLE DOCUMENTS

The following specifications, standards, and handbooks form a part of this SOW to the extent cited herein. Unless otherwise specified, the issue of Government documents is that listed in the current issue of the Department of Defense Index of Specifications and Standards (DoDISS) on the issue date of the solicitation associated with this SOW. Non-Government standards listed are those in effect on the issue date of the solicitation associated with this

SOW.

2.1 Military Specifications, Standards and Handbooks

MIL-STD-31000A Detail Specification, Technical Data Packages, 26 Feb 2013

MIL-HDBK-470A Notice 2 Design and Develop Maintainable Products and Systems, 31 May 2012

MIL-HDBK-781A Reliability Test Methods, Plans, and Environments for Engineering Development, Qualification, and Production, 01 Apr 1996

MIL-HDBK-1785 System Security Program Management requirements, 01 Aug 1995

MIL-STD-881C Work Breakdown Structures for Defense Materiel Items, 03 Oct 2011

MIL-HDBK-29612-1A Guidance for Acquisition of Training Data Products and Services (Part 1 of 5 Parts), 31 Aug 2001

MIL- PRF-29612B Performance Specification, Training Data Products, 31 Aug 2001

MIL-STD-129P (4) DoD Standard for Military Marking for Shipment and Storage, 19 Sept

MIL-STD-130N, CH 1

DoD Standard Practice for Identification Marking of U.S. Military Property, 16 Nov 2012

MIL-STD-461F Requirements for the Control of Electromagnetic Interference Emissions & Susceptibility, including notices, 10 Dec 2007

MIL-STD-882E DoD Standard Practice for System Safety, 11 May 2012

EIA 649B National Consensus Standard for Configuration Management, 17 Jun 2011

GEIA-STD-0007 Logistics Product Data, 15 Oct 2008

MIL-STD-1472G Human Engineering, 10 Jan 2012

MIL-STD-2073-1E DoD Standard Practice for Military Packaging, change notice, 17Jan 2011

MIL-STD-40051-2B DoD Standard Practice Preparation of Digital Technical Information for Page-Based Technical Manuals (TIMs), 30 Nov 2012

MIL-HDBK-61A Configuration Management Guidance, 02 Feb 2001

MIL-STD-3034-Notice 1 Reliability-Centered Maintenance (RCM) Process, 22 Jun 2011

2.1.2 Joint Chiefs of Staff, Department of Defense and DoD Services Documents

DoD 4120.24 M Defense Standardization Program (DSP) Policies and Procedures, Mar 2000

DoDI 5200.39, CH 1 Mandatory Procedures for Research & Technology Protection with the DoD, 28 Dec 2010

DoD MCTL Military Critical Technologies List

DoDI 5000.02 Operation of the Defense Acquisition System, 08 Dec 2008

DoDD 5220.22M, CH 1 National Industrial Security Program Operating Manual, 28 Mar 2013

DoDD 8500.01E Information Assurance (IA), 24 Oct 2002

DoDI 8500.2 Information Assurance (IA) Implementation, 06 Feb 2003

DoDI 8510.01 DoD Information Assurance Certification and Accreditation Process (DIACAP), 28 Nov 2007

DoDD 8570.01-M Information Assurance Workforce Improvement Program

DISA STIG Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIG)

Directive-Type Memorandum

Security of Unclassified DoD Information on Non-DoD Information Systems, 16 Sep 2010

2.1.3 Non-Government and Commercial Standards, Specifications and other applicable publications AR 700-15 Packaging Of Materiel, 12 Jan 2004

ASME Y14.24M Types and Applications of Engineering Drawings

CMMI-SE/SW/IPPD/SS Capability Maturity Model Integration (CMMISM) for Systems Engineering, Software Engineering, Integrated Product and Process Development, and Supplier Sourcing, 10 Mar 2002

IEEE 1220-2005 IEEE Standard for Application and Management of the Systems Engineering Process, 09 Sept 2005

IEEE/EIA 12207-2008 IEEE Systems and Software Engineering - Software Life Cycle Processes

IEEE STD 1016-2009 IEEE Standard for IT Systems Design Software Design Description, 19 Mar

ISO/IEC-15288 Systems Engineering- System Life Cycle Processes, 01 Nov 2002

ISO 9000 & 9001 Quality Management Systems, 01 Dec 2000

ISO 10007:2003 Quality Management - Guidelines for Configuration Management

NAS 411 National Aerospace Standard (NAS) 411, Hazardous Materials Management Program

NSTISSAM

TEMPEST/1/92

Compromising Emanations Laboratory Test Requirements, Electromagnetics

SAE AS5553 Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, & Disposition

The Contractor shall use the revision effective as of the date of contract award for each of the documents listed in the following subparagraphs and to the extent specified in the requirements of this SOW. Nothing in this document however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

It is the intent of this solicitation and the resulting contract to fully implement the principles of the Department of Defense (DoD) Acquisition Reform initiatives. Specifically, reference is made to the Secretary of Defense policy promulgated by memorandum on 29 June 1994 regarding the use of specifications and standards. When specifications are not practical, non-Government (industry developed) standards shall be used.

In the event of conflict between the documents referenced herein and the contents of this SOW, the Order of precedence shall be:

1) Section 3 of this SOW;

2) Specifications, Standards and Other Documents, listed in Section 2.1 of this SOW.

Unless otherwise indicated, copies of federal and military specifications, standards, and handbooks are available on the internet at the Department of Defense Single Stock Point (DoDSSP) at https://assist.dla.mil. DoD Directives, Instructions and Publications documents, as well as other services publications at DoD Issuances website at:

http://www.dtic.mil/whs/directives/. Non- Government documents should be obtained from the commercial sources.

Requests for copies of documents not available from sources listed above should be directed to the designated Government technical point of contact for the Basic Ordering Agreement (BOA).

3.0 REQUIREMENTS

Requirements contained herein describe at the contract level the Deliveries that are associated with this SOW. The individual Job orders will further define specific requirements and will provide the necessary details via a statement of objectives, statement of work, or detailed specification.

3.1. Design and Engineering

The Contractor shall provide a hardware design for requirements as detailed in the Job order. The Contractor shall make maximum use of Commercial Off the Shelf (COTS) and Non-Developmental Items (NDI), modified as necessary, to meet the requirements of this SOW. The Contractor shall minimize obsolescence by selecting products that will avoid or resolve hardware and software/firmware obsolescence issues, refer to MIL-HDBK-470A Notice 2.

3.1.1. Design Analysis

The Contractor shall conduct a detailed analysis of the proposed hardware and software design. Detailed physical and performance design characteristics shall be specifically identified including, where applicable, the engineering decision process for using one methodology over another. The Contractor shall include a discussion of alternatives and the ramifications thereof, risk assessments and trade-offs made and proposed logistic support/level of repair.

The Contractor shall present the results of the design analysis at the Preliminary Design Review (PDR), supported by the deliverables listed in this SOW section. The Contractor shall provide a Technical Report – Studies/Services, Drawing Tree identifying each of the major assemblies/sub- assemblies, software modules, manufacturer names, model, and product/part numbers. If the Job order requires, the Contractor shall also provide a Reliability Prediction and Documentation of Supporting Data, Reliability Analysis Report documenting the study’s performance and providing a system reliability prediction.

CDRL A001 - TECHNICAL REPORT – STUDY/SERVICES, DRAWING TREE

CDRL A002 - RELIABILITY PREDICTION AND DOCUMENTATION OF SUPPORTING DATA,

RELIABILITY ANALYSIS REPORT

3.1.2 Software/Firmware Engineering

The Contractor shall perform all necessary software/firmware engineering efforts to design, develop, test, evaluate, and provide software/firmware products, services, and artifacts that implement the capabilities stated in the Job order. The details of those efforts, including the required data deliverables and reviews, are described in the subsequent paragraphs of this SOW. The Government desires unlimited technical data rights for software/firmware, middleware, and modeling artifacts. The Contractor shall minimize the amount of unique non-commercial software/firmware that must be developed/modified in the design of all deliverables.

3.1.2.1 Software/Firmware Design

To the maximum extent possible the Contractor shall implement open, modular software/firmware architecture, composed of Software Components (SC), which minimize coupling and inter-dependencies. If required by Job order, the Contractor shall provide a Software Requirements Specification (SRS). The SRS shall include all middleware/interfaces and software/firmware, with associated details, to ensure requirements are met. If required by Job order, the Contractor shall develop a Software Design Description (SDD) that describes the architectural modularity and detailed design of the software/firmware/middleware component.

CDRL A003 - SOFTWARE REQUIREMENTS SPECIFICATION (SRS)

CDRL A004 - SOFTWARE DESIGN DESCRIPTION (SDD)

3.1.2.2 Software/Firmware Development

The Contractor shall develop any software/firmware/middleware not available in the open market. Per Job order, the Contractor shall develop and deliver a Software Development Plan (SDP), based upon guidance found in IEEE/EIA 12207 and in accordance with (IAW) CMMI requirements such as CMMI-SE/SW/IPPD/SS. The software/firmware/middleware shall include functions as specified by Job order. Open Architecture conventions shall be used in this development and shall be included in the Contractor’s SDP. Any unique support items developed during the software/firmware/middleware development process shall be Government property and any non-unique support items shall be available to the Government for review/approval as required. The SDP shall discuss software/firmware/middleware design integrity, quality and stability addressing Configuration Management (CM), defect tracking, peer reviews and other associated processes. The SDP shall detail the software/firmware build environments. The Contractor shall use software/firmware management indicators and metrics to aid in managing the software/firmware/middleware development process and communicating its status to the Government.

The Contractor shall define a corrective action process for identifying software/firmware/middleware development impacts and resolution when goals are not met. This process shall be documented in the SDP.

The Contractor shall define the software Operating Environment (OE) and manage the OE baseline throughout the development process. Changes to the OE baseline shall be processed in accordance with the Government approved Contractor’s Configuration Management (CM) Plan. The Contractor shall obtain Government approval of any OE change before proceeding with software/firmware/middleware development. The Contractor shall develop a Software Version Description (SVD). The SVD shall detail all Operating Systems with their associated kernel version, configuration, operational libraries and firmware.

CDRL A005 - SOFTWARE DEVELOPMENT PLAN (SDP)

CDRL A006 - SOFTWARE VERSION DESCRIPTION (SVD)

CDRL A007 - CONTRACTOR’S CONFIGURATION MANAGEMENT PLAN

3.1.2.3 Commercial Off-the-Shelf (COTS) Software/Firmware

The Contractor shall provide to the Government all COTS based software/firmware/middleware products, along with supporting documentation and all required runtime licenses. This software/firmware/middleware shall include all COTS software/firmware/middleware incorporated into the OE baseline(s) as well as software/firmware/middleware packages utilized to generate OE baselines but not incorporated into the OE. The Contractor must ensure interoperability of such software/firmware/middleware with the OE and shall document any interdependencies (such as minimal revision required) in the appropriate SVD(s). All licensing requirements/restrictions for each COTS product shall be documented in the SVD. This documentation requirement includes all delivered software/firmware/middleware licenses necessary to provide the system capabilities and support full lifecycle implementation.

CDRL A006 - SOFTWARE VERSION DESCRIPTION (SVD)

3.1.2.4 Software/Firmware Testing

The Contractor shall plan and conduct SC-level tests for all developed and modified COTS software/firmware/middleware SCs. The Contractor shall identify and document test cases describing their purpose, the functions being tested, the test environment, and the test cases as part of the Software Test Plan (STP), Software Test Description (STD) and Software Test Reports (STR). The Contractor shall conduct the SC test and record the results in accordance with the SDP and applicable SRS and SDD documents.

The Contractor shall plan and conduct software/firmware/middleware integration testing. Iterative software/firmware/middleware testing shall include additional Computer Software Configuration Item (CSCI) and external interfaces ensuring requirements compliance and sub-system stability. This process is continued until all CSCIs and interfaces are integrated and tested. The Contractor shall conduct this testing in accordance with the Contractor’s STP.

CDRL A008 - SOFTWARE TEST PLAN (STP)

CDRL A009 - SOFTWARE TEST DESCRIPTION (STD)

CDRL A010 - SOFTWARE TEST REPORT (STR)

3.1.2.5 Software/Firmware Products

The Contractor shall develop Software Product Specifications (SPS) for each approved software/firmware/middleware product baseline. The Contractor shall identify all software/firmware/middleware licensing requirements and any software/firmware/middleware usage restrictions. The Contractor shall deliver all required software/firmware/middleware licenses with the final software/firmware/middleware product. The SPS shall ensure software/firmware/middleware and software/firmware revisions are under CM control. The Contractor shall deliver the Computer Software Products including libraries and software/firmware/middleware packages, as well as all software/firmware/middleware tools/utilities. The Contractor shall successfully complete qualification testing of the computer software/firmware/middleware products prior to submission.

CDRL A011 - SOFTWARE PRODUCT SPECIFICATION (SPS)

CDRL A012- COMPUTER SOFTWARE PRODUCT

3.1.2.6 Software/Firmware Delivery and Transition

The Contractor shall prepare a Software/Firmware/Middleware Support Manual (SFSM) as required by individual Job Orders. The SFSM shall contain detailed technical information addressing the processes and resources required to build software/firmware/middleware. In addition, the SFSM shall include file format and data structures used in downloadable datasets and system logs, and describe processes and associated equipment to load and verify software/firmware/middleware on system hardware devices that are not defined in a CSCI. The Contractor shall prepare, with the Government, the Software Transition Plan (STRP) that shall accompany the final Government accepted software/firmware/middleware release products and artifacts. This plan shall also be accompanied with a current SVD and SFSM.

CDRL A013 - FIRMWARE SUPPORT MANUAL (FSM), SOFTWARE FIRMWARE SUPPORT MANUAL

(SFSM)

CDRL A014 - SOFTWARE TRANSITION PLAN (STRP)

3.1.3 Technical Data Package (TDP)

The Contractor shall develop, maintain, and deliver a TDP in accordance with MIL- STD-31000A. The TDP shall include all components, sub-assemblies, and final-assemblies. The Contractor shall document any test requirements on the components, sub-assemblies, and final-assemblies necessary to ensure the characteristics of performance and include these in the TDP. Material and process specifications, special inspection equipment drawings and special tooling drawings and their associated lists shall be included in the TDP for complete product definition and total design disclosure. The TDP shall define the connectors and the pin- outs for all Job Order deliverables.

The TDP shall contain, but not be limited to, drawings, parts lists, data lists, wiring lists, schematics, interconnect diagrams, special tooling drawings, specifications, special packaging instructions that include storage and shipping containers and any requirements per MIL-STD-129P (4), MIL-STD-130N, MIL-STD-2073-1E and AR 700-15 , source control drawings, specification control drawings, cable dressing techniques, software/firmware/middleware version description documents, software/firmware/middleware, source code, gerber files and interface control documents and information for both hardware and software/firmware/middleware, operating systems, and artifacts.

The Contractor shall develop Installation Control Drawing Source Data when applicable.

The Contractor drawings and associated lists shall be developed and structured IAW ASME Y14.24 and MIL-STD- 31000A. Classified portions of the TDP shall be handled in accordance with approved security procedures and the DD Form 254. The Government will take configuration control of the TDP at the end of the Period of Performance (PoP) of each Job Order. The contractor shall modify/revise the TDP as necessary to obtain Government approval of the TDP prior to Government acceptance of each TDP.

CDRL A015 - TECHNICAL DATA PACKAGE

CDRL A016 - INSTALLATION CONTROL DRAWING, SOURCE DATA

3.2 FABRICATION

3.2.1 Engineering Development Models (EDM)

After successful completion of PDR, the Contractor shall fabricate EDMs and associated software elements in support of Contractor in-house testing to verify the system design meets the functional and performance requirements. The Contractor shall complete a Factory Acceptance Test (FAT), as described below, for each EDM.

Upon successful completion of FAT, EDM’S will be delivered as specified in the Job Orders. During the fabrication process, the Contractor shall correct any design characteristics that are found to inhibit or make fabrication unnecessarily costly with the proviso that these corrections do not adversely affect system functional or performance capabilities.

3.2.2 Pre-production Units (PPU)

After successful completion of the EDM testing and CDR , the Contractor shall fabricate PPUs of the approved system design, including both Hardware and Software element, to support Environmental Qualification Testing (EQT), training, system integration tests and Developmental Tests (DT). The Contractor shall complete a Factory Acceptance Test (FAT), as described below, for each PPU prior to EQT. Following EQT, the Contractor shall update the PPUs to incorporate all changes to the design, design documentation and processes resulting from EQT and restore the PPUs to a condition representative of the updated design. The Contractor shall complete a Factory Acceptance Test (FAT), as described below, for each PPU following restoration.

3.2.3 TESTING

The Contractor shall prepare a Test Plan, Master Test Plan (MTP) that employs an integrated test and evaluation strategy designed to provide continuous insight into the design and performance of the EDMs and PPUs. The MTP shall be the top-level working document that addresses all testing anticipated by the Contractor and its subcontractors, and encompasses all major system and component level testing. At a minimum, the MTP shall address asset allocation and sequencing and unique or long lead test support equipment requirements.

The Contractor shall perform all testing in accordance with the MTP and Test Procedure, Master Test Procedure.

The contractor shall reference MIL-HDBK-781A for guidance on testing methods. The Test Procedure, Master Test Procedure shall include procedures for all testing required in this SOW. The Contractor shall develop a Test/Inspection Report for any test performed.

CDRL A017 - TEST PLAN, MASTER TEST PLAN (MTP)

CDRL A018 - TEST PROCEDURE, MASTER TEST PROCEDURE

CDRL A019 - TEST/INSPECTION REPORT

3.2.3.1 Interface Tests

When required by Job Order, the Contractor shall develop an Interface Test Plan as part of the MTP to demonstrate that the components communicate effectively and processes the input/output data correctly. The Contractor shall provide the results of that test in a Test/Inspection Report. The Contractor shall also develop an Interface Design Description (IDD) defining the Contractor interfaces between all components.

CDRL A017 - TEST PLAN, MASTER TEST PLAN (MTP)

CDRL A020 - INTERFACE DESIGN DESCRIPTION (IDD)

CDRL A019 – TEST/INSPECTION REPORT

3.2.3.2 Environmental Qualification Testing (EQT)

The Contractor shall develop inputs to an Environmental Qualification Testing Plan(s) as part of each of the environmental tests required in the Job order. The Environmental Qualification Testing Plan will be written and executed by the Government Integrator with the Contractor’s support. The EQT shall be conducted by the Government after the CDR utilizing one or more of the EDMs or PPUs. The EDMs or PPUs will not be destroyed during testing.

3.2.3.3 Factory Acceptance Tests (FAT)

The contractor shall provide a Factory Acceptance Test Plan/Factory Verification Test Plan for Government review/approval prior to conducting testing on EDMs, PPU, and LRIP products/systems. The contractor shall coordinate with the Government technical point of contact to obtain Government approval of factory testing.

The Contractor shall conduct FAT on all EDMs, PPUs, and LRIP systems. The Contractor shall develop a FAT Procedure as part of the MTP and FAT Procedures to verify that the unit complies with the performance requirements. The Contractor shall generate a Test/Inspection Report documenting the results for each unit tested/delivered. In addition to the FAT procedures, and when applicable each LRU shall have its own acceptance procedure, such that spares can be accepted without relying on a higher assembly level test.

CDRL A017 – TEST PLAN, ACCEPTANCE TEST PLAN

3.2.4 LRIP

The Contractor shall manufacture LRIP hardware, software, firmware, middleware products and/or systems in accordance with the TDP provided, and as authorized per Job Order.. The Contractor shall procure materials, manufacture, assemble and conduct component and manufactured item/system testing necessary to assure the quality of the manufactured items. Any additional changes or deviations from the baselined TDP shall be submitted for approval via the Government Integrator’s Engineering Change Proposal (ECP) process.

3.2.5 PROGRAM MANAGEMENT

The Contractor shall establish and perform the necessary management procedures required to ensure that all work performed under the contract is planned and executed in a manner that will satisfy the requirements and achieve all management, technical, logistical, quality control, cost, and schedule objectives. The Contractor shall address, at a minimum, the following areas:

• Program Planning and Control Procedures

• Subcontractor Control Procedures

• Financial Management

• Data Management

• Quality Control Procedures

• Risk Management

• Management and Accountability for Government Furnished Equipment, Material, Information and Data.

The Contractor shall utilize a Program Office like function to manage all technical performance, reliability, maintainability, integrated logistic support, quality control, cost, schedule, and system/data delivery requirements of the contract. The Contractor shall provide a Contract Funds Status Report (CFSR).

CDRL A021 - CONTRACT FUNDS STATUS REPORT (CFSR)

3.2.5.1 Quality Assurance

The Contractor shall be in compliance with ANSI/ISO/ASQ 9001:2008 standards. The Contractor shall develop and continually update (as needed) a Quality Assurance Program Plan, to include a Quality Assurance Surveillance Plan (QASP). Once the Quality Assurance Program Plan is approved by the Government, the Quality Assurance Program Plan shall appropriately delineate a plan applicable to all requirements and standards and shall be used as a Quality Assurance (QA) measuring tool for work performed under this contract. The Quality Assurance Program Plan shall detail the processes, procedures, and metrics for assuring quality, such as; (1) Identification of roles, responsibilities and process owners, (2) Implementation of an effective root cause analysis and corrective action process, (3) Continuous process improvement to reduce costs and timelines, (4) Incorporating Lessons Learned, After Action Reports and customer satisfaction surveys into process improvement, and (5) Documentation of all outstanding deficiencies related to all phases of design, fielding, and logistics support. All manufacturing processes and quality systems procedures shall be in accordance with applicable ANSI/ISO Standards. The Contractor shall flow all quality system requirements down to subcontractors, sub-tier suppliers, and vendors.

CDRL A022 - QUALITY ASSURANCE PROGRAM PLAN

3.2.5.2 Meetings

The Contractor shall coordinate, schedule, prepare, conduct, facilitate and participate in reviews, meetings and conferences specified herein. The Contractor shall prepare a conference agenda and presentation materials for all meetings, reviews, and conferences identified in this SOW. At a minimum, the Contractor shall support meetings and reviews identified within the following paragraphs.

CDRL A023 - CONFERENCE AGENDA, MEETING AGENDA

CDRL A024 - PRESENTATION MATERIAL

3.2.5.3 Program Management Reviews (PMR)

PMRs shall be conducted in person or via Government approved meeting solutions with the Contractor providing a summary of their current program status as part of the presentation materials. This presentation shall contain the following main sections: Summary, Accomplishments, Current Status, Problem Areas, Risks and Mitigation Plans, Cost and Schedule Data, and Future Plans. The Contractor shall deliver a monthly Contractor’s Progress, Status, and Management Report (CPSMR). The CPSMR shall include but not be limited to:

• Status of significant/major design, development, testing, qualification, certification, production

• Key technical concerns and proposed changes;

• Action item status;

• Risk identification and mitigations strategies (to include Mitigation burn-down plans);

• Business, financial, cost and schedule metrics;

• Status of significant program events (e.g. Program Reviews);

• Failure reporting including analysis, risks and resolutions;

• Schedules for individual Deliveries, and equipment production/deliveries;

• Funding status;

• Problem identification and resolutions;

• Actual versus expected performance assessment.

CDRL A025 - CONTRACTOR’S PROGRESS, STATUS AND MANAGEMENT REPORT

3.2.5.4 Technical Interchange Meetings (TIM)

TIMs shall be scheduled as needed to focus on specific engineering or Program Management discussion during the execution of this contract.

3.2.5.5 Preliminary Design Review (PDR)

The Contractor shall conduct a system PDR to assess the state of the system architecture and preliminary system design for each Hardware (HW) and Software (SW) Configuration Item (CI). The Contractor shall conduct a dry run two weeks prior to the formal PDR event. The PDR shall identify all single source, sole source, and diminishing source(s). Prior to PDR, the Contractor shall conduct sub-component design reviews.

The entrance criteria for the PDR are the following:

• Documentation complete for functional design and test plans.

• Plans established for the next phase of system development.

• Technical review teams have reviewed and assessed appropriate CDRLs to satisfy the entrance and exit criteria.

Technical reviews and technical interchange meetings shall be scheduled between the Government technical design agent representatives and the Contractor development team representatives to adjudicate comments and clarify questions on the documents submitted for review and assessment prior to the PDR.

The exit criteria for the PDR are the following:

• Analysis definition complete:

All subsystems are identified.

Each subsystem, its interfaces, allocated functionality, and algorithms needed to implement the functionality are defined and accepted.

Environmental and system integration impacts are addressed in design.

All top-level components (SCs) are identified.

Each…