W900KK20R0004_Amend 0003_Mod_06232020.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

See Clause 52.252-3 for the purpose of Amendment 0003.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 30

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 23-Jun-2020

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W900KK20R0004

X 9B. DATED (SEE ITEM 11)

27-Feb-2020

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

23-Jun-2020

CODE

ARMY CONTRACTING COMMAND - ORLANDO

ATTN: ECHO DIVISION

12211 SCIENCE DRIVE

ORLANDO FL 32826-3224

W900KK 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W900KK20R0004

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION A - SOLICITATION/CONTRACT FORM

The number of offeror copies required has decreased by 1 from 2 to 1.

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

*******NOTE: Insourcing for some of the support services stated in this requirement will occur after award.

The Government does not have specific data at this time to incorporate into this solicitation. Negotiations will be conducted with the awardee of this effort, after contract award, when the specifics have been defined.

******** (Amend 0002).

L.1.0. Proposal Submission

L.1.1 Introduction. The Staff Technical Assistance and Functional (STAF) effort is being competed as Small

Business set-aside 8(a) Competition under NAICS code 541611, Administrative and General Management

Consulting, with a size standard of $15M in average annual receipts. The STAF effort will be a Single Award (SA)

Indefinite Delivery Indefinite Quantity (IDIQ) contract to provide administrative, project management, and technical staff support services consisting of a 1-month phase-in period, 11-month base period of performance, and four 12-month option periods for a total of 60 months.

Volume I – Factor 1 proposals are due no later than the date and time annotated on the SF 33 coversheet. Early delivery is authorized.

The required method of STAF proposal delivery is via the DoD Secure Access File Exchange (SAFE) located at https://safe.apps.mil/. Offerors shall ensure the recipients receiving the proposal submitted via DoD SAFE are the

STAF Primary Point of Contact (POC), Alternate POC, and the Procuring Contracting Officer (PCO), identified in

Section L.2.8.

Offerors are encouraged to test the DoD SAFE proposal exchange methodology by sending a copy of the STAF

PWS to the aforementioned POCs at least 72 hours prior to the proposal due date/time. The Government will confirm receipt, via email, within one business day. If confirmation email is not received, please coordinate directly with the PCO to resolve issue.

If there are any technical difficulties with DoD SAFE, the Offeror shall coordinate an alternate method of STAF proposal submittal with the Primary POC, no less than 24 hours prior to the due date and time. It is the Offeror’s responsibility to ensure that the entire proposal is received by the Government prior to the proposal due date and time. All proposals submitted must be in compliance with the full solicitation.

L.1.2 Phased Acquisition Approach

The Government will evaluate Offerors’ proposals in a two phased approach to progressively reduce the number being considered for contract award. The purpose of this procedure is to reduce the time and cost of source selection, both for the Government and for the competing Offerors.

Phase I: Offerors shall prepare and submit ONLY Volume I – Factor 1 – Security Reference (Amend 0002) and

Volume II – Factor 2 – Technical Experience (Amend 0002) proposal in accordance with the instructions provided below. The Government will evaluate each volume in accordance with the acceptability criteria in Section M of this solicitation. The Government will eliminate from further consideration any Offerors proposals evaluated and assigned an unacceptable rating.

The decision to eliminate any Offeror through this procedure will not constitute the establishment of a competitive range, as described in FAR 15.306(c), and it will not obligate the Government to conduct discussions or to solicit or entertain proposal revisions. FAR 15.202(b) the last sentence states, “The agency shall inform all respondents that, notwithstanding the advice provided by the Government in response to their submissions, they may participate in the resultant acquisition.” This sentence does not apply to those offeror eliminated from Phase I. However, the

Government reserves the right to establish a competitive range and conduct discussions if the PCO decides that it is in the best interest of the Government to do so.

Phase II: Offerors with an Acceptable Phase I proposal will be notified by the PCO and requested to submit , Volume III – Factor 3 – Program Management, Volume IV – Factor 4 – Past Performance, and Volume V – Factor

5 –Cost/Price, and Volume VI – Administrative/General (Amend 0002) Information of the proposal in accordance with the instructions established below and within the notification.

L.1.3 Proposal Validity: The Government requires that the proposal, in its entirety, be valid for at least two hundred and seventy (270) calendar days from the final, phase II proposal due date which will be annotated in the

PCO notification referenced in the above paragraph. Offerors are cautioned that for their proposal to be eligible for award, the proposal shall be in compliance with the terms and conditions set forth in the solicitation. The Offeror shall insert the validity date in Block 12 of the SF 33.

L.1.4 The Offeror’s proposal shall consist of five (5) volumes:

PHASE I

Volume I – Factor 1 – Security Reference (Amend 0002);

Volume II – Factor 2 – Technical Experience (Amend 0002)

PHASE II

Volume III – Factor 3 – Program Management:

Subfactor 3.1 Program Management Plan

Subfactor 3.2 Phase-in/Phase-out Approach

Volume V – Factor 4 Past Performance (Amend 0002)

Volume V – Factor 5 Cost / Price

