Section_L_v4 01132026.docx

UNCLASSIFIED

SECTION L Supplemental - Instructions, Conditions, and Notices to Bidders L1.2 The NAICS Code for this effort is 541519 - Other Computer Related Services.

L1.2.1 Prospective offerors are encouraged to review the full text of solicitation provision FAR 52.204-7, including the requirement for continuity of SAM registration. Offerors are expected to ensure compliance with all laws, regulations, standards, and any other constraints specifically identified in this RFP. If a proposal fails to conform to the instructions provided herein, it may be deemed noncompliant and ineligible for contract award. Offerors are advised that System for Award Management (SAM) registration in accordance with clause at 52.204-7, “System for Award Management (Oct 2018)”, will be used by NGA to review Section K Representations and Certifications and to facilitate contract payment. NGA will verify SAM registration at the time of proposal submission and prior to award, during the contractor responsibility review. The SAM registration requirements set forth in FAR 52.204-7(b)(1) are intended to facilitate NGA’s review of offeror Representations and Certifications and to facilitate timely contract awards and payments. However, a lack of or lapsed SAM registration does not automatically deem an offeror ineligible for award. The Contracting Officer will provide an opportunity to register or to remedy a lapsed registration in accordance with FAR 9.104-5(d). As part of the responsibility determination, the Contracting Officer will consider the totality of the circumstances, including whether the offeror can demonstrate that it has already remedied a lapsed registration, completed a new registration, or initiated an update to a lapsed registration that was previously active. Offerors who are not registered in SAM should consider applying for registration immediately upon issuance of a solicitation. Offerors who are already registered should actively monitor their registration status and apply for renewal at least 10 days before their registration lapses. Any exchanges with an offeror regarding its registration status on SAM pertain to the offeror’s responsibility and, therefore, are not considered discussions.

L1.3 Point of Contact

a) The Contracting Officer (CO) is the sole point of contact for this acquisition. Any and all questions regarding any aspect of this solicitation must be addressed only to the CO. Prospective Offerors are cautioned against contacting other Government personnel in regard to this solicitation prior to contract award. Prospective Offerors are also cautioned to advise potential subcontractors or teaming contractors of this instruction. If such contact occurs and is found to be prejudicial to competing Offerors, the Offeror (including subcontractors or teaming contractors) making such contact may be excluded from award consideration. The CO will use the SAM.gov website to post the solicitation announcement. The CO will utilize System for Award Management (SAM.gov) website to post announcements, the solicitation and associated attachments, amendments (if any) to the solicitation, and answer appropriate (validated) questions.

b) It is the Offeror’s sole responsibility to access the appropriate website routinely to obtain current information relevant to this acquisition (i.e., announcements, updates, technical and contractual Question & Answer (Q&A), amendments to solicitation, etc.).

c) Contractor Bidder’s Library (CBL) - The CO will use the XXX.

L1.4 Proposal Preparation and Delivery

The Government will not be obligated to pay any costs incurred by an Offeror in the preparation and submission of a proposal in response to this RFP. All proposal information shall be delivered in accordance with the Proposal Submission Schedule below to the addresses indicated below. Proposals shall be submitted via XXX. Offerors shall also send a courtesy email to the Contracting Officer, Daniel Fadely, at daniel.r.fadely@nga.mil, upon their submission of the proposal.

Proposal Submission Schedule: All proposal volumes and documents are due – TBD.

L1.5 General Instructions

The Offeror’s proposal shall include all data and information required by this solicitation and must be submitted in accordance with these instructions. Offerors are expected to ensure compliance with all laws, regulations, standards, and any other constraints specifically identified in this RFP. Non-conformance with the instructions provided in this section may result in a poor evaluation of the proposal such that the proposal would not be competitive for award.

Information in the proposal shall unclassified with exceptions for past performance information and the SCIF verification letter as noted below.

Proposals must be clear, concise, and include sufficient detail to support a thorough and effective evaluation.

Offerors shall not simply rephrase or restate the Government’s requirements. Proposals shall provide convincing rationale supported by factual, verifiable information that fully demonstrates that the Offeror understands the scope and objectives of this acquisition and all of the Government stated needs associated with the solicitation and any resultant contract. Proposals shall clearly describe how the Offeror intends to fully satisfy the needs identified by the Government. The Offeror shall assume the Government has no prior knowledge of its capabilities and experience, and will base its evaluation solely upon the information presented in the Offeror’s proposal with the exception of Past Performance.

Elaborate brochures or documentation, detailed artwork, or other embellishments are unnecessary and are not desired.

If one or more proposal volume is received after the time and date specified in the Proposal Submission Schedule, the Offeror's entire proposal will be considered LATE and shall not be accepted, except as authorized in accordance with FAR 52.215-1, Instructions to Offerors - Competitive Acquisition.

