FA8681-18-R-0006_0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

See Block #2

PAGE OF PAGES

2. AMENDMENT/MODIFICATION NO.

3. EFFECTIVE DATE

19 SEP 2018

4. REQUISITION/PURCHASE REQ.NO.

5. PROJECT NO. (If applicable)

6. ISSUED BY AFLCMC/EBDK CODE FA8681 7. ADMINISTERED BY (If other than Item 6) CODE

USAF/AFMC/AFLCMC/EBK

DEPARTMENT OF THE AIR FORCE

102 W D AVE STE 5 BLDG 11

EGLIN AFB FL 32542

BRENT P. BARNHILL 850-883-3411

brent.barnhill.1@us.af.mil

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X) 9A. AMENDMENT OF SOLICITATION NO.

FA8681-18-R-0006

X

9B. DATED (SEE ITEM 11)

27 AUG 2018

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

CODE FACILITY CODE

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 Offers is extended, X is not extended.

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

(a) By completing Items 8 and 15, and returning 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 MODIFICATION OF CONTRACTS/ORDERS,

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

(X )

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

10A.

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

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

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor X 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.)

See Schedule of Changes

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

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

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

DIANA R. GRAZIANO

15B. CONTRACTOR/OFFEROR

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA

16C. DATE SIGNED

(Signature of person authorized to sign)

BY________________________________________

(Signature of Contracting Officer)

NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (REV.10-83)

PREVIOUS EDITION UNUSABLE Prescribed by GSA ConWrite Version 7.0.10.74 FAR (48 CFR) 53.243 Created 19 Sep 2018 3:57 PM

LIST OF ATTACHMENTS

FA8681-18-R-0006 0001 PAGE 2 OF 4

Below is a summary of the changes captured by 0001:

1. Section J - Attachment 12 Section L Page 4, Para L-1.2.3.3

From:

L-1.2.3.3 The page limitation for Volume II, Written Technical Proposal is 100 pages. The page limitation for Volume III, Small Business Participation Submission, is 25 pages. The page limitations include any cover page, charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, but excludes any table of contents or list of acronyms (if utilized). Offerors are cautioned that any pages that exceed the page limitations shall not be read and shall not be considered in the evaluation.

To:

L-1.2.3.3 The page limitation for Volume II, Written Technical Proposal is 100 pages. The page limitation for Volume III, Small Business Participation Submission, is 25 pages. The page limitations include any cover page, charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, but excludes any table of contents, list of acronyms (if utilized), and Microsoft Project Integrated Master Schedule (IMS).

Offerors are cautioned that any pages that exceed the page limitations shall not be read and shall not be considered in the evaluation.

2. Section J - Attachment 12 Section L Page 14, Para L-3.3.2(c)

From:

c. The IMS shall be detailed and valid in accordance with CDRL A002 for the entire DO and aligned with the DO SOW Appendix A.

To:

c. Provide the initial IMS with the proposal in Microsoft Project format. The IMS shall be detailed and valid in accordance with CDRL A002 for the entire DO and aligned with the DO SOW Appendix A.

3. Section J - Attachment 15 DO Package

DO SOW paragraph 1.1.1 and paragraph 2.6.2, and Table 5 Deliverables have been updated to reflect a CAF MPE version of 4.X.

4. Section J - Attachment 15 DO Package DO SOW Page 3, Para 1.2

From:

1.2 The WPS v2.0 ER#3 shall be the software baseline for development and enhancements.

To:

1.2 For evaluation purposes, the WPS v2.0 ER#3 shall be the software baseline for development and enhancements. After award, further development and enhancements will be accomplished utilizing the released WPS v2.1 (estimated May 2019) which will be ultimately integrated into the latest version of the

CAF MPE.

LIST OF ATTACHMENTS

FA8681-18-R-0006 0001 PAGE 3 OF 4

5. Section J - Attachment 15 DO Package DO SOW Page 12, Table 5 WPS v2.2 Prototype on JMPS 4.X MPE Due Date

From:

Tentatively Scheduled 30 Sept 2019

To:

6 Months ACA (date will be identified at award)

SCHEDULE OF CHANGES

FA8681-18-R-0006 0001

DOCUMENT PGS DATE TITLE

ATTACHMENT 12 27 18 SEP 2018 SECTION L - INSTRUCTIONS, CONDITIONS, AND

NOTICES TO RESPONDENTS REVISION 1

ATTACHMENT 15 29 18 SEP 2018 DELIVERY ORDER RFP PACKAGE REVISION 1

FA8681-18-R-0006 RFP

Section J – Atch 12 Section L Rev 1

Attachment 12

SECTION L

Instructions, Conditions, and Notices to Offerors or Respondents 18 September 2018 Rev 1

L-1.0 Instructions to Offerors

L-1.1. Proposal Preparation

L-1.1.2 General: The following instructions cover the preparation and submittal of the offeror’s proposal for this Weapons Planning Software (WPS) solicitation. Offerors are cautioned that noncompliance with the terms and conditions of this Request for Proposal (RFP) may cause the offeror’s proposal to be determined ineligible for award. If a joint venture arrangement exists for this acquisition, the offeror shall provide a copy of the joint venture agreement signed and dated by all joint venture members as part of the proposal submission. Offerors shall submit only one proposal for the WPS acquisition. The Government will review only one proposal per offeror. Proposals must be produced on either a CD or DVD and received by no later than the date and time specified in Block 8 on the face page of the RFP at the following address:

Attention: Diana Graziano 210 West D Avenue Building 373, Suite 101 Eglin AFB, FL 32542

L-1.1.3 Communications: Exchanges of source selection information after submission of the initial proposal packages between the Government and offerors will be controlled by the Procuring Contracting Officer (PCO). Source selection information will be transmitted to the PCO at diana.graziano@us.af.mil and the Contract Specialist (Buyer) at brent.barnhill.1@us.af.mil via AMRDEC SAFE at https://safe.amrdec.army.mil/safe/guide.aspx. In the instance there is an issue with AMRDEC SAFE, alternate method will be direct email. Upon the need to execute communications via email, transmitting shall only occur if source selection information can be encrypted, and must include “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email. In order to facilitate sending and receiving of encrypted emails, offerors must use MS Outlook email configured to support encryption or a different email product that is configured to support encryption. If you intend to submit your source selection information via encrypted email, contact the buyer/PCO indicated on the face page of the solicitation prior to submittal in order to exchange encryption certificates. To ensure the process is working correctly, send a test encrypted message first (without including any source selection information). When submitting source selection information via email or AMRDEC SAFE, file compression utilities, to include but not limited to zip files, will not be accepted.

mailto:diana.graziano@us.af.mil mailto:brent.barnhill.1@us.af.mil https://safe.amrdec.army.mil/safe/guide.aspx

L-1.1.4 Discrepancies: If an offeror believes the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the PCO in writing with supporting rationale as well as the remedies the offeror is asking the PCO to consider.

L-1.1.5 Participation by Foreign Firms: Participation is limited to those firms registered in

JCP and SAM. In accordance with (IAW) the National Industrial Security Program Operating Manual (NISPOM), foreign firms or U.S. companies determined to be under Foreign Ownership, Control, or Influence (FOCI) will not be permitted to participate.

The offeror shall provide substantiation that the offeror is not under FOCI.

L-1.1.6 Electronic Reference Documents: Some referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) website at https://www.fbo.gov/ . Potential offerors are encouraged to subscribe for real time e-mail notifications by FBO when information has been posted to the website for this solicitation. Most of the referenced documents will be provided to the offeror upon official request as identified in L-1.1.7.

L-1.1.7 Access to Distribution D and Export Controlled Data: Upon written request, a copy of the requirements documents referenced within this RFP that are Distribution D and/or export controlled will be made available from Diana Graziano, diana.graziano@us.af.mil, or Brent Barnhill, brent.barnhill.1@us.af.mil. Offerors must officially request these documents in writing, via email, utilizing the Export Controlled Information Request Form in Section J, Attachment 18. To complete the documentation release the offeror must have a current CAGE number, active System for Award Management (SAM) registration and an active registration at the U.S./Canada Joint Certification Program (JCP) website http://www.dlis.dls.mil/jcp/. With the information request form, include a copy of the current DD Form 2345. The JCP Point of Contact (POC) listed within the JCP site and identified on the DD Form 2345 is the only individual authorized to email the request and is the only one authorized to receive the export controlled information from the Government on behalf of the U.S. contractor. The company JCP POC is responsible for disseminating appropriately within the company. Any recipient of the export controlled information shall be a U.S. citizen or a person admitted lawfully into the United States for permanent residence and is located in the United States. Upon verification of the offeror’s status and acknowledgement of responsibilities under U.S.

export control laws and regulations, the requested information package will be provided via CD-R or DVD-R (write once/read only).

NOTE: All offerors shall submit a request for the information package within 20 days of the solicitation date posted to FedBizOpps. Failure to comply with this requirement will eliminate an offeror from consideration for award.

L-1.1.8 Debriefings: The PCO will promptly notify offerors of any decision to exclude the offeror from the competitive range; whereupon, they may request and receive a https://www.fbo.gov/ mailto:diana.graziano@us.af.mil mailto:brent.barnhill.1@us.af.mil http://www.dlis.dls.mil/jcp/ debriefing IAW FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing. However, offerors excluded from the competitive range are entitled to no more than one debriefing. The PCO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR

15.506. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW the requirements of FAR 15.505 or FAR 15.506, as applicable.

L-1.1.9 Factors and Subfactors:

Factor I: Technical and Technical Risk

Subfactor 1: Technical Experience with Weapons Mission Planning Software and Joint Mission Planning System (JMPS) Integration Subfactor 2: Management, Software and Systems Engineering Processes Subfactor 3: Delivery Order: FY19 Development and Legacy Enhancements Subfactor 4: Small Business Participation

Factor II: Cost/Price

L-1.2. Volume Organization

L-1.2.1 General: Proposals shall be submitted as electronic copies to the Government in the four volumes as set forth below:

Table L-1 – Volume Organization Volume Page Limits

(Not to Exceed) Number of Copies

Description

I N/A 1 Completed RFP II 100 1 Written Technical Proposal – Factor I: Subfactors 1, 2, and 3 III 25 1 Small Business Participation– Factor I: Subfactor 4 (participation submission has page limitation) (Subcontracting Plan does not have a page limitation)

