W900KK-18-R-0010_Amendment.01_Modification.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) Address questions by contractors generated by the subject Request for Proposal (RFP).

2) Document the corresponding changes to the RFP initiated by the questions.

3) Provide the updated Cost Price Workbook.

4) Update Task Order 01's Performance Work Statement.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 45

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

16C. DATE SIGNED

BY 14-Dec-2017

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 W900KK-18-R-0010

X 9B. DATED (SEE ITEM 11)

17-Nov-2017

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

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

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

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

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

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

12. ACCOUNTING AND APPROPRIATION DATA (If required)

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

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

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

CONTRACT ORDER NO. IN ITEM 10A.

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

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

D. OTHER (Specify type of modification and authority)

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

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

10A. MOD. OF CONTRACT/ORDER NO.

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

6. ISSUED BY

3. EFFECTIVE DATE

14-Dec-2017

CODE

ARMY CONTRACTING COMMAND - ORLANDO

ATTN: CHARLIE DIVISION

12211 SCIENCE DRIVE

ORLANDO FL 32826-3224

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W900KK-18-R-0010

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0101

The CLIN extended description has changed from:

PWS Ref: 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.12, 3.13, 3.16, 3.18, 3.19, 3.20, 3.22

To:

PWS Ref: 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.12, 3.13, 3.15, 3.16, 3.18, 3.19, 3.20, 3.22.

CLIN 0103

PWS Ref: 3.9.1, 3.11

PWS Ref: 3.11.

CLIN 0106

PWS Ref: 3.17, 3.21

PWS Ref: 3.1.7, 3.21.

CLIN 0201

PWS Ref: 3.10, 3.10.2.2

PWS Ref: 3.10, 3.10.2, 3.10.2.1.

CLIN 0202

The option status has changed from No Status to Option.

CLIN 1101

PWS Ref: 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.12 , 3.13, 3.16, 3.18, 3.19, 3.20, 3.22PoP: TBD

CLIN 1103

PWS Ref: 3.9.1, 3.11PoP: TBD

CLIN 1106

PWS Ref: 3.17, 3.21PoP: TBD

CLIN 1301

PWS Ref: 3.10, 3.10.2.2PoP: TBD

PWS Ref: 3.10, 3.10.2PoP: TBD.

CLIN 2101

CLIN 2103

CLIN 2106

CLIN 2401

CLIN 3501

PWS Ref: 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.12 , 3.13, 3.15, 3.16, 3.18, 3.19, 3.20, 3.22PoP: TBD.

CLIN 3503

PWS Ref: 3.11PoP: TBD.

CLIN 3506

PWS Ref: 3.1.7, 3.21PoP: TBD.

CLIN 4501

PWS Ref: 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.12 , 3.13, 3.15, 3.16, 3.18, 3.19, 3.20, 3.22PoP: TBD.

CLIN 4503

CLIN 4506

CLIN 4703

PWS Ref: 3.10.1PoP: TBD

PWS Ref: 3.10, 3.10.1PoP: TBD.

CLIN 5501

PWS Ref: 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.12 , 3.13, 3.15, 3.16, 3.18, 3.19, 3.20, 3.22PoP: TBD.

CLIN 5503

CLIN 5506

CLIN 5509

The option status has changed from No Status to Option.

CLIN 5801

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

TECHNICAL DATA

C.2 TECHNICAL DATA AND INFORMATION

Technical Data and Information shall be delivered in accordance with the requirements of the Contract Data Requirements List, DD Form 1423, Exhibit A CDRLs Section J, attached hereto, and the following:

(a) The contractor shall concurrently deliver technical data and information per DD Form 1423, Blocks 12 and 13 (date of first/subsequent submission) to all activities listed in Block 14 of the DD Form 1423 (distribution and addresses) for each item. Complete addresses for the abbreviations in Block 14 are shown in paragraph (g) below. Additionally, the technical data shall be delivered to the following cognizant codes, which are listed in Block 6 of the DD Form 1423.

(1) PCO, Code ACC-ORL-OPC

(2) ACO, Code (To be Determined at time of Award)

(b) Partial delivery of data is not acceptable unless specifically authorized on the DD Form 1423, or unless approved in writing by the PCO.

(c) The Government review period provided on the DD Form 1423 for each item commences upon receipt of all required data by the technical activity designated in Block 6.

(d) A copy of all other correspondence addressed to the Contracting Officer relating to data item requirements (i.e., status of delivery) shall also be provided to the codes reflected above and the technical activity responsible for the data item per Block 6, if not one of the activities listed above.

(e) The PCO reserves the right to issue unilateral modifications to change the destination codes and addresses for all technical data and information at no additional cost to the Government.

(f) Unless otherwise specified in writing, rejected data items shall be resubmitted within thirty (30) days after receipt of notice of rejection.

(g) DD Form 1423, Block 14 Mailing Addresses: 12211 Science Drive Orlando FL 32826

C.3 DOCUMENT SUMMARY LIST (SECTION J, EXHIBIT B)

C.4 TASK ORDERS PROCEDURES

(a) The Procuring Contracting Officer (PCO) is:

Dunamis T. Triska Mrs. Triska is responsible for issuing and administering any orders placed hereunder. Any deviation from the terms of the basic contract must be submitted to the PCO for contractual action.

(b) Task orders. All orders issued hereunder are subject to the terms and conditions of this contract. The contract shall control in the event of conflict with any order.

(c) A task order shall be issued for each order. In addition to any other data that may be called for in the contract, the following information shall be specified in each order, as applicable:

(1) Date of order.

(2) Contract and task order number.

(3) Applicable contract line item number (CLIN).

(4) Description of the task to be performed.

(5) Description of the end item or service.

(6) DD Form 254 (Contract Security Classification Specification).

(7) DD Form 1423 (Contract Data Requirements List).

(8) Exact place of performance.

(9) The inspecting and accepting codes.

(10) Estimated cost and fee and level of effort by labor category (and billing rate if known).

(11) List of Government furnished property and the estimated value of the property.

(12) Invoice and payment provisions to the extent not covered by the contract.

(13) Accounting and appropriation data.

(14) Period of performance.

(15) Organizational Conflict of Interest provisions.

(16) Type of order (e.g., completion, term, FFP)

(d) Negotiated Agreement. The information contained in each task order with respect to labor categories, man-hours and delivery date shall be the result of a negotiated agreement reached by the parties in advance of issuance of the order.

(1) The PCO shall furnish the contractor with a written preliminary task order and request for proposal. The request shall include:

(i) A description of the specified work required,

(ii) The desired delivery schedule,

(iii) The place and manner of inspection and acceptance, and

(2) The contractor shall, within the time specified by the preliminary task order, provide the PCO with a proposal to perform, which shall include:

(i) The required number of labor hours by labor classification and scheduled billing rates, for each end product or task,

(ii) Overtime hours by labor category,

(iii) Proposed completion or delivery dates,

(iv) Other direct costs (i.e., direct material, travel subsistence, and similar costs)

(v) Dollar amount and type of any proposed subcontracts, and

(vi) Total estimated cost/price.

The cost factors utilized in determining the estimated cost/price under any order shall be the rates applicable at time the order is issued.

(3) Upon receipt of the proposal, the PCO shall review the estimates therein to ensure acceptability to the Government, enter into such discussions with the contractor as may be necessary to correct and revise any discrepancies in the proposal, and effect whatever internal review procedures are required. Should the PCO and contractor be unable to reach agreement as to the terms of the order prior to its issuance, the conflict shall be referred to one level above the Contracting Officer.

(e) Total Estimated Dollar Amount. The total estimated dollar amount of each order constitutes a ceiling price for that order. The requirements for notification set forth in Federal Acquisition Regulation (c) of FAR Clause 52.232-22, “Limitation of Funds” are applicable to individual task orders. The ceiling amount for each order may not be exceeded unless authorized by a modification to the order. All revisions providing additional funds to a task order will include fee in the same manner as established in the basic task order.

(f) Modifications. Modifications to orders shall be issued using a Standard Form 30 and shall include the information set forth in paragraph (c) above, as applicable.

C.5 CLIN LEVEL DESCRIPTION AND SPECIFICATIONS FOR ONESAF PRODUCTION AND

SUPPORT TASK ORDERS

C.5.1 Task Order 0001, 0005 – Software Product Baseline Management and Support (CLINs 0101, 1101, 2101, 3501, 4501, 5501) The contractor shall provide the supplies/services in accordance with Performance Work Statement (PWS) PWS-2017-036 and the Contract Data Requirement’s List (CDRLs). The contractor shall provide for services described in sections 3.2 through 3.8, 3.12, 3.13, 3.15, 3.16, 3.18, 3.19, 3.20, and 3.22 of the

PWS.

C.5.2 Task Order 0001, 0005 – Program Management (CLINs 0102, 1102, 2102, 3502, 4502, 5502) The contractor shall provide the supplies/services in accordance with PWS-2017-036 and the CDRLs.

The Contractor shall provide for services described in sections 3.1 of the PWS. The Contractor shall provide the overall management and administrative effort necessary to ensure that the requirements in this PWS are accomplished. The program management associated with this effort shall include technical and administrative planning, organization, coordination, resource allocation, development environment management/maintenance, and risk management.

C.5.3 Task Order 0001, 0005 – Development and Customer Support (CLINs 0103, 1103, 2103, 3503, 4503, 5503)

The contractor shall provide the supplies/services in accordance with PWS-2017-036 and the CDRLs.

The contractor shall provide for services described in, but not limited to, section 3.11 of the PWS. The Government will provide a not-to-exceed (NTE) ceiling and shall not be priced separately. Throughout the course of the Task Order execution, as requirements are identified, the Government will request a proposal to support each requirement from the Contractor and the contract will be modified and funded as necessary to support the execution of the requirements.

The Contractor should expect to develop, enhance, integrate and test OneSAF Product Line Architecture Components as defined in the OneSAF Product Line Architectural Specification (PLAS). A typical requirement may include, but is not limited to:

- Execution of the full software life cycle for Behavioral, Physical, Entity, Unit and Munition Model development.

- Execution of the full software life cycle for environment, service, infrastructure and interoperability component enhancements.

- Execution of the full life cycle for Mission Command Adapter interfaces and mappers.

- Provide customer support to include, problem analysis, technical support, on-site support, scenario development, set-up, test/integration, and document findings/results.

- Provide labor necessary to deliver a maintenance release/patch to support specific exercises and/or user events.

- Provide labor necessary to deliver a tailored version of the software product in accordance to section

3.9.1 of the PWS.

- Provide technical expertise, engineering design, capability production, integration and test, on-site support, training and fielding in support of Foreign Military Sales (FMS) customer requirements.

Travel, per diem, and other direct costs resulting from these requirements will be processed separately on a Cost Reimbursable CLIN.

C.5.4 Task Order 0001, 0005 – Training (1-week) (CLINs 0104, 1104, 2104, 3504, 4504, 5504) The contractor shall provide the supplies/services in accordance with PWS-2017-036 and the CDRLs.