Volume VI – Administrative/General Information. (Amend 0002)

L.1.5 All proposals must clearly and convincingly demonstrate that the Offeror has a thorough understanding of the entire requirement and associated risks; is able, willing, and competent to devote resources necessary to meet the requirement; articulates a specific detailed approach with sufficient information, details, procedures and techniques to support the determination that the Offeror has a valid and practical solution for the requirement. Statements that the prospective Offeror understands, can, or will comply with the requirements, and statements paraphrasing the requirements or parts thereof without supporting information/narrative are considered inadequate and unsatisfactory.

Mere reiteration of the requirement or standard reference material is discouraged and is considered inadequate and unsatisfactory. The Offeror must include any data necessary to illustrate the adequacy of the various assumptions, approaches, and solutions to problems. In presenting material in the proposal, Offerors are advised that quality of information is more important than quantity. Offerors are encouraged to use quantitative terms wherever possible and avoid the use of qualitative and subjective terms to the maximum extent practicable.

L.1.6 Offerors are cautioned that while the Government will not evaluate every PWS requirement for the purposes of the source selection evaluation, the awardee/Contractor will be required to comply with all PWS requirements during performance of the contract. The Offeror’s proposal shall describe its approach to implementing PWS requirements that are being evaluated.

L.1.6.1 The proposal shall reference the related paragraphs of the PWS (e.g. 3.1.2) and Section L, and provide the detail necessary to substantiate the proposed approach and methodology for performance. The proposal should identify any unique or innovative approaches which ensure successful performance.

L.1.7 The Government will determine that an Offeror's proposal is non-compliant, and therefore ineligible for award, if the proposal indicates that: it cannot or will not meet all the requirements; takes unreasonable or unjustifiable exception to any of the terms and conditions of the solicitation; provides an approach that clearly does not meet any of the requirements; or, includes data which prompts the Government to question the Offeror's compliance with any of the requirements. The Source Selection Authority may reject all proposals received in response to a solicitation, if doing so is in the best interest of the Government. Offerors are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal. Proprietary information shall be clearly marked.

L.1.8. If an Offeror believes that the solicitation contains an error, omission, or is otherwise unsound; the

Offeror shall immediately notify the Contract Specialist and PCO stated in L.2.8 in writing with supporting rationale prior to the solicitation closing date and time.

L.2. PROPOSAL SUBMISSION REQUIREMENTS

L.2.1 Failure to submit documents in the correct format is grounds for non-compliance determination, at the sole discretion of the PCO.

L.2.2 It is the sole responsibility of the Offeror to ensure that the electronic files submitted are virus free and can be opened and read by the Government. Proposal submissions shall not be locked, encrypted, or otherwise contain barriers to opening. All files shall be clearly identified with a filename appropriate to the content (e.g., Volume-

I_Security Reference__Attachment_1). Use separate files to permit rapid location of all portions of the proposal, including exhibits, annexes, and attachments, if any. Compressed files are not allowed. When submitting proposals, Offerors shall follow these instructions.

L.2.3 File Packaging. All of the proposal files shall be separate documents in their native format; i.e. xls, doc, ppt,.

In addition, an Adobe Portable Document Format (PDF) version of all electronic documents, other than the Volume

IV – Factor 4 –STAF Price Workbook, shall also be included as separate volumes (Amend 0002) as a control copy.

Control Copy shall be in the title of the files after the name of the volume as stated below (Amend 0002). All price breakdown information to aid in the cost/price evaluation shall be submitted in Microsoft Office Excel Read/Write format, showing all formulas and calculations with no hidden/locked cells (Amend 0002) and viewable in Microsoft

Excel 2013. Please note – Self extracting .exe files are not acceptable. PDF documents shall use Adobe Acrobat 9.0 or later. Do NOT submit main documents in the PDF “image.” Teaming Agreements, Letters of Intent (Amend

0002) or Letters of Commitment may be in the image format and must be readable (Amend 0002)

L.2.4 All proposal files shall be verified to be free of any virus or malware.

L.2.5 All submitted files (MS Office and PDF) shall be created with textual search and copy functions enabled.

Non-searchable signature pages are acceptable, but other submitted materials that are not searchable may not be evaluated, and the Offeror may be determined non-compliant, at the sole discretion of the PCO.

L.2.6 The following volumes of material shall be submitted:

VOLUME TITLE

PAGE LIMIT

I – Factor 1 - Security Reference Complete Security Reference Workbook, Solicitation Attachment 2. Amend 0002 deleted language)

II – Factor 2 – Technical Experience Technical Experience Workbook, Solicitation Attachment 3. All information/narrative shall be documented in the space provided in the workbook space provided.

Technical Experience Evidence – No page limit

III – Factor 3 –Program Management

Subfactor 3.1 – Program Management Plan

Subfactor 3.2 – Phase-in / Phase-out Approach

40 Pages

IV – Factor 4 – Past Performance Unlimited (Amend 0002)

V – Factor 5 – Cost/Price Unlimited

VI – Administrative/General Information Unlimited

