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

Amendment 0003:

1.) Updates language at Statement of Work sections 3.5.5, 3.1.7.2, 3.4.7 and CDRL A007.

2.) Removes Section L Small Business Approach, Small Business Participation Plan bullet 2 w hich reads, "A copy of the System for Aw ard Management profile for each of the firms included in the plan."

3.) Deletes clauses: 52.227-14 Alt V and 252.227-7022 4.) Adds clauses: 52.227-1 Alt 1, 52.227-3 Alt II (w ith language), 52.227-6, 52.227-9, 252.227-7015, 252.227-7019, 252.227-7025, 252.227-7027, 252.227-7028, and 252.227-7038.

5.) Revises the first line of the Basis of Aw ard language located in Section M to read "single aw ard contract" instead of "single contract".

6.) Provides Question and Answ er Set #3.

7.) Attachment J.1 revised to remove references to "TLM" in row s tw o and three and provides the WORD version of the Performance Specif ication for redlining purposes.

8.) Updates the Submission Address for Proposals and Sample Hardw are (section 2.1.1.1.8) in Section L.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 88

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

16C. DATE SIGNED

BY 16-Jan-2018

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 W91CRB-18-R-0001

X 9B. DATED (SEE ITEM 11)

15-Dec-2017

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 is extended, X 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

16-Jan-2018

CODE

ACC - APG - W91CRB

4310 BOOTHBY HILL AVE

ABERDEEN PROVING GROUND MD 21005-3013

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

24 September 2015

W91CRB-18-R-0001

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

AMENDMENT 0003

Amendment 0003: Summary of Revised Language 1.) Updates language at Statement of Work section 3.5.5 and CDRL A007.

a.) Section 3.5.5 Obsolescence Management. The contractor shall establish and maintain a proactive Diminishing Manufacturing Sources and Material Shortages (DMSMS) program using a risk-based approach for all items included in the end item deliverable including but not limited to electronics, COTS items, firmware, operating systems, and software. The contractor shall notify the Government of DMSMS items and materials that suppliers/vendors have declared obsolete or discontinued that may impact production or logistics support of systems, subsystems, software, or equipment. The contractor shall take appropriate corrective actions to mitigate obsolescence. The Prime contractor shall notify the Government within ten (10) days of determination that an item required in the end item deliverable of this contract poses a DMSMS issue, will become unavailable due to obsolescence, or is likely to within two (2) years after the end of the period of performance. This notification shall be made through submission of an Obsolescence Alert Notice IAW CDRL A007. This requirement shall be included in all subcontracts at all levels. The notice shall be given to the Government within five (5) days of the date of determination if the obsolete item is part of a deliverable under delivery order issued prior to determination that the item is obsolete.

b.) Section 3.1.7.2 Data Rights: "The Government’s rights in non-commercial technical data and software deliverables shall be governed by DFARS 252.227-7013 and DFARS 252.227-7014, respectively. The Government's rights in commercial technical data deliverables shall be governed by DFARS 252.227-7015. All non-commercial technical data and software deliverables shall be properly marked in accordance with the marking requirements set forth in DFARS 252.227-7013(f) and DFARS 252.227-7014(f), respectively. Technical data and software deliverables with non-conforming restrictive markings shall be rejected and corrected by the Contractor at the Contractor's expense, in accordance with DFARS 252.227-7013(h)(2) and DFARS 252.227-7014(h)(2), respectively."

c.) Section 3.4.7 Contractor Development Test (CDT). The contractor shall conduct CDT for the LLDR 3 in accordance with those tests identified as First Article Test (FAT) in the Requirements Verification Matrix (RVM) defined in Appendix J.3-G of the LLDR 3 PS and test procedures concurred on by the IPT, to demonstrate conformance to all requirements of the LLDR 3 PS

(CLIN 0001)…….”

d. The following language was added to CDRL A007:

"The contractor shall prepare and electronically submit Obsolescence Alert Notices in accordance with the SOW. The contractor shall notify the Government within ten (10) days of determination that an item required in the end item deliverable of this contract will become unavailable due to obsolescence, or is likely to within two (2) years after the end of the period of performance. The notice shall be given to the Government within five (5) days of the date of of determination if the obsolete item is part of a deliverable under delivery order issued prior to determination that the item is obsolete" and "The Obsolescence Alert Notice shall be used to provide notification from the contractor that a pending and/or emergent obsolescence issue exits."

2.) Deletes Section L Small Business Approach, Small Business Participation Plan bullet 2 which reads, "A copy of the System for Award Management profile for each of the firms included in the plan."

4.) Adds the following language to added clause 52.227-03 Alt II: "This patent indemnification shall be applicable to any patent claims or suits against the Government arising out of any activity occurring pursuant to this contract regarding the making, use, or sale of any items, or materials; or the practicing of any processes; which, in either case, have been sold or offered for sale by the contractor or its subcontractors hereunder to the public, in the commercial open market, and to such items, materials, or processes with relatively minor modifications thereto.”

