W911SR-17-R-0002-0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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

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

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

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

FAR (48 CFR) 53.243

The purpose of this amendment is to:

1) Provide Questions and Answ ers (Q&As) dated 9 November 2016, in response to the solicitation posted on 2 November 2016. Section J, Attachment 12_JEM Questions and Answ ers Q&As

2) Revise CDRLS, DD Form 1423. CDRL A004 and A024.

3) Revise Attachment 4_ Excel Cost Proposal Template 9 NOV 16.

1. CONTRACT ID CODE PAGE OF PAGES

1 20

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

16C. DATE SIGNED

BY 09-Nov-2016

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

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

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W911SR-17-R-0002

X 9B. DATED (SEE ITEM 11)

02-Nov-2016

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

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

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

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

09-Nov-2016

CODE

USA CONTRACTING CMD-APG. - W911SR

EDGEWOOD CONTRACTING DIVISION

E4215 AUSTIN ROAD

ABERDEEN PROVING GROUND MD 21010-5401

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W911SR-17-R-0002

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been added by full text:

AMENDMENT 0001

Section J has been revised. This version supersedes all previous versions. Changes are highlighted in red.

Exhibits

Exhibit A DD Form 1423, Contract Data 9 November 2016 Requirements List (CDRL)

Attachments

1 Task Order 0001 PWS 19 October 2016

2 Award Fee Plan 26 July 2016

3 Past Performance Questionnaire

4 Excel Cost Proposal Template 9 November 2016

5 Defined Labor Categories

6 ProjectForge Access Request Form and Non- Disclosure Agreement

7 Government Furnished Information Listing April 2016

8 DD254 Contract Security Specification 4 January 2016

9 Joint Program Executive Office For Chemical and Biological Defense (JPEO-CBD) Critical Information List (CIL)

10 Facility Clearance (FCL) Request October 2015

11 Excel Uncosted Proposal Template

12 JEM Questions and Answers Q&As 9 November 2016

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been added by full text:

AMENDMENT 0001

Section L has been revised. This version supersedes all previous versions. Changes are highlighted in red.

Small Disadvantaged Business goals have been revised in section L.3.5.3, Table L-3 and L.3.5.3.1.4.

JEM ProjectForge

The Army Contracting Command – Aberdeen Proving Ground (ACC/APG) is providing an online repository, hereafter referred to as the ProjectForge, which will provide prospective Offerors access to various program documents and artifacts such as software and technical data that will provide insight into the JEM Program.

Access to the JEM Project will require a DoD PKI certificate, either via a Common Access Card (CAC) or an External Certification Authority (ECA) soft certificate. If an ECA certificate is required, information on obtaining one through an authorized vendor can be found on the ECA PKI Program’s website: http://iase.disa.mil/pki/eca/.

This MUST be completed BEFORE requesting ProjectForge access.

Access to the JEM Project is limited to U.S. DoD Contractors and their identified subcontractors.

Each Contractor shall have a Primary Point of Contact (PPOC) submit an initial request for ProjectForge access on behalf of the firm. This access must be obtained prior to any other individual requests being submitted.

The PPOC shall request access to ProjectForge as follow:

(1) Verify listing in Central Contracting Registry at http://www.federalcontractorregistry.com [If registration is confirmed, proceed to step (2)]

(2) The PPOC will access the system using the following link: http://project.forge.mil

(3) Follow the self-registration process to create a ProjectForge account. You need to setup an account now, to allow the administrator to later search for your account and add you to the “access granted” list.

(4) Provide the ProjectForge Access Request Form and Non-Disclosure Agreements (NDAs) provided in

Section J of the RFP. These documents shall be emailed to Kelly Paul at kelly.n.paul.civ@mail.mil and David Shriner at david.j.shriner3.civ@mail.mil.

(5) In addition to the items listed in (4), the PPOC shall also provide the following information EXACLTY as listed to the individuals listed under (4) in their email:

a. Company Name

b. Company Address

c. Company’s Commercial and Government Entity (CAGE) code

d. Company’s Data Universal Numbering System (DUNS) number

e. PPOC’s Name

f. PPOC’s Corporate Email

g. PPOC’s Telephone Number

(6) In addition to the items listed in (4) and (5) the PPOC must provide the following individual information for any additional Individuals Users (IUs) from the Contractor requesting access:

a. Complete Name

b. Phone Number

c. Email address – must be a corporate email address

d. Citizenship (MUST be a U.S. citizen)

(7) Upon approval, the PPOC will receive an email notification from the JEM Project Administrator indicating that the PPOC and other employees can request access to the ProjectForge website. This will usually occur within 72 hours (excluding weekends and holidays).

Question about this process should be directed to Kelly Paul at kelly.n.paul.civ@mail.mil and David Shriner at david.j.shriner3.civ@mail.mil.

FACILITY CLEARANCE SPONSORSHIP DURING THE PRE-AWARD PHASE

In the event that the Offeror does not hold a security clearance, in accordance with the DD Form 254 in Section J, the JPEO-CBD Security office will be able to sponsor the Offeror. The Offeror shall complete the following requirements for sponsorship during the pre-award phase:

Complete Facility Clearance (FCL) Request Form on Company letterhead (Section J of the solicitation) and submit the request form to Contract Specialist, kelly.n.paul.civ@mail.mil and the Contracting Officer, david.j.shriner3.civ@mail.mil. The Government will submit the FCL request letter and a copy of the DD254 to the Defense Security Service (DSS) Facility Clearance Branch (FCB) for processing. This request must be submitted prior to the closing time of this solicitation.

The FCL requirements are set forth in the National Industrial Security Program (NISP) and the specifics are spelled out in the National Industrial Security Program Operating Manual (NISPOM).

The Offeror shall possess, or acquire prior to award of the contract, a facility clearance equal to the highest classification stated on the Contract Security Classification Specification (DD Form 254) attached to this solicitation.

Accessing Controlled Data

Section J of this solicitation identifies the following controlled data whose access is controlled:

Government Furnished Information Listing

The Government Furnished Information Listing, attached to Section J of the solicitation, is restricted and can be accessed electronically via the Federal Business Opportunities website (https://www.fbo.gov) with valid contractor login credentials.

Once directed to the Federal Business Opportunities Website search for the JEM solicitation and follow these steps:

1) Log in using your SAM Marketing Partner Identification Number (MPIN) code

2) Select "Request Explicit Access"

3) Select "Verify MPIN"

4) This will generate an email to the FBO System Administrator

5) Please allow 2-3 working days to complete the FBO-TDP process from the FBO system

6) The FBO Administrator will provide notice of contractor approval or denial for access to the contract specialist, who will then grant “Explicit Access” to the controlled data.

For more specific instructions on how to access controlled data and requesting explicit access view the FBO Vendor Guide at https://www.fbo.gov/index?s=getstart&mode=list&tab=list&tabmode=list&static=guides

Acquisition Source Selection Interactive Support Tool (ASSIST)

During the conduct of this acquisition, the ASSIST will be used by the Government to support the proposal evaluation and source selection process. A separate tool, the ASSIST2Industry, will be used in conjunction with ASSIST to accomplish all exchanges with The Offeror after receipt of proposals pursuant to Federal Acquisition Regulation (FAR) 15.306. ASSIST2Industry provides the ability for the Government to issue, and the Offeror to receive and respond to, all Evaluation Notices (ENs) in a secure online environment.

In order to initiate the use of ASSIST2Industry, the Offeror shall provide the names, company titles, telephone numbers, and email addresses of two (2) individuals that the Offeror has designated as responsible for receiving and responding to Government ENs through ASSIST2Industry as stated in L.3.6.1.4 The designation of two (2) individuals is for the purpose of insuring availability of one individual if the other individual is not available.

After the solicitation’s closing date, the Government will establish an account in ASSIST2Industry for each individual identified by the Offeror that has submitted a proposal in response to this solicitation. The two individuals named by the Offeror will be authorized access to that account. Two (2) separate system generated emails will be sent to each individual. One of the emails will contain the individual’s ASSIST2Industry username.

The other email will contain the individual’s temporary password. Using the provided username and temporary password, each individual can then go to https://ASSIST2Industry.army.mil to access the account. NOTE: The first time a user logs in, the user will be required to change the temporary password before the user can proceed to use the site.

Whenever the Government issues ENs to the Offeror through ASSIST2Industry, the Government’s Procuring Contracting Officer will notify the Offeror through a medium independent of ASSIST2Industry ( e.g., e-mail) that the Offeror has ENs in ASSIST2Industry waiting for a response. There will be no ENs in ASSIST2Industry until such notice is issued by the Procuring Contracting Officer. The Offeror can contact the ASSIST2Industry helpdesk at (609) 562-7050 or (609) 562-7031 for any technical assistance that may be needed.

The Offerors are cautioned that the system generated emails referred to above are intended for administrative purposes only. Receipt of these emails does not constitute the commencement of any type of exchange with the Offeror in accordance with FAR 15.306(a), (b), or (d) (i.e., clarifications, communications, or discussions). Also, receipt of these emails does not signify that a competitive range determination in accordance with FAR 15.306(c) has been made or that the Offeror’s proposal will be included in the competitive range when that determination is made. All notifications that any type of exchange with the Offeror has commenced and the Offeror has evaluation notices (ENs) available to respond to, or any notification that the Offeror’s proposal has been included in or excluded from the competitive range, will be sent to the Offeror by the Procuring Contracting Officer independently of the Assist2industry.

Instructions to Offerors

The Government intends to make a Single Award Indefinite Delivery/Indefinite Quantity (SA ID/IQ) contract under this solicitation. The ordering period for the SA ID/IQ contract is five (5) years in duration. The period of performance for a Task Order (TO) will be specified in each TO.

All questions shall be submitted via email to kelly.n.paul.civ@mail.mil and david.j.shriner3.civ@mail.mil no later than 4:00 PM Eastern Standard Time on November 8, 2016.

