2nd_Draft_Request_for_Proposal_SBEAS_June_2017.pdf

Proper Format for Second Draft RFP Questions Submission

Submit all questions in an Excel Spreadsheet with the following Column Headings (only):

Document Page / Section / Table Questions

SOO Pg. 1 Section 3.1.1 What is Project Management?

Section L Pg. 1 Section 1.0 How many proposals may I submit?

Attachment 1

FA8771-17-R-1000

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 specifically established within the Business Enterprise System (BES) Directorate, 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, 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. Specific cybersecurity requirements will be stated in the Task Order(s)

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. 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 held in a Government facility at a location that might require overnight travel. A PMR may alternatively be conducted via a virtual webinar when resources for facilities or travel are not available to the Government. Contractors shall provide briefing materials for the PMR as well as a capability description for the Government’s use. (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 require 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. All costs associated with obtaining/possessing such security clearances are the responsibility of the

Contractor.

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 5200.2-R, Personnel Security

Program (Jan 87), DoD military, civilian, consultants and contractor personnel using unclassified automated information systems, including e-mail, shall have, at a minimum, a completed favorable National Agency Check plus Written Inquiries (NACI).

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. All Contractors shall be certified as a small business under this NAICS code prior to contract award.

4.4 Limitation of Subcontracting

In accordance with FAR 52.219-14, Limitations on Subcontracting, in performance of services awarded, at least 50% of the cost of task order performance incurred for personnel shall be expended by the SBEAS Prime Contractor.

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 (CDRL A004, A006)

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, recertifications shall be completed 120 days before the end of the base period and every year thereafter. 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 periods 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.

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 CMMI appraised in

Development or Services 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 CMMI appraised in Development or Services 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.

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 competition (utilizing the same evaluation criteria as the initial SBEAS solicitation) to bring the awardee pool up to the initial awardee pool. 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 and commercial practices and certifications) as the original competition.

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, inclusive of options, but shall not extend the overall term of the contract beyond the original ordering period nor shall it re-establish the contract base period, inclusive of options.

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. ODCs will be paid on a reimbursable basis. No profit, fee, G&A, or overhead will be paid.

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. No higher than 10% of the travel cost will be paid in fee, G&A, or overhead. 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. Period of Performance (PoP)/Ordering Period

5.1 Period of Performance

The PoP for the SBEAS contract is defined as the time period the overarching IDIQ is available for performance to continue for all the task orders issued under the contract. The SBEAS contract PoP is a total of 10 years from date of contract award. The PoP is broken out as follows: a five (5) year base period and one 5-year option period, if exercised.

5.2 Ordering Period

The ordering period for this contract is 10 years. The ordering period for the SBEAS contract is defined as the time period that a task order award can be issued under this contract. Each ordering agency shall specify the PoP for each task order awarded under this contract. Task orders must be solicited and awarded prior to the SBEAS ordering period expiring and may extend up to 5 years after the SBEAS ordering period expires.

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.

FAR clause 52.216-22 can be inserted into task orders and section (d) states, an order issued during the effective period of this contract and not completed within that period shall be completed by the Contractor within the time specified in the order. 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 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 and contract period expiring.

6. 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): No reference

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. Specifications, Standards and Policies

Individual task orders may impose additional standards to those required at the contract level.

A list of certifications, specifications, standards, policies and procedures that may be placed on individual task orders may be found under the AF Standards of Excellence header 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

Attachment 2

Section L Instructions to Offerors

1.0 General Instructions to Offerors (ITO)

(a) Only one (1) proposal may be submitted by each qualified offeror in response to this requirement. A qualified offeror (Offeror) is one who is determined to be a responsible source, submits a proposal that conforms to the requirements of this solicitation and is one for whom the

Procuring Contracting Officer (PCO) has no reason to believe would likely offer other than fair and reasonable pricing at the task order level. 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 for Award. 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, IAW FAR 15.208, if they are not received by the date specified in this ITO.