8.) Updates the Submission Address for Proposals and Sample Hardware (section 2.1.1.1.8) in Section L. The address now reads Army Contracting Command – Aberdeen Proving Ground (ACC-APG) 6515 Integrity Court Building 4310 Aberdeen Proving Ground, MD 21005-3013 Attn: Karen Gibson – (410) 278-5405 Attn: Peter P. Buckless – (410) 306-1887

BLOCK 14 CONTINUED

Point of Contact: Karen Gibson at karen.gibson2.civ@mail.mil.

All other terms and conditions of solicitation W91CRB-18-R-0001 remain unchanged.

SECTION A - SOLICITATION/CONTRACT FORM

The following have been added by full text:

QUESTIONS AND ANSWERS #3

Solicitation W91CRB-18-R-0001 11 JAN 2018 Questions & Answers #3

Question 9:

Government Answer 9:

Attachment J.1 incorrectly specifies “TLM” for Target Acquisition Range (Day and Night). The Government shall assess all imagers provided as part of the Hardware Sample evaluation and will require modeling input and corresponding output decks for all imagers provided as part of the sample hardware.

Attachment J.1 will be updated accordingly.

Question 10:

Government Answer 10:

The Government concurs with the request to provide the LLDR 3 Performance Specification in a format that facilitates track changes.

Question 11:

Government Answer 11:

The requirement is for an HDMI format as stated in Performance Specification paragraphs 3.1.8 and 3.2.1.16 as the baseline. However, additional commercial standard video formats are allowable. The HDMI format shall originate from the TLM without the need for any external conversion methods.

Question 12:

Government Answer 12:

Attachment J.8 states “To be eligible for award and for VATEP to be applied, an offeror’s proposal must clearly demonstrate the capability and intention to meet ALL minimum threshold requirements”. Both the PAVAM and night celestial components are threshold requirements (Performance Specification, Table 1) and therefore shall be part of the TLE analysis relative to VATEP.

Question 13:

Government Answer 13:

Performance Specification paragraph 3.2.4.1 applies to meeting the day imager range performance during dusk, dawn and bright daylight. Day imager modeling predictions shall be based on the criteria listed in Performance Specification Tables 2 and 4.

Question 14:

Government 14:

Yes, it is acceptable to the Government, if there is a means to output uncompressed, high bit, depth digital imagery through a common port that can also output other imagery (like the final processed imagery) However, if done, it is possible that secondary hardware may be required in order to de-serialize the data for high bit, depth capture.

"Original" video needs to be post-nuc, post-bad pixel corrected, high bit depth imagery and, interfaces exist for capturing it through frame grabbers at full frame rate.

Question 15:

Government Answer 15:

The Government confirms that “an optical field of view is one that does not use electronic interpolation to create samples for the video output of the display.” An optical field of view shall be used to meet the threshold day and night target acquisition ranges listed in Performance Specification Table 1. “Additional image processing techniques may be used to extend ranges beyond optical based threshold values, and to mitigate the impact of atmospheric turbulence” as stated in the Performance Specification Table 1.

Question 16:

Government Answer 16:

"Primary mission cable" is defined as the connection of power and data communications between the LLDR 3 modules, and will be dependent on the offeror's design (see Performance Specification para 3.1.2. Modularity). Note that separate cables (not an integral part of either the TLM or one of the modules being connected to it) for power or data communications between modules shall not be used.

Question 17:

Government Answer 17:

The remote fire cable and remote fire/control cable are the same item with the minimum functions listed in Performance Specification paragraph 3.1.3.

Question 18:

Government Answer 18:

Contractor Development Test (CDT) is intended to have the same test requirements as outlined in the First Article Test (FAT) column of the Requirements Verification Matrix (RVM).

Therefore, Section C, paragraph 3.4.7 of the LLDR 3 Statement of Work (SOW) will be changed to read as follows:

“3.4.7 Contractor Development Test (CDT). The contractor shall conduct CDT for the LLDR 3 in accordance with those tests identified as First Article Test (FAT) in the Requirements Verification Matrix (RVM) defined in Appendix J.3-G of the LLDR 3 PS and test procedures concurred on by the IPT, to demonstrate conformance to all requirements of the LLDR 3 PS

(CLIN 0001). …….”

Question 19:

Government Answer 19:

No, the requirement stands as stated; meaning, a second optical FOV is required.

Question 20:

Government Answer 20:

No, the requirement stands as stated; meaning, a second optical FOV is required.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

The information below pertains to solicitation for W91CRB-18-R-0001 Lightweight Laser Designator Rangefinder 3 (LLDR 3) Systems.

Recipients shall:

i. Read and comply with distribution markings.

ii. Direct all requests for distribution to other parties to Mr. Peter P. Buckless at peter.p.buckless.civ@mail.mil.

iii. Destroy the documents once they are no longer required to support this solicitation.

Recipients shall NOT: Redistribute the SOW outside of Distribution Statement D, of the program security classification guide, to include subsidiaries and subcontractors within the corporate structure for this program.

In the event of a conflict between the text of this document and the references cited herein, the text of this document takes precedence. Nothing in this document supersedes applicable laws and regulations unless a specific exemption has been obtained.

