Amendment_02_19_Oct_2017.pdf

For the best experience, open this PDF portfolio in

Acrobat X or Adobe Reader X, or later.

Get Adobe Reader Now!

http://www.adobe.com/go/reader

DEPARTMENT OF THE AIR FORCE

BUSINESS AND ENTERPRISE SYSTEMS DIRECTORATE

MAXWELL AIR FORCE BASE GUNTER ANNEX ALABAMA

19 October 2017

Request for Proposal (RFP) for Small Business Enterprise Application Solutions (SBEAS) Indefinite Delivery Indefinite Quantity (IDIQ) Contract

FA8771-17-R-1000

Amendment 02

The following attachment to the SBEAS RFP has been amended:

1. Instructions to Offerors (ITO)

The attachment contains lines next to each section that has been updated.

Additionally, the Government would like to clarify the answer to question 135 provided in the Questions and Answers document posted on 13 October 2017.

Question: The sixth sentence in section 1.2.2 states, "Pages shall be numbered sequentially by volume." Does the Government intend for page 1 to start at the Table of Contents for each volume?

The Government’s Initial Response: No, the Government does not intend for page 1 to start at the "Table of Contents"

The Government’s Revised Response: Pages of each document shall be numbered sequentially within each volume. For example, Volume Organization for Volume II shall contain the information in tabbed sections IAW the following general outline:

(1) Table of Contents (Numbering shall begin with page 1)

(2) Cross-Reference Matrix (CRM) (Numbering shall begin with page 1)

(3) Glossary (Numbering shall begin with page 1)

(4) Self-Scoring Worksheet (Numbering shall begin with page 1)

(5) Technical Narratives (Numbering shall begin with page 1)

The proposal due date remains unchanged and Offerors shall submit their proposal (IAW) the Instructions to Offerors (ITO).

At this time, the Government does not anticipate another round of questions and answers.

This RFP is not authorization to begin performance, and in no way obligates the Government for any costs incurred by the contractor for this requirement. Prior to commencement of any activities associated with performance of this requirement, the Government will issue a written directive or contractual document signed by the Contracting Officer with appropriate consideration established.

Shaneka K. Brown Contracting Officer

2017-10-19T16:03:08-0500

BROWN.SHANEKA.K.1258521273

Section L Attachment 2 Instructions to Offerors

1.0 Section L Instructions to Offerors (ITO)

(a) Only one (1) proposal may be submitted by each qualified offeror in response to this requirement. For this solicitation, each Offeror may only be a member of one approved Joint Venture (JV). Additionally, if an Offeror proposes as a member of an approved JV, that Offeror may NOT also propose as a prime. An Offeror found to be bidding in violation of these instructions will be removed from the competition and, therefore, ineligible for an award.

All proposals submitted in response to this solicitation shall be in compliance with these instructions. Non-conformance with the instructions provided in this ITO may result in an Offeror’s proposal being rejected from the competition.

(b) The proposal shall be clear, specific, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical and Past Performance criteria defined in Section M, Evaluation Criteria. All the requirements specified in the solicitation are mandatory. The proposal should not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the Offeror’s proposal meets these requirements. The Offeror shall assume that the Government has no prior knowledge of the Offeror’s facilities and experience, and therefore will base its evaluation on the information presented in the Offeror's proposal. By your proposal submission, you are representing that you will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal.

(c) Elaborate brochures or documentation, binding, detailed art work, or other embellishments shall not be submitted with the Offeror’s proposal.

(d) The completion and submission of all proposal volumes constitutes the Offeror's acceptance of the terms and conditions in this RFP including all attachments hereto. Proposals will be considered late, in accordance with (IAW) Federal Acquisition Regulation (FAR) 15.208, if the hard copy and electronic copy of the proposals are not received by the date specified in this

ITO.

(e) IAW FAR Subpart 4.8 (Government Contract Files), the Government will retain the original copy of all unsuccessful proposals. Unless the Offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

(f) Offerors are advised that contractor prime/subcontractor teaming arrangements are not allowed and are not being evaluated at the IDIQ level. Offerors may submit technical experience and past performance references for work it performed as a prime, subcontractor (the prime offeror proposing must have been the subcontractor). Offerors proposing as a Joint Venturer (JV) may submit technical experience and past performance references for work performed if proposing on this solicitation under the same JV. Offerors who are/were members of a JV that is NOT proposing on this solicitation may submit technical experience and past performance references from that non-proposing JV. These references from a non-proposing JV will only be evaluated if a PPQ is provided by the customer which clearly identifies work performed by the proposing Offeror and proof that proposing Offeror is/was a member of the other JV is verified by providing the documentation which is specified IAW paragraph 5.2.4 of the ITO. For example, if Company A is a part of a JV proposing on this solicitation, the references being used can be in the name of Company A or in the name of the JV proposing on this solicitation. If Company A is/was a part of another JV that is NOT proposing on this solicitation, those references CAN be used if a PPQ, and appropriate documentation IAW paragraph 5.2.4 of the ITO, is provided for Company A. Once contract awards have been made, all awardees are allowed to form prime/subcontractor relationships as necessary at the task order level.

Proposal Submission