NOTE: Pages that exceed the required page limitations will not be evaluated. Additional pages over the maximum allowed will be removed or not read and will not be evaluated by the Government. Documents submitted in their native format will be the official version and take precedence over PDF control copy (e.g. difference in page count and/or content)

L.2.7 Acronym lists, cover pages, title pages, table of contents, cross reference matrices, dividers, index tabs, and lists of tables or figures will not be counted as part of the page count, so long as they are inserted solely for the purpose of reading ease and locating sections of the proposal. Pages marked: "This page is intentionally left blank" will not be counted nor evaluated. Additionally, teaming agreements, letters of commitment, letters of Intent

(Amend 0002) and the Contractor work breakdown structure, attached to their respective volume, will not be counted as part of the page count.

L.2.8 STAF solicitation Points of Contact:

Primary:

Isabel Rodriguez

Contract Specialist

U.S. Contracting Command – Orlando

12211 Science Drive, Orlando, FL 32826-3224

Ofc: (407) 384-3709 isabel.m.rodriguez12.civ@mail.mil

Alternate:

Jey Jeyasingam

Contract Specialist/Procuring Contracting Officer

U.S. Contracting Command – Orlando

12211 Science Drive, Orlando, FL 32826-3224

Ofc: (407) 384-5113 jeyanthan.jeyasingam.civ@mail.mil

Procuring Contracting Officer

Gloria E. Bailey

Branch Chief/Contracting Officer

U.S. ARMY Contracting Command - Orlando

12211 Science Drive, Orlando, FL 32826-3224 gloria.e.bailey2.civ@mail.mil

L.2.9 Beneficial features offered beyond the requirements of this solicitation will be incorporated into the awardee’s contract and subsequent Task Order. The Offeror will be expected to perform based on the entire proposed approach, including any over-and-above features and/or merits contained within its proposal.

mailto:jeyanthan.jeyasingam.civ@mail.mil

L.2.10 If there are any questions resulting from this solicitation, each respective Offeror shall coordinate its questions through one company representative. The Government will provide responses to these questions via the

Government Point of Entry in which the solicitation was posted or email to all Offerors. All questions regarding the solicitation shall be submitted in writing, via email, to the STAF solicitation Primary and Alternate POCs identified within Section L, NLT 1400 hours EDT 7 calendar days after the solicitation Amendment 0002

(Amend 0002) issue date annotated on the SF 33 coversheet. The Government will respond to questions/comments specific to Phase I prior to the proposal due date for Phase I. Responses specific to questions/comments regarding

Phase II of the solicitation may be provided by the Government after the Phase I due date and prior to the Phase II due date. Offerors with an acceptable Phase I proposal will be afforded an additional opportunity to submit questions/comments regarding Phase II; specific instructions will be within the PCO notification referenced in L.1.2

Phased Acquisition Approach (Amend 0002). The subject line of the email for Offeror’s questions/comments shall include the Solicitation number, W900KK-20-R-0004. Questions/comments shall be submitted using the RFP attachment 7 entitled, “Question/Comment Form.”

L.2.11 Information previously submitted to the Government should be assumed unavailable during this proposal evaluation and source selection process. Proposals submitted will not be returned. Alternate proposals will not be evaluated or accepted.

L.2.12 In accordance with FAR Subpart 52.215-1, Instructions to Offerors – Competitive Acquisition, the

Government intends to evaluate proposals and award a contract without discussions with Offerors (except clarifications as described in FAR 15.306(a)). Therefore, the Offeror’s initial proposal should contain the Offeror’s best terms from a cost or price and technical standpoint. However, the Government reserves the right to conduct discussions if the PCO later determines them to be in the best interest of the Government. The PCO will schedule the discussion sessions, and each Offeror within the competitive range will be notified of the time and place. The

PCO will provide additional instructions with the notification.

L.2.13 If the PCO determines that the number of proposals that would otherwise be in the competitive range exceeds the number at which an efficient competition can be conducted, the PCO may limit the number of proposals in the competitive range to the greatest number that will permit an efficient competition among the most highly rated proposals. Clarifications are not discussions. Offerors may be given the opportunity to clarify certain aspects of the proposal or resolve minor or clerical errors (see FAR 15.306(a)(1) and (2)). (Deleted language Amend 0002)

L.2.14 Any proprietary information submitted separately for major Subcontractors shall be furnished in the same format, level of detail, and submission due date as prescribed for the prime Offeror. A Subcontractor is considered a

Subcontractor executing at least 10% of the total proposed value. Subcontractor proposals submitted separately are considered part of the Offeror’s proposal, including the page count. All Subcontractor proposals submitted separately must identify the prime Contractor and be clearly marked in accordance with (IAW) L.2 and L.3. If

Subcontractor proposals are late or not in accordance with the other submission requirements, the entire proposal may be considered non-compliant.

L.2.15 A Major Subcontractor is considered a Subcontractor, Joint Venture, parent company and/or affiliate company executing at least 10% of the total proposed SA IDIQ contract value (Amend 0002).

L.3 PROPOSAL FILES