When the term “days” is used throughout this document, it shall refer to calendar days, unless explicitly specified as business days. All deliveries shall be made on a business day and Close of Business (COB) is defined as 16:00 (Eastern Standard Time).

Special Instructions

1. This solicitation is for the design, integration, testing, qualification and production of LLDR 3, spares, associated data items, and contractor maintenance support tasks.

DISTRIBUTION STATEMENT A: Approved for public release. Distribution is unlimited.

STATEMENT OF WORK

Lightweight Laser Designator Rangefinder 3 (LLDR 3) Production and Maintenance

1.0 Scope. This procurement is for the production of the Lightweight Laser Designator Rangefinder 3 (LLDR 3), associated spare and repair parts, maintenance, and system technical support. This Statement of Work (SOW) establishes the design, fabrication, performance, test, manufacture, and acceptance requirements for the LLDR 3. The LLDR 3 is a man-portable, crew-served, ground-based targeting device that provides the ability of precision, long range, target acquisition and target location, laser designation and laser spot imaging with an all-weather 24/7 precision targeting capability. The proposed design is required to have three (3) separate modules including a Targeting Locator Module (TLM), long-range Thermal Imaging Module (TIM) and a Laser Designator Module (LDM). The planned timeline for this effort is one hundred twenty (120) months. The scope of the effort includes initial design and integration of fifteen (15) units, fully tested and qualified for production no later than twenty-four (24) months after contract award, followed by initial production and Full Rate Production (FRP) of the LLDR 3.

1.1 Contract Data Requirements List (CDRL). CDRLs may have corresponding Data Item Descriptions (DID), which specify specific instructions on deliverables from the contractor. The contractor shall comply with the CDRLs and associated DIDs.

2.0 Applicable Documents. The contractor shall adhere to the following documents that form parts of this SOW to the extent specified herein. Unless otherwise specified, the version of each document in effect at the time of solicitation release shall apply. The Government may tailor the required documentation as appropriate for the LLDR 3 program in order to streamline and improve efficiencies as needed, without superseding applicable laws and regulations.

2.1 Government Documents. The following specifications, standards, and handbooks may be downloaded from the Army Publishing Directorate website at http://armypubs.army.mil/ the ASSIST (Acquisition Streamlining and Standardization Information System) Quick Search website at http://quicksearch.dla.mil/ and the DoD Issuances website at http://www.esd.whs.mil/Directives/issuances/dodi/

Number Title Date N/A Performance Specification, Lightweight Laser

Designator - Rangefinder (LLDR 3)

TBD

N/A

Combat Developer Failure Definition and Scoring Criteria (FDSC) for the Lightweight Laser Designator Rangefinder (LLDR) Increment I

15 November 1999

N/A Security Classification Guide for AN/PED-1, AN/PED-1A, AN/PED-1B Range Finger- Target Designator, Laser

16 May 2013

AR 381-12 Threat Awareness and Reporting Program 1 June 2016

Number Title Date AR 530-1 Operations Security (OPSEC) 26 September 2014 AR 750-1 Army Materiel Maintenance Policy 3 August 2017 DI-ADMN-81306 Program Protection Implementation Plan (PPIP) 25 January 1993

DI-ATTS-802848

Notice 1

Test Program Set Documentation (TPSD) 6 July 2017

DI-ILSS-80739

Notice 1

Depot Maintenance Study 28 June 2017

DI-MGMT-81808 Contractor’s Risk Management Plan 21 April 2010

DI-MGMT-81861A

Integrated Program Management Report

(IPMR)

16 September 2015

DI-NDTI-80566A Test Plan 14 November 2006 DI-NDTI-80603A Test Procedure 14 November 2006

DI-NDTI-80809B

Notice 1

Test/Inspection Report 27 August 2014

DI-PSSS-81873A Level of Repair Analysis (LORA) Input Data 22 July 2014 DI-SAFT-80102C Safety Assessment Report (SAR) 12 June 2015 DI-SESS-80255A Failure Summary & Analysis Report 19 December 2014 DI-SESS-81715 Provisioning Parts List (PPL) 29 November 2006 DI-SESS-81759A Logistics Product Data Summaries 21 May 2013

DI-SESS-81785A

Systems Engineering Management Plan

(SEMP)

29 September 2015

DI-SESS-81874 Engineering Data for Provisioning (EDFP) 7 December 2012 DI-SESS-81875 Configuration Management Plan (CMP) 28 February 2013 DoD 5220.22-M With Change 2

National Industrial Security Program Operating Manual

18 May 2016

MIL-DTL-14072F

Finishes for Ground Based Electronic Equipment

13 August 2013

MIL-PRF-32070A

Notice 1

Test Program Sets 11 October 2016

MIL-PRF-49503C

General Style and Format, Test Program Sets for Automatic Test Equipment

18 July 2013

MIL-STD-129R Military Marking for Shipment and Storage 18 February 2014

MIL-STD-130N

with Change 1

Identification Marking of US Military Property 16 November 2012

MIL-STD-881C

Work Breakdown Structures for Defense Materiel Items

3 October 2011

MIL-STD-2073-1E

with Change 1

DoD Standard Practice for Military Packaging 7 January 2011

