OTIS
FleetHacker2026 / A Task Force Hopper Hackathon Event
Judge briefing · Working draft
OTIS watchstanding sea otter emblem

OTIS

Operational Tasking Integration System

Keeping the Watch

I have the watch.
You have the mission.

Know what’s due next.
Find the order behind it.

On your
watch

A crypto changeover in one message. A report deadline in another. You read, cross-check, and copy the times into a schedule—then new traffic arrives. You’re responsible for getting the next action right.

With
OTIS

OTIS turns supported naval messages into searchable tasking and one consolidated schedule, helping you find what matters to your command and trace it back to the source.

Watch demo
From incoming order to next actionSYNTHETIC ILLUSTRATION
Message traffic24-hour UTC view
0006121824Z
Extract → Organize → Review
Next action / verify against the order
0400Z · Crypto changeover
14 tested OPTASK typesZulu or local timeLocal search · Original sources
Watch the demo

See OTIS in action.

The team’s recorded demonstration.

OTIS demo recordingOpen video ↗
What OTIS does for the Sailor

Take over the watch.
Get to the tasking.

Catch up on traffic since turnover. Focus on the ships you’re watching. Check the next event, open the order behind it, and prepare an acknowledgement—all in the same watch desk.

  1. Bring the tasking into view.

    OTIS monitors a configured inbox and extracts activities, frequency plans, crypto changeovers, reporting requirements, locations, and contacts from supported OPTASK layouts.

  2. Catch up since the last watch.

    Review published messages issued since a selected UTC watch boundary. Filter by ship, see sent and received times separately, and open each message’s processing history.

  3. Focus on the ships you’re watching.

    Select ships and compare their day schedules side by side, or browse a week or month. See timed activities and supported recurring changeovers in Zulu or your selected time zone.

  4. Search beyond the exact wording.

    One search combines keywords and meaning. Narrow message results by type, sender, and issue date, then open the message you need.

  5. Go back to what the message says.

    Open a schedule item’s source message. Switch between labeled USMTF fields, the original text, and the recorded intake and processing history.

  6. See the locations on a map.

    When a message contains usable coordinates, view its points and supported shapes on a map. Pan and zoom using bundled map data.

  7. Prepare the response for review.

    Choose an acknowledgement type and generate a formatted AKNLDG draft using the source message and configured command details. Save it privately or copy it; the draft remains unsent.

  8. Know when traffic needs attention.

    In-app notifications flag new messages, intake and publication failures, and recovery. Open the related message when available, and keep track of what you’ve read.

Built to run locally. OTIS retains accepted source emails, avoids duplicate message entries, and retries interrupted work. The application, search, and maps run locally without a GPU; disconnected use requires prepared runtime assets and the configured local services.

The order stays the reference. Coverage is based on tested OPTASK layouts. Check the original message when timing is incomplete, and confirm command applicability before acting. “Since last watch” lists traffic by issue time; it does not identify amendments or cancellations.

The judging lens / Start with the Sailor

Less time piecing together traffic.
More time for the watch.

Select a criterion. Explore the case.

Help the Sailor find the next obligation.

Bring the changeover, the report deadline, and the next scheduled activity into one view, with the order behind each item close at hand.

Evidence behind the approach

Ship-filtered schedules, combined keyword and semantic search, and links to original messages support the Sailor’s review.

Auto-cycling · 12 seconds per criterionRubric weights shown. Operational benefit to be measured in a watch-team pilot.
Built by the Parse Command team

A watch desk built around the work.

Follow a message from the inbox to extracted tasking, the schedule, the original source, and a private acknowledgement draft. Keep the review in the Sailor’s hands.

The next step

Put it in front of a watch team.

Have Sailors find a task, verify its timing, and check the source. Measure the effort, confirm command-specific responsibilities, and use what they find to improve OTIS.

Synthetic illustration / not live traffic

A direct path back to the order.

Fictional plain-language excerpt used to explain the workflow. This is not a standards-conformant USMTF fixture or a live parser result.

The working application links scheduled items to their source messages. The reader shows parsed fields, original text, and processing history. Incomplete timing requires checking the source; the calendar has no separate unresolved-time review list.

Challenge requirements / Current coverage

The outcome—and the remaining work.

The required deliverable converts mock USMTF text into a synchronized 24-hour visual schedule, with command-relevant tasking and a coordinating C2 point of contact.

Challenge requirementCurrent positionOperational meaning
Convert raw USMTF message textImplemented for tested profilesFourteen tested OPTASK message types feed a common extraction and review workflow.
Extract frequencies, crypto windows and flight-quarters timesCoverage is partialFrequency plans, crypto changeover points and other explicit activities are covered. Flight quarters needs a representative fixture and SME validation.
Surface tasking for the specified commandCommand resolution remainsTask records and command filters exist. Reliable command aliases and local applicability still need validated mapping.
Present a consolidated 24-hour scheduleImplemented workflowDay, week, and month views support Zulu or a selected time zone, with ship filters and side-by-side day schedules. Unresolved timing is excluded from the plotted schedule; users must check the source message.
Identify the coordinating C2 point of contactSource contacts extractedSource POCs are preserved. Assigning the correct local CO / XO / OPS / CHENG role requires a command roster and validation.
Nice-to-haves: response drafts and conflict awarenessPrivate acknowledgement draftsAcknowledgement drafts can be generated and saved privately for review; SMTP response delivery is not implemented. Broader formatted operational responses and existing-command-schedule conflict detection remain to be validated or added.

Tested profiles establish example-based coverage. Flight quarters, command applicability and local officer ownership need representative inputs and domain validation.

Supporting detail

What supports this briefing.

Briefing refined 05 Nov 2026. Prior validation is attributed to the project records below; application test suites were not rerun for this presentation. No source traffic is embedded.

Opening statement / about 30 seconds

Start with the Sailor.

“You have the watch. A crypto changeover is in one message, a report deadline in another, and more traffic is coming. OTIS turns supported naval messages into searchable tasking and one schedule. Find what’s due, check the time, and open the original order. It runs locally and keeps you in control of the review. We’ve tested fourteen OPTASK message types. Next, we want Sailors to use it on a watch-team pilot and measure the difference.”