To award a contract, the Government must receive an acceptable offer. An offer is acceptable when it meets all of the material terms and conditions of the RFP, which includes the solicitation provisions, contract clauses, specifications, documents, exhibits, and attachments.

L1.6 Solicitation Question & Answer Period

The Government will allow a period to submit questions after the release of the RFP. Any questions or requests for clarification regarding the RFP shall be submitted via email to POCs listed in SAM.gov. All questions and requests for clarification shall, at minimum, identify the applicable RFP section and page number for each question. Any proprietary information contained in a question(s) shall be identified in the submission and that information will not be posted by the Government. Questions received after 9:00 AM CDT January 23, 2026.

may not receive a response.

L1.7 Proposal Acceptance

The Offeror shall make a clear statement in the proposal as to the expiration date of the proposal; however, the proposal shall remain valid for a period of at least 240 days.

L1.8 Proposal Volumes and Organization

The proposal volumes, titles, maximum pages, and other related information are listed in Table L.1 below. Each volume shall be written on a stand-alone basis. Information required for proposal evaluation not found in its designated volume or presentation will be assumed to have been omitted from the proposal. The format of proposal volumes shall correlate directly and sequentially with the instructions contained herein. A table of contents shall be incorporated into each volume of the Offeror's proposal, and shall include a listing of the section titles, subsection titles, and paragraph along with page numbers for each title. A glossary of acronyms and terms for each volume shall be provided which (including table of contents) will not count against the volume page limit. All acronyms shall be defined at first use. For clarity and completeness of presentation, Offerors shall provide a cross-reference matrix for each of the volumes listed. This matrix shall indicate the proposal volume section, subsection, and paragraph, cross-referenced appropriate with the PWS paragraphs, applicable RFP instructions, evaluation criteria, and contract deliverables, as applicable.

Proposal Organization Table L.1

Signature in Adobe File.

Appendix 1-E

OCI Disclosure and Analysis Form(s) and Mitigation Plan

No Limit OCI Disclosure and Analysis - MS Word File (Template – RFP Attachment L-1) Note: Mitigation Plan is Contractor Format

Appendix 2-C

Résumés for Key Personnel

(Template – RFP Attachment L-3)

(Excel File Template – RFP Attachment L-4)

(Template – RFP Attachment L5)

(Template – RFP Attachment L7)

(Template – RFP Attachment L8)

MS Word File for Narrative

Appendix 6-B

Price/Cost Proposal

The following Section L addendum documents shall be utilized in the Offeror’s proposal preparation and submission in accordance with the RFP.

L1.9 Price/Cost Information

All proposed price/cost information (i.e., proposed dollar amount) shall be included only in the Price Volume. Work hour estimates and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale to support a technical/management position, or unless otherwise specified in this section.

L1.10 Page Limitations

To aid in the Government’s evaluation, all proposals shall follow the same general format. A "page" shall consist of print on one length of 8-1/2 by 11-inch paper. Page limitations shall be treated as maximums and are specified for each volume in Table L.1 above. Page limits on revised proposals, if required, shall be provided as part of the request for revised proposals notification. All pages submitted by an Offeror in excess of the limitations contained in the RFP instructions will be removed and not evaluated. Unless otherwise specified, page limitations include charts and graphic material. The Offeror's page numbering methodology must clearly demonstrate the pages included in the page limitations of Table L.1 Proposal Organization Table. Partial pages count as a full page for page limitation purposes. All pages shall be numbered sequentially. All pages within a page-limited section shall be consecutively numbered, starting at page one (1), and shall not exceed the page limitation.

L1.11 Format

L.11.1 Page margins shall be a minimum of one (1) inch on top, bottom, and each side. Minimum type size shall be 10 point Arial standard font, unless instructions elsewhere specify different. Text lines shall be single-space. Line spacing before and after a heading shall be double-spaced. Typesetting, font compression, or other techniques to reduce character size or spacing are not permitted and are considered a deliberate attempt to circumvent the page limitations. Prohibited techniques include setting the paragraph line spacing. Two-column presentation is not acceptable. Headers and footers shall be no smaller than 8 point Arial.

L.11.2 Illustrations, tables, charts, graphs, and figures are graphical displays of data that may be used, wherever practical, to depict organizations, systems, layout, implementation schedules, etc. Offerors may use JPEG images for charts or screen shots. Figure call-outs (identification and titles) may be single-spaced. Embedded text shall be no smaller than the following:

• Art: 8 point Arial

• Tables: 8 point Arial

• Titles: 8 point Arial, bold, initial letter capitalization

L.11.3 Graphic displays of data are for supplemental information only. Including large amounts of narrative within artwork and tables is not permitted. This practice will be considered a deliberate attempt to circumvent the page limitations, and the data will not be considered for evaluation.

L.11.4 Graphics embedded into documents shall be kept as simple as possible. When considering graphics, use the following guidelines:

• Limit colors to 256 colors at 1024 x 768 resolution; avoid color gradients

• Simplify the color palette used in creating figures

• Be aware of size for graphic files. Large files are discouraged

• Avoid scanned images, where possible

L.11.5 The Offeror shall not use embedded sound or video files in proposal documents.

L.11.6 Unless otherwise specified, each page of the proposal volumes, including appendices and annexes, will be counted, with the following general exceptions: blank pages, title pages, tables of content, tables of illustrations, and appendices that include a list of acronyms, glossary of terms, and cross-reference matrices. Further, all volume parts marked as “None” for Page Limit will be excluded from the page count. Pages excluded from the count shall not contain additional or inappropriate information, and, if such is found, these pages will be removed by the CO and not evaluated. Pages marked "This page intentionally left blank" will not be counted.

L1.12 Electronic Format L.12.1 This section is intended to provide information to the Offeror on the electronic format and application software to be used for submitting its proposal. Use of the software and procedures described in this section reduces the amount of time and effort needed by the Government to receive and install proposals onto the electronic evaluation system and will help to ensure that proposals are suitable for reading electronically. The information regarding electronic productions listed below shall not be construed as Government endorsement for such products. Efforts by the Government to clarify and install electronic proposal submission in accordance with FAR 15.207(c) will not be considered discussions.

L.12.2 The Offeror’s proposal shall be submitted using appropriate Microsoft Office version applications. The Government will access the Offeror's proposal using a network running Microsoft (MS) Windows 10 and MS Windows XP Workstations. The Government will use two core applications of MS Office 2016 (Word and Excel) to access files. The Offeror shall submit the Proposal Pricing Template (Attachment L-10) in Excel format. It is the Offeror's responsibility to ensure that all of its ".docx" file submissions are fully compatible with MS Word 2016 and its ".xlsx" file submissions are fully compatible with MS Excel 2016. Proposals which fail to provide this compatibility may not be evaluated. Offerors shall remove macros and close any linked information used in developing spreadsheets prior to submittal. Excel spreadsheets shall include the Offeror's working formulas of calculations within the spreadsheet. Excel spreadsheets shall remain unaltered, unless permitted within the RFP instructions, and unincorporated into any other format. No files, documents, spreadsheet, or cells shall be password protected. Any other file application must be saved to a PDF file with security features turned off, and must be capable of being read, manipulated, searched, and saved using Adobe Reader DC on a Windows 10 platform. Failure to comply with this instruction may result in the Offeror being determined non-compliant and removed from the evaluation process, whether Prime Contractor or Subcontractor.

L.12.3 Electronic submissions shall contain hyperlinks or cross-references when reference is made to other sections, tables, or figures within a given proposal volume. Offerors shall make the existence of hyperlinks or cross-references obvious by using a different font color, underlining, or other methods to highlight hyperlinks. Electronic submission shall contain a table of contents with hyperlinks to facilitate ease of navigation within the proposal volume. Features inherent to MS Office 2016 applications should be used to accomplish this navigation feature. Hyperlinks or cross references shall not be used to link items between different proposal volumes. This restriction is necessary because the Government will be placing electronic versions of the documents on its evaluation server, causing the previously created hyperlinks between volumes to not function.

L1.13 File Naming Conventions

The Offeror shall name files using the naming conventions that clearly identify the file. All file names shall not exceed 20 characters. Offerors shall use standard Microsoft/Adobe extension naming conventions such as:

L1.14 Volume Format and Content

This section describes the format and content of each volume that are to be included in the Offeror's proposal. Each volume shall only include the information specified herein, (i.e., Technical/Management information only in Volume 2, Past Performance only in Volume 3, etc.). Any information that is included in the wrong volume will not be considered.

L1.15 Volume 1 – Offer

L1.15.1 Cover Letter The cover letter is considered the first page of the proposal and shall include the following:

• Statement that the proposal is firm for a period of not less than 240 calendar days from the proposal due date.

• Statement of compliance indicating either complete compliance with the solicitation or a detailed analysis of any objections, exceptions, or contingencies to the terms of the solicitation. The completion and submission to the Government of the items listed below shall constitute an offer and shall indicate the Offeror's unconditional consent to the terms and conditions of the RFP. Exceptions to any of the terms and conditions of this RFP may be considered by the Government to be unacceptable.

• Statement acknowledging the Offeror's compliance with general standards for responsible prospective contractors included in FAR Part 9.104-1.

• Complete business address of the Offeror, the corporate name to be used on any resultant contract, and the remittance address if different from above. If this name does not identify a "parent company" or sponsoring "corporation" name, also provide such identity, as appropriate.

• Solicitation Number.

• At least two names and telephone numbers of personnel to be contacted for clarification or questions, if necessary, of the Offeror's proposal.

• A statement acknowledging consent for the Government to use the planned consultant(s) in support of the acquisition.

• Commercial and Government Entity (CAGE) Code.

