DRAFT RFP Attachment 1 - Addendum to 52_212-1.pdf

FA701424RXXXX

DEPARTMENT OF THE AIR FORCE STRATEGIC TRANSFORMATION SUPPORT (DAFSTS) II

ADDENDUM TO FAR 52.212-1 INSTRUCTIONS TO OFFERORS – COMMERCIAL ITEMS

ATTACHMENT 1

1.0 Contract:

This requirement is a competitive full and open acquisition. The Government intends to award a Firm

Fixed Price (FFP) multiple-award indefinite delivery/indefinite quantity (IDIQ) contract with a five (5) year ordering period.

DAFSTS II will consist of two (2) Tiers within the multi-award IDIQ structure. The Government intends to award to each and all Technically Acceptable vendors that submit a proposal in Tier 1 and each and all

Technically Acceptable vendors that submit a proposal in Tier 2.

2.0. To assure timely and equitable evaluation of proposals, offerors shall comply with all instructions within section 52.212-1 Instructions to Offerors, including all solicitation submission requirements, including submission requirements within the terms and conditions and representations and certifications.

Proposals shall be submitted in accordance with 52.212-1 and addressed to the points of contact listed below;

Points of Contact (POC): Below are the only points of contact for this acquisition. All questions or concerns shall be e-mailed to the Contracting Officer (CO) and Contract Specialist (CS).

Name Email

Ms. Destinee Narak Destinee.narak@us.af.mil

Mr. Kyle Beck Kyle.Beck.5@us.af.mil

Mrs. Theresa Terry Theresa.Terry.1@us.af.mil

2.0.1 This acquisition will use a combination of oral presentations and written submissions.

2.1. Instructions to Offerors (ITO)

2.1.1 The Offerors proposal must include all data and information requested by this ITO and must be submitted in accordance with these instructions. The Offeror shall be compliant with the requirements as stated in this solicitation. In order to be eligible for award, offerors are required to meet all solicitation requirements, such as terms and conditions; representations and certifications; evaluation factor requirements; and be deemed responsible in accordance with FAR Part 9. Nonconformance with the instructions provided in this ITO will not be further evaluated. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims.

The proposal shall not simply rephrase or restate the Government's requirements but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume the Government has no prior knowledge of its facilities and experience and will base its evaluation on the information presented in the Offerors proposal. Questions related to the RFP are due to the POCs by XXXXAM ET three (3) calendar days after RFP release.

mailto:Theresa.Terry.1@us.af.mil

2.1.2 System for Award Management (SAM): Offerors will not be eligible to receive a contract award from a Department of Defense (DoD) activity unless they are registered in SAM. IAW FAR 52.204-7, An Offeror is required to be registered in SAM with an active record when submitting an offer , and shall continue to be registered until time of award, during performance, and through final payment of any contract, resulting from this solicitation. On-line registration and instructions can be accessed at https://www.sam.gov/index.html.

2.1.3 Tier Definitions. DAFSTS II consists of two (2) tiers covering differing levels of qualifications for each; separated by level of complexity value, structure and definition of problems for the applicable mission partner. The Fortune 500 list can be found at https://fortune.com/fortune500/.

2.1.3.1 Tier 1 - Corporate experience successfully performing studies, research and analysis and developing transformational strategies for Fortune 50 companies (public or privately owned) and experience advising C-suite executives and large organizations through crisis response and highly complex, undefined, unstructured problems. Has extensive experience advising and implementing a comprehensive rethinking of business models, systems, or processes and;

Corporate experience successfully assisting the Federal Government at the agency level, no lower than Major Command (or equivalent), advising senior leaders through developing transformational strategies; translating and incorporating commercial (private sector) best practices through crisis response and highly complex, undefined, and unstructured problems.

For the purpose of Tier 1, the term “highly complex, undefined, and unstructured problems” means the problems faced in this tier of effort are usually large in scale with little context or definition provided. Crisis scenarios often call for an immediate and dramatic response, usually making a step change essential. Requests usually require engagement across multiple stakeholder communities

(external but in limited cases internal to the requesting Agency), and usually have political or statutory impacts. There are potentially no existing best practices in Government to leverage. These initiatives are usually characterized by sudden, disruptive changes brought about by outside forces.

2.1.3.2 Tier 2 - Corporate experience successfully performing studies, research and analysis and developing transformational strategies and implementation plans for Fortune 1-200 (public or privately owned) companies and experience advising C-suite executives and large organizations through moderate to complex problems. Has extensive experience advising and implementing organizations through cautious progression when the risks associated with drastic changes loom large and;