IV N/A 2 Cost/Price Proposal – Factor II

L-1.2.2 Electronic Submissions: The offeror shall submit electronic copies as identified above in compact disc (CD-R) or digital video disc (DVD-R) (write once/read only) that is “closed” so that no further writes can be made to the media. CD-R/W or DVD-R/W media types are not acceptable. Media must be virus scanned by the offeror prior to submitting to the Government. Indicate on each CD/DVD the volume number and title.

Use separate files to permit rapid location of all portions, including subfactors, exhibits, annexes and any attachments. Documents shall not be compressed and shall be compatible with Microsoft Office or adobe Portable Document Format (PDF). On the cost/price volume, the offeror shall provide the cost/price volume with the ability to view formulas.

NOTE: Do not submit any information on flash drive media. All content must be

“READ ONLY”

L-1.2.3 Proposal Format Specifications: In addition to the page limitations set forth above, electronic proposal documents within each volume shall comply with the following format:

L-1.2.3.1 Proposals shall be in the English language and all monies shall be proposed in United States dollars. Each CD/DVD shall be externally marked with the RFP number and the offeror’s name and address, and the volume number, i.e. I, II, III, etc. with the following statement:

SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104

L-1.2.3.2 Print shall be no smaller than a font size of 12 with the exception for supporting illustrations that shall be no smaller than a font size of 10. Paper size shall be 8 ½” X 11,” excluding any charts, drawings, diagrams, and/or supporting illustrations, spreadsheets. Charts, drawings, diagrams, and/or supporting illustrations, spreadsheets shall not be greater than 11” x 17”. Each volume within the proposal shall have a separate file and shall be identified by the Volume number, i.e. I, II, III, etc. Margins shall be no smaller than 1 inch and each page within a volume shall be numbered consecutively. Elaborate formats, bindings, or color presentations are not desired or required.

L-1.2.3.3 The page limitation for Volume II, Written Technical Proposal is 100 pages. The page limitation for Volume III, Small Business Participation Submission, is 25 pages.

The page limitations include any cover page, charts, graphs, drawings, diagrams, supporting illustrations, spreadsheets, but excludes any table of contents, list of acronyms (if utilized), and Microsoft Project Integrated Master Schedule (IMS). Offerors are cautioned that any pages that exceed the page limitations shall not be read and shall not be considered in the evaluation.

L-1.2.3.4 Page limitations may be placed on responses to Evaluation Notices (ENs), if issued. The specified page limits for EN responses will be identified in the letters forwarding the ENs to offerors or on the EN form itself. All other formatting, page specifications identified herein are also applicable to ENs.

L-1.2.3.5 Each page containing proprietary information should be so marked.

L-1.2.3.6 Each page should minimally contain the following legend at the bottom of each sheet:

SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104

L-1.2.3.7 Submission of the initial proposal packages via electronic mail will not be accepted. Initial proposal packages (CDs/DVDs) shall be mailed to the address identified in block 8 of the Solicitation document.

L-2.0. Volume I, Completed RFP

L-2.1 General: Volume I, Completed RFP shall consist of the completed and signed RFP (to include any amendments issued) with a cover letter delineating exceptions (see item L-2.2.3.12 below) taken to the RFP terms and conditions with accompanying rationale.

Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined ineligible for award. Offerors shall ensure that all clauses and provisions that require “fill in” information are appropriately completed.

L-2.2 Format and Specific Content: The offeror shall acknowledge understanding of each section. The initial page of this volume shall be a Table of Contents identifying the sections below. Additionally, a section/document within the offeror’s electronic proposal file for the volume shall contain the following:

L-2.2.1 Authorized Offeror Personnel: Provide the name title, and telephone number of the company/division POC regarding decisions made with respect to your proposal and who can obligate your company contractually and those individuals authorized to negotiate with the Government.

L-2.2.2 Government Offices: Provide the mailing address, telephone numbers and facility codes for the cognizant Contract Administration Office, DCAA and Government Paying Office. Provide the name, email and telephone number for the Administrative Contracting Officer (ACO).

L-2.2.3 Company/Division Address, Identifying Codes: Provide company/division street address, county and facility code, CAGE code, DUNS code, TIN, and size of business (large or small). List all locations where work would be performed for this effort, facility CAGE code, and indicate whether the location is a division, affiliate, or subcontractor and the percentage of work to be performed at each location.

L-2.2.3.1 Section A – Solicitation/Contract Form: The offeror shall complete blocks 14, all of 15, 16, and signature and date for blocks 17 and 18 of the SF 33. Signature by the Offeror on the SF 33 constitutes an offer, which the Government may accept. The signature constitutes agreement to block 12 fill-in of 180 days. The signature page can be scanned in or contain an electronic signature.

L-2.2.3.2 Section B – Supplies or Services and Prices: The offeror shall acknowledge basic contract CLIN structure.

L-2.2.3.3 Section C – Description/Specifications/Work Statement: See Section J for all specification information.

L-2.2.3.4 Section D – Packaging and Marking: The offeror shall acknowledge packaging and marking requirements associated with each Contract Data Requirements List (CDRLs).

