Attachment 2 _ 52.212-1 Instructions to Offerors_APS_20261023.pdf

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

52.212-1 Instructions to Offerors—Commercial Products and Commercial

Services.

1. As prescribed in 12.301(b)(1), insert the following provision:

Instructions to Offerors—Commercial Products and Commercial Services (Sep 2023)

(a) North American Industry Classification System (NAICS) code and small business size standard. However, the small business size standard for a concern that submits an offer, other than on a construction or service acquisition, but proposes to furnish an end item that it did not itself manufacture, process, or produce is 500 employees, or 150 employees for information technology value-added resellers under NAICS code 541990, if the acquisition—

(1) Is set aside for small business and has a value above the simplified acquisition threshold;

(2) Uses the HUBZone price evaluation preference regardless of dollar value, unless the Offeror waives the price evaluation preference; or

(3) Is an 8(a), HUBZone, service-disabled veteran-owned, economically disadvantaged women-owned, or women-owned small business set-aside or sole-source award regardless of dollar value.

(b) Submission of offers. Submit signed and dated offers to the office specified in this solicitation at or before the exact time specified in this solicitation.

Proposal Structure.

The following Proposal Structure Table is to assist the offeror in organizing the proposal submission documents to ensure the Government can easily identify which documents apply to which criteria for evaluation purposes. Offerors must adhere to the Volume

Numbers, Titles, Format and/or Templates, and Page Limitations (if any) provided in the

Proposal Structure Table, any deviation will result in proposal rejection. A title page or title slide is permitted and will not count towards the total page count.

Phase of Submittal

Volume Factor Description Page Count

1 1 Technical

1 1 1.a Agile Implementation Plan [Word Document or PDF]

15 pages

1 1 1.b Key Personnel [Word Document or PDF] 3 pages

1 1 1.c Cybersecurity Compliance Gate [Word Document or PDF]

3 pages https://www.acquisition.gov/far/12.301#FAR_12_301

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

2 1 1.d

Technical Presentation and Agile Scenarios – Part 1 - Implementation and Alignment with Subfactor 1.a – Agile Implementation Plan and SOO Oral Presentation [PowerPoint Slides or PDF] and Part 2 - Government provided Scenario Injects Oral Presentation [NO slides]

40 slides in total

2 1 1.d Visit Authorization Request (VAR) via the Defense Information System for Security

(DISS)

N/A

2 1 1.d Oral Presentation Attendees List [Word Document or PDF]

1 page

3 1 1.e Proposed Performance Work Statement (PWS) [Word Document]

50 pages

3 1.e (Contract Data Requirements List (CDRL)) [Word Document]

Unlimited

3 1 1.e Quality Assurance Surveillance Plan (QASP) [Word Document]

Unlimited

3 1 Compliance Matrix [Excel Spreadsheet] Unlimited

3 1 1.f Transition Plan [Word Document or PDF] 10 pages

1 2 2 Organizational Conflict of Interest (OCI) Mitigation Plan [Word Document or PDF]

10 pages

3 3 3 Cost/Price Workbook [Excel Spreadsheet]

Unlimited

4 N/A Administration

1 4 Cover Letter [Word Document or PDF] 3 pages

3 4 Amendment Acknowledgements [Word Document or PDF]

Unlimited

3 4 Teaming Agreements (If Applicable) [Word Document or PDF]

Unlimited

1 & 3 4 NAICS Size Standard Certification [Word Document or PDF]

1 page

3 4 Representations and Certifications [Word Document or PDF]

Unlimited

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

Proposal File Format.

a. No paper version shall be submitted; any paper media submitted will not be evaluated.