• Tax Identification Number (TIN).

• Dunn & Bradstreet (D&B) Data Universal Numbering System (DUNS) Number.

• Defense Contract Management Agency (DCMA) POC (Name, Position, Phone Number, E-mail).

• Defense Contract Audit Agency (DCAA) POC (Name, Position, Phone Number, E-mail).

• Corporate Name, Address, Additional Details for Award (if different than the submission).

• Validation that the proposal signatory is authorized to legally bind the Offeror.

L1.15.2 Master Table of Contents A master table of contents for the entire proposal.

L1.15.3 SF 33, "Solicitation, Offer, and Award," with blocks 12 through 18 completed by the Offeror

L1.15.3.1 RFP Sections B through K (and Section I fill-ins) Offerors shall provide any fill-ins or certifications required by the solicitation, for inclusion in any resulting contract.

L1.15.4 Small Business Subcontracting Plan (Large Businesses Only)

All Offerors that are classified as a Large Business under the NAICS code of this RFP shall provide a Small Business Subcontracting Plan that contains all the elements required by FAR 52.219-9 and DFARS 252.219-7003 (or DFARS 252.219-7004 if the Offeror has a comprehensive subcontracting plan). This plan shall be submitted separately from the Small Business Participation Plan, which applies to both Large and Small Businesses. The Small Business Subcontracting Plan is not a requirement for evaluation in source selection, but rather, a requirement for award to a Large Business and will be incorporated into any resultant contract. The Small Business Subcontracting Plan shall reflect and be consistent with the commitments proposed in the Small Business Participation Plan. The DoD has established small business goals to ensure that small businesses will have maximum practicable opportunity to participate in performance of DoD contracts. The small business goal for this acquisition is 31% of the total value of the IDIQ. For evaluation purposes, the 31% will be assessed as the cumulative totals of Task Order 1 and Task Order 2.

L1.15.5 Organizational Conflict of Interest Disclosure and Analysis Form(s)

The Offeror shall complete an Organizational Conflict of Interest (OCI) Disclosure and Analysis Form for itself and for all proposed supporting companies whether or not an OCI exists. If there is a perceived or actual OCI, the Offeror shall submit a synopsis of the applicable contract SOW or PWS with an OCI Mitigation Plan. The Offeror shall use the OCI Disclosure and Analysis Form template.

L1.15.6 OCI Mitigation Plan

If the CO determines, after receipt of the proposal and review of the information required in the OCI Disclosure and Analysis form and OCI Mitigation Plan, that there is an OCI issue that is mitigable, both parties shall be provided the opportunity to engage in negotiations regarding an acceptable mitigation plan. If the plan is approved, it will be incorporated into Section J of the resulting contract. Any resultant mitigation plan shall comply with FAR Subpart 9.5. The OCI Mitigation Plan shall provide a disclosure statement that describes all relevant information concerning any past, present, or planned interests bearing on whether it (including its chief executives and directors, or any proposed consultant or subcontractor) may have an existing or potential organizational conflict of interest. In addition, it shall delineate the company's approach to avoiding, mitigating, or neutralizing any identified conflicts. Any negotiations or request for additional information regarding potential or actual OCIs does not constitute discussions under FAR 15.306.

L1.16 Volume 2 – Technical/Management

This volume consists of information describing the Offeror’s proposed technical/management approach to meet this solicitation’s objectives, and convey the Offeror’s understanding of the requirements and objectives. The information contained in the Offeror’s Technical/Management Volume shall be specific, complete, clear, and coherent and provide industry best practices. The volume shall detail the information required to assess the Offeror’s approach proposed for the effort. The Offeror shall also include all key assumptions, constraints, dependencies, risks, and that have significant impacts on the approach.

L1.16.1 – Factor 1, Technical/Management

The Offeror shall provide its technical approach to successfully fulfill the FS3i requirements outlined in the RFP, conveying and detailing the Offeror’s understanding of the technical/management requirements, including any risks, and highlight any key or unique functions and features of its proposed approach to meeting the PWS requirements. The Offeror’s response will be evaluated against the Technical/Management Sub-Factors listed below and further defined in the Evaluation Criteria in Section M.

L1.16.1.1 – Sub-factor 1.1 Operations Support Services:

The Offeror shall describe its technical approach to meeting the FS3i requirements of the PWS, including:

(a) Offeror shall demonstrate an adequate approach to provide DevSecOps Management support in accordance with Air Task Order PWS, Section 6.3, WBS 4.11.

(b) Offeror shall demonstrate an adequate approach to provide System Performance support in accordance with Air Task Order PWS, Section 6.3, WBS 4.25.

(c) Offeror shall demonstrate an adequate approach to provide Automation support in accordance with Air Task Order PWS, Section 6.3, WBS 4.4.

L1.16.1.2 Sub-factor 1.2 Integration Services:

The Offeror shall describe its technical approach to meeting the FS3i requirements of the PWS, including:

(a) Offeror shall demonstrate an adequate approach to provide Cloud Engineering, Integration, and Management support in accordance with Air Task Order PWS Section 6.1, WBS 2.37.

(b) Offeror shall demonstrate an adequate approach to provide Engineering support in accordance with Air Task Order PWS Section 6.1, WBS 3.38.

(c) Offeror shall demonstrate the ability to provide Release Management support in accordance with Air Task Order PWS, Section 6.3, WBS 4.5.

L1.16.1.3 Sub-factor 1.3 Software Maintenance Services:

The Offeror shall describe its technical approach to meeting the FS3i requirements of the PWS, including:

(a) Offeror shall demonstrate an adequate approach to provide Corrective Maintenance support in accordance with Air Task Order PWS, Section 6.2, WBS 3.16.

(b) Offeror shall demonstrate an adequate approach to provide Adaptive Maintenance support in accordance with Air Task Order PWS, Section 6.2, WBS 3.17.

(c) Offeror shall demonstrate an adequate approach to provide Preventive Maintenance support in accordance with Air Task Order PWS, Section 6.2, WBS 3.18.

(d) Offeror shall demonstrate an adequate approach to provide Perfective Maintenance support in accordance with Air Task Order PWS, Section 6.2 WBS 3.19.

L1.16.1.4 Sub-Factor 1.4 Common Services:

The Offeror shall describe its management approach to meeting the FS3i requirements of the PWS, including:

(a) Offeror shall demonstrate an adequate approach to provide software license procurement support in accordance with Common Services Task Order PWS Section 6.2.

(b) Offeror shall demonstrate an adequate approach to providing integrated and comprehensive help desk support for Tier 1, 2, and 3 support to include tracking escalation and resolution in accordance with Common Services Task Order PWS Sections 6.1 and WBS 2.20 – WBS 2.24.

(c) Offeror shall demonstrate an adequate approach to provide Cyber Security support in accordance with Common Services Task Order PWS, Section 4.3 and Base PWS WBS 6.28.

(d) Offeror shall demonstrate an adequate approach to provide Innovation and AI/ML support in accordance with Base PWS, Section 6.46.

L1.16.1.5 Sub-Factor 1.5 Program Management:

The Offeror shall describe its management approach to meeting the FS3i requirements of the PWS, including:

(a) Offeror shall demonstrate an adequate Program Management Plan in accordance with the IDIQ PWS Section 7.1.

(b) Offeror shall demonstrate an adequate approach to providing key personnel. The Offeror shall meet all of the required qualifications and education/equivalencies for proposed key personnel. Failure to demonstrate in the resume that each key personnel meet the requirements will result in the assessment of a deficiency and a rating of Unacceptable for this sub-factor, which will result in an overall rating of Unacceptable. Resumes for key personnel shall include a description of the experience and capabilities for all proposed key personnel. The resumes shall demonstrate how the proposed individuals meet the required and/or desired skills. Resumes shall also address the proposed individuals’ technical background, education, work experience, and accomplishments related to the activities described in this solicitation. A signed letter of commitment is required for all key personnel currently employed by the Offeror or a teaming partner. A signed letter of intent is required for any key personnel not currently employed by the Offeror or a teaming partner.

(c) Offeror shall describe an adequate staffing plan to meet the requirements of the Common Services Task Order and Air PWSs. The Offeror’s Staffing Plan shall demonstrate sound methodologies and resources for staffing (to include recruitment and onboarding at initial award and throughout life of the IDIQ) and maintaining an appropriate level of qualified personnel sufficient to perform the FS3i requirements (as substantiated in the Offeror’s BOEs for Common Services Task Order and Air Task Order PWSs). The Government will utilize the Offeror’s BOEs (without pricing) to determine if the proposed labor categories, skill mix, and hours are sufficient to accomplish the tasks in the Common Services Task Order and Air Task Order PWSs. The staffing plan must demonstrate that adequate Contractor SCIF facilities are available during the full performance of this effort to accommodate the proposed staff.

(d) Offeror shall demonstrate an adequate transition-in plan in accordance with Base IDIQ PWS. The Offeror shall describe a detailed transition-in plan that will result in negligible impact to operations to include risk mitigation strategies, structured onboarding to ensure seamless operational continuity, a demonstrated ability to transition all capabilities (operational and administrative), and an approach to transitioning from legacy contract resources and methods to new, different, and/or innovative resources and methods.

(e) The Offeror shall describe a cohesive subcontractor and total teaming strategy that leverages complementary capabilities to maximize efficiency, mitigate risk, and delivers the best value to the Government.

L1.16.1.6 Sub-factor 1.6 Small Business:

Offerors shall clearly detail their approach and ability to meet the small business objectives as described in the solicitation.

