SAM_DRAFT ASTRA Section L_30Apr25.pdf

Section L

INSTRUCTIONS

Section L - Instructions, Conditions and Notices to Bidders

L-1 PROGRAM INFORMATION

L-1.1 Program Structure and Objectives The National Air and Space Intelligence Center (NASIC) has a requirement to purchase a full spectrum of Advisory and Assistance Services (A&AS) focused on engineering support to maintain, enhance, and operate the current NASIC mission and incorporate new engineering capabilities required to meet future requirements. The NASIC Advisory Support & Technical Requirement Administration (ASTRA) contractor personnel shall augment the NASIC workforce by providing support for the production of technical intelligence through collection, analysis, planning, processing, dissemination, archiving, and associated activities for NASIC, the USAF, the DoD, and National Level intelligence efforts. The work provides agile and innovative resource capability supporting technical analysis in the Intelligence Community (IC), turning needs derived from innovative thought into intelligence and engineering products, and constantly improving productivity in technical analysis product generation. NASIC’s mission is to discover and characterize air, space, missile, forces, and cyber threats to enable full-spectrum multi-domain operations, drive weapon system acquisition, and inform national defense policy.

The Government intends to issue Task Orders through the ASTRA Indefinite Delivery, Indefinite Quantity (IDIQ) contract. The Offeror’s proposal should be structured to reflect an overall understanding of the technical requirements and a Program Management (PM) strategy for managing the contracted workforce.

L-2 GENERAL INSTRUCTIONS

Offerors will submit an electronic-only proposal; hard copies will not be accepted. The Offeror’s proposal must include all data and information requested by these Instructions to Offerors (ITO) and must be submitted in accordance with these instructions. The Offeror shall be compliant with the requirements as stated in the Performance Work Statement (PWS), and Model Contract. Non-conformance with the instructions provided in this ITO may result in an unfavorable proposal evaluation.

The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but, rather, shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities or experience and will base its evaluation on the information presented in the Offeror’s proposal.

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

In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one copy of all unsuccessful proposals.

L-2.1 Point of Contact The Procurement Contracting Officer (PCO) and Contract Specialist are the sole points of contact for this acquisition. Address any questions or concerns you may have to the PCO. Written requests for clarification may be sent to the PCO at the email in Section 3.8 below.

L-2.2 Debriefings

The PCO will promptly notify Offerors of any decision to exclude them from the competitive range;

where upon, they may request and receive a debriefing in accordance with FAR 15.505. Offerors excluded from the competitive range may request a pre-award debriefing or a post-award debriefing upon notification of exclusion from the competitive range. However, Offerors excluded from the competitive range are entitled to no more than one debriefing. The PCO will notify unsuccessful Offerors in the competitive range of the source selection decision in accordance with FAR 15.506. Upon such notification, unsuccessful Offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or FAR 15.506 as applicable.

L-2.3 Discrepancies If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the PCO in writing with supporting rationale as well as the remedies the Offeror is asking the PCO to consider as related to the omission or error.

L-2.4 Electronic Reference Documents All referenced documents for this solicitation are available on the System for Award Management website at https://SAM.gov. Potential Offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

L-2.5 Communications Exchanges of source selection information between Government and Offerors will be controlled by the PCO. Email may be used to transmit such information to Offerors only if the email can be sent and received encrypted and includes “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line or utilizing the Department of Defense Secure Access File Exchange (SAFE) (https://safe.apps.mil/) to securely transmit encrypted files. Submit a request via email to the PCO (see paragraph 3.7) who will initiate a file drop-off request.

L-3 PROPOSAL PREPARATION INSTRUCTIONS

Organization/Number of Copies/Page Limits Information submitted shall not exceed the page limits stated below for each volume. Evaluators will only read up to the maximum number of pages specified. If the page limit is exceeded, the pages in excess of the limit will be removed from the applicable volume and will not be considered as part of the evaluation.

Page limitations are as follows:

Table 1

Table 1 – Proposal Organization Table VOLUME ITO Paragraph

Number

VOLUME TITLE PAGE LIMIT

I L-4.1 Executive Summary 10 II L-4.2 Technical (Factors 1 & 2) 100 III L-4.3 Price No Limit IV L-4.4 Contract Documentation No Limit V L-4.5 Resume No Limit

L-3.1 Page Limitation for Technical Volume Page limitations shall be treated as maximums. If exceeded, the excess of the limit will be removed from the applicable volume and will not be considered as part of the evaluation. NOTE: Each page shall be counted except the following: cover pages, table of contents, tabs, glossaries, consent and authorization letters, and key personnel résumés. Page limitations may be placed on responses to Evaluation Notices

(ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the Offerors.

L-3.2 Page Size and Format

a) A page is defined as each face of a sheet of paper containing information. Page shall be formatted to fit a piece of paper no larger than 8.5 x 11 inches and may not include foldouts. Pages shall be single spaced typed. Except for the reproduced sections of the solicitation document, the font shall be Calibri and the text size shall be no less than 11 point. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1- inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume. These page size and format restrictions shall apply to responses to ENs.

b) 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 and legible. For tables, charts, graphs and figures, the text shall be no smaller than 8 point.

