Advancing Assured Access: Integrated Digital Capabilities for the 2 SLS to Accelerate Mission Tempo and Readiness

**Changes to Q&A:** Q2 received a new answer clarifying scheduling requirements: functional parity with Puckboard's full capabilities is expected, including shift scheduling, leave, meetings, appointments, and events. Q6 remains unanswered.

**Summary of Q&A Changes:** Added new Q3 clarifying CSO feasibility documentation eligibility: feasibility documentation CANNOT include extended work from previous/ongoing SBIR/STTR awards. Renumbered subsequent questions accordingly. All other answers remain substantively identical.

**Q&A Changes Summary:** Added 2 new duplicate questions (Q1 and Q2) clarifying the relationship between the topic's listed systems (personnel, certification trackers, operational tasking, mission integration repositories) and the named enterprise systems (Teams, SharePoint, Confluence, Jira)—addressing whether these represent one or two distinct integration scopes. Answers remain pending for both.

**Q&A Changes Summary:** Added 2 new questions: Q1 clarifies preferred hosting environment (Nebula IL-4/IL-5); Q2 confirms all work at unclass/CUI level with no classified system access required during Phase II. Added Q3 requesting clarification on scheduling capability scope (2 SLS vs. full personnel scheduling parity). Remaining questions (now Q4-Q7) are duplicates of previous answers with no substantive changes.

Four previously unanswered Q&As now have responses clarifying: (1) Phase I deliverable expectations (documented architecture with component validation acceptable); (2) Phase II enterprise system integrations (MS Teams, SharePoint, Confluence, Jira with government-furnished access/APIs/data); (3) scheduling system replacement scope (confirmed Puckboard replacement); (4) classification levels (CUI/UNCLASS prototype, unclassified environments with potential higher-classification path if needed).

Q3 received an answer clarifying that the government seeks to replace their existing scheduling system (Puckboard), not provide decision support within current processes.

These Q&As clarify critical technical scope boundaries: applicants should understand that Phase I may proceed with architecture documentation rather than working demos, Phase II integration scope depends on government system access availability, and proposals should address whether solutions augment or replace existing scheduling systems—with classification level expectations to be determined during award negotiations.

New opportunity: Advancing Assured Access: Integrated Digital Capabilities for the 2 SLS to Accelerate Mission Tempo and Readiness