W15QKN18R0037-0002.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of

2. Amendment/Modification No.

3. Effective Date

4. Requisition/Purchase Req No.

5. Project No. (If applicable)

6. Issued By Code 7. Administered By (If other than Item 6) Code

8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)

9A. Amendment Of Solicitation No.

9B. Dated (See Item 11)

10A. Modification Of Contract/Order No.

10B. Dated (See Item 13) Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

Offers 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 ____________ copies of the amendments: (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 ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS

It Modifies The Contract/Order No. As Described In Item 14.

A. This Change Order is Issued Pursuant To: 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 data, 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.)

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)

16A. Name And Title Of Contracting Officer (Type or print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed

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

NSN 7540-01-152-8070

PREVIOUS EDITIONS UNUSABLE

30-105-02 STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

SEE SCHEDULE

X

Firm Fixed Price

0002 2018APR12

W15QKN

ARMY CONTRACTING COMMAND - NJ

PICATINNY ARSENAL, NJ 07806-5000

PAUL GIOVANNOLI

EMAIL: PAUL.GIOVANNOLI.CIV@MAIL.MIL

W15QKN-18-R-0037

2018MAR23

X

X 2018APR30 03:30pm

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 46

CONTINUATION SHEET

Reference No. of Document Being Continued Page of

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION A - SUPPLEMENTAL INFORMATION

Buyer Name: PAUL GIOVANNOLI

Buyer Office Symbol/Telephone Number: ACC-NJ-IC/(973)724-2136

Type of Contract 1: Firm Fixed Price

Kind of Contract: Supply Contracts and Priced Orders

*** End of Narrative A0000 ***

GENERAL INFORMATION TO OFFERORS OR QUOTERS

1. Responses must set forth full, accurate and complete information as required by this solicitation (including attachments). Fill-ins are provided on Standard Form (33), and other solicitation documents. Examine the entire solicitation carefully. The penalty for making false statements is prescribed in 18 U.S.C. 1001.

2. Responses must be plainly marked with the Solicitation Number and the date and local time set forth for bid opening or receipt of proposals in the solicitation document.

3. Information regarding the timeliness of response is addressed in the provision of the solicitation entitled either

Late Submission, Modification and Withdrawal of Bid or Instructions to Offerors Competitive Acquisitions.

4. Procurement Information (use one of the below in your solicitation)

_X_ This Procurement is unrestricted (use if soliciting Full and Open Competition)

5. Issuing Office

U.S. Army Contracting Command - New Jersey ATTN:

Office Symbol: ACC-NJ-IC __

Buiding 10 Phipps Road______________________

Picatinny Arsenal,NJ 07806-5000 Email: paul.giovannoli.civ@mail.mil ___

6. Point of Contact for Information: Name: Paul Giovannoli _______________

Title: Contract Specialist ___________________

Email: paul.giovannoli.civ@mail.mil

Phone: 973-724-2136

DISCLOSURE OF UNIT PRICE INFORMATION

This constitutes notification pursuant to Executive Order 12600, Pre-Disclosure Notification Procedures for Confidential Commercial

Information (June 23, 1987), of our intention to release unit prices in response to any request under the Freedom of Information Act, 5 USC 552. Unit price is defined as the contract price per unit or item purchased. We consider any objection to be waived unless the contracting officer is notified of your objection to such posting prior to submission of initial proposals.

*** END OF NARRATIVE A0002 ***

The purpose of Amendment 0002 is to:

1. Extend the proposal submission date from 23 April 2018 to 30 April 2018.

2. Establish a deadline of 23 April 2018 for all RFP questions.

3. Answer questions from Industry in Section A.

4. Update Sections A, C, L and M based on changes resulting from the questions from Industry.

2 46

W15QKN-18-R-0037 0002

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

*** END OF NARRATIVE A0004 ***

Amedment 0002 Questions from Industry

1. RFP Sec A, Narrative A0002, Para No. 1 page 2

States the following - (insert form numbers) should there be form numbers within the parentheses?

A1. Yes, the form numbers 33 should have been included in there. Section A has been updated to include this update.

2. RFP Sec C SOW, Para No C.8.2, Shipment of Production Items, sub paragraph 4, Page 29

References MIL-DTL-58662, however, cannot locate a document with that title in the RFP or in government databases. Could the number be incorrect?

A2.This is a typo, it should say MIS-DTL-58668. The SOW in Section C has been updated to fix this typo.

3. RFP Sec J, Att 0003 Spec, Para No 3.6.1.3, 3.6.1.4, Human Engineering Requirements, Center-to-Center Distance

It appears that paragraphs in the keyboard section were separated by other text. Believe paragraphs 3.6.1.3 - 3.6.1.4 are keyboard requirements and may belong with 3.5.7.

A3. Correct, however all keyboard requirements remain the same and must be met. The Specification will not be updated at this time.

4. RFP Sec J, Att 0003 Spec, Para No 3.6.8, 400 AC Hz Power Supply, Page 25

Should this read 100 to 240 VAC at 47-400 Hz rather than 50 to 60 Hz?

A4. Correct the 400Hz power supply should be able to operate from 47 to 400Hz.

Spec should read (The 400Hz AC Power Supply shall operate from 100 to 240 VAC at 47 to 400 Hz commercial input power and supply the necessary input power to power and operate the MSD-V4L). The Specification will not be updated at this time. The Specification will either be updated to incorporate this change prior to the contract award or language will be placed in the resultant contract to state that this change will be made to the Specification.

5. RFP Sec L, Instructions, Conditions, and Notices to Offerors, Para L-1 thru L-8, page 72, and L.1 thru , page 73

There appears to be an issue with Section L. On page 72 it starts with section L, paragraphs L-1 L8 and on page 73 it starts again with section L, paragraphs L.1 - Please clarify intended content.

A5. Our contract writing systems automatically numbers the clauses in each section which is why page 72 starts with L-1. The narrative on page 73 is our specific proposal instructions which we just happened to start with L.1, L.2, etc. We apologize for the confusion but to keep references in place these will be unchanged. Any questions to the specific clause should include the clause number and questions related to the instructions should include the specific paragraph number like L.2.1.3 for example.

6. RFP Sec L & M, Instructions & Evaluation, pages 72-85

Section L and M do not seem to address specific requirements found in the statement of work for Program Management, Configuration

Management, Production, Quality System, Logistics, Warranty, First Article Test, Cybersecurity, etc. Where will these SOW requirements be located in the proposal volumes (section L)? How will these SOW requirements be evaluated as part of the scoring criteria (section

M)?

A6. Offeror must acknowledge that they meet all SOW and Specification requirements, and then address the specific areas defined in

Section L. Section M shows the adjectival rating definitions and Factors evaluation criteria. The successful offeror will be required to meet all the requirements of the RFP once on contract.

7. RFP Sec C SOW, Para 6.8.1, Warranty Program, 4th para, Page 26

The warranty wording for Ship In Place units does not specify the amount of time that systems are held in bonded storage prior to shipment. The warranty does not start until the units are shipped from the bond room. Under this requirement, is it possible that the units could be held for years prior to the warranty commencing. Would the government consider bounding this requirement to say, as an example that if the units are not shipped from the bond room within 18 months after ship in place that warranty will commence?

A7. The SOW in section C has be revised to provide clarity under 6.8.1 " The contractors warranty clock shall start when the contractor ships the MSD-V4L units from its staging facility to the shipper or 12 months from when the MSD-V4L kits DD250 is signed"

8. RFP Sec C SOW, Para 6.10, Manpower Reporting, Page 28

Typically, FFP production IDIQ contracts do not require manpower reporting except on level of effort type labor tasks. Is it possible to remove this requirement for all but LOE managed efforts?

A8. Contractor Manpower Reporting is required for service(s) CLINs once they have been placed on an order.

3 46

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

9. Page 2, 6th Para, **The affordability cap for the MSD-V4L kit, as defined in MIS-DTL-58668 (MSD-V4L Detail Specification), is $3,800.

Any proposal received in response to this RFP with the MSD-V4L kit price above $3,800 may be considered unaffordable and may not be considered for award.** Is it correct to assume this cap only applies to CLIN 003, Ordering Period 2, Quantity range 2501 - 6000?

A9. The affordability cap applies to CLIN 0003, on the Attachment 0002 Section B Matrix, for all quantity ranges in ordering periods 2-

5.

10. Page 4-12 CLIN Structure. The Section B CLIN Structure does not match the spreadsheet provided. There are significant mis-matches in the descriptions and items that must be ordered in the contract and priced in the Attachment 002. Will the Government please clarify why the differences? Example: Is RFP Section B CLIN 0032 all inclusive of Attachment 002 CLINs 003 - 033?

A10. The CLINs in the RFP are set up as a place holder. Agree that the CLINs in the RFP do not match the CLINs in Attachment 0002 but the pricing should all be added in Attachment 0002. The pricing evaluation will be based on the unit pricing included in Attachment

0002. The unit prices included on Attachment 0002 will be added to the base IDIQ contract when an award is made.

11. Page 83, Para M.3.4, The total evaluated price will be computed by summing the weighted evaluated prices computed from the unit prices proposed in Section B of the solicitation. The spreadsheet provided and the instructions do not identify how each range will be weighted to develop the Total Evaluated Price. Understanding our offer Total Evaluated price is required for the offeror to properly complete the Small Business plan and understand the total program being awarded. Without being able to see the Total Evaluated Price, it is impossible for the offeror to complete the Small Business plans. Will the Government please add the weighted calculations and a Total

Evaluated Price tab to the spread sheet?

A11. The Government will not be providing the weighting for the ranges. For the purposes of calculating the Total Evaluated Price for the Small Business plan only, offerors shall use the maximum quantity for each of the items. For example, CLIN 0003 would be 6,000 units for each OP2-5 and CLIN 0004 would be 100 units for each OP2-5.

12. Page 11, Para 3.3.6,Trusted Platform Module (TPM). The specification does not address a number of critical issues referenced in the

SOW under paragraph 9.11 Cybersecurity/ Program Protection. Typically the specification contains requirements on Virtualization

Technology for Directed I/O, verification of TPM authenticity, asserting TPM ownership (including lockout, endorsement, endorsement keys, configuration register, Golden PCRs, BIOS TPM Passwords, TPM platform hierarchy, and reference to the DoD Risk Management

Framework. Will the Gov't please consider updating Section 3.3.6 to include a reference to the SOW paragraph 9.11 and other cyber security requirements mentioned above?

A12. The Government requirements remain unchanged. The Specification will not be updated to include references to the SOW and offerors are again reminded that they must be able to meet all requirements of the RFP to include the Specification.

13. Supply Chain Risk Management- Multiple recent Army RFPs have included complete and detailed Supply Chain Risk Management (SCRM) requirements including a plan submission with the offerors proposal. SCRM is FAR requirement for all IT procurements. Will the

Government consider adding SCRM requirements and the submission of a plan to ensure the offeror is capable of meeting all Supply Chain

Risk Management requirements?

A13. Supply Chain Risk Management is addressed in the SOW (Throughout Section 9).

14. Page 82, Para M.2.1, SUBFACTOR 1: Performance. The Performance Subfactor evaluation is based on the Offerors bid sample meeting or exceeding the threshold benchmark score utilizing PassMark Software Performance Test requirements as specified in the MSD Performance

Test Plan and Detail Specification MIS-DTL-58668, section 3.8.7. The current evaluation of Bid Samples only addresses Benchmark testing and the display. There is no evaluation criteria for many other critical aspects of the program including battery life, optional accessories, packaging approach, environmental requirements, program management, logistics and lifecycle support, production capability, cybersecurity, configuration management, etc. In order for the Government to evaluate the complete offer and have reasonable assurance the offeror can meet all the requirements of both the specification and SOW, will the Government consider adding to Section L and

Section M a reference to all specification and SOW requirements? (this question ties to Similar question 15 below)

A14. Offeror must acknowledge that they meet all SOW and Specification requirements, and then address the specific areas defined in

Section L. Section M shows the adjectival rating definitions and Subfactors evaluation criteria.

15. Page 82, Para M.2.1-M.2.1 SUBFACTOR 1: Performance. The Performance Subfactor evaluation is based on the Offerors bid sample meeting or exceeding the threshold benchmark score utilizing PassMark Software Performance Test requirements as specified in the MSD Performance

Test Plan and Detail Specification MIS-DTL-58668, section 3.8.7. Bid Samples are the key determining factor for the Government to evaluate the suitability and quality of each offerors MSD V4L. This includes environmental and other factors beyond Benchmark testing.

Will the Government consider adding testing beyond benchmark to include drop tests, temperature test, display capability, battery life, etc.?

A15. Offeror must acknowledge that they meet all SOW and Specification requirements, and then address the specific areas defined in section L. Section M shows the adjectival rating definitions and Subfactors evaluation criteria. The bid sample testing will only be tested on the benchmark score.

4 46

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

16. Page 75, L.4 SPECIFIC PROPOSAL INSTRUCTIONS - Offerors are responsible for including sufficient details (i.e. drawings, test data, specification sheets) to permit a complete and accurate evaluation strictly from a technical standpoint. The instructions say to include test data, specification sheets, and drawings but there is no Appendix or location to include this data. It is also not clear that this data is not included in the page count. Can the Government update Section L to add an Appendix for Test data, an Appendix for specification sheets, and an Appendix for drawings?

A16. Test reports should be excluded from maximum page count and should be included in Technical submission. Section L.3.3.1 was updated on Amendment 0001.

17. Page 28, Para 3.9.2.1.1 -"3.9.2.1.1 Shock, Logistic Transit Drop MSD-V4L

The MSD-V4L with the battery or batteries and hard drive installed shall perform to the requirements of this specification after being dropped from a height of 18 inches on each face for a total of six drops." The draft Specification does not call out MIL-STD-810G Method

516.6 which is the standard for drop testing. It is called out for all other requirements but not for drop. The current requirement only focuses on the six (6) major surfaces but fails to address ruggedness and survivability concerns repeatedly voiced by Warfighter end-users. The standard identifies 26 drop points which is a more realistic test scenario. Will the Government add MIL-STD 810G Method 516.6 to the specification and update the drop test requirements accordingly?

A17. Government requirements remain unchanged. As this is the Light version of the MSD-V4, the methods and drop test requirements in the

Specification are what is required.

18. Page 82, Para M.2, M.2.1 SUBFACTOR 1: Performance - Currently Section M is not clear on how credit will be given for meeting Objective requirements. Can the Government clarify how meeting Objective requirements will be evaluated?

A18. The Technical Factor and Subfactors will receive a color/adjectival rating in accordance with the chart in Section M.2. Strengths and significant strengths will be determined based on the benefit to the Government which will be determined by the source selection evaluators.

19. Page 9, Para 3.2.4 - Shall include the following: IUID Reader - IUID to USB Cable - IUID Transit Case Currently the IUID

Reader is provided in its own transit case. However, if it can be provided in the MSD V4 Kit, it will save the Government logistics and transportation costs. Will the Government add an objective requirement to package the IUID Reader in the same transit case as the MSD

Kit?

No objective requirement will be added, however the IUID Reader can be incorporated into the MSD-V4R and MSD-V4S kit if it still meets the transit case specification dimension and weight requirements.

20. Page 2, Section A, What is the total Army Acquisition Objective (AAO) for the MSD V4L program?

A20. The Government will not be releasing its AAO for the MSD-V4L program.

21. Page 25, Section 3.7 - The MSD-V4L shall be compatible with Microsoft Windows\'ae 10 through the currently approved AGM and 64-bit

Red Hat Enterprise Linux OS Version 7 or later. The specification Section 3.7.1 The MSD-V4L shall be compatible with Microsoft

Windows\'ae 10 through the currently approved AGM and 64-bit Red Hat Enterprise Linux OS Version 7 or later. "The SOW Sect 9.9 states that the Windows operating system will be GFI. What does the Government mean that it will be supplied through the AGM Std? Is it correct to assume this means the offeror provides but it must be the same release version because there are separate priced CLINS (0027 and

0028) for the operating systems and therefore, we assume it is not GFE?

A21. The current approved AGM version is Microsoft Windows\'ae 10, although the Cyber Security requirement may dictate a newer OS at a later date. The Government will provide updated GFI ERDs with the AGM Standard to contractor for replication on semi-annual basis unless otherwise directed. CLIN number 0027 and 0028 are for the OS licenses.

22. "L.4 - The Offeror shall provide detailed narrative discussions that address both the SOW and the CDRLs of the solicitation.L.4.1.1, L.4.1.1.a, L.4.1.1.b and L.4.1.2, do not include requirements for the SOW/CDRL narrative discussion in the proposal subfactorsM.2.1 and

M.2.2 do not evaluate a SOW/CDRL detailed narrative" Would the Government please clarify 1) whether the offerors proposals are or are not to include the SOW/CDRLs narrative? And, 2) if yes, please clarify the Governments desired location within the proposal 3) and page limit for these responses in excess of the 25 page limit for the volume or included within the 25 page limit for the volume.

A22. The language in Section L.4 has been removed for the SOW/CDRL narrative discussion.

23. Does the Government have an anticipated contract award date and can that information be provided to offerors?

A23. L.2.1.5 requests that proposals be valid through 31 July 2018.

24. "L.3.3.4 lists native formats to be Zipped that do not include PDF

L.2.3.1 allows for the submission of PDF formatted files " Would the Government please clarify that PDF files are allowed and whether

5 46

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

all files must be compressed?

A24. PDF are allowed and compressed files allow for easier submission to the Government for larger files if needed.

25. The MSD-V4L display shall have multitouch screen capability. Does the multi-touch have to work with a MOPP 4 gloved hand (which is one of the specification requirements)? "The MSD-V4L shall be capable of being properly shut down and stored by personnel dressed in chemical and environmental protective equipment MOPP IV" not operated. The MSD V4L shall contain a minimum of 8GB of RAM. The

8GB is the minimum acceptable, does the customer have an objective for expansion and therefore will the Government add an objective requirement?

A25. Government requirements remain unchanged as the Government only has a requirement for a minimum of 8GB of RAM.

26. MSD V4L shall incorporate and support Secure Boot capability and technology. Will the customer (USG) provide the Secure Boot software or will the contractor be asked to develop and provide?

A26. The contractor shall provide the Secure Boot software.

27. The 400 Hz Power Supply shall operate from 100-240 VAC at 50 to 60 Hz commercial input power and supply the necessary input power to power and operate the MSD-V4L. This is the standard 50-60 Hz power supply, there is no mention of the 400 Hz input power. Is 400 Hz input a requirement?

A27. The Specification should read (The 400Hz AC Power Supply shall operate from 100 to 240 VAC at 47 to 400 Hz commercial input power and supply the necessary input power to power and operate the MSD-V4L). The Specification will not be updated at this time. The

Specification will either be updated to incorporate this change prior to the contract award or language will be placed in the resultant contract to state that this change will be made to the Specification.

28. The MSD V4L FMS system software shall be configured with Windows 10 or later, or 64-bit Red Hat Enterprise Linux OS Version 10 or later. Linux is currently at release 7.2, is this section accurate in calling out Linux 10? Version 7 or later is called out in section

3.7.5.

A28. The MSD-V4L OS software shall be configured with Red Hat Enterprise Linux OS Version 7 or later.

29. In Section L.4.2.1 states that FAT shall be provided for all ordering periods. However, the Spread sheet for Section B, FAT is blacked out for all ordering periods after Year 1. Is it correct to assume that FAT is only to be bid in year 1?

A29. The Government only requests pricing for FAT in Ordering Period 1.

30. Past Performance Relevancy Ratings Definition - Can the Government clarify what the term "magnitude" means for relevancy of a past performance effort? Can we assume that V4L is approximately a $100M program?

A30. The ceiling amount for this contract is $111,277,000.

31. "The MSD-V4L shall utilize a SSD of no less than 300 GB for operating system software and data storage." Will the Government consider adding an Objective requirement for a 512GB Hard Drive?

A31. Government requirements remain unchanged as the Government only has a requirement for no less than 300GB for operating system software and data storage.

32. Please clarify how the training referenced in SOW 6.2.22 should be priced? Should training be incorporated into each of the kits within CLIN 12, 22, 32, & 42 or priced into the Services CLIN following receipt of a Letter of Consideration?

A32. 6.2.22 Material Fielding Team (MFT): New Equipment Training (NET) Team and Fielding Team will apply to the Materiel Fielding and

Training Specialist II labor category of Service CLIN. The Government has estimated the number of hours for all labor categories for the five (5) ordering periods. The Offerors are asked to include fully burdened labor rates on Attachment 0002 Section B Matrix -

Services OP1-5 Tab. When the Government has a specific service requirement, it will be solicited on a Letter of Contemplation to the successful contract holder and the rate proposed for the labor categories must be equal or less than to those labor rates on contract.

33. The following SOW paragraphs are not referenced within CDRLs: 6.2.2, 6.2.3, 6.2.14, 6.2.15, 6.2.16, 6.2.17, 6.2.22, 6.4.4, 6.5, 6.6.2.1, 6.8, and 6.8.1. The following training artifacts are called out within those paragraphs: Operator Training Package, NET CBT, Institutional Training, POI, Lesson Plans, Slides, and Student Guide. Can it be assumed that all of these items relate to CDRL 0035, the

Instructional Media Package?

A33. CDRL requirements are in place to cover deliverables. The assumption is incorrect that all these requirements need to be tied to

CDRL 035.

6 46

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

34. SOW, CDRLs 6.4.4 / 6.5 - Is it correct to assume these paragraphs apply to CDRL 0023?

A34. No - there are no deliverables associated with these paragraphs.

35. SOW, CDRLs 6.9 - How does "frequently asked questions and answers from help line calls, technical information which is essential to field users or IETM developers, or information which shall enhance ease of use" get delivered?

A35. This is considered normal business practices and should be submitted via email correspondence with word or pdf attachments as needed.

36. SOW, CDRLs 6.11 - Can it be assumed that this SOW paragraph's scope should be included within CDRL 028 (IMS)?

A36. Yes.

37. The SOW indicates that first article testing may be repeated at any time during the contract. Is it the government's intent to issue a Letter of Contemplation in order to fund any required additional testing?

A37. Addressed in SOW, Para 7.1.c.

38. Is the intent of the detachable keyboard to have an external wired keyboard for use in an office environment or for an integrated keyboard to be removable from the Tablet?

A38. The design is at the discretion of the vendor, and shall comply with cybersecurity requirements.

39. This section describes a test of the transit case but references having the device operational during the testing. Is it the intent to expose the operational tablet, keyboard, and USB devices to the rain environment? If so, please provide the contractor with a list what USB devices need to be exposed to the test.

A39. No, this is a non-operational test in Transit Case. There is however a functional check that must be performed within 10 minutes after each 30 minute test.

40. IUID Reader Kit is included in the detailed specifications but not included in either the Pricing sheet in Attachment 2 or the CLINs in Section B. Where is the IUID Reader Kit Priced?

A40. The IUID Reader Kit was inadvertently left off the price sheet. Please provide a Unit Price for a quantity range of 1-25 and 26-100 for Ordering Periods 2-5. Attachment 0002 Section B Matrix has been updated to include the IUID Reader Kit in Amendment 0001.

41. European power adapter is stated to be equivalent to NSN 5935-01-359-5698 but this item is not available and details of its specifications cannot be found. Section 4.4.4.1 of the Specification asks to verify the supplied power adapter is equivalent to the NSN

5935-01-359-5698 via documentation. Can the Government provide documentation on NSN 5935-01-359-5698 so the Contractor can identify an equivalent power adapter?

A41. The correct NSN is 5975-01-452-1275. The specification will not be updated to reflect this change. The Specification will either be updated to incorporate this change prior to the contract award or language will be placed in the resultant contract to state that this change will be made to the Specification.

42. Does the bid sample submission include only the standard accessories called out in parenthesis "The Offerors proposal shall include one (1) bid sample with standard accessories (Battery or Batteries, Alternating Current (AC) Power Cable, and Adapter Assembly)" or all standard accessories called out in Attachment 3 Section 3.2.2 Standard Accessories?

A42. The bid sample shall include all the standard accessories which are called out in Section 3.2.2 of the Specification.

43. Do warranty & repair shipments need to go through the DCMA / SIR eTool process? If so, what is the typical time this process takes?

Our concern is how much of the 72 / 168 hour turn around time requirement is consumed by this requirement.

A43. There is no requirement to use DCMA/SIR eTool for warranty shipments. Para 8.2 and 6.8.2 reflect two separate requirements.

44. How does the Bond Room Inventory Report get delivered?

A44. By email; a Government POC will be provided at the initial Start of Work meeting.

45. What is the desired timing and frequency of submission of the Bond Room Inventory Report?

A45. The Bond Room Inventory Report shall be delivered bi-weekly (once every two weeks).

7 46

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

46. How should the Product Acceptance System be delivered in order to receive verification and formal approval?

A46. Dependent upon vendor's methodology. Delivery method will be determined at initial Start of Work meeting.

47. What is the desired timing of the Product Acceptance System validation and approval?

A47. Must be approved prior to start of First Article Test (FAT)

48. SOW 9.2 - Is it correct to assume this paragraph applies to CDRL 0037?

A48. Yes.

49. How should "All details of Cybersecurity implementation in RedHat Linux software" be provided to the Government?

A49. The same method as the Windows OS.

50. How long should it be assumed that Cybersecurity testing last?

A50. Dependant on vendor's hardware/software solution.

51. Please clarify the intended duration of the "lifecycle" and "reciprocity" periods.

How should the Corrective Action Plan get delivered?

A51. By email; a Government POC will be provided at the initial Start of Work meeting.

52. There are many requirements within this section of the SOW that are not referenced within CDRLs. Can we assume that where no delivery is specified, there is no requirement to provide the associated information to the Government?

A52. Yes.

53. Is there a requirement to submit the contractor Supplier Management Plan & the Anonymity Plan?

A52. No, however the Government retains the right to review at contractor's location upon request.

54. The Government indicates a total evaluated price will be achieved (in part) by summing the weighted evaluated prices computed from the unit prices proposed in Section B of the solicitation. Please provide detail on the weighting criteria to be used.

A54. The Government will not be providing the weighting associated with each range.

55. In this section describing FACTOR 2 : PRICE, there is language related to past performance? Is this misplaced? If not, please clarify how the Government with evaluate past performance in relation to offered price.

A55. The past performance language was copied into that section by accident. Section M.3.1 has been updated to remove the language associated with past performance.

56. What is the frequency, duration, and location planned for the Cybersecurity (Adversarial Assessment)? Is attendance either in person or via teleconference?

A56. As required by DISA vulnerability findings. Attendance depends on classification level of assessment.

57. TRADOC PAM 350-70-2 specifies four levels and the assoicated development time for each is significantly different. Based on Section

6.2.18 in the PWS, should CBT be at Level 2?

A57. Yes

58. SAM provides an option to print the FAR Report or the FAR and DFARS Report under the Reps & Certs Entity Registration page. Please confirm the FAR and DFARS Report is what we need to provide as the .XPS file.

A58. FAR and DFARS Report shall be provided.

59. Does the government require all CDRL's or only priced CDRL's in Vol. V?

A59. All.

60. Section L.2.1.4 states that alternate proposals will not be accepted. We understand this requirement. However, would the Army be

8 46

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

willing to allow vendors to propose more than one technical solution?

A60. The Government will only accept one proposal/technical solution per prime contractor. Offerors should submit the solution that they feel makes the most business sense in meeting the requirements of the RFP.

*** END OF NARRATIVE A0005 ***

9 46

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

STATEMENT OF WORK (SOW) FOR

MAINTENANCE SUPPORT DEVICE-VERSION 4 LIGHT (MSD-V4L)

1.0 BACKGROUND

The intent of the Maintenance Support Device-Version 4 Light (MSD-V4L) program is to produce and field an improved system of at-platform test equipment. The MSD-V4L System, a member of the Integrated Family of Test Equipment (IFTE), is the Armys next generation of standard general purpose at-platform automatic test equipment. The MSD-V4L System consists of commercial software and hardware components operating together with system specific software, standard accessories, interconnecting cables, and test adapter modules. This system shall be used throughout the U. S. Army at all levels of maintenance as the Armys standard at-platform tester for a wide variety of complex systems. Additionally, the MSD-V4L shall be used to host Interactive Electronic Technical Manuals (IETMs) and Electronic

Technical Manuals (ETMs), specific application software, and to upload/download mission data or software. The MSD-V4L System is intended to support all Army maintainers including ground, armor, aviation, missile, wheeled vehicle, signal/radio, command and control, and other tactical system maintainers. The MSD-V4L Kit with optional accessories shall be configured to support various Army weapon systems and platforms with optional and standard accessories. Companion accessories to the MSD-V4L Kit include the Smart Wireless

Internal Combustion Engine (SWICE) Test Adapter Set and Wireless At-platform Test Set (WATS), although SWICE and WATS are not produced under the MSD-V4L contract.

2.0 SCOPE

This Statement of Work (SOW) defines the effort required for the production, test, delivery, storage, and support of the MSD-V4L System.

The contractor shall provide all labor, resources, expertise, facilities, and material necessary to satisfy the requirements of MSD-V4L

SOW and MIS-DTL-58668 (MSD-V4L Detail Specification) in order to produce, test, and deliver MSD-V4L Kits, optional accessories, and support services. The work required by this contract shall be performed in accordance with (IAW) MIS-DTL-58668. In the event of a conflict between this SOW and MIS-DTL-58668, the MIS-DTL-58668 shall take precedence.

3.0 GENERAL REQUIREMENTS

General requirements of this contract include contractor support in the following areas: Program Management (PM), Configuration

Management (CM), Logistics, First Article Testing (FAT), Production, and Engineering. This SOW presents the MSD-V4L System and accessories support requirements in broad terms and as generalizations. Further detail shall be provided in each Letter of Contemplation

(LoC) issued to the contractor on a task-by-task basis. In responding to those LoCs, the contractor will have the opportunity to submit a proposal for the task utilizing the agreed-to labor categories and material overhead rate, if applicable, as incorporated into the contract as well as propose required travel, if applicable, to support the requirements of the order.

4.0 PROGRAM MANAGEMENT REQUIREMENTS

The contractor shall establish and maintain program management operations that shall include the following areas: program planning and control, subcontractor control, financial management, data management, risk management, and accountability for Government Furnished

Information (GFI).

The contractor shall use a program management system to develop and perform to an Integrated Master Plan (IMP) and Integrated Master

Schedule (IMS), DI-MGMT-81650, throughout the life of the program. The contractor Program Manager and supporting teams shall support the delivery of accurate and timely schedule and performance information, including IMP and IMS, to Product Director Test, Measurement and

Diagnostic Equipment (PD-TMDE) throughout the period of the contract to include units under warranty after the last contractual delivery. The schedule shall be generated and provided in Microsoft Project 2010 or later.

The contractor shall be responsible for leading bi-monthly In-Process Reviews (IPR) to facilitate a common understanding and agreement with the Government on MSD-V4L system requirements, actions, and schedules to meet those requirements. Meetings shall be held at the respective places of performance for the manufacture of MSD-V4L, contractor's facilities and at PD-TMDE facilities, as needed. The contractor shall provide personnel (such as Engineers, PM, CM, Quality, Productions) and others as needed to support and conduct these meetings. The Government may choose to hold these meetings by telephone conferences or web enabled conferences. Meetings at PD-TMDE facilities can be accommodated through coordination and agreement between Government and contractor.

Technical meetings shall be held as needed for discussion, determinations, and clarifications of technical items and issues. Technical meetings shall be performed through telephone and/or web conferences, person-to-person or group meetings, and/or via electronic mail to help resolve technical items and for clarifications. Technical meetings shall not change the terms of the contract or cause any impacts to the contract. All recommended changes shall be coordinated by notification to the Procuring Contracting Officer (PCO) and shall not be implemented without authorization from the PCO.

4.1 Start of Work Meetings

Start of Work meetings shall be held for the following general requirements: PM, CM, TM Development, Logistics, Training, FAT, Software/

Cybersecurity, Engineering and Production. The IMP and IMS shall incorporate start of work meetings and specify criteria and dates, respectively. The IMS shall also include In-process Reviews.

4.2 Conference Minutes

The contractor shall be responsible for recording, maintaining, and providing detailed written minutes, including any tasks of the Start of Work Meetings, all IPRs, and conferences (DI-ADMN-81250B). The Government will notify the contractor when minutes are required. The minutes shall not to be interpreted or construed as redirection for the contractor to incur additional costs that will increase the price of the contract.

10 46

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

4.3 Changes to Scope

Changes outside the scope of the contract, including this SOW, without specific authorization by the PCO, are unauthorized and shall be at the sole responsibility of the contractor.

4.4 Control Procedures

4.4.1 Antiterrorism/Force Protection for Defense Contractors outside the US

DFARS Clause 252.225-7043 shall be used in solicitations and contracts that require performance or delivery in a foreign country. This clause applies to both contingencies and non-contingency support. The key antiterrorism requirement is for non-local national contractor personnel to comply with theater clearance requirements and allows the combatant commander to exercise oversight to ensure the contractors compliance with combatant commander and subordinate task force commander policies and directives.

4.4.2 Contractor Clearance, Security and Training

The contractor shall forward the necessary visit requests to the appropriate installations for all contractor personnel who will require access in the performance of this contract. Contractor shall have Common Access Cards (CAC) for access to the Training Development

Capability (TDC) database.

4.4.3 Antiterrorism (AT) Awareness Training for Contractor Personnel Traveling Overseas. This standard language requires United States

(U.S.) based Contractor employees and associated subcontractor employees to make available and to receive Government-provided Area of

Responsibility (AOR)specific AT awareness training as directed by AR 525-13. Government provided awareness training specific to an area of responsibility traveled is provided to Contract personnel upon request by contacting the ARDEC Antiterrorism Officer at usarmy.pica.ardec.mbx.pica-ardec-at-training@mail.mil or 973-724-3005.

4.4.4 Access and General Protection/Security Policy and Procedures - All contractor employees, including subcontractor employees, shall comply with all installation and facility access and local security policies and procedures (provided by the Government representative), and security/emergency management exercises. The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by the installation Provost Marshal Office, Director of Emergency Services, or

Security Office. Contractor workforce must comply with all personal identity verification requirements (CFR clause 52.204-9, Personal

Identity Verification of Contract Personnel) as directed by DoD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes. During FPCONs Charlie and Delta, services/installation access may be discontinued/postponed due to higher threat. Services will resume when FPCON level and or threat is reduced to an acceptable level as determined by the Installation Commander. Contractor personnel working on an installation are required to participate in the Installation Random Antiterrorism Measures Program as directed. Contractors may be subject to and must comply with vehicle searches, wearing of ID badges, etc.

4.4.5 For contractors requiring CAC - Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated

National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled National Awareness Check with Inquiries (NACI) at the

Office of Personnel Management.

4.4.6 For contractors that do not require CAC, but require access to a DoD facility or installation - Contractor and all associated subcontractor employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate

Identification Index (NCIC-III) and Terrorist Screening Database (Army Directive 2014-05/AR 190-13); applicable installation, facility and area commander installation and facility access and local security policies and procedures (provided by Government representative);

or, at OCONUS locations, in accordance with status-of-forces agreements and other theater regulations.

4.4.7 For Contractors Authorized to Accompany the Force - DFARS Clause 252.225-7040 applies to this contract.

4.4.8 For Contract Requiring Performance or Delivery in a Foreign Country - DFARS Clause 252.225-7043 applies to this contract.

4.4.9 Access to Government Information Systems -All contractor employees and associated sub-contractor employees, including subcontractor employees, with access to a Government information system must be registered in the ATCTS (Army Training Certification

Tracking System) at commencement of services, and must successfully complete the DoD Cyber Awareness training prior to access to the information system and then annually thereafter.

4.4.10 IA/Information Technology (IT) Certification - All contractor employees, including subcontractor employees, employees must complete the DoD Cyber awareness training before issuance of network access and annually thereafter. All contractor employees working

IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M, and AR 25-2 within six (6) months of employment.

11 46

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

4.4.11 Government Furnished Items -All Contractor employees, including subcontractor employees, will return all issued U.S. Government owned equipment which includes travel laptops, mobile devices, Common Access Cards, installation badges, and/or access passes to the

Contracting Officer Representative (COR) when the contract is completed or when a Contractor employee no longer requires access to the installation or facility.

4.4.12 Information Management Army Information Technology /IA - The Contractor shall be capable of accessing, handling, receiving, and storing UNCLASSIFIED documents, equipment, hardware, and test items, using the applicable standards of FOUO information. All Controlled

Unclassified Information (documents designated as FOR OFFICIAL USE ONLY and/or LIMITED DISTRIBUTION) shall be submitted by a controlled means using USPS mail, Safe Access File Exchange (SAFE) website and/or DoD Army approved encryption software as per AR 25-1.

4.4.13 Export Control Laws/International Traffic in Arms Regulation - Information Subject to Export Control Laws/International Traffic in Arms Regulation (ITAR): Public Law 90-629, Arms Export Control Act, as amended (22 U.S.C 2751 et. Seq.) requires that all unclassified technical data with military application may not be exported lawfully without an approval, authorization, or license under EO 12470 or the Arms Export Control Act and that such data required an approval, authorization, or license for export under EO 12470 or Arms Export Control Act. For purposes of making this determination, the Militarily Critical

Technologies List (MCTL) shall be used as general guidance. All documents determined to contain export controlled technical data will be marked with the following notice: WARNING: - This document contains technical data whose export is restricted by the Arms Export Control

Act (Title 22, U.S.C., App. 2401 et seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DOD Directive 5230.25.

4.4.14 For Official Use Only Information (FOUO) and Controlled Unclassified Information (CUI) Contractor personnel shall be capable of accessing, handling, receiving, and storing UNCLASSIFIED documents, equipment, hardware, and test items, using the applicable standards of FOUO and CUI. DFARS Clause 252.204-7012 (Safeguarding Covered Defense Information and Cyber Incident Reporting) applies to this effort.

4.4.15 OPSEC Training - Per AR 530-1 (or DoDM 5205.02-M), new Contractor employees, including subcontractor employees, must complete initial OPSEC training within 30 calendar days of reporting for duty and must also complete annual OPSEC awareness training as provided by the appropriately designated OPSEC level II trained OPSEC Officer/Coordinator. The COR or Agreements Officer Representative (AOR) can request Armament Research Development and Engineering Center (ARDEC) OPSEC training from the ARDEC OPSEC Point of Contact (POC), e-mail:

usarmy.pica.ardec.mbx.ardec-opsec@mail.mil.

4.4.16 Public Release Information - Per AR 530-1(or DoDM 5205.02-M), an OPSEC review is required prior to all public releases. All government information intended for public release by a contractor will undergo a government OPSEC review prior to release.

5.0 CONFIGURATION MANAGEMENT (CM) REQUIREMENTS

CM requirements apply throughout the period of the contract to include units under warranty after the last contractual delivery. The purpose of CM is to assure that the Product Configuration Identification (PCI) accurately describes the as-designed/as-built delivered item(s). The configurations of MSD-V4L Systems as defined in the approved First Article Test Report shall establish the initial product baseline.

5.1 Start of Work Meeting

The CM Start of Work Meeting shall be held at Redstone Arsenal, AL no later than thirty (30)…