All communications shall be conducted only in writing and directly to the Contract Specialist and Procuring Contracting Officer as identified herein. Offerors shall not contact any other Government personnel other than the Contract Specialist or Procuring Contracting Officer identified. Contacting any other Government personnel other than the Contract Specialist or Procuring Contracting Officer identified may result in an organizational conflict of interest (OCI) and may result in an Offeror being excluded from competition and award.

L.1 PROPOSAL SUBMISSION INSTRUCTIONS:

L.1 Proposal Submission Instructions:

L.1.1 In order for proposals to receive consideration for award, the Offeror shall ensure that the information furnished in support of the proposal is factual, accurate, complete and defensible. Failure to provide the information requested by the solicitation may render the Offeror’s proposal incomplete and ineligible for further consideration for award. The Offeror’s proposal shall be submitted electronically via the FedBizOpps.gov (FBO) Secure Document System (SDS) as further discussed below. Proposals Volumes shall not contain classified data. The use of hyperlinks in proposals is prohibited.

L.1.2 The solicitation will be issued electronically, as well as any amendments subsequently issued thereto. It will therefore be the sole responsibility of all interested parties to periodically access the FBO website described below in order to obtain any amendments which may be issued. Failure by the Offeror to obtain said amendments, and to respond to them prior to the date and time set for receipt of proposals is at the sole risk of the offering contractor, and shall result in offers or proposals, (or any portion thereof); being declared unacceptable, which will result in the rejection of proposal submissions.

L.1.3 All submissions shall strictly comply with all filing requirements and content as specifically set forth in the solicitation. Failure to fully comply with all filing requirements shall result in rejection of an offer/submission as unacceptable. Offeror’s proposing conditions or exceptions to the solicitation requirements or terms and conditions will also have their proposals determined unacceptable.

L.1.4 Requirements/Instructions for using the FBO Secure Document System (SDS) located at www.fbo.gov:

L.1.4.1 An Offeror must be registered in the System for Award Management (SAM) at www.sam.gov and have a SAM Marketing Partner Identification Number (MPIN) and CAGE Code. For further information regarding registration for SAM or registration/use of FBO, please visit the FBO Learning Center at https://gsafsd.servicenow.com/fsd-gov/learning-center-system.do?sysparm_system=FBO and the FBO Vendor Guide, particularly Chapter 4.

L.1.4.2 If the solicitation is found by searching on FBO, Offerors may start the online offering process by using the “Notice Details” sub-tab (once a vendor has selected the review icon, the “Notice Details” sub-tab is opened). Under the “Notice Details” sub-tab, there will be a blue “click here” link to submit a response; if selected, the system will open a new tab called “Electronic Response.” At this point the Offeror shall upload all proposal documents as specified in the Solicitation. If the response deadline has passed for that opportunity, the user will no longer be able to submit an electronic response.

L.1.4.3 Offerors should note that due to the structure of the FBO SDS, obsolete attachments cannot be removed from existing packages. As such, Offerors need to ensure that they are accessing the most current version of the attachments when submitting their proposal.

L.1.4.4 The Offeror will receive a confirmation of offer upon completion of the offer submission process. If problems are encountered using FBO SDS, the Offeror may contact the FBO Learning Center at https://gsafsd.servicenow.com/fsd-gov/learning-center-system.do?sysparm_system=FBO or the FBO Vendor Guide."

L.1.4.5 The Offeror bears the responsibility to ensure timely transmission of their offer, that the offer is responsive to all requirements set forth in the solicitation, and to ensure the availability of an open transmission line and to take into consideration the length of time required to complete an upload transaction prior to the solicitation closing date/time stated in the solicitation. In no circumstances shall the tender of any offer or other required document that is filed beyond any filing deadline be considered. Proposals received will be handled in accordance with FAR 52.215-1(c)(3).

L.1.5 Each Offeror shall submit no more than one (1) proposal. The Offeror’s /proposal in response to this solicitation must be submitted individually, and must be separately and correctly identified as described in this section.

L.1.6 The preferred method is for the Prime to submit the Subcontractor's pricing information with its submission via FBO. As an alternative, Subcontractors may elect to submit their proprietary pricing data directly to the Procuring Contracting Officer, Mr. David Shriner, at david.j.shriner3.civ@mail.mil and the Contract Specialist, Ms.

Kelly Paul, at kelly.n.paul.civ@mail.mil, thus avoiding submitting it to the prime or higher tier subcontractor(s).

The prime contractor is responsible for the consistency of the cost data between its submission and any subcontractor/interdivisional submission. The Government will not communicate with any subcontractor directly to request information or to clarify information received. In the event that a subcontractor submits cost/pricing data directly, the subcontractor shall utilize both the “Excel Cost Proposal Template.xls” and “Excel Uncosted Proposal Template.xls” provided with the solicitation in Section J. The size per email shall not exceed 20 MB. If necessary, Offerors may submit multiple emails. If submitting multiple emails, the subject line shall include "Email 1 of 2", "Email 2 of 2", as appropriate to the number of emails submitted. Offerors shall not submit compressed or .zip files.

If the Offeror does not receive confirmation of receipt, it is the responsibility of the Offeror to contact Mr. David

