JUL 2019 CHANGES TO DEFENSE READINESS REPORTING SYSTEM-MARINE CORPS
Date Signed: 7/11/2019 | MARADMINS Number: 387/19
MARADMINS : 387/19

R 102110Z JUL 19
MARADMIN 387/19
MSGID/GENADMIN/CMC WASHINGTON DC PP&O//
SUBJ/JUL 2019 CHANGES TO DEFENSE READINESS REPORTING SYSTEM-MARINE CORPS//
REF/A/MCO 3000.13/18JUL2017//
REF/B/CJCSI 3401.02B/FORCE READINESS REPORTING/31MAY2011//
NARR/ REF A PROMULGATES POLICIES AND PROCEDURES FOR REPORTING READINESS ON MARINE CORPS ORGANIZATIONS. REF B ESTABLISHES POLICY, PROCEDURES, AND CRITERIA FOR THE REPORTINGOF AUTHORITATIVE INFORMATION TO THE PRESIDENT AND SECRETARY OF DEFENSE RELATED TO THE READINESS OF MILITARY FORCES TO MEET MISSIONS AND GOALS ASSIGNED BY THE SECRETARY OF DEFENSE//
POC/B. A. HULL/POR/(703)571-1031//
POC/J. T. ENOCH/POR/(703)571-1063//
POC/A.C. SOTO/POR/(703)571-1018//
GENTEXT/REMARKS/1.  This message summarizes updates for the Defense Readiness Reporting System-Marine Corps (DRRS-MC) scheduled for 11 Jul 2019.
2.  DRRS-MC updates will include:
2.a.  Import manning document (MD).
2.b.  Mission essential tasks (MET) assessment resource rollup.
2.c.  Intermediate report subordinate resource rollup.
2.d.  Net-Centric Unit Status Report Marine Corps (NETUSR-MC) style sheet refresh.
2.e.  Unit naming convention from the organizational server.
2.f.  Core and task organized structure display and printing.
3.  Import manning document (MD).
3.a.  Background.  Currently the DRRS-MC Network-Enabled Unit Status Report (NETUSR) requires the user to enter all personnel data for assigned missions manually based on an approved manning document (MD) or Joint Manning Document (JMD).  To reduce data entry workload and improve data accuracy a user interface (UI) will auto-populate the personnel for assigned missions from the authoritative source.
3.b.  Unit level user shall have a button to initiate the import from the assigned mission personnel page. The UI will import the file from the users local computer.  The unit must have already been given the assigned mission and the approved MD.
3.c.  Users shall be able to edit the on hand, available, and personnel data (i.e. Critical MOS).
3.d.  A new MD upload shall overwrite any existing assigned mission structure and DRRS-MC will warn the user before executing.  The assigned mission structure from an MD will carry forward until the assigned mission is dropped.
4.  MET assessment resource rollup.
4.a.  While completing MET assessments in DRRS-MC, many resource standards on the MET assessment page require resource data that has already been filled in on the Personnel (P) and Equipment (S)and(R) pages.  To make it easier to see what users have already entered, the resource data will be displayed at the top of the MET assessment page for both core and assigned missions.  MARFORs and Installations will not see this section as they do not have resource levels.
4.b.  The core mission MET assessment page will display the core resource roll-ups.  The primary assigned mission will display the assigned resource roll-ups.  Other assigned missions will display the core resource roll-up.
5.  Intermediate report subordinate resource rollup.
5.a.  Background.  Intermediate unit reports in DRRS-MC have resource levels (P, R, and S) that are not objectively calculated like regular reports.  Frequently, intermediate report resource levels are incongruent with their subordinate units.  IAW ref a, intermediate reports should consider the resources of their subordinate units when calculating their resource levels.  Displaying a rollup of the latest resources from the subordinate units on the intermediate commanders summary page will help with meeting the intent of ref a.
5.b.  For intermediate units, the commanders summary page will have a separate table that will display the P, S, R, and T of the first level of subordinate units by current OPCON.
5.b.1.  All tables will show the UIC of the subordinate unit.  If the user rolls over any of the row data, the unit name will be displayed.  The percentages used for the levels will be highlighted for the user to easily see which one was used.  A total row will be display at the bottom of each table.
5.b.2.  If a subordinate has never reported, the fields in the row will show with dashes. If the subordinate displays other intermediate units, or units that report level 6, the fields will display as blanks.
5.b.3.  The tables will not be seen on completed reports.  This is due to the data being from the most current of their subordinate reports information and the data could be confusing for completed reports.  Table data can be printed for in progress reports only.
6.  Net-Centric Unit Status Report Marine Corps (NETUSR-MC) style sheet refresh.
6.a.  DRRS-MC NETUSR-MC style sheet has not been updated since the application was fielded in 2010.  To be consistent with other Marine Corps applications and improve the user experience, the Cascading Style Sheet (CSS) has been updated to a desert MARPAT style similar to marines.mil.
6.b.  It will not change the functionality nor make the application harder to use.
7.  Unit naming convention from the organizational server.
7.a.  Background.  DRRS-MC maintains a separate naming convention than what is used on the Marine Corps Organizational Server (MCOS).  In order to be Global Force Management–Data Initiative (GFM-DI) compliant and reduce confusion, DRRS-MC will adopt the MCOS naming convention.
7.b.  When the next Total Force Structure Management System (TFSMS) Authorized Strength Report (ASR) is published, DRRS-MC will update the short and long unit names to match the MCOS data.  The system shall only update one year of past unit reports where the Unit Identification Code (UIC) is the same.
7.c.  This update will not change the functionality nor make the application harder to use.
8.  Core and task organized structure display and printing.
8.a.  Background.  Due to technical issues during deployment to SIPRNET, this capability was not functional as outlined in MARADMIN 284/19 May 2019(DTG 150844Z May 19).  All issues have been resolved and user will be able to export data for printing as desired.
9.  DRRS-MC will be updated on Thursday, 11 Jul from 1800 to approximately 2200 Eastern Standard Time (EST).  Users will not be able to access DRRS-MC while the system is updating.  In-progress reports will not be effected by this update.
10.  Way ahead.  The July updates to DRRS-MC are part of an enduring effort to improve the breadth, reliability, and utility of USMC readiness data.  The PP&O Readiness Branch, MARFOR, and MEF readiness offices are prepared and capable of providing additional support.  Commanders and units are encouraged to provide additional recommendations to strengthen service readiness policy and improve the accuracy and reliability of readiness reporting.
11.  Release authorized by Brigadier General Norman L. Cooling, Deputy Commandant, Plans, Policies, and Operations (Acting).//