Corporate experience successfully assisting the Federal Government at the agency level, no lower than Major Command (or equivalent), advising senior leaders through developing transformational strategies and implementation plans; translating and incorporating commercial

(private sector) best practices through moderate to complex problems

For the purpose of Tier 2, the term “moderate to complex problems” means the requirements of this tier are complex but are usually understood with a goal defined. The scope may involve stakeholders internal and external to the Federal Government but are usually limited to the https://www.sam.gov/index.html https://fortune.com/fortune500/ requiring organization being within the requesting Federal Agency. The challenges are usually not political and usually have no statutory impact. The coordination and collaboration effort needed to resolve the problem is challenging and usually requires incremental change to complete.

Responses in these efforts usually require a progressive evolution, emphasizing continuous improvements. These initiatives are also usually introduced in response to internal needs, but they are usually characterized by an urgent challenge to the status quo such as a sudden organizational restructuring or the introduction of a new strategic initiative.

A step or incremental-change that will fundamentally impact the enterprise, through the improvement of how organizations holistically use people, processes, technology, data, and physical infrastructure to develop capabilities to meet their mission. Transformation should achieve measurable improvements in efficiency, effectiveness and stakeholder satisfaction.

• Step change is like the sledgehammer: powerful, impactful, and capable of sweeping changes quickly.

• Incremental change is the scalpel: precise, deliberate, and resulting in gradual but consistent improvements over a more extended period.”

2.2 Proposal Submission.

Proposal submission will be completed in three (3) steps to ensure an efficient process.

◼ 2.2.1 Step 1 – Minimum “Pass/Fail” Gate - Declare Tier, Facility Clearance Validation, and SB

Subcontracting plan compliance review

2.2.1.1 Facility Clearance (FCL): Due to the clearance requirements, all prospective Prime Offerors shall possess a TOP SECRET Facility Clearance (FCL). TOP SECRET FCL is not required for the

Joint Venture (JV) itself if the Offeror is an unpopulated JV and all members of the JV possess a TOP

SECRET FCL. A JV without its own FCL will not have access to classified information and all access will solely be through the JV members with a TOP SECRET FCL. Therefore, a JV without its own

FCL is required to submit, as part of its proposal, a Security Plan/Standard Operating Procedure. The

FCL shall be approved/issued by the Defense Security Service (DSS) and FCL must be posted in

Defense Information Security System (DISS). A verifiable TOP SECRET FCL shall exist in DISS at time of proposal submission. The Government will validate the Prime Offerors/JV Members FCL based on the CAGE code provided on the completed DD254 per the instructions in paragraph 2.2.1.2.

Offerors FCL will be assessed as “compliant/noncompliant” at proposal submission. Offerors without the required TOP SECRET FCL will be deemed “noncompliant.” Offerors shall have an approved facility clearance no later than the due date shown in Table 1.

2.2.1.2 DD Form 254, Contract Security Classification Specifications: The Offeror shall complete blocks 6a – c, (and if applicable, blocks 7a – c, and 8a – c or a continuation sheet) of the DD Form 254

(RFP Attachment 3). Complete the form and submit via email with your response to Step 1 no later than the due date shown in Table 1.

2.2.1.3 Prime Offerors shall also email the Contracting POCs to declare the Tier it will propose in no later than the due date shown in Table 1. Once an Offeror has declared which Tier it will propose in that Offeror SHALL NOT change Tiers at any point during the RFP process OR after award. Prime contractors can only be primes in one Tier; shall not subcontract in the same or opposite Tier. No exceptions. Joint Ventures (JV) – shall not be a part of a JV and be a prime/sub. Must choose one. No exceptions. Complete the provided Tier declaration memo/template on the Offerors official letterhead.

If it is a Joint Venture or Teaming arrangement, the offeror shall list all active members.

2.2.1.4 All Prime Offerors (other than Prime small businesses) shall submit a Small Business

Subcontracting Plan (SBSP)as required by FAR 52.219. The plan will be reviewed by the Contracting

Officer for compliance with FAR Clause 52.219-9, Small Business Subcontracting Plan. Each Small

Business Subcontracting Plan shall, at a minimum, adhere to the minimum goal percentages below for small businesses concerns and for the specific socio-economic small business concerns. Offerors are encouraged to propose higher than the minimums listed below. No Offerors shall use $100M as the total subcontracting dollars for Small Business Subcontracting Plan purposes. The Subcontracting Plans shall be updated once the total task order award amounts exceed $100M. Note: The offerors proposed

