W15QKN17R0124-0003.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

0003 2017JUL14

W15QKN

ARMY CONTRACTING COMMAND - NJ

PICATINNY ARSENAL, NJ 07806-5000

ANDREW CONNER

EMAIL: ANDREW.D.CONNER7.CIV@MAIL.MIL

W15QKN-17-R-0124

2017JUL06

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 15

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: ANDREW CONNER

Buyer Office Symbol/Telephone Number: ACC-NJ-MA/(973)724-2670

Type of Contract 1: Firm Fixed Price

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

The purpose of this amendment is as follows:

1. Paragraph 5.2 of the Performance Work Statement has been revised. See Section C below.

2. Paragraphs L.3.1 and L.4.2.2(5) of Section L have been revised. See Section L below.

3. Paragraph C.5 of Section M has been revised. See Section M below.

The closing date and time, and all other terms and conditions, of this solicitation remain unchanged.

*** END OF NARRATIVE A0004 ***

2 15

W15QKN-17-R-0124 0003

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION C - DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

Performance Work Statement (PWS) for M109A7 Line Replace Unit (LRU) Testing and Diagnostic Support

1. Scope

1.1 This Performance Work Statement (PWS) outlines the requirements for the effort required to purchase Line Replaceable Units (LRUs) associated with the M109A7 and develop the Next Generation Automated Test System (NGATS) system software required to support Test

Program Set (TPS) development for the purchased LRUs. This equipment and services are required for the future development of Test

Program Sets (TPSs), which will be used to maintain the M109A7 fleet throughout its life cycle. The future TPSs will be utilized to enhance the maintenance of critical equipment and will assure a high level of readiness, platform supportability, improved reliability, expanded capability and reduced maintenance costs.

1.2 Background

1.2.1 An analysis has been completed on the M109A7 and it has been determined that the organic maintenance of the identified LRUs through the use of Army standard Automated Test Equipment (ATE) would have the most benefit to the Government. The hardware and integration is required in order to meet the fielding schedule of the M109A7 program.

1.2.2 NGATS is the latest addition to the Armys and DoDs approved family of ATE. It is a modern state-of the-art system designed and built utilizing an open architecture and commercial instrumentation. The NGATS was designed and developed to replace the Direct Support

Electrical System Test Set (DSESTS), Integrated Family of Automated Test Equipment (IFTE) Version 3 (V3) and Version 5 (V5) and to support future weapon systems requirements.

1.2.3 The Government has developed the NGATS based on a common architecture and commercial instrumentation termed Common Operator Test

Environment (COTE).

1.2.4 NxOMS, also known as Health Management Software (HMS), is the joint Department of Defense (DoD) software framework that fulfills the netcentric KPP (KPP1) of the NGATS station, and facilitates software accounting, software updates, hardware configuration accounting, log consolidation, and log extraction, and remote administration.

1.2.5 COUGAR is the working prototype for an ATE/TPS software code generation program to assist development environment users that are less experienced with computer science principles or are more familiar with graphical programming. This tool also doubles as a single step simulator where developers can try out various combinations of instruments commands real-time without having to recompile them into test programs. Both aspects are anticipated to increase developer productivity.

2. Applicable Documents:

- AR 25-1 Army Information Technology

- AR 530-1 Operations Security (OPSEC)

- NGATS System Specification, NGATS-SS-001, dated 15 Feb 2016 (Attachment 1)

- ARDEC Common Operator Test Environment (COTE) briefing, dated Feb 2017 (Attachment 2)

- NGATS Capability Production Document (CPD), V1.6, dated April 2007 (Attachment 3)

- List of Materials/LRUs (Attachment 4)

3. Requirements

3.1 No proprietary code in any software shall be used in this effort unless identified at award of this contract.

3.2 M109A7 Paladin LRUs (equipment)

3.2.1 The Contractor shall procure all of the equipment identified in Attachment 0003.

3.2.2 The contractor shall include an extended 2 year manufacturers warranty on all equipment provided to the Government on this contract.

3.3 Next Generation Automated Test System (NGATS) Enhancements

3.3.1 The Contractor shall develop an Ethernet instrument capability with corresponding Common Operator Test Environment (COTE) interface to allow for control of Ethernet ports from the TPS development interface.

3.3.2 The Contractor shall expand the digital test instrument capability and expose it through COTE interface.

3.3.2.1 The Contractor shall implement the following capabilities:

3.3.2.1.1 The user shall have the ability to program the high and low voltage level for an output and input signal.

3 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

3.3.2.1.2 The user shall have the ability to program the high and low threshold level for an output and input signal.

