W900KK23R0041_EDIF-IE Amend_0004.pdf

3100004768

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 0004.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 19

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

16C. DATE SIGNED

BY 27-Jun-2023

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 W900KK23R0041

X 9B. DATED (SEE ITEM 11)

18-May-2023

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

27-Jun-2023

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:

W900KK23R0041

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS

The following have been modified:

Item Description

Attachment 1 Performance Work Statement (PWS) EDIF-IE IDIQ_AMEND_0003

Attachment 2 PWS EDIF-IE Program Management Operations (PMO) Task Order_AMEND_0003

Attachment 3 PWS EDIF-IE Requiring Activity (RA) Task Order_AMEND_0003

Attachment 4 PWS EDIF-IE Sample Project Support Task Order_AMEND_0003

Attachment 5 Contract Data Requirement List (CDRL)_AMEND_0003

Attachment 6 DD 254 (DRAFT with solicitation, FINAL at award)_AMEND_0003

Attachment 7 Wage Determination (WD) 2015-5719_R19_AMEND_0003

Attachment 8 RFP Cross Reference Program Management Matrix_AMEND_0003

Attachment 9 RFP Cross Reference Sample Project Support Matrix_AMEND_0003

Attachment 10 Questions_Comments_Form

Attachment 11 EDIF-IE Cost Price Workbook_AMEND_0003

Attachment 12 SF 1408 PreAward Survey

Attachment 13 SF 1408 Checklist_AMEND_0004

Attachment 14 Government Furnished Property (GFP) List

Attachment 15 GFP incidental property List

Attachment 16 Past Performance Questionnaire_AMEND_0004

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

L.1.0. Proposal Submission

L.1.1 Introduction. The Education, Doctrine, and Instruction for Intelligence Efforts (EDIF-IE) effort is being competed as Small Business set-aside 8(a) Competition under NAICS code 611430, Professional and Management Development Training, with a size standard of $15M in average annual receipts. The EDIF-IE effort will be a Single Award (SA) Indefinite Delivery Indefinite Quantity (IDIQ) contract to provide service to develop and maintain current and relevant training products, guidance and instruction through continued research and analysis of doctrine, policies, and training methodologies. Support services consisting of a five-year ordering period. The Task Order awarded with the Base ID/IQ will have a 1-month phase-in period, 11-month base period of performance, and four 12-month option periods for a total of 60 months.

Proposals are due no later than the date and time annotated on the SF 33 coversheet. Early delivery is authorized.

The required method of the EDIF-IE proposal delivery is via the DoD Secure Access File Exchange (SAFE) located at https://safe.apps.mil/. It has been discovered that there is a Phishing site dedicated to look like DOD SAFE. Be sure to ONLY use the one located here: https://safe.apps.mil/. Offerors shall ensure the recipients receiving the proposal submitted via DoD SAFE are the EDIF-IE 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 EDIF-IE PWS to the 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 EDIF-IE 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.

(Amend 0002)