L1.16.1.6.1 Small Business Participation Plan All Offerors shall submit a Small Business Participation Plan (SBPP) that addresses the extent of small business participation in performance of the requirements under this RFP. The plan must demonstrate a commitment to achieve the small business goal of 31% for the IDIQ, and for the purposes of evaluation, achieving 31% of the combined total value of Common Services Task Order and Air Task Order. The socio-economic category goals (which are not additive to the small business goal) are as follows: Small Business – 15%; Small Disadvantaged Business - 3%; Small Disadvantaged Veteran Owned Business – 5%; Women-Owned Small Business - 5%; Historically Underutilized Business Zone (HUBZone) - 3%.

L1.16.1.6.2 For purposes of subcontracting, Historically Black Colleges and Universities/Minority Institutions (HBCUs/MIs) shall be included in the small disadvantaged business category. All Offerors shall propose the level of participation of small businesses (as a small business prime and/or small business subcontractors) in the performance of the acquisition relative to the objectives/goals set forth. The Government approved SBPP will be incorporated into any resultant contract. The Government reserves the right, after award, to enforce FAR 52.219-16 Liquidated Damages—Subcontracting Plan. The SBPP shall include the following, at a minimum, proposed to participate in the performance of the requirements outlined in the RFP:

(1) Type of Business of Prime Contractor (check all applicable boxes):

{ } Large { } Historically Black Colleges and Universities/Minority Institution (HBCU/MIs) Or { } Small Business (also check type of Small Business below) { } Small Disadvantaged Business (SDB) { } Women-Owned Small Business (WOSB) { } Historically Underutilized Business Zone (HUBZone) (SBA certified) { } Small Disadvantaged Veteran Owned Small Business (VOSB)

(2) The total combined percentage of work to be performed by both large and small businesses (include the percentage of work to be performed both by Prime and Subcontractors):

Total Common Services Task Order and Air Task Order combined (TCV): %__________ Dollar Value of your participation as a Prime Contractor: %_________ Total Percentage Planned for Large Business(es): __________% Total Percentage Planned for Small Business(es): __________% *Note – When combined, Large and Small Business totals must equal 100%.

(3) Indicate the total percentage of participation to be performed by each type of subcategory small business.

An Offeror who qualifies as a small business should include its Prime Contractor dollars in calculating its proposed percentage goals in all of the small business categories that it qualifies. The percentage of work performed by small businesses that qualify in multiple small business categories may be counted in each category.

*Note – The sum of all the percentages need not equal 100% as individual subcontractors may be counted towards more than one category. All percentages shall use Task Order 1 Total Value as a baseline.

Offerors who propose small business participation percentages that cannot meet the Government’s small business goals for this acquisition shall explain in detail why such goals cannot be met.

(4) Provide a listing of all proposed subcontractors, Company address, CAGE code, and Company type(s) (i.e., Large, Small, Small Disadvantaged, HUBZone, Women-Owned, Veteran-Owned, Service-Disabled Veteran Owned).

Note – any subcontractor identified as an 8(a) or HUBZone MUST have an active SBA certification of its status at the time of proposal.

(5) Describe the extent of commitment to use small businesses as defined by FAR Part 19, as subcontractors. Offerors shall also list all small business subcontractors with which they have teaming agreements for this solicitation and types of commitments, if any, are in place for this specific acquisition (either small business prime, written contract, verbal, enforceable, non-enforceable, joint venturing, mentor-protégé, etc.). Offerors that have enforceable agreements must provide copies of the fully executed agreement (Note: copies of the agreement do not count towards the page limit). An enforceable commitment is defined as “A written and signed agreement (by both parties) that details that all parties have agreed to a business relationship for this acquisition. This document must be clear that both parties have defined and agreed to the extent of the relationship to include the type or types of work the subcontractor(s)/partners(s) shall perform and what areas of the SOW/PWS they will cover. The agreement shall be specific in nature.”

(6) A list of service(s) each small business will provide for this acquisition, to be as specific as possible (i.e., references to the SOW/PWS), to demonstrate the variety and complexity of work:

(7) Provide narrative information on how goals for the effort were developed and the proposed plan of execution to ensure goals will be met or exceeded, detailed explanations/documentation supporting the proposed participation percentages, or lack thereof, detail regarding historical performance with small businesses, and specifics/details of how the plan will be executed in order to meet requirements.

(8) Small business participation, to include all small business socio economic categories, expressed in percentages of TCV:

L1.17 Volume 4 – PAST PERFORMANCE

The Offeror shall provide the following in the Past Performance Volume:

L1.17.1 The Offeror shall include information for no more than five (5) recent programs that are similar in scope and complexity to this program. A recent program is defined as performance within the last five (5) years, provided that there have been at least 12 months of completed performance on the contract/task order as of the date of issuance of this solicitation. Within the five (5) permitted references, no more than two (2) are allowed to be submitted for significant subcontractors. Significant subcontractors are defined as a subcontractor performing at least 15% of the total cost (combined value of Common Services Task Order and Air Task Order) of all work including options that are similar in scope and complexity to this program. Classified past performance information may be submitted on the Classified ARC. Offerors are responsible for ensuring the total page limitations are not exceeded for Classified and Unclassified responses.