Shriner and Ms. Kelly Paul, to confirm their subcontractor’s pricing information has been received.

L.1.7 The Offeror shall have sole responsibility for ensuring that all electronic responses are submitted correctly, are properly identified, contain all the information requested by the Government, are responsive, and timely filed.

L.1.8. Submission of proposal via electronic mail is not authorized, except as described for subcontractor submission of proprietary data.

L.1.9 Security

L.1.9.1 For the purpose of this acquisition, an appropriate security clearance and facility clearance in accordance with the DD Form 254 demonstrates the Offeror's ability to access classified or sensitive information. An Offeror does not require a Clearance and Safeguarding security classification of Secret to propose on this solicitation;

however, the Offeror shall possess, or acquire prior to award of the contract, the appropriate classification in accordance with the DD Form 254 at the Basic ID/IQ level to be considered for award.

L.2 PROPOSAL PREPARATION INSTRUCTIONS:

L.2.1 Format: The Offeror’s Technical Approach to Task Order 0001, Management, Cost, Past Performance, Small Business Utilization and Administrative volumes shall be submitted in accordance with Table L-1. All information the Offeror wishes to have considered shall be submitted with the initial proposal and shall be confined to the appropriate volume and within the specified page limitation. The Government will not consider any information that is not included in the appropriate volume as required, or information that exceeds the number of pages allowed. The Offeror is cautioned that the Government will not read or consider any information on pages in excess of the below page limitations. Pages exceeding the limitation will be removed from the proposal prior to evaluation.

L.2.1.1 Electronic submissions shall be Microsoft Office 2013 or higher and be made, as appropriate, in Microsoft Word, Microsoft Excel (data file shall be .XLSX file format), and/or Microsoft PowerPoint. Adobe .pdf files for narrative sections are acceptable as well. Excel files shall not contain any hidden cells, hidden sheets, locked formulas, or access data from any files that are not included with the proposal package. The Offeror is responsible for ensuring electronic copies are virus free. The titles and contents of the volumes shall be as defined in this document.

L.2.1.2 Each Volume shall be an independent electronic file and submitted with the following naming convention [Volume Number, Offeror Name, Date, Volume Title,l.xls(x)/.doc] For example, “Volume I_ABC Inc._20160816_Technical Approach to Task Order 0001.doc”.

Table L-1

Volume Subject Page Limit I

Technical Approach to Task Order

II Management 30

III Past Performance 3 per Contract

Reference IV Cost Unlimited

V Small Business Utilization

VI Administrative Unlimited VII Uncosted Information Unlimited

L.2.2 The title page for each volume shall include: volume number, volume subject, and company name. The Offeror may use indices, and a proposal identification number.

L.2.3 Indices to include table of acronyms, table of contents, cross-reference matrices between the proposal and the solicitation to the proposal are used for ensuring that all pertinent sections of the proposal are fully understood. The use of an effective and organized Table of Contents and/or List of Tables/Figures along with tabs to easily locate sections of the proposal also facilitates thorough evaluation.

L.2.4 Each volume shall be as brief as possible, yet consistent with a complete submission. Pages shall not exceed

8.5 inches in width and 11 inches in length; however, oversized pages, as appropriate, not exceeding 11 x 17 inches, depicting such items as charts, matrices, or schedules may be used and will count as a single page. The Offeror shall number all pages within each volume.

L.2.5 The Offeror's proposal shall not exceed the above page limitations and shall be typed using 12 point font, Times New Roman, (tables, graphics, oversized pages, or electronic spreadsheets - 10 point font) with one-inch margins (top, bottom, left and right). Cover letters, cover page, table of contents, table of acronyms, and cross-reference matrices do not count against page count limitations.

L.2.6 The Offeror is expected to provide sufficient detail in a clear and concise manner to completely and logically address every aspect the Government intends to evaluate. The Government does not desire excess verbiage, unnecessary and elaborate brochures, or lengthy, repetitious, disorganized presentations beyond that sufficient to present a complete and clear offer. Such presentations are not desired and may be construed as an indication of the Offeror’s inefficiencies and lack of cost consciousness in proposal preparation. All Offerors are reminded that unsupported promises to comply with the contractual requirements will not be sufficient. Proposals must not merely parrot back the contractual requirements, but rather must provide convincing documentary evidence in support of any statements relating to the promised performance.

L.2.7 The Government will presume that each proposal received represents the Offeror’s best efforts to respond to the solicitation. In its proposal, the Offeror shall explain any inconsistency between proposed performance and price.

L.2.8 The Offeror shall include cost information ONLY in Volume V: Cost. Inclusion of cost data in any other Volume will result in the removal of each page containing the cost data and the entire page or pages will not be evaluated or considered as part of the proposal.

L.3 SPECIFIC INSTRUCTIONS BY VOLUME. The Offeror shall submit its proposal, segregated by volume, as follows:

Table L-2: Proposal Volume Requirement

Volume Subject I

Technical Approach to Task Order

II Management III Past Performance IV Cost V Small Business Utilization VI Administrative VII Uncosted Information

L.3.1 VOLUME I – TECHNICAL APPROACH TO TASK ORDER 0001.

