ANNOUNCEMENT OF THE OPERATIONAL DATA INTEGRATION NEXUS (ODIN) AS THE AUTHORITATIVE OPERATIONAL REPORTING APPLICATION FOR THE MARINE CORPS

R 181647Z JUN 26
MARADMIN 281/26
MSGID/GENADMIN/CMC PPO WASHINGTON DC//
SUBJ/ANNOUNCEMENT OF THE OPERATIONAL DATA INTEGRATION
NEXUS (ODIN) AS THE AUTHORITATIVE OPERATIONAL REPORTING
APPLICATION FOR THE MARINE CORPS//
REF/A/MCO 3000.2J/SUBMISSION REQUIREMENTS FOR THE COMMANDERS'
OPERATIONAL SITREP.
NARR/REF A IS SUBMISSION REQUIREMENTS FOR THE
COMMANDERS' OPERATIONAL SITUATIONAL REPORT (SITREP).
REF/B/MCO 3504.1A/MARINE CORPS LESSONS LEARNED PROGRAM
NARR/REF B IS THE ORDER THAT DIRECTS REQUIREMENTS FOR THE
MARINE CORPS CENTER FOR LESSONS LEARNED AND GOVERNS AFTER
ACTION REPORT GENERATION.//
REF/C/MCO 5750.1H MANUAL FOR THE MARINE CORPS HISTORICAL
PROGRAM
NARR/REF C IS THE ORDER THAT DIRECTS COMMAND CHRONOLOGY
REPORTING REQUIREMENTS.//
POC1/HUFF, CHRISTOPHER/LTCOL/PP&O, PO, POC, COG
OIC/CML:703-571-1038/NIPR:[email protected]/
SIPR:[email protected]
POC2/GOODALE, JASON/COL/PP&O PO, POC BRANCH
HEAD/CML:703-571-1070/NIPR:[email protected]/
SIPR:[email protected]//
POC3/M. SILVIA/CIV/MCCLL/CML:703-432-1950/EMAIL:MARK.A.
[email protected]
POC4/T. MCKAVITT/LTCOL/MARINE CORPS HISTORY DIVISION/CML:
703-432-5216/EMAIL:[email protected]
GENTEXT/1. Purpose. This MARADMIN announces the transition
to a new operational Situation Reports (SITREP) reporting
platform, reiterates current reporting requirements for
SITREPs, After Action Reports (AARs), and command
chronologies, and directs all Marine Corps units to comply
with the references.
2. Background
2.a. The Operational Data Integration Nexus (ODIN) is a
digital application in Maven Smart System (MSS) to support
Operational SITREP reporting requirements.
2.b. Scheduled for release on 7 July 2026, ODIN will serve
as the official reporting tool for Marine Corps
Operational SITREPs, operations, activities, and
investments, and custom report generation.
2.c. Prior to the 7 July 2026 release, the Deputy Commandant
for Plans, Policies, and Operations will issue a task
order detailing instructions and providing the access link
for the ODIN application in MSS.
2.d. Commanders must activate their MSS licenses and
designate key personnel to do the same to ensure
compliance with the task order for SITREP reporting via
the ODIN.
2.e. Reference (a) is in draft re-write and will be released
upon approval.
3. Action. This MARADMIN directs all Marine Corps units to
comply with the guidance contained in references (a), (b),
and (c).
3.a. Reference (a) is available at:
https://www.marines.mil/news/publications/mcpel/electronic
-library-display/article/899454/mco-30002j/
(1) SITREP reporting transitions to the ODIN on 7 July
2026.
(2) Reporting requirements in accordance with
reference (a) remain in effect until the release of MCO
3000.2k, which supersedes MCO 3000.2j.
3.b. Reference (b) is available at:
https://www.marines.mil/news/publications/mcpel/electronic
-library-display/article/898975/mco-35041a/
(1) Active component Marine Corps organizations and units
will submit AARs and any supporting material for
operations, deployments, major exercises, Marine Corps
combat readiness evaluations, and service-level training
exercises to Training and Education Command (TECOM) within
30 days of completion.
(2) Reserve component units will submit AARs and any
supporting material to TECOM within 60 days of event
completion to accommodate a development, review, and
submission process occurring over two consecutive drill
periods.
(3) Lessons learned materials classified Top
Secret/Sensitive Compartmented Information (TS/SCI) will
be uploaded directly to the Joint Lessons Learned
Information System (JLLIS) on the Joint Worldwide
Intelligence Communication System (JWICS).
(4) In addition to submitting lessons learned products to
TECOM for posting to the Marine Corps Center for Lesson
Learned Knowledge Management Site, units must ensure final
products are disseminated to all commands with equity in
The event.
3.c. Reference (c) is available at:
Https://www.marines.mil/news/publications/mcpel/electronic
-library-display/article/899505/mco-57501h/.
MARADMIN 200/25 provides updated guidance for submissions
pending a revision of reference (c).
(1) Submit command chronologies directly to Marine Corps
History Division per the schedule in MARADMIN 200/25. The
complete command chronology must be a single digital PDF
containing a signed cover page. A valid submission
requires the digital transfer of the complete command
chronology to the History Division via email or DoD Safe
to [email protected].
(2) Units temporarily activated for specific exercises or
operations will complete a command chronology at
deactivation. If the unit remains active for more than six
months, the annual or semi-annual reporting periods apply
until the deactivation date.
(3) Units deployed to combat or contingency operations
must submit monthly command chronologies by the 15th of
the following month. The affected command will be notified
by message when monthly submissions are required. Upon
conclusion of the deployment or special situation,
reporting will revert to an annual or semi-annual basis,
covering only the period since the last submission.
(4) If submitting a classified command chronology, contact
the History Division via the e-mail in para 3.c.(1) for
specific instructions.
4. This MARADMIN is applicable to the Marine Corps Total
Force.
5. Release authorized by LtGen J. M. Bargeron, Deputy
Commandant for Plans, Policies, and Operations.//