Table 2 - Technical Volume

Evaluation Factor RFP Section L Section M Entry Gate L-4.2.3 M-2.2

Factor 1: Technical PWS paragraphs 3.2 – 3.9 (including subparagraphs) L-4.2.4 M-2.3

Subfactor One: Research and Development

PWS paragraphs 3.2, 3.8 (including subparagraphs) L-4.2.4.1 M-2.3.1.1

Subfactor Two: Systems Engineering PWS paragraphs 3.4 (including subparagraphs) L-4.2.4.2 M-2.3.1.2

Subfactor Three: Deep Subject Matter Expertise

PWS paragraphs 3.6 (including subparagraphs) L-4.2.4.3 M-2.3.1.3

Subfactor Four: Modeling & Simulation PWS paragraphs 3.5 (including subparagraphs) L-4.2.4.4 M-2.3.1.4

Subfactor Five: NASIC Mission Management

PWS paragraphs 3.4, 3.7, 3.8,

3.9 (including subparagraphs) L-4.2.4.5 M-2.3.1.5

Factor 2: Program Management PWS paragraphs 3.1 (including subparagraphs) L-4.2.5 M-2.3.2

Subfactor One: Management Approach L-4.2.5.1 M-2.3.2.1

• IDIQ Management L-4.2.5.1.1 M-2.3.2.1

• Security PWS paragraphs 13.0, 13.1,

13.2 L-4.2.5.1.2 M-2.3.2.1

• Human Resources L-4.2.5.1.3 M-2.3.2.1

• Staffing Approach L-4.2.5.1.4 M-2.3.2.1

Subfactor Two: Transition Approach PWS paragraph 8.3 L-4.2.5.2 M-2.3.2.2 Subfactor Three: Organizational Conflict of Interest PWS paragraphs 3.1.8, 8.1 L-4.2.5.3 M-2.3.2.3

Subfactor Four: Subcontracting Plan and Subcontractor Management PWS paragraph 3.1.8 L-4.2.5.4 M-2.3.2.4

Subfactor Five: Small Business Participation Commitment Document L-4.2.5.5 M-2.3.2.5

L-3.3 Classified Information Volume II will include classified information, up to the SECRET Collateral level. The Offeror must ensure classified volume is properly labeled and marked, conforming to the DD Form 254 provided in this solicitation. The classified volume may be delivered to NASIC via one of the following three methods: (1) submitted via JWICS email to andrea.carney@nasic.ic.gov and megan.moening@nasic.ic.gov (a NASIC Point of Contact will be provided for coordination of receipt of classified volumes); (2) mailed to NASIC as outlined in DoD Manual DoDM 5200.01, Vol 3 (dated 28 July 2020); or (3) hand carried to NASIC, 4180 Watson Way, WPAFB, OH 45433, using proper courier procedures as outlined in DoDM 5105.21, Vol 1. All proposals must be received by NASIC by 14:00 eastern daylight time on the proposal due date. The proper 2-line Defense Courier Service mailing address for SECRET Collateral is:

If the classified material contains only SECRET collateral information, it can be mailed as outlined in DoDM 5200.01, Vol 3 (dated 28 July 2020) to:

NASIC/A8C

4180 Watson Way Wright-Patterson AFB, OH 45433-5648

Note: These instructions apply only to the classified volume of your proposal. This is the only portion that is allowed to be printed and hand delivered. If you choose to print and hand-carry your Classified volume, you must provide three copies of your printed volume. Each printed copy of the volume shall be separately bound in a three-ring loose leaf binder which shall permit the volume to lie flat when open.

