Attachment 10_Section L_Instructions to Offerors.pdf

SECTION L - INSTRUCTIONS TO OFFERORS (ITO)

Using FAR Part 15 source selection procedures, the Government will use a tradeoff approach to conduct a Service Disable Veteran Owned Small Business (SDVOSB) set-aside competition to target a single award Indefinite Delivery, Indefinite Quantity (IDIQ) contract for Intelligence, Surveillance and Reconnaissance (ISR) Processing, Exploitation and Dissemination (PED) support. The resultant contract will establish firm fixed price rates proposed and accepted to perform advisory and assistance services (A&AS) to Air Force Special Operations Command (AFSOC) and mission partners. The requirements will primarily be performed at Hurlburt Field, FL, but could include OCONUS locations, as required by mission requirements. The 765th Enterprise Sourcing Flight (ESF), Hurlburt Field, FL, will write and administer task orders issued for this contract.

As confirmed by market research, subcontracting and teaming arrangements are likely because of the broad scope of contract requirements; therefore, such arrangements are encouraged.

During this contract competition, companies identified as prime Contractor or teaming partner/subcontractor on any proposal cannot participate as a prime Contractor or teaming partner/subcontractor on any other proposal. This limitation applies to components of joint venture partners. It is the Offeror’s responsibility to ensure teaming partners and subcontractors are not teamed with other Offerors during the ISR-PED contract competition.

A. General Instructions:

1. Offerors must follow the instructions contained herein. Offerors will meet all solicitation requirements, to include, terms and conditions, representations and certifications, technical requirements, and those identified as evaluation factors or subfactors. ITO instruction non-compliance may result in an unfavorable proposal evaluation, and render the proposal ineligible for award. Offerors must clearly identify solicitation terms and conditions exceptions with rationale for each exception. Documents submitted, in response to this RFP, must be fully responsive to, and consistent with, the requirements of the RFP, Performance Work Statement, and evaluation factors for award in RFP, Section M.

2. Points of Contact: The below individuals are this acquisition’s points of contact.

Primary:

Shawn Edwards

Contracting Officer

AFICC/765 ESF

427 Cody Ave, Bldg 90333, Ste 215 Hurlburt Field, FL 32544 Email: shawn.edwards.14@us.af.mil

Alternate:

Ashley Williams Contract Specialist

AFICC/765 ESF

427 Cody Ave, Bldg 90333, Ste 215 Hurlburt Field, FL 32544 Email: ashley.williams.85@us.af.mil

3. Submission of Questions. Submit written questions, concerning this solicitation, via e-mail to BOTH Contracting POCs no later than SEVEN (7) business days after issuance of this solicitation.

4. Discrepancies. If an Offeror believes the instructions contain an error, omission, or are otherwise unsound, the Offeror will immediately, in writing, notify the Contracting POCs with supporting rationale, as well as, remedies the Offeror wants the Contracting POCs to consider related to the omission or error.

5. Electronic Submission of Proposals. The Offeror will submit proposals electronically via the DoD Secure Access File Exchange (SAFE) website, https://safe.apps.mil/, no later than the solicitation closing date and time referenced in Standard Form (SF) 33, Block 9. DoD SAFE site instructions can be found at https://safe.apps.mil/about.php.

5.1. Submit proposals via DoD SAFE to BOTH of the Contracting POCs in paragraph A.2.

above.

5.2. The files’ titles will include the Offeror’s CAGE code, volume number and title, i.e. CAGE CODE, Volume #, Volume Title. Offeror’s will submit proposals via DoD SAFE, allow sufficient time for upload prior to solicitation closing date/time.

5.3. It is the Offeror’s responsibility to ensure all electronic files are submitted virus free.

Submissions will not be locked, encrypted, zipped, or otherwise contain opening barriers.

Microsoft (MS) Excel template files will be submitted as MS Excel files. The Offeror will not modify, adjust, or change any part of this solicitation’s MS Excel files unless authorized by the Contracting POCs, and annotated on proposal. Any unauthorized changes to any MS Excel files will make the proposal unresponsive.

5.4. Classified data is prohibited in any files, and the Offeror must adhere to the solicitation’s required page limits.

6. Only one (1) proposal per company is accepted. Proposals received after the required date/time will be handled in accordance with FAR 52.215-1(c) (3), Submission, Modification, and Revision of Proposals.

7. Pre-proposal Site/Visit. A pre-proposal site visit will not be conducted for this solicitation.

B. Proposal Preparation Instructions:

1. The following prescribes proposal’s formats, and describe the development and presentation approach for the proposal data. The proposal will include all of the requested information in the specified instructions. Failure to include all requested information may adversely affect the evaluation, and may result in a unawardable determination.

2. Proposals will be clear, concise, and contain sufficient detail for effective evaluation and substantiating stated claims. The proposal will not rephrase or restate the Government’s requirements, but will provide rationale on how the Offeror will meet these requirements.

Offerors will assume the Government has no prior knowledge of their facilities and experience, and will base its evaluation on the Offeror’s proposal. Elaborate formats, binding, detailed art work, or other embellishments are unnecessary and not desired or required.

3. Proposals will be complete and consist of four (4) separate volumes consisting of the number of electronic copies as follows:

Proposal Submission Volume Copies Number of Pages General and Administrative Qualifying Criteria 1 1 6 Transition Plan 2 1 10 Corporate Experience and Management 2 1 20 Past Performance 3 1 No Limit Price 4 1 No Limit

C. Volume Preparation Instructions:

1. Proposal Organization/Number of Copies/Page Limits. The Offeror will organize each volume as identified in the paragraphs below.

1.1. Each volume will be written as standalone, so its contents may be evaluated with no requirement to cross reference other proposal volumes.

1.2. Page limitations will be treated as maximums. If exceeded, the excess pages will not be read or considered in the proposal’s evaluation. The PCO may also place page limitations on responses to Evaluation Notices (ENs). EN response page limits will be identified in the EN form. Unless otherwise indicated in Volume details, each page will be counted except for cover pages, table of contents and indexes, blank pages, glossaries, and cross reference matrices.

1.3. A page is defined as each face of an 8 1/2 x 11-inch document containing information. Page margins will be a minimum of 1-inch each for the top, bottom and sides. Except for the reproduced sections of the solicitation document and footnotes, the text size will be no less than 12-point in Times New Roman or Arial font. Tracking, kerning, leading values, and footnote font size will not be changed from the default values of the word processing or page layout software. Include the following legend on each page of all volumes: “Source Selection Information - See FAR 2.101 and 3.104.”

1.4. Charts, illustrations, tables, or diagrams will not exceed 11 x 17-inches. For page count, this page will count as two (2) 8 1/2 x 11-inch pages and will only be used for graphics and exhibits.

All information, except for document numbers, page numbers, etc., will be provided with an image area of 9 x 15-inches. Text used for call-outs on graphics and exhibits will be no smaller than 8-point Times New Roman or Arial, after final reductions. Call-outs may be single-spaced.

1.5. Cross Referencing. Cross-referencing within a proposal volume is permitted when its use conserves space without impairing clarity. Required proposal evaluation information not found in its designated volume is assumed omitted from the proposal. Offerors are responsible for their proposal’s accuracy and the Government will NOT search for information not provided in the required Volume.

1.6. Offerors who submit proprietary or restricted information or data will mark it as such. The Government assumes no liability for disclosure or use of unmarked information or data, and may use or disclose the unmarked information or data for any purpose. Unless restricted, information and data submitted in response to this request may become subject to disclosure to the public pursuant to the provisions of the Freedom of Information Act (5 U.S.C. 551).

1.7. The Government reserves the right to make a selection based upon initial proposals;

therefore, the Offeror should submit its best terms in its initial proposal. The Government reserves the right to confer with Offeror(s) to clear up proposal details, if necessary, at the Government’s discretion, and may determine to make no award.

1.8. The Offeror is required to submit the below information in identifiably separate and distinct parts. If an Offeror fails to submit any of the required information as stated in this RFP, it is considered non-responsive and may be eliminated from award consideration.

2. Volume I - General and Administrative Qualifying Criteria (Factor 1). Offerors will prepare Volume I as follows.

Section Title Page Limit Section 1 Table of Contents No Page Limit Section 2 Executive Summary 1 Page Limit Section 3 SF33, Solicitation and SF30, Amendments No Page Limit Section 4 Completed DD254 No Page Limit Section 5 Contractor Team Organization 5 Page Limit Section 6 Certifications and Representations No Page Limit Section 7 Exceptions to Solicitation Requirements (If Applicable) No Page Limit Section 8 Financial Responsibility Document No Page Limit

2.1. Section 1 - Table of Contents. A detailed table of contents delineating the subparagraphs within the volume.

2.2. Section 2 - Executive Summary. The executive summary will include the following information, and be signed by an official authorized to contractually commit the Offeror.

2.2.1. Company name, complete business address, CAGE code, DUNS number.

2.2.2. Statement the proposal is valid until at least 180 days after proposal is due.

