Predictive Movement for Object Oriented Tracking

**Key Changes to Q&A:** **New Answers Added:** - **Q1**: Clarifies tiered confidence thresholds required—predictive alerts must have visibly lower confidence than confirmed detections in user interface. - **Q3**: Defines two forecast horizons: Short-term (minutes-hours for tactical use) and medium-term (12/24/48 hours for operational planning like port destination prediction). - **Q5**: Confirms fully synthetic data acceptable for Phase I if it includes realistic sensor noise, dropouts, and clutter. - **Q7**: Confirms METOC data (sea state, wind, currents) integration is in-scope and encouraged for false positive reduction. **Previously Unanswered Questions Still Pending:** - Q10 & Q11 remain incomplete—no government response on vessel prioritization logic, decision-making processes, or Phase II performance baselines vs. current manual operations. **Summary:** Four new technical clarifications on confidence thresholds, forecast horizons, synthetic data acceptability, and environmental data inclusion. Two multi-part questions (Q10, Q11) remain partially or fully unanswered.

# Q&A Update Summary **New Questions Added (Q1-Q6):** Six new questions addressing operational confidence thresholds, government baseline data availability, prediction warning-time expectations, Navy-specific proposal formatting, response time measurement baselines, and dual-submission eligibility clarification. **Key Clarifications:** - Confirmed small businesses can submit both Phase I and Direct-to-Phase II proposals in same cycle - Navy submission instructions link provided for formatting/page limits - No quantified baseline specified for "improved response time" or prediction horizon requirements - Government will not provide representative/historical track data; synthetic data acceptable for Phase I **Unchanged:** Questions 7-11 (previously Q1-Q5) retained without answer modifications, maintaining prior guidance on environmental data fusion, data modalities, CMMC/FCL requirements, vessel tracking prioritization, and performance baselines.

**Q&A Changes Summary:** **New Question Added:** Q1 addresses environmental data fusion—whether incorporating weather, sea state, and seasonal factors into Pattern of Life algorithms to reduce false positives is within scope and valued in evaluation metrics. **Questions Renumbered:** Previous Q2-Q4 are now Q2-Q5 (no content changes to answers). **Key Clarifications Retained:** Answers confirm Phase I scope limited to structured track data (no raw sensor processing), no government-furnished datasets, CMMC Level 2 (Self) sufficient at award, and FCL not required until Phase II selection.

**Q&A Changes Summary:** **New Answer Added to Q1:** Navy clarified Phase I scope focuses on ingestion of **structured track state data only** (time, coordinates, course, speed, classification)—raw/unstructured data processing is out of scope. No government datasets provided; performers should use publicly available unclassified maritime datasets and open-source simulation frameworks to model non-cooperative behaviors (transponder gaps, spoofing, evasive maneuvers). **Q3 & Q4 Remain Unanswered:** No new responses provided to Q3 (tracking methodology, prioritization, data access, operational decision-making) or Q4 (government sample datasets, performance baselines for Phase II).

**Q&A Changes Summary:** Q2 received answers clarifying compliance requirements: CMMC Level 2 (Self) is required by Phase I award (C3PAO certification not required), and current FCL is not required at Phase I proposal/award stage. Navy will initiate DCSA sponsorship for selected Phase II performers lacking active FCL. Q1, Q3, and Q4 remain unanswered.

**Q&A Changes Summary:** New Q1 added: Asks for specific data modalities the system should ingest (AIS, SAR, EO/IR, acoustic) and whether Navy will provide standardized data dictionary/API parameters, plus request for government-furnished simulated datasets or recommended unclassified proxy datasets for Phase I training. Previous questions reordered: Original Q1 (CMMC/FCL compliance) moved to Q2; original Q2 (vessel tracking details) moved to Q3; original Q3 (datasets/baselines) moved to Q4.

**Q&A Changes Summary:** Added new Q1 with 2 questions on security requirements: CMMC Level 2 self-assessment via NIST SP 800-171 sufficiency for Phase I award (C3PAO certification not required), and FCL timing (not required at proposal/award; Government-initiated DCSA sponsorship at Phase II selection). Original technical questions renumbered from Q1→Q2 and Q2→Q3 with no content changes.

Added 7 new questions to Q1 covering: vessel tracking scope (specific vs. anomalous behavior), Pattern of Life development approach, target prioritization methodology, primary sensing modality, government imagery repositories (GEGD/iSPY), Phase I data availability, multi-source data access (space/airborne/AIS/RF/commercial), and Navy response decision-making processes. Original Q1-Q2 retained as new Q2.

This Q&A clarifies that applicants should plan Phase I work around Navy-provided datasets and simulation environments (rather than developing their own), and should expect Phase II success to be measured against established performance baselines from current manual operations—requiring proposals to address how their AI models will demonstrably exceed these quantitative thresholds.

Status changed from Pre-Release to Open

New opportunity: Predictive Movement for Object Oriented Tracking