Staples shall not be used. All printed pages shall be in an 8 ½” x 11” format. No foldouts should be included in the printed volume. All material shall be contained within the page limit identified for each volume, and all appendices, charts, graphs, diagrams, tables, photographs, drawings, etc., are included in the page count, with exception of items stated in Table 1 above. Printed files must utilize the same formatting specified in paragraph L-3.2.

L-3.4 Cross-Referencing To the greatest extent possible, each volume shall be written on a standalone basis so that its contents may be evaluated with a minimum of cross referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity.

L-3.5 Glossary of Abbreviations and Acronyms Each volume shall contain a glossary of all abbreviations and acronyms used, and an explanation for each.

Glossaries do not count against the page limitations for their respective volumes.

L-3.6 Submission of Proposals The Offeror shall submit all UNCLASSIFIED portions of volumes I through IV in electronic format via DoD SAFE transmission, https://safe.apps.mil/. To request a drop off code for DoD SAFE please send an email to margaret.lennen@us.af.mil and jeffrey.godby.1@us.af.mil, and a drop off code will be provided within 24 hours. A drop off code must be requested no later than 5 days before the proposal due date. The Offeror shall submit the CLASSIFIED addendum to its proposal in accordance with paragraph L-3.3. The Offeror shall use separate files to permit rapid location of all portions, including subfactors, exhibits, mailto:andrea.carney@nasic.ic.gov https://safe.apps.mil/ mailto:margaret.lennen@us.af.mil annexes, and attachments, if any. The UNCLASSIFIED electronic copies of the proposal shall be submitted using the following instructions:

1) Electronic files shall be submitted via DoD SAFE. In order to submit via DoD SAFE, a drop-off request is required. In order to receive a DoD SAFE drop-off, email the contracting officer and contract specialist listed in paragraph 3.7 below no more than 14 days and no less than 3 days prior to proposal submittal date.

2) Submit documents using Microsoft Office 2016 or greater:

3) Word documents – Set "Save as type" to "Word Document (*.docx)"

4) Excel spreadsheets – Set "Save as type" to "Excel Workbook (*.xlsx)."

5) PowerPoint presentations – Set "Save as type" to "PowerPoint Presentation (*.pptx)."

6) Submit any Microsoft Project files in Microsoft Project 2016 or greater. There are no special

“save” functions required for later versions of Project.

7) Submit PDF documents using only Adobe Acrobat XI (11) or later. Do NOT submit any documents in PDF format that are copied as "images." When creating PDF files always create to enable textual search and copy functions.

Offerors are cautioned to strictly comply with all instructions within this solicitation to ensure submission of a complete proposal. Failure to furnish a complete proposal at the time of proposal submission may result in elimination from consideration for award. The Government will not accept any changes to an Offeror’s proposal after the closing date of this solicitation unless requested by the Government (see FAR

15.208 for further information regarding late proposals).

For all CLASSIFIED information, follow instructions in paragraph L-3.3. Classified Information.

L-3.7 Distribution Proposals shall be addressed to both PCO and contract specialist below and submitted via DoD SAFE (safe.apps.mil) to:

AFLCMC/PZIEC AFLCMC/PZIEC

Attn: Margaret Lennen Attn: Jeffrey Godby margaret.lennen@us.af.mil jeffrey.godby.1@us.af.mil Reference: FA8604-25-R-B017 Reference: FA8604-25-R-B017

L-4 PROPOSAL ORGANIZATION

L-4.1 Volume I – Executive Summary In the Executive Summary volume, the Offeror shall provide the following information:

L-4.1.1 Narrative Summary The narrative summary of the entire proposal should be concise, to include addressing the significant risks, and highlighting any key or unique features, excluding price. The salient features should tie in with Section M evaluation factors/subfactors. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

L-4.1.2 Table of Contents Include a master table of contents of the entire proposal.

L-4.2 Volume II – Technical Volume

L-4.2.1 General mailto:margaret.lennen@us.af.mil

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation. Excluding Entry Gate (pass/fail), each subfactor is eligible to be awarded strengths, which allow the Offeror to receive a subfactor technical rating higher than Green/Acceptable. The Government reserves the right to assess and award strengths, with or without discussions. Simply repeating Section L, Section M, or PWS language as substantiation will not justify the Government’s evaluation of an approach as a strength.