2.2.3. Name and phone number of persons authorized to represent the company for clarification and/or questions about the proposal.

2.2.4. Organizational Conflict of Interest per paragraph 15 of this document.

2.3. Section 3 - SF33, Solicitation/Contract/Order and SF30s, Amendment of Solicitation/Modification of Contract Documents. Offerors will complete Blocks 12, 13, 14, 15A-15C, 16, 17, and 18. The Offeror’s signature must be from an individual authorized to negotiate on behalf of the Offeror.

2.3.1. Proposal Acceptance Period. The proposal acceptance period is a minimum or 180 calendar days after the proposal due date. Insert the number of calendar days in SF 33, Block 12.

Offerors may specify a longer acceptance period than the Government’s minimum 180 days by inserting its proposed acceptance period in SF 33, Block 12.

2.4. Section 4 - Completed DD254, Attachment 3, to this solicitation. Offerors will complete DD254, Blocks 6a-7c, DoD Contract Security Classification Specification.

2.4.1. Offerors are required to maintain a TOP SECRET level facility clearance. Offerors must provide proof of current TOP SECRET level US Facility clearance in accordance with DoDD 5220.22, National Industrial Security Program Operating Manual (NISPOM). The TOP SECRET clearance must be current at time of proposal submission. The TOP SECRET level clearance requirement applies to the contract’s prime. The TOP SECRET level clearance also applies to any subcontractors that will perform work under this contract. The Contractor and subcontractor personnel will have access to TOP SECRET level classified information. For those Offerors submitting a proposal as a newly formed partnership, joint venture, or limited liability company, the requirement can be satisfied through the submittal of documentation evidencing the fact that all of the partners or member companies of the partnership currently possess the required Facility Clearance. Offerors will include the CAGE and DUNS codes for verification.

2.4.2. If an Offeror lacks the proper facility clearance classification, the offer will be deemed non-responsive, not evaluated, and eliminated from further consideration.

2.5. Section 5 - Contractor Team Organization.

2.5.1. The Offeror will provide:

2.5.1.1. Contractor Name

2.5.1.2. Place of Performance

2.5.1.3. Cage Code/DUNS #

2.5.1.4. Brief Work Description

2.5.1.5. Percentage of Total (Indicate Prime, and/or Program Proposed Price Joint Venture Responsibility Team Member, or Sub)

2.5.2. The Offeror will include all subcontractors and Joint Venture team members who will be involved with the performance of the contract, and list all sites where the work will be performed. If a Joint Venture teaming or subcontracting arrangement is proposed, identify the work share, distribution elements, and ratios that each contractor will perform using the table below. Also provide a definition of the legal relationship between the entities if it is other than a Prime/subcontractor relationship.

2.5.3. The Offeror will provide a written explanation if multiple CAGE codes/DUNS, for the same physical location, are provided in section 2.5.1 above. The written explanation will detail the distinct roles and responsibilities for entities with different CAGE codes/DUNs at the same physical location where the work is being performed or from where the work is being directed.

The description will include all organization changes resulted from corporate acquisition, reorganization, merger, or other administrative reason.

2.5.4. Offeror will provide all Teaming Arrangements and Letters of Intent for Team Members to receive credit for performing as a team. A business entity can participate, in this acquisition, on one proposal only. During this evaluation, if a company is identified as a prime contractor or teaming partner/subcontractor on any proposal for this acquisition, then the company cannot participate on any other Offeror's proposal. It is the Offeror's responsibility to ensure teaming partners and subcontractors are not teamed with other Offerors.

2.6. Section 6 - Certifications and Representations. The Offeror will provide the following certifications and representations.

2.6.1. FY 2019 NDAA, Section 889, prohibits the Government from contracting with any entity that uses any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system, on or after August 13, 2020, unless an exception applies or a waiver has been granted. Contractors will be required to complete the representation at FAR 52.204-24, Representation Regarding Certain Telecommunications and Video Surveillance Services or Equipment.

2.6.2. Authorized Offeror Personnel. Provide the name, title, and telephone number of the Offeror point of contact regarding decisions made with respect to the Offeror's proposal and who can contractually obligate the Offeror. Also, identify those individuals authorized to negotiate with the Government along with the name, title, and telephone number of the CEO, Division President, Vice President, or similar person of the Offeror for notification purposes.

2.6.3. Company/Division Address, Identifying Codes, and Applicable Designations: provide Company or division's street address, county and facility code; CAGE code; DUNS code; TIN;

and labor surplus area designation.