(e) In accordance with 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 teaming arrangements 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) and/or joint venture. Once contract award has been made, all awardees are allowed to form teaming agreements/arrangements, as necessary, for solicitations at the task order level.

Proposal Submission

Submission of Hard Copy Proposal Volumes

One hard copy of the proposal shall be clearly marked, addressed, and mailed or hand-carried to the Procuring Contracting Officer (PCO) at the below address no later than TBD (CST):

SHANEKA K. BROWN, PCO, SBEAS

AFLCMC HIK

501 EAST MOORE DR.

BLDG 884, SUITE 1400M

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

TBD (CST). With the exception of the information submitted via the PPI Tool, the content, format and page size of electronic copies must be identical to the hard copies. The electronic copy of the proposal shall be submitted in a format readable by Microsoft (MS) Office suite of programs dated no higher than 2013.

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.

Proposal Validity

The Offeror shall make a clear statement in each proposal volume that the proposal is valid for a period of not less than 365 days from receipt.

1.1 General Information

Point of Contact Ms. Shaneka K. Brown, PCO - SBEAS, is the 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.

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 https://safe.amrdec.army.mil/safe/Welcome.aspx mailto:AFLCMC.BES.SB_IDIQ_RFP@us.af 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 in accordance with 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/.

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 will 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:

https://www.fbo.gov/ 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

Table 1.2 - Proposal Organization

VOLUME ITO Paragraph

Number

VOLUME TITLE COPIES PAGE LIMIT

I 2.0 CMMI Development or

Services Appraisal

1 Original Hard Copy and 1 Electronic

Copy

No Page

Limit

II 3.0 Technical Experience 1 Original Hard Copy and 1 Electronic

Copy

20 Pages

Total

III 4.0 Past Performance 1 Original Hard

Copy,1 Electronic

Copy AND 1

Electronic Copy of

Past Performance

Information Tool

(PPI) Database

25 Pages

Total

IV 5.0 Contract

Documentation

1 Original Hard

Copy and 1

Electronic Copy

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, Government Facility Clearance Letter, Past Performance Information (PPI) Tool, Contractor Performance Assessment Reports (CPAR), Past Performance Questionnaires (PPQ), Tabs and Glossaries of abbreviations and acronyms.

1.2.2 Page Size and Format

Page size shall be 8.5 x 11 inches. Foldouts are not permitted. Pages shall be single-spaced.

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 shall be numbered sequentially by volume. For tables, charts, graphs and figures, the font shall be no smaller than eight (8) points. Please note that line spacing, font size, and other restrictions do not apply to the pages that are generated by the PPI Tool.

1.2.3 Cross-Reference Matrix (CRM)

Offeror shall complete the CRM at Section J, Attachment 4 of this solicitation. The Offeror shall include the same copy of the CRM in both the Technical (Volume II) and Past

Performance (Volume III) volumes. The Offeror’s CRM shall show traceability between the

Offeror’s contract references used for both Volume II and Volume III. Specifically, the

Offeror’s CRM shall show which contract references are used to satisfy each technical element and each past performance sub-factor. Finally, 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 IAW section 4.3 below. When completing the CRM to be submitted with each volume, please refer to the instructions within the CRM attachment.

1.2.4 Glossary of Abbreviations and Acronyms

Each volume 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 proposal. Offerors shall only define terms that are not already defined and included in Attachment 8, Definition of Terms.

1.2.5 Binding and Labeling

Proposals shall be bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. Volumes I and II shall be submitted together in one (1) binder and the remaining volumes shall be submitted in separate binders. A cover sheet shall be included in each volume identifying the volume number, title, solicitation identification, and the

Offeror's name. The same identifying data shall be placed on the spine of each binder. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with 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. A recent contract is defined as ongoing or completed work that is no more than three (3) years from the date of this solicitation.

Multiple-award IDIQ: Multiple award IDIQ contract numbers are not allowed to be used as a reference however, individual task order numbers issued against the multiple-award

IDIQ are allowed. 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 in order to verify and validate that the IDIQ being referenced is in fact a single award IDIQ contract. Task orders issued against a single-award IDIQ can be combined and counted as one contract reference to address the criteria however, each task order number shall be identified.