MIL-STD-31000A Technical Data Packages 28 February 2013

MIL-STD-38784A

with Change 1

Standard Practice for Manuals, Technical:

General Style and Format Requirements

11 July 2016

MIL-STD-40051-

2C

Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)

15 December 2015

MIL-HDBK-502A Product Support Analysis 8 March 2013

Number Title Date

MIL-HDBK-1222

Guide to the General Style and Format of U.S.

Army Work Package Technical Manuals

15 December 2015

MIL-HDBK-2361C

Army Digital Publications Development Implementation Guide

15 January 2012

2.2 Non-Government Documents. Are found on the ANSI, ASME, IEEE, ISO, and SAE International websites.

ANSI/NCSL-

Z540.3-2006 (R2013)

Requirements for the Calibration and Measurement of Test Equipment

26 March 2013

ASME Y14.5-2009 Dimensioning and Tolerancing 27 March 2009

ASME-Y14.24 Types and Applications of Engineering Drawings

5 April 2013

EIA 748-C Earned Value Management Systems 1 March 2013

IEEE STD

15288.1-2014

IEEE Standard for Application of Systems Engineering on Defense Programs

15 May 2015

IEEE STD

15288.2-2014

IEEE Standard for Technical Reviews and Audits on Defense Programs

15 May 2015

ISO 15288:2015 Systems and Software Engineering – System Life Cycle Processes

15 May 2015

ISO/IEC/IEEE

24748-4:2016

Systems and Software Engineering Life Cycle Management – Part 4: Systems Engineering Planning

15 May 2016

ISO 9001:2015 Quality Management Systems – Requirements 23 September 2015 ISO 10012:2003 Measurement Management Systems -

Requirements for Measurement Processes and Measuring Equipment

15 April 2003

SAE GEIA-STD-

0007B

Logistics Product Data 1 May 2013

SAE GEIA-STD-

Reliability Program Standard for Design, Development and Manufacturing

1 August 2008

3.0 Description and Requirements. The LLDR 3 is a modular, tripod mounted, day/night, all-weather, target observation, location, and designation system to be used by Forward Observers (FO) as part of a Fire Support Team (FIST), Scouts, and others to execute “call-for-fire” missions including those for precision guided, laser guided, and all other munitions.

Additionally, the LLDR 3 will be used to assist in guiding laser seeker equipped aircraft for selected high-value targets. When connected to a Forward Entry System (FES), target information will be forwarded to higher authority.

The contractor shall design, fabricate, test, and deliver LLDR 3 and identified spare and/or repair parts in accordance with this SOW, specific delivery orders, and delivery schedules. The contractor shall ensure that the delivered LLDR 3 system components comply with all of the requirements of the LLDR 3 Performance Specification (PS). The contractor shall provide maintenance and repair support for the LLDR 3 in accordance with the Maintenance Planning and Management paragraphs of this SOW.

3.1 Program Management.

3.1.1 Program Management Objective. The contractor shall manage all aspects of the contract with respect to schedule, system design, development, engineering, fabrication, configuration management, risk management, test, technical performance, and cost. The contractor shall provide timely programmatic, schedule and performance information to the Government throughout the life of the contract. The contractor shall maintain a program management structure with a single point of contact for program oversight. The contractor shall perform administrative, technical, business, and financial management functions during the course of this effort to include organizing, directing, and controlling actions, reporting status, recommending solutions, and resolving issues to ensure the successful execution of efforts needed to achieve contract objectives. The contractor shall implement processes for the following:

3.1.1.1 Program Planning, Management, and Control. The contractor shall manage and participate in necessary business and administrative planning, quality assurance, test planning, organizing, directing, coordination, and approving actions designated to accomplish overall program objectives. The contractor shall ensure that only technically qualified personnel with the proper security clearances and training support the program.

3.1.1.2 Contractor and Subcontractor Management. The contractor shall establish and maintain a subcontract management program. The contractor shall facilitate Government and subcontractor discussions and activities as requested by the Government.

3.1.1.3 Earned Value Management System (EVMS). In the performance of this contract, the contractor shall use an EVMS that complies with the EVMS guidelines in EIA 748-C.

3.1.1.4 Integrated Baseline Review (IBR). The contractor shall host an IBR as soon as possible after establishing an integrated Performance Measurement Baseline (PMB), but not later than six

(6) months after contract award. The IBR is used to achieve a mutual understanding of the baseline plan, cost, and schedule risk, the underlying management processes used for planning and controlling the program, and the earned value methods used to accurately status contract cost, schedule, and technical performance. Subsequent IBRs will be held following all major changes to the baseline. The contractor shall flow down the IBR requirement to those subcontractors that meet the applicable thresholds for EVMS. The contractor leads the IBR with subcontractors, with participation from the Government.

3.1.2 Integrated Program Management Report (IPMR). The objective of the IPMR is to provide a tool that provides sufficient detail and insight to the Government concerning the current contract status and to project future contract performance. The IPMR data elements must reflect the output of the contractor's EIA 748-C compliant system, where applicable. The contractor shall prepare and submit the IPMR in accordance with CDRL-B001.

3.1.3 Handling or Access to Classified Information. The contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified

“Confidential,” “Secret,” or “Top Secret” and requires contractors to comply with the Department of Defense Security Agreement (DD Form 441), the National Industrial Security Program Operating Manual (NISPOM) (DoD 5220.22-M) and any revisions thereto.

3.1.3.1 DoD Contract Security Classification Specification (DD 254). The Government will provide the contractor with a DD 254 in order to convey security requirements, classification guidance and provide handling procedures for classified material received and/or generated on a classified contract. The DD 254 will allow the contractor to use FOUO information, the LLDR 3 Security Classification Guide (SCG), receive and generate classified material (at the SECRET level), and be authorized to use the services of Defense Technical Information Center (DTIC) or other secondary distribution center. Any information (classified or unclassified) pertaining to this contract shall not be released for public dissemination except as provided by the NISPOM or unless it has been approved for public release by appropriate U.S. Government authority.

Proposed public release shall be submitted to the Government for approval prior to release.

Safeguarding FOUO information shall be IAW the LLDR 3 SCG.

3.1.3.2 Verification Process. The contractor shall implement an employee verification process, whether through background checks or other similar processes, provide a written explanation of how the verification process was completed and attest to the trustworthiness of the workforce within forty-five (45) days after contract award.

3.1.4 Antiterrorism (AT) / Operational Security (OPSEC). The contractor shall develop an OPSEC Standard Operating Procedure (SOP)/Plan within ninety (90) days of contract award (and updated annually thereafter), to be reviewed and approved by the responsible Government OPSEC officer. The contractor shall use the provided LLDR 3 SCG in developing the SOP/Plan. The SOP/Plan shall specify the Government’s critical information, why it needs to be protected, where it is located, who is responsible for it and how to protect it. In addition, the contractor shall identify an individual who shall be an OPSEC Coordinator. The contractor shall ensure that this individual becomes OPSEC Level II certified. The Government will evaluate contractor OPSEC performance on an annual basis or as conditions warrant.

3.1.5 Threat Awareness Reporting Program. Contractor personnel working on this contract shall attend live TARP training conducted by a CI agent or other trainer as specified in paragraph 2–4 of AR 381-12 at least annually and report threat-related incidents, behavioral indicators, and other matters of counterintelligence (CI) interest specified in chapter 3, to the facility security officer, the nearest military CI office, the FBI, or the Defense Security Service.

3.1.6 Correspondence Transmission. The contractor shall submit written program correspondence and documentation viewable with MS Office products for electronic dissemination to members of the IPT. The preferred method of file submission is via e-mail. If the contractor proposes an alternative method for correspondence transmission, the contractor shall manage such distribution at no cost to the Government. Non-email alternatives may be allowed on a case-by-case basis, with Government approval.

3.1.7 Data Submissions. The contractor shall meet all data submissions on time as defined in the associated CDRLs. Data items shall be submitted to the Government via electronic media (on-line access, e-mail, compact disc). The format shall be Microsoft Word for text documents, Microsoft Excel for spreadsheets, Microsoft Power Point for graphic presentations, Microsoft Project for schedules, and Pro/Engineer for drawings, unless otherwise approved by the Government. Use of Adobe format is permitted when required to facilitate delivery and approved by the Government.

3.1.7.1 On-Line Technical Information. It is the intent of the Government to gain on-line access to contractor maintained data, configuration files, to include drawings down to the spare parts level, and information supporting the LLDR 3 program. The type of information to be available on-line shall be concurred to by the IPT prior to its implementation. The most recent version of all data shall be made available within five (5) business days of being updated. The contractor shall allow the Government the capability of retrieving, on-line, all current and modified versions of documentation, as well as uploading documentation to facilitate an information sharing medium. Classified data shall be provided on magnetic or optical media. Classified data shall be handled in accordance with DOD 5220.22-M and DD Form 254, Security Classification Guide, attached to the contract. Any restrictions on the use of the electronic data shall be as prescribed in the data rights clauses of this contract.

3.1.7.1.1 Common User File Management System. The contractor shall establish a common user file management system, concurred with by the IPT, to be initially presented at the PAC review.

The file management shall be reviewed at each IPT meeting.

3.1.7.1.2 File Sharing Library. The contractor shall establish a specific file-sharing library entitled “Deliveries to the Government,” containing separate sub-files named exclusively for each contract CDRL, by CDRL number and deliverable title (e.g., LLDR 3 CDR Report). The contractor shall post all submitted deliverable drafts, Government comments and deliverable final submissions in the appropriately named CDRL folder. This electronic CDRL library shall be the sole recognized file sharing point for electronic copy deliverables for the contract.

3.1.7.1.3 File Naming Convention. The contractor shall, for all deliverables, establish and enforce a file naming convention that requires a standard format for naming the basic submitted file, and all subsequent serial revisions/versions separately, by basic filename, serial revision/version number and date. The file naming convention shall be defined/established as agreed to by the IPT no later than (NLT) thirty (30) days after PAC review.