2.6.4. Joint Venture Certifications. If the Offeror is a Joint Venture, the Offeror will provide a copy of the Small Business Administration (SBA) approved Joint Venture certification documentation.

2.6.5. Size of Business, and Labor Surplus Area Designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

2.7. Section 7 - Exceptions to Solicitation Requirements.

2.7.1. Offerors must meet all solicitation requirements; i.e., terms and conditions, representations and certifications, technical requirements, and identified evaluation factors and subfactors.

Offerors will clearly identify any exceptions to solicitation/contract terms and conditions. While Offerors may propose exceptions to the solicitation requirements, the Government is not obligated to accept or consider such exceptions. As well, exceptions could result in an offer being ineligible for award. Any requirement change resulting from exception acceptance will be reflected in the resultant contract.

2.7.2. Terms and conditions taken exceptions of the solicitation/contract, to any of its formal attachments, or to other parts of the solicitation will be identified.

2.7.3. Each exception will be related to each paragraph and/or specific part of the solicitation to which the exception is taken.

2.7.4. This information will be provided using the content below. Failure to comply with the solicitation’s terms and conditions may result in the Offeror being removed from award consideration.

2.7.4.1. Solicitation Document Paragraph/Page Number Requirement/Area Rationale

2.7.4.2. Contract Clause

2.7.4.3. Applicable page and Identify the area Justify why the solicitation paragraph

2.7.4.4. Paragraph number to which exception requirement will not be met

2.7.5. In the event the Offeror takes no exception to the stated requirements, a statement to this effect is required in this volume.

2.8. Section 8 – Financial Responsibility Documents. This information is used to determine the Offeror’s responsibility pursuant to FAR 9.104.1. Offeror will submit a financial capability letter from Offeror’s financial institution or Certificate of Competency (COC) issued by the Small Business Administration (SBA).

2.8.1. Send Financial Responsibility Questionnaire (Attachment 4), to one or more banking/lending institutions Offeror does business with and have a representative complete the questionnaire and return to the solicitation’s POC no later than proposal due date.

2.8.2. Financial responsibility will not be evaluated as a separate cost/price subfactor. However, it is a basic contract requirement with a pass/fail determination, and will be evaluated during source selection. A contract may only be awarded to Offerors deemed responsible in accordance with the Federal Acquisition Regulation (FAR).

3. Volume II – Transition Plan (Factor 2) and Corporate Experience and Management (Factor 3). Offerors will prepare Volume II as follows:

Section 1 Table of Contents No Page Limit Section 2 Cross Reference Matrix No Page Limit Section 3 Factor 2 – Transition Plan No Page Limit Section 4 Factor 3 – Corporate Experience and Management No Page Limit

3.1. Section 1 – Table of Contents. A detailed Table of Contents delineating subparagraphs within the volume. The Table of Contents does not count against Volume II page limits.

3.2. Section 2 – Cross-Reference Matrix. The Cross-Reference Matrix provides critical interrelationships and dependencies between the PWS, RFP Sections L and M, and the Offeror's proposal. Offerors will cross-reference proposal sections with the PWS requirements. The Government has completed the Description, Sections L and M Columns; Offerors will complete "Proposal Volume, Section No., Page & Para No." column. The Cross-Reference Matrix does not count against Volume II page limits.

SAMPLE:

Cross Reference Matrix Description PWS

Para No.

Section L Section

Para No.

Section M Section Para

No.

Proposal Section No., Page & Para No.

Factor 2 Transition Plan Factor 3 Corporate Experience and Management

3.3. The information submitted in Sections 3, 4, and 5 will be specific and complete. Legibility, clarity, and coherency are important. The Offeror's responses will be evaluated against the Technical evaluation criteria in Section M, Evaluation Factors for Award. Using the instructions provided below, provide, as specifically as possible, the actual methodology the Offeror would use for accomplishing/satisfying these subfactors. All requirements specified in the solicitation are mandatory. By the Offeror's proposal submission, the Offeror is representing the Offeror's firm will perform all requirements specified in the solicitation. Do not reiterate the objectives or reformulate the solicitation’s requirements, instead discuss how the Offeror plans to accomplish each requirement. Exceptions to any requirements will be documented in Volume I - Contract Documentation, Section 6. The total combined page limit for Sections 3, 4, and 5 is 20 pages.

3.4. Volume II will address the proposed approach to meeting the minimum requirements of the following two (2) Technical Factors:

Factor 2: Transition Plan Factor 3: Corporate Experience and Management

