W15QKN-15-R-0161-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 2015SEP21

W15QKN

ARMY CONTRACTING COMMAND - NJ

PICATINNY ARSENAL, NJ 07806-5000

JASON KENLAN

EMAIL: JASON.A.KENLAN2.CIV@MAIL.MIL

W15QKN-15-R-0161

2015SEP15

X

X

/SIGNED/

2 signed

SEE SECOND PAGE FOR DESCRIPTION

1 14

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: JASON KENLAN

Buyer Office Symbol/Telephone Number: ACC-NJ-JA/(973)724-9857

Type of Contract 1: Firm Fixed Price

Kind of Contract: Service Contracts

*** End of Narrative A0000 ***

The purpose of Amendment 0002 to Solicitation No. W15QKN-15-R-0161 is as follows:

1. Change the Contract Specialist from Mr. Jason Kenlan to Ms. Nadine Schneider and provide the following contact information:

Nadine Schneider

Contract Specialist

ACC-NJ-JA

973-724-4800 nadine.k.schneider.civ@mail.mil

2. Offerors are required to sign this amendment (SF30) and return two (2) copies to the issuing office with proposal submission.

3. The proposal submission date remains unchanged at 3:00pm on 15 October 2015.

*** END OF NARRATIVE A0003 ***

Status Regulatory Cite Title Date Status Regulatory Cite Title Date _______ _______________ ______________________________________________________________________ ____________ _______ _______________ ______________________________________________________________________ ____________

A-1 CHANGED 52.215-4006 GENERAL INFORMATION TO OFFERORS OR QUOTERS (AS6042) MAR/2012

1. Responses must set forth full, accurate and complete information as required by this solicitation (including attachments). "Fill-ins" are provided on Standard Form 18, 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:

_X_ This Procurement is unrestricted

___ This Procurement is ___% set-aside for __________________.

The applicable SIC/NAICS codes are: 541330.

5. Issuing Office:

U.S. Army Contracting Command - New Jersey

ATTN: Nadine Schneider

ACC-NJ-JA

Bldg. 9, Phipps Road

Picatinny Arsenal, NJ 07806-5000

Email: nadine.k.schneider.civ@mail.mil

6. Additional Information: n/a

7. Point of Contact for Information:

Name: Nadine Schneider

2 14

W15QKN-15-R-0161 0002

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Title: Contract Specialist

Email: nadine.k.schneider.civ@mail.mil

3 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION G - CONTRACT ADMINISTRATION DATA

CONTRACT ADMINISTRATION DATA____________________________

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

ACC-NJ-JA

Bldg. 9, Phipps Road

Picatinny Arsenal, NJ 07806-5000

Contract Specialist: Nadine Schneider

Phone: 973-724-4800

Fax: 973-724-2722

Email: nadine.k.schneider.civ@mail.mil

Contracting Officer: Christie R. Vicci

Phone: 973-724-4179

Fax: 973-724-2722

Email: christie.r.vicci.civ@mail.mil

Contracting Officer's

Representative (COR): TBD on a task order basis

DFAS Office: TBD on a contract basis

*** END OF NARRATIVE G0001 ***

Status Regulatory Cite Title Date Status Regulatory Cite Title Date _______ _______________ ______________________________________________________________________ ____________ _______ _______________ ______________________________________________________________________ ____________

G-1 CHANGED 252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS MAY/2013

(a) Definitions. As used in this clause--

"Department of Defense Activity Address Code (DoDAAC)" is a six position code that uniquely identifies a unit, activity, or organization.

"Document type" means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

"Local processing office (LPO)" is the office responsible for payment certification when payment certification is done external to the entitlement system.

(b) Electronic invoicing. The WAWF system is the method to electronically process vendor payment requests and receiving reports, as authorized by DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) WAWF access. To access WAWF, the Contractor shall--

(1) Have a designated electronic business point of contact in the System for Award Management at https://www.acquisition.gov; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this

Web site.