L-2.2.3.5 Section E – Inspection and Acceptance: The offeror shall acknowledge this section and that Inspection and Acceptance details will be identified at the DO level.

L-2.2.3.6 Section F – Deliveries or Performance: The offeror shall acknowledge this section and that deliveries or performance details will be identified at the DO level.

L-2.2.3.7 Section G – Contract Administration Data: The offeror shall provide the fill-in information for DFARS 252.232-7006 Wide Area Work Flow.

L-2.2.3.8 Section H – Special Contract Requirements: None.

L-2.2.3.9 Section I – Contract Clauses: The offeror shall acknowledge clause requirements and compliance.

L-2.2.3.10 Section J – List of Attachments: The offeror shall complete required attachments and acknowledge list of attachments. Section J, Attachments 12-17 will be removed at time of award.

L-2.2.3.11 Section K – Representations, Certifications and other Statements of Offerors.

a. The Offeror is required to complete and provide the representation, certification, acknowledgements and statements identified throughout the RFP to include completing and submitting DFARS 252.227-7017 Identification and Assertion of Use, Release, or Disclosure Restrictions. Copies of all non-disclosure agreements and consent shall be provided within this Section/Folder.

b. Consent and Non-Disclosures: IAW the Department of Defense (DoD) Source Selection Procedures paragraph 1.4.6.2.1, use of non-government advisors are authorized. Offerors are advised that technical and cost/price data submitted to the Government in response to this solicitation may be released to non-government advisors for review and analysis. Additionally, IAW FAR 9.505-4(b), offerors shall obtain non-disclosure agreements with the companies and shall provide a copy of these agreements within this section/folder. The non-government advisor support will be provided by the prime and subcontractors on the Engineering, Professional, and Administrative Support Services (EPASS) contract:

Prime: Odyssey Systems Consulting Group, Ltd.

Address: 201 Edgewater Drive, Suite 270, Wakefield, MA 01880 Contract Number: FA8622-15-F-8120/FA8622-15-F-8121 POC: Daeri D. Coskren, Esq Title: Director of Legal & Compliance Email: daericoskren@odysseyconsult.com Tel: (781)399-5807 Subcontractors: DCS Corporation and MacAulay-Brown Inc.

c. Offerors shall provide a signed written consent (paragraph below), and, if required, provide written objections, as stated in the paragraph below.

i. I understand technical and cost/price data submitted to the

Government in response to this solicitation may be released to Non- Government advisors. I consent to the release of any (unless objection is provided in (ii) below) proprietary, confidential, or privileged commercial or financial data provided by the firm(s) named below in response to this solicitation, to non-government advisors for review and analysis. I acknowledge, and am providing copies of the non-disclosure agreements with this consent:

Firm:

Name (individual authorized to commit firm):

Title:

Date of Execution:

ii. Any objection to disclosure shall be provided in writing no later than 10 days after the RFP is posted to FedBizOpps. This objection shall include a detailed statement of the basis for the objection. The detailed statement shall identify the specific portions of the proposal the Offeror objects to disclosing to Non-Government Advisors.

L-2.2.3.12 Exceptions to Solicitation Requirements: Offerors are required to meet all solicitation requirements (such as terms and conditions, representations and certifications, and technical requirements) in addition to those identified as evaluation factors and/or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale for each exception. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, price, and specific mailto:daericoskren@odysseyconsult.com requirements of the solicitation. This information shall be provided in the format and content of Table L-2 below.

Table L-2 – Solicitation Exceptions (if none, so state) Solicitation Document

Page/Paragraph Requirement/Portion Rationale

SOW, SRD,

MPRD,JMPS Rules, Model Contract, CDRL, etc.

Applicable Page and Paragraph

Identify the requirement or portion to which exception is taken

Describe why the requirement cannot or will not be met

L-2.2.3.13 The Government anticipates providing the Government Furnished Property (GFP) identified in Section J, Attachment 3. Provide the Point of Contact (POC), address, and Department of Defense Activity Address Code (DODAAC) for shipping and receiving.

L-2.2.3.14 Reserved.

L-2.2.4 Cross Reference Matrix: The offeror shall fill out the cross reference matrix at

Section J, Attachment 14 indicating where in its proposal the information can be found as it relates to the RFP. The cross reference matrix will be utilized as a tool to show critical interrelationships and dependencies of the solicitation; Section L (Instructions to Offerors), Section M (Evaluation Basis for Award). The contractor shall fill-in the specific page and paragraph of the proposal as it relates to Section L and M. The cross reference matrix will help an offeror ensure it has responded to all the evaluation criteria and proposal submittal requirements identified in the solicitation. If the matrix conflicts with any other requirement, direction, or provision of this solicitation, the other reference shall take precedence over the matrix. Section M references in the matrix are for informational purposes only, and the Government will evaluate proposals solely in conformance with Section M of the solicitation.

L-2.2.5 Organizational Conflict of Interest:

Organizational Conflict of Interest (OCI) is a concern requiring specific attention.