L1.17.2 The Offeror shall provide the Master Project List (Attachment L-5) which summarizes the performance requirements being referred to in Past Performance Questionnaires (PPQ) and Project Summaries.

L1.17.3 Project Summaries: Offerors shall submit information on each reference to demonstrate their ability to perform the proposed effort, explain how/why the referenced projects are relevant to the proposed effort, illustrate the company’s capabilities, and show the company’s ability to ensure quality and mitigate risks. For each contract/task order listed in the Master Past Performance Project Reference List and PPQs, the Offeror shall provide a summary of the project that contains, at a minimum, the following information:

a. Date the PPQ was requested and to whom it was sent

b. Company performing the project and company division/business segment

c. Place of performance for the project (city, state, country, etc.)

d. Original and final/current total contract/task order value

e. Scheduled and actual performance start and completion dates

f. Indication if the Offeror (include parent companies and affiliated firms) is a stakeholder/customer of the work being performed

g. Performance metrics, incentives utilized

h. Description of the project’s relevance to the FS3i effort

If performance was as a subcontractor on the project, include the above information as well as the following information in the summary:

Contract type for the subcontract Function/services on the project and description of the subcontracting effort Original and final value of the subcontract

L1.17.4 Recent contracts/task orders are those completed within five (5) years from date of issuance of this solicitation or contracts/task orders currently being performed, provided that there have been at least 12 months of completed performance on the contract/task order as of the date of issuance of this solicitation.

L1.17.5 Relevant contracts/task orders are considered to be those contracts/task orders of a similar size, scope, and nature to the FS3i requirements. Past performance submissions may be submitted from any of the significant subcontractors on the Offeror's team; however, no more than two of the past performance submissions are allowed to be from significant subcontractors. The past performance submissions must have been performed within the same contractor organization proposing on a contract/task order resulting from this solicitation (e.g., division, directorate, office, etc.). The Offeror shall state if its team has not performed any contracts/task orders as characterized in this section. Joint-venture companies may submit the past performance of their partner companies for the Government's consideration. It is the responsibility of the Offeror to explain how each past performance reference submission is relevant to the proposed contract. For each contract/task order reference, the Offeror shall identify a customer POC and the individual's contact information. Preferred Government POCs are, in order of descending preference: Program Manager, Contracting Officer's Representative, technical lead, Contracting Officer or Administrative Contracting Officer.

L.17.6 The Offeror shall complete and submit PPQs in the Government format template for each relevant contract identified by the Offeror. The PPQ shall be completed and submitted by the referenced customer to the Government in accordance with the stated due date. The PPQ without customer completion (Part 1 / Page 2 of the PPQ only) shall be filled in and submitted by the Offerors to the Government with the entire electronic submission.

L1.17.7 Subcontractor/Teaming Partner Consent Forms: Completed consent forms shall be submitted as part of the Offeror’s proposal. Past performance information concerning subcontractor and teaming partners cannot be disclosed to a private party without the subcontractor's or teaming partner's consent. Because a prime contractor is a private party, the Government will need that consent before disclosing subcontractor/teaming partner past performance information to the prime during exchanges.

L1.17.8 Organizational Structure Change History: Many companies have acquired, have been acquired by, or have otherwise merged with other companies, and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant efforts or between conclusion of recent past efforts and this acquisition. As a result, it can provide complications in determining what Past Performance is relevant to this acquisition. Offerors shall include a detailed "roadmap" describing all such organizational changes (if applicable), to include specific company names and dates. If there are no such organizational changes, the Offeror shall include a statement to that effect.

L1.18 Volume 5 – INTELLECTUAL PROPERTY

L1.18.1 The Offeror shall detail its ability to comply with the Government’s minimum required data rights regarding technical data, computer software and computer software documentation. The Offeror shall complete the Intellectual Property Schedule found in Section L, in accordance with the outlined instructions. The Intellectual Property Schedule shall be incorporated into any resulting contract.

L1.18.2 Offerors, in developing their proposal response, should consider the following references: Unlimited Rights in Technical Data (as specified in DFAR 252.227-7013(b)(1)), and Computer Software Documentation and Software (as specified in DFARS 252.227-7014(b)(1)); Government Purpose Rights in Technical Data (as specified in DFARS 252.227-7013(b)(2)), and Computer Software Documentation and Software (as specified in DFARS 252.227-7014(b)(2)); Limited Rights in Technical Data (as specified in DFAR 252.227-7013(b)(3)); and Restricted Rights in Software (as specified in DFARS 252.227-7014(b)(3)). The minimum rights considered for Technical Data associated with commercial item acquisitions are specified in DFARS 252.227-7015(b).