The Offerors shall address the Technical Approach to Task Order 0001 factor in accordance with the instructions provided below:

L.3.1.1 Software Development Approach (SDA)

The Offeror shall provide a Software Development Approach for an agile process that describes its plan for developing JEM. The Offeror shall integrate relevant aspects of the Technical Data Package (TDP), housed on ProjectForge, into its SDA. The Offeror’s proposal shall address the following items below.

L.3.1.1.1 The process to synchronize and transition physics-based modeling software products with multiple configurations into a single Common Chemical Biological Radiological and Nuclear (CBRN) Model Interface (CCMI) integrated baseline.

L.3.1.1.2 The process to apply state-of-the-art development practices that allow for expedited, high-quality Service Oriented Architecture-based (SOA) Tactical Decision Aid (TDA) capability into software modernization and maintenance builds.

L.3.1.1.3 The process to apply state-of-the-art development practices for Graphical User Interfaces (GUIs) that utilize integrated mapping capabilities, such as GeoServer and other mapping tools, in an Ozone Widget Framework (OWF) that expedites the integration, test, and fielding of high-quality capabilities.

L.3.1.1.4 The process to utilize automated test tools such as Automated Test / Retest Toolkit (ATRT), CCMI Autogenerated Test Toolkit (CATT), and “The Plumenator” for unit level (subroutine / method), CCMI component level, and system level verification.

L.3.1.1.5 The process to integrate, modernize and sustain SOA-based TDA functionality into the Global Command and Control System Joint (GCCS-J), GCCS Maritime (GCCS-M), Command and Control Personal Computer (C2PC)/Joint Tactical COP Workstation (JTCW), and Army Battle Command Common Server (BCCS).

L.3.1.1.6 The process to upgrade and maintain an integrated software baseline of physics-based hazard prediction models such as those contained in legacy CBRN Science and Technology (S&T) products such as Hazard Prediction and Assessment Capability (HPAC), Vapor Liquid Solid Tracking (VLSTRACK), and D2Puff.

L.3.1.1.7 The process to perform developmental level verification and validation of CBRN hazard prediction modeling and simulation software.

L.3.1.1.8 Alignment of Software Development Approach to the Government’s Standard Operating Procedures 10, 12, & 31 as provided in the Technical Data Package (TDP).

L.3.1.2 Software Development Approach content and format:

L.3.1.2.1 General Software Development Activities. The Offeror shall describe their approach to perform general software development activities. If different builds or different software on the project require different planning, these differences shall be noted in the approach. In addition to the content specified below, each paragraph shall identify applicable risks/uncertainties and plans for dealing with them.

L.3.1.2.1.1 Software-development process. The Offeror shall describe the software development process to be used.

L.3.1.2.1.1.1 Software development methods. The Offeror shall describe the software development methods to be used. Included shall be descriptions of the manual and automated tools and procedures to be used in support of these methods. Reference may be made to other paragraphs in this approach if the methods are better described in context with the activities to which they will be applied.

L.3.1.2.1.1.2 Standards for software products. The Offeror shall describe or reference the standards to be followed for representing requirements, design, code, test cases, test procedures, and test results. The standards shall cover all contractual clauses concerning this topic.

L.3.1.2.1.1.3 Standards for code shall be provided for each programming language to be used.

L.3.1.2.1.1.4 Incorporating reusable software products. The Offeror shall describe the approach to be followed for identifying, evaluating, and incorporating reusable software products, including the scope of the search for such products and the criteria to be used for their evaluation. Candidate or selected reusable software products known at the time this approach is prepared or updated shall be identified and described, together with benefits, drawbacks, and restrictions, as applicable, associated with their use.

L.3.1.2.2 Approach for performing detailed software development activities. If different builds or different software on the project require different planning, these differences shall be noted in the proposal. The discussion of each activity shall include the approach (methods/procedures/tools) to be applied to: 1) the analysis or other technical tasks involved, 2) the recording of results, and 3) the preparation of associated deliverables, if applicable.

The approach shall also identify applicable risks/uncertainties and plans for dealing with them.

L.3.1.2.2.1 Establishing a software development environment. The Offeror’s proposal shall address the establishment and use of the software engineering environment, software test environment, software development library, software development files, and identification of any non-deliverable software

L.3.1.2.2.2 Software implementation and unit testing. The Offeror’s proposal shall address the implementation of the software in a test environment, preparing for unit testing, performing unit testing, revision and retesting, and analyzing and recording unit test results.

L.3.1.2.2.3 Unit integration and testing. The Offeror’s proposal shall address the preparation for unit integration and testing, performing unit integration and testing, revision and retesting, analyzing and recording unit integration and test results

L.3.1.2.2.4 Computer Software Configuration Item (CSCI) qualification testing. The Offeror’s proposal shall address the independence in CSCI qualification testing, testing on the target computer system, preparing for CSCI qualification testing, performing CSCI qualification testing, revision and retesting, and analyzing and recording CSCI qualification test results

L.3.1.2.2.5 CSCI integration and testing. The Offeror’s proposal shall address preparing for CSCI integration and testing, performing CSCI integration and testing, revision and retesting, and analyzing and recording CSCI integration and test results