Offerors are advised the SAFE restricts the maximum file submission to 8 GB. Chrome and Edge are recommended. Internet Explorer limits SAFE uploads to 2GB; therefore, it is not recommended. Offerors shall include the following information in the SAFE upload comments block: Offeror’s name, Solicitation number, primary and alternate points of contact (POC) (include name, email, and telephone number(s) for each POC. (Amend 0003)

L.1.2 Acquisition Approach

The Offerors shall prepare and submit Volume I- Security Volume II – Factor 2 – Program Management, Volume III– Factor 3- Sample (Amend 0003) Project Support, Volume IV – Factor 4 – Past Performance, and Volume V – Factor 5 –Cost/Price, and Volume VI – Administrative/General 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 three hundred and sixty-five (365) calendar days from the final, proposal due date. 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. (Amend0003)

L.1.4 The Offeror’s proposal shall consist of Six (6) volumes:

Volume I – Factor 1 Security Volume II – Factor 2 Program Management Volume III– Factor 3 Sample (Amend 0003) Project Support Volume IV– Factor 4 Past Performance Volume V – Factor 5 Cost / Price Volume VI – Administrative/General Information

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, innovative and/or efficient 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 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 V – Factor 5 –EDIF-IE Price Workbook, shall also be included as separate volumes as a control copy. Control Copy shall be in the title of the files after the name of the volume as stated below. 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 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 or Letters of Commitment may be in the image format and must be readable.

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 Unlimited

II – Factor 2 –Program Management 30 Pages

III – Factor 3 – Sample (Amend 0003) Project Support 10 Pages

IV – Factor 4 – Past Performance 3 Pages per contract – 12 Pages Total (Executive summary and Table of Contents are excluded from the page count. Amend0004)

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 and the Contractor work breakdown structure, attached to their respective volume, will not be counted as part of the page count.

L.2.8 EDIF-IE 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@army.mil

Alternate:

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@army.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(s). 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.

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 EDIF-IE solicitation Primary and Alternate POCs identified within Section L, NLT 1400 hours EDT 8 (Amend 0001) calendar days after the solicitation issue date of May 26, 2023 annotated on the SF 33 coversheet. No additional questions will be accepted. The Government will respond to questions/comments prior to the proposal due date. The subject line of the email for Offeror’s questions/comments shall include the Solicitation number, W900KK-23-R-0041. Questions/comments shall be submitted using the RFP attachment 10 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)).

L.2.14 Any proprietary information submitted separately for (Deleted Language Amend 0003) Subcontractors shall be furnished in the same format, level of detail, and submission due date as prescribed for the prime Offeror.

A (Deleted Language Amend 0003) 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.

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 Class Deviation 2023-O0001 — Verification of Eligibility of Small Business Joint Ventures A small business joint venture offeror must submit, with its offer, the representation required in paragraph

(c) of FAR solicitation provision 52.219-1, Small Business Program Representations, in accordance with 52.204-8(d) for the following categories:

(A) Small Business;

(B) Service-Disabled Veteran-Owned Small Business (SDVOSB);

(C) Women-Owned Small Business (WOSB);

(D) Economically Disadvantaged Women-Owned Small Business (EDWOSB); or

(E) Historically Underutilized Business Zone (HUBZone) Small Business

L.3 Proposal Files

L.3.1 Format. The submission shall be clearly indexed and logically assembled, including the completed solicitation Attachment 8, Cross-Reference Matrix within Volume II – Factor 2 – Program Management and Attachment 9 Volume III- Factor 3- Sample Project Support submitted in Volume III (Amend 0003) 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. Standard proposal text format shall be 12-point Arial or Times New Roman font. A 10-point Arial or Times New Roman font may be utilized for charts and graphs.

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: “CUI//SP-SSEL//LDC” Controlled Unclassified Information (CUI) Specified (SP) - Source Selection (SSEL) Limited Dissemination Controls (LDCs) in the footer. Additional data use restrictions shall be 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, DD254, Pricing, Security References, etc. Additionally, attachments to the proposal, such as: Teaming agreements, verification documents for CWBS MS Project file, and, the Cross-Reference Matrix, 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 II - Factor 2 - Program Management and Volume III- Factor 3- Sample (Amend0003) Project Support Sample task 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 and has no page limit.

L.3.3 Compliancy Screening. The proposal volumes will be reviewed for compliance in accordance with the Instruction to Offerors provided in Section L. 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 Qualifying Criteria- Facility Clearance (Pass/Fail)

L.4.0.1 The Offeror shall have, at a minimum, an active Top Secret Facility Clearance (FCL), as accredited by the Defense Counterintelligence and Security Agency (DCSA) at time of proposal submission in order to be eligible for contract award.

The Offer submitted shall provide documentation evidencing that the Offeror (Prime) possesses, at a minimum, an active Top Secret FCL as accredited by DCSA at time of proposal submission. (Reference;

32 CFR Part 117, DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM) and Section 1629 of the 2020 NDAA)