Experience is defined in this solicitation as an Offerors’ participation in work that is similar in scope and technical complexity to what is contained in the PWS. For all listed experience, the Offeror shall include relevant and recent contract performance information including a description of the work performed by the Offeror, contract number, and the period in which the work was performed. All cited work must have occurred within the last three years with at least six months of performance.

L-4.2.2 Format and Specific Content All specific Technical subfactors set forth in Section M and instructions set forth in Section L must be addressed. Describe your proposed approach to meeting the requirements of each Technical subfactor.

a) The Technical volume shall be organized according to the following general outline:

b) Table of Contents

c) List of Tables and Drawings

d) Glossary

e) Entry Gate

f) Factor One: Technical

1) Subfactor One: Research and Development

2) Subfactor Two: Systems Engineering

3) Subfactor Three: Deep Subject Matter Expertise

4) Subfactor Four: Modeling & Simulation

5) Subfactor Five: NASIC Mission Support

g) Factor Two: Program Management

1) Subfactor One: Management Approach

• IDIQ Management

• Security

• Human Resources

• Staffing Approach

2) Subfactor Two: Transition Approach

3) Subfactor Three: Organizational Conflict of Interest

4) Subfactor Four: Subcontracting Plan and Subcontractor Management

5) Subfactor Five: Small Business Participation Commitment Document

h) Factor Three: Price

L-4.2.3 Entry Gate: Compliance The Offeror must provide a copy of their Defense Counterintelligence and Security Agency (DCSA)Verification inquiry from the National Industrial Security database (NISS) showing that they possess a Top-Secret facility clearance at the time of proposal submission. The copy of the DCSA Verification Inquiry shall be placed as the first page of the Technical Volume, e) Entry Gate.

L-4.2.4 Factor One: Technical

L-4.2.4.1 Subfactor One: Research and Development: The Offeror’s proposal shall provide a detailed description of the approach to support government execution of Research and Development (R&D) programs, to include planning, prototyping, and advocating. In addition, the Offeror shall provide one example of experience their company or team-mates have with regard to Task 1: Planning and Task 2:

Prototyping, and Task 3: Advocating, and for all the tasks that are addressed, the Offeror shall clearly show in their staffing plan how they would obtain qualified personnel for each task.

L-4.2.4.1.1 Planning: The Offeror shall describe the experience they have developing and managing R&D programs for the acquisition of new sensors, data collection, data processing, data analysis or data delivery capabilities, to include technical requirements, test & evaluation, milestones, costs, schedules, and contract strategy. If the example of experience wasn’t for the IC, the Offeror shall explain how the experience would be applied to IC objectives. Also, for the example of experience, the Offeror shall include a description of the sponsor organization, the role your company (or team-mates) played and the scale of results or impacts the R&D had for the sponsor organization.

L-4.2.4.1.2 Prototyping: The Offeror shall describe the experience analyzing and assessing R&D prototypes and supporting transition of the prototype to being used in its target operating environment. If the example of experience wasn’t for the IC, the Offeror shall explain how the experience would be applied to IC objectives. Also, for the example of experience, the Offeror shall include a description of the sponsor organization and the scale of results or impacts the R&D had for the sponsor organization.

L-4.2.4.1.3 Advocating: The Offeror shall describe the experience developing and presenting R&D proposals for the purpose of gaining advocacy or funding from sponsor or stakeholder organizations. If the example of experience wasn’t for the IC, the Offeror shall explain how the experience would be applied to IC objectives. Also, for the example of experience, the Offeror shall include a description of the size or scale of the R&D, the level of seniority within the sponsor or stakeholder organizations, the role your company (or team-mates) played and the outcome or results of the R&D proposal.

L-4.2.4.2 Subfactor Two: Systems Engineering: The Offeror’s proposal shall provide a detailed description of the experience they have in supporting systems engineering, Model Based Systems Engineering (MBSE), and architecture tasks. In addition, the Offeror shall provide at least one example of experience their company or team-mates have with regard to either/both Digital Transformation or IA/AI/ML. Additionally for the examples the Offeror addresses they shall clearly show in their staffing plan how they would obtain qualified personnel for the task(s).