L.3.1.2.2.6 System qualification testing. The Offeror’s proposal shall address the independence in system qualification testing, testing on the target computer system, preparing for system qualification testing, dry run of system qualification testing, performing system qualification testing, revision and retesting, analyzing and recording system qualification test results

L.3.1.2.2.7 Software quality assurance. The Offeror’s proposal shall address the software quality assurance evaluations, software quality assurance records, including items to be recorded, and independence in software quality assurance

L.3.2 VOLUME II – MANAGEMENT

L.3.2.1 Management of JEM.

The Offeror shall address its process for managing a program with multiple task orders on an Indefinite Delivery, Indefinite Quantity (ID/IQ) contract that may include both Cost-Plus-Award-Fee and Cost-Plus-Fixed-Fee pricing arrangements.

L.3.2.1.1 Key Personnel.

The Offeror shall identify key personnel for the program and subsequent Task Orders and discuss how the identified resources are qualified, through education and experience, to perform and manage the functions outlined in the PWS. In particular, experience shall be demonstrated regarding the analysis of chemical or biological agent(s) or toxic chemicals. For the purposes of this solicitation, the following three (3) key personnel is defined as the (1) Technical Lead, (2) Software Engineer 5/Engineer/Scientist 5, and (3) CBRN Hazard Modeling Subject Matter Expert (SME).

L.3.2.1.1.1 Key Personnel Required Qualifications. Key Personnel shall be identified by the Offeror. Refer to the attached Defined Labor Categories, in Section J. The Offeror shall submit a resume for each individual identified as Key Personnel. Resumes shall be limited to pertinent experience as described in Section J, Defined Labor Categories, and will be limited to two (2) pages per resume. Resumes will not count against overall volume page count.

L.3.2.1.1.2 The Offeror shall submit an “Availability of Key Personnel” statement that indicates each individual’s current assignment and the Offeror’s plan to ensure that the named personnel will be used on this project; however, if the named person isn’t available upon award, the Offeror shall state how they intend to ensure the requirement will be satisfactorily met.

L.3.2.1.2 The Offeror shall discuss its approach to ensuring that its team (subcontractors and personnel) will remain free of Organizational Conflicts of Interest (OCI) relative to future JEM procurements. The Offeror’s attention is directed to FAR Subpart 9.5 and Section H relating to organizational conflicts of interest. If applicable, prospective Offerors shall furnish with their proposals information that may have a bearing on any existing or potential conflict of interest. Should actual conflict(s) of interest exist, i.e. not merely ones that may potentially arise, the Offeror shall include a mitigation plan with its proposal.

L.3.2.2 Management of Task Order 0001. The Offeror shall provide a proposed JEM Management approach for Task Order 0001. The Management approach should adhere to the format and content guidelines described below.

The following items are of particular interest to the Government, and shall be addressed in the Offeror’s proposal.

L.3.2.2.1 Provide a draft Contractor Work Breakdown Structure (CWBS) and Integrated Master Schedule (IMS) that is aligned to the entire JEM Performance Work Statement (PWS) for Task Order 0001.

L.3.2.2.2 Project Planning and Oversight. The Offeror’s proposal shall address the following:

L.3.2.2.2.1 Approach for performing detailed management activities. If different builds or different software on the project require different planning, these differences shall be noted in the proposal. The discussion of each activity shall include the approach (methods/procedures/tools) to be applied to: 1) the analysis or other technical tasks involved, 2) the recording of results, and 3) the preparation of associated deliverables, if applicable. The proposal shall also identify applicable risks/uncertainties and plans for dealing with them.

L.3.2.2.2.1.1 Project Planning and Oversight. The Offeror’s proposal shall address the process for software development planning (covering updates to the Software Development Approach), CSCI test planning, system test planning, software transition planning, following and updating plans, including the intervals for management review

L.3.2.2.2.2 Project Organization and Resources. This section shall be divided into the following paragraphs to describe the project organization and resources to be applied in each build.

L.3.2.2.2.2.1 Project organization. The Offeror shall describe the organizational structure to be used on the Task Order (0001), including the organizations involved, their relationships to one another, and the authority and responsibility of each organization for carrying out required activities.

L.3.2.2.2.2.2 Project resources. The Offeror shall describe the resources to be applied to the Task Order (0001). It shall include:

L.3.2.2.2.2.2.1 Personnel resources, including: the estimated staff-loading for the project (number of personnel over time), the breakdown of the staff loading numbers by responsibility (for example, management, software engineering, software testing, software configuration management, software product evaluation, software quality assurance) and a breakdown of the skill levels, geographic locations, and security clearances of personnel performing each responsibility. The Offeror shall identify and translate, within his/her cost volume, any difference between Offeror’s labor categories and Government defined labor categories in Section J, Attachment “Excel Cost Proposal Template.xls”, Labor Category Definitions tab, Column C, Rows 2-15 and Section J, Attachment “Excel Uncosted Proposal Template.xls”, JEM uncosted tab, Column A, Rows 3-5 and Rows 10-20.