The Contractor shall provide the labor required to provide a one (1) week training, in accordance to section 3.14 of the PWS, to a maximum of 20 students per class. Training topics may include developers, operators, maintainers, or a combination. When locations are identified, training syllabus will be coordinated with the Government. Travel, per diem, and other direct costs (ODCs) will be processed separately on a Cost Reimbursable CLIN. Course materials will not be developed under this CLIN.

Training materials are delivered as part of the software baseline release and shall be leveraged to compile the training materials for the course. Pricing of this CLIN shall include the conduct of a single 1-week course. This CLIN can be exercised up to three (3) times per base and option year.

C.5.5 Task Order 0001, 0005 – Training (2-weeks) (CLINs 0105, 1105, 2105, 3505, 4505, 5505) The contractor shall provide the supplies/services in accordance with PWS-2017-036 and the CDRLs.

The Contractor shall provide the labor required to provide a two (2) week training, in accordance to section 3.14 of the PWS, to a maximum of 20 students per class. Training topics may include developers, operators, maintainers, or a combination. When locations are identified, training syllabus will be coordinated with the Government. Travel, per diem and ODCs will be processed separately on a Cost Reimbursable CLIN. Course materials will not be developed under this CLIN. Training materials are delivered as part of the software baseline release and shall be leveraged to compile the training materials for the course. Pricing of this CLIN shall include the conduct of a single 2-week course. This CLIN can be exercised up to two (2) times per base and option year.

C.5.6 Task Order 0001, 0005 – Travel and Other-Direct-Costs (ODC) (CLINs 0106, 1106, 2106, 3506, 4506, 5506) The contractor shall provide Travel support in support of the total OneSAF program. Travel is expected to take place at CONUS and OCONUS locations. The Government will provide a NTE ceiling. CLIN will be incrementally funded as travel requirements are identified and will be in accordance with sections

3.1.7 and 3.21 of the PWS.

C.5.7 Task Order 0001, 0005 – Manpower Reporting (CLINs 0107, 1107, 2107, 3507, 4507, 5507) The Contractor shall input required information IAW PWS-2017-036 Section 3.1.1.1. This CLIN may be separately priced

C.5.8 Task Order 0001, 0005 – Technical Data and Information (CLINs 0108, 1108, 2108, 3508, 4508, 5508) Technical data and information shall be furnished in accordance with the requirements set forth in the CDRL, DD Form 1423, and Section J, Exhibits A001 – A008. B001 – B006, C001 – C005 provided as an attachment to this RFP. This CLIN may be separately priced.

C.5.9 Task Order 0001 – Transition-In (CLIN 0109) The contractor shall provide the supplies/services in accordance with PWS-2017-036 and the CDRLs.

The contractor shall provide for services described in sections 3.17 and 3.17.1 of the PWS.

C.5.10 Task Order 0002, 0003, 0004, 0006, 0007, 0008 - Capability P3I (CLINs 0201, 1301, 2401, 3601, 4701, 5801) The contractor shall provide the supplies/services in accordance with PWS-2017-037 and the CDRLs.

In reference to CLIN 0201, the contractor shall provide for services described in sections 3.10, 3.10.2 and

3.10.2.1 and shall use the OneSAF v9.0 RIB Items document and associated Use Cases as the bases for pricing.

In reference to CLIN 1301, 2401, 3601, 4701, 5801, the contractor shall provide for services described in sections 3.10 and 3.10.2 and shall use similar requirements described in the OneSAF v9.0 RIB Items document and associated Use Cases as the basis for pricing the out year Task Orders.

C.5.11 Task Order 0002, 0003, 0004, 0006, 0007, 0008 - Tailored Product Release (CLINs 0202, 1302, 2402, 3602, 4702, 5802) The contractor shall provide the supplies/services in accordance with PWS-2017-037 and the CDRLs.

The Contractor shall provide for services described in section 3.9.1 of the PWS.

C.5.12 Task Order 0002, 0003, 0004, 0006, 0007, 0008 - Capability Concurrency (CLINs 0203, 1303, 2403, 3603, 4703, 5803) The contractor shall provide the supplies/services in accordance with PWS-2017-037 and the CDRLs.

The Contractor shall provide for services described in section 3.10 and 3.10.1 of the PWS.

C.5.13 Task Order 0002, 0003, 0004, 0006, 0007, 0008 - Integration, Test and Release (CLINs 0204, 1304, 2404, 3604, 4704, 5804) The contractor shall provide the supplies/services in accordance with PWS-2017-037 and the CDRLs.

The Contractor shall provide for services described in section 3.9 and 3.9.1 of the PWS and deliver one annual and tailored product release.

C.5.14 Task Order 0005 - Transition Out (CLIN 5509) The contractor shall provide the supplies/services in accordance with PWS-2017-037 and the CDRLs.

The contractor shall provide for services described in sections 3.17 and 3.17.2 of the PWS.

*** END OF NARRATIVE ***

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

LIST OF ATTACHMENTS

J.1. Exhibit/Attachment Table of Contents

DOCUMENT

TYPE

DESCRIPTION

LOCATION

PAGES

DATE

Exhibit A CDRLs Section C 19 Oct 2017

Exhibit B

Document Summary List (DSL)

Section C

Oct 2017

Attachment 1

PWS for Basic ID/IQ

Nov 2017

Attachment 2

PWS for TO 01

Dec 2017

Attachment 3 PWS for TO 02 Section C 18 Nov 2017