Offerors shall identify any existing or potential conflicts as detailed in FAR Subpart 9.5 as soon as possible, but no later than 21 days prior to submission of the Offeror’s proposal. If the Government Contracting Officer (CO) deems the offeror to have an actual or apparent OCI, the offeror will be required to submit a plan to mitigate OCI concerns and the solicitation may be modified to add appropriate clauses and/or provisions. The offeror’s proposal may be deemed unawardable if the offeror is unable to mitigate an actual or apparent OCI, or fails to supply an adequate mitigation plan. A mitigation plan submitted by an offeror at the direction of the CO will not be evaluated as part of the proposal and will only be used to determine whether an award can be made to the offeror submitting a plan.

L-2.2.6 Security Requirements:

The offeror must possess, or acquire prior to award of a contract, a facility clearance equal to the highest classification stated on the Contract Security Classification Specification (DD Form 254) attached to the solicitation (Attachment 2). The offeror must acknowledge this requirement, confirm compliance, and identify the level of security approved for each location work will be performed for this effort in order to be eligible for award.

L-3.0 Volume II, Written Technical Proposal –Factor 1: Subfactors 1, 2 and 3

L-3.1 General: The written technical proposal shall be clear, concise, and include all the information required by this provision in sufficient detail for effective evaluation. The proposal should not simply rephrase or restate the Government’s requirements but shall provide convincing rationale to address how the offeror intends to meet these requirements. Offerors shall assume the Government has no prior knowledge of the offeror’s capabilities, work processes, facilities, and experience and that the Government will base its evaluation on the information presented in the offeror’s technical proposal.

It is expected for this effort that the contractor shall deliver data and the developed product, both source code and executable (compiled code) with unlimited rights.

Proposals with solutions containing less than unlimited rights to the Government may be deemed ineligible for award. The offeror is reminded the Government reserves the right to award based on the initial proposal as received, without discussions.

L-3.2 Format and Specific Content: The following information shall be provided in the written technical proposal demonstrating offeror’s applicable technical experience, management approach and processes along with associated technical risk IAW Section M, Evaluation Factors for Award. The written technical proposal shall address each of the following subfactors listed below to describe the offeror’s experience and proposed approach to performing the requirements set forth in the basic Weapon Planning Software Statement of Work Section J, Attachment 1, Systems Requirements Document (SRD), Mission Planning Requirements Documents (MPRD), Joint Mission Planning System (JMPS) Business Rules (JBR), JMPS Technical Rules (JTR) found within the Export Controlled CD (see Section J, Attachment 18 for instructions to obtain) and Delivery Order (DO) Statement of Work (SOW) found in Section J, Attachment 15. For each subfactor, the offeror shall identify risks (if any) associated with the offeror’s experience and proposed approach and actions the offeror will take to mitigate the identified risks. If no risks are identified in the offeror’s proposal, it indicates the offeror does not consider any risk associated with the offeror’s proposed approach. This does not preclude the Government from determining risks.

Factor I: Technical and Technical Risk

Subfactor 1: Technical Experience with Weapons Mission Planning Software and JMPS Integration Subfactor 2: Management, Software and Systems Engineering Processes Subfactor 3: Delivery Order: FY19 Development and Legacy Enhancements

L-3.2.1 Subfactor 1: Technical Experience with Weapons Mission Planning Software and JMPS Integration

L-3.2.1.1 The offeror shall provide specific examples of the offeror’s software engineering experience and software development experience (Agile, Agile-like) associated with weapon mission planning software components that the offeror has developed and/or maintained within the last 10 years. The offeror shall detail JMPS framework integration experience within the last 10 years. For each experience area (Critical and Additional as listed below) the offeror shall describe their experience including nature of involvement (e.g. prime contractor, subcontractor, developer, etc.), years of experience, list of work performed/software developed, number of developers working on the project, and unique skills or capabilities related, to the areas of interest (listed below). The experience provided shall be evidence of the offeror’s knowledge and understanding related to the items below. The offeror shall identify Additional Experience areas, from the list below, in which the offeror does not have experience and describe the offeror’s plan to mitigate risks associated with these areas. The offeror shall include/demonstrate experience, length in time, timeframe and examples of associated artifacts the offeror deems related to the following experience areas:

a. Critical Experience Areas:

• Network Enabled Weapon (NEW) experience

• Universal Armament Interface experience (UAI) to include Mission Data

Exchange Format (MiDEF) files and Configuration Datasets

• Launch Acceptability Regions (LARs) and Weapon Fly-out-models

• Crypto key management (GPS and NEW) to include M-Code

• Programmable Fuze support

• Out-of-JMPS Process development

• Aircraft mission software integration, to include weapon interfaces

• Precision Guided Weapon software experience

• Visual Studio .NET Development using C#

b. Additional Experience Areas:

• Mission Planning Systems supported

• Mission Planning Environments (MPE) supported

• Aircraft supported

• Integration with other software components

• Targeting Data Management

• United States Message Text Format (USMTF) message handling

• Integration with other software components (CCs, UPCs, etc.)

• Electronic Warfare data management and analysis

• Mission Planning Data Service Layer (MPDSL) experience

• Geozone management

• Aircraft Unique Planning Component (UPC) integration

• Data link mission planning

• Clobber Analysis

• Weapons Planning for Foreign Military Sales Mission Planning Support

(i.e. ITAR)

• Utilization of Agile Process Model (or similar)

• Major software projects developed in other areas (e.g. accounting software, munition software, scheduling software…)

