DESIGNATION OF DATASET RECORDS MANAGERS (DRM):
RAAUZYUW RUENAAA0078 2411226-UUUU--RUCCBWF. ZNR UUUUU ZUI RUEWMCF0928 2412223 R 291226Z AUG 06 PSN 865983I39 FM CNO WASHINGTON DC//DNS// TO NAVADMIN INFO RHMFIUU/CNO WASHINGTON DC//DNS// RUENAAA/CNO WASHINGTON DC//DNS// BT UNCLAS NAVADMIN 246/06 MSGID/GENADMIN/CNO WASHINGTON DC/DNS/AUG// SUBJ/DESIGNATION OF DATASET RECORDS MANAGERS (DRM)// REF/A/DOC/OPNAVNOTE 5210/28JUL2006// AMPN/REF A IS OPNAVNOTE 5210 THAT DESCRIBES THE DESIGNATION OF NAVY FUNCTIONAL AREA MANAGER (FAM) APPROVED RECORDS MANAGEMENT SOLUTION FOR CHIEF OF NAVAL OPERATIONS (CNO) COMMANDS.// POC/CHALEY BARTH/CIV/OPNAV DNS-5/LOC:WASHINGTON DC/TEL:(202) 433-2434 // RMKS/1. ELECTRONIC RECORDS MANAGEMENT SOLUTION (ERMS) DATASETS ARE CURRENTLY BEING DEPLOYED ON NAVY MARINE CORPS INTRANET (NMCI) ACROSS THE DEPARTMENT OF THE NAVY. THE ERMS, TRIM CONTEXT, DEPLOYMENT SCHEDULE IS VERY AGGRESSIVE. PER REF A, IN ORDER TO SUPPORT AN OPNAV DNS-5 FUNDED SIX WEEK INITIAL IMPLEMENTATION PERIOD FOR THESE TRIM DATASETS, DESIGNATED COMMANDS SHALL APPOINT A COMMAND DATASET RECORDS MANAGER (DRM) AND PROVIDE POINT OF CONTACT (POC) INFORMATION TO OPNAV DNS-5 NLT 15SEP06, THIS IS A DATE CHANGE FROM REF A. THIS INITIAL IMPLEMENTATION PERIOD WILL INCLUDE DATASET PLANNING, PROCESS ANALYSIS, AND TRAINING FOR END USERS, ADMINISTRATORS, AND THE DRM. 2. THE PURPOSE OF THIS MESSAGE IS TO IDENTIFY NAVY COMMANDS CURRENTLY SCHEDULED TO RECEIVE A DATASET DURING THE INITIAL DATASET DEPLOYMENT AND TO PROMULAGATE THE PROCEDURE FOR NAVY COMMANDS TO REPORT POC INFORMATION TO OPNAV DNS-5. 3. THE FOLLOWING COMMANDS ARE CURRENTLY SCHEDULED TO RECEIVE A TRIM DATASET AND SHALL APPOINT A COMMAND DATASET RECORDS MANAGER AND PROVIDE POC INFORMATION TO OPNAV DNS-5: NAVAL SUPPLY SYSTEMS COMMAND COMMANDER, NAVAL SUBMARINE FORCES NAVY EXPEDITIONARY COMBAT COMMAND COMMANDER, NAVAL AIR FORCES COMMAND NAVAL NETWORK WARFARE COMMAND OFFICE OF NAVAL INTELLIGENCE NAVAL FACILITIES ENGINEERING COMMAND COMMNADER, OPERATIONAL TEST AND EVALUATION FORCE COMMANDER, NAVAL SURFACE FORCES COMMAND REGIONAL MAINTENANCE COMMAND, NORFOLK COMMANDER, U.S. PACIFIC FLEET COMMANDER, NAVAL INSTALLATIONS COMMAND NAVAL METEOROLOGY AND OCEANOGRAPHY COMMAND NAVY WARFARE DEVELOPMENT COMMAND NAVAL EDUCATION AND TRAINING COMMAND BUREAU OF NAVAL PERSONNEL COMMANDER, NAVAL FORCES CENTRAL COMMAND COMMANDER, NAVAL RESERVE FORCE COMMANDER, NAVAL FORCES EUROPE MATERIAL AND LOGISTICS COMMAND NAVAL SPACE AND WARFARE COMMAND OFFICE OF NAVAL RESEARCH 4. PROCEDURE FOR REPORTING: IN ORDER TO COMPLY WITH REF A, COMMANDS SHALL APPOINT A DRM AND REPORT THE POC INFORMATION TO OPNAV DNS-5 AS FOLLOWS: COMMAND NAME DRM NAME DRM EMAIL ADDRESS DRM PHONE NUMBER PROVIDE POC INFORMATION TO OPNAV DNS-5 VIA EMAIL TO CHARLEY.BARTH@NAVY.MIL OR LOG ON TO NAVY KNOWLEDGE ONLINE (NKO) AND PROVIDE POC INFORMATION VIA THE OPNAV DNS-5 ORGANIZATION PAGE ON NKO. TO LOCATE THE PAGE, LOG ON NKO AT WWW.NKO.NAVY.MIL, THEN SELECT ORGANIZATIONS IN THE ORGANIZATIONS AND COMMUNITIES DROP DOWN BOX ON THE NKO MAIN PAGE, THEN SELECT OPNAV DNS-5. THIS WILL TAKE YOU TO THE ELECTRONICS RECORDS MANAGEMENT COMMUNITY PAGE. ON FEEDBACK GEAR ON THIS PAGE, ENTER THE REQUIRED REPORTING INFORMATION AND CLICK ON THE SUBMIT BUTTON. ALL COMMANDS WILL BE IN COMPLIANCE ONCE THEY RECEIVE A REPLY EMAIL STATING YOUR POC INFORMATION HAS BEEN RECEIVED. 5. ALL COMMAND POCS WILL BE GIVEN ACCESS TO THE DRM COMMUNITY OF PRACTICE (COP) PAGES ON NKO AND WILL BE ADDED TO THE DRM FORUM EMAIL DISTRIBUTION LIST. 6. SPECIFIC SCHEDULING OF DATASET IMPLEMENTATIONS SHALL BE PROVIDED SEPCOR. DRM POC PROVIDED BY COMMANDS SHALL BE THE POC FOR FURTHER INFORMATION ON DATASET IMPLEMENTATION SCHEDULING. PLEASE DIRECT ALL QUESTIONS OR CONCERNS TO MR. CHARLEY BARTH. 7. RELEASED BY VADM A. E. RONDEAU, DIRECTOR, NAVY STAFF.// BT #0078 NNNN