R 211745Z FEB 20
MARADMIN 097/20
MSGID/GENADMIN/CMC WASHINGTON DC PP&O//
Subj/FEBRUARY 2020 CHANGES TO DEFENSE READINESS REPORTING SYSTEM-MARINE CORPS//
Ref/a/MCO 3000.13a/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.//
POC/J.P. Brown/Col/POR/(703)571-1064//
POC/B.A. Hull/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 20 Feb 2020.
2.  DRRS-MC updates will include:
2.a. Consolidated Mission Essential Tasks (MET) assessment update.
2.b. Replace Military Occupational Specialty fill (MOSFL) with Critical Military Occupational Specialty (MOS).
3. Consolidated MET assessment update.
3.a. Background.  The mission and MET assessment pages will be updated so that more of the data is automatically imported from Authoritative Data Sources (ADS) to reduce user workload and improve data quality.  The changes will reduce subjectivity in the task and mission assessments, and allow for qualitative differences in training to be captured.  This update is in conjunction with updates to the Marine Corps Training Information Management System (MCTIMS).
3.a.1. The “resourced/trained/observed” checkboxes will be removed and “trained” and “cmd subjective assessment” columns will be added to the mission page.
3.a.2. The standards on the MET assessment page will be split into two sets, one for “baseline” and one for “advanced” standards.  Additional automation from MCTIMS will be used to populate the values for each standard.
3.b. The “baseline” and “advanced” met standards will add rows to the met assessment popup.  This will show the user the section heading of “baseline” and “advanced” tasks after the heading of either “baseline MET” or “advanced MET.”  There will be a dash and then the definition of that category for that MET, which will come from the MCTIMS feed.  The MCTIMS feed will be updated to distinguish whether a standard is a “baseline” (b) or “advanced” (a) category and will send the definitions for the categories specific to their METs.  Tasks with performance standards that do not have “baseline” or “advanced” categories will not show the row headings. 
3.c. The MET assessment page for each task will be updated with new columns and assessment fields.  This change will allow for more automation to reduce user workload.
3.c.1. The value column will be split into two columns, one labeled “auto” and one labeled “manual input.”  The “auto” column reflects values that have been automatically updated.  The “manual input” column will allow the user to provide data that has not been populated from an ads.  It will also allow the user to provide a different value than the automated data.
3.c.2. An “achieved” column will be added to show if the standard has accomplished the criterion.  The “achieved” column will be based on whether or not the value, “manual” or “auto,” has accomplished the criterion.  If the user has a value in the “manual” input, that value will override the value in the “auto” input.  If the standard has accomplished the criterion, a green checkbox will appear in the “achieved” column.  If the standard has not accomplished the criterion, a red “x” will appear in the “achieved” column.
3.c.3.  A new column will be added to allow for a commander’s override. This column will have a checkbox for each of the performance standards.
3.c.3.a. If the commander checks the box, then the performance will be seen as the opposite of what the “achieved” field shows.  Users will be prompted to enter information into the “task remark” justifying the override.
3.c.3.b. A column beside the calculated assessment will be added, with the heading “commander subjective assessment.”  The values in the “achieved” column will remain the same, but the commander’s override values will be used to update the “commander subjective assessment” value.  If the commander override is checked, and the user changes the “manual” input, the “commander override” checkbox will automatically be cleared.
3.d. The resourced/trained/observed checkboxes will be removed from the MET assessment popup.  The column heading for “task overall assessment” will be renamed to “calculated assessment.”  The “calculated assessment” value will now be based on the “achieved” column using the business rules below.
3.d.1. Standard rules for baseline and advance standards.
3.d.1.a. To be a Yes “Y,” all standards, baseline and advance, are achieved.
3.d.1.b. To be a Qualified Yes “Q,” all baseline standards must be achieved.
3.d.1.c. To be a no “n,” means baseline standards are not achieved.
3.d.1.d. To be considered met trained “trained,” all baseline training standards must be achieved, or if no training standards, all output standards are achieved.
3.d.2. Rules for METs without baseline and advance standards.
3.d.2.a. To be a Yes “Y,” all standards are achieved.
3.d.2.b. To be a Qualified Yes “Q,” all output standards achieved, any other standards not achieved.
3.d.2.c. To be a No “N,” any output standards not achieved.
3.d.2.d. To be considered met trained “trained”, all training standards achieved, or if no training standards, all output standards are achieved.
3.e. The trained value for T-level will be added as a column in the overall section for the task.  This will have a column heading of “trained” with “Y” or “N” green/red images as the value, the value determined by the rules in 3.d.1 and 3.d.2.  The trained value will be based on the “cmd overridden” values if there have been any overridden.  Justification must be provided in the “task remark” for any standards overridden.
3.f. Additional changes of note:
3.f.1. The Data Change Management (DCM) page will update if a value has been automatically populated through an ads.  If the user updates a resource page that affects the “auto” field within the mission/met page, the user will be prompted with the DCM page to show the update to the performance.
3.f.2. Currently, MARFOR units carry forward their mission and met data from the previous report.  The new fields, “manual input” and “commander override” will be carried forward with this effort.  Note: the first MARFOR report after the new release will not copy forward data.
3.f.3. Units are able to copy mission data to other missions if it is the same mission/task/performance combination, and there has been no data entered for the other mission for that mission/task/performance.
3.f.4. The mission assessment (YQN) value will be based on the MET assessment (YQN) “commander subjective assessment” values.  The commander subjective assessment will be shown for the task “YQN” on the main mission/MET page.  If users override the mission “YQN,” they will be prompted to enter justification into the “mission remark.”
4. Replace MOSFL with critical MOS.
4.a. Background. Currently, the P-level is calculated from the lower of the assigned strength or MOSFL.  This Engineering Change Proposal (ECP) will remove MOSFL and replace it with critical MOS.  The critical MOS allows for detailed tracking of either primary or billet MOS and captures the full duty status. The critical MOS list is not editable in DRRS-MC. It is listed by unit type for all core missions.  For assigned missions, the unit must select at least three critical mos.  The core mission lists are reviewed as part of the mission essential task list development process and are maintained in DRRS-MC.
4.b. The critical MOS percentage is currently calculated against the assigned strength and is not used to calculate the p-level.  A change from “assigned strength” to “deployable” will be part of the change that uses critical MOS to calculate the p-level.  The percentage will be total critical MOS deployable / total critical MOS structure.  There will be two business rules implemented with associated guidance.
4.b.1. Critical MOS is a billet identification code (BIC) fill - so the number assigned cannot exceed the structure.
4.b.2. A valid BIC fill must be qualified for the BMOS/PMOS and +/- 1 grade.
4.c. The system will provide the list of BICS and associated data from the table of organization, as a csv/spreadsheet on demand from the personnel page.
4.d. The P-level will be calculated for assigned strength and critical MOS, and the lowest P-level (not percentage) is selected as the overall P-level.  The personnel page shall highlight the factor that was used (assigned or critical MOS) for the overall P-level.  The personnel page will segregate the assigned strength input and the critical MOS input to facilitate phased implementation of automation. Each is calculated distinctly, so all personnel are entered into the assigned strength numbers.  Those with a critical MOS are also entered in the critical MOS input.
4.e. mosfl will be displayed on historical reports.
5. DRRS-MC will be updated on Thursday, 20 Feb from 1800 to 2200 Eastern Standard Time (EST).  Users will not be able to access DRRS-MC while the system is updating.  All in-progress reports will be deleted as part of the update.  Users are encouraged to complete any in progress reports prior to the update.
6. Way ahead.
6.a. The February 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.
6.b. Commanders and units are encouraged to provide additional recommendations to strengthen service readiness policy and improve the accuracy and reliability of readiness reporting.
7.  Release authorized by Lieutenant General George W. Smith, Jr. Deputy Commandant, Plans, Policies, and Operations.//