L.3.1 Format. The submission shall be clearly indexed and logically assembled, including the completed solicitation attachment 5, Cross-Reference Matrix within Volume III – Factor 3 – Program Management proposal.

A Table of Contents should be created to delineate the paragraphs and subparagraphs within that volume. As annotated above, the Cross-Reference Matrix and Table of Contents does not count against that volume’s respective page limitations. Tab indexing shall be used to identify sections, blank pages may be used and will not count against the page count.(Amend 0003). Standard proposal text format shall be 12 point Arial or Times New Roman font.

All pages of each volume shall be appropriately numbered (X of Y) and shall contain the company name, date and solicitation number in the header and/or footer. Pages shall be numbered sequentially within each volume. All pages shall be marked: “SOURCE SELECTION INFORMATION -- SEE FAR 2.101 AND 3.104” in the footer.

Additional data use restrictions shall be located in the header/footer area of each page where applicable. The signed

Standard Form (SF) 33, each SF30 – as applicable – and Section K – Certifications and Representations may be submitted in Adobe.pdf file format. Microsoft Word and PDF files shall use the following page setup parameters:

Margins – Top, Bottom, Left, Right – 1”

Gutter – 0”

From Edge – Header, Footer 0.5”

Page Size, Width – 8.5”

Page Size, Height – 11”

Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible and can utilize an alternate paper size of 11x17, if necessary. For page-count purposes, each side of an 11x17 page with content will count as two pages.

Format requirements provided in this section do not apply to Government provided documents, such as: SF forms, Section K clauses (Amend 0002), DD254, Pricing, Technical Experience References, Security References (Amend

0002), Deleted language Amend 0002, etc. Additionally, attachments to the proposal, such as: Teaming agreements, verification documents for Vol VI, etc., are not required to be compliant with the format requirements.

L.3.2 Cross-Reference Matrix –The intent of the attached Cross-Reference Matrix is to ensure that all requirements for Volume III - Factor 3 - Program Management are addressed and easily accessible to evaluators.

The Cross-Reference Matrix must provide a single integrated index for the corresponding proposal Volume/Factor.

The Cross-Reference Matrix is to assist evaluators during the evaluation; however, the Cross-Reference Matrix will not be evaluated.

L.3.3 Compliancy Screening. The proposal volumes will be reviewed for compliance in accordance with the

Instruction to Offerors provided in Section L (Amend 0002 Deleted language).Failure of an Offeror to provide all requested proposal information may render the Offeror's proposal non-compliant, and as such, the Offeror's proposal will not be evaluated, at the sole discretion of the PCO. If determined to be non- compliant, the PCO will notify the

Offeror as soon as practicable.

L.3.4 The Offerors shall ensure that each proposal volume submitted contains only the information relevant to that specific volume. The Offerors are cautioned that each volume of the proposal is evaluated standalone against the criteria set forth in Section M and the evaluators for one volume may be different than the evaluators of another volume. It is incumbent upon the Offerors to ensure they properly submit their proposals. If the data is not contained in the appropriate volume of the proposal, it will not be evaluated. The Government will consider information it requires for proposal evaluation not found in its designated volume as the Offeror having omitted it from the proposal. No cost information shall be included in the Program Management volume of the Offerors proposal. No

Program Management information shall be included in the Cost volume of the Offerors proposal. Files shall not contain classified information.

L.4.0. Volume I – Factor 1 – Security Reference

L.4.0.1 The Offeror shall provide Security Reference information within attachment 2 (Amend 0002) which demonstrates current possession of an Active Facility Security Clearance (FCL) for the Prime as stated and required by the contract DD254 at the time of the proposal. Submission. Reference: TO 0001 & 0002 PWS Section 1.8, Security (Amend 0002).

Note: At the time of proposal submission both companies and/or entities forming the Joint Venture must have a Top Secret Facility Security Clearance.

Additionally, if the CAGE Code provided for the Prime does not correlate to current valid required FCLs, no further review or evaluation will be completed (to include Factor 2, Technical Experience) and the proposal will be deemed unacceptable and unawardable and will not receive (Amend 0002) continued evaluation.

(Amend 0002 deleted language).

L.4.1. Volume II -- Factor 2 – Technical Experience

L.4.1.1 This volume shall contains technical experience information. The Offeror's shall provide no more than four projects/ (Amend 0002 deleted language) contracts on which the Offeror served as either the prime, subcontractor or as a Major Subcontractor, during the past three years of this solicitation issuance date, which are relevant to the efforts required by this solicitation. Each submitted reference shall defined whether the work was done as a prime, subcontractor or Major Subcontractor. No more than four technical experience references will be considered and evaluated. If more than four technical experience references are submitted, the Government will evaluate the first four consecutive submissions; any additional references will not count towards meeting the requirement and will not be evaluated (Amend 0002).

(Deleted Language Amend 0002)

Technical Experience shall be submitted using Solicitation Attachment 3 entitled, “Technical Experience Reference

Workbook.” Each reference submitted shall clearly delineate how the referenced project is relevant experience performing (Amend 0002) the following STAF Core Experience areas:

a) Experience executing a service contract with services managing a workforce in excess of 40 Full-Time

Equivalent Contractor personnel required to have and maintain a security clearance (ranging from a Secret to Top Secret and Specialized Compartmentalized Information). Reference: TO 0001 and 0002 PWS

Section 1.8.2; TO 0002 PWS section 5 (Amend 0002)

b) Experience executing a service contract with administrative, Program Management, and Technical services in support of DoD training centers of excellence (or comparable, to include non-DoD) and/or Combat

Training Centers (CTCs). Government agencies or organizations considered “comparable” to DoD COEs and CTCs will be any organization and/or agency aligned within a formal federal chain of command and tasked with a national security mission requiring Contractor support in a classified environment. This may include organizations and agencies such as the Defense Intelligence Agency (DIA), National Geospatial

Agency (NGA), etc. as described in STAF PWS paragraph. Reference: TO 0001 and 0002 PWS Section

1.8.2; TO 0002 PWS section 5 (Amend 0002).

c) Each Technical Experience reference submitted in support of any of the above letters (a) through (b) shall have been gained during a period of at three years of the solicitation release date and has at least 12 months of performance completed (Amend 0002).

L.4.1.2 Offerors shall submit Technical Experience References using the attached Technical Experience Reference

Workbook. At least one of the up to four Technical Experience references shall provide verifiable experience for

Section L.4.1.1 paragraphs (a) thorough (c) to be rated as Acceptable. If the Offeror’s referenced projects submitted fail to provide evidence of technical experience in the STAF Core Experience areas defined in both a) and b) above or does not meet the criteria stated in paragraph (c), no further review or evaluation will be completed and the proposal will be deemed unacceptable and unawardable and will not receive continued evaluation. These requirements may be met separately or in the up to four Technical Experience References submitted. (Deleted language Amend 0002)

L.4.1.3 An overarching Indefinite Delivery / Indefinite Quantity (ID/IQ) base contract, Blanket Purchase Agreement

(BPA), or Basic Ordering Agreement (BOA) shall not be submitted as an individual Technical Experience

References reference. Offerors may submit an order issued from a single ID/IQ contract, BPA, or BOA as one

Technical Experience Reference to show experience in each relevant area. Each Technical Experience Reference shall comply with the criteria established within this solicitation.

L.4.1.4 Technical Experience References may include references of the Offeror’s proposed Major Subcontractors for this effort. Joint Ventures may include references executed by individual member(s) of the Joint Venture.

(Amend 0002 deleted language)

(Amendment 0002 Deleted Language)

L.4.1.5 (Deleted language Amend 0002) The Offeror shall include applicable verification documents, which unambiguously and sufficiently validate the individual Technical Experience References submitted. Examples (not an inclusive list) of such documents would be: a copy of the contract with this requirement (with POC information), a copy of the Subcontractor proposal/contract with the prime that has the requirement (with POC information), signed contract surveillance reports, other documents that can show the link between the requirements of this solicitation and performance on that effort (Amend 0002). When a Technical Experience Reference submitted was executed in the capacity of a Subcontractor, the Offeror shall ensure the applicable verification documents patently differentiate the Subcontractor’s Technical Experience from the prime Contractor’s Technical Experience. Failure to provide verifiable documents, which unambiguously and sufficiently validate the individual Technical Experience, will result in the Government not considering the individual submittal for evaluation.

L.4.1.6 If the Technical Experience Reference was accomplished through a Teaming agreement(s) and/or Joint

Venture, the agreement documentation shall be submitted with this Volume. Agreements shall be submitted and bilaterally signed, by authorized representatives from each organization, for all major Subcontractors or individual members of the team or of the JV citing their Technical Experience in this Volume. The Technical Experience shall reference the appropriate agreement that is submitted in this volume. (Amend 0002)

L.4.2 Volume III -- Factor 3 – Program Management

The Offeror shall prepare and submit a standalone Program Management Volume organized IAW the factor description below. All general assumptions concerning the proposal shall be stated in this volume as well as the

Cost/Price volume. No cost/price data shall be included in this volume.

This volume provides Offerors with an opportunity to demonstrate their approach in meeting the solicitation requirements. While Offerors will not be evaluated on all requirements of the STAF PWSs, they must comply with and be able to accomplish all PWS requirements throughout the life of the contract.

** NO COST/PRICE INFORMATION SHALL BE INCLUDED WITHIN THIS VOLUME. **

L.4.2.1 Subfactor 3.1 Program Management Plan

The Program Management Plan shall contain all of the elements outlined below.

L.4.2.1.1 Management Structure. Offeror must provide a realistic approach to creating and depicting its management structure for the geographically separated sites in the required area of operation, from general staff oversight by first line supervisors, through its local organizational structure to the company headquarters management. Key Personnel resumes ONLY with names redacted, shall be submitted with this volume. They shall not contain any salary information or other information as specified in L.4.3.5. Reference TO 0001 PWS 1.6-1.6.2, 1.7, 2.2 and 5.1.11, and TO 0002 PWS 1.6-1.6.2, 1.7(Amend 0002).

