FA8771-17-R-1000_Amendment_01.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

17 October 2017

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

FA8771-17-R-1000

Amendment 01

The following attachments to the SBEAS RFP have been amended:

1. Statement of Objectives (SOO)

2. Instructions to Offerors (ITO)

3. Evaluation Criteria

4. Cross Reference Matrix (CRM)

5. Self-Scoring Worksheet (SSWS)

6. Definition of Terms

The attachments contain lines next to each section that has been updated. The Government will NOT be providing a summary of changes or releasing any other documents in an editable format with the exception of the CRM and SSWS.

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

Question: We assume that the project summary in the PPQ must include all factors and sub-factors that the offeror is claiming in its Past Performance Narrative. Is this assumption correct? If this is not the case, offerors could claim credit for experience for past performance sub-factors in the Past Performance Narrative and the Government would have no validation from the PPQ that this work had actually been performed.

The Government’s Initial Response: Yes, this is correct.

The Government’s Revised Response: The project summary in the PPQ should speak to the overall scope of the contract that is being used and not the specific criteria listed for the factor/sub-factors. The PPQs as well as the CPARs are for the evaluation of quality as it pertains to the contract reference as a whole.

Offerors who have submitted PPQs will not penalized as this information is NOT required to be provided in the PPQs and they DO NOT need to resubmit PPQs with this information.

The Government would like to clarify the information posted in the general statement as it relates to the small business certification. Offerors are required to be certified as a small business at the time of initial proposal submission ONLY.

The Government would like to clarify that the PPN and TN Submission Template posted on 13 October 2017 is NOT required to be submitted. The document was provided as a result of the questions received in an effort to help offerors structure their PPNs and TNs for proposal submission. Offerors are still required to be in compliance with the ITO, specifically relating to how contract references should be combined in accordance with (IAW) section 1.2.6. The example provided in the template was for a single award IDIQ/BPA contract ONLY. Offerors are not allowed to combine task orders under a multiple award IDIQ contract.

The proposal due date has been extended to 2 November 2017 10:00 a.m. Central Daylight Time (CDT). 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-17T09:34:02-0500

BROWN.SHANEKA.K.1258521273

Section J Attachment 1

Statement of Objectives

STATEMENT OF OBJECTIVES (SOO)

FOR

SMALL BUSINESS ENTERPRISE APPLICATION SOLUTIONS (SBEAS)

1. Purpose

The purpose of this Indefinite Delivery/Indefinite Quantity (IDIQ) Contract is to provide a vehicle for customers to access a wide range of Information Technology (IT) Network Centric services and solutions that support the IT lifecycle. While the SBEAS contract is mandatory use for the Air

Force, this contract vehicle may be used by all other agencies that support an Air Force requirement.

2. Scope

The scope of this IDIQ includes the comprehensive suite of IT services and IT solutions to support

IT systems and software development in a variety of environments and infrastructures. Additional IT services include, but are not limited to documentation, operations, deployment, cybersecurity, configuration management, training, commercial off-the-shelf (COTS) product management and utilization, technology refresh, data and information services, information display services and business analysis for IT programs.

3. Technical Objectives

The objectives identified within this SOO are described in general terms. Each task order will address specific requirements, project scheduling, and other related performance criteria, as applicable. In accordance with AF and DoD standards referenced in section 8, Contractors shall provide IT solutions that operate in approved Network Centric enterprise environments and exploit approved infrastructures.

3.1 Life-Cycle Software Services

Life-cycle Software Services include but are not limited to:

3.1.1 Project management

3.1.2 Systems engineering, including technical and technical management processes

3.1.3 System architecture and design documentation

3.1.4 Technical solution design, creation, and implementation from a defined business process, user stories, or business use cases

3.1.5 Software development using various methodologies to include Agile, Prototype, Dev

Ops, Rapid, Dynamic, Lean, or Waterfall. Agile is the preferred methodology

3.1.6 Information/web services development and information/web services testing to include using Service-Oriented Architectures

