SOURCES SOUGHT NOTICE TIMES.pdf

SOURCES SOUGHT NOTICE

TOTAL INTEGRATION MOBILIZATION EXECUTION SYSTEM (TIMES)

Reference Number: FA701425RPKHB09

PROCURING & ADMINISTRATIVE CONTRACTING OFFICE

Air Force District of Washington (AFDW) Contracting Directorate (PK) Headquarters Air Force (HAF) - Enterprise Support Division (PKH) DoDAAC: FA7014

INTRODUCTION

This is a Sources Sought Notice (SSN) which is being released to industry for information gathering and planning purposes only pursuant to FAR Part 10 Market Research.

This SSN is not a solicitation, nor shall this SSN constitute a Request for Proposal (RFP), Invitation for Bid (IFB), or Request for Quote (RFQ). The Government shall not award any contract solely on the basis of this SSN nor shall the Government reimburse any Contractor for any associated costs they incur to submit a Capability Package to the Government in response to this SSN. This market research notice is being deployed to bring forth qualified, capable sources and in no way shall restrict the Government’s final acquisition strategy, planning, or requirements refinement.

NAICS CODE

The North American Industrial Classification System (NAICS) Code for this SSN is 541511- custom computer programming services. and the Small Business Size is $30M.

*Note: A small business firm competing as a Prime Contractor would need to perform at least 50% of the total requirement form within its own company (See FAR 52.219-14, Limitations on Subcontracting).

BACKGROUND & DESCRIPTION OF GOVERNMENT’S NEEDS/REQUIREMENTS

TIMES will provide the Air Force with a single, integrated system of software suites linking Airmen of the Air Reserve Component to deployment and/or mobilization authorities that supports a rapid and accurate information flow from the first identification of a requirement through the processing and delivering of orders to start pay and benefits in an auditable manner.

The Deputy Chief of Staff (DCS) of the Air Force (AF) for Operations (AF/A3), pursuant to Title 10 United States Code (USC) §§ 8031-8038, and as documented by paragraph 4.3.3 of the Air Force Mission Directive (AFMD) 1-54, Headquarters Air Force, assists the Secretary of the Air Force (SECAF), other Secretariat offices, and the Chief of Staff of the Air Force (CSAF) in carrying out air, space, and cyberspace operations by establishing and overseeing policy to organize, train, and equip those forces for the Department of the Air Force (DAF). Specifically, the A3 assists the CSAF in providing and allocating operationally ready air, space, and cyberspace forces and capabilities in response to the need of the combatant commanders via the Global Force management (GFM) process.

According to Title 10 USC §§ 8013-8016 and AFMD 1-24, Paragraph 4.1, the Assistant Secretary of the Air Force for Manpower and Reserve Affairs (SAF/MR) has the overall responsibility for: manpower, military, and civilian personnel policy; specifically, providing guidance, direction, and oversight of the Air Force’s utilization of Air Force Reserve Component (ARC) members, to include mobilization and demobilization. Therefore SAF/MR has mandated that the A3 will provide a suite of applications that centralizes

Reference Number: FA701425RPKHB09 relevant data and automates the process for mobilization and deployment in a system known as the Total Integration Mobilization Execution System (TIMES).

The Contractor shall ensure contractor personnel take action to integrate into the AF

War Planning and Policy Division (AF/A3OD) office, creating a seamless Government- Contractor team. The Contractor shall manage contractor personnel. The Contractor will closely interface with Air Force staff and other contractors, as required by the Government, and follow the direction of the Contracting Officer (CO), A3O staff, COR, Alternate COR, and designated USAF Project Manager(s)/Lead(s). Collaboration includes day- to-day activities, consulting, planning, prioritization, development, configuration, implementation, problem solving, knowledge transfer, and creating and sharing documents. The Contractor shall also ensure lifecycle software engineering (verification, coding, testing, fielding, support, etc.) and cybersecurity/information assurance.

QUESTIONS FOR INDUSTRY

1. For software application sustainment (not new development), what type of metrics are you using to demonstrate customer satisfaction? Specifically, please address two areas:

a. User Interface/User Experience (UI/UX): Does your company utilize specific front-end development frameworks? Do you have UI/UX specialists (as opposed to full-stack developers), and how do you approach continuous improvement in GUI design?

b. Customer Feedback Integration: How does your company incorporate customer feedback into the development cycle? Please outline the feedback mechanisms available for customers, the process for adding feedback to the backlog, reviewing the backlog, and how these items are prioritized and actioned.

c. Is your company capable of providing quantifiable or verifiable data/information?

2. Does your company support telework? How does your company ensure successful work completion and communications?

3. Does your company currently employ individuals with a SECRET-level security clearance available in the Defense Information for Security System (DISS), or have employees eligible to obtain one? If eligibility applies, please provide a general timeline for clearance acquisition following contract award (e.g., 1 week, 2 months). Additionally, please confirm whether at least one team member, preferably an on-site project manager, has or is able to obtain a TS/SCI clearance, which may be required for specific tasks involving secure environments and classified information. (Please do not include any personally identifiable information)

4. What is the size of your company (to include socio-economic status), given the designated

NAICS?

5. What demonstrated experience does your company have with Development Security

Operations (DevSecOps) policies and procedures for handling DoD software and/or IT systems? Please detail your experience with DevSecOps tools and past use of these as part of a DevSecOps pipeline, as well as your familiarity with containerization and Kubernetes orchestration.

6. Does your company have historical experience in Agile Software Development for DoD applications, software systems, Air Force Risk Management Framework (RMF), Security Technical Implementation Guide (STIG), and Authority to Operate (ATO) processes? Please describe which specific Agile development methodologies you have experience with, your current Agile methodology, tools for managing the process, sprint cycle lengths, and how you handle long-term planning and backlog management.