L-4.2.4.2.1 Digital Transformation: The Offeror shall describe the experience they have developing and managing plans and programs to digitally transform an organization, to include their application of cloud technology and modernizing or adapting legacy systems to work in cloud computing environments. If the cloud modernization wasn’t for multiple, hybrid classified IC clouds, then the Offeror shall explain how their experience would be applied to IC objectives. Also, for the example of experience, the Offeror shall include a description of the sponsor organization, the size or scale of the digital transformation, the role their company (or team-mates) played and the results or impacts the digital transformation had for the sponsor organization.

L-4.2.4.2.2 IA/AI/ML: The Offeror shall describe the experience they have developing and managing plans and programs to guide intelligent automation, artificial intelligence or machine learning implementation. If the IA/AI/ML wasn’t for the IC, then the Offeror shall explain how their experience would be applied to IC objectives. Also, for the example of experience, the Offeror shall include a description of the sponsor organization, the scale or complexity or the IA/AI/ML, the role their company (or team-mates) played and the results or impacts the IA/AI/ML had for the sponsor organization.

L-4.2.4.3 Subfactor Three: Deep Subject Matter Expertise: The Offeror’s proposal shall provide a detailed description of their approach to provide deep subject matter expertise. In addition, the Offeror shall provide one example of experience their company or team-mates have with regard to the tasks that are addressed, the Offeror shall clearly show in their staffing plan how they would obtain qualified personnel for the task(s).

L-4.2.4.3.1 SME in NASIC Mission: The Offeror shall describe the experience they have providing deep expertise in phenomenology, sensors, or analysis to inform acquisition of new capabilities or plans for future architectures. If the example was not directly applicable to the NASIC mission areas, then the Offeror shall explain how their experience could be applied to NASIC mission areas or IC objectives.

Also, for the example of experience, the Offeror shall include a description of the depth or scale of their expertise, the role their company (or team-mates) played and the results or impacts the expertise had for the customers or sponsor organizations.

L-4.2.4.3.2 Technical (Proxy) Project Management: The Offeror shall describe experience they have providing (proxy) project management of complex, technical projects, to include independent planning, programming, budgeting, leading technical teams, contract execution, briefing and advocating the program to senior government leaders. If the example wasn’t supporting the IC, the Offeror shall explain how the experience could be applied to IC objectives. Also, for the example of experience, the Offeror shall include a description of the size of the project, the dynamics of the technical team, the scope of senior level interactions, the role their company (or team-mates) played and the results or impacts the project management had for the sponsor organizations.

L-4.2.4.3 Collaboration: The Offeror shall describe the experience they have providing deep subject matter expertise to (with government oversight) independently collaborate with, inform and influence government planning, programming and budget decisions at the very highest levels of US or Foreign governments. If the example is not for the IC, the Offeror shall explain how the experience would be applied to IC objectives. Also, for the example of experience, the Offeror shall include a description of the type and scale of expertise, the government organizations and levels the expertise informed, the role your company (or team-mates) played, and the results or impacts of the engagements.

L-4.2.4.4 Subfactor Four: Modeling & Simulation: The Offeror’s proposal shall provide a detailed description of the approach to support Modelling & Simulation tasks described in PWS. In addition, the Offeror shall provide one example of experience their company or team-mates have with regard to all of the tasks, or (optional) they can provide an example of experience for all of the tasks, and for the tasks that are addressed, the Offeror shall clearly show in their staffing plan how they would obtain qualified personnel for the task(s).

L-4.2.4.4.1: M&S of Threat Systems: The Offeror shall describe the experience they have guiding the development and management of plans and programs to conduct modelling & simulation on objects or systems. If the M&S isn’t related to intelligence on military threat systems, then the Offeror shall explain how their experience would be applied to IC objectives. Also, for the example of experience, the Offeror shall include names or classes of systems modelled, the M&S techniques or products used, the size or scale of the M&S, the role their company (or team-mates) played and the results or impacts the M&S had for the sponsor organization.

L-4.2.4.4.2: M&S of engagements: The Offeror shall describe the experience they have guiding the development and management plans and programs to conduct modelling & simulation on engagement scenarios. If M&S isn’t related to intelligence on military engagement scenarios, then the Offeror shall explain how their experience would be applied to IC objectives. Also, for the example of experience, the Offeror shall include a description of the engagement scenarios modelled, the M&S techniques or products used, the size or scale of the M&S, the role their company (or team-mates) played and the results or impacts the M&S had for the sponsor organization.