3.1.7 Mobile or other Internet of Things (IoT) devices applications life-cycle software services

3.1.8 Information Display Solutions and Services, including but not limited to, mashups, dashboards, portals, and rich internet applications (RIA)

3.1.9 Database development or conversion

3.1.10 Incorporation of and compliance with Cybersecurity objectives and information security concepts to include Risk Management Framework (RMF) and DoD Information

Assurance Certification and Accreditation Process (DIACAP)(DoD 8510.01)

RMF Cybersecurity Objectives

3.1.10.1 Confidentiality

3.1.10.2 Integrity

3.1.10.3 Availability

Basic information security concepts

3.1.10.4 Authentication

3.1.10.5 Authorization

3.1.10.6 Accountability (non-repudiation)

3.1.11 Build, testing, implementation and integration

3.1.12 Data or system migration

3.1.13 Administration of applications, systems, databases and interfaces to include system performance monitoring, tuning, provisioning and configuration management

3.1.14 Modifications to the Form, Fit, Function, or Interface (F3I) of an in-service, configuration-managed or produced Configuration Item (CI)

3.1.15 Technology refresh, software or hardware upgrades

3.1.16 Software modernization or re-engineering

3.1.17 Decommission planning and execution

3.2 Supporting IT Services

Supporting IT services objectives include, but are not limited to:

3.2.1 Data and Information Services

3.2.2 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

3.2.3 Service desk, field and technical support to include access management, event management, incident management, problem management, and request fulfillment

3.2.4 Customer and user training

3.2.5 Creating and updating system documentation

3.3 Supporting Systems Within Various Computing Environments

Provide development and supporting IT services and solutions within environments including:

3.3.1 AF-owned

3.3.2 DISA-operated

3.3.3 Commercial, Non-commercial and Hybrid Cloud environments

3.3.4 Mobile devices

3.3.5 Other DoD-approved common operating environments

3.4 General Objectives

Other general requirements include:

3.4.1 Comply with DoD policy that Cybersecurity requirements shall be identified and included in the design, acquisition, installation, operation, upgrade, or replacement of all DoD information systems. This includes systems and processes developed within the Defense Acquisition System (DAS); systems and processes developed at private expense; outsourced business processes supported by private sector information systems; and outsourced information technologies. IAW DoD 8570.01-

M [Information Assurance (IA) Workforce Improvement Program (WIP)] and AFI

17-1303 [Cybersecurity Workforce Improvement Program (WIP)], all personnel assigned to perform cybersecurity function(s) are required to carry an approved certification for their particular job classification. Specific cybersecurity requirements will be stated in the Task Order(s). (CDRL A007)

Reference National Institute of Standards and Technology (NIST) Special

Publications 800-37, 800-53, 800-53A Rev 4 and Committee on National

Security Systems Instructions (CNSSI) 1253 in relation to the Risk

Management Framework (RMF) standards

3.4.2 Apply disciplined/best practices for systems engineering process optimizations

Each contract holder is required, at the time of proposal submission, to be appraised at Level 2 (at a minimum) for either Capability Maturity Model

Integration (CMMI) for Development or CMMI for Services using the Software

Engineering Institute’s (SEI) Standard CMMI Appraisal Method for Process

Improvement (SCAMPI) (Method A). For approved Joint Ventures, at least 50% of the venturers are required to hold the appraisal level if the Joint Venture itself does not

CMMI appraisal level held at contract award shall be maintained or increased throughout the life of the contract. Each contract holder shall provide, on an annual basis, the appropriate documentation which verifies the appraisal level held at contract award has been maintained or increased (CDRL A006)

3.4.3 Generate necessary design and implementation artifacts that will support lifecycle management of each solution developed or service provided

3.4.4 Develop and provide all data in accordance with the data right clauses and as identified in each task order

3.4.5 Use only Government-off-the-Shelf (GOTS) tools, approved Commercial-off-the-