Attachment 4 QA Surveillance Plan Section L 10 Nov 2017

Attachment 5 DD 254 Section C 9 Oct 2017

Attachment 6 v.9 Memo Section C 2 Feb 2017

Attachment 7 v.9 Use Cases Section C 11 Sep 2017

Attachment 8 GFE List Section C N/A May 2017

Attachment 9 Key Personnel Section L 3 Oct 2017

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

NOTICES TO BIDDERS

PROPOSAL SUBMISSION

L.1 INTRODUCTION.

Proposals for the Basic ID/IQ, Task Order 0001, and Task Order 0002 shall comply with the requirements of the RFP and instructions contained within this section. Proposal submissions for the Basic ID/IQ, TO 0001, and TO 0002 will be evaluated for consistencies to ensure the Offeror’s understanding of the entire OneSAF requirement.

L.1.1 Electronic submission: Volumes I through V of the Offeror’s proposal are due electronically via compact disc/digital video disc (CD/DVD) no later than (NLT) 1:00 PM Eastern Standard Time (EST) on date 8 January 2018 to the point of contacts (POC) listed in paragraphs L.1.4 below. See Table L-1 for additional details pertaining to proposal submission. The Offeror’s proposal shall be submitted with one (1) original digital copy and two (2) digital copies which shall consist of five (5) Volumes.

L.1.2 Offerors are hereby on notice that a failure to submit all the required documentation in exactly the manner (timeliness and format) specified in the solicitation may constitute a basis for the Government to reject a proposal as non-compliant and therefore unacceptable (ineligible to receive award), at the sole discretion of the contracting officer.

L.1.3 Award Date: The anticipated award date for this requirement is the first quarter of the Government’s fiscal year 2019. This information is provided for use as a basis for schedules and burden (labor, overheads, G&A, etc.) mid-point calculations. The Contractor is not entitled to an equitable adjustment in contract price in the event the Government awards the task order before or after the date above.

L.1.4 Point of Contact (POC) The primary POC for this effort is Contract Specialist Mr. David Hagler.

U.S. Army Contracting Command - Orlando ATTN: David Hagler, Contract Specialist

W900KK-18-R-0010

12211 Science Drive Orlando, FL 32826 Email – david.a.hagler.civ@mail.mil

The alternative point of contact (APOC) for this effort is Contracting Officer Ms.

Dunamis T. Triska, ATTN: Ms. Dunamis T. Triska, Procuring Contracting Officer

W900KK-18-R-0010

12211 Science Drive

Email – dunamis.t.triska.civ@mail.mil

L.1.5. All proposals must clearly and convincingly demonstrate the Offeror has a thorough understanding of the requirements and associated risks, and is able, willing, and competent to devote and maintain the resources necessary to meet the requirements and has valid and practical solutions for all requirements. Statements that the prospective Offeror understands, can or will comply with the specifications, and statements paraphrasing the requirements or parts thereof are considered inadequate and unsatisfactory. Mere reiteration of the requirement or standard reference material is discouraged and may be considered inadequate and unsatisfactory.

The Offeror must include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. In presenting material in proposals, Offerors are advised that quality of information is more important than quantity. Offerors are encouraged to use quantitative terms wherever possible and avoid the use of qualitative and subjective terms to the maximum extent practicable. Offerors are cautioned that while the Government will not evaluate every PWS requirement for the purposes of the source selection evaluation, the awardee/Contractor will be required to comply with all PWS requirements during task order performance. The proposal shall reference the related paragraphs of the PWS (e.g. 3.1.2) and provide the detail necessary to substantiate the proposed approach and methodology for performance. The Government will determine that an Offeror's proposal is non-compliant, and therefore ineligible for award, if the proposal indicates that: it cannot or will not meet any of the PWS requirements; provides an approach that clearly does not meet any of the PWS requirements; or, includes data which prompts the Government to question the Offeror's compliance with any of the PWS requirements. The Source Selection Authority may reject all proposals received in response to a solicitation, if doing so is in the best interest of the Government.

L.1.6. Any data previously submitted in response to another solicitation, whether submitted to the ACC-Orlando Contracting Center or another agency should be assumed to be unavailable during this proposal evaluation and source selection process. Proposal data shall not be incorporated into the proposal by referring to another proposal or other source. Proposals submitted will not be returned. Alternate proposals will not be evaluated or accepted.

L.1.7. The Offerors shall ensure that each proposal Volume submitted contains only the information relevant to that specific Volume. The Offerors are cautioned that each Volume of the proposal is evaluated standalone against the criteria set forth in Section M and the evaluators for one Volume may be different than the evaluators of another Volume. It is incumbent upon the Offerors to ensure they properly submit their proposals. If the data is not contained in the appropriate Volume of the proposal it will not be evaluated.

For example, if Past Performance narratives are submitted under the Price Volume rather than the Volume specified, the proposal will be evaluated as if no Past Performance narratives were submitted at all. No cost information shall be included in the Technical or Program Management Volumes of the offerors proposal.

L.1.8. The proposal shall be valid for not less than 300 calendar days from the proposal due date.

L.1.9. In accordance with FAR 52.215-1(f)(4) the Government intends to make award without discussions. However, the Government reserves the right to request additional information (for purposes of clarification only) after receipt of Offeror’s response to the solicitation. However, the Government reserves the right to enter into discussions if necessary, at the sole discretion of the Contracting Officer. The Government will evaluate all proposals in accordance with FAR Subpart 15.305(a), and the Department of Defense (DoD) Source Selection Procedures, dated 31 March 2016 and Army Source Selection Supplement (AS3), dated 21 December 2012. If discussions are determined to be necessary, a competitive range will be established and be comprised of all of the most highly rated proposals, based upon the ratings of each proposal against all evaluation factors and sub-factors of this solicitation. The decision to establish a competitive range will be made at the sole discretion of the Contracting Officer.