• Automated testing

• Structured Query Language (SQL) Server Database integration

• Windows Presentation Foundation (WPF)

• Service Oriented Architecture (SOA)

• Team Foundation Server (TFS)

• WinForms

• Multithreaded Applications

• 64-bit applications

L-3.2.2 Subfactor 2: Management, Software and Systems Engineering Processes

L-3.2.2.1 Capability Maturity Model Integration (CMMI): The offeror shall detail its management approach and ability to manage software development projects following processes of CMMI V1.2 Level 3 IAW the JMPS Business Rules (JBR). The offeror shall provide evidence of current CMMI Level 3 (or above) assessment as part of the offeror’s proposal and describe the offeror’s plan to flow CMMI requirements to subcontractors/teaming partners ensuring all meet CMMI requirements IAW JBR 1.2.2.

The offeror shall describe their plan to maintain certification in CMMI Level 3 throughout the contract.

L-3.2.2.2 Software and Systems Engineering Processes: The offeror shall detail the offeror’s management approach to executing Software and Systems Engineering processes. The offeror shall clearly explain the proposed Agile (or similar) Software and Systems Engineering processes and how the offeror will manage executing the offeror’s Agile (or similar) processes to meet Government requirements for builds/releases; how the offeror will maintain the necessary agility to meet concurrent DO requirements (e.g. Navy/FMS) and adjust to re-prioritized requirements and schedules within the scope of each DO. The offeror’s management approach shall address, at minimum, the below items.

Additionally, the offeror shall identify risks, if any, associated with the proposed approach and actions the offeror will take to mitigate the identified risks.

a. Cite the Agile technique(s) being employed (e. g. Scrum, pair programming, extreme programming, etc.).

b. For each agile technique employed, describe your approach and provide a model/illustration depicting the process.

c. Describe the approach for release planning.

d. Identify the sprint length and how it was determined.

e. Describe how the backlog is initially established, and the process for modifying and re-prioritizing it.

f. Describe the typical sprint activities, and activities/processes during each iteration.

g. Describe the acquirer’s role (Government end user) in the sprints if the customer is not also the product owner (WPS program office).

h. Describe the mechanism for getting acquirer (end user) feedback for each sprint.

i. Describe how the product (working, useful piece of software) will be demonstrated to the product owner after each sprint (e.g., live demo on real equipment, in the lab with sim/stim, PowerPoint slides, etc.).

j. Describe the handling of incomplete user stories, unsatisfactory user stories, and bugs, and how they are factored back into the backlog.

k. Describe your process for keeping track of which user stories passed without any rework needed, which require rework, and which failed.

l. Reserved.

m. Discuss your approach to refactoring (clarifying or simplifying design of existing code).

n. List and describe the software metrics to be used.

o. Discuss your approach to paying off technical debt (i.e. cost of additional code re-work by choosing an easy solution now instead of a better approach that would take longer).

p. Describe how you will determine story points for the velocity metric (metric that a team can tackle during a single sprint).

q. Describe your Integrated Requirements Toolset (IRT) that traces user stories to mission threads and Key Performance Parameters (KPP’s), and whether this is a commercial tool or a tool developed by your organization. Additionally, describe how requirement changes shall be coordinated with the Enterprise Deficiency Reporting (EDR) IAW ELSG-ENG-PRO-REQ-004.(see export-controlled CD/DVD)

r. Describe how software development activities will be coordinated with your Integration and Test (I&T) team(s), and how it will assure I&T team(s) can meet testing requirements for software releases.

s. Describe how sprint-to-sprint dependencies (related to product and development resources) will be resolved and factored into the Sprint/Release Plan.

t. Describe your strategy/mechanism for keeping multiple sprint teams synchronized.

u. Describe how the integrity of the baseline is maintained for use in the development of the next sprint.

v. Describe how regression testing will be conducted for each sprint release for all previous functions released.

w. Describe how automated testing techniques will be used for sprint and/or regression testing.

x. Describe how the software development effort will be synchronized and coordinated with systems engineering activities and reviews.

