R 262042Z SEP 19
MARADMIN 531/19
MSGID/GENADMIN/CMC WASHINGTON DC PPandO//
SUBJ/OCT 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 REPORTING OF 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/CIV/POR/(703)571-1031//
POC/J. T. ENOCH/CIV/POR/(703)571-1063//
POC/A.C. SOTO/CTR/POR/(703)571-1018//
GENTEXT/REMARKS/1. THIS MESSAGE SUMMARIZES UPDATES FOR THE DEFENSE READINESS REPORTING SYSTEM-MARINE CORPS (DRRS-MC) SCHEDULED FOR 03 OCT 2019.
2. DRRS-MC updates will include:
2.a. Assigned mission name display.
2.b. Display submitted reports only latency.
2.c. Equipment equivalence for table of Authorized Material Control Number (TAMCN).
2.d. Geolocation Standardization and display.
2.e. DRRS-S–Marine Corps Total Force System (MCTFS) data file (interim solution).
3. Assigned mission name display.
3.a. Background. With recent updates to the view reports page of the Net-Centric Unit Status Report-Marine Corps (NETUSR-MC) application, units that have an assigned mission are not easily identified visually. To determine what the assigned mission is the user must click on one of the assigned mission boxes. This slows rapid evaluation and search.
3.b. The view report page will now display the assigned mission (if one exists) names in a column named “assigned mission name.” The column will reside after the assigned mission levels and before the “status” column. If the assigned mission name has more characters than can fit in the column, the text will be cut off and the full assigned mission name will be displayed if the user rolls over it with the mouse.
3.c. The HHQ report review and unit dashboard pages will be updated with an “assigned mission name” column.
3.d. The print and Comma-Separated Values (CSV) capabilities will be updated to include the assigned mission column.
4. Display submitted reports only latency.
4.a. Background. The NETUSR-MC application experiences unacceptable latency when the “view submitted reports only” option is selected on the view reports page.
4.b. The filters “show unsubmitted subordinate reports,” “show only the most recent submitted reports,” and “show deleted reports” will be consolidated into a drop down box for selection of one of these at a time. This change will not stop users from seeing their subordinate units’ reports.
4.c. When “show only most recent submitted reports” is selected, the “show all dates” checkbox is automatically selected. With this change, it will not automatically be selected. The user can still select it if they wish.
4.d. Three new fields will be added to also assist the user in filtering the units on the page.
4.d.1. Type of unit–a drop down selection based on the “type of unit” reference table.
4.d.2. Report type–a drop down box of the four different report types (Regular, Intermediate, Installation, MARFOR).
4.d.3. Report status–a drop down of the status of the report.
4.e. An “all submitted” filter has been added. This option will show all submitted reports.
4.f. If the user selects “show deleted reports” filter while also selecting a report status such as “in progress,” the results will display both the deleted reports and the in progress reports.
5. Equipment equivalence for TAMCN.
5.a. Background. When equipment is fielded that replaces older equipment, timing of the fielding can create false degraded readiness in units. For example the table of equipment (t/e) calls for an old piece of equipment (e.g. M2 .50 Cal machine guns), although the unit received the new replacement equipment which is not listed on the T/E. The system will calculate degraded readiness as the report will show the unit has zero M2 .50 Cal machine guns despite having newer, more capable equipment. The end state of this change is to eliminate this false negative in S-levels and improve accuracy in reports.
5.b. HQMC will create a grouping of the unit’s Principal End Items (PEI) or Mission Essential Equipment (MEE) core mission equipment items that have an equivalent value for calculating the S-level. For example, item A001 could have A002 and A0003 in the table as acceptable equivalents. If any item in the group has a requirement in T/E, it is totaled for the group.
5.c. The system shall calculate the S-level against the total group requirement, not individual items within the group. The individual line items will continue to calculate an item’s specific s and R-levels.
5.c.1. In the equipment page, the default setting of these groups will be rolled up. When expanded, it will show the group member items for input. The rollup item will be “read only.”
5.c.2. If the group requirement does not meet the group quantity and there is excess, the excess will automatically be added to the quantity until the requirement is met.
5.d. The “group name” will be added to Marine Corps Readiness Analysis Tool (MCRAT) under AD HOC, resources, equipment, equipment detail, detail other. This will allow the user to sort the AD HOC data by group to see all the data within the group itself.
6. Geolocation standardization and display.
6.a. DRRS-MC uses Joint Operational Planning and Execution System (JOPES) standard geolocation codes across numerous data elements for unit, personnel, and equipment locations. This is a four character code that has significant deficiencies. The primary deficiencies are that the code typically has no intuitive connection with a location, and can only be deciphered via mouseover. This discourages accurate entry of geolocation data and makes analysis problematic.
6.b. To resolve the inherent weakness of the JOPES geolocation codes, the system will have an abstraction layer of headquarters Marine Corps approved geolocations that resolve to JOPES codes for system interfaces. The HQMC approved geolocations will have a standard display name throughout DRRS-MC.
6.c. The list shall include additional regional data for grouping, (i.e. MEF, West Coast, CONUS).
6.c.1. The system will add a Geographic Information Systems (GIS) page that allows geolocation data to be displayed on a map with supporting information to the side.
6.c.2. The GIS page will allow geographic query by geometric overlay.
6.c.3. The GIS page map portion can be exported to print or as an image for other productivity applications such as word or PowerPoint.
7. DRRS-S–Marine Corps Total Force System (MCTFS) data file (interim solution).
7.a. Background. Since 2009, Manpower & Reserve Affairs provided daily personnel data to the Office of the Secretary of Defense (OSD) for the DRRS-S application. DRRS-S is a fully accredited, program of record that resides on the SIPRNET and has PERSTAT with Geographic Location (GEOLOC) data. DRRS-MC will access that data without the cross-domain challenge.
7.b. As an interim solution to on-hand personnel automation, DRRS-MC will query the Marine Corps Total Force System (MCTFS) on SIPR in DRRS-S and update the baseline data.
7.c. This update will not change the functionality or make the application harder to use.
8. DRRS-MC will be updated on Thursday, 03 Oct from 1800 to 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.
9. Way ahead. The September 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.
10. Release authorized by Lieutenant General George W. Smith Jr, Deputy Commandant, Plans, Policies and Operations.//