Shelf (COTS) tools or approved Free and Open Source Software (FOSS) for systems design and development, or incorporation into system solutions, in accordance with AF and DoD Standards

3.4.6 Support the Government in demonstrating audit readiness by responding to agency audits, inspections, and product assessments (i.e., monitoring/inspection/auditing of

IT regulated activities to ensure compliance)

3.4.7 Supply work breakdown structure (WBS), integrated master schedule (IMS), and transition plans as defined at the task order level

3.5 Program Management Objectives

At time of contract kickoff, identify a Program Manager (PM) who shall be the primary representative responsible for all work awarded under this contract, participating in Program Management Reviews (PMR) and ensuring all standards and requirements referenced herein are adhered to. The SBEAS Program conducts a maximum of one (1) mandatory PMR per fiscal year.

The PMR will be conducted via a virtual webinar or teleconference. Contractors are free to travel to the Government’s facility to conduct the PMR however, travel expenses will not be reimbursed as this method of conducting the PMR is not required. Contractors shall provide briefing materials for the PMR. Contractors shall also provide a capability description for the Government’s use in accordance with CDRL A003.

3.5.1 Ordering Authority

The SBEAS Program will utilize a control number process for all requests for proposal (RFP) or request for quote (RFQ) on this contract. RFPs and RFQs are only valid if they include a control number. No decentralized orders shall be placed by DoD and other Federal Agencies without an assigned SBEAS control number.

3.5.2 Task Order Management and Status Reporting

Establish and maintain a documented set of disciplined, mature, and continuously improving processes for administering all task order efforts. All information for overall task order reporting will be submitted via a contract data requirements list (CDRL). This monthly CDRL will include but not be limited to; new task orders, modifications to existing task orders, RFQ submissions, order status updates, service descriptions, payment amounts/dates by CLIN, and DFAS invoices. Additionally, this CDRL also requires a copy of each award and modification be sent to the Government PMO as soon as received but no later than with CDRL A001.

3.5.3 Contractor Manpower Reporting

Comply with Section 2330a of title 10, United States Code (10 USC 2330a), requiring an annual inventory of contracts for services performed during the prior fiscal year by completing the Air Force’s on-line contractor manpower reporting application (CMRA).

The inventory must include the number of contractor employees and associated cost data collected from all SBEAS task orders during that period. An email copy of the CMRA submittal shall be provided to the Government. (CDRL A005)

3.5.4 Earned Value Management (EVM)

EVM may be required at the task order level. If required, each individual task order will provide specific requirements for EVM.

4. Other Considerations

4.1 Security

The IDIQ will support the following levels of security: Unclassified; Unclassified, But Sensitive;

Secret (S); Secret Sensitive Compartmented Information (S/SCI); Top Secret (TS); and Top Secret

Sensitive Compartmented Information (TS/SCI).

Task orders may require personnel security clearances up to and including Top Secret and may require all employees to be United States citizens. The security clearance requirements will depend on the security level requirements at the task order level. The task orders may also require access to sensitive compartmented information (SCI) for which SCI eligibility will be required.

Individuals performing work under task orders shall comply with applicable program security requirements as stated in the task order. Contractor personnel shall be required to have the appropriate level of investigation and/or security clearance for each agency and information system as applicable at the task order level prior to performing services under the task order. The cost of the associated investigations for contractors will be in accordance with governmental directives at the time of the contract award.

All Contractors located on military installations shall also comply with Operations Security

(OPSEC) requirements as set forth in DoD Directive 5205.02, Operations Security Program and

AFI 10-701, Operations Security. In accordance with DoD Manual 5200.02, Procedures for the

DoD Personnel Security Program (PSP) and DoD Instruction 1000.13, DoD military, civilian, consultants and contractor personnel using unclassified automated information systems, including e-mail, shall have, at a minimum, a completed favorable T1, equivalent or higher background investigation.

4.2 Facility Clearance Level (FCL)