3.3.2.1.3 The station mass inter-connect panel (MIP) pins shall have bi-directional capability and thus shall be able to drive and detect signals concurrently.

3.3.2.1.4 The station mass inter-connect panel (MIP) pin shall have the ability to provide a constant voltage source. It shall either sink or source current to provide a constant voltage and have the capability of programming the current up to the maximum output available.

3.3.2.1.5 Ability to operate in static mode. The channels shall be commanded, either individually or as a group to a given state (High, Low or Tristate). Static mode is non-deterministic.

3.3.2.1.6 Ability to retrieve any channel measurement results independent of any other channel no matter whether the channel is static or dynamic (real time data).

3.3.2.1.7 Ability to set a group of timing events that will allow control of the state of a channel, the duration of the state, and how the channel acts in a default state.

3.3.2.1.8 Ability to create up to four (4) patterns when the channel will be asserted based on the programmed value. There shall also be the ability to create up to four corresponding measurement windows to verify the channel state.

3.3.2.1.9 Ability to program the time when the state of the channel changes and to specify the time period after which the signal will return to high.

3.3.2.1.10 Ability to program the time when the state of the channel changes and to specify the time period after which the signal will return to Low.

3.3.2.1.11 Ability to program the time when the state of the channel changes to a new state and shall remain in that new state.

3.3.2.1.12 Ability to program the time when the state of the channel changes and to specify the time period after which the signal will return to a Tristate state.

3.3.2.1.13 Ability to program the detect window of each channel and specify the duration of each channel.

3.3.2.1.14 Ability to change the state of a channel based on a condition on the same or different channel.

3.3.2.1.15 Ability to control high voltage pins (Utility Channels) which can be used to control relays.

3.3.2.1.16 Ability to provide an external clock to drive execution.

3.3.2.1.17 Ability to pause execution based on an external event.

3.3.2.1.18 The Contractor shall provide recommendations for capability exposure that would minimize Di-050-specific functionality.

3.3.2.1.19 The Contractor shall note where research indicates a Di-050-specific function has been implemented.

3.3.3 Graphical User Interface (GUI) Enhancements

3.3.3.1 The Contractor shall conduct a study to recommend GUI changes to both the main station GUI and TPS run-time system GUI for usability, modernization, and human factor accounting (DI-HFAC-81399B, CDRL B001). The Contractor shall hold design reviews to discuss the findings, and implement all Government approved changes. The study shall include, but is not limited to:

- Button color gradients.

- Button color shadows.

- Mouseover popups and help.

- Minimizing button text by promoting common graphic symbols to reduce the amount of text translation necessary in other languages.

- Color schemes and combinations. This includes replacement of difficult combinations such as black text on grey background.

- Text fonts

- Replacement of ASCII art and tables with minimization of ALL CAPS usage.

- Graphical functional divisions of information on the screen to provide a visual break between title headers and main bodies of information. Screens of note are main menu, single test menu, and disposition screen.

- Implementation of a simple display mode that reduces the amount of buttons and tabs on the screen to the minimum needed for the current activity.

3.3.3.2 The Contractor shall expand the picture display capability on station self-test and COTE to include animated GIFs and MPEG4 videos.

4 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

3.3.3.3 The Contractor shall implement a method for displaying the station specification / instrument capabilities and the COTE programming manual once available.

3.3.3.4 The Contractor shall implement a method for the COTE environment to display PDF documents which have built-in named destinations.

3.3.4 NxOMS Integration

3.3.4.1 The Contractor shall fully integrate NxOMS with the NGATS station GUI and COTE.

3.3.4.2 The Contractor shall make recommendations for displaying NxOMS data within COTE. For example, the station GUI and TPS data sheet could display the most common Line Replaceable Unit (LRU) and step number failures respectively.

3.3.5 COUGAR Implementation

3.3.5.1 The Contractor shall fully implement all instruments in the Test Developer Interface (TDI) in the COUGAR interface (which allows the TPS engineer to set up an instrument and generate TPS source code).

3.3.5.2 The Contractor shall implement the ability of COTE and COUGAR to maintain instrument control handles simultaneously.

4. General Information

4.1 The Contractor shall provide personnel well versed in Automatic Test Equipment (ATE) hardware and software as well as proficient knowledge in Army LRUs functionality and maintenance philosophies.

4.2 The Contractor shall support the analysis of the identified LRUs (See Attachment 0004). The Contractor shall support the identification of all necessary equipment to enhance the maintenance of the identified LRUs.

4.2.1 The Contractor shall support the assembly and build the newly upgraded modeling and simulation environment. The Contractor shall develop software (if necessary) and documentation for support and maintenance of the system (DI-IPSC-81488, CDRL A001).