3.1.7.2 Data Rights. The Government’s rights in non-commercial technical data and software deliverables shall be governed by DFARS 252.227-7013 and DFARS 252.227-7014, respectively. The Government's rights in commercial technical data deliverables shall be governed by DFARS 252.227- 7015. All non-commercial technical data and software deliverables shall be properly marked in accordance with the marking requirements set forth in DFARS 252.227-7013(f) and DFARS 252.227- 7014(f), respectively. Technical data and software deliverables with non-conforming restrictive markings shall be rejected and corrected by the Contractor at the Contractor's expense, in accordance with DFARS 252.227-7013(h)(2) and DFARS 252.227-7014(h)(2), respectively.

3.1.8 Program Protection. The contractor shall assist and support the Government in performing a Critical Functional Analysis (CFA) and Critical Program Information Assessment (CPIA) for the LLDR 3 system in order to identify Critical Components and Critical Program Information (CPI). The Government will provide the contractor with written guidance reference implementation of countermeasures to protect CPI. Additionally, the contractor shall implement Government specified Supply Chain Risk Management Countermeasures to safeguard Government identified Critical Components. The contractor shall provide a Program Protection Implementation Plan (PPIP) (CDRL B004) within thirty (30) days of receiving countermeasures.

3.2 Systems Engineering.

3.2.1 Systems Engineering Objective. The objective of systems engineering under this contract is to ensure the contractor successfully integrates all of the necessary technologies into the LLDR 3 to meet the requirements of the LLDR 3 PS. The contractor shall tailor their systems engineering processes, documentation, and plans to meet the requirements of this SOW.

3.2.2 Systems Engineering Management Plan. The contractor shall deliver an integrated Systems Engineering Management Plan (SEMP) that describes the contractor’s processes and resources to incorporate Systems Engineering (SE) practices to build, test, deliver and support the LLDR 3 (CDRL-A001). The SEMP is a living document to be updated when technical plans change, systems engineering activities complete, existing technical risks are mitigated or substantially change, new technical risks emerge, and any reason that a significant change is needed to the contractor’s approach. The contractor shall use IEEE 15288.1:2014, Section 6.3.1.4, Project Planning Process Outputs, when developing the SEMP. Guidance for SEMP attributes and elements can be found in ISO/IEC/IEEE 24748-4:2016. The SEMP shall discuss how the contractor operates and conforms to IEEE 15288.2-2014 for technical reviews and audits. The contractor shall prepare and submit the initial SEMP NLT thirty (30) days after contract award and provide an update at the Critical Design Review (CDR).

3.2.2.1 Work Breakdown Structure (WBS). The contractor shall update the proposed WBS, IAW MIL-STD-881, see CDRL-B001. The WBS shall be extended to the lowest appropriate level required by the Government to provide adequate management, surveillance, and performance measurement and shall be the basis for tracking, controlling, measuring and reporting all costs, risks and schedule performance under this contract. The WBS shall be used in developing the Integrated Master Schedule (IMS).

3.2.3 Integrated Master Schedule. The contractor shall update the proposed IMS each month throughout the period of performance of the contract in accordance with CDRL-B001. The IMS submitted with the proposal shall serve as the baseline at the start of the effort. The purpose of the IMS is to provide a common schedule by which the contractor and Government can effectively manage the program. It shall indicate major tasks, major sub-tasks, milestones, program reviews, test dates, deliverables, critical path, and other mutually agreed upon items.

3.2.4 Risk Management/Mitigation Plan. The contractor shall conduct and document an in-house risk management program that identifies, analyzes, tracks, and plans alternatives to reduce schedule and technical risks, see CDRL-B002. The plan shall discuss system risk management (technical, schedule, cost). Risk items and their mitigation efforts shall be presented at formal reviews and on an as needed basis during other meetings. The risk management/mitigation plan shall include, but is not limited to, risk description, rating (stoplight or low, medium, high), program impact, mitigation strategy, action officer, schedule and status. The contractor shall include monthly risk updates as part of CDRL-B001.

3.2.5 Integrated Product Team (IPT). The goal of the IPT is to resolve many issues and concerns at the lowest level possible and to expeditiously escalate issues requiring resolution at higher levels. On a quarterly basis, the Government and contractor will conduct an overarching IPT meeting, while smaller groups conduct business related to their specialty in Working IPTs, led by Government and contractor co-chairs.

3.2.5.1 IPT Overview. The contractor shall incorporate an IPT discipline into the LLDR 3 program. The objectives of the IPT are to foster an open, shared data/information environment and to implement a disciplined systems engineering approach to influence the design, manufacturing, testing, logistics support, and on-schedule delivery of specification compliant units, while striving to continuously improve the various Government/contractor processes and reduce system life cycle cost. The IPT shall also complete the following additional actions throughout the life of the contract:

a. Hold IPT reviews.

b. Use risk management techniques to document, track, and manage program areas of risk.

c. Review/concur on program documentation.

d. Review follow-on qualification testing with the goal of reducing repetitive testing.

e. Review/concur on all Failed Item Analysis Reports (FIARs)/Engineering Change

Proposals (ECPs)/Waivers/Deviations.

f. Review the Integrated Master Schedule.