Submission of Hard Copy Proposal Volumes One hard copy of the proposal shall be submitted and clearly marked, addressed, and mailed or hand-carried to the Procuring Contracting Officer (PCO) at the below address no later than 2 November 10:00 a.m. Central Daylight Time (CDT).

SHANEKA K. BROWN, PCO, SBEAS

AFLCMC HIK

501 EAST MOORE DR.

BLDG 884, SUITE 1400L

MAXWELL AFB - GUNTER ANNEX, AL 36114

Submission of Electronic Proposal Volumes One copy of the proposal shall be submitted electronically by uploading a copy to the Army’s Safe Access File Exchange (SAFE) at https://safe.amrdec.army.mil/safe/Welcome.aspx no later than 2 November 10:00 a.m. CDT. The following email address shall be entered into SAFE for the Recipeint’s List: AFLCMC.BES.SB_IDIQ_RFP@us.af.mil. **In the event the AMRDEC/SAFE site is down on 2 November 2017, offerors shall contact the Contracting Officer immediately for further direction.

In the event there are any discrepancies between the hard copy and the electronic copy of the proposal, the hard copy will take precedence and will be used for evaluation.

Offerors’ hard copy/electronic proposal documentation shall include “Source Selection Information markings – See FAR 2.101 & 3.104”.

1.1 General Information

https://safe.amrdec.army.mil/safe/Welcome.aspx file://periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc#T2101 file://periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC#b3104

Point of Contact Ms. Shaneka K. Brown, PCO - SBEAS, is the sole point of contact for this acquisition. Written requests for clarification may be sent via e-mail to the PCO at AFLCMC.BES.SB_IDIQ_RFP@us.af.mil.

Joint Venture Agreements Only Joint Ventures (JVs), including Mentor Protégé JVs, whose JV agreement was previously approved by the SBEAS PCO are allowed to submit a proposal in response to this solicitation.

Debriefings Pre-award Debriefing of Offerors: IAW FAR 15.505, Offerors excluded from the competitive range or otherwise excluded from the competition before award may request a debriefing before award. The Offeror may request a pre-award debriefing by submitting a written request for debriefing to the PCO within three (3) days after receipt of the notice of exclusion from the competition. At the Offeror’s request, this debriefing may be delayed until after award. If the debriefing is delayed until after award, it shall include all information normally provided in a post-award debriefing. If the Offeror does not submit a timely request, the Offeror need not be given either a pre-award or a post-award debriefing. Offerors are entitled to no more than one debriefing for each proposal. The PCO shall make every effort to debrief the unsuccessful Offeror as soon as practicable, but may refuse the request for a debriefing if, for compelling reasons, it is not in the best interest of the Government to conduct a debriefing at the requested time.

Post-award Debriefing of Offerors: An Offeror, upon its written request received by the agency within three (3) days after the date on which that Offeror received notification of contract award IAW 15.503(b), shall be debriefed and furnished the basis for the selection decision and contract award. To the maximum extent practicable, the debriefing should occur within five (5) days after receipt of the written request. Offerors that requested a post-award debriefing in lieu of a pre-award debriefing, or whose debriefing was delayed for compelling reasons beyond contract award, also should be debriefed within this time period. An Offeror that was notified of exclusion from the competition, but failed to submit a timely request, is not entitled to a debriefing.

Discrepancies If an Offeror believes that 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 as related to the omission or error.

Electronic Reference Documents Official RFP documentation, including RFP amendments, and other related information will be available via Federal Business Opportunities (FedBizOpps) at https://www.fbo.gov/. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has https://www.fbo.gov/ been posted to the website for this solicitation.

Communications Exchanges of source selection information between Government and Offerors will be controlled by the PCO, therefore all questions or concerns shall be submitted to the PCO IAW ITO Section 1.1—Point of Contact. Email will be used to transmit source selection information to Offerors only. Offerors’ emails shall include “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line.

1.2 Organization/Number of Copies/Page Limits

The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1.2 below). The titles and contents of the volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 1.2.

The contents of each proposal volume are described in the ITO paragraph as noted in the table below:

Table 1.2 - Proposal Organization

VOLUME ITO Paragraph Number

VOLUME TITLE COPIES PAGE

LIMIT

I 2.0 CMMI

Documentation

1 Original Hard Copy and 1

Electronic Copy

No Page Limit

II 3.0 Technical Experience 1 Original Hard

20 Pages Total

III 4.0 Past Performance 1 Original Hard Copy,1 Electronic

Copy

25 Pages Total

IV 5.0 Contract Documentation

1 Original Hard

No Page Limit

1.2.1 Page Limitations

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Each page shall be counted except the following; any Cover Sheets, Table of Contents, Cross-Reference Matrix (CRM), Self-Scoring Worksheet, Contractor Performance Assessment Reports (CPAR), Past Performance Questionnaires (PPQ), Tabs, and Glossaries of abbreviations and acronyms.

1.2.2 Page Size and Format

The following page size and format instructions will allow for a common baseline for proposals.

Page size shall be 8.5 x 11 inches. Foldouts are not permitted. Pages shall be single-spaced and file://periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/Far02.doc#T2101 file://periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC#b3104 printed double-sided. The font size shall be no less than Times New Roman ten (10) point. Use at least 1-inch margins on the top and bottom and ¾-inch side margins. Pages of each document shall be numbered sequentially within each volume. Offerors are allowed to use a font style of its choice for tables, charts, graphs and figures; the font shall be no smaller than eight (8) points for tables, charts, graphs and figures. Line spacing, font size, margins, and other restrictions do not apply to the pages that are generated by the Cross-Reference Matrix, CMMI documentation, or Self-Scoring Worksheet.