L.1.10. Proposals shall not contain CLASSIFIED information.

L.1.11. Security Clearance Requirements: Contractor employees working under the resultant contract must have a Secret Security Clearance issued by the U.S. Government.

L.1.12. Questions regarding this solicitation shall be submitted in writing to the Contract Specialist and Contracting Officer, via email to the POCs identified in Section L.1.4., within 15 calendar days after the RFP is published with the solicitation number in the subject line. Offerors shall submit questions using RFP Section L, Attachment L1, Solicitation Question/Comment form. No phone inquiries regarding the RFP will be received or acknowledged. Offerors will receive an acknowledgement of their question via response to the email submission. If the Government deems the question appropriate, the answer will be published through the issuance of a solicitation amendment prior to the deadline for final proposal Submissions. If an Offeror perceives the questions may reveal proprietary or protected information they must clearly mark the subject sentence or paragraphs and notify the Government that they consider the information proprietary (if the Government does not agree the information is proprietary the Government may choose not to answer the question).

Questions received after the above referenced deadline may not be answered prior to proposal submission or at all. The Government does not anticipate that the closing date for receipt of offers will be extended however, the contracting officer reserves the right to do so. The Government will post the non-proprietary answers, without Offeror identification, to the FedBizOpps website located at https://www.fbo.gov.

L.1.13. Solicitation Exceptions/Deviations - The proposal should identify any unique or innovative approaches which ensure successful performance. The Source Selection Authority may reject all proposals received in response to a solicitation, if doing so is in the best interest of the Government. Offerors are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal. Proprietary information shall be clearly marked

L.1.14. If the Procuring Contracting Officer (PCO) determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the PCO may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals.

L.1.15. Technical Data Package

a. Potential Offerors are reminded that the OneSAF Technical Data

Package (TDP) is controlled by DISTRIBUTION STATEMENT “C”, as such, distribution is authorized to the United States Government Agencies and their contractors (Administrative or Operational Use).

Requests for access to the OneSAF TDP must be referred through David Hagler, david.a.hagler.civ@mail.mil and Bruce Robbins, bruce.e.robbins.civ@mail.mil for appropriate vetting through the PEO STRI Security Office.

b. All intended "teammates" must provide the following to receive access to the OneSAF TDP for this requirement within:

i. Full Name of Company/Organization

ii. Company's/Organization's address

iii. Company's/Organization's Commercial and Government Entity

(CAGE) code

iv. Full Name of Company's/Organization's Facility Security

Officer (FSO).

v. Prime shall provide single POC (name, email) who will serve as the recipient of the TDP.

c. Once “teammates” have been vetted through PEO STRI Security Office, an AMRDEC file transfer will be initiated with the contents of the TDP. All portions of the TDP and its contents shall be deleted from any and all systems upon submittal of Offerors proposal but NLT 8 January 2018.

d. Section L, Attachment L2 of the RFP provides the OneSAF distribution agreement for offerors to obtain the OneSAF v8.7 software. . A single copy of the software media will be provided to the Offeror. Upon submission of their proposal, or NLT 8 January 2018, the software media set shall be returned to the contract specialist. Any OneSAF software that has been copied as part of this proposal shall be deleted/removed from any and all systems upon submittal of Offerors proposal but NLT 8 January 2018.

e. Potential Offerors are also reminded that All Foreign Owned, Controlled, or Influenced (FOCI) companies must have their FOCI status mitigated in writing by the Defense Security Services (DSS) and listed in the DSS Industrial Security Facility Database (ISFD) prior to being allowed any materials or information relating to this contract. A copy of this written mitigation must be provided to David Hagler, david.a.hagler.civ@mail.mil and Bruce Robbins, bruce.e.robbins.civ@mail.mil for appropriate vetting through the PEO STRI Security Office.

L.1.16. As a result of this RFP, the Government intends to award the ID/IQ contract, and Task Order 0001 simultaneously; while awarding Task Order 0002 the following day to the Offeror whose offer conforms to the RFP and is deemed the best value to the Government. Information for Task Order 0001 and Task 0002 is included in this RFP. The period of performance for Task Order 0001 is 36 months from date of contract award. The period of performance for Task Order 0002 is 16 months from contract award. The projected award date is 22 September 2018. The cost/price information for Task Order 0001 and Task Order 0002 must be included in the appropriate TAB within the designated CLIN structure for Basic ID/IQ-TO1-TO2 Cost Price Workbook (Section L Attachment L3) located in Section B, in the Cost-Price Workbook within the TAB for Task Order 0001 and the TAB for Task Order 0002 provided as Attachment L3 located in Section L, and IAW the Performance Work Statements for Task Order 0001 and Task Order 0002.

L.1.17. Notional Task Order Execution Plan for the OneSAF Production and

Support Indefinite Delivery/Indefinite Quantity (ID/IQ) Notional Task Orders execution is depicted in Figure 1. Planned Task Order support of all of the OneSAF program activities across the life of the ID/IQ.

Figure 1. Notional execution of Task Orders across life of ID/IQ

L.1.18. Indirect Rates Table