4.2.2 The Contractor shall support performance testing to ensure proper performance with existing and future test scenarios.

4.3 The Contractor shall provide personnel experienced with automatic test hardware including, but not limited to, Next Generation

Automatic Test Station (NGATS), Maintenance Support Device (MSD), and DIT-MCO.

4.4 The Contractor shall provide personnel experienced with automatic test programming software including, Visio, Visual studio, XML, C#, C programming, and .Net.

4.5 The Contractor shall provide personnel experienced with ground vehicle electronics for the M109A7.

4.6 Integrated Master Schedule (IMS):

The Contractor shall provide an Integrated Master Schedule (IMS) which indicates start dates, completion dates and dependencies for all

LRUs as well as critical project tasks and sub-tasks to provide meeting of the events/deliveries called out in this contract. Microsoft

Office Project 2013 or later software shall be used to develop the IMS. Schedule impact shall be a consideration in all program decisions and the Contractor shall notify the Government of possible adverse schedule variances in the Monthly Progress Report. The schedule shall contain activities, durations, start and finish dates, activities name, and coding to identify type of activity (e.g., design, test, material procurement, software deliverables and testing) and index to the Work Breakdown Structure (WBS). The IMS shall be updated and provided monthly to the Government for review and comment (DI-MGMT-81861A, CDRL B002).

4.7 The LRUs which are acquired from Attachment 4 require a vulnerability assessment to determine if any potential risks are present.

This assessment will identify Critical Technologies that would adversely affect the operational effectiveness of the sub-assemblies.