1.2.3 Cross-Reference Matrix (CRM)

Offerors shall complete the CRM located in Section J, Attachment 4 of this solicitation.

Offerors shall include the same copy of the CRM in both the Technical (Volume II) and Past Performance (Volume III) volumes; the CRM shall be submitted as MS Excel documents for both volumes. The Offeror’s CRM shall show traceability between the Offeror’s contract references used for both Volume II and Volume III. The Offeror’s CRM shall show which contract references are used to satisfy each technical element and each past performance sub-factor. The CRM shall verify that all contract references used by the Offeror to support points claimed in Volume II are also used in Volume III. When completing the CRM to be submitted with each volume, please refer to the instructions within the CRM attachment. (Note: Please read the instructions in the CRM prior to completing.)

1.2.4 Glossary of Abbreviations and Acronyms

Both volumes II and III shall contain a glossary of all abbreviations and acronyms used, and with an explanation for each. By providing this information, the Offeror is not required to spell out each acronym within other sections of the corresponding volume. Offerors shall only define terms that are not already defined and included in Attachment 7, Definition of Terms.

1.2.5 Binding and Labeling

Hard Copy Submission:

Proposals shall be bound in a single three-ring, loose leaf binder permitting the volumes to lie flat when open. Staples shall not be used. All volumes shall be submitted together in one (1) binder. Offerors may use any color binder other than red. Each volume shall be tabbed using standard page tabs or a blank sheet may be inserted. A cover sheet shall be included in each volume identifying the volume number, title, solicitation number, cage code, and the Offeror's name. The same identifying data shall be placed on the spine of the binder.

Electronic Copy Submission:

Volumes I and II: Shall be submitted as one combined Adobe PDF document with the exception of the CRM and Self-scoring Worksheet. The CRM and Self-Scoring Worksheet shall each be submitted as separate MS Excel documents.

Volume III: Shall be submitted as one combined Adobe PDF document with the exception of the CRM. The CRM shall be submitted as a separate MS Excel document.

Volume IV: Shall be submitted as one combined Adobe PDF document.

Be sure to apply all appropriate markings including those prescribed IAW FAR 52.215-1(e), Restriction on disclosure and use of data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

1.2.6 Contract References

All contract references submitted for both Volume II and Volume III shall be within the three (3) year window for recency. The Government defines recent contracts to be any contract that is ongoing or completed within the past three (3) years from the date of issuance of the solicitation.

• Multiple-award IDIQ: Multiple award IDIQ contract numbers are not allowed to be used as a reference however, an individual task order issued against the multiple-award IDIQ is allowed. Multiple task orders issued against a multiple-award IDIQ cannot be combined and counted as one contract reference.

• Single-award IDIQ: Offerors using single-award IDIQ contract numbers as a contract reference shall include BOTH the IDIQ contract number AND the individual task order number(s) in order to verify and validate that the IDIQ being referenced is in fact a single-award IDIQ contract. A maximum of three (3) task orders issued against a single-award IDIQ can be combined and counted as one (1) contract reference to address the criteria. A method of quality assessment shall be obtainable to the Government (i.e.

CPAR/PPQ) for each contract reference.

• Blanket Purchase Agreements (BPAs): BPA contract numbers are not allowed to be used as a reference. However, the individual call/delivery order numbers issued against the BPA are allowed. Offerors using single-award BPA call/order numbers as a contract reference shall include BOTH the BPA number AND the individual call/order number in order to verify and validate that the BPA being referenced is in fact a single award BPA.

A maximum of three (3) call/orders issued against a single-award BPA can be combined and counted as one contract reference to address the criteria. A method of quality assessment shall be obtainable to the Government (i.e. CPAR/PPQ) for each contract reference.

file://periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR52.215.doc#b522151 file://periwinkle_vnx/SAF_AQC_ORG/AQCP/5640%20-%20AFFARS/Templates%20Project%20--%20Sep%202013/5315/AppData/Local/Microsoft/Windows/Temporary%20Internet%20Files/AFAC%20Working%20Folders%20--%20PM/far/FAR03.DOC#b31044

• Predecessor: “Predecessor” means an entity that is replaced by a successor and includes any predecessors of the predecessor (FAR 52.204-16- Predecessor of Offeror). A predecessor company’s past performance may be considered as long as (1), the Offeror succeeded the predecessor company; (2) the predecessor company actually performed the work for which the successor company is referencing. The Government will not consider sister or affiliated company past performance.

• Joint Ventures (JV): For Offerors proposing as a JV, contract references submitted shall represent work performed by the approved JV, if available AND a minimum of one (1) contract reference shall be submitted, for Volumes II and III, by each member comprising the JV (see CFR 13 125.8(e)); offerors shall annotate the name of the JV member for these references on all documents ( PPQ, CRM, Technical Narratives and Past Performance Narratives). If a minimum of one contract reference is not submitted by each member comprising the JV for Volumes II and III, the Offeror will be considered non-compliant and not eligible for contract award.