3.5. Section 3 – Factor 2: Transition Plan. The Offeror’s proposal will be written clearly and contain the pertinent information necessary for the Government to determine if the proposal meets/does not meet solicitation requirements. The Government will evaluate this information in accordance with Section M.

3.5.1. The Offeror’s transition plan details their plan to staff and transition the requirement from Contract Award. The PWS and Pricing Matrix details the requirement to be fulfilled by labor category and Full Time Equivalent (FTE) count.

3.5.1.1. The Offeror will address and provide a schedule with milestones by labor category that demonstrates its capability to execute a phase-in/transition leading to assumption of full contractual responsibility for positions 90 days from contract period of performance start date.

Milestones will be established at the 30th, 45th, 60th, 75th, and 90th day from performance start date. The proposal will include fill-rate metrics. These metrics will include milestone fill rates to achieve at least the minimum fill rate of 85% of required FTEs by the 90th day of the Transition Period.

3.5.1.1.1. Fill Definition. Contract employee assigned to an Authorized Position and is available to provide PWS identified services.

3.5.1.1.1.1. Contract Fill Rate. The Daily Manning Report will calculate and state Contract Fill Rate on a daily basis. The daily Contract Fill Rate will be averaged across each twelve-month performance period to determine Annual Contract Fill Rate. At no time will the Contract fill rate exceed 100%.

3.5.1.2. Any contract employees filling authorized positions and being paid under the predecessor contract will not be counted against the 30, 45, 60, 75, or 90-day fill rate requirement. Only contract employees working under the successful Offeror’s contract will be counted (including any incumbent captures once they begin being paid under the Successful Offeror’s contract).

3.5.2. This Transition Plan will include management expertise, ability to meet all security requirements (facility and personnel), procedures and policies, risk mitigation techniques, flexibility, logistics of moving the Offeror’s personnel into contract locations and assuming control of the Government’s requirement for real time analysis support to AFSOC that when viewed collectively demonstrates the Offeror’s ability to successfully execute a contract phase-

in. The Offeror will describe, in detail, the differenctiation between any proposed transition team and the contract management team, to include, any designated as Key Personnel. The Offeror in its transition plan will:

3.5.2.1. Identify all major activities,

3.5.2.2. Explain how each activity would be assured of timely completion,

3.5.2.3. Identify its phase-in management team, and

3.5.2.4. Describe its approach for interfacing with the incumbent Contractor.

3.5.3. Offerors will describe its plan for insertion of non-incumbent employees in the event incumbent employees decline employment with the Offeror’s company or subcontractors, or are otherwise unavailable for work under this requirement.

3.5.4. The Offeror will describe if/how it will assimilate incumbent contract employees (those currently performing under the existing contract) into its operations. The Offeror will provide details of any previous corporate experience on accomplishing succession from performance by a legacy Contractor to its own performance.

3.5.5. The Offeror’s detailed plan to transition the Contractor Initial Qualification and Mission Qualification Course from the incumbent Contractor to their control. Plan should include a detailed description of how the Offeror plans to staff, coordinate, and facilitate the course and course objectives for their students. Offeror will include details on the proposed facility, to include, the physical address, size, business management of the property (i.e. owned, leased, provided by subcontractor under a right of use) and availability date to meet PWS requirements.

3.5.6. The required Key Personnel will also be considered as part of the risk to successful execution of the Transition Plan Factor.

3.5.7. Describe the Offeror's corporate organizational structure, including prime and subcontractor roles (if any), and how performance will be managed between the prime and subcontractor (if any).

3.5.8. Resolution Process. Address how the Offeror plans to review, track, monitor, and respond to Government complaints regarding contractor employee performance, and the action the Offeror takes to resolve issues to satisfy Government concerns.

3.5.9. Address how the Offeror will ensure they meet Limitations on Subcontracting requirements. Offerors will explain their methodology to ensure at least 50% of the incurred cost of contract performance is expended for the prime contractor's employees (see FAR 52.219-14, Limitations of Subcontracting). Offerors will include information demonstrating incurred personnel costs will be from individuals who meet the definition of employee set forth in 13 CFR

(S) 121.106. Further guidance on the use of that term is found in SBA Size Policy Statement No.

1, published in Federal Register on February 20, 1986, 51 FR 6099.

3.5.10. Glossary of Abbreviations and Acronyms. Include a glossary of abbreviations and acronyms used throughout the volume. The Glossary of Abbreviations and Acronyms does not count toward Volume II page limits.

3.6. Section 4 - Factor 3: Corporate Experience and Management. The Offeror’s proposal will be written clearly and contain the pertinent information necessary for the Government to determine if the proposal meets/does not meet solicitation requirements. The Government will evaluate this information in accordance with Section M.