L-4.2.4.4.3: Verification & Validation of M&S: The Offeror shall describe the experience they have conducting verification delivered systems meet requirements and validating delivered systems meet user requirements. If the V&V isn’t related to IC M&S systems, then the Offeror shall explain how their experience would be applied to IC objectives. Also, for the example of experience, the Offeror shall include a description of the sponsor organization, the size or scale of the V&V, the role their company (or team-mates) played and the results or impacts the V&V had for the sponsor organization.

L-4.2.4.5 Subfactor Five: NASIC Mission Support: The Offeror’s proposal shall provide a detailed description of their approach to support a broad range of services that generally require specific skills or certifications, but not specific knowledge about NASIC missions. In addition, the Offeror shall provide one example of experience their company or team-mates have with regard to each task and for the tasks that are addressed, the Offeror shall clearly show in their staffing plan how they would obtain qualified personnel for the task(s).

L-4.2.4.5.1 Facility infrastructure support: The Offeror shall describe the experience they have for planning and managing the electrical, lighting, plumbing, heating, ventilation & air conditioning and similar infrastructure needs of large facilities. Also, for the example of experience, the Offeror shall include a description of the sponsor, the facilities they supported, the role their company (or team-mates) played and the results or impacts the facility support had for the customers or sponsor organizations.

L-4.2.4.5.2 Secure Facilities: The Offeror shall describe the experience they have managing classified facilities, to include security policies, and procedures to open & close the facilities, and response to alarms. Also, for the example of experience, the Offeror shall include a description of the sponsor, the facilities they supported, the role their company (or team-mates) played and the results or impacts the facility support had for the customers or sponsor organizations.

L-4.2.4.5.3 Information Technology and Cyber Security: The Offeror shall describe their experience providing information technology and cyber security support. If the example isn’t for classified government networks, the offer shall explain how their experience would be applied to classified networks. Also, for the example of experience, the Offeror shall include a description of the sponsor, the scale of the networks they supported, the role their company (or team-mates) played and the results or impacts the IT and Cyber support had for the customers or sponsor organizations.

L-4.2.4.5.4 Other mission support: The Offeror shall describe their experience providing support for one or more of the tasks in PWS 3.4, 3.7, 3.8, 3.9. The Offeror shall include a description of the sponsor, the role their company (or team-mates) played and the results or impacts the support has for the customers or sponsor organizations.

L-4.2.5 Factor Two: Program Management

L-4.2.5.1 Subfactor One: Management Approach. Discuss the Offeror’s practices to successfully meet the ASTRA management requirements of the ASTRA PWS in accordance with the five (5) Measures of Merit identified in Section M.

L-4.2.5.1.1 IDIQ Management: The Offeror shall provide its approach to manage the ASTRA IDIQ contract. The Offeror must identify a management presence physically located within 25 miles of Wright- Patterson Air Force Base. Cite specific Prime experience as appropriate to substantiate the Offeror’s capability to maintain continuity of mission support during transition following award and successfully manage the ASTRA IDIQ contract. Cite specific Prime experience managing 15 or more concurrent task orders on an IDIQ and/or individual services contracts.

L-4.2.5.1.2 Security: The Offeror shall provide specific Prime experience as appropriate to substantiate the Offeror’s capability to manage a TS//SCI contract. b) The Offeror demonstrates its ability to destroy classified material and how they will maintain a complete listing of classified material issued by the Government and maintained at the contractor’s facility in performance of individual TOs to include: the title of the materials; the origination date; the overall classification; the type of material (i.e., report, electronic media, etc.) the number of copies held; and any other information necessary to identify the inventory. c) The Offeror provides documentation that they have individuals who are TS//SCI cleared.

L-4.2.5.1.3 Human Resources: The Offeror shall provide its approach to attract, recruit, hire, train and retain qualified management and technical personnel within 25 miles of Wright-Patterson Air Force Base for at least 75% of the work to ensure the Offeror’s team possesses or can readily obtain personnel with the appropriate security clearance, levels of education, experience and expertise to accomplish ASTRA tasks. Identify Prime approach to ensure continuation of services during personnel absences due to sickness, leave, voluntary or involuntary termination from employment such that impact to the Government is minimal. Furthermore, the approach must discuss the Offeror’s ability to effectively manage and ensure continuity of services during 24/7 shift work; travel; personnel issues; absences due to sickness, leave, and voluntary or involuntary termination from employment such that disruption to mission accomplishment is minimal. Provide approach for maintaining currency of any required certifications or specialized training.