7. Could you elaborate on your company’s expertise in Air Force Active Duty, National Guard, and/or Reserves mobilization programs and processes? Additionally, what specific subject matter expertise does your company hold in Air Reserve Component (ARC) utilization policies and processes?

a. Can you provide verifiable or quantifiable data and/or information?

8. Does your company anticipate any Subcontracting opportunities in the performance of this requirement?

a. Please provide your previous subcontractor’s performance history regarding the nature of this contract, or your company’s performance requirements for any potential subcontractor hires.

9. Does your company hold any CMMI certifications, and if so, which type (e.g., Services, Development) and maturity level (e.g., Level 2 or 3)? Additionally, are there other relevant industry certifications your company possesses or can obtain that would enhance our ability to effectively manage this DoD software system?

10. What recommendations would you have on the GSA vehicle (GWAC or MAC) that would best meet this requirement?

*NOTE: Please provide answers to the listed questions and you may submit a detailed capability statement of your corporate/industry experience.

MANDATORY FORMATTING, & DEADLINE

Interested Respondents should submit Capability Packages to the Government which meet all formatting, and the submittal deadline as instructed below:

a. Capability Packages and any allowable attachments shall be delivered to the Government electronically via one (1) email before the SSN deadline.

b. Capability Packages and any allowable attachments must be submitted in Microsoft

Office format (Word, Excel or PowerPoint) or Adobe pdf format (which is preferred by the Government).

c. Capability Packages and any allowable attachments submitted to the Government via email must NOT exceed 5MB.

*Note: If file size is 5MB or larger, the Government will NOT receive the Respondent’s email and attached package file due to internal system limits and restrictions.

d. Capability Packages and any allowable attachments submitted to the Government must contain UNCLASSIFIED data/information/content only.

*Note: Capability Packages and any allowable attachments submitted to the Government in response to this Sources Sought Notice SHALL NOT and MUST NOT contain any Controlled Unclassified Information (CUI), Classified, Secret, or Top Secret data/information/contents.

e. Capability Packages shall NOT exceed 5 total pages, each single side counting as one page, 8.5 inch x 11 inch, with one-inch margins, and font size no smaller than 10 point Times New Roman. Item #a - Item #g under the CAPABILITY PACKAGE CONTENTS section below must be addressed by the Respondent within the allowable 5 total pages.

Documentation proof submitted by the Respondent to verify the six (6) critical requirements identified at Item #h under the CAPABILITY PACKAGE CONTENTS section below will not count against the 5 total page limit however such proof documentation must be submitted within one (1) email to the Government and file size must NOT exceed the 5MB email delivery restriction. f. Capability Packages and any allowable attachments must not be submitted as a Zip File via email because the Government email system does not allow transmittal of Zip files.

f. All Capability Packages and any allowable attachments must be received at the identified

Government office no later than 5:00 PM (Eastern Standard Time) on Monday, 6 January 2025.

g. Capability Packages and any allowable attachments shall be sent via email to the AFDW/PKH Contracting Officer, Mr. Mark R. Luckritz, at mark.luckritz@us.af.mil and AFDW/PKH Contracting Specialist, Dr. Damian R. Bell, at damian.bell.1.ctr@us.af.mil

CAPABILITY PACKAGE CONTENTS

Respondents must fully address the Government’s questions and/or provide documentation to address the mandatory data responses below within Capability Packages submitted in response to this Sources Sought Notice.

a. Contractor’s company name, company address, company point of contact, POC e-mail address, and POC telephone number.

b. Contractor’s Cognizant DCMA Office Code and Info, if applicable.

mailto:mark.luckritz@us.af.mil

c. Contractor’s Federal Cage Code and Unique Entity ID (SAM.gov).

*Note: A company must be registered in the System for Award Management (SAM) to be considered responsible for a federal contract award. To register your company, go to https://www.sam.gov.

d. Contractor’s business size (large or small) and applicable socioeconomic categories (VOSB, 8a, HUBzone, SDB, WOSB, etc.) for the established SSN NAICS Code and/or for NAICS Codes of the Contractor’s similar types of work.

e. Identification of any Federal Supply Schedules (FSS), Multiple Award Contracts (MACs), Government-wide Acquisition Contracts (GWACs), and/or Blanket Purchase Agreements (BPAs) that the Contractor currently holds (provide the respective contract numbers, identify the source of the procurement vehicle, and add any other relevant information).

f. Provide up to three (3) examples/references/samples of recent and relevant performance

(recent, meaning within the last 3 years. For each example/reference/sample, provide the Federal Contract Numbers, Commercial Company-to-Company Purchase Order Numbers, Dates/PoPs, Total Dollars, Description of Work/Requirements, Project POC Name, Project POC Email Address, and Project POC Phone Number.

g. Describe your company’s history, capabilities, experience, strengths, and weaknesses in providing Services which are similar to and/or consistent with the Government’s requirements detailed above.

ORGANIZATIONAL CONFLICT OF INTEREST

The Government would also like to remind companies of their responsibility to avoid and/or mitigate any potential Organizational Conflict of Interest (OCI). Guidance is found in Federal Acquisition Regulation (FAR) Part 9.5. If a company has a potential OCI situation, they must submit and have an approved mitigation plan prior to the Government’s consideration of any proposal for award. Since the approval process can be lengthy and approval of any plan is not assured, it is highly recommended that potential OCI identification and resolution processes begin during the planning phase if possible. An OCI could result in the canceling of a contract or determining an Offeror to be ineligible for award. Potential OCI issues, and mitigation plans if developed, shall be included as an attachment to Capability Package. An OCI attachment shall NOT be considered in the Capability Package total page count.

https://www.sam.gov/