2.0 Volume I – CMMI Development or Services Appraisal Documentation

The Government shall be able to obtain proof of an Offeror’s Level 2 (at a minimum) appraisal in Capability Maturity Model Integration (CMMI) Development or Services using the Standard CMMI Appraisal Method for Process Improvement (SCAMPI) This appraisal must be held at the Offeror’s organizational level, not for an individual person. Upon proposal receipt, the Government will enter the company name into the Published Appraisal Results (PAR) system to obtain a copy of the Final Findings Report which must display a “current” CMMI appraisal at that time.

If the Offeror’s previously validated CMMI appraisal expires prior to contract award, the PCO will notify the Offeror.The Offeror shall notify the Contracting Officer (via SBEAS email address) that a reappraisal has been accomplished. The updated appraisal results shall meet the same requirements listed above. Offeror shall submit the reappraisal notification to the CO within three (3) business days of being notified; otherwise, the Offeror will be ineligible for contract award.

For approved JVs, a minimum of 50% of the individual members comprising the JV must hold the CMMI appraisal. Offerors with an odd number of JV members shall round up to the next even number BEFORE calculating the 50%.

Example: If the JV has 5 members…round up to 6 then calculate 50% to get a requirement of 3 members that must hold the CMMI requirement.

Offerors shall submit the following information:

a. Name(s) of the company holding a current CMMI appraisal; provide name ‘exactly’ as listed on the appraisal. For JVs, list the name of each member who holds a CMMI appraisal.

b. Type of CMMI appraisal (Development or Services)

3.0 Volume II - Technical Experience

3.1 General

Each Offeror shall submit a Technical Experience volume (Volume II) with its proposal. Offerors may submit a maximum of six (6) contract references to address the criteria of the Technical Experience factor (see 1.2.6 Contract References). Any contract references used in Volume II shall also be used in Volume III. If during the evaluation process, the Government discovers a contract was used to claim points in Volume II and the same contract was not used in Volume III, the contract reference will be removed from consideration and the Offeror will NOT receive credit (zero points) for the points being claimed for those technical experience elements related to that contract reference.

3.1.1 Volume Organization

Volume II shall contain the information in tabbed sections IAW the following general outline:

(1) Table of Contents

(2) Cross-Reference Matrix (CRM)

(3) Glossary

(4) Self-Scoring Worksheet

(5) Technical Narratives

3.1.2 Self-Scoring Worksheet

Offerors shall complete and submit a single Self-Scoring Worksheet located in Section J, Attachment 5 of this solicitation. The worksheet shall be submitted in no higher than MS Excel 2013. A .pdf document will not satisfy this requirement and shall not be submitted. The Government will not accept any worksheets that have been password protected or “locked”.

Worksheets submitted in any other format than what is specified above shall be considered to be non-compliant with the instructions of the solicitation and therefore, the worksheet will not be evaluated. Offerors shall use the instructions provided in the Self-Scoring Worksheet attachment to complete the document.

3.1.3 Technical Narrative (TN)

The technical narrative section shall describe the Offeror’s experience that supports the technical element points claimed on the Self-Scoring Worksheet. The TN section shall not exceed the maximum of 20 pages. Each TN shall only address one (1) contract reference. The contract references used to address the criteria for the technical experience shall be submitted in numerical order; ex. TN one (1) through six (6). When starting a new TN, include the TN number, project title, contract/project number (or equivalent) and period of performance at the beginning of the narrative. For example: TN 1; Logistics Systems Support; FA8771-XX-F- XXXX; 1 Oct 2015 -30 Sep 2017. The pages allotted can be used at the Offeror’s discretion.

For technical elements which do not call out a specific term (e.g., operating system, tool, software, etc.), the Offeror may claim credit for similar experience. In those instances, the Offeror shall describe the similarities.

3.2. Technical Element Criteria

Offerors shall utilize the Definition of Terms provided in Section J, Attachment 7 of this solicitation, the Risk Management Framework (RMF) and DoD Information Assurance Certification and Accreditation Process (DIACAP) standards to help form a better understanding of the Government’s use and definition of specific technical terms.

1. Life-cycle Software Services Sub-Element 1a: Life-cycle Software Services (Developing/ Implementation) Offeror shall describe its experience in design, build, test, and implementation of an Information System (IS) as defined in all of the following:

• The process of implementing software solutions to one or more sets of problems

• The process by which source code is converted into a stand-alone form that can be run on a computer or to the form itself. One of the most important steps of a software build is the compilation process, where source code files are converted into executable code

• Obtaining, verifying, or providing data for any of the following: the performance, operational capability, and suitability of systems, subsystems, components, or equipment items; or vulnerability and lethality of systems, subsystems, components, or equipment items

• Planning; coordinating; scheduling; deploying/installing (or providing all needed technical assistance to deploy/install) and transitioning a technical solution (e.g., information system) into the operational environment.

(SOO Sections 3.1.11, 3.4.3, and 3.4.5)

Sub-Element 1b: Life-cycle Software Services (Re-Engineering) Offeror shall describe its experience re-engineering an IS during its life-cycle to include what was altered from the system’s existing state and the resulting reconstituted form (SOO Sections

3.1.4 and 3.1.16).