An FCL is not mandatory at the IDIQ level; however task orders may require an FCL up to and including Top Secret. The requirement for an FCL will be specified at the task order level.

4.3 North American Industry Classification System (NAICS)

The NAICS code for this acquisition is 541511: Custom Computer Programming Services. This

U.S. industry comprises establishments primarily engaged in writing, modifying, testing, and supporting software to meet the needs of a particular customer. This NAICS Code is revenue based at $27.5M annually. All Contractors shall be certified as a small business under this NAICS code prior to contract awardat the time of initial proposal submission.

4.4 Limitation of Subcontracting

In accordance with FAR 52.219-14, Limitations on Subcontracting and 13 CFR 125.6(e), in performance of services awarded, at least 50% of the cost of contract performance incurred for personnel shall be expended by the SBEAS Prime Contractor. It is the Government’s intent to invoke this clause at the task order level.

In an effort to monitor and strictly enforce this requirement, the Contractor shall specifically identify the total prime and subcontracted labor dollars combined and the total labor dollars subcontracted separately in each invoice submitted under SBEAS task orders. (CDRL A002)

4.5 Small Business Recertification

Each contract holder under this IDIQ shall recertify under the 541511 NAICS Code used for this contract award. In accordance with 13 CFR 121.404, recertification shall be completed no more than 120 days priorto the end of the base period and no more than 120 days prior to exercising any option thereafter. Since SBEAS only has one option period, recertification will only take place at the end of the Base period. Any Contractor who cannot recertify as a small business, will be removed from the contract. However, if a Contractor has been awarded task orders and the task order period of performance has not ended, the Government will exercise the

Contractor’s remaining option period for the purpose of task order performance completion only.

The Contractor shall not, however, be awarded any new contract actions under the contract and the contract will be terminated for convenience once task order performance is completed.

In accordance with 13 CFR 121.404 the following applies:

Within 30 days of an approved contract novation, a contractor must recertify its small business size status to the procuring agency, or inform the procuring agency that it is other than small.

o Note: If a company or JV has recertified within the 30 days of an approved contract novation, and it falls within the 120 day window for all companies to recertify as a small business, the requirement has been satisfied; if it does not, a recertification would be required.

In the case of a merger, sale, or acquisition, where contract novation is not required, the contractor must, within 30 days of the transaction becoming final, recertify its small business size status to the procuring agency, or inform the procuring agency that it is other than small.

Recertification is required:

o When a concern, or an affiliate of the concern, acquires or is acquired by another concern;

o From both the acquired concern and the acquiring concern if each has been awarded a contract as a small business; and o From a joint venture when an acquired concern, acquiring concern, or merged concern is a participant in a joint venture that has been awarded a contract or order as a small business.

o If the merger, sale or acquisition occurs after offer but prior to award, the offeror must recertify its size to the contracting officer prior to award.

In addition to the requirements set forth in 13 CFR 121.404, the following requirements also apply:

Once contract award has been made to a joint venture (JV), no new members, participants or partners shall be added to the JV.

If a member, participant or partner of a JV is acquired or merged, the JV shall submit an addendum to the approved Joint Venture Agreement (JVA) for this contract and each member, participant or partner shall recertify as a small business.

o In the case of a mentor protégé JV, the JV shall submit, in addition to the SBEAS

JVA addendum, a new Mentor Protégé Agreement (MPA) approved by Small

Business Administration (SBA).

o The JV shall also provide the appropriate documentation which verifies that at least

50% of the JV still meets the minimum requirement to be appraised at Level 2 (at a minimum) for either Capability Maturity Model Integration (CMMI) for

Development or CMMI for Services using the SEI SCAMPI (Method A) and shall identify which participant(s) of the JV holds the required appraisal.

In the case where a JV is dissolved, the contract held with the JV will be terminated for convenience.

For JVs that are formed between two members, if one of the members leaves the JV, the contract held will be terminated for convenience.

