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

Status changed from Open to Closed after topic disappearance

# Q&A Changes Summary **New Answer Added:** - **Q2** now answered: Clarifies that spaceport operational readiness evaluation is above 2 SLS level (handled by SLD30). For 2 SLS specifically, focus is on launch site readiness tracked through testing with pass/fail criteria for launch authorization. **Updated Answers:** - **Q5** significantly clarified: Reframes data scope by topic area. LSP Chatbot and Mission Integration tool use qualitative data (schedules, reports, documentation). Scheduling tool uses personnel data and activity schedules. Explicitly states LMS/training/travel data categories are "not really the types of data" they'll handle. - **Q6** expanded: Confirms offerors can use proof-of-concept evidence from other federal deployments mapped to 2 SLS requirements. Clarifies launch-vehicle-specific data is not required—similar qualitative data types are acceptable for Phase II validation. **Key Takeaway:** Guidance now more explicitly separates requirements by capability area and accepts non-launch-vehicle-specific validation evidence for the intelligent-search/chatbot component.

# Summary of Q&A Changes **New Answer Added:** - **Q4** now answered: End users are internal to 2 SLS, with 2 SLS as Phase III sponsor candidate. **All other Q&As remain unchanged** from the previous version. No new questions were added, and all previously answered questions (Q1, Q3, Q7-Q12) retain identical answers. Questions Q2, Q5, and Q6 remain unanswered.

# Summary of Q&A Changes **Minimal changes detected.** Q3 now includes a brief answer ("This question has been answered in earlier posts") instead of being unanswered. Q13's answer appears truncated in the updated version (ends with "multiple sour...") versus the previous version, suggesting either formatting loss or no substantive update. No new questions were added, and answers to Q1, Q2, Q4-Q12 remain substantively identical.

**Key Changes to Q&A:** - **New Q1 added:** Asks if government values staffing forecasting capability that predicts required staffing levels from launch cadence and identifies coverage gaps before schedules are built. - **Questions renumbered:** Previous Q2-Q13 shifted to Q2-Q13 (content largely preserved with minor truncation at Q13). - **No new answers provided:** All government responses remain unchanged from previous version; the update primarily adds one new forward-looking question about staffing forecasting value.

# Q&A Changes Summary **New Questions Added (5):** - Q1: Operational readiness evaluation metrics and computation methods - Q3: End users, stakeholders, and Phase III sponsorship candidates - Q4: Data scope, granularity, and availability of representative test data/use cases - Q5: Validation evidence from other federal deployments and domain-specific testing timing for intelligent-search capability **Renumbered:** Original Q1-Q13 renumbered to Q6-Q18 (administrative consolidation) **Key clarifications in new Q&A:** - Q5 addresses Direct-to-Phase II feasibility: offerors may use validated components from existing federal deployments with clear mapping to 2 SLS use case; domain-specific validation acceptable during Phase II using Government-furnished data

# Q&A Changes Summary **Added 2 new questions** on administrative requirements: Q1 addresses FWA training timing (must complete before submission), and Q2 clarifies CCR (Company Commercialization Report) submission—only required for companies with prior SBIR/STTR awards; new companies answer "NO" to mark Volume 4 complete. **Renumbered remaining questions** (original Q1-Q11 became Q3-Q13) to accommodate new administrative guidance. All technical content remained substantively unchanged.

# Q&A Changes Summary **New Answer Added:** - Q9 now has Answer A9: Clarifies that usable outputs should include plain English summaries of questions asked, plus standard reports, briefing templates, and other formatted outputs would be highly valuable. **Note:** All other Q&As (Q1-Q8, Q10-Q11) remain unchanged from previous version.

# Q&A Changes Summary **New Questions Added:** - Q1: Clarified that Government seeks to **replace Puckboard entirely**, not augment it - Q2: Detailed current pain points—specifically that shift creation is manual/tedious (3-6 shifts daily for 30 days = multi-day effort), distinct from information flow issues **Questions Reordered/Renumbered:** Previous Q2-Q11 shifted to Q3-Q11 with no substantive answer changes (same content on Puckboard baseline, plain English preference, info-management gaps, multi-unit pain points, launch cadence drivers, flexibility on demonstrating all three capability areas, and two distinct integration problems). **Key Clarification Reinforced:** Q3 (previously Q1) reiterates write-back to Teams/Outlook is **preferred** (not mandatory) and certification/currency records **must** factor into scheduling eligibility.

# Q&A Changes Summary **New answer added to Q3:** Government clarified the info-management gap—they lack any automation tool currently and must manually aggregate data from multiple sources and hundreds of technical manuals. They're not changing data sources, only how information is accessed. **Key clarification:** Q10 now explicitly confirms that personnel scheduling capability (with leave, meetings, appointments, events support) is the focus, with shift scheduling speed/ease as the primary pain point to solve versus Puckboard.

# Q&A Changes Summary **New Answer Added:** - **Q2** now has an answer clarifying that there is no specific framing or language preference for proposals. **Note:** All other questions and answers appear identical between versions. Q3, Q7, and the conclusion of Q14 remain unanswered in both versions.

# Q&A Changes Summary **New answers provided:** - **Q5**: No specific failure triggered topic; motivation is increased launch cadence (2-3 launches/week vs. 1/month previously) - **Q6**: Scheduling workflow unchanged since Velocity event (May) - **Q8**: Offerors need demonstrate capability in only ONE of three areas (intelligent scheduling, centralized info management, intelligent search); can propose single-area or multi-area solutions **Key clarifications:** Topic allows modular approaches; Phase I feasibility cannot extend prior SBIR/STTR work; solutions must achieve full Puckboard parity with improved speed.

Added 8 new questions (Q1-Q8) seeking clarification on: functional parity baseline documentation, scheduling tool integration scope (read vs. write access), certification eligibility logic, proposal language preferences, specific scheduling gaps vs. past efforts, applicability beyond 2 SLS, workflow changes since prior submission, and output format expectations. All previous Q&As (now Q9-Q18) retained without answer changes.

**Q&A Changes Summary:** Q6 received an updated answer with additional detail. The response now explicitly lists examples of required scheduling functions (leave, meetings, appointments, squadron events, holidays) beyond shift scheduling, reinforcing that full personnel scheduling capability parity with Puckboard is expected. No new questions were added. All other answers remain unchanged.

Status changed from Pre-Release to Open

**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).