After assessment is complete, an appropriate risk strategy will be developed to offset any potential risk areas. The vulnerability to be examined are performance degradation, data loss, loss of data integrity and system availability. The risk areas include but are not limited to: intrusions due to cyber equipment over-run by adversarial forces, maintenance functions such as software/firmware updates, etc. (DI-MISC-80508B, Technical Report/Risk Strategy/Assessment (CDRL B003).

4.8 Travel - There is no travel required.

4.9 Government Furnished Material (GFM) - There will be no Government Furnished Material provided.

4.10 Reserved

5. Deliverables

5 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

5.1 The Contractor shall provide a delivery schedule for all deliverable items (Technical Report/Study Services, Delivery Schedule, DI-

MISC-80508B, CDRL B004) and a Certificate of Compliance, (DI-MISC-81356A, CDRL B005).

5.2 The Contractor shall deliver all items identified in Attachment 0003.

5.3 The Contractor shall deliver a baseline and updated project schedule (DI-MGMT-80507C, Tailored, CDRL B006) that tracks the status of tasks and milestones.

5.4 The Contractor shall report immediately any major accident/incident (including fire) resulting in any one or more of the following:

causing one or more fatalities or one or more disabling injuries; damage of Government property exceeding $10,000; affecting program planning or production schedules; degrading the safety of equipment under contract, such as personnel injury or property damage may be involved; identifying a potential hazard requiring corrective action which are related to this contract. The Contractor shall prepare an Accident/Incident report (DI-SAFT-81563, CDRL B007) for each incident.

5.5 The Contractor shall submit a Program Progress Report (DI-MGMT-80555A, CDRL B008) and a Contract Summary Report (DI-ADMN-80447A, CDRL B009).

6. Security

6.1 THIS EFFORT IS UNCLASSIFIED.

6.2 Information Management Army Information Technology /Information Assurance (IA) - The Contractor shall be capable of accessing, handling, receiving, and storing UNCLASSIFIED documents, equipment, hardware, and test items, using the applicable standards of FOR

OFFICIAL USE ONLY (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 United States Postal Service (USPS) mail, Safe Access File Exchange

(SAFE) website and/or DoD Army approved encryption software as per AR 25-1.

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

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

6.5 Development of an Operations Security (OPSEC) Standing Operating Procedure/Plan The Contractor shall develop an OPSEC Standing

Operating Procedure (SOP)/Plan, in accordance with DI-MGMT-80934C (CDRL B010), within 90 calendar days of contract award, to be reviewed and approved by the responsible Government OPSEC officer, per AR 530-1, Operations Security. This SOP/Plan will specify the projects 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 will be an OPSEC Coordinator. The Contractor will ensure that this individual becomes

OPSEC Level II certified per AR 530-1. Armament Research Development and Engineering Center (ARDEC) OPSEC POC email:

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

6.6 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 Contracting Officer Representative (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.

6.7 Public Release of 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.

6.8 Information Disclosure- A Certificate of Non-Disclosure shall be signed by all Contractor employees working under this task and returned to the COR prior to task award. The Contractor shall not release any information or data without the approval of the

Government.

7. Non-United States (US) Citizen Employee Requirement

6 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

7.1 Only US Citizens are authorized to work on this contract. Non-US Citizens will not be allowed to perform work on contracts or subcontracts involving access (or possible access) to sensitive data, software, or equipment without prior approval from Headquarters

Army Material Command (HQ AMC).

8. Combating Trafficking in Persons

8.1 The Contractor shall establish policies and procedures for ensuring its employees do not engage in or support trafficking in persons or use forced labor in the performance of this contract.

9. Quality Assurance Surveillance Plan (QASP) - See Attachment 5 in Section J.

10. ACCOUNTING FOR CONTRACT SERVICE

10.1 The Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil/, and then click on Department of the Army CMRA or the icon of the DoD organization that is receiving or benefitting from the contracted services.

10.2 Reporting inputs will be for the labor executed during the period of performance during each.Government Fiscal Year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than

October 31 of each calendar year, beginning with 2017. Contractors may direct questions to the help desk by clicking on Send an email which is located under the Help Resources ribbon on the right side of the login page of the applicable Service/Components Contractor

Manpower Reporting (CMR) website.

*** END OF NARRATIVE C0001 ***

7 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L. PROPOSAL SUBMISSION:

L.1 Introduction: This section contains general proposal submissions instructions as well as specific proposal requirements for the

M109A7 LRU Testing and Diagnostic Support.

L.1.1 General. The proposal shall be presented in sufficient detail to allow Government evaluation of response to the requirements of the Request for Proposal (RFP). The Government will not assume the Offeror possesses any capability, understanding, or commitment not specified in the proposal.

L.2 PROPOSAL INSTRUCTIONS:

L.2.1 General:

L.2.1.1 Offerors shall provide information by addressing each Factor in the format and sequence identified in the solicitation. The

Offerors must provide information in sufficient detail to allow the Government to make a best value assessment of the Offerors capability to support the proposed response to the evaluation criteria. Proposals that do not contain the information requested in the solicitation risk being determined unacceptable by the Government. The Government will not assume the Offeror possesses any capability, understanding, or commitment not specified in the proposal.

L.2.1.2 The proposal must not merely repeat the solicitation requirements, but rather must provide convincing documentary evidence in support of conclusive statements of how contract requirements will be met.

L.2.1.3 The Government intends to award without discussions (see FAR 52.215-1). Proposals that do not contain the information requested in the solicitation risk being determined Unacceptable by the Government. The Government will not assume the Offeror possesses any capability, understanding, or commitment not specified in the proposal.

L.2.1.4 Alternate Proposals: Alternate proposals will not be accepted.

L.2.1.5 Proposals shall be valid through 31 October 2017.

L.2.2 All questions concerning this procurement, either technical or contractual must be submitted in writing to the Contracting

Officer. No direct discussion between the technical representative and a prospective Offeror shall be conducted. Questions and proposals shall be submitted to the following point of contact:

Army Contracting Command New Jersey

ACC-NJ-MA, Bldg.10

ATTN: Geoffrey R. Cramer, Telephone: (973) 724-2917

Picatinny Arsenal, NJ 07806-5000

E-mail: geoffrey.r.cramer.civ@mail.mil

Please note that electronic e-mail proposal submissions will not be accepted.

L.2.3 The proposal shall consist of the following:

L.2.3.1 Each proposal shall be submitted in the English language and consist of and include all of the following:

a. One (1) signed and completed electronic copy of the Standard Form 33 (SF 33) and continuation sheets (Sections A through M) signed by a person authorized to enter into the proposed contract on behalf of the Offeror. Acknowledgment of all amendments to the solicitation and all continuation sheets are to be filled in as directed, i.e., proposed prices in the CLINs/Pricing Matrices in Section B, any fill-ins required, such as Contract Data Requirements List: DD Form 1423 with Blocks 17 and 18 completed if required, and Certifications and

Representations in Section K. Offerors are directed to thoroughly read the solicitation and fill in the required information in the appropriate solicitation clauses. For any fill-ins that are not applicable, the Offeror must acknowledge by indicating N/A. The proposal must also include computation for the use of Government Property, if applicable.

b. Two (2) electronic CD copies of the proposal volumes, as reflected in D.3, shall be compiled using the Microsoft Office for Windows suite of applications, submitted on a single-write CD-ROM to prevent accidental erasure of the data therein, and formatted for an MS

Windows compatible computer. The Price Factor shall be contained on a separate CD from non-price Factors. Price breakdown, when applicable, will include MS Excel spreadsheets with formulae intact. Process flows may be delivered in hard copy if not compatible with the above software. CD copy must mirror the submitted hard copies. If the CD copy and hard copy differ, the CD copy supplied for each

Factor will be used for the evaluation. Each CD must be clearly marked with the Offerors Name and the Solicitation Number.

Alternatively, files may be provided in Portable Document Format (.pdf).

c. Representations through System for Award Management. The purpose of electronic Representations and Certifications is to provide all

Offerors with a portal in which to submit Reps/Certs in a publicly accessible format, nullifying the requirement to submit identical

8 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

information in response to each and every Federal contract solicitation. As a requirement under the M109A7 Line Replaceable Unit (LRU)

Testing and Diagnostic Support solicitation, all Offerors must submit Reps/Certs data into the System for Award Management (S.A.M.) at https://www.sam.gov/ and provide one (1) hard copy and one (1) electronic copy (on CD) submitted as an .XPS file. Any Offeror that has previously submitted Reps/Certs data into SAM is reminded to update the data prior to submitting with the proposal.

L.3 FORMAT FOR PROPOSALS

L.3.1 The Offerors proposal shall be submitted in severable volumes based on the Factors as set forth below and all information specific to each Factor shall be confined to that volume. Each proposal must include all volumes and shall be submitted by the closing date and time of the solicitation. Failure to provide any volume may result in the proposal being given an Unacceptable rating.

Information provided shall be specific to each Factor.

Page limitation for each Volume is as follows:

Volume I: Technical Factor (Maximum of 25 pages)

Volume II: Past Performance Factor (Maximum of 20 pages)

Volume III: Price Factor (No Maximum)

Volume IV: Solicitation, Offer and Award Documents; and Certifications/Representations

L.3.2 Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date and solicitation number in the header and/or footer. A Table of Contents should be created using the Table of Contents feature in MS Word. MS Word (.doc) files shall use the following page setup parameters:

Margins Top, Bottom, Left, Right - 1

Gutter 0

From Edge Header, Footer 0.5

Page Size, Width 8.5

Page Size, Height 11

L.3.3 Length:

L.3.3.1 Each volume shall be as brief as possible, consistent with complete submission. The page count will be made by counting the pages from left to right, consecutively. Pages that exceed the page limitation will be returned to the Offeror and will not be evaluated. Each paragraph shall be separated by at least one blank line. Annexes, documentation and attachments that are submitted by the Offeror, which are not required as part of the RFP, will count against the page limitations. If pages are printed on both sides, each side will count as a separate page. The following will not count against page limitations: volume title pages, table of contents pages, cross-referencing pages, indices, acronym lists and page dividers (used to separate proposal sections). Pages should not exceed 8-

1/2 inches in width by 11 inches in length; foldout pages depicting such items as sketches, factory floor layouts, etc. may be used, with each fold counted as one additional page. The font used shall not be less than 10 point.

L.3.3.2 Deviation from Requested Format. Request for deviations from the requested format shall be submitted to the Procuring

Contracting Officer (PCO) no later than fifteen (15) days after release of the solicitation. Offerors shall provide an explanation, in a clearly relatable format such as a matrix, of any differences between the manner in which the proposal was requested and the manner in which it is proposed to be submitted.

L.3.3.3 The Offeror is responsible for including sufficient details to permit a complete and accurate evaluation of the proposal.

Offerors shall provide a proposal that, at a minimum, addresses those evaluation Factors required in Section M of the RFP.

L.3.3.4 File Packaging - All of the proposal files shall be compressed (zipped) into one file using WinZip version 6.2 or later, or as separate uploads in their native format, i.e. doc, xls, ppt, etc. Please note Self extracting .exe files will not be accepted.

L.4 SPECIFIC PROPOSAL INSTRUCTIONS

Offerors are responsible for including sufficient details (i.e. drawings, test data) to permit a complete and accurate evaluation strictly from a technical standpoint. The Technical Volume(s) shall have a separate index, which contains narrative titles that are cross-referenced to both the applicable Performance Work Statement (PWS) paragraph and page number. This index shall not count against the Page limitation for the Technical Volume. The narrative discussions shall also be related to the applicable PWS paragraph by placing the appropriate PWS number at the beginning of the discussion text. The proposal shall be detailed and clearly stated to allow an assessment by the Government without the need for additional clarifications. The Offeror shall provide detailed narrative discussions that address both the PWS and the Contract Data Requirements List (CDRLs) of the solicitation. All information and data provided shall be specific to the M109A7 Line Replaceable Units (LRUs) Testing and Diagnostic Support, except for the area of Past Performance. In the response to the Request for Proposal, the Offeror must address the following Factors:

L.4.1 Volume I FACTOR 1: TECHNICAL

9 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

L.4.1.1 The Offeror shall present sufficient information to demonstrate a thorough understanding of the requirements as defined in the

Performance Work Statement (PWS) to provide M109A7 LRU Testing and Diagnostic Support. The submission shall include overall capabilities, company knowledge, and expertise to perform the effort.

L.4.1.2 The Offeror shall demonstrate its ability to provide Next Generation Automated System (NGATS) system software and runtime modifications and enhancements to support the M109A7 in the areas of Common Operator Test Environment (COTE), Graphical Users Interface

(GUI) and Test Development Interface (TDI). The submission shall include sufficient information demonstrating the Offerors understanding of the NGATS, its architecture, system software and runtime environment. The offeror shall demonstrate its ability to develop software in C# and C++ and integrate modifications into existing software baselines. The offer shall demonstrate its understanding of test development environments, and instrument layer functionality and implementation.

L.4.1.3 The Offeror shall submit a project plan which shall address its approach to successfully fulfilling the requirement. The plan shall include methodologies and processes, personnel allocation, available resources and their management and allocation.

L.4.2 Volume II FACTOR 2: PAST PERFORMANCE

L.4.2.1 Offerors shall identify pertinent past history, which indicates that similar efforts of equal or greater complexity have been performed using the Offerors existing plant capability and demonstrate satisfaction of customer requirements.

L.4.2.2 Offerors shall submit a list of all recent Government contracts (prime and major subcontracts) in performance or awarded to the

Offeror and any of its major subcontractors within the past three (3) years, or awarded earlier than three (3) years ago, but for which deliveries/performance occurred or were scheduled to occur within the past three (3) years, which are relevant to the effort required by the solicitation. Data concerning the prime Offeror shall be provided first, followed by each proposed major subcontractor, in alphabetical order. Offerors are reminded that both independent data and data provided by the Offerors in their proposals may be used to evaluate the Offerors past performance. The Government plans to rely on existing documentation from Federal databases to the maximum extent practicable. Sources of existing information available to the Government include, but are not limited to, Past Performance

Information and Retrieval System (PPIRS), Federal Awardee Performance and Integrity Information System (FAPIIS), and Electronic

Subcontract Reporting System (eSRS). The Government may use past performance information obtained from sources other than those identified by the Offeror. The burden of providing thorough and complete past performance information remains with the Offerors.

Proposals that do not contain the information requested by this paragraph may result in rejection or receipt of a high performance risk evaluation by the Government. This volume shall be organized into the following sections:

(1) Section 1 Contract Descriptions. This section shall include the following information in the following format:

(a) Contractor/Subcontractor place of performance, Commercial and Government Entity (CAGE) Code and Data Universal Numbering System

(DUNS) Number. If the work was performed as a subcontractor, also provide the name of the prime contractor and Point of Contact (POC) within the prime contractor organization (name, and current address, e-mail address, and telephone and fax numbers).

(b) Government contracting activity, and current address, Procuring Contracting Officer's name, e-mail address, telephone and fax numbers.

(c) Governments technical representative/COR, and current e-mail address, telephone and fax numbers.

(d) Government contract administration activity and the Administrative Contracting Officer's name, and current e-mail address, telephone and fax numbers.

(e) Government contract administration activity's Pre-Award Monitor's name and current e-mail address, telephone and fax numbers.

(f) Contract Number and, in the case of Indefinite Delivery type contracts, GSA contracts, and Blanket Purchase Agreements, also include Delivery Order Numbers.

(g) Contract Type (specific type such as Fixed Price (FP), Cost Reimbursement (CR), Time & Materials (T&M), etc.) In the case of

Indefinite Delivery contracts, indicate specific type (Requirements, Definite Quantity, and Indefinite Quantity) and secondary contract type (FP, CR, T&M, etc)).

(h) Awarded price/cost.

(i) Final or projected final price/cost.

(j) Original delivery schedule, including dates of start and completion of work.

(k) Final or projected final, delivery schedule, including dates of start and completion of work.

(2) Section 2 - Performance. Offerors shall provide a specific narrative explanation of each contract listed in Section 1 describing the objectives achieved and detailing how the effort is relevant to the requirements of the solicitation.

(a) For any contracts that did not/do not meet original schedule or technical performance requirements, provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. The Offerors shall list each time the delivery schedule was revised and provide an explanation of why the revision was necessary. All Requests for Deviation and Requests for

Waiver shall be addressed with respect to causes and corrective actions. The Offerors shall also provide a copy of any Cure Notices or

Show Cause Letters received on each contract listed and a description of any corrective action implemented by the Offeror or proposed subcontractor. The Offerors shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.

(b) For all contracts, the Offeror shall provide data on all manufacturing warranty returns. Data shall delineate total number of

10 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

warranty returns, number of Could Not Duplicate (CND), number of failures attributable to GFE component failures, and number and nature of failures attributable to the Offerors delivered product.

(3) Section 3 Subcontracts. Offerors shall provide an outline of how the effort required by the solicitation will be assigned for performance within the Offerors corporate entity and among the proposed subcontractors. The information provided for the prime Offeror and each proposed major subcontractor must include the entire company name, company address, CAGE Code, DUNS Number and type of work to be performed by citing the applicable Government SOW subparagraph number. This includes all major subcontractors who will be providing critical hardware/services or whose subcontract is for more than 25% of the total proposed price.

(4) Section 4 New Corporate Entities. New corporate entities may submit data on prior contracts involving its officers and employees.

However, in addition to the other requirements in this section, the Offeror shall discuss in detail the role performed by such persons in the prior contracts cited. Information should be included in the files described in the sections above.

(5) Past Performance Questionnaire. For all contracts identified in Section 1, Past Performance Questionnaires must be completed and submitted (Attachment 0012). The Offeror shall complete Part I of the Past Performance Questionnaire and e-mail the questionnaire to both the Government contracting activity and technical representative responsible for the past/current contract. The POCs shall be instructed to electronically complete Part II of the questionnaire and e-mail the entire questionnaire to the Contracting Officer within thirty (30) calendar days of the release of the RFP, to geoffrey.r.cramer2.civ@mail.mil and andrew.d.conner7.civ@mail.mil. The Offeror shall also e-mail to the Contracting Officer a list of all the POCs who were sent a questionnaire. The Government must receive this list within thirty (30) calendar days after release of the RFP. The POC List shall be submitted in Word for Windows Table Format to include the following fields: Solicitation Number; Company Name; Contract Number;

Government Agency; POC Last Name, First Name; POC Title; POC Telephone Number; POC E-Mail Address; Date E-Mailed to POC (month/day).

L.4.3 Volume III FACTOR 3: PRICE

L.4.3.1 The Offerors shall submit pricing in Section B for all priced CLINs. Each Offeror must propose a firm-fixed-price for CLINs

0001 through 0029. For CLIN 0030 (Contractor Manpower Reporting), Offerors may choose to propose a firm-fixed-price or propose it as Not

Separately Priced (NSP). CLIN 0031 shall be NSP.

L.4.3.2 In accordance with FAR 45.202(a), the Government shall consider any potentially unfair competitive advantage that may result from an offeror using Government property. To eliminate the competitive advantage, a rental equivalent evaluation factor shall be added to each offer which is predicated on the use of Government property. Offerors shall refer to Local Clause 52.245-4003 Use and Rental of

Government Property in Section L for submission instructions. The quantities stated in Section B shall be used to calculate the amount of rent that would otherwise be charged in accordance with FAR 52.245-9 , Use and Charges.

L.4.4 Volume V SOLICITATION, OFFER AND AWARD DOCUMENTS AND CERTIFICATIONS/REPRESENTATIONS

L.4.4.1 Each Offeror shall complete (fill-in and signatures) the solicitation sections indicated below using the file (without modification to the file) provided with the solicitation. An authorized official of the firm shall sign the SF 33 and all certifications requiring original signature. An Acrobat PDF file shall be created to capture the signatures for submission.

Section A through M Fill-ins as required

Section A Standard Form 33 (SF 33), Solicitation, Offer and Award

Section B Supplies or Services and Prices/Costs

Section G Contract Administration Data

Section J Contract Data Requirements List (DD1423) with blocks 17 & 18 completed

Section K Completed Representations, Certifications and Other Statements of Offeror

*** END OF NARRATIVE L0001 ***

11 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION M - EVALUATION FACTORS FOR AWARD

A. BASIS FOR AWARD

A.1 The Government intends to make a single award as a result of the RFP. The Government will select for award the proposal that is most advantageous and represents the best value to the Government, with the Source Selection Authority (SSA) giving the appropriate consideration to the three (3) evaluation Factors: Technical, Past Performance, and Price. The Government will weigh the relative benefits of each proposal and award will be made based on an integrated assessment of the results of the evaluation. In making this assessment, the SSA will give due consideration to all of the Factors and their relative order of importance. For evaluation purposes, the Technical Factor is more important than the Past Performance Factor, and the Past Performance Factor is more important than the

Price Factor. When all evaluation Factors other than Price are combined, they are significantly more important than Price. Price will be evaluated, but will not be rated with a color or adjectival rating. The Government reserves the right to make an award to other than the lowest priced Offeror, or to other than the Offeror with the highest technical rating if the SSA determines that to do so would result in the best value to the Government. Offerors that receive a final rating of Red/Unacceptable at any Factor level are ineligible for award.

A.2 The Government intends to award a contract without discussions (except for clarification as described in FAR 15.306(a)), as permitted by FAR 15.306(a)(3) and FAR 52.215-1. However, the Government reserves the right to conduct discussions to permit Offerors to revise their proposals.

A.3 Minimum Acceptability: If an Offeror takes exception to any of the terms and conditions of the solicitation, the Offeror may not be considered for contract award. All Offerors are urged to ensure that their initial proposals are submitted with the most favorable terms in order to reflect their best possible potential.

B. FACTORS TO BE EVALUATED:

B.1 The Government will weigh the relative benefits of each proposal and the SSA will assess the results of the following Factors, listed below in descending order of importance:

Factor 1: Technical________

Factor 2: Past Performance________

Factor 3: Price________

B.1.1 The Technical Factor does not have any Subfactors.

B.1.2 The Past Performace Factor does not have any Subfactors.

B.1.3 The Price Factor does not have any Subfactors.

B.2 The evaluators will use the following terms in support of the rating of all non-cost/price evaluation Factors:

a.Deficiency - A material failure of a proposal to meet a Government requirement or a combination of significant weaknesses in a proposal that increases the risk of unsuccessful contract performance to an unacceptable level.

b.Significant Weakness - A flaw that appreciably increases the risk of unsuccessful contract performance.

c.Weakness - A flaw in the proposal that increases the risk of unsuccessful contract performance.

d.Strength - An aspect of an Offerors proposal that has merit or exceeds specified performance or capability requirements in a way that will be advantageous to the Government during contract performance.

e.Significant Strength - An aspect of an Offeror's proposal that has appreciable merit or appreciably exceeds specified performance or capability requirements in a way that will be appreciably advantageous to the Government during contract performance.

f.Uncertainty - Any aspect of a non-cost/price Factor proposal for which the intent of the Offeror is unclear (e.g., more than one way to interpret the offer or inconsistencies in the proposal indicating that there may have been an error, omission or mistake).

g.Adverse Past Performance Past Performance information that supports a less than satisfactory rating from sources where the information is from other than formal rating systems such as PPIRS or FAPIIS.

C. EVALUATION APPROACH:

C.1 TECHNICAL EVALUATION APPROACH

C.1.1 Careful, full, and impartial consideration will be given to all proposals received pursuant to the RFP. A team of Government personnel will evaluate each proposal relative to the Factors. The result will be a determination of the overall merits of each proposal in terms of its potential to best satisfy the needs of the Government. In making the integrated assessment of the results of

12 15

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

the evaluation of all Factors, the Government will give due consideration to the relative order of importance of such Factors and their merit ratings in relationship to price. The Government weighs any increase in merit rating against any additional cost to determine if the parity of the relationship warrants the paying of additional cost for additional merit.

C.2 FACTOR 1: TECHNICAL

The Technical Factor will receive a color/adjectival rating in accordance with the chart below.

Color Rating Description

Blue Outstanding Proposal indicates an exceptional approach and understanding of the requirements and contains multiple strengths, and risk of unsuccessful performance is low.

Purple Good Proposal indicates a thorough approach and understanding of the requirements and contains at least one strength, and risk of unsuccessful performance is low to moderate.

Green Acceptable Proposal meets requirements and indicates an adequate approach and understanding of the requirements, and risk of unsuccessful performance is no worse than moderate.

Yellow Marginal Proposal has not demonstrated an adequate approach and understanding of the requirements, and/or risk of unsuccessful performance is high.

Red Unacceptable Proposal does not meet requirements of the solicitation, and thus, contains one or more deficiencies, and/or risk of unsuccessful performance is unacceptable. Proposal is unawardable.

The Technical Factor will be rated using the color code/adjectival ratings. The Technical Factor will be assessed for significant strengths, strengths, significant weaknesses, weaknesses, deficiencies, risks (see below), and uncertainties. The Technical Factor will be assigned an adjectival rating based upon these collective findings.

Offerors that receive a final rating of Red/Unacceptable at any Factor level are ineligible for award.

The adjectival/color ratings from the table above have an assessment of technical risk, which is manifested by the identification of weakness(es), considers the potential for disruption of schedule, increased costs, degradation of performance, the need for increased

Governmnet oversight, and/or the likelihood of unsuccessful contract performance.