L-4.2.5.1.4 Staffing Approach: The Offeror shall submit an organizational chart which illustrates a clear understanding of the manning requirements necessary for each of the functional areas. The Offeror’s organizational chart shall include: a) The number of personnel required to perform each part of the requirements. b) The proposed organization to convey the structure, staffing, and key aspects of the Offeror’s management methodology over the life of the contract.

The Offeror shall also submit a detailed narrative to describe the staffing approach illustrated in the organizational chart described above. The narrative should include: a) The minimum qualification requirement for each person that will perform the functions found in the PWS. b) Information for recruiting and retaining qualified personnel capable of meeting the requirements of this solicitation.

L-4.2.5.2 Subfactor Two: Transition Approach The Offeror shall submit a Transition Approach that addresses the Offeror’s proposed approach to staffing, equipment, supplies, and security considerations. The Offeror’s Transition Plan shall include the following: a) A plan for ensuring personnel have the required clearance, as outlined in the DD Form 254, Attachment X to the solicitation, at the beginning of the period of performance. See schedule of SF1449 for Period of Performance. b) Procedures to provide appropriate mix of skilled employees to assume responsibilities for all contract functions for a successful transition from the incumbent performing this work.

L-4.2.5.3 Subfactor Three: Organizational Conflict of Interest The Offeror shall provide a detailed narrative that discusses the Offeror’s approach for detecting, disclosing, avoiding, and mitigating OCI issues and risks IAW FAR Part 9.5, including those resulting from teaming arrangements. The narrative should include: a) The adequate employee conflict of interest training and compliance with non-disclosure policies and directives. b) The Prime experience or staff qualifications to substantiate the Offeror’s capability.

L-4.2.5.4 Subfactor Four: Subcontracting Plan and Subcontractor Management Discuss the Offeror’s approach to subcontractor management. The Offeror’s approach must reference when subcontracting arrangements will be utilized for coverage of the mission areas and disciplines identified in PWS paragraphs 1.1 – NASIC Missions (including subparagraphs) and 1.2 – NASIC Disciplines (including subparagraphs). The Offeror must identify if the subcontractor qualifies as a small business under NAICS code 541330. Identify the Offeror’s approach to manage subcontractors utilized on the contract. Discuss the Offeror’s approach to comply with the Limitations on Subcontracting IAW FAR 52.219-14.

L-4.2.5.5 Subfactor Five: Small Business Participation Commitment Document The Offeror shall submit a Small Business Participation Commitment Document (SBPCD) which specifies the Offeror’s level of commitment to small business utilization for the effort to be performed. A SBPCD is required from all Offerors, to include small businesses. This also applies to companies with commercial plans and comprehensive subcontracting plans. The winning Offeror’s SBPCD will be incorporated as an attachment to the awarded contract. The SBPCD is separate from the Subcontracting Plan required by FAR 19.704. The SBPCD must address the following:

The Offeror shall submit a Small Business Participation Commitment Document (SBPCD) which specifies the Offeror’s level of commitment to small business utilization. A SBPCD is required from all Offerors, including small businesses. This also includes companies with commercial plans and comprehensive subcontracting plans. The winning Offeror’s SBPCD will be incorporated as an attachment into the awarded contract. The SBPCD is separate from the Subcontracting Plan required by FAR 19.704. The SBPCD must address the following:

a) The extent to which the Offeror will utilize small business, small disadvantaged business, women-owned small business, Historically Underutilized Business Zone small business, veteran-owned small business, and service-disabled-veteran-owned small business.

b) Level of commitment to use such firms identified above to include strength and specificity of commitment (commitment type, legal binding of commitment, an specificity of commitment in relation to ASTRA).

c) Types of work to be performed by small business.

d) Statement of quantitative degree to which small businesses (including small businesses in all identified socio-economic categories) will participate in ASTRA. Small business prime performance will count against proposed quantitative degree of small business participation.

e) Additionally, all Offerors must submit the supporting documentation that will be excluded from the page count. This supporting documentation will NOT be incorporated into any resulting contract.

1) Past performance information to demonstrate compliance with the requirements of FAR

52.219-8, Utilization of Small Business Concerns, including the extent to which small business performance objectives/requirements were met for the contracts that required submission of a Small Business Participation Plan or other small business participation/utilization document. Copies of contractual reports may be submitted to validate compliance with requirements of FAR 52.219-8. Explanation of efforts where minimum quantitative requirements and/or goals were not met should be provided. Supporting documentation shall be relevant to the requirements of this solicitation and shall be within the past five years. As mentioned previously, this documentation is excluded from the page count.