The Offeror shall populate the table below with all indirect rates, to include the fixed fee rate, for all contract years. The below rates are the Not-to-Exceed rates to be applied to all CLINs and Task Orders. The Offeror shall provide any additional rates as appropriate.

Indirect Yr 1 Yr 2 Yr 3 Yr 4 Yr 5 Yr 6

OH

G&A

Handling Fee

Fixed Fee

*The offeror is to include any other indirect rates not mentioned in the table.

L.1.19. Property Management Plan

The offeror shall submit a Property Management Plan meeting the requirements of FAR Clause 52.245-1 (specifically, 52.245-1(f)). The Property Management Plan is not a requirement for evaluation in source selection, but rather a requirement for award to a business who has been determined “responsible” by the Contracting Officer; the Property Management Plan will be incorporated into any resultant contract.

L.2 PROPOSAL DELIVERY.

L.2.1 Proposals for solicitation W900KK-18-R-0010 may be hand delivered, sent by standard mail delivery through the United States Postal Services (USPS) or by a certified express vendor (e.g. FedEx) and shall be received no later than 1:00 pm Eastern Standard Time (local time) on 8 January 2018. The Offeror shall use the “Tracking” option for the proposal package(s). The Offeror shall provide a copy of the receipt for USPS or express vendor delivery options via email message to the POCs identified below within 24 hours of mailing the proposal. Submission of telegraphic, e-mail or facsimile offers is not authorized for this solicitation. The outside shipping container shall be marked with the solicitation number. Proposals shall be mailed/delivered as follows:

ATTN: David Hagler, Contract Specialist

W900KK-18-R-0010

12211 Science Drive

Email – david.a.hagler.civ@mail.mil

The APOC for this effort is Ms. Dunamis T. Triska.

ATTN: Ms. Dunamis T. Triska, Procuring Contracting Officer mailto:david.a.hagler.civ@mail.mil

12211 Science Drive

Email – dunamis.t.triska.civ@mail.mil

L.2.2 For a hand-carried proposal, the Offeror shall complete Section L, Attachment L8 - Proposal Receipt Form (Company name, Date Delivered, Company Representative’s Name, Company Representative’s Title and Number of CD/DVD Packages Received). The Contracting Officer/Specialist will annotate the date and time of proposal receipt. The Offeror’s Representative will confirm the data and sign the Proposal Receipt. The Contracting Officer/Specialist will provide a copy of the Proposal Receipt Form to the Offeror. The Contracting Officer/Specialist’s signature only denotes the receipt of the proposal package. The Government is not responsible for the proposal delivery content or condition upon delivery.

L.2.3 Solicitation Ombudsman

The Army Contracting Command-Orlando (ACC-Orlando) has established the office of Solicitation or Task Order Ombudsman, to assist industry in removing unnecessary and burdensome requirements from solicitations and Task Orders.

If you feel that this contract or any Task Order issued under this contract contains improper elements or can be further streamlined to promote more efficient use of taxpayer dollars, you should first identify these issues to the Procuring Contracting Officer (PCO). If the PCO is unable to resolve your concerns satisfactorily, or cannot do so in a timely manner, you are encouraged to call the ACC-Orlando Ombudsman at (407) 384-5432. The PCO/Ombudsman should be advised of any deficiency at least five (5) days prior to solicitation or Task Order closing date.

You may also write to the following:

U.S. Army Contracting Command-Orlando Solicitation/Task Order Ombudsman ATTN: ACC-ORL (Ms. Lesley Sullivan) 12211 Science Drive

L.2.4 Funding Profile

The table below shows the projected funding for the base program from FY18- FY23. This is being included in Section A of the RFP to give offerors a basic understanding of the Program’s Funding Profile during the PoP of this contract.

This funding profile, however, does not include the projections for ECPs, and other funding that is traditionally provided by customers for development and support activities.

mailto:dunamis.t.triska.civ@mail.mil

OneSAF Funding projections for the Production and Support ID/IQ ($K)

FY18

FY19

Option

FY20

Option

FY21

Option

FY22

Option

FY23

Option Total

Base Program 9,800 9,800 10,200 10,600 11,000 11,600 63,000

L.3 PROPOSAL FILES.

L.3.1 The Offeror’s proposal shall be submitted with one (1) original digital copy and two (2) copies and shall consist of five (5) Volumes:

Volume I – General Information Volume II – Technical Volume III – Management Volume IV – Past Performance Volume V – Cost/Price

L.3.2 The proposal shall be accompanied by a cover letter (letter of transmittal) prepared on the company’s letterhead stationery. The cover letter shall identify all enclosures being transmitted and shall be used only to transmit the proposal and shall not include other information. The first or title page shall be in accordance with FAR 52.215-1, paragraph (c)(2). The first or title page shall also include the Offerors’ CAGE Code and DUNS Number. The Offeror shall restrict the use of company identifying information (e.g. logos, company name), specifically in the proposal information provided in Volumes II Technical Approach and III Management Approach.

L.3.3 Page Limitations. The cover letter, title page, table of contents, table of figures, list of tables and glossary of abbreviations & acronyms do not count against page count limitations. Proposal contents that exceed the stated page limitations will not be considered in the evaluation.

L.3.4 Format. Volumes I, II, III, and IV text shall be single-spaced, using Arial or

Times New Roman Font Size 12 on 8 1/2 x 11 inch paper, with a minimum one-inch margin all around, and shall be oriented in portrait and single column format.

Pages shall be numbered consecutively. For Volume V, all MS Excel spreadsheets shall be in MS Excel 2013 format that is editable and executable by the Government evaluators, clearly showing the calculations and formulas used in each cell. There shall be no hidden formulas or protected cells.