Small Business Participation Commitment Document (SBPCD) goals shall match your Small Business

Subcontracting Plan goals (see subfactor 3).

Business Category Minimum Subcontracting

Percentage

Small Disadvantaged Business (SDB) 5%

Service Disabled Veteran Owned Small Business

(SDVOSB)

5%

Women Owned Small Business (WOSB) 5%

Historically Underutilized Business Zone Small

Business (HUBZone)

3%

Small Business 28%

2.2.1.5 Offerors will be notified via email if they are deemed compliant or noncompliant for the FCL, Tier Declaration, and Small Business Subcontracting Plan requirements. If the Offeror is deemed compliant with Step 1 instructions, the Offeror will be notified via email and will move to Step 2. If the Offeror it deemed noncompliant with Step 1 instructions, the Offeror will be notified via email that is was noncompliant, the proposal will not be evaluated further, and the Offeror will not move on to

Step 2.

2.2.2 The Technical Factor has four (4) Subfactors

Factor I: Technical

Subfactor 1: Scenario (SOO) Response

Subfactor 2: Corporate Experience

Subfactor 3: Small Business Commitment Document (SBCD)

Subfactor 4: Management and Capacity Plan

2.2.3 Step 2 – Submit Technical Volume 1, Technical Subfactor 1

2.2.3.1 2a Scenario (SOO) 1

2.2.3.2 2b Scenario (SOO) 2

2.2.4 Step 3 – Submit Technical Volume 2 , Technical Subfactor 2-4 n

2.2.6 Proposal submission. Proposal submissions shall be sent via email only to the contracting POC no later than the due date shown in Table 1. No hard copies are required. Late proposals will be processed in accordance with FAR Provision 52.212-1(f) Late Submissions, Modifications, Revisions and

Withdrawals of Offers.

2.2.7 Table 1 below provides a proposal timeline.

Table 1 – Proposal Timeline (ET - Eastern Time)

Requirement Due Date

STEP 1

Minimum “Pass/Fail” Gate - Declare Tier, Facility

Clearance Validation, and SB Subcontracting plan compliance review

XX MOS 24, 1:00PM ET

Notification of Compliance / Noncompliance for

Step 1

XX MOS 24, 1:00PM ET

STEP 2a

Offeror receives Scenario 1 (SOO) and Government

Schedules Oral Presentations

Starting XX MOS 24

(11 Calendar Days Prior to Scheduled Oral

Presentation Day)

Provide information for in-person attendees for base access

Next Business Day after invite receipt, 1:00PM

ET

Submit Technical Volume 1, Technical Subfactor 1

(Scenario 1 (SOO))

Due 1 Calendar Day Prior to Offerors Scheduled

Oral Presentation, 1:00 PM ET

Oral Presentations (Scenario 1 (SOO)) Various Dates (11 Calendar Days after Scenario

(SOO) Receipt )

STEP 2b

Offeror receives Scenario 2 (SOO) and Government

Schedules Oral Presentations

Starting XX MOS 24

(4 Calendar Days Prior to Scheduled Oral

Presentation Day)

Provide information for in-person attendees for base access

Next Business Day after invite receipt, 1:00PM

ET

Submit Technical Volume 1, Technical Subfactor 1

(Scenario 2 (SOO))

Due 1 Calendar Day Prior to Offerors Scheduled

Oral Presentation, 1:00 PM ET

Oral Presentations (Scenario 2 (SOO)) Various Dates (4 Calendar Days after Scenario

Receipt )

STEP 3

Submit Technical Volume 2, Technical Subfactor 2-

XX MOS 24

2.3 Communications.

Exchanges of source selection information between Government and Offerors will be controlled by the

CO and CS. E-mail will be used to transmit such information to Offerors. The Government intends to send answers to questions by amendment to the solicitation and post to www.beta.SAM.gov. The

Offerors must submit all communications via email to the Contracting POCs.

2.4 Amendments to Solicitation.

If this RFP is amended, all terms and conditions that are not amended remain unchanged. Offerors shall acknowledge receipt of any amendment to this request by the day and time specified in the amendment(s).

2.5 Base Access/Function List.

Step 2 Attendance Requirements. Please fill out and provide Attachment 11 function list (base access ) excel sheet for attendees for Oral Presentations NLT than the date provided in Table 1. Joint Base