3.2.5.2 IPT Membership. The IPT shall consist of Government and contractor personnel associated with the LLDR 3 program and related efforts. The U.S. Army LLDR 3 Assistant Product Manager (APM) will co-chair the IPT with the associated contractor counterpart. The IPT chairpersons will work in good faith to reach agreement on all items requiring IPT approval.

If agreement cannot be reached between the co-chairpersons, then the issue(s) will be escalated per each organization’s chain of command. The co-chairs shall define the membership of the IPT at the PAC.

3.2.5.3 IPT Reviews. The contractor shall participate in and support IPT Reviews at approximately 120-day intervals throughout the life of the contract, or as agreed to by the IPT chairpersons. IPTs include major program management meetings such as design and test readiness reviews. The first IPT Review shall be conducted on or about thirty (30) days after the PAC. IPT reviews may be conducted as teleconferences or video-teleconferences (VTCs) if mutually agreed upon by the IPT co-chairpersons; however face-to-face meetings are preferred to be at the contractor’s facility. With Government approval, IPT reviews may be relaxed in frequency, and/or may be combined with significant meeting events. The IPT co-chairs will develop an agenda for all reviews/meetings. IPT reviews shall provide a working level forum to identify, discuss, and resolve issues that could affect the system performance, design, production, testing, logistics support, system deliveries, life cycle cost, and program schedule. IPT reviews will also address the status of all Government Furnished Equipment. The IPMR and Risk Management/Mitigation Plan shall also be reviewed at these meetings, as well as an agenda approved by the Government that includes items such as: deliverable status, test status, and Technical Manual (TM) development status.

3.2.6 Working Integrated Product Teams (WIPT). The LLDR 3 APM will designate chairs to lead WIPTs. The WIPTs will include separate functional area for Acquisition, Cost, Product Support Management, Technical, Quality Assurance, and Test & Evaluation (T&E). The contractor shall designate their respective subject matter expert for relevant WIPT participation.

3.2.6.1 WIPT Reviews. The contractor shall participate in and support WIPT reviews as defined in the contractor’s proposal, IMS, throughout the life of the contract, or as agreed to by the IPT chairpersons. WIPT reviews shall provide a working level forum to identify, discuss, and resolve issues that could affect the system performance, design, production, testing, logistics support, system deliveries, life cycle cost, and program schedule.

3.2.6.2 Informal Reviews. The contractor shall support WIPT reviews in order to resolve issues cited by the IPT, and to prepare for IPT reviews. The contractor shall be available for informal reviews and Government visits in addition to the WIPT reviews. The WIPT will, whenever possible, attempt to minimize travel costs for both parties by utilizing teleconferences or VTCs to conduct these informal reviews. WIPT will meet frequently and informally in order to develop strategies, tailor documentation, resolve issues and promote working progress of the program.

WIPT provides status and informs the IPT prior to IPT reviews.

3.2.6.3 Formal Reviews.

3.2.6.3.1 Post Award Conference. The contractor shall host a PAC within thirty (30) days of contract award to ensure there is a mutual understanding of the terms, conditions, requirements and risks among all parties responsible for the management and performance of the contract (Contract Line Item Number (CLIN) 0001). The contractor shall provide evidence/artifacts to satisfy the following PAC exit criteria. IPT agreement and Government approval will constitute verification that the contractor has:

a. Accepted all contract terms, conditions, and contract requirements.

b. Verified requirements for on-line technical information.

c. Properly conducted public announcements.

d. Verified configuration management plan.

e. Updated Risk Identification, Risk Analysis and Risk Mitigation Plan.

f. Prepared and submitted initial SEMP

3.2.6.3.2 Preliminary Design Review (PDR). The contractor shall host a PDR within three (3) months after contract award to provide a preliminary assessment of the design of the LLDR 3 (CLIN 0001) and submit a PDR report (see CDRL B001). The contractor shall demonstrate evidence/artifacts to satisfy the following PDR exit criteria. IPT agreement and Government approval will constitute verification that the contractor has:

a. Conducted a system trade analysis.

b. Verified all required system performance requirements for Qualification proposed for IPT review.

c. Ensured proposed design, as disclosed, satisfies the LLDR 3 System Level Performance and Component specifications.

d. Summarized status of the reliability and maintainability engineering design activities

(i.e., allocations, models, block diagrams, predictions, anticipated failure modes and effects).

e. Proposed system allocated baseline to enable the design to proceed with proper configuration management.

f. Proposed adequate processes and metrics for the program to succeed.

g. Proposed human integration design factors in the overall system design.

h. Identified program risks and established risk mitigation plan for all functional areas (e.g.

SE, Program Management, Quality/Test, Reliability, Logistics, Manufacturing).

i. Ensured program schedule is executable (technical, cost, risk).

j. Ensured program is staffed properly.

k. Identified all required unique tooling and test equipment required to produce and test the

LLDR 3.

l. Documented presentation of component design tolerances and compatibility between components.

m. Identified of long lead parts and suppliers.

n. Provided an initial system and data architecture.

o. Ensured draft test plans and procedures are developed and ready for submission for

Government review.

p. Updated risk assessment for all functional areas (e.g. SE, Program Management, Quality/Test, Reliability, Logistics, Manufacturing, System Architecture), and mitigating strategies are identified.

