R 242137Z FEB 26
MARADMIN 062/26
MSGID/GENADMIN/CMC L LF WASHINGTON DC//
SUBJ/MARINE CORPS ENTERPRISE MASS NOTIFICATION SYSTEM MIGRATION TO
ALERT!//
REF/A/DOWD 8422.01E, DOW PUBLIC SAFETY COMMUNICATIONS APABILITY, 8
JUN 2022 //
REF/B/DOWI 6055.17, DOW EMERGENCY MANAGEMENT (EM) PROGRAM, 1 DEC
2025//
REF/C/MCO 3440.10, MARINE CORPS EMERGENCY MANAGEMENT POLICY, 7 FEB
2025//
REF/D/MARADMIN 492/22, MARINE CORPS MASS WARNING AND NOTIFICATION
REGISTRATION AND ENROLLMENT, 23 SEP 2022//
REF/E/MCTP 10-10G, MULTI-SERVICE TACTICS, TECHNIQUES, AND PROCEDURES
FOR EMERGENCY MANAGEMENT, 21 JUL 2021//
REF/F/MCICOM MASS WARNING NOTIFICATION SYSTEM TRANSITION MEMO, 20
OCT 2024//
REF/G/ENTERPRISE ARCHITECTURE REQUIREMENTS FOR THE DEPARTMENT OF
DEFENSE EMERGENCY MASS WARNING AND NOTIFICATION SYSTEM MEMO, 5 SEP
2025//
REF/H/MARINE CORPS MASS NOTIFICATION SYSTEM CONCEPT OF OPERATIONS,
15 JUL 2024//
NARR/ REF (A) PROMOTES A STANDARDIZED AND RESILIENT APPROACH TO
EMERGENCY ALERTS, WARNINGS, AND COORDINATION SYSTEMS, ENSURING
EFFECTIVE COMMUNICATION DURING INCIDENTS.REF (B) DIRECTS DOW
COMPONENTS TO ENSURE TIMELY WARNING, NOTIFICATION, AND PROTECTIVE
ACTIONS FOR PERSONNEL AND PROPERTY, PROVIDING THE FOUNDATIONAL
FRAMEWORK FOR EM PROGRAMS AND MASS NOTIFICATION SYSTEMS ACROSS THE
DEPARTMENT. REF (C) INTEGRATES EMERGENCY MANAGEMENT INTO THE MARINE
CORPS' MISSION ASSURANCE FRAMEWORK AND REQUIRES COMMANDERS TO
MAINTAIN EFFECTIVE MASS WARNING AND NOTIFICATION SYSTEMS.  REF (D)
MANDATES REGISTRATION AND DATA MAINTENANCE REQUIREMENTS FOR ALL
MARINE CORPS PERSONNEL WITHIN THE MASS WARNING AND NOTIFICATION
SYSTEM. REF (E) PROVIDES MULTI-SERVICE TACTICS, TECHNIQUES, AND
PROCEDURES (TTPS) FOR THE COORDINATION, RESPONSE, AND RECOVERY
PHASES OF EMERGENCY MANAGEMENT OPERATIONS. REF (F) DIRECTS THE
TRANSITION FROM THE LEGACY ATHOC SYSTEM TO ALERT!. REF (G) DEFINES
THE ENTERPRISE ARCHITECTURE STANDARDS AND CYBERSECURITY
REQUIREMENTS FOR THE DOW EMERGENCY MASS WARNING AND NOTIFICATION
SYSTEM. REF (H) DEFINES THE MARINE CORPS MASS NOTIFICATION SYSTEM
CONCEPT OF OPERATIONS (CONOPS), WHICH DETAILS THE SYSTEM'S
OPERATIONAL PURPOSE, STRUCTURE, AND PERFORMANCE EXPECTATIONS.//
POC/GEORGE BERGER/GS-14/MCICOM G-3/EM BRANCH HEAD/EMAIL:
GEORGE.BERGER@USMC.MIL/TEL: (571) 256-7091//
POC/JASON TERRY/GS-13/MCICOM G-3/EM SPECIALIST/EMAIL:
JASON.TERRY@USMC.MIL/TEL: (571) 256-8195//
GENTEXT/REMARKS/1. This message supersedes MARADMIN 492/22. It
provides guidance on the Department of War (DOW) transition to a
single, enterprise-wide Mass Warning and Notification System (MWNS).
The Alert! MWNS is a multi-modal system that meets all DOW 
requirements for timely warnings to personnel on and off DOW
Installations, enhancing cost savings and operational efficiency.
All Marine Corps Installations and organizations using ATHOC will
transition to Alert! to provide a standard emergency notification
system. In order to protect personnel and property during
all-threats and hazard incidents, MCICOM G-3 will coordinate with
the U.S. Army Tank-Automotive and Armaments Command (TACOM) Alert! 
team to manage migration, training, and sustainment by providing a 
standardized MWNS. Achieving FOC will enable notifications to 90%
of the affected population within ten minutes of incident
verification, and 100% within one hour.
2. Commander, Marine Corps Installations Command (COMMCICOM)
directs all Alert! activities. MCICOM will deploy Alert! NLT Q3 
Fiscal Year 2026. The existing ATHOC system remains operational 
until Alert! is fully deployed locally. The migration will occur in
four phases:
2.A. Phase 1, Coordination: Appoint POCs, publish orders,
coordinate migration requirements, and develop fielding timelines.
2.B.2. Phase 2, Preparation: Review data, assess migration
needs, and coordinate configuration with TACOM.
2.C.3. Phase 3, Migration/IOC: Migrate data, conduct System
Operational Verification Testing (SOVT), final data validation and
deliver New Equipment Training (NET).
2.D.4. Phase 4, Sustainment/FOC: TACOM provides 24/7/365 help
desk support, lessons learned reporting, and system sustainment.
3. Phase 1
3.A. MCICOM G-3 (Emergency Management):
3.A.1. Serve as mission lead and ensure compliance.
3.A.2. Provide regular progress updates to G-3 leadership.
3.A.3. Manage deployment coordination.
3.A.4. Identify key installation and command POCs.
3.A.5. Coordinate dates for pre-deployment engagements.
3.A.6. Ensure administrators and operators attend training.
3.A.7. Establish Information Owners utilizing DD Form 2875 (SAAR).
3.A.8. Develop standardized notification templates for Alert!.
3.A.9. Coordinate all subordinate installation locations.
3.A.10. Coordinate facility support for deployment needs.
3.A.11. Schedule migration assessment meetings.
3.A.12. Identify telephone throttling information.
3.A.13. Coordinate with information technology and network support
organizations to push the Alert! PC client to test workstations.
3.A.14. Identify users by type: Standard User (operator and
personnel manager), Operator (send/manage alerts), Personnel
Manager (manage personnel), and Component Level Admin (manage
component wide settings).
3.A.15. Finalize deployment dates and workforce notifications.
3.A.16. Reserve facilities for deployment engagements.
3.A.17. Document unique reimbursable work requirements.
3.B. MCICOM G-6:
3.B.1. Act as the MCEN Technical SME and principal liaison.
3.B.2. Identify G-6 technical, cyber, and integration POCs.
3.B.3. Review infrastructure and identify gaps.
3.B.4. Add Alert! software to the Marine Corps Enterprise Desktop
Standardization (MCEDS) image.
3.B.5. Manage cybersecurity assessment and develop an assess-only
authority to operate (ATO) package in Enterprise Mission Assurance
Support Service (eMASS).
3.B.6. Coordinate vulnerability scanning of the Alert! software.
3.B.7. Develop an eMASS package for reciprocity with TACOM.
3.B.8. Formalize the Alert! Department of the Navy Application and
Database Management System (DADMS) record.
3.C. Installation Geospatial Information and Services (IGI&S):
3.C.1. Act as the SME for geospatial data.
3.C.2. Appoint POCs for the fielding initiative.
3.D. Marine Corps Cyberspace Operations Group (MCCOG):
3.D.1. Ensure the security and operational readiness of the MWNS.
3.D.2. Appoint POCs for the fielding initiative.
3.E. Program Executive Office for Digital and Enterprise
Services (PEO Digital):
3.E.1. Ensure timelines are met, resources are allocated, and risk
mitigation are mitigated.
3.E.2. Appoint POCs for the fielding initiative.
3.E.3. Add Alert! software to the MCEDS image.
3.F. TACOM Help Desk
3.F.1. Respond to user service tickets and calls.
3.F.2. Troubleshoot system access issues.
3.F.3. Manage incident tickets from creation to resolution.
3.F.4. Monitor for system outages.
3.F.5. Send broadcast messages to affected users.
3.F.6. Process user account creation and deletion.
3.F.7. Manage access requests via DD Form 2875 (SAAR).
3.F.8. Validate user authorization per DOW policies.
3.F.9. Coordinate with system, cyber, and database teams.
3.F.10. Communicate system status to users and leadership.
3.F.11. Maintain detailed ticket logs and status reports.
3.F.12. Support audit and compliance reporting.
3.F.13. Provide MWNS training and system upgrades as required.
3.F.14. Conduct trend analysis.
3.F.15. Provide system upgrades and modifications for improvements.
4. Phase 2
4.A HQ MCICOM G-3 (Emergency Management):
4.A.1. Extract and deliver data .CSV files to TACOM via DOW 
SAFE.
4.A.2. Confirm TACOM migration script completion.
4.A.3. Schedule migration assessment meeting.
4.A.4. Validate Map (GIS), military locations, and UIC data.
4.A.5. Send initial workforce notification.
4.B. MCICOM G-6:
4.B.1. Attend scheduled meetings.
4.B.2. Validate network requirements and Security Technical
Implementation Guides (STIG) compliance.
4.B.3. Serve as Information System Security Manager (ISSM) and
facilitate cyber interactions with TACOM.
4.B. IGI&S:
4.B.1. Attend scheduled meetings.
4.B.2. Provide foundational map layers for the Alert! interface.
4.C. MCCOG:
4.C.1. Attend scheduled meetings.
4.C.2. Ensure Alert! systems remain compliant with DOW security.
4.D. PEO Digital:
4.D.1. Attend scheduled meetings.
4.D.2. Ensure Alert! software is deployed and maintained securely.
5. Phase 3
5.A. MCICOM G-3 (Emergency Management):
5.A.1. Finalize NET, installation access, and travel plans.
5.A.2. Confirm final client data validation with TACOM.
5.A.3. Schedule and confirm final deployment dates with TACOM.
5.B. MCICOM G-6:
5.B.1 Validate the Alert! ATO on NIPR networks.
5.B.2. Provide a list of all installation network types to TACOM.
5.B.3. Assist with cyber approvals and software testing.
5.B.4. Validate connectivity to the Alert! enterprise environment.
5.C. IGI&S:
5.C.1. Advise G-3 on technical feasibility of geospatial plans.
5.C.2. Attend scheduled meetings.
5.D. MCCOG:
5.D.1. Maintain network configurations, updates, and patches.
5.D.2. Ensure network availability, redundancy, and resiliency.
5.E. PEO Digital:
5.E.1. Ensure networks meet cyber standards,  and Zero Trust
Architecture, updated patches, and secure mobile devices access.
5.E.2. Roll out enterprise identity and credentialing tools.
5.E.3. Push PC clients to workstations.
6. Phase 4
6.A. MCICOM G-3 (Emergency Management):
6.A.1. Submit close-out reports to TACOM.
6.A.2. Establish ongoing support communication channels.
6.A.3. Document lessons learned from the migration.
6.B. MCICOM G-6:
6.B.1. Support routine system updates, patches, and configurations.
6.B.2. Maintain continuous cybersecurity monitoring.
6.B.3. Provide technical troubleshooting and liaison with TACOM.
6.B.4. Ensure sustained system performance.
7. MCICOM Regional Commanders; CG TECOM; COMMARFORRES; and 
COMMARFORCOM.
7.A. Regional Commanders shall appoint regional EMs as Alert!
Information Owners via DD Form 2875 (SAAR). The Regional G-6/S-6
will sign as the Information System Security Officer (ISSO) on the
SAAR.
7.B. NLT 30 working days from release, MWNS Administrators will be
appointed in writing. A copy shall be provided to MCICOM G-3 EM
branch.
7.C. Operators must complete Alert! user training before access.
7.D. TACOM conducts Alert! user training.
7.D.1. Weekly training: Wednesdays at 1300 ET.
7.D.2. Additional training: First Wednesday (0800 & 1800 ET) and
third Wednesday (0800 & 2000 ET) of each month.
7.D.3. Contact the TACOM training team for the training link:
usarmy.detroit.devcom-gvsc.mbx.em2p-help-desk@army.mil or
(866)515-0551.
7.E. Host installation-specific NET is completed with MCICOM G-3
coordination as required.
7.F. All of the Primary Population must enroll and update their info
in Alert! every 90 days, including after-hours contact info.
7.F.1 Primary population (DOW military, civilians, contractors)
whose normal place of duty is on a DOW Installation or within a DOW
Facility (DOW badge holder).
7.F.2. Secondary population are family members associated with the
primary population, including guests, visitors, and other
potentially impacted personnel (extended family, guests) are highly
encouraged to enroll.
7.F.3. Enroll or update information via the Alert! PC client in the
workstation system tray or by signing into dod.alert.mil.
7.G. Integrate Alert! enrollment into check-in/check-out
procedures.
7.H. Test and exercise the Alert! MWNS per refs (a) and (e).
8. Coordinating Instructions.
8.A. MCICOM G-3 EM Branch is the sole Marine Corps conduit to TACOM.
8.B. Operators will coordinate training via the TACOM help desk.
8.C. The Alert! PC client will be installed on all NIPR and program
of records (POR) workstations.
8.D. Installation Commanders will report milestone completion to
MCICOM (G-3, EM) via the chain of command. 
8.E. Direct questions to this MARADMIN's POCs.
9. This MARADMIN is effective upon release and reviewed annually.
10. Release authorized by MajGen Jason G. Woodworth, Assistant 
Deputy Commandant, Installations and Logistics (Facilities).//