2) Past performance information to demonstrate compliance with the requirements of FAR 52.219-9 (DEVIATION 2016-O0009) Small Business Subcontracting Plan (when applicable), including the extent to which applicable goals and other small business performance objectives/requirements were met for the contracts submitted to demonstrate compliance. Explanation of efforts where goals were not met should be provided. Supporting documentation shall be relevant to the requirements of this solicitation and shall be within the past five years. As mentioned previously, all supporting documentation is excluded from the page count.

f) The work to be performed directly by a small business prime Offeror shall be evaluated as Small Business Participation. Small business prime Offerors shall include their information in the above requested section 4.2.5.6, subparagraphs a-d as required.

g) SBPCD enforceable, contractual requirements shall require periodic progress reporting to facilitate Government monitoring in the event of an award. Offerors are to propose quarterly reporting for the requirements in section 4.2.5.6, sub-paragraphs a-d.

h) Prime Offeror’s Size: Identify the applicable size and applicable socioeconomic categories for the PRIME Offeror only when submitting your proposed SBPCD. Include this information within the initial section of the proposed SBPCD and check all applicable boxes:

1) Prime Offeror’s Size {} Other than Small Business or

2) {} Small Business also categorized as a

3) {} Small Disadvantaged Business (SDB)

4) {} Woman-Owned Small Business (WOSB)

5) {} Historically Underutilized Business Zone (HUBZone) Small Business

6) {} Service-Disabled Veteran Owned Small Business (SDVOSB)

Consent/Authorization Letters Along with the information required in this section, the Offeror shall submit a consent letter executed by each subcontractor, teaming partner, and/or joint venture partner, authorizing release of adverse past performance information to the Offeror so the Offeror can respond to such information. For each identified effort for a commercial customer, the Offeror shall also submit a client authorization letter, authorizing release to the Government of requested information on the Offerors’ performance. See attachments 4 and 5 for sample consent and client authorization letters. These letters will not be included in the overall page count.

L-4.3 Volume III - Price

The Price volume is currently in progress and is excluded from this draft. The Price volume will be provided with the Official Request For Proposal.

L-4.4 Volume IV Contract Documentation

L-4.4.1 Model Contract/Representations and Certifications The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The Offeror’s proposal shall complete in its entirety the “Offeror” portion of the Standard Form (SF33). An official having the authority to contractually bind your company shall sign the SF33 IAW FAR 4.102. The SF33 must bear an original signature of an authorized representative for the Offeror. Complete all required representations and certifications or indicate if information is contained in https//sam.gov.

L-4.4.2 Exceptions to Solicitation Requirements Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken. Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 2.

Table 2 - Solicitation Exceptions

Solicitation Document

Page/ Paragraph

Requirement/ Portion Rationale

SOO, SOW, SPEC,

Model Contract, ITO, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

L-4.4.3 Other Information Required

L-4.4.3.1 Authorized Offeror Personnel Provide the name, title, email address and telephone number of the company/division point of contact regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

L-4.4.3.2 Government Offices Provide the mailing address, email address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office. Also, provide the name and telephone and fax number for the Administrative Contracting Officer (ACO).

L-4.4.3.3 Company/Division Address, Identifying Codes, and Applicable Designations Provide company/division's street address, county and facility code; CAGE code; DUNS code; TIN; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

L-4.4.3.4 GFP and/or Base Support Requirements The Government plans to provide the items listed in the Task Order PWSs section 5.3.

L-4.4.3.5 Proposal Acceptance Period The proposal acceptance period is specified in Section A of the model contract/solicitation. The Offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this date.

L-4.5 Volume V – Resume

In the Resume volume, the Offeror shall provide the following information:

L-4.5.1 Resumes The Offeror shall submit resumes of all proposed personnel to meet the ASTRA requirements, and each resume should include at a minimum a) security clearance, b) levels of education, and c) experience and expertise to accomplish ASTRA tasks. No names shall be included in the resumes but rather have the appropriate labor category and distinguished by number.

L-5 LIST OF ATTACHMENTS

Section L attachments are in progress and are excluded from this Draft. A list of attachments will be provided with the Official Request For Proposals.