R 241425Z JAN 01 ZYW
FM CMC WASHINGTON DC//C4//
TO MARADMIN
BT
UNCLAS //N01234//
MARADMIN 039/01
MSGID/GENADMIN/CMC WASHINGTON DC/C4//
SUBJ/EXIT CRITERIA FOR USER TRANSITION TO DEFENSE MESSAGE
/SYSTEM (DMS)//
REF/A/MARADMIN 573-00/CMC WASHINGTON DC C4/272103ZNOV2000//
AMPN/REF A IS MARADMIN 573/00 PROVIDING DMS TRANSITION GUIDANCE FOR
USMC.//
POC/AUGUSTO G CATA/MAJ /CMC WASHINGTON DC C4 CS/-/TEL:703-607-5552
/EMAIL:CATAAG@HQMC.USMC.MIL//
RMKS/1. PER REF A, THIS MESSAGE DEFINES AND PROVIDES AMPLIFYING
INSTRUCTION AND GUIDANCE ON THE MARINE CORPS EXIT CRITERIA FOR DMS.
THIS EXIT CRITERIA WILL BE THE BASIS FOR DETERMINING WHEN THE MARINE
CORPS WILL DECLARE ITSELF DMS OPERATIONAL.
2. DEFINITIONS.
A. EXIT CRITERIA: THOSE MEASUREMENTS REQUIRED TO ASSESS THE
OPERATIONAL ACCEPTABILITY OF THE DMS.
B. SUSTAINED DMS OUTAGE: ANY SITUATION THAT PREVENTS AN
ORGANIZATION FROM SENDING/RECEIVING DMS ORGANIZATIONAL MESSAGES,
EXCLUDING SPECIAL HANDLING (SHD), SPECIAL CATEGORY (SPECAT),
EMERGENCY ACTION MESSAGES (EAM) AND ALLIED MESSAGING, FOR MORE THAN
24 HOURS.
C. HIGH PRECEDENCE MESSAGES: MESSAGES ASSIGNED A MESSAGE
HANDLING PRIORITY OF IMMEDIATE OR ABOVE.
D. DISTINGUISHED NAME (DN): IDENTIFIES A COMMAND WITHIN THE
X.500 DIRECTORY. SIMILAR TO AUTODIN PLAIN LANGUAGE ADDRESS (PLA).
3. DMS OPERATIONAL MILESTONES. REF A DIRECTS ALL MARINE
CORPS ORGANIZATIONS, WHILE IN A GARRISON STATUS, TO BEGIN
TRANSMITTING ALL OUTBOUND ORGANIZATIONAL MESSAGES VIA DMS BEGINING
15 DEC 00 OR ONCE THE UNIT IS DMS FUNCTIONAL AND TO ACHIEVE DMS
OPERATIONAL STATUS NLT 30 JUN 01. THE MARINE CORPS GOAL FOR BEING
OPERATIONAL CAN ONLY BE MET WHEN THE COMMANDERS/COMMANDING OFFICERS
OF THOSE ORGANIZATIONS ARE COMFORTABLE WITH AND CONFIDENT IN THE
ABILITY OF DMS TO MEET MESSAGING REQUIREMENTS. THE FOLLOWING
MINIMUM EXIT CRITERIA SHALL BE MET PRIOR TO TERMINATION OF INCOMING
LEGACY MESSAGING SERVICES TO ANY MARINE CORPS GARRISON ORGANIZATION.
THIS POLICY DOES NOT APPLY TO SPECIAL HANDLING (SHD), SPECIAL
CATEGORY
(SPECAT), EMERGENCY ACTION MESSAGES (EAM), OR ALLIED MESSAGING.
A. COMMANDS SHALL AUDIT DMS VS AUTODIN MESSAGE ACCOUNTABILITY
FOR AT LEAST 30 DAYS, AND THEY SHALL DETERMINE THAT DMS HAS
DEMONSTRATED RELIABLE MESSAGE DELIVERY.
B. PROCEDURES FOR NOTIFICATION OF HIGH PRECEDENCE DMS MESSAGE
TRAFFIC SHALL BE ESTABLISHED BY EACH COMMAND PRIOR TO 01 MAR 01.
C. CONTINGENCY PROCEDURES SHALL BE ESTABLISHED BY EACH COMMAND,
IN COORDINATION WITH THEIR SUPPORTING LCC, FOR RESTORING AUTODIN
MESSAGE SERVICE IN THE EVENT OF A SUSTAINED DMS OUTAGE. NOTE:
CURRENT DMS INFRASTRUCTURE LACKS REDUNDANCY/FAIL OVER CAPABILITIES,
LOCAL CONTROL CENTERS MUST RETAIN LEGACY MESSAGING EQUIPMENT FOR
PURPOSES OF CONTINGENCY RESTORAL OF MESSAGE SERVICE UNTIL FURTHER
NOTICE.
D. LCC'S SHALL COORDINATE TRANSITION TO DMS-ONLY DELIVERY.
CUSTOMERS WITH VALID REQUIREMENT FOR SPECAT, SHD, EAM, OR ALLIED
MESSAGING SERVICES WILL RETAIN DUAL AUTODIN AND DMS MESSAGE
DELIVERY, FOR THESE TYPES OF MESSAGES ONLY, UNTIL EQUIVALENT
FUNCTIONALITY IS INCORPORATED IN A SUBSEQUENT DMS REVISION.
4. IN ORDER TO ASCERTAIN THE MARINE CORPS ACCEPTANCE OF THE DMS,
COMMANDS LISTED IN PARAGRAPH 5 WILL TRANSMIT AN OFFICIAL MESSAGE TO
DIRECTOR C4, CMC WASHINGTON DC PROVIDING THE INFORMATION LISTED IN
PARAGRAPH 6 ON THE LAST DAY OF EACH MONTH BEGINING IN FEB 01.
5. THE FOLLOWING COMMANDS ARE RESPONSIBLE FOR PROVIDING THE
INFORMATION LISTED IN PARAGRAPH 6 FOR THEIR COMMANDS AND ANY
SUBORDINATE COMMANDS AND BASE/POST/STAIONS UNDER THEIR CONGNIZANCE:
CMC WASHINGTON DC/ARI
COMMARFORLANT
COMMARFORPAC
COMMARFORRES
COMMARFORSOUTH
COMMARFOREUR
COMMARCORMATCOM ALBANY GA
CG MCB QUANTICO VA
CG MCAGCC TWENTYNINE PALMS CA
6. THE FOLLOWING QUESTIONS WILL BE ANSWERED PER PARAGRAPH 4. ANY
NEGATIVE RESPONSES REQUIRE DETAILED COMMENTS OUTLINING THE PROBLEMS,
RECOMMENDED SOLUTIONS, AND/OR COMPLETION DATES.
A. TRAINING
1. HAS THE COMMAND INSTITUTIONALIZED DMS USER TRAINING?
2. DOES THE COMMAND HAVE ANY USER TRAINING SHORTFALLS THAT
REQUIRE MCSC OR DIRECTOR C4 ATTENTION?
B. SYSTEM RELIABILITY
1. IS THE SYSTEM AVAILABLE GREATER THAN NINETY-FIVE PERCENT
OF THE TIME? IF NOT, WHAT PROBLEMS ARE AFFECTING SYSTEM RELIABILITY?
C. COMMAND PROCEDURES
1. HAVE COMMANDS IMPLEMENTED HIGH PRECEDENCE NOTIFICATION
PROCEDURES?
2. DOES THE COMMAND HAVE A NEED FOR DUAL-ADDRESSING OF OUTBOUND
DMS MESSAGES, I.E. ADDRESSING A MESSAGE TO A UNITS AUTODIN PLA AND
DMS DN?
3. WHY IS THE DUAL DELIVERY OF NON-SPECAT, SPECIAL HANDLING, OR
EAM MESSAGES REQUIRED?
4. HAVE CONTINGENCY PROCEDURES, IN THE ADVENT OF A SUSTAINED DMS
OUTAGE, BEEN DRAFTED AND COORDINATED WITH THE SUPPORTING LCC?
D. WHAT DATE DO YOU EXPECT TO BE 100% OPERATIONAL, AS DEFINED IN
REF A?
E. LIST THOSE COMMANDS THAT ARE 100% OPERATIONAL, AS DEFINED IN
REF A.
F. ARE THERE ANY INHERENT SYSTEM FLAWS THAT PREVENT YOU FROM
BECOMING OPERATIONAL?
7. LOCAL CONTROL CENTERS (LCC) WILL CONTINUE TO PROVIDE DMS STATUS
REPORTS TO MARCORSYSCOM. MARCORSYSCOM WILL PROVIDE GUIDANCE UNDER
SEPARATE CORRESPONDENCE.//
BT