Joint Venture(s) (JV) – A JV may not be required to have a Top Secret FCL pursuant to section 1629 of the 2020 NDAA IF that joint venture is composed entirely of entities that are cleared for access and ALL joint venture entities possess a minimum of a Top Secret FCLs as accredited by DCSA at time of proposal submission.

Subcontractor(s) ‐ If any proposed Full Time Equivalent (FTE) is employed by a subcontractor, then the proposed subcontractor shall ALSO have at a minimum an active Top Secret Facility Clearance as accredited by the DCSA at time of proposal submission. The Offeror shall provide documentation evidencing this. (No Page Limit)

NOTE: Offerors who fail to supply evidence of clearance levels shall be deemed ineligible for award.

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 the proposal will be deemed to have failed this requirement, is un-awardable and will not receive continued evaluation.

L.4.1 Volume II - Factor 2 – 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. All proposed general assumptions will not be included in the page limit.

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 EDIF-IE PWSs, they must comply with and be able to accomplish all PWS requirements throughout the life of the contract.

The Program Management Volume will holistically depict all pertinent attributes of the Offeror’s approach to performing all requirements of the EDIF-IE IDIQ as identified in the Task Order 1 (TO1) Program Management (PM),and TO2 and Requiring Activity (RA) PWSs and shall, at a minimum, contain all the elements outlined below.

L.4.1.1 Program Management Plan: The PMP must describe the Offeror’s approach and management methodology for executing the overall program management, performance requirements, and administrative responsibilities necessary to successfully perform requirements identified in TO 0001 and TO 0002, Deleted Language (Amend 0003) Task PWSs of the EDIF-IE contract. The Offeror must clearly and comprehensively describe how it will perform and manage the High-Level Functions (HLFs) of EDIF- IE. The PMP must incorporate the Annual Work Plan (AWP) as define in the PWS section 1.5.7 and further identify safeguarding capabilities and manpower structures associated with all proposed separated sites of performance (i.e., “off-site” stations) as well as proposed on-site performance. These structures will depict general EDIF-IE oversight by first line supervisors, through its local organizational structure to the company headquarters management. The PMP must clearly articulate any innovative technologies, capabilities, approaches, or other solutions the Offeror will leverage to enhance the quality, effectiveness, or efficiency of performance and/or reduce the risk of performance during contract execution. Proposals shall include resumes for Key Personnel that demonstrate the required experience as indicated in the IDIQ PWS section 1.10.1. Optimal proposals will integrate innovative technologies, capabilities, approaches, or other solutions throughout the PM Volume. Key Personnel resumes ONLY with names redacted, shall be submitted with this volume, other than Key Personnel, Offeror's are not required to include names of personnel within any element submitted under this volume (Amend 0003).

L.4.1.2 Quality Control Plan (QCP). The PMP must include a QCP clearly articulating the capacity to provide continuous improvement and problem resolution in coordination with local management and supported Government unit and/or higher headquarters as defined in IDIQ PWS 1.5.1.

If the Offeror proposes multiple Subcontractors, joint venture, and/ or teaming partners to execute multiple requirements, the PMP must describe the methodology and approach that will be utilized to manage the performance of these partners.

If the Offeror proposes the use of Offeror-owned facilities in which to perform any EDIF-IE requirements, the PMP must describe the methodology and approach that will be utilized to synchronize the geographically separated workforces to the benefit of the Government’s requirements. This should include the identification of risks and corresponding risk-mitigation strategies that will be employed during contract performance and must address the capacity to providing management with authority, flexibility, and the efficiency to resolve all performance-related issues quickly and effectively.

L.4.1.3 Contract Work Breakdown Structure (CWBS): The Offeror shall provide, as an attachment to this volume, a CWBS describing the disposition of all proposed labor categories executing performance-based requirements within the Task Order PWSs. The CWBS shall identify the following for all 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). The 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) Proposed number of personnel for each labor category, broken out by PWS section

e) Proposed number of hours proposed for each category, broken out by PWS section