L.3.2.2.2.2.2.2 Overview of developer facilities to be used, including geographic locations in which the work will be performed, facilities to be used, and secure areas and other features of the facilities as applicable to the contracted effort.

L.3.2.2.2.2.2.3 Contractor Acquired Property (i.e hardware or equipment), software, services, documentation, data, and facilities required for the contracted effort. A schedule detailing when these items will be needed shall also be included.

L.3.2.2.2.2.2.4 Other required resources, including a plan for obtaining the resources, dates needed, and availability of each resource item.

L.3.2.2.2.2.2.5 The Offeror shall discuss their approach for the accomplishment of Task Order 0001 requirement by describing the composition of the team assigned to the JEM effort, including interfaces with subcontractors and the Government and work the Contractor and each Subcontractor will perform.

L.3.2.3 The Offeror shall submit a proposed Quality Assurance Surveillance Plan (QASP) which describes the methods used to monitor performance, and to identify the required documentation and resources to be employed for Task Order 0001. The Offeror shall define the roles and responsibilities related to the administration of the contract, identify the performance objectives, define the methodology used to monitor performance, describe the quality assurance documentation, and describe the analysis of quality assurance monitoring results.

L.3.2.3.1 The Government reserves the right to either accept or reject the Offeror’s submitted QASP for use in administering and surveilling the resultant TO.

L.3.3 VOLUME III – PAST PERFORMANCE

L.3.3.1 Information contained in this volume will be used for: (1) evaluating whether the Offeror's present/past performance is recent and relevant to the solicitation requirements, and (2) determining how well the Offeror performed on the contracts.

L.3.3.2 This volume shall be organized into the following sections:

L.3.3.2.1 Section 1 – Contract Descriptions.

This Section shall include the following information in the following format:

L.3.3.2.1.1 The Offeror shall submit with its proposal contract descriptions representing its recent and relevant performance under Government and/or commercial contracts. The past performance information may be from predecessor companies, key personnel who have relevant experience, or subcontractors that will perform major or critical aspects of the effort. “Relevant” means performance that demonstrates the Offeror has provided software Research and Development, modernization, sustainment, and fielding support within an IT-box construct or similar process on a large scale software development and integration project, with a source line of code count in excess of 3 million or greater. “Recent” means any contract under which any performance, delivery, or corrective action has taken place within the last five (5) years of the issuance of this solicitation.

L.3.3.2.1.1.1 For large multi-function firms, all past performance information provided shall be specific to the offering segment of the firm (e.g., division, group, unit, etc.) that is submitting the proposal.

L.3.3.2.1.2 The prime contractor shall submit no more than three (3) contract references and no more than one (1) contract reference from up to two (2) major subcontractors. Major subcontractors are defined as members of an Offeror’s overall team who are expected to perform ten (10) percent or more of the entire ID/IQ effort, not limited to the Task Order 0001. The following information shall be included for each contract reference:

L.3.3.2.1.2.1 Contractor place of performance, CAGE Code, and 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, current address, e-mail address, and telephone and fax numbers).

L.3.3.2.1.2.2 Government or Commercial contracting activity and current address; Procuring Contracting Officer’s name, e-mail address, and telephone and fax numbers.

L.3.3.2.1.2.3 Government or Commercial technical representative/Contracting Officer’s Representative (COR) and current email address and telephone and fax numbers.

L.3.3.2.1.2.4 Government contract administration activity and the Administrative Contracting Officer’s name, current e-mail address, and telephone and fax numbers, if applicable.

L.3.3.2.1.2.5 Contract Number and, in the case of Indefinite Delivery type contracts, GSA contracts, and Blanket Purchase Agreements, include Delivery Order Numbers.

L.3.3.2.1.2.6 Contract Type (e.g., Fixed-Price (FP), Cost Reimbursement (CR), Time & Materials (T&M), etc.). In the case of Indefinite Delivery contracts, indicate specific type (i.e., Requirements, Definite Quantity, and Indefinite Quantity) and secondary contract type (e.g., FP, CR, T&M, etc.).

L.3.3.2.1.2.7 Awarded price/cost.

L.3.3.2.1.2.8 Final or projected final price/cost.

L.3.3.2.1.2.9 Original delivery schedule, including dates of start and completion or work.

L.3.3.2.1.2.10 Final or projected final delivery schedule, including dates of start and completion of work.

L.3.3.2.2 Section 2 – Performance.

Offerors shall provide a specific narrative explanation of each contract listed in Section 1, Contract Description, describing the following:

L.3.3.2.2.1 A detailed narrative for each contract cited and the similarities and relevance of that work to the work required by this solicitation, objectives achieved, and cost growths or schedule delays encountered. The Offeror shall provide copies of Contract Deficiency Reports (CDR) and Corrective Actions submitted by the Defense Contract Management Agency (DCMA) office within the past five (5) years. The Offeror shall provide the Government with a statement indicating that there have been no CDRs in the past five (5) years, if applicable. For Government contracts that did not nor do not meet original requirements with regard to either cost, schedule, or technical performance the Offeror shall provide a brief explanation of the reason(s) for such factor(s) and any corrective actions taken to avoid recurrence. The Offeror shall not exceed three (3) pages for each contract cited (this page limitation is inclusive of all information requested in L.3.3.2.1 [Section 1] and L.3.3.2.2 [Section 2]).