q. Updated program development schedule including fabrication, test and evaluation, firmware coding, critical path drivers.

r. Established system initial product baseline.

s. Updated Logistics Support Plan updating program sustainment development efforts and schedules based on current budgets, test evaluation results and firm supportability design features.

3.2.6.3.3 Critical Design Review (CDR). A CDR shall be hosted by the contractor no more than six (6) months following the contract award to review the final component and system designs (CLIN 0001). The contractor shall submit a system level CDR report (see CDRL B001). The contractor shall demonstrate evidence/artifacts to satisfy the following CDR exit criteria. IPT agreement and Government approval will constitute verification that the contractor has:

a. Ensured all required system performance for Qualification is fully decomposed and defined in the functional baseline.

b. Updated design, as disclosed, satisfies the LLDR 3 System Level Performance and Component specifications.

c. Updated status of the reliability and maintainability engineering design activities (i.e., allocations, models, block diagrams, predictions, anticipated failure modes and effects).

d. Established and documented system allocated baseline to enable the design to proceed with proper configuration management.

e. Established adequate processes and metrics for the program to succeed.

f. Included human integration design factors in the overall system design.

g. Identified program risks and established risk mitigation plan, and are on track, for all functional areas (e.g. SE, Program Management, Quality/Test, Reliability, Logistics, Manufacturing).

h. Ensured program schedule is executable (technical, cost, risk).

i. Ensured program is staffed properly.

j. Provided traceability of requirements/specifications to testing is clear in the allocated baseline.

k. Developed presentation of component design tolerances and compatibility between components.

l. Identified long lead parts and suppliers.

m. Provided an initial system and data architecture.

n. Updated program development schedule including fabrication, test and evaluation, firmware coding, critical path drivers.

o. Identified all exposed materials of the design (to include ancillary items) to support the

Chemical, Biological, Radiological, and Nuclear (CBRN) Contamination Survivability analysis.

p. Ensured draft test plans and procedures are updated and delivered for Government review.

q. Established system initial product baseline.

r. Updated Logistics Support Plan updating program sustainment development efforts and schedules based on current budgets, test evaluation results and firm supportability design features.

s. Presented a draft Production Manufacturing Plan.

t. Updated SEMP.

3.2.6.3.4 Test Readiness Review. The contractor shall conduct a Test Readiness Review prior to initiating contractor qualification and First Article Test (FAT), see CDRL-A003. The purpose of the TRR is to assure the Government that the contractor has the plans, procedures, personnel, material, and facility resources to test the LLDR 3. The contractor shall provide evidence to assess the system for development maturity, cost/schedule effectiveness and risk to determine readiness to proceed to formal testing. IPT agreement and Government approval will constitute verification that the contractor has:

a. Completed and approved test plan(s).

b. Completed and approved test procedures.

c. Completed identification and coordination of required test resources, to include roles and responsibilities of all test participants identified.

d. Provided test/inspection data on subsystem and components verifying that the specifications have been met for those items.

e. Identified risk levels and mitigation plans acceptable to the program leadership.

f. Ensured configuration of the systems under test has been identified; both hardware and software, and all units and test are of the same configuration.

g. Ensured all action items from previous technical and design reviews have been dispositioned and closed.

3.2.6.3.5 LLDR 3 Production Readiness Review (PRR). The contractor shall host a Production Readiness Review in conjunction with the Government at the contractor’s facility no more than twenty-one (21) months after contract award (CLIN 0001). The purpose of the PRR is to assure the Government that the LLDR 3 design is finalized and that the contractor has the personnel, material, and facility resources to produce the LLDR 3. The contractor shall prepare and submit the PRR presentation material in contractor format (see CDRL-A004). The contractor shall fully address the following criteria. IPT agreement and Government approval will constitute verification that the contractor has:

a. Ensured their design is ready for production and meets Manufacturing Readiness Level

(MRL) 9.

b. Confirmed that no unacceptable production risks (cost, schedule, performance) exist for prime and subcontractors.

c. Established and documented the system product baseline.

d. Established adequate processes and metrics for the program to succeed.

e. Presented a final production manufacturing plan.

3.2.6.4 LLDR 3 Production Phase. The contractor shall deliver initial production systems for use in a FAT event to commence within four (4) months of delivery order award and for an Operational Test and Evaluation (OT&E) event to commence within nine (9) months of delivery order award. Initial production systems off the production line shall be required to support the FAT event. The Government anticipates deliveries of up to 29 LLDR 3 units per month (CLINs 0003-0012).

3.2.6.4.1 Production Systems. The contractor shall provide LLDR 3 systems, components, and spare parts that meet the requirements in the LLDR 3 PS.

3.2.6.4.2 Production Management. The contractor shall track the status of LLDR 3 production management with critical suppliers, inventory control, resources and schedules, and material balances. This information shall be made available for Government review upon request. If the contractor determines a need to change suppliers, they shall notify the Government in advance, develop a requalification plan and obtain approval prior to implementing those changes.

3.2.6.4.3 Production Manufacturing Plan. The contractor shall provide the Production…