f) Identification of CONUS positions being Exempt or Non-Exempt from the Service

Contract Act

Within the CWBS, the Offeror must provide the methodology used to determine the proposed Labor Categories. 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 (no cost/price data shall be submitted anywhere in the PM Volume). 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 performance requirements identified in the TO PWSs.

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 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 to be provided in this volume without pricing. 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. Task Order 0001 and 0002, PWSs in totality.

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

L.4.1.4 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 EDIF-IE performance requirements.

At a minimum, the plan shall address: how best practices will be incorporated to improve recruitment and retention practices; describe recruitment and hiring practices that will be used for this contract; 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 that will ensure a stable workforce over the life of the contract.

The Government is concerned about the continuity of services and understands the value of recruiting and retaining an experienced and qualified workforce familiar with the Government Agency’s operations and system architecture. With that, if the Offeror plans to propose an alternate workforce, or intends to reduce the incentives of the existing workforce, it shall provide a detailed explanation of how it will maintain a qualified and stable workforce to ensure there is zero interruption to the services currently being provided.

(Language Deleted Amend0003)

L.4.1.5 Joint Venture/Teaming or (Language Deleted Amend0003) 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 legally binding (Amend0003) signed document [contingent upon award and (Amend0003) format as established by Offeror] specifying an agreement (e.g., Teaming Agreements or Joint Venture Agreement) among the parties. Offeror shall identify for each proposed team member or Subcontractor: a) what PWS section each Joint Venture team member or Subcontractor will support; b) the team member or Subcontractor’s name and address (Amend0003); c) the actual services to be provided; d) the percentage of work it will perform. The Teaming Agreements or Joint Venture Agreement shall be attached to this volume and are not included in the page count.

Teaming agreement(s) shall be submitted as part of the written, electronic proposal submission IAW Proposal Structure Table. The list of subcontractors will be listed in the resultant contract, FAR Clause 52.244-2, Subcontracts, and will be binding within the EDIF-IE contract. (Amend0003)

L.4.2 Volume III - Factor 3 – Sample (Amend 0003) Project Support

The Offeror shall develop a Sample Project Support (Amend0003) Plan detailing its approach to satisfy the requirements of the sample project provided. The PP must describe the allocation of manpower and resources, a detailed schedule depicting timeline associated with delivery, pertinent milestones, and the offeror’s use of organic technologies and/or specialized equipment (if applicable). Optimal PPs will articulate any innovative technologies, capabilities, approaches, or other solutions the Offeror will leverage to enhance the quality, effectiveness, or efficiency of performance and/or reduce the risk of unsuccessful project completion. The Sample Project Support (Amend0003) Task will be evaluated to ensure comprehensive understanding of the IDIQ requirements but will not be awarded with the IDIQ.

L.4.3 Volume IV - Factor 4 – Past Performance

This volume shall contain past performance information regarding similar contracts for up to four (4) recent and relevant (as defined in Section L.4.3.1, L.4.3.2 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 will be limited to 3 pages per PP example. The executive summary page and Table of Contents pages are excluded from the page count. (Amend 0004)

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 submissions from a Joint Venture (JV), each partner to the joint venture may provide a submission or submit performance by the joint venture itself. The partners to the joint venture in the aggregate must demonstrate the past performance member.

Two (2) Any remaining 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.(Amend 0003)

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 EDIF-IE 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 of 35 Full-Time Equivalent Contractor personnel or more required to have and maintain a security clearance (ranging from a Secret to Top Secret and Specialized Compartmentalized Information).; b) Contracts demonstrating support of DoD training centers of excellence (or comparable, to include non-DoD) and/or Combat Training Centers (CTCs) education and doctrine development requirements. 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.

Each reference submitted shall clearly delineate how the referenced project is relevant experience performing the following EDIF-IE Core Experience areas:

Experience related to the development and integration of emerging and innovative technologies, theories, techniques, and methodologies, associated with doctrinal and non-doctrinal education.

Reference: IDIQ PWS para. 5.2.1 (Amend 0003).