Sub-Element 1c: Life-cycle Software Services (Data or System Migration) Offeror shall describe its experience migrating an IS or its data during the life-cycle to include moving data or the IS from the previous operating environments to the new operating environments (SOO Section 3.1.12).

Sub-Element 1d: Life-cycle Software Services (Modernization) Offeror shall describe its experience modernizing a legacy IS during its life-cycle to include the conversion and code rewriting of a legacy system, software libraries and protocols to a modern programming language and porting the new IS to a new hardware platform (SOO Sections 3.1.9, 3.1.14, and 3.1.16).

Sub-Element 1e: Life-cycle Software Services (Commercial-off-the-Shelf/Government-off-the-Shelf/Free and Open Source Software [COTS/GOTS/FOSS] Enterprise Resource Planning [ERP] Software Systems) Offeror shall describe its experience in one of the following:

• Implementing one (1) COTS, GOTS or FOSS ERP software package to satisfy business processes in the finance, personnel, and/or supply chain/manufacturing domain for one or more customer organizations where the Offeror's COTS, GOTS or FOSS ERP software implementation was ultimately fielded for operational use by the customer

OR

• Providing lifecycle software service support for one (1) COTS, GOTS or FOSS ERP software implementation for which the Offeror was not the original implementer at initial deployment where one (1) of the following is demonstrated:

o Offeror played a key role in working with the customer to develop, define and/or blueprint operational business rules that were implemented by the COTS, GOTS or FOSS ERP software package; or o Offeror performed gap analysis and developed resulting custom reports, interfaces, data conversions, and functional extensions to the COTS, GOTS or FOSS ERP software product.

(SOO Section 3.4.5)

2. Cybersecurity Sub-Element 2a: Cybersecurity (Vulnerabilities and Threats) Offeror shall describe its knowledge and experience in providing services to assess software application vulnerabilities and threats using the Risk Management Framework (RMF).

Sub-Element 2b: Cybersecurity (Risk Management) Offeror shall describe its knowledge and experience in incorporating risk management principles and information security requirements to prevent the loss of data Confidentiality, Integrity, and Availability using the following three (3) preventative technical controls;

Authentication, Authorization, and Accountability (Nonrepudiation) (SOO Section 3.1.10).

3. Information Technology [IT] Business Analysis Sub-Element 3a: IT Business Analysis (Requirements Analysis) Offeror shall describe its experience providing Requirements Analysis as a Life-cycle Software Service. Offeror shall also describe its experience working with stakeholders to define a design solution (SOO Section 3.2.2 and 3.1.2).

Sub-Element 3b: IT Business Analysis (Testing, Validation and Verification) Offeror shall describe its experience providing Testing, Validation and Verification as a Life-cycle Software Service in all areas defined below:

• Obtaining, verifying, or providing data for any of the following: the performance, operational capability, and suitability of systems, subsystems, components, or equipment items; or vulnerability and lethality of systems, subsystems, components, or equipment items

• Evaluating a system or software component in the development process to determine whether the item satisfies specified requirements; and

• Confirming a system element meets design-to or build-to specifications.

(SOO Section 3.2.2 and 3.1.2)

Sub-Element 3c: IT Business Analysis (Service Desk/Help Desk) Offeror shall describe its experience providing Service Desk/Help Desk services for an IS in any of the following IT Service Desk/Help Desk domains:

• Access Management - process of granting authorized users the right to use a service while preventing access to non-authorized users.

• Event Management - process of identifying and prioritizing all events that occur throughout the IT infrastructure and establish the appropriate response to those events.

• Incident Management - process of restoring normal service operation as quickly as possible, minimizing the adverse impact on mission partner operations, thus ensuring that the best possible levels of service quality, security, and availability are maintained.

• Problem Management - process of preventing problems and incidents from happening, eliminate recurring incidents and minimizing the impact of incidents that cannot be prevented.

• Request Management - process of fulfilling requests from users and routing each request to the appropriate process owner for handling within accepted service levels.

(SOO Section 3.2.3)

Sub-Element 3d: IT Business Analysis (Functional Business Area Expert [FBAE]) Offeror shall describe its experience providing FBAE as Life-cycle Software service. Offerors shall also demonstrate FBAE experience assessing either the “as is” or the “to be” operational/functional business process, identifying inadequacies or deficiencies affecting the ability of the technical solution to meet stakeholder requirements (SOO Section 3.2.2).

4. Programming Languages /Frameworks Sub-Element 4a Offeror shall describe its experience providing Life-cycle Software Services using any two (2) of the following: Java, COBOL, PowerBuilder, .NET, ColdFusion, C#.

Sub-Element 4b Offeror shall describe its experience providing Life-cycle Software Services using any two (2) of the following: JavaScript, Perl, SQL, PYTHON, PHP.

Sub-Element 4c Offeror shall describe its experience providing Life-cycle Software Services using any one (1) of the following: SWIFT, Ruby On Rails, JavaScript MV* Frameworks, Spark.

(SOO Section 3.1.5)

5. Tools / Software Development Methodologies Sub-Element 5a: Tools/Development Methodology (Security) Offeror shall describe its experience using a COTS, GOTS or free and open source (FOSS) tool in the functional areas of security to analyze source code for vulnerabilities during the life-cycle of a project. Offeror shall identify the tool with which they have experience to include, but not limited to: Fortify, Sonatype, AppScan.