Andrews requires a 100% ID check. If a visitor does not possess proper identification (government issued

CAC, dependent ID, Retired ID) for access to Joint Base Andrews, the visitor must comply with the action provided below. If you require access and you don’t have a sponsor, please provide the following information in Attachment 11. Due to Personally Identifiable Information (PII being provided, please password protect the visitors pass form and send a separate email with the password and send it to destinee.narak@us.af.mil and kyle.beck.5@us.af.mil. Do not send the form to the Visitors Center. The

VCC will process the request, and those properly vetted DO NOT need to go the VCC for passes. Simply drive to the gate and show a valid ID. The gate guard will check for clearance and allow entry. Only place individuals who are 18 years of age and older, and do not hold any form of ID onto the

Function List. List all guests in alphabetical order by last name, then first name, followed by their date of birth, and lastly, list there ID and associated state and number in order to be vetted through the National

Crime Information Center (NCIC). All visitors vetted through NCIC, must have a form of State or federally issued ID (Driver’s license State ID car, Passport, etc).

http://www.beta.sam.gov/ http://www.fbo.gov/ http://www.fbo.gov/ mailto:destinee.narak@us.af.mil mailto:kyle.beck.5@us.af.mil

2.6 Step 2: Oral Presentations.

The Government will require unclassified oral presentations for Technical Subfactor 1 (Technical

Scenarios (SOO)) (see instructions in Table 1) via in person at 1500 West Perimeter Road, Room 4170, Joint Base Andrews, MD 20762. Do not enter the building until 30 minutes prior to your oral presentation. Offerors can wait in the lobby of the building at that time. A government POC will meet in the lobby 15 minutes prior to your scheduled oral presentation.

2.6.1 Attendance Requirements. Due to the high-level support required for DAFSTS II, the Government is requiring Key Executive Personnel to be in attendance. Each Key Executive shall introduce themselves at the start of the oral presentation. While each firm is organized differently, the following executive level (decision maker) personnel are required to be in attendance and brief/provide solutions and be prepared to answer questions:

One (1) Commercial (Private Sector) Account Partner/Vice President/Principal/Managing Director

One (1) Federal (Public Sector) Account Partner/Vice President/Principle/Managing Director

*One (1) Engagement Executive – lead executive for engagement with high level clients

*One (1) Transformation Executive - lead executive for transformation within the organization

**Note: Some firms have executives that are dual-hatted. Please identify that when you provide listing of attendees and their roles. Attendance is limited to 10 personnel per Offeror.

2.6.2 Offerors will receive the scenario(s) and be contacted based on the schedule in Table 1 for a time slot for oral presentations. Offerors shall also provide a listing of attendees and their roles during the presentation. See Table 1 for due dates.

2.6.3 Oral presentations will be in person at Andrews AFB and Offerors shall present its’ slides in person via Government laptop as stated above in Table 1. In-person contractor attendees shall not exceed ten (10) personnel. Virtual participation is prohibited. The Offeror shall state in the footer that the presentation is

‘unclassified’ and no information will be provided by the Offeror that is classified during the presentation.

All documents are submitted by Offerors in the same time frame. No changes can be made to the presentation once it has been received by the Government. 10 minutes prior to the scheduled oral presentations, the Meeting room will be open to ensure there are no technical issues. Five (5) minutes prior to the scheduled presentation, the Contracting Officer will go over rules of engagement and address any questions.

2.6.4 Restrictions on Electronic Devices. Personal cell phones and laptops are not permitted in the presentation room. There is a temporary locker available for personal cell phones outside of the presentation room. NO LAPTOPS allowed. The presentation shall be emailed to the Government prior to the scheduled brief to ensure functionality. No CD-ROMS are permitted.

2.6.5 Time Limit. Oral presentations will be limited to 30 minutes. The Government will not interrupt during the presentation to ensure all Offerors are afforded the same amount of time to brief.

2.6.6 Format for Presentations. Offerors shall provide their presentation in Microsoft PowerPoint for projection during the oral presentation. Any other format may become distorted on the screen. Offerors can provide the presentation in Portable Document Format as backup if they desire.

2.6.7 No cameras, camcorders, cellular devices, recording devices, etc. of any kind are allowed before, during, or after the oral presentation. Offerors shall NOT record the presentation or conversation with the Government.

Any Offeror found not in compliance will be deemed ‘noncompliant”, its proposal will not be further evaluated, and the Offeror will be ineligible for award.

2.7 Period of Acceptance of Offers.

The Offeror agrees to hold its proposal firm for 180 calendar days from the date specified for receipt of offers.

2.8 Federal Holidays: The following Federal Legal Holidays are observed:

• New Year’s Day

• Martin Luther King Day

• President’s Day

• Memorial Day

• Juneteenth

• Independence Day

• Labor Day

• Columbus Day

• Veterans Day

• Thanksgiving Day

• Christmas Day

3.0 Preparation Instructions to Offerors:

The purpose of these instructions is to prescribe the format of proposals and describe the approach for the development and presentation of proposal data. They are designed to ensure the essential information required for evaluation of proposals is submitted. Offerors are cautioned to follow the detailed instructions fully and carefully, as the Government intends to make award based on initial offers received without discussions but reserves the right to hold discussions.

3.1 Organization/Number of Copies/Page Limits

To assure timely and equitable evaluation of the proposal, the Offeror must follow the instructions contained herein. The proposal must be complete, self-sufficient, and respond directly to the requirements of this solicitation. The response shall consist of two (2) separate volumes: Technical

Volume1, Technical Subfactor 1 and Technical Volume 2, Technical Subfactors 2-4.

3.1.1 Offerors shall prepare proposals as set forth in the Proposal Organization Table below. The titles and contents of the volumes shall be as defined in the Table, all of which shall be within the required page limits and with the number of copies as specified. The volumes identified in the Table shall be emailed.

The content of each proposal volume is described in the ITO paragraph as noted in the Table 2 below:

Table 2 – Proposal Organization

Requirement ITO

Paragraph(s)

Delivery Format Page Limit (page numbers are maximums)

Step 1: FCL, Tier

Declaration, and Small

Business

Subcontracting Plan

(Written)

2.2.1 Email completed DD254, Email

with Tier Declaration (with teaming arrangements), Small

Business Subcontracting Plan

- 3 pages for DD254;

- 1 page Tier declaration memo/template and attach reps and certs (no page limit);

- 50 pages for Small Business

Subcontracting Plan

Step 2: Base

Access/Function List

2.5 Email completed function list No Page limit

Step 2a: Submit

Technical Volume 1, Technical Subfactor 1

(Scenario1 (SOO))

(Written & Oral)

2.2.3 Email Oral Presentation

(PowerPoint) for scenario 1

(SOO) and Contractor Proposed

PWS (PDF)

-15 pages for Oral Presentation

-15 pages for PWS

Step 2b: Submit

Technical Volume 1, Technical Subfactor 1

(Scenario 2 (SOO))

(Written & Oral)

2.2.3 Email Oral Presentation

(PowerPoint) for scenario 1

(SOO) and Contractor Proposed

PWS (PDF)

-15 pages for Oral Presentation

-15 pages for PWS

Step 3: Technical

Volume 2, Technical

Subfactors 2-4

(Written)

2.2.4 Email Presentation (Power Point)

SBPCD & Management Capacity

Plan (PDF)

-CORPORATE EXPERIENCE:

No more than 2 pages per (max

30 slides).

-SBPCD: 5 pages

-MANAGEMENT CAPACITY:

5 pages

3.2 Specific Instructions.

3.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. Blank pages, title pages, cover pages, Table of contents, tab indexing, glossaries, list of Tables and figures are not included in page limitation. Legible

Tables, charts, graphs and figures may be used to depict organizations, systems and layout, implementation schedules, plans, etc.

3.2.2 Page Size and Format for Written Proposal Submission. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8½ x 11 inches. Pages shall be single-spaced and typed, except for displays and the reproduced sections of the solicitation document. The font shall be Times New Roman and no less than

12 point in size. Use at least 1 inch margins on the top and bottom. Pages shall be numbered sequentially by volume. When text is included within displays (graphs, charts, figures, tables, pictures), it may be no smaller than 8 point, but must be clearly legible without magnification, as determined solely by the CO. The size of these displays shall not exceed the page size as defined above. These limitations shall apply to both email and hard copy proposals. The email copy of the proposal shall be submitted in the following formats:

Any Microsoft Office documents prior to 2010 will not be allowed, or Portable Document Format (PDF), as applicable. There are no formatting requirements for Oral Presentation (which the exception of the required use of

PowerPoint ™); however, it is the Offerors responsibility to ensure its presentation is legible and viewable by the intended audience. The recommended resolution is 16:9. The email size limit to the Government is 20MBs per email. Proposals can be broken up into more than one email (label each email proposal stating more than one email is being distributed, i.e. proposal email 1of 1) or Offerors can request the proposals to be sent through DoD

Safe-(must email POC to request a link). Non-CAC holders cannot use DoD Safe at this time. Contact the POCs if you require assistance.

3.3.4 Title Page (not included in the page count): Each volume must include a title page. The title pages must show:

• Solicitation Number

• Name, address, telephone numbers and e-mail address of the Offeror

• Cage Code & UEI

3.3.4 Cross-Referencing: The proposal volumes shall be written on a stand-alone basis so that its contents may be evaluated without cross referencing to another volume. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

3.3.5 Indexing: Each volume shall contain a detailed Table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections and will not count against page limitations IAW paragraph 3.1.1 above.

3.3.6 Glossary of Abbreviations and Acronyms: Each volume shall contain a glossary of all abbreviations and acronyms used, with an explanation for each. As stated above in paragraph 3.1.1, glossaries do not count against the page limitations for their respective volumes.

3.3.7 Compliant: Documents submitted in response to this solicitation must be fully compliant to and consistent with the terms and conditions of the solicitation or may result in being rejected as noncompliant and not being evaluated.

4.0 Proposal Volume Instructions. The following details the specific instructions for each volume.

4.1 FACTOR I –Technical.

The Technical proposal should be specific and complete. Legibility, clarity, and coherence are very important. The Offerors responses will be evaluated against the Technical subfactor criteria defined in the Addendum to FAR 52.212-2 - Evaluation – Commercial Items. The proposal should not merely reiterate or rephrase the objectives or reformulate the Government’s requirements specified in the solicitation, but shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume the Government has no prior knowledge of their facilities and experience and will base its evaluation on the information presented in the Offerors proposal.

4.1.1 Subfactor 1: Scenario (SOO) Response.

4.1.1.1 Offerors will be provided each scenario (SOO) prior to the presentation date as depicted in Table

1 for submittal of Step 2. The assistance of technical experts is allowed. Each Offeror shall provide an executive-level PowerPoint briefing explaining a detailed solution to the scenario (SOO). The Offeror shall utilize and incorporate industry best practices in developing the strategy.

a. The solicitation response shall include the contractor proposed Performance Work

Statement (PWS) (the “what”).

b. A PWS is a document that provides a transformation resolution to the Statement of

Objectives (SOO)-the scenario. An executive summary not required; however, if Offeror elects to do one, it will count toward the page limit.

c. The PWS will minimally contain the following;

i. General – From SOO

ii. Background – From SOO

iii. Scope – From SOO

iv. Problem Statement – From SOO

v. Technical Solution/PWS proposed tasks to meet objectives

vi. Section 3.0 to 7.0 (not counted towards page number) – From SOO

d. The PWS shall provide the Offerors detailed technical solution to meet the Statement of

Objectives (desired transformation outcome). This includes the Offerors proposed milestones/timeline, deliverables, and stakeholder engagement plan.

e. The Oral presentation (the “how”) shall provide the Offerors; detailed approach on how the transformation will be completed. At a minimum the slides should address the below:

i. Milestones - Data, visualization, recommendations, decision points, etc.

ii. Strategic Approach, Methodology –Explain how the problem will be solved.

Explain the selected methodology and why it was chosen

iii. Executable Approach – Explain the definability of the approach (data, metrics, applicable experience)

iv. Risks Assessment – Explain risk identification, monitoring, measuring, and mitigation

v. Objective metrics – How will success/failure be measured?

vi. Betterment – Explain how the approach will make the organization better. Must be a measurable increase in output, efficiency, return on investment, cost savings, etc.

4.1.1.2 Subfactor 2: Corporate Experience

To be recent, the Prime Offeror shall provide corporate experience examples that were performed in the past three (3) years from the date of issuance of this solicitation. The Offeror shall demonstrate experience regarding scope based on, but not limited to, the similarities between recent experience on transformational efforts in terms of the subject areas in Table 3 (below) and application within a complex, global-scale organization. Submission must demonstrate how the Offeror made a transformation impact and betterment of the entity it supported.

• Impact – a significant major effect or influence in resolving the organizations’ problem set and meeting the mission (people, processes, technology, culture)

• Betterment - Must be a measurable (cost, schedule, performance) increase in output, efficiency, return on investment ROI, etc.

Corporate experience must be at the corporate level and not based on individual employee experience.

All submissions must provide POC information for verification from credible source (intimate knowledge of submitted transformation example).

Table 3– Corporate Experience Instructions

Subfactor 2: Corporate Experience

a. Provide two (2) transformation examples (public or private) where the Prime offeror unsuccessfully implemented a transformation strategy or plan and how did the

Prime offeror recover?

b. As prime, provide five (5) submissions of successfully translated commercial

(private sector) best practice to a Government agency

(public sector)

c. As prime, provide seven (7) submissions of private sector transformation efforts

• Cannot be client caused issue

• Shall be prime; Cannot use subcontractor’s experience

• Shall be from minimally three (3) different organizations

• SB primes can use experience performed as a first-tier subcontractor, shall not

• Shall be from minimally four

(4) different organizations

• SB prime can use experience as a first-tier subcontractor; however,

4.1.1.2.1 Efforts submitted should be specific about the Offerors corporate experience in meeting the

Government’s requirements as outlined in the Tier Definitions at paragraph 2.1.3. The submitted efforts should demonstrate the Offerors prior or current experience on private sector and public sector contracts (call orders, task orders) accomplishing enterprise level transformations that would meet the requirements within the scope of DAFSTS II. The

Offeror shall explain how the submitted efforts provided in the proposal meet the requirements in Table 3.

4.1.1.2.2. During the Corporate Experience validation process, the Government will call identified

POCs and ask questions concerning the Offeror’s performance on the submitted effort only

(to confirm if the Offeror met objectives/outcomes and quality). The Government will not ask proprietary questions. This is a reference check only.

4.1.1.2.3. For each effort Offerors shall provide: (1) Organization name, (2) Period of Performance, (3)

Point of Contact, (4) description of the transformational task completed, (5) how the effort is relevant in terms of scope and, (6) impact to the organization.

4.1.1.2.4. The Corporate experience examples provided must meet the minimum declared Teir requirements.

4.1.1.3 Subfactor 3: Small Business Participation Commitment Document (SBPCD)

4.1.1.3.1 The Small Business Commitment Document (SBPCD) is Applicable to ALL Offerors.

The SBPCD is separate and distinct from the Small Business Subcontracting Plan required by FAR

Clause 52.219-9, Small Business Subcontracting Plan. All Offerors shall submit a SBCD as required by

DFARS 215.304(c)(i)(B). The proposed SBPCD will be incorporated into any resulting contracts. The offeror shall plan to assign complex/variety of the work small firms are to perform. The offeror shall plan to incorporate Non-Traditional Small Business (NTSB), and shall utilize a minimum of three (3) nontraditional small businesses over the ordering period. The offeror shall include a training program plan for SB & NTSB’s. The training shall assist SB’s subcontractors to include NTSB’s in becoming federal contractors (SAM registration, RFP process, intricacies of Government contracting, applicable regulations, etc.). The training includes plans for all socio-economic groups plus NTSB and NTSB –

Requires at least one new NTSB annually.

exceed two submissions of the five (5) max OR

• SB primes can use experience from their first-tier subcontractor, shall not exceed two submission of the five max shall not exceed three (3) submission of the seven (7) max OR

• SB prime can use experience from their first-tier subcontractor, shall not exceed three submission of the seven max

4.1.1.3.2 For the purpose of this requirement, “Nontraditional Small Business (NTSB) Contractor” means a small business entity that is primarily engaged in similar lines of activity as listed and described in the

North American Industry Classification System (NAICS) manual, having met the small business standards for that industry, established by the Small Business Administration, that is not currently performing and *has not performed any contract or subcontract for the Federal Government. Any entity organized for profit (even if its ownership is in the hands of a nonprofit entity) with a place of business located in the United States or its outlying areas and that makes a significant contribution to the U.S.

economy through payment of taxes and/or use of American products, material and/or labor, etc. A NTSB

Contractor includes but is not limited to an individual, partnership, corporation, joint venture, association, or cooperative. *If the NTSB has received a contract(s) through “Pitch Day” or Small Business

Innovation Program, they can be considered a NTSB. NTSB’s will only retain NTSB status for up to two

(2) years.

4.1.1.3.3 Offerors shall propose an annual minimum quantitative requirement (MQR) percentage for small businesses concerns and non-traditional small business (NTSB) using Table 4, and explain how they intend to meet the proposed MQR percentages for the overall IDIQ. The MQR’s shall match your small business Subcontracting Plan that was submitted in Step 1.

Table 4 – MQR

4.1.1.3.4 Offerors shall provide narrative information on how percentages for this effort were developed and explain why and how they are realistic.

4.1.1.3.5 SBPCD Using Table 5, Offerors shall provide the company name of each small business, its socio economic status (if applicable), nature of commitment (subcontract, letter of commitment, agreement, etc.), and what types of products/services the small business/NTSB provides (specific to this requirement).

Table 5 SBPCD Companies

Company Name Business

Category(ies)

Nature of

Commitment

Product/Services

Provided

NAICS

Ex. Company ABC WOSB 541611

Business Category Proposed MQR

Percentage

Small Disadvantaged Business (SDB)

Service Disabled Veteran Owned Small Business (SDVOSB)

Women Owned Small Business (WOSB)

Historically Underutilized Business Zone Small Business

(HUBZone)

Small Business

Non-traditional Small Business

4.1.1.4 Subfactor 4: Management and Capacity Plan

4.1.1.4.1 For the purpose of this requirement, Teaming Arrangements are permitted; however, a Prime

Offeror shall be identified in the arrangement and upon award shall perform at least 50% of the work on all awarded DAFSTS II task orders. Offerors shall explain its approach and methodology to perform more than 50% of each awarded task order. Offerors shall explain their plan to manage capacity and resources that will enable the Offeror to rapidly respond to the breadth of transformational tasks via the Task Order

Proposal Request process through partnerships, methodologies, automation, etc. Offerors shall explain its plan to mitigate the risk to the Government associated with teaming arrangements, subcontracting, etc.

consisting of several different entities to meet the scope of this requirement. Offerors shall explain their plan to manage and monitor its workforce (including subcontractors) at multiple locations at the same time while continuously meeting the Government’s high-level requirements.

◼ Plan to handle breadth of transformational tasks

◼ Plan to manage multiple task orders across multiple locations simultaneously

◼ Risk Mitigation Plan

◼ Turn-over

◼ Subcontractors

◼ Performance issues

4.2 General Information.

4.2.1 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 CO in writing with supporting rationale as well as the remedies the Offeror is asking the CO to consider as related to the omission or error. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussion. Accordingly, Offerors are advised to submit initial proposals that are well defined and clearly acceptable without additional information, additional or substitute pages.

4.2.2 Correction Potential of Proposals. The Government intends to award without discussions. The

Government will consider, throughout the evaluation, the "correction potential" of any deficiency.

The judgment of such "correction potential" is within the sole discretion of the Government. If an aspect of an Offerors proposal does not meet the Government's requirements and is not considered correctable, the Offeror may be eliminated from competition.

4.2.3 Discussions. The Offerors initial proposal should contain the Offerors best terms. The Government intends to award without discussions but reserves the right to conduct discussions if it is determined to be in its best interest. Offerors are advised to submit proposals that are fully and clearly acceptable without additional information. Any discussions will be conducted in accordance with FAR 15.306.

Discussions can occur at any time during the evaluation process.

4.2.4 Evaluation Notices (EN). ENs may be used for clarification or communication purposes as well as discussions. Responses to the ENs will be evaluated in accordance with the evaluation criteria stated herein. Failure to respond to ENs will eliminate the Offeror from further evaluation and consideration for award. No written ENs will be issued for oral presentations.

4.2.5Final Proposal Revisions (FPR). If discussions are held, at the conclusion of discussions, the CO will provide each Offeror an opportunity to submit a FPR. The CO will establish a common cut-off date for receipt of FPRs. FPRs will be evaluated in accordance with the evaluation criteria stated herein.

After receipt of the FPR, the Government intends to make award without obtaining further revisions.

4.2.3 Debriefings. Debriefing information relating to other Offerors proposals will not be disclosed.

4.2.3.1 Post Award. All Offerors (successful and unsuccessful) may request a Post Award debriefing within three (3) calendar days after the date in which the Offeror received notification of contract award. Post award debriefings will be available to interested parties that advance past step 1. In an effort to allow for full feedback, during post award debriefing, the Government will provide strengths, weaknesses, significant weaknesses, and deficiencies.

4.2.3.2. A “strength” is an aspect of an Offerors proposal that has merit or exceeds specified performance or capability requirements in a way that will be advantageous to the Government during contract performance. A “weakness” means a flaw in the proposal that increases the risk of unsuccessful contract performance. A “significant weakness” is a flaw that appreciably increases the risk of unsuccessful contract performance; and a “deficiency” is a material failure of the proposal to meet a Government requirement or combination of significant weaknesses in a proposal that increases the risk of unsuccessful contract performance to an unacceptable level. Offerors who receive a debriefing may submit additional questions related to the information provided during the briefing within two (2) business days after receiving the debriefing. After the two business days expire, the

Contracting Officer is not required to respond to any additional questions. The debriefing is concluded when the Contracting Officer delivers written responses to the Offerors timely additional questions.