Experience related to the creation, coordination, development, and maintenance of educational products, and other interrelated media directly connected to a Government Agency’s core mission.

Reference: IDIQ PWS para. 5.2.2 and all subsequential paragraphs.

Experience related to the accessibility, effectiveness, and sustainment of learning technologies and platforms related to adult learning models and training. Reference IDIQ PWS para. 5.2.3 (Amend 0003)

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. (Deleted Language Amend 0003). 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 Unique Entity ID 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) Contract Number and, in the case of Indefinite Delivery type contracts, GSA contracts, and Blanket Purchase Agreements, include Delivery Order Numbers.

(e) 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.).

(f) Awarded price/cost.

(g) Final or projected final price/cost.

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

(i) 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 – Major Subcontractors. Offerors shall provide an outline of how the effort required by the RFP will be assigned for performance within the offeror’s corporate entity and among the proposed Major subcontractors. The information provided for the prime offeror and each proposed major subcontractor must include the entire company name, company address, CAGE Code, Unique Entity ID Number and type of work to be performed by citing the applicable Government PWS’s subparagraph number for Task Order 0001 and 0002. This includes all Major subcontractors who will be providing critical hardware/services or whose subcontract is for more than 10% of the total proposed cost/price. This section will further include written consent of major subcontractors to allow the disclosure of their subcontractor’s past performance information to the Offeror. In addition, letters of commitment shall be included for all major subcontractors. Major Subcontractor Past performance submissions are included in page count. All other requested information is excluded from page count (Amend0003)

Section 4 – 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 to be considered. (Letters of intent or commitment are excluded from page count. Amend0003).

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. (Letters of intent or commitment are excluded from page count. Amend0003)

Section 5 - 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@army.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 (Deleted Language Amend0003) ; 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. If past performance questionnaires are included in this volume, they are not included in the page count.

(Amend0003)

Section 6 - 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 V- Factor 5 – Cost/Price

This volume shall consist of all information, required to support proposed costs and prices. Section B of the IDIQ is 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 IDIQ. TO 3 will be priced for evaluation purposes and will be included in the Total Evaluated Price but will not be awarded. 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.

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

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 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.1.3 Contractor Work Breakdown Structure

(CWBS)).

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

Any proprietary information submitted separately for (Deleted Language Amend0003) Subcontractors shall be furnished in the same format, level of detail, and submission due date/time as prescribed for the prime Offeror. If the (Deleted Language Amend0003) Subcontractor information is provided late, then the entire proposal may be found to be untimely. If the (Deleted Language Amend0003) Subcontractor information does not conform to the solicitation requirements, it will be determined to be non-compliant and not evaluated. Non-conforming/not evaluated Subcontractor data may render the complete prime Offerors proposal as non-compliant. Separately submitted data shall be submitted via SAFE as described in L.1.1, and label their volume as Cost/Price Volume V, the prime Contractors name and Subcontractors name. Any difference between rates provided to the prime to populate the cost/price workbook and what is submitted in the (Deleted Language Amend0003) subcontractors workbook, the prime workbook data will prevail. The Government expects the offeror to use the subcontractor’s fully burdened rate as the prime's base rate and then apply the prime's indirect rates in accordance with their indirect rate structure.

The Government will validate calculations of the subcontractor and then validate the application of the Prime offeror's application of indirect to the subcontractor's fully burdened rate. (Amend0003)

L.4.4.1 Since the award consists of cost type CLINs the awardee is required to have an adequate accounting system. The Offeror shall submit a copy of the most recent ACO letter regarding the status of their accounting system. If that letter is more than a year old and the Offeror has a more current DCAA audit report commenting on the status of their accounting system, a copy of that report will also be submitted and included in the Proposal Volume V – Cost/Price. If the Offeror does not have an approved accounting system, the Offeror shall complete SF1408 - Preaward Survey (See EDIF- IE_RFP_Attachment 12) of Prospective Contractor Accounting System Checklist and return the documentation as part of the Price Volume of the proposal.