Sub-Element 5b: Tools/Development Methodology (Quality) Offeror shall describe its experience using COTS, GOTS or FOSS tool, in the functional areas of quality to analyze source code, executables, and related artifacts (e.g., code documentation) against code metrics during the life-cycle of a project. Offeror shall identify the tool with which they have experience to include, but not limited to: Sonar, AppDynamic, CAST Code Analysis Tool.

Sub-Element 5c: Tools/Development Methodology (Testing) Offeror shall describe its experience using a COTS, GOTS or FOSS tool in the functional area of testing to analyze source code for vulnerabilities during the life-cycle of a project. Offeror shall describe its experience using a common database to manage the test information for the system under test (to include capturing defects) or the offeror’s experience creating, maintaining, and executing test scripts using an automated tool. Offeror shall identify the tool with which they have experience to include, but not limited to: HP Application Lifecycle Management, Selenium, Quick Test Pro.

Sub-Element 5d: Tools/Development Methodology (Software Development Methodologies) Offeror shall describe its experience using the preferred software development methodology during the life-cycle of a project as identified in Section 3.1.5 of the SOO. Offeror shall identify the specific methodology with which they have experience.

(SOO Sections 3.1.5, 3.1.6, 3.1.11 and 3.4.5)

6. Platforms / Environments Sub-Element 6a: Platforms/Environments (Mainframe, Mid-tier/Client-server, or Web Services) Offeror shall describe its experience implementing an IS into any of the following: mainframe, mid-tier/client-server, web services.

Sub-Element 6b: Platforms/Environments (Customer’s Facility)Offeror shall describe its experience providing support services in the customer’s facility (e.g., not the offeror’s home office) of a non-DoD or DoD mainframe, mid-tier/client-server or web services.

Sub-Element 6c: Platforms/Environments (Commercial, Non-commercial, or Hybrid Cloud) Offeror shall describe its experience developing or modifying an existing IS to operate within or migrate to a commercial, non-commercial, or hybrid cloud.

Sub-Element 6d: Platforms/Environments (Defense Information Systems Agency [DISA] Enterprise Computing Center [DECC] or Department of Defense [DoD] Computing Facility) Offeror shall describe its experience developing or modifying an existing IS to operate within a DISA DECC or DoD computing facility.

(SOO Section 3.3)

7. Database Components Sub-Element 7a: Database Components (Relational Database Management System

[RDBMS])

Offeror shall describe its experience developing, designing or maintaining a RDBMS database to include, but not limited to: Oracle, SQL Server, DB2, SyBase, Postgresql, MarialDB, JasperSoft, MYSQL.

Sub-Element 7b: Database Components (Not Only Structured Query Language [NoSQL]) Offeror shall describe its experience developing, designing, or maintaining a NoSQL database to include, but not limited to: Postgresql, Cassandra, MongoDB, Hadoop, Spark, CouchDB.

Sub-Element 7c: Database Components (RDBMS or NoSQL) Offeror shall describe its experience providing any of the following data store support services in a RDBMS or NoSQL database: managing the current storage environment, providing application support, maintaining proper backup schedule, monitoring current storage environment or planning and execution of new installs. (SOO Section 3.1.9)

8. Mobile/Internet of Things (IoT) Sub-Element 8a: Mobile/IOT (New Mobile Application Development) Offeror shall describe its experience developing and implementing a new mobile application that runs on any of the following: Apple iPhone Operating System (IOS), Windows, Android.

Sub-Element 8b: Mobile/IoT (Legacy Application & Mobile Integration Services) Offeror shall describe its experience redesigning a legacy system to work with or on a mobile device using any of the following: Apple IPhone Operating System (IOS), Windows, Android.

Sub-Element 8c: Mobile/IoT (Automatic Identification Technology [AIT]/Sensors/RFID) Offeror shall describe its experience developing and implementing an IoT software-based solution to include, but not limited to: operating an AIT handheld terminal, collecting data from sensors, or using Radio Frequency Identification (RFID) (Active or Passive) to track and identify tags attached to equipment.

(SOO Section 3.1.7)

9. Server Operating Systems Offeror shall describe its experience providing life-cycle services to support the efficient operations of an IS for any of the following: Windows Server, Red Hat enterprise Linux, SUSE, UBUNTU (SOO Sections 3.1.13 and 3.1.15).

10. COTS/GOTS/FOSS Software Offeror shall describe its experience maintaining IS’s in development, test, or production environments by implementing COTS, GOTS or FOSS software patches and upgrades (SOO Section 3.1.15 and 3.4.5).

3.3 Non-Technical Experience Element

Government Facility Clearance Level (FCL) Offeror’s claiming points for FCL on the Self scoring worksheet shall ensure the Government can verify an “active” FCL in the National Industrial Security System (NISS). The NISS will be searched by each Offeror’s Cage Code. Offerors shall only claim points for either a “Secret” or a “Top Secret” FCL. A Technical Narrative reference is not required on the Self-Scoring Worsheet for FCL.

4.0 Volume III - Past Performance

4.1 General