L1.18.3 The Offeror shall complete the Intellectual Property Schedule, in accordance with the outlined instructions. The Offeror shall submit all data rights for FS3i. If the proposal includes an assertion of restricted data rights in technical data or limited rights in computer software, the Offeror shall submit the assertion as a Data Rights, License Agreements attachment to the offer in the format specified in DFARS 252.227- 7013 and 252.227-7014. If the Offeror is awarded the contract, the Intellectual Property Schedule shall be incorporated into Section J at award of the contract.

L1.19 Volume 6 – SECURITY

The Security Volume shall demonstrate the Offeror’s ability to meet the security requirements of the solicitation and in accordance with the DD Form 254, and Sections L and M of the RFP, that will enable limited Government transition at the time of award to full performance of the effort. Information on the proposed subcontractor(s) should not be included in the Security Volume, as the Offeror will be responsible for ensuring that its subcontractor(s) meet(s) security requirements in accordance with the DD Form 254 and applicable security policies and regulations. The Security Volume shall provide sufficient information for the Government to evaluate the Security sub-factors set forth in Section M of the solicitation. The Security Volume must specifically contain the below information:

L1.19.1 Facility Clearance (FCL) and Foreign Ownership, Control, or Influence (FOCI). The security volume must provide the following information on the Offeror’s FCL level using the Facility Clearance Level template at Attachment L-8:

· Company Name

· Address and Zip Code

· Commercial and Government Entity (CAGE) Code

· Facility Clearance Level

L1.19.1.1 If the Offeror is a small business joint venture and if 13 Code of Federal Regulations (C.F.R.) 121.103(h)(4) applies, “Offeror” includes the “joint venture itself or the individual partner(s) to the joint venture that will perform the necessary security work.”

L1.19.1.2 The security volume must provide a copy of the most recently adjudicated signed, dated, witnessed or notarized Certificate Pertaining to Foreign Interest (SF 328) for the FOCI evaluation. If any of the responses on the SF 328 are “yes”, the Offer must submit official communications documentation from Defense Counterintelligence and Security Agency (DCSA) that corresponds with the CAGE code(s) and most recently adjudicated SF 328 form submitted that authorizes the company’s FCL with FOCI. Official communications documentation can be in the form of a letter on DCSA letterhead, a memorandum from DCSA with DCSA logo or letterhead, or an email communication from DCSA showing date/time stamp and official DCSA email address. In lieu of documentation from DCSA, the Offeror must submit a screen capture of their current FCL status as reflected in the National Industrial Security System (NISS) that corresponds to the CAGE code(s) submitted. The screen capture must display a date that is no more than thirty (30) days before the date of the proposal submission.

L1.19.1.3 Per C.F.R. 32 Part 117.11, National Industrial Security Program Operating Manual (NISPOM), the Cognizant Security Authority (CSA) will consider a U.S. entity to be under FOCI when a foreign interest has the power to direct or decide issues affecting the entity’s management or operations in a manner that could either result in unauthorized access to classified information; or adversely affect performance of a classified contract or agreement. The U.S. entity may also be considered to be under FOCI when a foreign interest or government is currently exercising, or could exercise, that power, whether directly or indirectly, such as through ownership of the U.S. entity’s securities, by contractual arrangements, or other means. When a CSA has determined that an entity is under FOCI, the primary consideration will be the protection of classified information. The CSA will take whatever action is necessary to protect classified information, in coordination with other affected agencies as appropriate.

L1.19.1.4 NOTE: Offerors (prime contractor, sub-contractor, or small business joint venture member, if applicable) that have an FCL arrangement under a Special Security Agreement (SSA) and require a National Interest Determination (NID) for access to proscribed information shall not gain access to such information until the NID is properly executed by the Government. Proscribed information is identified in 32 C.F.R. §2004.22 and includes Top Secret, COMSEC, SCI, Special Access Programs and Restricted Data. This applies to pre and post award access.

L1.19.2 Personnel Security Clearance (PCL)/Sensitive Compartmented Information (SCI) access. The security volume shall contain a listing of the proposed key personnel required by the RFP or RFQ with the information indicated below using the Personnel Security Clearance template as Attachment L-9:

· Full Name (Last, First, Middle)

· Name of current employer

· Date of Birth

· Place of Birth

· Social Security Number (SSN) *

· Current Investigation (Type and Date)

· SCI Adjudication (Eligibility) Date

· Government Sponsor L1.19.2.1 *NOTE: Directive-Type Memorandum (DTM) 2007-015-USD (P&P) – DoD Social Security Number (SSN) Reduction Plan (and references) - Security Clearance Investigation or Verification and NGA NI 5401.1: Privacy and Civil Liberties Program - The initiation, conduct, or verification of security clearances requires the use of SSN.