For JVs comprised of more than two members, if one of the members leaves the JV, the JV shall submit an addendum to its JVA for SBEAS and also provide the appropriate documentation which verifies that at least 50% of the JV still meets the minimum requirement to be appraised at Level 2 (at a minimum) for either Capability Maturity Model

Integration (CMMI) for Development or CMMI for Services using the SEI SCAMPI

(Method A) and shall identify which participant(s) of the JV holds the required appraisal. If this information cannot be verified, the JV will be terminated for convenience. (CDRL

A004, A006)

4.6 On Ramp

The Government intends to establish an awardee pool under the SBEAS effort by competitively awarding multiple-award IDIQ contracts. The Government reserves the right to reopen competition at any time during the term of the contract to add additional Contractors to the original pool of awardees.

When reopening competition, the Government will advertise via Federal Business Opportunities

(FedBizOpps) and conduct a total small business set-aside to bring the awardee pool up to a level to ensure adequate competition . Any awardee already in the awardee pool will not recompete for an awardee pool position. The On-Ramp competitions will use the same evaluation methodology and documentation updated to reflect changes in regulatory provisions as well ascommercial technologies, practices and certification standards.

Once a new awardee is selected, that awardee will be included in the awardee pool and will compete for future task orders. The ordering period for new Contractors being added to the initial awardee pool will coincide with initial awardees ordering period but shall not extend the overall term of the contract beyond the original ordering period nor shall it re-establish the contract base period.

4.7 Places of Performance

It is anticipated that there may be task orders under this contract for work within and outside of the

United States. The specific place of performance will be identified at the task order level. For the purposes of this IDIQ, Contiguous United States (CONUS) means the 48 contiguous States and the

District of Columbia, and OCONUS means outside of the contiguous United States to also include the Non-Foreign OCONUS Area (the states of Alaska and Hawaii, the Commonwealths of Puerto

Rico and the Northern Mariana Islands, Guam, and U.S. territories and possessions).

4.8 Other Direct Costs (ODCs)

ODCs will be addressed at the task order level and will be paid on a reimbursable basis. G&A or overhead cost are permissible and will be negotiated at the task order level.

4.9 Travel

Travel requirements will be addressed at the task order level. Costs associated with Contractor travel shall be in accordance with FAR Part 31.205-46, Travel Costs. Travel will be reimbursed on a cost reimbursable basis. G&A or overhead cost are permissible and will be negotiated at the task order level. No profit will be paid.

4.10 Organizational Conflicts of Interest (OCI)

FAR 9.5 Organizational and Consultant Conflicts of Interest, prescribes responsibilities, general rules, and procedures for identifying, evaluating, and resolving organizational conflicts of interest;

provides examples to assist contracting officers in applying these rules and procedures to individual contracting situations; and implements section 8141 of the 1989 Department of Defense

Appropriation Act, Pub. L. 100-463, 102 Stat. 2270-47 (1988).

The general rules in FAR 9.505-1 through 9.505-4 prescribe limitations on contracting as the means of avoiding, neutralizing, or mitigating organizational conflicts of interest that might otherwise exist in the stated situations. Conflicts may arise in situations not expressly covered in

FAR section 9.505 or in FAR section 9.508. Each individual contracting situation should be examined on the basis of its particular facts and the nature of the proposed contract. The exercise of common sense, good judgment, and sound discretion is required in both the decision on whether a significant potential conflict exists and, if it does, the development of an appropriate means for resolving it.

In the event that a task order requires activity that would create an actual or potential conflict of interest, the procedures in FAR 9.506 Procedures, are applicable to resolving such conflict.

5. Contract Period

The contract period for SBEAS is 10 years from date of contract award. The contract period is defined as the time period the overarching IDIQ contract is active.

5.1 Ordering Period

The ordering period for SBEAS is 10 years. The ordering period is defined as the time period that http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/09.htm#P665_119008 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/09.htm#P686_123711 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/09.htm#P659_117582 http://farsite.hill.af.mil/reghtml/regs/far2afmcfars/fardfars/far/09.htm#P717_129579 task orders can be issued under this contract. The ordering period is broken out as follows: a five