Spreadsheets shall show the formulas used to calculate the rates/factors for each entry and shall not be included as an un-executable, un-editable or flat file such as an embedded picture (Enhanced Metafile). Mathematical explanations shall be provided for any embedded macro/extended formula utilized, clearly describing the functioning of the macro or extended formula. Any narrative regarding the Cost/Price Volume may be submitted in MS Word 2013 format.

L.3.5 Illustrations, such as graphics, figures, graphs, embedded screen shots

(or graphics) shall have a minimum 10-point using Arial or Times New Roman font. However, all tables shall be a minimum 12–point using Arial or Times New Roman font. Pages containing illustrations may be oriented in landscape format and shall use a font size of no less than 12-point font.

L.3.6 Each Volume in the proposal shall include a copy of the cover letter (letter of transmittal), title page and table of contents. The table of contents shall list sections, subsections and page numbers. Each Volume shall contain a glossary of all abbreviations and acronyms used. Each acronym used shall be spelled out in the text the first time it appears in each proposal Volume.

L.3.7 All of the proposal files shall be compressed (zipped) into one file entitled

“Volume <number and name> OneSAF_Production_And_Support.zip” proposal zip using WinZip version 6.2 or later, or as separate uploads in their native format, i.e. doc, xls, ppt, etc., and provided on CDs or DVDs. No other electronic media will be permitted. All price breakdown information to aide in the cost/price evaluation shall be submitted in Microsoft Office Excel Read/Write format and viewable in Microsoft Excel 2013. For the Technical and Program Management Volumes each CD/DVD case cover ONLY shall be externally labeled with the volume number, date, RFP number, and the Offeror’s name. Each disc inside the CD/DVD cover of the Technical and Program Management Volumes shall be externally labeled with the volume number, date, and RFP number. For all other volumes other than the Technical and Program Management Volumes, Each disc and CD/DVD case cover shall be externally labeled with the volume number, date, RFP number, and the offeror’s name.

L.3.8 Text and graphics portions of the electronic copies shall be in a format readable by Microsoft (MS) Office 2013 format. Data submitted in spreadsheet format shall be readable by MS Office 2013.

NOTE: 11”X17” pages are acceptable for tables/graphic representations ONLY. Each printed side of an 11”X17” page counts as two pages for the relevant page count.

L.4 PROPOSAL VOLUMES.

L.4.1. The proposal must consist of Volumes I through V as delineated in Table

L-1, below.

L.4.2. Failure of an Offeror to provide all required proposal information may result in a determination that an Offeror is non-compliant and therefore ineligible to be considered for award, at the sole discretion of the PCO.

VOLUME

TITLE

VOLUME

SECTIONS

SUB-

FACTORS

SECTION L

REFERENC

E

PAGE LIMIT

I – General Information

Section 1 NA L.5.1 Unlimited

Section 2 NA L.5.2 10

Section 3 NA L.5.3 Unlimited

Section 4 NA L.5.4 Unlimited

Section 5 NA L.5.5 Unlimited

Section 6 NA L.5.6 Unlimited

II -

Technical

Sub-factor 1.1

L.6.1 Sub-factors 1.1, 1.2 and 1.3 are limited to 40 pages collectively

Sub-factor 1.2

L.6.2

Sub-factor 1.3

L.6.3

III -

Manageme nt

Sub-factor 2.1

L.7.1 Sub-factors 2.1, 2.2, and 2.3 are limited to 40 pages collectively

Key Personnel Resumes

Resumes for key personnel are unlimited / Appendix A

– Modified QASP doesn’t count towards the page count

Sub-factor 2.2

L.7.2

Sub-factor 2.3

L.7.3

Sub-factor 2.4

L.7.4 Sub-factor 2.4 is unlimited

IV - Past Performanc e

Section 1 NA L.8.2 25 total

Section 2 NA L.8.3

Section 3 NA L.8.4 Unlimited

V – Cost / Price

NA L.9 Unlimited

Table L- 1 Proposal Volume Organization

L.5 VOLUME I – GENERAL INFORMATION

L.5.1 Section 1 – Table of Contents. Offerors’ shall provide detailed Table of

Contents 1 (one) for the overall proposal in the General information Volume and in accordance with the requirements in Section L.5.2.

L.5.2 Section 2 – Offeror shall provide an overview and synopsis of the proposal, to be used as an aid in understanding the organization, content and interrelationship of the proposal material. The Offeror shall provide a brief history of the creation and development of the company and a description of the legal structure and organization of the company. Joint Ventures shall be clearly explained, to include the organization of each member in the venture, the construct of the joint venture, the relationship between the members of the joint venture and the Small Business Administration’s (SBA) approval of the joint venture. Information is to be presented at a summary level. Pertinent aspects of the proposal approach including Teaming approaches, if any. Subcontracting and any proposed unique approaches should also be highlighted. Cost/Price information shall not be included in this document. Reference to the proposal areas containing substantiating information should be given when possible.

(LIMIT 10 PAGES). The information provided in the Executive Summary will not be considered in the evaluation of the factors found in Volumes II through V.

L.5.3 Section 3 – Solicitation Documents. Offeror shall complete blank lines and provide signatures for the solicitation sections indicated below without modification to the files. An authorized official of the company shall sign the Standard Form (SF) 33 and all certifications requiring original signatures. An Adobe Acrobat file, “.pdf”, shall be created to capture the signatures for submission.

(a) Section A – Standard Form 33. Complete blocks 14 through 18