b. File naming shall NOT include special characters (e.g. ~, #, %, &, *, {, }, \, :, , ?, /, +, |, and ”) shall be 40 characters or less and use “_” instead of spaces when possible; abbreviations are permissible within file names.

c. The Offeror shall utilize the following file naming convention when submitting documents: OfferorName_VOLUME_X_FileName_ORIGINAL

d. In the event that the Government requests revisions, in whole or in part, to the

Offeror’s proposal submission, the Offeror shall submit using the following convention: OfferorName_VOLUME_X_FileName_REVISION#

e. All information shall be confined to the appropriate file. The offeror shall confine submissions to essential matters, sufficient to define the proposal in a concise manner, to permit a complete and accurate evaluation of each proposal.

f. Each paragraph should be single-spaced and shall be separated by at least one blank line.

g. Offerors shall not make any changes to the solicitation. Any objections to the terms and conditions of the solicitation should be addressed to the Procuring

Contracting Officer (PCO). If the proposal takes exceptions to the terms and conditions of the solicitation, all exceptions shall be denoted in a cover letter to the proposal; however, exceptions to the solicitation taken in the proposal may result in the offer being non-compliant.

h. It is the sole responsibility of the Offeror to ensure the electronic files submitted are virus-free and can be opened and read by the Government.

i. OFFERORS ARE HEREBY ON NOTICE THAT A FAILURE TO SUBMIT ALL THE

REQUIRED DOCUMENTATION IN EXACTLY THE MANNER (TIMELINESS

AND FORMAT) SPECIFIED IN THE SOLICITATION MAY CONSTITUTE A

BASIS FOR THE GOVERNMENT TO REJECT A PROPOSAL AS NON-

COMPLIANT AND THEREFORE UNACCEPTABLE, AT THE SOLE

DISCRETION OF THE SOURCE SELECTION AUTHORITY. FURTHERMORE,

SHOULD AN OFFEROR INDICATE IN ITS PROPOSAL THAT: IT CANNOT OR

WILL NOT MEET ONE OR MORE CONTRACT REQUIREMENTS; PROVIDE

AN APPROACH THAT CLEARLY DOES NOT MEET ONE OR MORE

CONTRACT REQUIREMENTS; OR, INCLUDE PROPOSAL INFORMATION

THAT PROMPTS THE GOVERNMENT TO QUESTION THE OFFEROR’S

COMPLIANCE WITH ONE OR MORE CONTRACT REQUIREMENTS, THE

GOVERNMENT MAY DETERMINE, AT ITS DISCRETION THAT THE

OFFEROR’S PROPOSAL IS NON-COMPLIANT, AND THEREFORE

INELIGIBLE FOR AWARD.

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

Proposal File Instructions.

a. General requirements:

1. All files shall be clearly titled to represent the specific portion of the

Offeror’s Volume, as identified in the Volume’s Table of Contents. A Table of Contents should be created using the Table of Content feature in MS

Word. MS Word (doc) files shall use the following page setup parameters:

• Utilize Microsoft Office 365

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

• Gutter – 0”

• From Edge – Header, Footer 0.5”

• Page Size, Width – 8.5”

• Page Size, Height – 11”

2. Each page shall include the Offeror’s name, proposal Volume number, file name, date, solicitation number (and amendment, if applicable), and

“SOURCE SELECTION INFORMATION -- SEE FAR 2.101 AND 3.104” in the header and/or footer.

3. Files shall not be locked, encrypted, or otherwise contain barriers to opening.

4. Compressed files (e.g. *.zip) and executable files (e.g. *.bat, *.exe, *.jar, *.vb, *.wsf) will NOT be accepted.

5. Offerors shall submit proposals that are clear, concise, and readily readable. To ensure accurate analysis by automated evaluation tools and maintain the integrity of the source selection process.

b. Visible Text Only: All proposal content must be presented as visible text. The inclusion of any concealed text is strictly prohibited. Concealed text includes but is not limited to:

1. Micro-text (text with a font size below 8pt); White text on a white background;

2. Text utilizing colors that render it indistinguishable from the background;

Text hidden within images or graphics.

3. Arial font is required with 12-point minimum font size. (EXCEPTIONS:

headers/footers with administrative information. Tables, screenshots, illustrations, and/or images have no font/font size restrictions but must be legible [tables, screenshots, illustrations, and/or images shall not be utilized to encompass excessive amounts of information, i.e., putting substantial portions of proposal in tables to circumvent using Arial 12])

c. Formatting Consistency: All text must apply uniform formatting throughout the proposal. Variations in font size, color, or style that the Government deems manipulate or obscures the readability of content are prohibited.

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

d. Compliance Verification: The Government may conduct technical verification to ensure compliance with these requirements. Proposals found to contain concealed or manipulated text may be considered non-compliant and may be rejected. Adobe Acrobat (pdf) files shall be able to be searched for text and shall allow the Government to copy and paste from the proposal. The Government will not accept scanned documents in lieu of this requirement and will not invoke the text recognition feature within Adobe Acrobat.

e. Microsoft (MS) Excel files shall:

1. Utilize Microsoft Office 365.

2. Be editable and executable by the Government and shall clearly show the calculations and formulas used in each cell.

3. NOT include hidden formulas or protected cells; shall show the formulas used to calculate the rates/factors for each entry and shall not be included as an un-executable, un-editable, or flat file such as an embedded picture

(Enhanced Metafile).

4. Contain mathematical explanations for any embedded macro/extended formula utilized, clearly describing the functioning of the macro or extended formula.

f. Microsoft PowerPoint files shall:

1. Utilize Microsoft Office 365.

2. Have the text and tables presented in each slide that are legible and clearly visible to the audience and in accordance with the font, minimum sizes and other limitations set forth in this section.

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

Phase I – Proposals - must include the following, but each Volume shall be submitted as a separate file:

• Volume 1 – Factor 1 – Technical, Subfactor 1.a – Agile Implementation Plan

• Volume 1 – Factor 1 – Technical, Subfactor 1.b – Key Personnel

• Volume 1 – Factor 1 – Technical, Subfactor 1.c – Cybersecurity Compliance

Gate

• Volume 2 - Factor 2 - OCI Mitigation Plan

• Volume 4 – Administration

i. Cover Letter

ii. NAICS Size Standard Certification

Phase I - Instructions

VOLUME 1 - FACTOR 1 – Technical – Instructions

Volume 1 contains the technical capabilities, workforce management strategies, and cybersecurity compliance necessary to execute the Agile Professional Services contract.

i. Subfactor 1.a – Agile Implementation Plan (15 Pages Max)

The Offeror shall provide a detailed, actionable Agile Implementation Plan (not to exceed 15 pages) describing their operational approach to executing Agile Professional

Services across the Capability Program Executive Simulation, Training, Test and Threat

(CPE ST3) enterprise traceable to the Attachment 1 - Statement of Objectives. To demonstrate an executable baseline, the plan must clearly address all the following:

1. Cultural Change Management Strategy:

a. The Offeror shall provide a detailed actionable method for migrating the Offeror’s workforce to a cross-functional operating mindset. The Offeror’s strategy shall explicitly outline the approach for driving cultural adoption and securing compliance from Government team members.

2. Dynamic Resource Allocation Mechanics:

a. The Offeror shall detail clear operational triggers, workflows, and triage mechanics for reallocating cross-functional teams to meet emergent, high-priority demands across all CPE ST3 program offices and directorates for clear lines of communication and delegation of tasks.

3. Backlog Prioritization and Sizing Strategy:

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

a. The Offeror shall explicitly detail the repeatable strategy and methodology for collaborating with Government Product Owners to assign priority weights and

Level of Effort (LOE) estimates to incoming backlog tasks to ensure transparent planning and optimal capacity utilization.

4. Manpower Resource Efficiency:

a. The Offeror shall describe specific strategies to eliminate resource idling ("bench time") and leverage multi-skilled professionals to maximize capacity pool productivity.

b. The Offeror shall clearly articulate how their efficiency strategies translate into a tangible, measurable benefit to the Government.

5. Commercial Business Model Application:

a. The Offeror shall provide a practical translation of commercial Agile practices into a compliant Government operational model.

ii. Subfactor 1.b – Key Personnel (Agile Program Manager - 3 Pages Max /

Person)

The Offeror shall propose a qualified individual(s) to serve as the Agile Program

Manager(s) (APM) to lead the overall contract effort, manage the capacity pool, and interface with Government leadership. The Offeror shall submit a resume(s) (not to exceed 3 pages each) demonstrating that the proposed APM(s) meets or exceeds the following minimum qualifications:

1. Experience:

a. The Offeror shall propose Key Personnel with minimum of five (5) years of demonstrated program management experience leading Agile teams or managing cross-functional, capacity-based professional services contracts in either a federal or commercial environment, with at least three (3) of those years occurring within the past five (5) years.

b. The Offeror shall provide a resume(s) that demonstrates experience scaling

Agile practices across multiple teams while maintaining alignment with strategic goals.

2. Certifications:

a. The Offeror's Key Personnel must possess a current, recognized advanced

Agile-specific credential (e.g., Project Management Institute Agile Certified

Practitioner (PMI-ACP), Certified Scrum Professional (CSP), Scaled Agile

Framework (SAFe) Agilist, SAFe Practice Consultant (SPC), or equivalent

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023 advanced certification). The Offeror shall submit a copy of the certificates for these credentials (not part of the 3 page resume).

3. Technical Competency:

a. The Offeror's Key Personnel resume must demonstrate hands-on experience utilizing enterprise Agile management tools (Jira at a minimum) to track capacity, manage backlog workflows, forecast delivery velocity, and generate flow metrics and dashboards.

b. The Offeror's Key Personnel's resume must demonstrate the specific metrics the proposed APM has historically used and how they used those metrics to pivot a failing project or improve team performance.

4. Security Clearance:

a. The Offeror's Key Personnel must provide supporting documentation that the

Key Personnel are eligible for up to a Top Secret/SCI security clearance.

iii. Subfactor 1.c – Cybersecurity Compliance Gate (SPRS 110 Score) (3 page max.)

Prerequisite for Government Controlled Unclassified Information (CUI) Data Release:

The Offeror shall submit a three-page Compliance Statement before the Offeror can receive Government data to participate in Phase II. The Government will verify the

Offeror’s cybersecurity compliance rating in Supplier Performance Risk System (SPRS).

1. 110-Score Requirement: The Offeror shall provide documentation/CAGE code confirming an active, self-certified National Institute of Standards and Technology

Special Publication (NIST SP) 800-171 Revision 2 assessment score of 110

(indicating full implementation of all 110 security controls) active and posted in the DoD SPRS as of the Phase I submission date for the Offeror and joint venture members, affiliates, team members, and subcontractors.

2. Flow-Down Mandate: The Offeror shall provide substantiating documentation that their 110-Score requirement applies to the Prime Offeror, and all proposed subcontractors, teaming partners, or affiliates who will have access to

Government-provided data or participate in contract performance.

3. Notice of Non-Compliance: Failure to possess a verified score of 110 in SPRS on the date of submission will result in an immediate "Non-Compliant" determination., and the Offeror will be ineligible to receive the Jira data needed to participate in the Oral Presentation. Proposals deemed non-compliant at this stage will be rejected in their entirety, as further evaluation is not possible.

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

VOLUME 2 - FACTOR 2 – OCI MITIGATION PLAN - Instructions

i. Factor 2 – Organizational Conflict of Interest (OCI) Mitigation Plan (10

Pages Max)

All individual offerors, members in teaming arrangements, and partners in joint ventures shall submit a comprehensive, written OCI Mitigation Plan that completely identifies any potential or actual OCIs associated with the performance of this requirement and proposes mitigation strategies that avoid, neutralize, or mitigate those conflicts in accordance with FAR Subpart 9.5.

The plan must specifically address and provide comprehensive mitigation strategies for the following three (3) OCI categories as well as the information in Section 8 of the

APS_Combined Synopsis Solicitation:

1. Unequal Access to Information: Occurs when a contractor has access to non-public, sensitive, or proprietary information as part of its performance of a

Government contract, and that information provides the contractor with an unfair competitive advantage in a later competition.

2. Biased Ground Rules: Occurs when a contractor, in the course of performance, drafts or influences specifications, Statements of Objectives (SOOs), Statements of Work (SOWs), Program Objective Memorandum (POM) or acquisition plans for a future procurement, thereby biasing the competition in favor of its own capabilities, tools, or those of an affiliate.

3. Impaired Objectivity: Occurs when a contractor’s work under one Government contract requires it to evaluate its own products, services, or performance (or those of a competitor, teammate, or affiliate) on another Government contract, thereby impairing its ability to render impartial, objective advice.

VOLUME 4 - ADMINISTRATION – Instruction

i. Section 1: Cover Letter

The Offeror shall submit a formal corporate Cover Letter signed by an authorized corporate official, including at a minimum the following information (3 Pages Max):

a. Corporate Identification: Company Name, CAGE Code, UEI, and primary/alternate POCs.

b. Facility Security Clearance (FCL) Verification: Formal statement confirming that the Prime Contractor possesses an active Top Secret FCL issued by Defense

Security Cooperation Agency (DCSA), with personnel eligible up to TS/SCI.

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

c. The solicitation number;

d. The time specified in the solicitation for receipt of offers;

e. The name, address, and telephone number of the Offeror;

f. A technical description of the items/services being offered in sufficient detail to evaluate compliance with the requirements in the solicitation. This may include product literature, or other documents, if necessary;

g. Terms of any express warranty; and

h. "Remit to" address, if different than mailing address.

ii. Section 2: NAICS Size Standard Certification

a. NAICS Certification: Formal certification confirming business size status under the assigned NAICS code (541990).

b. SAM.gov Representations & Certifications: Confirmation that the Offeror's

SAM.gov profile is current, active, and fully compliant as of the proposal due date.

c. Offers that fail to furnish required representations or information, or reject the terms and conditions of the solicitation may be excluded from consideration

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

Phase II – Proposals - must include:

• Volume 1 – Factor 1 – Technical, Subfactor 1.d – Part 1, Technical Presentation and Agile Scenarios with Subfactor 1.a – Agile Implementation Plan and SOO –

Oral Presentation Slides - Oral Presentation Slides; Part 2, Government provided

Scenario Injects – Oral Presentation (No slides); and Visit Authorization Request

(VAR) via the Defense Information System for Security (DISS) to the Government

Security Point of Contact (POC) annotated in Phase II Advisory Notification /

Invitation Letter

• Volume 1 – Factor 1 – Technical, Subfactor 1.d – In-Person Attendees List

VOLUME 1 - Phase II - Technical Presentation and Agile Scenarios (Oral

Presentation) – Instructions

Only Offerors who successfully pass all Phase I gates (including the NIST SP 800-171

Rev 2 Cybersecurity Compliance Gate) will be recommended to participate in Phase II.

• Format & Scheduling: All oral presentations will be performed in person at a

Government facility located in the Research Park area of Orlando, FL. The PCO will determine the order in which the Offerors will present their oral presentations.

The PCO will notify Offerors of the scheduled date and precise location of their presentation via email no less than seven (7) days before the required presentation date. The Government reserves the right to reschedule any presentation at the discretion of the PCO.

• Presentation Slides Submission: The PCO will email each Offeror a Phase II

Advisory Notification and Invitation upon completion of the Government’s evaluation of Phase I, but no less than seven (7) days before the required presentation date. This notification will provide the date, location and time of the

Offeror’s designated Oral Presentation Day (See Factor 1, Subfactor 1.d for additional information). The Offerors in return shall email their final PowerPoint presentations (Part 1 and Part 2) to the PCO no later than 48 hours after receipt of their Phase II Advisory Notification and Invitation. No modifications to the slides will be permitted after this submission.

• Costs: The Government is not responsible for, nor will the Government pay any portion of the costs associated with Offerors’ personnel attendance for the oral presentations.

• Time Limit: The total session shall not exceed sixty (60) minutes not to include

Government introduction timeline requirements. The Government will keep the official time and will maintain a hard stop; any content presented or actions taken

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023 after the 60-minute mark will not be evaluated. Up to ten (10) additional minutes may be allocated for the Offeror to prepare their responses to the Government’s inject scenarios. This 10-minute allotment is NOT part of the Offeror’s 60 minutes

Oral Presentation time.

• Facility Access & Security: There is no security clearance requirement for participation in Phase II or for access to the designated Research Park facility, however all participants must be US citizens. To facilitate unclassified building access, the Offeror shall submit a formal Visit Authorization Request (VAR) via the Defense Information System for Security (DISS) to the Government Security

Point of Contact (POC) (SMO Code and POC to be provided in the Phase II notification letter) by the Phase II submission due date. All proposed personnel must present a valid, Government-issued photo identification upon arrival.

• Attendees: The Offeror is limited to a maximum of five (5) participants.

Identification of all attendees, along with the company name, position, and confirmed DISS VAR status shall be identified to the Government points of contact (POCs) via email as part of Phase II submission. The proposed APM(s), identified in Phase I, should be the primary lead(s) for the session.

• Equipment: The Government will provide the computer and large screen display for the Oral Presentation. There is no requirement for the Offeror to bring IT equipment to the presentation.

Recording: Oral presentations will be recorded for Government use during the solicitation evaluation. Offerors are strictly prohibited from recording the session.

THE 60-MINUTE ORAL PRESENTATION AGENDA & SUBFACTOR MAPPING

(Subfactor 1.d)

The oral presentation is broken into 2 distinct parts: Part 1 - Implementation and

Alignment with Subfactor 1.a – Agile Implementation Plan and SOO Oral Presentation

Slides Oral Presentation, Part 2 – Oral Presentation with Government provided

Scenario Injects. The Offeror must strictly adhere to the following steps and address the mapped evaluation criteria:

Part 1: (First 50 Minutes) - Implementation and Alignment with Subfactor 1.a –

Agile Implementation Plan and SOO Oral Presentation Slides

Part 1 Instructions: The Offeror shall provide a 40-page (maximum) PowerPoint presentation and shall present that information during the first 50 minutes of the oral presentation. The Offeror must clearly and comprehensively address the following elements:

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

1. Resource Allocation & Dispersed Support (Subfactor 1.a / 1.d): The Offeror shall detail a strategy for providing appropriate and sufficient capacity to meet the requirements of the Government’s SOO and Offeror’s Phase 1 Agile

Implementation Plan. The offeror shall explicitly address an approach for resourcing geographically dispersed sites to ensure uninterrupted, synchronized mission support.

2. Workforce Management & Backfill Speed (Subfactor 1.d): The Offeror shall demonstrate their plan to recruit and manage a qualified, large, and geographically dispersed workforce, detailing the exact procedural pipeline to backfill vacant positions as expeditiously as possible to prevent degradation of sprint velocity and mission support.

3. Retention & Turnover Mitigation (Subfactor 1.d): The Offeror shall describe its strategies and incentives it will use to retain employees and reduce turnover.

4. Corporate Training Investment Protection (Subfactor 1.d): The Offeror shall detail its approach for providing corporate-funded, domain‑specific training to ensure employees remain highly skilled assets and shall explicitly demonstrate that all such training will be company-funded and not constitute a responsibility or expense of the Government.

5. Operations & Multi-Level Interactions (Subfactor 1.a / 1.d): The Offeror shall describe the concrete approach for conducting daily APS operations. The Offeror shall detail the specific processes, task assignments, and communication flows across Organizational (CPE ST3), Project Managers/Leads (PMs/PLs), Product

Managers/Leads (PdM/PdL), and Team levels that will enable responsive and effective execution.

6. Cross-Functional Governance & Tool Utilization (Subfactor 1.d): The Offeror shall present the company’s "Talent Pool Composition and Cross-Functional

Governance" approach aligned to the Offeror’s business practices. The Offeror shall describe the manner in which it will utilize the Jira environment to actively manage cross-functional resources and track talent capabilities in real time, validating the methodology proposed in the Phase I Submission.

7. Multi-Level Dashboards & Metrics (Subfactor 1.d): The Offeror shall describe its approach for utilizing the Jira environment to organize data, visualize workflow, and clearly communicate status via informative dashboards configured for the CPE, PM/PL, and PdM/PdL levels.

8. Agile Implementation Approaches (Subfactor 1.d): The Offeror shall utilize the Government provided Jira data to present the top three approaches for

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023 improving the effectiveness of the APS services and shall describe how each recommended change would be implemented in Jira.

Part 2: (Final 10 Minutes) Government provided Scenario Injects (Subfactor

1.d): - Oral Presentation.

Part 2 Instructions: At the 50-minute time during the Oral Presentation, the

Government will stop the Oral Presentation timer and present two (2) scenario injects requiring the Offeror to address real‑time triage of multiple operational changes. The Offeror will have 10 minutes to prepare their responses to the 2 injects. After 10 minutes, the timer will start again at which time the Offeror shall describe its capability to maintain continuity of operations and apply agile change‑management practices to ensure uninterrupted contractual performance. For each scenario inject the Offeror shall provide a response that addresses the applicable areas below. The response may address one area, multiple areas, or all areas, as relevant to each inject. The 2 scenario injects will include the areas that the Government will use to evaluate each response:

a. Entering, sizing, and triaging requirements generated by the scenario inject.

b. Reprioritizing the backlog and adjusting sprint or workflow plans.

c. Orchestrating technical and functional resources.

d. Executing effective HR actions, including access management, onboarding/offboarding, and labor resource reassignment.

e. Demonstrating compliance with labor category qualification and hiring requirements.

f. Describing and demonstrating continuity-of-operations measures.

g. Explaining and demonstrating how uninterrupted performance is maintained through communication protocols, risk mitigation, technical remediation, and workflow stabilization.

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

Phase III – Proposals - must include:

• Volume 1 – Factor 1 – Technical, Subfactor 1.e - Proposed Performance Work

Statement (PWS), applicable Contract Data Requirements List (CDRLs), QASP, and Compliance Matrix

• Volume 1 – Factor 1 - Technical, Subfactor 1.f – Transition Plan

• Volume 1 – Factor 1 – Technical, Compliance Matrix (Not Evaluated)

• Volume 3 - Factor 3 – Cost/Price Workbook

• Volume 4 – Administration Volume

a. NAICS Size Standard Re-Certification (The purpose of this document is to revalidate that the Offeror’s Size Standard has not changed from Phase I to

Phase III Submittals.)

b. Amendment Acknowledgments

c. Teaming Agreements (If Applicable)

d. Representations and Certifications to include Data Rights Certifications

Volume 1 – Factor 1 - Subfactor 1.e - Proposed PWS, CDRLs and QASP

A. PWS INSTRUCTIONS

The Offeror shall author and submit a binding, contractor-developed PWS that translates the Government’s requirements into a single, comprehensive, and enforceable contract document. The PWS shall be organized using the Government-provided PWS Template and must incorporate all tasks, plans, approaches, and commitments detailed in the following three source documents:

1. Statement of Objectives: The Offeror shall develop a PWS that converts every performance objective, desired end-state, and operating constraint from all sections of the into measurable, enforceable contractual requirements and deliverables (CDRLs).

2. Phase I Agile Implementation Plan: The Offeror shall develop a PWS that integrates and codifies all tasks, plans, and approaches detailed in the Offeror’s written Phase I submission, transforming the proposed methodology into binding contractual commitments.

3. Phase II Oral Presentation: The Offeror shall develop a PWS that incorporates all tasks, plans, and approaches detailed in the Offeror’s Phase II Oral

Presentation, ensuring that all written and verbal commitments are formalized as unambiguous, enforceable contractual requirements.

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

B. CDRL INSTRUCTIONS

The Offeror shall complete and submit a DD Form 1423, Contract Data Requirements

List (CDRL), for each required data deliverable.

1. Completeness & PWS Traceability: The Offeror shall complete and submit all four (4) required CDRLs, ensuring that each DD Form 1423 is accurately and explicitly mapped to its corresponding PWS reference.

2. Content Alignment: The Offeror shall ensure the content and description of each

CDRL directly and fully align with the requirements and deliverables specified in the corresponding PWS task.

C. QASP INSTRUCTIONS

The Offeror shall submit a comprehensive QASP detailing the objective methods the

Government will use to monitor contractor performance and ensure services are received in accordance with the PWS. The QASP must be structured to directly address the five (5) evaluation gates outlined in FAR 52.212-2 of this solicitation.

1. Objective Standards & Numerical Acceptable Quality Levels (AQLs): The

Offeror shall develop a QASP that includes a detailed Performance Requirements

Summary (PRS) Table. This table must establish specific, measurable, and numerical Acceptable Quality Levels (AQLs) for all core tasks identified in the PWS.

The PRS Table must include, at a minimum, columns for: PWS Task Reference, Performance Standard, AQL (as a numerical threshold), Surveillance Method, and

Remedies/Disincentives.

2. Automated Surveillance Integration via Live Dashboard & Portal: The Offeror shall develop a QASP that establishes a primary surveillance method which will provide continuous Government access to the contractor-provided live dashboard and knowledge management portal.

3. Workforce Availability & Rapid Backfill Surveillance: The Offeror shall provide a QASP that establishes a binding surveillance availability metric across the workforce including dedicated Key Personnel. The plan must define the specific AQL and surveillance method to enforce that all positions are filled with fully qualified, Labor Category (LCAT) - compliant personnel within 20 calendar days of vacancy.

4. Financial Accuracy & FMS SLIN Segregation Auditability: The Offeror shall develop a QASP that establishes a specific AQL of 95% financial accuracy on all monthly Consolidated Cost Reports. The offeror shall detail the auditing method to

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023 ensure there is a 0% tolerance for misallocation or cross-charging between domestic funding lines (CLINs) and Foreign Military Sales (FMS) cases (SLINs).

5. Corrective Action Plan (CAP) Remediation & Enforceable Remedies: The

Offeror shall develop a QASP that defines the formal Corrective Action Plan (CAP) workflow that is triggered whenever performance drops below an established AQL.

The plan must explicitly bind the Contractor to a 5-Business Day deficiency cure period and detail the specific contractual remedies the Government may invoke for non-performance.

VOLUME 1 - Factor 1 - Subfactor 1.f - Transition Plan

The Offeror shall submit a detailed, executable Transition Plan governing the phase-in period after contract award.

1. 90-Day Transition Schedule: The Offeror shall provide a detailed, time-phased schedule illustrating milestones, deliverables, and resource ramp-up across the up to 90-day transition period.

2. Workforce Capture & Clearance Transition: The Offeror shall document their plan from Phase 1 Agile Implementation Plan and Phase II Oral Presentation with their detailed procedures for recruiting, onboarding, and transferring incumbent personnel, including verification that 100% of the workforce possess the required security clearances and facility access approvals prior to Day 90.

3. Knowledge Transfer & Shadowing: The Offeror shall provide a detailed knowledge acquisition process at a minimum provides a schedule for shadowing incumbent personnel, a methodology for ingesting existing technical documentation, and a plan for integrating with Government teams to ensure a seamless transfer of all required knowledge.

4. Live Dashboard, Account, & Facility Access Handover: The Offeror shall provide a clear plan for protocols in conducting the handover of the live dashboard, transferring Government-furnished information (GFI), obtaining

Common Access Cards (CACs), establishing building access, and assuming

24/7/365 coverage of the TSMO SCIF at Redstone Arsenal, AL.

5. Risk Mitigation: The Offeror shall identify a minimum of three credible risks to the transition and propose specific, actionable mitigation strategies to ensure minimal impact to ongoing CPE ST3 mission support.

VOLUME 1 – Factor 1 – Compliance Matrix (Not Evaluated)

The Offeror shall submit a Compliance Matrix in MS Excel (Offeror’s preferred format with Unlimited Pages), that maps to the following:

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

1. The Offeror’s PWS to all sections of the SOO.

2. The Offeror’s Agile Implementation Plan to the Offeror’s PWS.

3. The Offeror’s Oral Presentation to the Offeror’s PWS.

4. The Offeror’s proposed QASP to the Offeror’s PWS.

5. The Offeror’s price volume to the Offeror’s PWS, Agile Implementation Plan, Oral

Presentation, and Transition Plan.

The Government will NOT evaluate the Compliance Matrix as part of the Acceptable /

Unacceptable criteria. The Government will use the matrix to assist in assessing where the Offeror has detailed their proposal to the Government’s requirements.

• VOLUME 3 – Factor 3 – Cost/Price Proposal Instructions Fully Burdened Labor

Rate Schedule (Attachment 10 _ APS Pricing Workbook)

1. The Offeror shall complete the Government-provided Excel APS Pricing

Workbook (Attachment 10), providing fixed hourly rates for all labor categories identified in their approved LCAT Crosswalk.

2. Labor rates must encompass all direct labor, fringe benefits, overhead, general and administrative (G&A) expenses, corporate-funded training costs, and profit.

3. No separate training surcharges or off-site infrastructure fees will be paid by the

Government.

4. Instructions for completing Attachment 10:

i.Offerors shall NOT alter, adjust, or manipulate any formulas contained in the attachment.

ii.Offerors shall NOT alter, adjust, or manipulate any data contained in Tab 1-

Proposal Summary.

iii.Offerors shall ONLY alter, adjust, or manipulate cells shaded “green” in Tabs

2-8, and SHALL fill in ALL cells shaded “green” on Tabs 2-8. (Exception noted in item v. Below.)

iv.The shaded cells in column “A” of Tabs 2-8 are reserved for Offeror identification of LCATs required for the administration of the Agile processes required in support of the Offeror performance proposal and methodology (e.g., Agile PM, SCRUM Masters, etc.)

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023 v.Column “E” in Tabs 2-8 is intended to serve as the Offeror assertion as to whether the position is exempt from the Service Contract Act. If a position

IS exempt Column “E” should be marked “Yes” and the corresponding Cell in Column F should be left blank.

vi.Offerors are advised that Column “CI” of Tabs 2-8 are reserved for any and all contract level employees and positions that will be Direct Charged to the contract but will operate out of Contractor facilities. The location of the

Contractor Facility must be identified by replacing the red font in Cell

“CI10” of Tabs 2-8 with the City and State of the Contractor facility.

vii.Columns CM-CP of Tabs 2-8 are formatted in accordance with Generally

Accepted Accounting Principles (GAAP) to properly calculate a “Total

Burden Rate in Column CQ when Offerors identify their respective burden rates in the “green” shaded cells of Columns CM-CP.

VOLUME 4 – Administration Volume

• NAICS Size Standard Re-Certification (1 Page Maximum)

The Offeror shall provide formal certification confirming business size status under the assigned NAICS code (541990). The purpose of this re-validation is to ensure that the

Offeror’s Size Standard has not changed from Phase I to Phase III Submittals.

• Teaming Agreements (If Applicable)

The Offeror shall provide documentation, if applicable, of Teaming Agreements.

Teaming Agreements shall, at minimum, include the Company Name, CAGE Code, UEI, and confirmation of an active NIST SP 800-171 Revision 2 assessment score of 110 for the Offeror and applicable Teaming Partners.

• Unlimited Data Rights Certification

The Offeror shall include a signed statement in Volume 4 – Administrative Volume, certifying that the Government will receive Unlimited Rights to all technical deliverables, dashboards, portals, database configurations, and business process artifacts generated under the contract.

(1) Period for acceptance of offers. The Offeror agrees to hold the prices in its offer firm for 180 calendar days from the date specified for receipt of offers, unless another time period is specified in an addendum to the solicitation.

https://www.acquisition.gov/far/subpart-4.10(d) Late submissions, modifications, revisions, and withdrawals of offers.

https://www.acquisition.gov/far/subpart-4.10

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

(1) Offerors are responsible for submitting offers, and any modifications, revisions, or withdrawals, so as to reach the Government office designated in the solicitation by the time specified in the solicitation.

(2)(i) Any offer, modification, revision, or withdrawal of an offer received at the

Government office designated in the solicitation after the exact time specified for receipt of offers is "late" and will not be considered unless it is received before award is made, and the Contracting Officer determines that accepting the late offer would not unduly delay the acquisition; and-

(A) If it was transmitted through an electronic commerce method authorized by the solicitation, it was received at the initial point of entry to the Government infrastructure not later than 5:00 p.m. one working day prior to the date specified for receipt of offers; or

(B) There is acceptable evidence to establish that it was received at the

Government installation designated for receipt of offers and was under the

Government’s control prior to the time set for receipt of offers; or

(C) If this solicitation is a request for proposals, it was the only proposal received.

(2)(ii) However, a late modification of an otherwise successful offer, that makes its terms more favorable to the Government, will be considered at any time it is received and may be accepted.

(3) If an emergency or unanticipated event interrupts normal Government processes so that offers cannot be received at the Government office designated for receipt of offers by the exact time specified in the solicitation, and urgent

Government requirements preclude amendment of the solicitation or other notice of an extension of the closing date, the time specified for receipt of offers will be deemed to be extended to the same time of day specified in the solicitation on the first work day on which normal Government processes resume.

(4) Offers may be withdrawn by written notice received at any time before the exact time set for receipt of offers. If the solicitation authorizes facsimile offers, offers may be withdrawn via facsimile received at any time before the exact time set for receipt of offers, subject to the conditions specified in the solicitation concerning facsimile offers. An offer may be withdrawn in person by an offeror or its authorized representative if, before the exact time set for receipt of offers, the identity of the person requesting withdrawal is established and the person signs a receipt for the offer.

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

(e) Contract award. The Government intends to evaluate offers and award a contract without discussions with offerors. Therefore, the offeror’s initial offer should contain the offeror’s best terms from a price and technical standpoint. However, the

Government reserves the right to conduct discussions if later determined by the PCO to be necessary. The Government may reject any or all offers if such action is in the public interest; accept other than the lowest offer; and waive informalities and minor irregularities in offers received.

(f) Availability of requirements documents cited in the solicitation.

(1)(i) The GSA Index of Federal Specifications, Standards and Commercial Item

Descriptions, FPMR Part 101–29, and copies of Federal specifications, standards, and product descriptions can be downloaded from the ASSIST website at https://assist.dla.mil.

(2) Most unclassified Defense specifications and standards may be downloaded from the ASSIST website at https://assist.dla.mil.

(3) Defense documents not available from the ASSIST website may be requested from the Defense Standardization Program Office by—

(i) Using the ASSIST feedback module ( https://assist.dla.mil/feedback); or

(ii) Contacting the Defense Standardization Program Office by telephone at 571–767–6688 or email at assisthelp@dla.mil.

(4) Nongovernment (voluntary) standards must be obtained from the organization responsible for their preparation, publication, or maintenance.

(g) Unique entity identifier. (Applies to all offers that exceed the micro-purchase threshold, and offers at or below the micro-purchase threshold if the solicitation requires the Contractor to be registered in the System for Award Management (SAM).)

The Offeror shall enter, in the block with its name and address on the cover page

(limited to 2-pages, which will not be included in any respective page count) of its offer, the annotation "Unique Entity Identifier" followed by the unique entity identifier that identifies the Offeror's name and address. The Offeror also shall enter its Electronic

Funds Transfer (EFT) indicator, if applicable. The EFT indicator is a four-character suffix to the unique entity identifier. The suffix is assigned at the discretion of the Offeror to establish additional SAM records for identifying alternative EFT accounts (see

FAR subpart 32.11) for the same entity. If the Offeror does not have a unique entity identifier, it should contact the entity designated at www.sam.gov for unique entity identifier establishment directly to obtain one. The Offeror should indicate that it is an offeror for a Government contract when contacting the entity designated at www.sam.gov for establishing the unique entity identifier.

https://assist.dla.mil/ https://assist.dla.mil/ https://assist.dla.mil/feedback mailto:assisthelp@dla.mil https://www.acquisition.gov/far/subpart-32.11#FAR_Subpart_32_11 http://www.sam.gov/ http://www.sam.gov/

Attachment 02: FAR 52.212-1 Instructions to Offerors for Agile Professional Services Solicitation W900KK-26-R-A023

(h) [Reserved]

(i) Debriefing. If a post-award debriefing is given to requesting offerors, the

Government shall disclose the following information, if applicable:

(1) The agency’s evaluation of the significant Acceptable or Unacceptable factors in the debriefed offeror’s offer.

(2) The overall evaluated cost or price and technical rating of the successful and the debriefed offeror and past performance information on the debriefed offeror.

(3) The overall ranking of all offerors, when any ranking was developed by the agency during source selection.

(4) A summary of the rationale for award;

(6) Reasonable responses to relevant questions posed by the debriefed offeror as to whether source-selection procedures set forth in the solicitation, applicable regulations, and other applicable authorities were followed by the agency.

(End of provision)