
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.
See OTIS in action.
The team’s recorded demonstration.
The video could not load here. Use “Open video” to watch the recording.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Ship-filtered schedules, combined keyword and semantic search, and links to original messages support the Sailor’s review.
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.
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.