(b) Section B – Contract Line Item Number projected costs

(c) Section G – Contractor’s Authorized Contract Coordinator and Technical

Liaison

(d) Section H – Organizational Conflict of Interest Mitigation Plan, if applicable.

(e) Section K - Representations, Certifications and Assertions.

(f) Section I – Data Rights Clauses: Please ensure that all fill-ins for Clauses:

252.227-7013 RIGHTS IN TECHNICAL DATA--NONCOMMERCIAL ITEMS (FEB 2014);

252.227-7014 RIGHTS IN NONCOMMERCIAL COMPUTER SOFTWARE AND

NONCOMMERCIAL COMPUTER SOFTWARE DOCUMENTATION (FEB 2014);

252.227-7017 IDENTIFICATION AND ASSERTION OF USE, RELEASE, OR DISCLOSURE

RESTRICTIONS. (JAN 2011),

are appropriately completed.

L.5.4 Section 4 – Acknowledgement of Amendments to the Solicitation.

Offerors’ shall provide a statement acknowledging reviewing and understanding of all amendments to the solicitation.

L.5.5 Section 5 - Acknowledgement of NO Exceptions/Deviations to

Solicitation. Offerors’ shall provide a statement acknowledging that the Government will not accept any exceptions or deviations to the solicitation for this effort.

L.5.6 Section 6 – Acronyms Defined. The Offerors’ shall provide a list defining acronyms utilized within the proposal.

L.6 . VOLUME II – Factor 1: TECHNICAL APPROACH

The Offeror shall submit one proposal for Task Order (TO) 0001 and TO 0002. The Offeror shall clearly identify in the proposal when addressing the TO 0001 requirements and the TO 0002 requirements. The Offeror shall comply with the requirements of the RFP and instructions contained within this section. Proposal submissions for TO 0001 and TO 0002 will be evaluated for consistency to ensure the Offeror’s understanding of the entire OneSAF requirement. The Offeror shall include all assumptions relative to their proposal submission.

L.6.1 Sub-factor 1.1 - Software Development Approach (OneSAF v9.0/I v9.0)

For T0 0002, the Offeror shall provide a complete description of their technical solution and approach to conducting requirements analysis, conceptual modeling, engineering design, development, production, test, and integration of the v9.0 capabilities. The Offeror’s approach shall include their methodology for development of the version 9.0 RIB items and proposed concurrency updates to the software baseline. The Offeror shall describe how their systems and software engineering practices, application of the OneSAF processes, innovative methodologies, and architectural enhancements will allow for the capability developed to meet the v9.0 requirements. The Contractor shall describe how its approach will leverage (or incorporate) new and evolving technologies and leverage and reuse existing products where practical with the goal of reducing overall life-cycle costs.

Reference: TO 0002 PWS paragraphs: 3.2, 3.3, and 3.10.

L.6.2 Sub-factor 1.2 – Product Line Management and Support

For T0 0001, the Offeror shall describe their integration and testing methodologies, processes, and tools for product line maintenance and support.

The Offeror's approach shall describe their use of innovation and testing efficiencies which will reduce cost and improve product quality. The Offeror shall describe how they will manage and provide multiple baselines in a variety of software configurations (e.g., Virtual Configuration, Battalion Product, etc.).

Reference: IAW TO 0001 PWS paragraphs 3.3, 3.4, 3.5, 3.8 and 3.15

The Offeror shall describe their approach to the maintenance and integration of co-developer handovers, lab management, configuration control, testing of system components such as, but not limited to, Mission Command Adapter (MCA), Management and Control Tool (MCT), Web Control Tool (WCT), Environment Runtime Component (ERC), interop, and behaviors, and general system performance testing.

Reference: TO 0001 PWS paragraphs: 3.3, 3.4, 3.5, 3.7, and 3.15.

L.6.3 Sub-factor 1.3 – Cybersecurity

For T0 0001, the Offeror shall describe their proposed application cybersecurity engineering processes to ensure that all releases of the OneSAF application meet the DoD and Army Risk Management Framework (RMF) requirements beginning with the v9.0 release. The Offeror’s approach shall describe how they intend on implementing the RMF process in order to improve the operational security posture and achieve efficiencies through cybersecurity process improvements. The Offeror’s approach shall illustrate their security engineering practices in order to ensure an appropriate security posture for the life-cycle maintenance of the application.

Reference: TO 0001 PWS section 3.18 and 3.18.1.

L.7 VOLUME III – Factor 2: MANAGEMENT APPROACH

L.7.1 Sub-factor 2.1 – Team Management and Expertise

The Offeror shall provide their organizational team structure and management approach (to include labor skill mix) to manage the OneSAF program throughout the entire program lifecycle for the ID/IQ PWS. The Offeror shall provide a list of proposed key personnel, which meets the requirements outlined in Section J Attachment 9, while emphasizing their experience, abilities, skill sets, and benefits to the program. Key personnel resumes shall be provided.

The Offeror shall describe their management approach and processes to meet responsibilities as a Prime contractor, to include roles and relationships with partners and sub-contractors, and the approach to obtaining and retaining necessary resources to meet OneSAF requirements. The Offeror shall describe their overall management approach and processes for performing within schedule and performance parameters to include effective coordination with teaming partners.

Reference: Paragraph 3.1 in TO 0001 PWS.

Reference: Key Personnel Requirements (Section J Attachment 9)

L.7.2 Sub-factor 2.2 – Software and System Engineering Management Approach

For T0 0001, the Offeror shall demonstrate their experience in tracking metrics and…