y. Describe your staffing plan to include number of current personnel and/or a plan to obtain personnel with specific expertise in software development for weapons planning software and JMPS integration (any agile specific certifications (e.g.

Certified Scrum Master (CSM), Project Management Institute-Agile Certified Practitioner (PMI-ACP) etc.).

z. Describe your Configuration Management Process and how it will comply with the Enterprise Configuration Management Plan (E-CMP) (see export controlled CD/DVD). Describe the ability to provide configuration management throughout the WPS product lifecycles, with special emphasis on change control and tracking change requests from identification to final resolution of the change.

aa. Describe the offeror’s process to meet the JMPS security and risk assessment requirements of Risk Management Framework (RMF) IAW AFI 17-101 (see export controlled CD/DVD)

L-3.3. Subfactor 3: Delivery Order: FY19 Development and Legacy Enhancements

L-3.3.1 General: The offeror is required to respond to the Delivery Order Request for Proposal (DO RFP) package (Section J, Attachment 15) FA8681-19-F-1001, for the initial Delivery Order titled “FY19 Development and Legacy Enhancements.” The offeror shall provide a written technical proposal describing the methodology to complete all requirements within the basic contract SOW and all DO SOW requirements to include completing the Compliance Documents Matrix (DO RFP Attachment 2). The offeror shall consistently align Work Breakdown Structure (WBS), Integrated Master Schedule (IMS), and Basis of Estimates (BOE) throughout the DO portion of the proposal (including the Technical Volume and Cost/Price Volume).

L-3.3.2 Transition: The offeror’s technical proposal shall document a detailed transition plan for fully assuming performance of the DO as identified in the basic contract SOW and in the DO SOW paragraph 2.1. The plan shall, at a minimum, address each of the items listed below and provide a clear timeline for each (as applicable):

a. Provide a detailed description of the methodology to execute the requirements of the basic contract SOW paragraph 4, Contractor Performance (Integrated Performance Management, Integrated Master Schedule, Integrated Baseline Review and Work Breakdown Structure) as well as complete the DO SOW Appendix A, WPS 2.X Build Plan for CLINs 0100, 0200 and 0800 on this DO (for SRD, Change Request (CRs), Deficiency Report (DRs) utilize the DO SOW tasks in Table 1 and Table 2 to represent methodology for CLINs 0100 & 0200).

b. How the offeror will execute the system and software engineering processes/methods specific to completing the requirements of this DO SOW.

c. Provide the initial IMS with the proposal in Microsoft Project format. The IMS shall be detailed and valid in accordance with CDRL A002 for the entire DO and aligned with the DO SOW Appendix A.

d. The offeror shall complete the Compliance Documents Matrix, DO RFP Attachment 2, indicating the offeror’s ability to comply with the documents contained in the matrix. The offeror shall identify any noncompliance and shall provide rationale and plans to mitigate/resolve noncompliance and/or submit waivers needed to perform.

e. Provide a detailed description of the method of assuming software baseline management, and ensuring full build capability at the offeror’s facility.

f. Describe the testing plan to validate software build capability at the offeror’s facility where performance will occur. Describe measures to be taken to resolve issues until successful validation of the software build occurs prior to beginning new development.

L-3.3.3 Software Development: The offeror shall explain the offeror’s overall design to execute all DO SOW paragraph/subparagraphs 2.2. The explanation shall provide evidence of understanding and sound design strategy for completing development. The offeror may use documentation such as a design plan, implementation plan, risk management plan, testing plan, or any other documentation to include diagrams, storyboards, and/or mock screenshots. Provided documentation shall provide enough detail to clearly represent a viable solution. The overall design shall provide specific detail to develop and integrate the minimum capability in the following requirements:

a. GPS Jamming Requirements (DO SOW Table 1):

• The implementation plan to integrate WPS with the GPS Common Component (GPS CC) GIANT tools to provide GPS jamming analysis.

• The method to ensure WPS software provides GPS jamming analysis results to the planner in a clear and understandable manner.

• The method by which the offeror will ensure the user is able to use the GPS jamming analysis results to optimize PGM deliveries in a GPS contested environment.

• The method by which WPS GPS jamming analysis will support long range, multi-waypoint, and salvo weapons.

• Adequacy/Deficiencies: The offeror shall provide an assessment of the adequacy of the current GPS CC interface and GIANT tools to meet their proposed design solution and identify deficiencies to include potential mitigation plans.

b. Weather Common Component (DO SOW Table 1):

• The method to integrate WPS with the JMPS Weather CC to provide wind, temperature, and other weather data to the user.

• The method to provide weather data, within WPS in a clear, concise, and relevant manner.

c. Timeline Tool Component (DO SOW Table 1):

• The method to implement a visual timeline tool within the user interface which depicts relevant action points within a mission.

• The method to provide the WPS user an easily interpreted mission timeline tool which clearly shows action points related to that mission. This method shall be capable of optimizing missions.

L-3.3.4 Legacy Enhancements: The offeror shall describe/explain the offeror’s design solutions for DO SOW paragraph 2.3. The explanation shall provide evidence of understanding and sound design strategy for completing the respective enhancements.

The offeror may use documentation such as a design plan, implementation plan, risk management plan, testing plan, or any other documentation to include diagrams, storyboards, and/or mock screenshots. Provided documentation shall provide enough detail to clearly represent a viable solution for adding the following minimum capability requirements to WPS v2.1.X:

a. JMPS Common Time Playback Tool (DO SOW Table 2):

• The method to implement, integrate, and display weapon routes within WPS as part of the JMPS Common Playback Tool.

• The method to provide a user-friendly WPS tool that will playback aircraft and weapon routes.

b. Laser Line of Sight - Planning Tool (LOS-PT)

• The method to integrate the LOS-PT into WPS v2.1.x based on the SRD 1.2.1 requirements in SRD paragraph 3.2.2.5.7 (Bullets 1, 2, 4-6, and 9 only).

• The method to indicate laser spot size and incidence angle at release and weapon impact.

• The method to support planning for buddy lasing.

• The method to graphically display masking along the aircraft ground track with the parameters given in SRD 1.2.1, paragraph 3.2.2.5.7 (Bullets 4 and 5).

• The method to display the ground footprint with the parameters given in SRD

1.2.1, paragraph 3.2.2.5.7 (Bullet 6).

• The method to support multiple sensors and designators with the parameters given in SRD 1.2.1, paragraph 3.2.2.5.7 (Bullet 9).

c. Vertical Launch Acceptable Region (LAR) Enhancements

• The method to provide an enhanced and user-friendly weapon flight path display and interactive controls within WPS as part of the existing WPS Vertical LAR Tool.

• The method to provide an option that will update the current weapon plan from the WPS Vertical LAR Tool.

• The methods to incorporate the enhancements included in CR number 2018- DRAFT, which is included in the export controlled CD/DVD within the folder titled “Initial delivery Order Documents.”

L-4.0 VOLUME III, Subfactor 4: Small Business (SB) Participation:

L-4.1 General: The SB Participation Submission is required from all offerors, including small businesses and companies with master, individual, commercial subcontracting plans and/or comprehensive subcontracting plans. The offeror/joint venture member and each proposed critical subcontractor shall include only the first tier of subcontractors for this effort. Offerors are advised the SB Participation Submission is not the same as the SB Subcontracting Plan required by FAR 52.219-9. Large business offerors shall not utilize the SB Subcontracting Plan in the place of the SB Participation Submission.

However, if an offeror is a large business, the proposal submission must include a separate SB Subcontracting Plan also.

L-4.2 Format and Specific Content: All offerors shall submit a SB Participation Plan

(IAW 52.219-8) for itself, any joint venture member, and each proposed critical subcontractor.

L-4.2.1 Small Business Participation: All offerors shall complete Table L-3 addressing the following elements in the proposed performance of the resultant contract and include it in the offeror’s SB Participation Submission.

The extent of participation of proposed SB when subcontracting possibilities exist.

Include the title of the companies the offeror plans to use in the performance of the resultant contract; the companies’ socio-economic category(ies), and the description of the subcontracted work each proposed subcontractor will perform.

Table L-3 – Small Businesses Participating

Company

Socio- Economic Category

Description of Supply/Service Performance

L-4.2.2 The offeror shall also complete Table L-4 SB Participation Goals and include it in the offeror’s SB Participation Submission. The goals shall be expressed in terms of percentages of the planned total contract dollars. If limited or no subcontracting possibilities exist for a category of small business, HUBZone, service-disabled veteran owned, small disadvantaged, women-owned, or veteran-owned concerns, the offeror shall provide substantiating rationale. Offerors are cautioned against only acknowledging a goal that does not meet the Government Goal. Rather, the offeror shall provide substantiating rationale including specific reasons why a proposed goal does not meet the Government Goal and any actions being taken to increase any shortfalls. For evaluation purposes, round the goals to 2 decimal places (hundredth’s place).

Table L-4 Offeror’s Proposed Participation Goals

Business Size

Government Goal (Based on Total

Contract Dollars)

Offeror’s Proposed

Participation Goals

Small Business 10%

Historically Underutilized Business Zone Small Business (HUBZone)

3%

Service-Disabled Veteran-Owned Small Business (SDVOSB)

3%

Small Disadvantaged Business (SDB) 5%

Woman-Owned Small Business

(WOSB)

5%

Veteran-Owned Small Business

(VOSB)

3%

L-4.2.3 Small Business Subcontracting Plan: Large business offerors are required to also submit a subcontracting plan. This plan may be a comprehensive subcontracting plan, approved by Defense Contract Management Agency, an individual subcontracting plan for this effort, or a master plan incorporated with an individual subcontracting plan for this effort. Small Businesses are not required to comply with this portion of this Subfactor.

Large business offerors shall provide a subcontracting plan IAW FAR Clause 52.219-9 Small Business Subcontracting Plan Alt II and DFARS 252.219-7003. If the proposed goals (based on total contract dollars) do not meet or exceed the Government’s total contract dollars goals, substantiating rationale shall be provided. Section J, Attachment 16 (Checklist Subcontracting Plan) is provided as a guide for submission. Offeror is not required to fill out the attachment or submit it with their proposal.

An offeror’s subcontracting plan shall be consistent with the commitments made in their SB Participation Submission.

L-5.0. VOLUME IV, Factor II, Cost/Price

L-5.1. Cost and Pricing Instructions

The offeror shall provide a cost/price proposal (Volume IV) which fully and clearly demonstrates completeness, reasonableness, cost realism, and balanced pricing for the Total Proposed Amount (TPA). The cost/price proposal shall be in accordance with (IAW) Section J, Attachment 17 – Cost/Price Spreadsheet. Instructions for completing Attachment 17 are found on the first tab of the spreadsheet titled “Read First.” The cost/price volume shall include rates for the first three years and shall include the cost/price for the initial DO CLINs as described in Attachment 17. The TPA will include the three years annual total proposed Burdened Labor Rates (BLR) (representative of the basic contract CLINs 0100, 0200, 0300, 0400), three years annual total proposed Fully Burdened Labor Rates (FBLR) (representative of basic contract CLIN 0700) and all the initial DO CLINs totaled as calculated in the Attachment 17 – Cost/Price Spreadsheet Tab 12.

L-5.1.1 The cost/price proposal shall document labor rates (BLR, FBLR) and CPFF fee rates for the first three years of the ordering period, and Tab 13 Section J - Attachment 7 Rates which will become Section J, Attachment 7 - Rates on the basic contract…