3.6.1. The Offeror's Plan should describe how the Offeror will monitor and manage performance of the requirement spelled out in the PWS across all labor categories and clearly describe and demonstrate how their corporate experience can enable successful implementation of the submitted plan. Offeror’s plans should address key functional areas including:

3.6.1.1. Technical Capability of the Company. The Offeror will describe their company’s familiarity with the scope of this effort, to include, its knowledge of the intelligence, security and computer science/support disciplines outlined in PWS. The Offeror will discuss its previous corporate experience in this line of work, to include, use of COTS and GOTS intelligence analysis software suite of applications.

3.6.1.2. A detailed explanation of how the Offeror will manage its subcontractor(s). To substantiate corporate experience, provide the number of years that the Offeror (not including partners/subcontractors) has managed subcontractors with a list of contracts (by contract number) spanning the provided number of years. Clearly describe how the Offeror’s corporate experience informs effective subcontractor management.

3.6.1.3. The Offeror will describe and specify staff and processes for hiring, recruitment, retention, and marketing that are currently in place or planned to identify qualified labor categories as described in the PWS for this effort. This plan will include all aspects of recruitment from prospect mining to actual deployment to customer locations and any steps in between. This includes, but is not limited to; first contact, screening, interview, and security/credential verification. This plan will include average time (in calendar days) from recruitment to actual deployment to customer location. This plan will describe the Offeror’s ability surge to meet emerging requirements and effectively conduct crisis management. Clearly describe how the Offeror’s corporate experience informs the recruitment and retention plan.

Provide verifiable data, including contract numbers, requirement descriptions, performance dates, relevant Government Points of Contact (Contracting Officer, COR/COTR, or Program Manager), and any other data that substantiates the Offeror’s corporate experience in recruiting and retaining personnel of similar labor categories, with similar security and performance requirements, and position fill-rate requirements.

3.6.1.4. A detailed explanation of how the Offeror will rapidly expand their current operations to meet this contract requirement. Explain in detail the number of managerial layers required to facilitate communication between the Government and the Offeror or managing partner regarding daily operations. Clearly describe how the Offeror’s corporate experience informs their ability to meet the requirements of this contract. Provide verifiable data, including contract numbers, requirement descriptions, performance dates, Government Points of Contact, and any other data that substantiates the Offeror’s corporate experience in providing services of a similar size and scope.

3.6.1.5. Detailed description of how the company will train new employees in compliance with the PWS requirements. Clearly describe how the Offeror’s corporate experience informs the process and procedures for new employee training.

3.6.1.6. The Offeror will describe the average washout rate (the number of proposed candidates

vs. the number approved by the security screening process) the Offeror has experienced historically for the labor categories described in this solicitation, and any mitigation strategies they will use to meet the PWS requirements and strive to meet maximum fill of authorized FTEs.

3.6.1.7. Describe in detail how the Offeror will successfully manage rotation/turnover of personnel during performance of the contract while maintaining maximum fill rates and minimizing degradation in services provided to the customer to include, knowledge transfer (while minimizing overlap of resources), accounting for leave periods and end of tour rotations, and emergency situations. Clearly describe how the Offeror’s corporate experience informs their plan to manage personnel to maintain maximum position fill rates. Provide verifiable data, including contract numbers, requirement descriptions, performance dates, Government Points of Contact, and any other data that substantiates the Offeror’s corporate experience with managing personnel of similar labor categories, with similar security and performance requirements, and position fill-rate requirements.

3.6.1.8. The Key Personnel required and submitted will also be considered as part of the risk to successful execution of the Corporate Experience and Management Factor.

3.6.1.9. The Offeror will describe its recruitment and placement plan which demonstrates how full coverage will be maintained and the methods used to cover unscheduled absences.

4. Volume III - Factor 4: Past Performance. Volume III will be prepared as follows:

Section 1 Table of Contents No Limit Section 2 Recent and Relevant Past Performance Information 3 Pages per Contract

Reference Section 3 Subcontractor or Teaming Partner Consent No Page Limit Section 4 Contractor Performance Assessment Reports (CPARS) No Page Limit Section5 Glossary of Abbreviations and Acronyms No Page Limit

4.1. Section 1 - Table of Contents. A detailed Table of Contents delineating the volume’s subparagraphs. The Table of Contents does not count against Volume III page limits.