Blanket Purchase Agreement (BPA): 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.

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

2.0 Volume I – CMMI Development or Services Appraisal

The Offeror shall provide valid proof of a Level 2 (at a minimum) appraisal in Capability

Maturity Model Integration (CMMI) Development or Services.

The Offeror shall submit a copy of its Appraisal Disclosure Statement (ADS) along with its

CMMI logo that identifies the company's current appraisal results from a CMMI Institute certified lead appraiser. The ADS should also confirm the date of appraisal which validates it is current. This appraisal must be held at the Offeror’s organizational level, not for an individual person.

If the Offeror’s CMMI appraisal expires prior to contract award, the PCO will notify the Offeror and the Offeror shall submit a copy of its reappraisal results, which shall meet the same requirements listed above. The reappraisal shall be submitted 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. For example, if a JV includes three members, two must provide valid proof of appraisal; if the JV includes five members, three must provide valid proof of appraisal.

In the case of an odd number of JV members, Offerors must round “up” to the next even number to determine the 50% requirement.

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). For Offerors proposing as a JV whose JV agreement was approved, if contract references submitted are not those of the approved JV, then references submitted shall represent work performed by each individual member comprising the

JV.

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 in Section J, Attachment 6 of this solicitation. The worksheet shall be submitted in no higher than Microsoft Excel 2013.

The Government will not accept any worksheets that have been password protected or “locked.”

A .pdf document will not satisfy this requirement. A locked worksheet shall be considered to be non-compliant with the instructions of the solicitation and therefore, the worksheet will not be evaluated.

Complete the Worksheet using the following instructions:

1. Enter the Offeror’s name in Row 4 of the Self-Scoring Worksheet.

2. In Column C, the Offeror shall check the box if points are being claimed for that technical element and if the technical narrative has been submitted to support the claimed points. Also the Offeror shall check the box if points are being claimed for the

FCL. The worksheet will auto populate the Offeror’s score and running total at the bottom of the worksheet. Offerors shall use the technical element criteria in section

3.1.3 below, the technical experience evaluation criteria in Section J, Attachment 3

(Section M), and the Definition of Terms in Section J, Attachment 8 to develop a clear understanding of the technical elements.

3. In Column F, Offerors shall enter the page number and technical narrative section corresponding with the chosen technical element. Example: If the Offeror’s technical narrative is referencing the Cybersecurity technical element of the self-scoring worksheet, the Offeror shall enter Page 3, Section 2 into column F (Technical

Narrative Reference). If multiple technical narratives are used, the Offeror shall separate each with a semicolon.

4. Offerors shall only enter responses in Columns C and F. Offerors shall not alter columns A, B, and D. Column E will auto-populate points and Column G is for

Government use only.

Offerors shall ensure the page number and technical narrative section for each technical element identified in Column F of the self-scoring worksheet are also reflected in the CRM. If points claimed on the self-scoring worksheet cannot be verified due to missing or conflicting technical narrative references on the CRM and the self-scoring worksheet, then the technical elements where points are claimed for that specific technical narrative section will not be evaluated.

3.1.3 Technical Narrative

The technical narrative section shall describe the Offeror’s experience that supports the technical element points claimed on the self-scoring worksheet. The technical narrative section shall not exceed the maximum of 20 pages. The pages allotted can be used at the Offerors discretion; however the Offeror shall include the contract/project number (or equivalent) at the beginning of each technical narrative section.

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 between the terms.

3.2. Technical Element Criteria

Offerors shall utilize the Definition of Terms provided in Section J, Attachment 8 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 the 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 [ERPs] Software Systems) Offeror shall describe its experience in one of the following:

Implementing one (1) COTS, GOTS or FOSS ERP Package software 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 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 in the life-cycle software services of Testing, Validation and Verification 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 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 an IT supporting 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 (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. Offerors shall identify the tool with which they have experience to include, but not limited to: Fortify, Sonatype, AppScan.

Sub-Element 5b…