Each Offeror shall submit a past performance volume with its proposal. Offerors are allowed to submit a maximum of six (6) recent contracts to address the criteria of the past performance sub-factors (see ITO Section 1.2.6 Contract References). The Government defines recent contracts to be any contract that is ongoing or completed within the past three (3) years from the date of issuance of this solicitation. Each contract reference used equates to a Past Performance Narrative (PPN). Any contract reference used in Volume II shall also be used in Volume III.

If the Offeror referenced less than six (6) contracts in Volume II, additional contracts may be used to address the past performance sub-factors up to the maximum allowed.

4.2 Volume Organization

IAW ITO Table 1.2 Proposal Organization, Offerors are required to submit a hard copy and electronic copy that shall be identical.

Volume III shall contain the information in tabbed sections IAW the following general outline:

(1) Table of Contents

(2) Cross-Reference Matrix (CRM)

(3) Past Performance Narratives (PPNs)

(4) Contractor Performance Assessment Reports (CPARS) (as applicable)

(5) Glossary

4.3 Past Performance Narratives (PPNs)

The PPN section shall describe the Offeror’s past performance that supports the three (3) past performance sub-factors below. The contract references used to address the criteria for each sub-factor shall be submitted in numerical order, ex. PPN one (1) through six (6). When starting a new PPN, include the PPN number, project title, contract/project number (or equivalent) and period of performance at the beginning of the narrative. For example: PPN 1;

Logistics Systems Support; FA8771-XX-F-XXXX; 1 Oct 2015 -30 Sep 2017. Each PPN shall only address one (1) contract reference (see ITO Section 1.2.6 Contract References). The PPN section shall not exceed the maximum of 25 pages. The pages allotted can be used at the Offerors discretion.

4.3.1 Past Performance Sub-Factor Criteria

Offerors shall utilize the applicable SOO sections, Definition of Terms (Section J, Attachment 7) and the Risk Management Framework (RMF) and DoD Information Assurance Certification and Accreditation Process (DIACAP) standards to help form a better understanding of the Government’s use of specific technical terms and requirements.

4.3.1.1 Sub-factor 1: Life-Cycle Software Services

Offeror shall describe past performance as it relates to the requirements identified in the SOO Sections 3.1.3 through 3.1.9 and 3.1.11 through 3.1.17. Sub-factor 1 excludes SOO

3.1.10 since it is evaluated as sub-factor 2.

Sub-Element 1a: System Architecture and Design The Offeror shall demonstrate past performance structuring system components and establishing component relationships by incorporating architectural principles and guidelines during their design process. The Offeror shall address past performance related to creating or modifying system architectural documents (i.e., Operational Views (OV) or System Views (SV)), and how the Offeror used those documents when designing a technical solution (SOO Section 3.1.3).

Sub-Element 1b: Technical Solution, Design, Build, Test and Implement The Offeror shall demonstrate past performance designing, building, testing, and implementing an IS. The Offeror shall address designing, building, testing and implementing software solutions to one or more sets of problems from a defined business process, user story, or business use cases (SOO Section 3.1.4).

Sub-Element 1c: Software Development Methodologies The Offeror shall demonstrate past performance using current and emerging software development methodologies. The Offeror shall address by name the methodology used such as Agile (SOO Section 3.1.5).

Sub-Element 1d: Information/Web Services Development and Testing The Offeror shall demonstrate past performance developing and testing a technical solution using various web services. The Offeror shall address a request and/or response mechanism that allows a client to remotely access or modify data (SOO Section 3.1.6).

Sub-Element 1e: Mobile or Internet of Things (IoT) The Offeror shall demonstrate past performance:

(a) Developing and implementing a new mobile application that runs on one (1) of the following: Apple iPhone Operating System (IOS), Windows or Android; OR

(b) Redesigning a legacy system to work with or on a mobile device using one (1) of the following: Apple iPhone Operating System (IOS), Windows, or Android; OR

(c) Developing and implementing an IoT software-based solution to include, but not limited to: operating an AIT handheld terminal, collecting data from sensors, or using Radio Frequency Identification (RFID) (Active or Passive) to track and identify tags attached to equipment (SOO Section 3.1.7).

Sub-Element 1f: Information Display Solutions and Services The Offeror shall demonstrate past performance designing, building and implementing or maintaining the services for one (1) of the information displays in SOO paragraph 3.1.8, as defined in Section J, Attachment 7 Definition of Terms (SOO Section 3.1.8).

Sub-Element 1g: Database Development or Conversion The Offeror shall demonstrate past performance developing a new database or converting a legacy system’s database during its life-cycle. The Offeror shall address the computer programming language, software libraries, protocols, or hardware platform used during the development or conversion (SOO Section 3.1.9).

Sub-Element 1h: Automated Integration Testing and Implementation The Offeror shall demonstrate past performance with Automated Integration Testing and Implementation. The Offeror shall address past performance planning, coordinating, scheduling and executing various automated test events which resulted in resource efficiencies (time, money, people or assets) (SOO Section 3.1.11).

Sub-Element 1i: System Migration The Offeror shall demonstrate past performance with migrating an IS during the IS life-cycle. The Offeror shall address past performance moving the IS from the previous operating environment to the new operating environment (SOO Section 3.1.12).

Sub-Element 1j: Application/System/Database/Interface Administration The Offeror shall demonstrate past performance administering one (1) of the following:

an application, system, database or interface (as described in SOO paragraph 3.1.13, and as defined in Section J, Attachment 7 Definition of Terms). The Offeror shall address the control process for the area described (SOO Section 3.1.13).

Sub-Element 1k: Modification of the Form, Fit, Function (F3I) or Interface of an In-Service Configuration Item (CI) The Offeror shall demonstrate past performance with controlling the modification of an in-service configuration item. The Offeror shall address past performance modifying configuration items and the configuration control used (SOO Section 3.1.14).

Sub-Element 1l: Hardware Technology Refresh The Offeror shall demonstrate past performance with a hardware technology refresh during an IS’ life-cycle. The Offeror shall address past performance replacing hardware components (SOO Section 3.1.15).

Sub-Element 1m: Software Modernization The Offeror shall demonstrate past performance modernizing a legacy IS during its life-cycle to include converting or rewriting the code to modern computer programming language, software libraries and protocols and porting the IS to a different hardware platform (SOO Section 3.1.16).

Sub-Element 1n: Decommission Planning and Execution The Offeror shall demonstrate past performance decommissioning a legacy IS. The Offeror shall address past performance archiving software and documentation libraries, archiving or migrating data from the old system to the receiving/target system, and preserving the system security and access rights of the legacy system to include the legacy system’s security overview (SOO Section 3.1.17).

4.3.1.2 Sub-factor 2: Cybersecurity

Offeror shall demonstrate past performance as it relates to the following requirements identified in SOO:

Solutions used that supported Risk Management Framework (RMF) Cybersecurity Objectives (Confidentiality, Integrity, and Availability) (SOO Sections 3.1.10.1, 3.1.10.2, and 3.1.10.3).

Methodologies used to implement the basic information security concepts for Identity Assurance (Authentication, Authorization, and Accountability (nonrepudiation)) (SOO Sections 3.1.10.4, 3.1.10.5, and 3.1.10.6).

4.3.1.3 Sub-factor 3: Information Technology Business Analysis Offeror shall describe past performance as it relates to the requirements identified in the

SOO:

IT Business analysis and Functional Business Area Expertise (FBAE) for business process areas to include, but not limited to, contracting, finance, medical, logistics, personnel, communications, transportation, civil engineering, munitions, infrastructure and operations (SOO Section 3.2.2). The Offeror shall delineate the specific business area(s) for which it possesses experience.

Service desk, field and technical support to include access management, event management, incident management, problem management, and request fulfillment (SOO Section 3.2.3).

4.4 Past Performance Quality

It is the Offeror’s responsibility to ensure the Government receives verifiable information to evaluate the quality of the past performance submitted in each PPN. Offerors shall either submit a copy of the CPAR IAW 4.4.1 below or ensure a completed Past Performance Questionnaire (PPQ) is provided IAW 4.4.2 below. If the Offeror submits a CPAR with their proposal, a PPQ is not required for the same contract reference.

4.4.1 Contractor’s Performance Assessment Report (CPAR)

If the contract references (CPARs) submitted are not those of the approved JV, then references (CPARs) submitted shall represent work performed by each individual member comprising the JV. For JV, the CPARs must match the name(s) of those members in the approved JVA.

Additionally, the CPAR shall also be inclusive of the same period of performance stated in the PPN. All CPARs shall be submitted IAW paragrapgh 1.2.5 of the ITO.

4.4.2 Past Performance Questionnaire (PPQ)

If a CPAR cannot be provided, the Offeror may use the PPQ to verify the quality of the past performance submitted. The Offeror shall complete the Project Identification information in Questionnaire Section I.A and the “Customer Information name” identified in Questionnaire Section I.B. The Offeror shall request its customer, the Assessor, return the completed Questionnaire to the Points of Contact (POCs) listed in Questionnaire Section III by the date of proposal submission.

The PPQ shall be completed and signed by a person with cognizance over the project for the period of performance (i.e., Program Manager, Contract Representative). PPQs shall be sent directly to the Government by the Assessor. The PPQ can be found at Section J, Attachment 6 of this solicitation.

5.0 Volume IV Contract Documentation

5.1 General Information

Each offeror shall submit a contract documentation volume with its proposal.

The Offeror shall make a clear statement, in Volume IV’s Cover Letter, that the proposal is valid for a period of not less than 365 days from receipt. This period may be extended upon agreement from the Offeror.

All proposing offerors shall be certified as a small business at the time of proposal submission.

Offerors are advised to NOT submit any cost/price data and labor category information with their proposal. Any proposals that are received that contains this information will be considered non-compliant and removed from the competition.

5.2 Volume Organization

Volume IV shall contain the information in tabbed sections IAW the following general outline:

(1) Assumptions and Exceptions

(2) Representations and Certifications

(3) Mentor Protégé Agreements (MPAs)

(4) PCO Joint Venture Approval Notice

(5) Approved Joint Venture Agreement (JVAs)

(6) JVAs for Technical and Past Performance References

5.2.1 Assumptions and Exceptions

Offerors shall provide a list of assumptions and/or exceptions made in developing the response to this RFP. Please be advised that any assumptions made that are not in compliance with the RFP may render an offeror’s proposal unawardable.

5.2.2 Representations and Certifications

IAW FAR 52.204-07—System for Award Management and…