4.2. Section 2 - Recent and Relevant Past Performance Information. Submit a list of no more than three (3) recent and relevant contracts performed for Federal agencies or commercial customers as a prime contractor. The contracts list must demonstrate ability to successfully perform the scope and breadth of the requirements described in the solicitation’s PWS. Any excess past performance references beyond the first three submitted will not be evaluated. If a teaming arrangement/Joint Venture is considered, include relevant and recent performance information on previous teaming arrangements/Joint Ventures with the same partner or as this entity (CAGE). If this is a first time joint venture, each party must provide a list of no more than two (2) Government contracts each. The total page limit is three pages per contract.

4.2.1. Recency. Refer to Section M, paragraph 5.2.1.

4.2.2. Relevancy. Refer to solicitation’s Section C and Section M paragraph 5.2.1.1.

4.2.3. Submit the following information for each contract submitted for past performance evaluation:

4.2.3.1. Company/Division name

4.2.3.2. Description of Services Provided

4.2.3.3. Contracting Agency/Customer

4.2.3.4. Contract Number

4.2.3.5. Total Contract Dollar Value (of Offeror's portion if performing as a subcontractor)

4.2.3.6. Period of Performance

4.2.3.7. Verified, up-to-date name, address, e-mail address, telephone number of the Government evaluator, contracting officer or customer POC responsible for procuring your services.

4.2.3.8. If Offeror performed as a major subcontractor, include the specific services and percentage of the contract performed.

4.2.3.9. Explanation of how the scope of the referenced contract is relevant to this solicitation’s PWS. Include rationale supporting the Offeror's assertion of relevance, and how it was determined the work performed was the same or similar in nature, size, and complexity to the work specified in paragraph 4.2.2 above. Identify the staffing full time equivalent (FTE) positions recruited, qualified, managed, and retained, and whether services were provided for SOF, DoD or other Federal agencies.

4.2.3.10. Comments regarding compliance with contract terms and conditions.

4.2.3.11. Comments regarding any known performance deemed unacceptable by the customer, or not in accordance with the contract terms and conditions, the resolution(s) implemented and results.

4.2.3.12. If the Offeror is submitting Past Performance information for, or in any way regarding, predecessor companies, key personnel who have relevant experience, or subcontractors that will perform major or critical aspects of the requirement, the Offeror will provide details as to what the predecessor companies, key personnel, or subcontractors participation was in the example past performance provided, and precisely how the predecessor companies, key personnel, or subcontractors will perform this effort.

4.2.4. If the Offeror claims there is no past performance, notification of this fact must be included in Volume III, Past Performance.

4.3. Section 3 - Subcontractor or Teaming Partner Consent and Client Authorization.

4.3.1. Subcontractor or Teaming Partner Consent Letter (if required). Past performance information pertaining to a subcontractor or teaming partner cannot be disclosed by the prime contractor without the subcontractor's/teaming partner's consent. Provide, with the proposal, a letter from all subcontractors (Attachment 5) that will perform major or critical aspects of the requirement, consenting to the release of their past performance information to the prime contractor. The Subcontractor or Teaming Partner Consent Letter does not count toward Volume III page limits.

4.3.2. Client Authorization Letter (if required). Each Offeror, subcontractor, teaming partner, and/or joint venture partner will execute a Client Authorization Letter for commercial customers similar to Attachment 5.

4.4. Section 4 - Contractor Performance Assessment Reports (CPARs). Offerors, including teaming partners or subcontractors proposed to perform 20% or more, will submit a copy of their CPARs for their recent and relevant contracts submitted in paragraph 4.2 above. CPARS do not count toward Volume III page limits.

4.4.1. Adverse Past Performance Information. If adverse performance information exists (i.e.

Marginal or Unsatisfactory ratings), the Offeror will submit, with its proposal, a response to the adverse performance review. It is the Contractor's responsibility to ensure it addressed adverse performance ratings on their recent and relevant performance record. Failure to do so may result in the evaluation team accepting the performance record as written in the CPARS.

4.5. Section 5 - Glossary of Abbreviations and Acronyms. Include a glossary of abbreviations and acronyms used throughout the volume. The Glossary of Abbreviations and Acronyms does not count toward the Volume III page limits.

4.6. Past Performance Questionnaires. The Offeror will send a copy of Attachment 6 - Past Performance Questionnaire (PPQ) to the Contracting and Technical POCs identified by the Offeror for each contract reference. When sending PPQs to each contract reference, the Offeror should courtesy copy the Contracting Officers identified in paragraph 2. above. If the Contractor received a CPARS rating for the past performance effort being submitted, the Contractor may attach a copy of the finalized CPARs in lieu of the PPQ. The POCs will submit the PPQs, by email, directly to the Contracting Officers identified in Section 2. above.

4.6.1. Offerors will ensure the PPQ is sent to allow sufficient time for the POCs to complete and provide back to this office prior to the RFP closing date and time. It is the Offeror's responsibility to encourage the POCs to complete and submit the PPQ in a timely manner. If PPQs or CPARS assessments are not received, by this office, by the closing date, the Government is not obligated to make additional attempts to obtain the information.

4.6.2. At Volume III, Past Performance, Offerors will indicate which technical/Contracting Officer POC the questionnaire was transmitted to, and confirm the questionnaire was received.

4.7. Early Past Performance Submission. To permit the past performance evaluation team to conduct its assessment more efficiently, Offerors are requested to submit their past performance volume five (5) calendar days prior to the solicitation closing date and time. Failure to submit past performance information early will not result in Offeror disqualification. As the past performance questionnaires direct respondents to submit responses directly to the Contracting Officer, the past performance volume will only include information up to Section 5 of Volume III as identified above.

5.0. Volume IV - Factor 4: Price. Volume IV will be prepared as follows:

Table L-9: Volume IV Price

Section Title Page Limit Section 1 Cover Letter No Page Limit Section 2 Table of Contents No Page Limit Section 3 Price Proposal Support No Page Limit Section 4 Price Proposal Worksheet No Page Limit

5.1. Offerors must ensure pricing information is included in Volume IV. Do NOT include pricing information in Volumes II and III.

5.2. Section 1 - Cover Letter. Offerors will include a single page cover letter with their price proposal signed by an authorized negotiator with signatory authority for the Offeror. The cover letter will include:

5.2.1. Offeror's CAGE Code.

5.2.2. Offeror's DUNS and TIN/EIN number.

5.2.3. Offeror's DCAA and/or DCMA points of contact to include: name, phone number, email address.

5.2.4. Name and DUNS number of any subcontractors anticipated to work under the contract.

5.3. Section 2 - Table of Contents. A detailed Table of Contents delineating the subparagraphs within the volume.

5.4. Section 3 - Price Proposal Support

5.4.1. The burden of proof for credibility of proposed costs/prices rests with the Offeror. To support price reasonableness, Offerors will describe and provide the basis for their proposed direct and indirect rates and factors and provide narrative support for all elements. This includes all direct and indirect factors, to include, profit for the prime and all teaming members. Offerors must, if used, include the escalation factors used from the base year to all out year periods.

5.4.2. The method to develop the basis of proposed prices narrative will be fully explained so the Government can readily identify how each computation was made. All indirect rates and factors should be fully explained as to the method and base of application. Offerors are expected to use their customary formats and calculations consistent with their normal accounting practices to develop the burdened rates.

5.4.3. Certified Cost or Pricing Data. As this is a competitive acquisition with anticipated adequate price competition, certified cost or pricing data in accordance with FAR 15.403-1 is not required. However, in the event that adequate price competition does not exist after receipt of proposals, the Government reserves the right to request additional cost or pricing data, as necessary, from both the Offeror and subcontractors. Further, pursuant to FAR 15.406-2, the Offeror may be required to provide a Certificate of Current Cost or Pricing Data prior to award.

If subcontractors are proposed, they will provide the same information required for the prime contractor, unless otherwise noted. If only one offer is received, DFARS 252.215-7008, Only One Offer, will apply.

5.5. Section 4 - Price Proposal Worksheet, Attachment 7.

5.5.1. Offerors will complete and submit Attachment 7 - Price Proposal Worksheet. This worksheet calculates the Offeror's Proposed Price and Total Evaluated Price (TEP). Offerors will use its proposed fully burdened labor rates, man hours, and Contractor Manpower Equivalents (CME) to assist in calculation of the TEP.

5.5.2. Offerors will follow the directions listed on the “instructions” tab of Attachment 7. Both the FBLR Table tab and See Project FBLR Table tabs will be completed and submitted as part of Volume 4, Price.

5.5.2. All unit and extended prices provided will be rounded to no more than two positions after the decimal point. Extended prices must be divisible by the number of units proposed.

5.5.3. Missing or incomplete cost/pricing data may result in proposal rejection.

5.5.4. Offerors will ensure their price proposal is consistent with the technical proposal in all respects since the price proposal will be used during the technical evaluation as an aid to determine the Offerors' understanding of the requirements. Discrepancies may be viewed as a lack of understanding and may result in proposal rejection. Price proposals deemed excessively low and/or excessively high may be rejected.