(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice

Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the "Web Based Training" link on the

WAWF home page at https://wawf.eb.mil/.

(e) WAWF methods of document submission. Document submissions may be via Web entry, Electronic Data Interchange, or File Transfer

Protocol.

(f) WAWF payment instructions. The Contractor must use the following information when submitting payment requests and receiving reports in WAWF for this contract/order:

(1) Document type. The Contractor shall use the following document type(s).

Invoice as 2-in-1 (Service Only)

(2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance location(s) in WAWF, as specified

4 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

by the contracting officer.

Inspection/Acceptance: W15BW9

(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in

WAWF when creating payment requests and receiving reports in the system.

Routing Data Table*

Field Name in WAWF Data to be entered in WAWF

Pay Official DoDAAC TBD

Issue By DoDAAC W15QKN

Admin DoDAAC TBD

Inspect By DoDAAC W15BW9

Ship To Code n/a

Ship From Code n/a

Mark For Code n/a

Service Approver (DoDAAC) W15BW9

Service Acceptor (DoDAAC) W15BW9

Accept at Other DoDAAC n/a

LPO DoDAAC n/a

DCAA Auditor DoDAAC n/a

Other DoDAAC(s) n/a

(4) Payment request and supporting documentation. The Contractor shall ensure a payment request includes appropriate contract line item and subline item descriptions of the work performed or supplies delivered, unit price/cost per unit, fee (if applicable), and all relevant back-up documentation, as defined in DFARS Appendix F, (e.g. timesheets) in support of each payment request.

(5) WAWF email notifications. The Contractor shall enter the email address identified below in the "Send Additional Email

Notifications" field of WAWF once a document is submitted in the system.

nadine.k.schneider.civ@mail.mil christie.r.vicci.civ@mail.mil

(g) WAWF point of contact. (1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact.

TBD

(2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988.

(End of clause)

5 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 PROPOSAL SUBMISSION ___________________

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

Tactical Mission Command Applications (TMCA) solicitation.

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/Subfactor 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

Offeror's 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 ninety (90) days after proposal due date.

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:

US Army Contracting Command - New Jersey

ACC-NJ-JA, Bldg. 9

ATTN: Nadine Schneider Telephone: (973)724-4800

Picatinny Arsenal, NJ 07806-5000

Email: nadine.k.schneider.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 paper copy of the attached 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 in Section B and Pricing

Matrices in Section J, 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. Original and four (4) paper copies and four (4) electronic CD copies of the proposal volumes, as reflected in L.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

Offeror's 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

6 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

Offerors with a portal in which to submit Reps/Certs in a publicly accessible format, nullifying the requirement to submit identical information in response to each and every Federal contract solicitation. As a requirement under the Tactical Mission Command

Applications 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 Offeror's 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 100 pages)*

Volume II: Past Performance Factor (No Maximum)

Volume III: Price Factor (No Maximum)

Volume IV: Small Business Participation Factor (No Maximum)

Volume V: Solicitation, Offer and Award Documents and Certifications/Representations

(includes Small Business Subcontracting Plan) (No Maxiumum)

*Resumes and Letters of Commitment will not count against the Technical Factor page limit, but shall not exceed ten (10) pages per subfactor.

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 and Subfactors 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

7 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 Tactical Mission Command Applications (TMCA) program except for the area of Past Performance. In the response to the

Request for Proposal, the Offeror must address the following Factors and Subfactors:

L.4.1 Volume I - FACTOR 1: TECHNICAL _______________________________

L.4.1.1 Subfactor 1: Program Management & Administration

The Offeror shall provide a detailed technical approach for Program Management & Administration to meet the requirements of the Tactical

Mission Command Applications (TMCA) solicitation and Performance Work Statement (PWS). Proposals shall address, at a minimum, the following:

a. Information with respect to Technical Process/Capability Maturity Model Integration (CMMI) (or equivalent) practices, Six

Sigma, Lean Design, cost reduction, reliability improvement, and how these continuous process improvements are incorporated.

b. A summary of teaming/subcontracting arrangements, if applicable. Each proposed Team Member shall be identified by company name and address. The Offeror shall provide a matrix identifying the Team Members vs. key solicitation and PWS requirements.

The Offeror shall provide resumes for proposed personnel including relevant knowledge, skills, experience, and training/certifications to meet their assigned labor category description per Attachment 0001. The Offeror shall also provide Letters of Commitment for proposed personnel's availability to begin performance at time of contract award.

L.4.1.2 Subfactor 2: Architecture & Systems Engineering

The Offeror shall provide a detailed technical approach for Architecture & Systems Engineering to meet the Tactical Mission Command

Applications (TMCA) solicitation and Performance Work Statement (PWS) requirements. Proposals shall address, at a minimum, the following:

a. A description of the Offerors approach to developing system architecture that demonstrates the Offerors abilities, institutional knowledge, and experience to meet the requirements detailed in the "Architecture and Systems Engineering" section of the

PWS.

b. A description of the Offerors approach for producing high quality systems engineering deliverables that demonstrates the

Offerors abilities, institutional knowledge, and experience with requirements definition and analysis, quantitative and qualitative analysis of system performance and support of Army and Joint Interoperability to meet the requirements detailed in the "Architecture and

Systems Engineering" section of the PWS.

The Offeror shall provide resumes for proposed personnel including relevant knowledge, skills, experience, and training/certifications to meet their assigned labor category description per Attachment 0001. The Offeror shall also provide Letters of Commitment for proposed personnel's availability to begin performance at time of contract award.

L.4.1.3 Subfactor 3: Software Design, Development, and Systems Integration

The Offeror shall provide a detailed technical approach for Software Design, Development, and Systems Integration to meet the requirements of the Tactical Mission Command Applications (TMCA) solicitation and Performance Work Statement (PWS). Proposals shall address, at a minimum, the following:

a. A description of the Offerors approach to developing Software Designs that demonstrates the Offerors abilities, institutional knowledge, and experience to develop to create a high quality software design through the translation of capability descriptions and system engineering requirements, and successfully implementing the software design within program quality, budget and schedule constraints to meet the requirements detailed in the "Software Design" section of the PWS.

b. A description of the Offerors approach to Software Development that demonstrates the Offerors abilities, institutional knowledge, and experience to develop high quality software through the translation of capability descriptions and system engineering requirements, and successfully implementing the software design within program quality, budget and schedule constraints to meet the requirements detailed in the "Software Development" section of the PWS.

c. A description of the Offerors approach to Systems Integration that demonstrates the Offerors abilities, institutional knowledge and experience to perform effective Systems Integration to meet the requirements detailed in the "Systems Integration" section of the PWS.

8 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

The Offeror shall provide resumes for proposed personnel including relevant knowledge, skills, experience, and training/certifications to meet their assigned labor category description per Attachment 0001. The Offeror shall also provide Letters of Commitment for proposed personnel's availability to begin performance at time of contract award.

L.4.1.4 Subfactor 4: Software Testing, Evaluation, and Security

The Offeror shall provide a detailed technical approach for Software Testing, Evaluation, and Security to meet the requirements of the

Tactical Mission Command Applications (TMCA) solicitation and Performance Work Statement (PWS). Proposals shall address, at a minimum, the following:

a. A description of the Offerors approach for testing and evaluation that demonstrates the Offerors abilities, institutional knowledge, and effective usage of test management, methodologies, techniques, tools, and best practices to ensure that products that pass acceptance testing are ready for certification and deployment to meet the requirements detailed in the "Test and Evaluation" section of the PWS.

b. A description of the Offerors approach for collecting, analyzing and reporting data for software metrics and software test management reporting to meet the metrics requirements detailed in the "Systems Engineering", "CSC and CSCI Integration and Testing" and

"Test Management Metrics" sections of the PWS.

The Offeror shall provide resumes for proposed personnel including relevant knowledge, skills, experience, and training/certifications to meet their assigned labor category description per Attachment 0001. The Offeror shall also provide Letters of Commitment for proposed personnel's availability to begin performance at time of contract award.

L.4.1.5 Subfactor 5: Software Maintenance, Engineering, and Logistical Support

The Offeror shall provide a detailed technical approach for Software Maintenance, Engineering, and Logistical Support to meet the requirements of the Tactical Mission Command Applications (TMCA) solicitation and Performance Work Statement (PWS). Proposals shall address, at a minimum, the following:

a. A description of the Offerors approach to software maintenance that demonstrates the Offerors abilities, institutional knowledge, and effective usage of software maintenance methodologies, techniques, tools, and best practices to meet requirements detailed in the "Software Maintenance" section of the PWS.

b. A description of the Offerors approach to engineering support that demonstrates the Offerors abilities, institutional knowledge, and effective usage of engineering support methodologies, techniques, tools, and best practices to leverage the experience of subject matter experts (SMEs) to meet requirements detailed in the "Engineering Support" section of the PWS.

c. A description of the Offerors approach to logistical support that demonstrates the Offerors abilities, institutional knowledge, and experience providing effective support to the logistics support integrator, the processes that the Offeror plans to use to ensure the integrator is able to develop adequate documentation/training and provide required field support for any software that is developed and fielded to the Army to meet requirements detailed in the "Support to Logistics" section of the PWS.

The Offeror shall provide resumes for proposed personnel including relevant knowledge, skills, experience, and training/certifications to meet their assigned labor category description per Attachment 0001. The Offeror shall also provide Letters of Commitment for proposed personnel's availability to begin performance at time of contract award.

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 Offeror's 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 Government reserves the right to use or not use past performance information submitted by the Offeror based on whether or not adequate recorded past performance information is available in its Federal databases. Since the Government may not necessarily interview any or all of the sources provided by the Offerors, it is incumbent upon the Offeror to explain the relevance of the data provided. The burden of providing thorough and complete past performance information remains with the Offerors. Proposals

9 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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). PLEASE NOTE:

While an Offeror may submit past performance information on relevant efforts where they performed as a major subcontractor, the

Government does not have privity with subcontracts and therefore, may not be able to obtain qualitative information.

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

(c) Government's 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 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 0011). 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 christie.r.vicci.civ@mail.mil. The Offeror shall also e-mail to the Contracting

10 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

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 Offeror shall complete Attachment 0002 which shall contain the offerors FFP fully loaded labor rates (inclusive of direct labor, indirect expenses and profit) for each labor category and ordering period. The Offeror shall propose one fully loaded labor rate for each labor categories for all five (5) ordering periods in Attachment 0002. Offerors may not deviate from the labor categories and hours listed by labor category and ordering period in Attachment 0002. The proposed fully loaded labor rates will be incorporated into any contract that may be awarded as a result of this solicitation. Offerors will have the opportunity to propose lower fully loaded FFP labor rates for orders but may not exceed what is incorporated into in the basic contract.

L.4.3.2 The Offeror shall complete Attachment 0003 which shall contain the offerors FFP indirect rates applicable to travel and ODCs.

The proposed indirect rates will be incorporated into any contract that may be awarded as a result of this solicitation. Offerors will have the opportunity to propose lower FFP indirect rates for task orders but may not exceed what is incorporated into in the basic contract.

L.4.3.3 Submission of data in accordance with the Contract Data Requirements List (CDRL), DD Form 1423 and Contractor Manpower

Reporting is a requirement for the contract but shall be Not Separately Priced.

L.4.3.4 If an Offeror fails to submit a complete proposal including all attachments and NSP items, the Government may reject the offer.

L.4.3.5 Task Orders will be issued and evaluated in accordance with the Ordering Procedures in Section A of this solicitation.

L.4.3.6 Unbalanced Pricing - If the Offeror's labor rates and/or indirect rates appear unbalanced when comparing them ordering period to ordering period, the Offeror shall provide documentation, including calculations and supporting rationale, explaining the apparent unbalanced pricing.

L.4.3.7 Each Ordering Period of the contract shall be from the date of award until one year later. The estimated award date for this

IDIQ contract is 13 January 2016, therefore the ordering periods shall be as follows:

Ordering Period 1: Twelve (12) months from the date of contract award

Ordering Period 2: Twelve (12) months from the end of Ordering Period 1

Ordering Period 3: Twelve (12) months from the end of Ordering Period 2

Ordering Period 4: Twelve (12) months from the end of Ordering Period 3

Ordering Period 5: Twelve (12) months from the end of Ordering Period

L.4.3.8 Please note: The Government reserves the right to award a single contract should proposal submission identify only one (1) acceptable source.

L.4.4 Volume IV - FACTOR 4: SMALL BUSINESS PARTICIPATION __________________________________________________

L.4.4.1 The Small Business Participation Factor Volume is comprised of a single chapter. Offerors are responsible for including sufficient detail to permit a complete evaluation. Any information provided as part of the Small Business Participation Factor Volume may be used to correlate the evaluation of the other proposal volumes.

L.4.4.2 This provision applies to every Offeror (U.S. and non-U.S.), regardless of size status or locations of working facilities or headquarters. For proposal preparation purposes, the Offeror's Small Business Participation proposals shall be consistent with any subcontracting references/identification contained elsewhere in any other Factor Volume. Percentages are calculated using proposed total contract price as calculated in accordance with D.4.3. This price becomes the denominator and includes first-tier subcontractors only. For the purpose of evaluating Small Business Participation, the total contract price is the sum of the extended prices for all five (5) ordering periods on Attachment 0002 which is the estimated maximum labor to be procured on this contract. Offerors shall also explain their rationale as to why the percentage of SB participation being utilized for this effort is appropriate for their company.

Offerors shall describe their approach and efforts undertaken to utilize small businesses (SB). SB targets will be incorporated into any resulting prime contract and contractors will be required to report SB participation.

L.4.4.3 All Offerors, including Offerors who are themselves U.S. small business concerns based on the NAICS code assigned to this requirement, are to identify the extent to which U.S. small business concerns will be utilized as first-tier subcontractors in the performance of this proposed contract. U.S. small business concerns are defined (1) in FAR 19.001 and (2) by the criteria and size standards in FAR 19.102 for the applicable NAICS code. U.S. small business concerns include Small Businesses (SBs), Small Disadvantaged

Businesses (SDBs), Woman-Owned Small Businesses (WOSBs), HUBZone Small Businesses (HUBZone SBs), Veteran-Owned Small Businesses (VOSBs), 11 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

and Service Disabled Veteran-Owned Small Businesses (SDVOSBs).

L.4.4.4 If the Offeror (to include any U.S. small business concerns who are proposing as part of a joint venture or teaming arrangement) is itself a U.S. small business concern, the Offeror's own participation as a SB, SDB, WOSB, HUBZone SB, VOSB, or SDVOSB will also be considered small business participation for the purpose of this evaluation. In this event, the extent of the Offeror participation as a U.S. small business concern shall be detailed in the same manner as subcontracts to first-tier U.S. small business concerns.

L.4.4.5 Small Business Amounts: All Offerors shall address anticipated U.S. small business concern participation and subcontracting based on the total contract dollars proposed by the Offeror.

L.4.4.6 The Offeror shall provide information for small business participation and subcontracting in a table format in accordance with the following example: __

| Business Category | $ Cost All Contracts | % of SB Participation | Cost Total SubK |

| Contract Total Price | $43.00 | | |

| SB | 10.34 | 0.24 | $10.34 of $43.00 |

| SDB | 2.86 | 0.0665 | $2.86 of $43.00 |

| SDB | 2.36 | 0.055 | $2.36 of $43.00 |

| HBCU/MI | 0.5 | 0.0115 | $0.50 of $43.00 |

| WOSB | 1.55 | 0.036 | $1.55 of $43.00 |

| HUBZone SB | 1.08 | 0.025 | $1.08 of $43.00 |

| VOSB | 1.55 | 0.036 | $1.55 of $43.00 |

| SDVOSB | 1.46 | 0.034 | $1.46 of $43.00 |

L.4.4.6.1 Guidance for filling in the above "Small Business Participation" Table:

(a) Include first-tier subcontractors only. Note that members of a joint venture may be considered the Offeror or the first tier subcontractors, depending on the legal form of the joint venture as defined in its agreement document.

(b) If the Offeror is a U.S. small business concern, detail the extent of the Offeror participation as a U.S. small business concern in the same manner as subcontracts to first tier U.S. small business concerns.

(c) Percentages should be rounded to the nearest tenth of a percent.

L.4.4.6.2 Additional Guidance for particular Business Categories:

(a) For "Contract Total Price": Include the Offeror's proposed Total Contract Price on this line.

(b) For SB: Include U.S. small business concerns from all categories (i.e. SB, SDB, WOSB, HUBZone SB, VOSB, SDVOSB and HBCU/MI) in the dollars and percentage on this line. The SDB, WOSB, HUBZone SB, VOSB and SDVOSB are subcategories of SB and the dollars in each of these may not add to match the total dollars in the SB line due to the following: In some cases the same dollars may be reported in more than one block (i.e., a $10,000 subcontract to a Woman-Owned Small Business that is also a Service-Disabled Veteran-Owned Small Business should be entered on four rows: $10,000 under SB, $10,000 under WOSB, $10,000 under VOSB and $10,000 under SDVOSB). Be sure that the dollars are counted in the SB line only once and not four times (e.g. $40,000 representing the same firm participating at $10,000 in differing categories). Note that the SB percentage is not simply a total of the percentages of each SB subcategory and must be calculated separately as shown in the chart.

(c) For HUBZone SB: Include only "SBA certified" HubZone SBs. Note that this is different from some of the state HUB certifications.

(d) The term "small disadvantaged business," when used in accordance with FAR 52.219-9, includes Historically Black Colleges and

Universities (HBCU) and Minority Institutions (MI), in addition to small disadvantaged business concerns. The percentages for HBCU and

MI shall be separately identifiable but included in the overall SDB percentage.

L.4.4.7 Small Business List: All Offerors shall provide the names and CAGE codes of small business concerns (including the Offeror if a small business concern) who would participate in accomplishing the proposed contract; the small business classification of each U.S.

small business concern (i.e. SB, SDB, WOSB, HUBZone SB, VOSB and SDVOSB); a short description of the specific services to be provided by each small business concern; and the estimated total dollars for each service or product.

a. This data shall be provided in a table format in accordance with the following example:

12 14

Name of Offeror or Contractor:

PIIN/SIIN MOD/AMD

| Name | | Location | SB | Description | Total |

| of | CAGE | | Class | of | $ |

| SB | Code | | | Supplies | (in |

| Concern | | | | or Services | millions) |

| ABC Co. | 123XX | City, USA | SB | Wire | $0.50 |

| DEF Co. | XX123 | City, USA | SB | Plating | $0.75 |

| GHI, Inc. | DD123 | City, USA | SB, WOSB, VOSB | Circuit Cards | $1.20 |

b. If a small business does not have a CAGE code, insert the word "None" in the table above. Note that during the evaluation, the

Government may request that the Offeror submit a letter from the small business affirming the information provided in your proposal.

c. For SB Classifications(s), list all SB classifications that apply to each concern in the table above.

L.4.4.8 If the Offeror IS NOT a U.S. small business concern and must submit a Small Business Subcontracting Plan under the RFP in accordance with FAR 52.219-9, the Small Business Subcontracting Plan shall be consistent with the Offeror's Small Business Participation proposal information provided in response to D.4.4.5 (recognizing that the Small Business Subcontracting Plan percentages will be different in that the percentage calculation denominator is total subcontracting amount as opposed to this Small Business Participation

Factor where the percentage calculation denominator is the Offeror's proposed Contract Target Price).

L.4.4.9 Compliance with FAR 52.219-9.

L.4.4.9.1 Offerors which are both: (a) other than U.S. small business concerns (as defined by the NAICS code applicable to the RFP), and (b) have had prior contracts requiring the submission of a Small Business Subcontracting Plan in accordance with FAR 52.219-9 are to:

Provide a description of their performance in complying with the requirements of FAR 52.219-9, including documentation of both their goals and their accomplishment of the goals established under subcontracting plans of prior contracts performed over the past twelve

(12) months (from date of solicitation issuance). This documentation shall include Individual Subcontracting Reports (ISRs/DD Form 294s) which list both goals and accomplishments against individual or master plans. If over the last twelve (12) months from the date of RFP release, the Offeror reported accomplishments against commercial or comprehensive subcontracting plans in lieu of individual or master plans, the Offeror shall submit the plans to document the goals and the Summary Subcontract Reports (SSRs/DD Form 295s) to document the accomplishments. (Note: if the Offeror has not performed a contract over the past twelve (12) months, which included FAR 52.219-9, the

Offeror shall so state).

L.4.4.9.2 Offerors which have had prior contracts requiring a Small Business Subcontracting Plan IAW FAR 52.219-9 and provide the information requested in D.4.4.9.1 above shall not respond to D.4.4.10 below.

L.4.4.9.3 If the reporting entity listed on a subcontracting report is different from the name of the proposing prime, provide an explanation of the legal relationship between the other entity and the proposing prime and a description of how the other entity's small business accomplishments reported are applicable to the current proposal. This explanation should include Business Name, CAGE Code and

DUNS number of the other entity and the proposing prime.

L.4.4.10 Approach to meeting FAR 52.219-8. Offerors which are either U.S. small business concerns, or other than U.S. small business concerns (as defined by the NAICS code applicable to the RFP) having had no prior contracts requiring a Small Business Subcontracting

Plan in accordance with FAR 52.219-9 shall substantiate their proposed approach to meeting the requirement of FAR 52.219-8.

Substantiation may include providing:

(a) A description of the Offeror's performance, over the past twelve (12) months (from date of solicitation issuance), in complying with the requirements of FAR 52.219-8 (Note: if the Offeror has not performed a contract over the past twelve (12) months (from date of solicitation issuance), which included FAR 52.219-8, the Offeror shall so state);

(b) A description and available documentation of any methods or techniques used to promote small business participation;

(c) Any listings of U.S. small business concerns who are subcontracting candidates;

(d) Internal procedures used to monitor small business participation during contract performance; and/or

(e) Any other information substantiating that the Offeror will satisfy the requirements of FAR 52.219-8.

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…