L.3.3.2.2.2 The Offeror shall also provide the aforementioned information for all contracts terminated in whole or in part, for default or cause during the past five (5) years, to include those currently in the process of such termination as well as those that are not for work similar to the proposed effort. The Offeror shall also provide the aforementioned information for any proposed major subcontractor.

L.3.3.2.2.3 An Offeror with no past performance experience shall provide an explanation that they have no recent or relevant experience. In the case of an Offeror without a record of relevant past performance or for whom information on past performance is not available, the Offeror may not be evaluated favorably or unfavorably on past performance.

L.3.3.2.2.4 Offerors shall include in their proposal the written consent of their proposed major subcontractors to allow the Government to discuss the subcontractor's past performance evaluation with the Offeror during negotiations.

L.3.3.2.3 Section 3 – Past Performance Questionnaire.

L.3.3.2.3.1 For all contracts identified in Section 1, Contract Descriptions, Offerors shall distribute the Past Performance Questionnaire located in Section J. 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 following Contracting Office email addresses no later than the proposal due date: david.j.shriner3.civ@mail.mil and kelly.n.paul.civ@mail.mil. The Government requests that Offerors e-mail a POC List to ACC-APG that provides information of all entities sent a Past Performance Questionnaire, to include those of any subcontractor the Offeror chose to include as part of their Past Performance submission. The POC List shall be submitted in Word for Windows Table Format to include the following fields:

Company Name; Contract Number; Government Agency; POC Last Name, First Name; POC Title; POC Telephone Number; POC E-mail Address; and Date the Past Performance Questionnaire was e-mailed to the POC (month/day).

L.3.3.2.3.2 The Government may contact an entity to obtain feedback when a Past Performance Questionnaire is not returned. The POC List is not to be included with the Offerors proposals and is not subject to evaluation.

Offerors shall send the POC List to the following ACC-APG emails addresses: david.j.shriner3.civ@mail.mil and kelly.n.paul.civ@mail.mil prior to the closing of the solicitation.

L.3.3.2.3.3 The Government may utilize past performance information from sources other than those identified by the Offeror, (i.e., Contractor Performance Assessment Reporting System (CPARS)).

L.3.4 VOLUME IV – COST

L.3.4.1 Summary: A completed cost volume will include both a Word/PDF “Cost Narrative” and a completed “Excel Cost Proposal Template.xls” for Task Order 0001. In the “Excel Cost Proposal Template.xls” Offerors shall propose Ceiling Fee Rates and Direct Labor Ceiling Rates for inclusion into the Basic ID/IQ contract. Costs and fee for Task Order 0001, when combined, will create the total proposed price. The Task Order Price Summary tab, from the “Excel Cost Proposal Template.xls”, provides the Government with the total proposed price of Task Order 0001.

The Task Order Price Summary includes all costs associated with R&D, O&M, Procurement and FMS efforts for both Year 1 and Year 2 (Option) of Task Order 0001.

L.3.4.1.1 Ceiling Rates: Offerors shall propose Ceiling Fee Rates and Direct Labor Ceiling Rates. The Ceiling Fee Rates will serve as maximum percentages that will be used to arrive at dollar values for all contract actions resulting from award of this ID/IQ contract, including any subsequent task orders, modifications and equitable adjustments.

The Ceiling Fee rates are to be used in the Task Order 0001 proposal.

L.3.4.1.2 Award Fee Pool Percentage, Labor: 0% - 10%, using all estimated costs to be funded under a CPAF CLIN as a basis, excluding any travel, materials, equipment and ODCs. Note that there will be a 0% base fee for the

CPAF CLIN.

L.3.4.1.3 CPFF (Non-Pass Through): Fixed Fee Percentage: 0% - 10%, using all non-pass through estimated costs to be funded under a CPFF CLIN.

L.3.4.1.4 CPFF (Pass Through): Fixed Fee Percentage: 0% - 10%, using all pass through estimated costs to be funded under a CPFF CLIN. For the purposes of this solicitation, pass through costs are defined as subcontracts and resulting indirect expenses.

L.3.4.1.5 Direct Labor Ceiling Rates: Offerors shall propose rates in the tab named “DL Ceiling Rates” located in the “Excel Cost Proposal Template.xls” attached to Section J. These rates will be incorporated in the awardees basic contract as ceiling rates for future task order pricing. Offerors shall acknowledge that it will not be reimbursed by the Government for hourly rates higher than those proposed in the “DL Ceiling Rates” tab in its “Excel Cost Proposal Template.xls” for any labor category and period of performance.

L.3.4.1.6 Non-Fee Bearing Costs: ODCs shall not be used as a basis for fee.

L.3.4.2 Cost Narrative for Task Order 0001 (Word or PDF): Offerors shall utilize and submit a completed “Excel Cost Proposal Template.xls” provided with this solicitation…