L.4.2.1.2 Recruitment and Retention Plan:

The Offeror shall describe the methodology to be employed by the Offeror to recruit, retain, and develop personnel with the requisite knowledge, skills, education, experience and clearances to ensure successful accomplishment of

STAF PWSs. At a minimum, the plan shall address, for the STAF contract: how lessons learned will be incorporated to improve recruitment and retention practices; describe recruitment and hiring practices that will be used for this contract; process and procedures for addressing performance issues; process for ensuring individuals are trained properly to perform PWS requirements; process for ensuring continuity and quality services during personnel absences due to leave, terminations, and resignations to ensure the impact to the Government mission is minimal or non-existent; and any other processes, business practices, personnel management resources and/or methodologies to maintain a qualified pool of candidates to ensure a stable workforce over the life of the contract. IDIQ PWS

Reference: 5.3.1 and TO 0001 PWS Reference: 5.1.11

L.4.2.1.3 Contractor Work Breakdown Structure (CWBS). Within Microsoft Project, the Offeror shall provide, as an attachment to this volume, a CWBS with all proposed labor categories executing performance-based requirements within the Task Order PWSs. Each CWBS shall identify, for the proposed labor categories, clearly defined lines of responsibility, clearly defined levels of decision authority, reporting structures, location of personnel, and the communications/interfaces (e.g., Contractor/Subcontractor to Government, Prime to

Subcontractor, Prime to Site/Site Manager, and Subcontractor to Site/Site Manager).

CWBS shall clearly articulate the Contractor’s approach to satisfy all Task Order requirements and must identify the following:

a) Labor categories, broken out by PWS section

b) Number of personnel for each labor category, broken out by PWS section

c) Number of hours proposed for each category, broken out by PWS section

d) Provide a copy of worksheet 1b from cost/price workbook with this volume with columns J, K, L, M and N deleted. (no cost/price data shall be submitted in this volume (Amend 0002)

e) Provide a copy of worksheets 2b and 2c with labor categories and labor hours – NOT COST data shall be included in these worksheets (Amend 0002)

CWBS rationale and assumptions: Within this the Volume, the Offeror must provide its overarching methodology for determining its proposed Qualifications by Labor Category and assumptions supporting staffing decisions or explanations needed to clarify staffing decisions made in order to ensure proper execution of the effort. The numbers of hours, personnel and labor categories must match the number of hours, personnel and labor categories in the

Offeror’s Cost/Price Workbook. The Offeror shall provide rationale and calculations that clearly identify the methodology used to arrive at the labor categories, number of personnel, and/or proposed hours for each labor categories proposed to meet the requirements in the TO PWSs.(Amend 0002) Task Order 0001 and 0002 PWSs in totality. (Amend 0002) *******No cost/price data shall be included in this volume. *******

No cost/price data shall be included in this volume.

L.4.2.1.4 Management Methodology. As part of its Program Management Plan, the Offeror shall:

a) Describe their methodology and approach to managing multiple Subcontractors, joint venture, and/ or teaming partners in order to execute multiple requirements;

b) Describe their methodology and approach to managing its workforce alongside the workforces of other

Contractors in shared spaces;

c) Describe their methodology and approach to providing on-site management with authority, flexibility and the efficiency to quickly and effectively resolve all performance-related issues; and

d) Identify risks and corresponding risk-mitigation strategies that will be employed during execution.

Task Order 0001 PWS Reference 1.6.2 – 1.6.5.3, 1.7, 2.2, 2.3 - 2.3.2.1, and Section 5 – with special focus on 5.1.11;

TO 0002 PWS Reference: 1.6.2 – 1.6.5.3, 1.7, 2.2, 2.3 - 2.3.2.1, and Section 5, (Amend 0002)

L.4.2.1.5 Quality Control Plan. Each Offeror shall provide a STAF Quality Control Plan (i.e., onsite quality control procedures) capable of providing continuous improvement and problem resolution in coordination with local management and supported Government unit and/or higher headquarters.

Task Order 0001 PWS Reference: 2.3.3, 5.1.7, and 5.1.11; Task Order 0002 PWS 2.3.3 (Amend 0002)

L.4.2.1.6 Joint Venture/Teaming or Major Subcontracting Arrangements. Each Offeror shall provide, if applicable, a summary describing the joint venture or subcontracting arrangement established for this solicitation as well as a bilaterally signed document (format as established by Offeror) specifying an agreement (e.g., Teaming

Agreements) among the parties. Offeror shall identify for each proposed team member/Subcontractor: a) what PWS section each joint venture team member/Subcontractor will support; b) the team member/Subcontractor’s name; c) the actual services to be provided; d) the percentage of work it will perform. The Teaming Agreements shall be attached to this volume and are not included in the page count.

Task Order 0001 and TO 0002 PWSs 2.2 - 2.3.2.1; TO 0001 PWS 5.1.11 (Amend 0002)

L.4.2.2 Subfactor 3.2: Phase-in / Phase-out Approach:

L.4.2.2.1 Phase-in. The Offeror shall provide a 30-day Phase-in approach that provides for continuity of STAF operations with no loss of service and minimal loss of operational knowledge. The plan shall address the following elements:

a) Detailed 30-day Milestone Chart

b) Identification of any risks and describe how those risks will be mitigated

c) Approach to ensure open communication with incumbent Contractor and the Government to include periodic meetings documenting progress

d) Personnel plan describing how the Contractor will provide personnel in order to assume Full

Performance after the Phase-in period, as required by this PWS

e) Approach to ensure proper, timely issuance of (as required): appropriate licenses, installation badges and Installation Access security clearances

f) Requirements Turnover/Handoff

g) Data and/or Property Transfer

h) Security Requirements to include OPSEC

TO 0001 and 0002 PWS Reference: Section 1.8.1, 1.8.2, 1.8.3, Section 1.9, and 2.3.5 (Amend0002)

L.4.2.2.2 Phase-out. The Offeror shall provide a Phase-out approach that provides for continuity of STAF operations with no loss of service and minimal loss of operational knowledge. The plan shall address the following elements:

a) Detailed Milestone Chart

c) Approach to ensure open communication with incoming Contractor and the Government to include periodic meetings documenting progress

d) Personnel plan describing how the Contractor will support the transition of personnel to incoming

Contractor

e) Requirements Turnover/Handoff

f) Data and/or Property Transfer

g) Security Requirements to include OPSEC

TO 0001 and 0002 PWS Reference: Section 1.8.1, 1. 8.2, 1.8.3, Section 1.9, and 2.3.5 (Amend 0002)

L.4.3 Volume V -- Factor 4 – Past Performance

This volume shall contain past performance information regarding similar contracts for up to four (4) (Amend 0003) recent and relevant (as defined in Section L.4.3, L.4.3.1 and M.4.3) past performance references. Proposal data supporting this submission shall not be incorporated into the proposal by referring to another proposal or other source. This volume this volume has an unlimited page count but should include an Executive Summary of 1 page, Table of Contents of 1 page, and Cross Reference Matrix of 1 page.

At least one of the past performance references shall be that of the Prime offeror. The Prime Offeror’s references must be where they performed either in a Prime contractor capacity, or as a major subcontractor capacity, or in the case of a Joint Venture (JV) member. Two (2) references may be that of major Subcontractor Team Member(s), as defined in L.4.3.3, who are represented by a major portion of the labor mix detailed for this effort and where their citation must be of that also performing in either a Prime contractor, or major subcontractor capacity.

L.4.3.1 Recent Past Performance. Recency is defined as past performance gained within the past 3-years from the date of solicitation issuance and that has at least 12 months of performance completed. Past performance references that are not considered recent will not be considered.

L.4.3.2 Relevant Past Performance. The offeror shall provide Past Performance references that must be relevant to the efforts of the same scope complexity of the STAF Base requirements. Relevant efforts should be of the same or similar efforts as compared to work efforts that: a) Contracts in support of services managing a workforce in excess of 40 Full-Time Equivalent Contractor personnel required to have and maintain a security clearance (ranging from a Secret to Top Secret and Specialized Compartmentalized Information).; b) Contracts demonstrating administrative, Program Management, and Technical services in support of DoD training centers of excellence (or comparable, to include non-DoD) and/or Combat Training Centers (CTCs). Government agencies or organizations considered “comparable” to DoD COEs and CTCs will be any organization and/or agency aligned within a formal federal chain of command and tasked with a national security mission requiring

Contractor support in a classified environment. This may include organizations and agencies such as the Defense

Intelligence Agency (DIA), National Geospatial Agency (NGA), etc.

L.4.3.3 Major Subcontractor Definition: Major subcontractor is defined as a work effort valued at 10% of the contract value. Joint Venture: A Joint Venture (JV) is considered a single entity; and Prime Offeror. If the Offeror is a JV, at least one past performance reference shall be submitted for each member forming the JV, with at least a total of Two (2) combined for the JV.

L.4.3.4 Past Performance reference data concerning the offeror shall be provided first, followed by proposed major subcontractors, in alphabetical order. The Offeror shall also submit the written consent of its major subcontractors to allow the disclosure of its subcontractor’s past performance information to the Offeror. In addition, letters of intent or commitment shall be included for all major subcontractors for their past performance to be considered.

Subcontractor written consent and letters of intent or commitment are excluded from the page count and shall be attached to this volume, organized by Attachment number and Title of the documents so that they can be quickly identified and reviewed. This volume shall be organized into the following sections:

Section 1 – Contract Descriptions. This section shall include the following information in the following format.

(a) Contractor/Subcontractor place of performance, CAGE Code and DUNS Number. If the work was performed as a subcontractor, also provide the name of the prime contractor and Point of Contact (POC) within the prime contractor organization (name, and current address, e-mail address, and telephone and fax numbers).

(b) Government contracting activity, and current address, PCO’s name, e-mail address, and telephone number.

(c) Government’s technical representative/Contracting Officer’s Representative and current email address, and telephone number.