(5) year base period and one 5-year option period, if exercised.

5.2 Period of Performance (PoP)

The SBEAS contract does not have a period of performance as performance occurs at the task order level. Each ordering agency shall specify the PoP for each task order awarded under this contract. All task orders must be solicited and awarded prior to the SBEAS ordering period expiring. The PoP under any task order issued cannot exceed five years AND cannot extend more than five years beyond the end of the ordering period.

5.3 Continuation of Task Order Performance

In accordance with FAR clause 52.216-22—Indefinite Quantity (Oct 1995), task order performance is allowed to continue up to 60 months after the ordering period and contract period has expired.

The contract shall govern the Contractor’s and Government’s rights and obligations with respect to that order to the same extent as if the order were completed during the contract’s effective period;

provided, that the Contractor shall not be required to make any deliveries under this contract after

60 months (5 years) of the ordering period and contract period expiring. The terms and conditions of the base contract remain valid and in full force and effect for the performance of any task order, including any exercise of options contained on the task order, during the contract's period of performance beyond the contract's effective period for placing orders.

6. Contract Maximum and Contract Minimum Guarantee

The maximum amount of this contract shall not exceed $13,367,559,547.00, which represents the maximum value of business opportunity available under the SBEAS contract. The maximum ceiling amount of $13,367,559,547.00 will be spread amongst all IDIQ contract holders via competition.

In accordance with AFFARS MP5316.504(a)(2), an obligation shall be recorded for the minimum for this contract. The minimum amount guaranteed to each contract holder is $5,000.00. If this amount has not been satisfied through task order competition, at the end of the base period, all awardees that have not been awarded a task order for the minimum guarantee amount will be issued a task order to satisfy this requirement. The exercise of the option periods shall not reestablish contract minimum amounts.

7. Data Deliverables

The Contractor shall provide reports identified below throughout the period of performance and while task order performance is ongoing:

1. CDRL A001: Task Order Status Report (TOSR): DI-MGMT-81991, tailored

2. CDRL A002: Limitation of Subcontracting: No Reference

3. CDRL A003: Vendor Capabilities Description: No Reference

4. CDRL A004: Mentor-Protégé Agreement (MPA): No Reference

5. CDRL A005: Contractor Manpower Reporting: No Reference

6. CDRL A006: CMMI Appraisal Documentation: No Reference

7. CDRL A007: Contractors Roster: DI-MGMT-81596, tailored

8. Specifications, Standards and Policies

The following certifications, specifications, standards, policies and procedures represent documents and standards that apply to life-cycle management services and may be required on individual task order contracts. Additionally, individual task orders may impose additional standards than those specified below.

In performing any task order under this IDIQ, the contractor shall ensure that services, solutions and products meet the standards identified in AF Standards of Excellence located at:

http://www.netcents.af.mil/Portals/30/documents/NETCENTS-

2/AppSrvsDocuments/Application%20Services%20Standards.pdf

The most current version of the document at the time of task order issuance will take precedence.

http://www.netcents.af.mil/Portals/30/documents/NETCENTS-2/AppSrvsDocuments/Application%20Services%20Standards.pdf http://www.netcents.af.mil/Portals/30/documents/NETCENTS-2/AppSrvsDocuments/Application%20Services%20Standards.pdf

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. 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 CANNOT be used as contracts are awarded to the JV not the individual companies that make up the JV. 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

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.

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%23T2101 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%23b3104

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 been posted to the website for this solicitation.

https://www.fbo.gov/

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 printed double-sided. The font size shall be no less than Times New Roman ten (10) point. Use 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%23T2101 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%23b3104 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%23b522151 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%23b31044

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 (i.e., PPQ, CRM, Self-scoring Worksheet). 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 a MS Word document (2013 or earlier), detailing 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.