(d) Government contract administration activity and the Administrative Contracting Officer’s (ACO) name, and current e-mail address, and telephone number.

(e) Government contract administration activity’s Quality Assurance Representative (QAR) name, and current e-mail address, telephone and fax numbers.

(f) Contract Number and, in the case of Indefinite Delivery type contracts, GSA contracts, and Blanket

Purchase Agreements, include Delivery Order Numbers.

(g) Contract Type (specific type such as Fixed-Price (FP), Cost Reimbursement (CR), Time & Material

(T&M), etc.). In the case of Indefinite Delivery contracts, indicate specific type (Requirements, Definite

Quantity, and Indefinite Quantity) and secondary contract type (FP, CR, T&M, etc.).

(h) Awarded price/cost.

(i) Final or projected final price/cost.

(j) Original delivery schedule, including dates of start and completion or work.

(k) Final or projected final, delivery schedule, including dates of start and completion of work.

Section 2 – Performance Narrative. Offerors shall provide a specific narrative explanation of each contract listed in Section 1, Contract Description, describing the objectives achieved and detailing how the effort is relevant to the requirement of this RFP.

(a) For any contracts that did not/do not meet original schedule or technical performance requirements, the offeror shall provide a brief explanation within the narrative of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. The offerors shall list each time the delivery schedule was revised and provide an explanation of why the revision was necessary. All Requests for Deviation and Requests for

Waiver shall be addressed with respect to causes and corrective actions. The offerors shall also provide copy of any Cure Notices or Show Cause Letters received on each contract listed and a description of any corrective action implemented by the offeror. The offerors shall indicate if any of the contracts listed were terminated and the type and reasons for the termination. The Government will gather any adverse past performance information that might support a less than satisfactory rating on any evaluation.

Section 3 – New Corporate Entities. New corporate entities may submit data on prior contracts involving its officers and employees. However, in addition to the other requirements in this section, the offeror shall discuss in detail the role performed by such persons in the prior contracts cited. Information should be included in the files described in the sections above. Letters of Intent or Commitment shall be included in the proposal for these employees in order to be considered.

Joint Ventures (JV’s) shall provide a copy of the approved JV agreement. JV agreements shall be attached to this volume if the Past Performance project was achieved through a JV.

Section 4 - Past Performance Questionnaire. For all contracts identified in Section 1, Contract Descriptions, a

Past Performance Questionnaire must be completed and submitted. The offeror shall complete Part I of the Past

Performance Questionnaire and e-mail the questionnaire to both the Government contracting activity and technical representative responsible for the past/current contract. The POCs shall be instructed to electronically complete Part II of the questionnaire and e-mail the entire questionnaire to the Contracting Office no later than the proposal due date, to Isabel Rodriguez at isabel.m.rodriguez12.civ@mail.mil . The offeror shall include a list as an attachment to this volume of all the POCs who were sent a questionnaire. The POC List shall be submitted in Word for Windows Table Format to include the following fields for each POC sent a Questionnaire:

Solicitation Number; Company Name; Contract Number; Government Agency; POC Last Name, First Name;

POC Title; POC Telephone Number; POC E-mail Address; and Date E-Mail sent to POC.

Section 5 - Submissions. Offerors are discouraged from providing points of contact with another contractors’ facility, i.e., in case an offeror (or one of his/her team members) is in a subcontract with another contractor who has submitted a proposal on the same requirement. Offerors shall provide and submit the prime contract number and all Governmental agency POCs in lieu of subcontract numbers or prime contract POCs in situations as described above.

L.4.4 Volume VI -- Factor 5 – Cost/Price

*******NOTE: Insourcing for some of the support services stated in this requirement will occur after award. The

Government does not have specific data at this time to incorporate into this solicitation. Negotiations will be conducted with the awardee of this effort, after contract award, when the specifics have been defined.********

(Amend 0002).

mailto:%20isabel.m.rodriguez12.civ@mail.mil

This volume shall consist of all information, required to support proposed costs and prices. Section B of the IDIQ and TOs are not to be priced; the workbook will contain all pricing for the purposes of evaluation and population of the appropriate CLINS within the TOs that will be evaluated and awarded with the SA IDIQ (Amend 0002). All general assumptions concerning the proposal shall be stated in this volume as well as the Program Management volume. There are no page limitations for this volume.

Certified cost and pricing data are not currently required; however, the Government reserves the right to request such data prior to award. The information submitted in this volume shall be other than certified cost and pricing data (Amend 0002) and shall comply with FAR 15.408, Table 15-2, and the requirements set forth below.

The numbers of hours, personnel and labor categories proposed in Factor 5 must match the numbers proposed in the

Offeror’s Program Management Factor (L.4.2.1.3 Contractor Work Breakdown Structure (CWBS)).

The Government will evaluate the Offeror’s Cost/Price Volume for completeness, price reasonableness, and unbalanced pricing. In order for a cost/price proposal to be complete, it must comply with all requirements of the solicitation and any attachments and exhibits. Cost proposals will not be scored, ranked, or rated.