COMNAVAIRPAC/COMNAVAIRLANTINST...

COMNAVAIRPAC/COMNAVAIRLANTINST 3500.38 11 Feb 14

i

TABLE OF CONTENTS

Page No. Section 1 General Provisions 1.1 Purpose...........................................1-1 1.2 Policy............................................1-1 1.3 Chain of Command Responsibilities.................1-1 1.4 DRRS-N Account Management.........................1-3 1.5 Carrier Air Wing Readiness Reporting (CARR).......1-4 Section 2 Unit Reporting Requirements 2.1 Reporting Units...................................2-1 2.2 Minimum Data Submission...........................2-1 2.3 Frequency.........................................2-2 2.4 Unit Point of Contact.............................2-3 2.5 Classification of Data............................2-3 Section 3 Navy Mission Essential Task List (NMETL) Management 3.1 Overview..........................................3-1 3.2 NMETL Development Process.........................3-2 3.3 NMETL Change Process..............................3-2 3.4 NMETL Mapping to ROC/POE Warfare Areas............3-3 Section 4 Reporting Requirements 4.1 Assessment Rules..................................4-1 4.2 Assessment Projections............................4-3 4.3 Assessment Remarks................................4-3 4.4 Information Assurance (IA) Reporting by CVNs......4-4 4.5 Special Instructions for Detachment Reporting.....4-5 Section 5 Reporting Organization and Resource Status (OARS) Data for Squadrons 5.1 Overview..........................................5-1 5.2 C Rates Section...................................5-1 5.3 Unit Status Data..................................5-2


ii

Section 6 Reporting Organization and Resource Status (OARS) Data for Aircraft Carriers 6.1 Overview..........................................6-1 6.2 C Rates Section...................................6-1 6.3 Unit Status Data..................................6-2 6.4 Chemical-Biological Defense Section...............6-3 6.5 Personnel Strength (PERSTREN).....................6-5 Appendices Appendix A Personnel Metrics.................................A-1 Appendix B Equipment Metrics.................................B-1 Appendix C Supply Metrics....................................C-1 Appendix D Training Metrics..................................D-1 Appendix E Ordnance Metrics..................................E-1 Appendix F CNAF Authoritative Data Sources...................F-1 Appendix G RESPORG NMETL Review Checklist....................G-1


1-1

Section 1 General Provisions

1.1 Purpose. This instruction contains supplemental guidance and procedures for submission of DRRS-N assessments for organizations under the administrative control of COMNAVAIRPAC and COMNAVAIRLANT. It provides clarification of certain sections of references (a) through (c) and contains procedures for reporting unique information required by COMNAVAIRPAC/COMNAVAIRLANT. 1.2 Policy. This instruction shall be the only source for COMNAVAIRPAC/COMNAVAIRLANT DRRS-N supplemental reporting guidance. No other additional subordinate DRRS-N instructions are authorized. Change recommendations should be forwarded to COMNAVAIRPAC/COMNAVAIRLANT N40 through the appropriate chain of command. 1.3 Chain of Command Responsibilities. In addition to the responsibilities outlined in references (b) and (c), aviation commanders shall be responsible for the following: a. Type Commander shall: (1) Maintain oversight for the DRRS-N program for all COMNAVAIRPAC/COMNAVAIRLANT units. (2) Provide DRRS-N training to all COMNAVAIRPAC/ COMNAVAIRLANT and Commander, Naval Air Forces, Reserve (CNAFR) units. (3) Provide Mission Essential Task List (METL) development training to all Type Wings, as required. (4) Maintain oversight of the Personnel, Equipment, Supply, Training and Ordnance (PESTO) Pillar metrics and PESTO data integrity. (5) Conduct an annual review of all COMNAVAIRPAC/ COMNAVAIRLANT unit Navy Mission Essential Task Lists (NMETLs). (6) Provide aviation unit and CVN organizational and task group changes to U.S. Fleet Forces (USFF) to maintain the accuracy of COMNAVAIRPAC/COMNAVAIRLANT units reporting in DRRS-N.


1-2

(7) Maintain the COMNAVAIRPAC/COMNAVAIRLANT Supplemental DRRS-N Guidance. (8) As Cognizant Review Authority (CRA), review and maintain all COMNAVAIRPAC/COMNAVAIRLANT NMETLs. b. Lead Type Wing Commanders shall: (1) Develop and maintain the Navy Mission Essential Task List (NMETL) for units under their administrative control. Conduct NMETL reviews annually. (2) Forward draft NMETLs and NMETL changes to COMNAVAIRPAC/COMNAVAIRLANT N40 for review. (3) Maintain oversight for squadron skill to task mapping and conduct bi-monthly Personnel Figure of Merit (PFOM) calculations/export to DRRS-N for units under their administrative control. (4) Assign a primary and secondary Action Official to manage the skill to task assignments in the PFOM database. (5) Maintain the Mission Essential Subsystem Matrix (MESM) for units under their administrative control. c. Carrier Air Wing (CVW) Commanders shall: (1) Submit a monthly Carrier Air Wing Readiness Report (CARR) in DRRS-N as per paragraph 1.5 of this instruction. (2) Conduct DRRS-N assessments for the CVW staff per the requirements of this instruction. (3) Ensure that DRRS-N reporters within their command are fully trained and comply with DRRS-N reporting requirements. (4) Monitor the readiness assessments and Fleet Response Training Plan (FRTP) training for all squadrons and detachments under their operational control.


1-3

d. Aircraft Carrier Commanding Officers shall: (1) Conduct DRRS-N assessments for the ship only per the requirements of this instruction. (2) Ensure that DRRS-N reporters within their command are fully trained and comply with DRRS-N reporting requirements. (3) Provide COMNAVAIRPAC/COMNAVAIRLANT N7 with feedback on the CVN NMETL, as required. (4) Ensure accurate and timely inputs are made to DRRS-N authoritative data sources Fleet Training Manpower Planning Systems (FLTMPS), Maintenance Figure of Merit (MFOM), Aviation Maintenance Supply Readiness (AMSR), Class Maintenance Plan (CMP), Carrier-Sierra Hotel Aviation Readiness Program (CV-SHARP), and Ordnance Information System-Wholesale (OIS-W). (5) Provide DRRS-N Afloat accounts and related Information Technology (IT) support for embarked squadrons, detachments and staffs. e. Squadron Commanding Officers shall: (1) Conduct DRRS-N assessments for their unit per the requirements of this instruction. (2) Ensure that DRRS-N reporters within their command are fully trained and comply with DRRS-N reporting requirements. (3) Provide the lead Type Wing with feedback on squadron NMETLs and community Training and Readiness (T&R) matrices. (4) Ensure accurate and timely inputs are made to DRRS-N authoritative data sources (FLTMPS, AMSRR and SHARP). 1.4 DRRS-N Account Management a. Overview: All units reporting in DRRS-N are required to obtain individual accounts either in the DRRS-N Ashore or DRRS-N Afloat programs. Since DRRS-N is a classified web-based application, users are required to possess a valid SECRET clearance and possess a Secret Internet Protocol Router Network (SIPRNET) account. In the case of DRRS-N Ashore, users are also required to possess a SIPRNET email account. DRRS-N Ashore accounts are managed by USFF and DRRS-N Afloat accounts are


1-4

managed by the ship on which the DRRS-N Afloat program resides. The Commanding Officer, Executive Officer, Detachment OIC (when applicable) and Operations Officer for each unit shall possess “Unit Commander” (Ashore) or “Releaser” (Afloat) permissions to draft and submit DRRS-N assessments. Commanding Officers may authorize other personnel in their command to possess “Unit Commander/Releaser” permissions with COMNAVAIRPAC/COMNAVAIRLANT N40 notification. All other account types are at the discretion of the Commanding Officer. DRRS-N account permissions are described below. In addition to the stated permissions, accounts also inherit all the permissions of the next lowest account type. (1) Unit Commander/Releaser: Allows the user to draft and submit DRRS-N assessments for the unit which he/she is assigned. (2) Unit User/Drafter: Allows the user to draft DRRS-N assessments for the unit to which he/she is assigned. (3) View Only/Browser: Allows the user to view approved assessments for any unit in DRRS-N. (4) Unit Admin: Allows the user to manage roles and create accounts within their unit (DRRS-N Afloat only) b. DRRS-N Ashore. Users can request DRRS-N Ashore accounts directly from the DRRS-N homepage (SIPRNET) at: https://drrsn. ffc.navy.smil.mil/drrsn. c. DRRS-N Afloat. Users shall contact the Operations (OPS) Admin Officer (for CVNs) or the ship’s Operations Department (all other ships) to coordinate requests for DRRS-N Afloat accounts. The DRRS-N Afloat account is a separate account from the DRRS-N Ashore account and only exists on the ship’s network. Draft assessments made on DRRS-N Afloat cannot be viewed or edited by DRRS-N Ashore users. 1.5 Carrier Air Wing Readiness Reporting (CARR) Policy a. Overview. The CARR is a communication tool that allows the Carrier Air Group (CAG) to describe overall warfighting capability and highlight readiness degradations within their CVW. This tool is used by the Type Commander to make resourcing decisions and understand total wartime capability. The CARR is a group view within DRRS-N which rolls up the DRRS-N assessments

https://drrsn.ffc.navy.smil.mil/drrsn

https://drrsn.ffc.navy.smil.mil/drrsn


1-5

and PESTO data for each squadron within that CVW. Squadron approved DRRS-N assessments will be visible to the CAG via drill downs on each Capability Area. b. CARR Assessment. The CAG can view the squadron rollup and shall assess each Capability Area and the Core assessment based on the DRRS-N assessment guidelines. This assessment is based on the capabilities of the CVW as a whole and does not take into account all the capabilities of the CAG in the role of Strike Warfare Commander. c. CARR Comments. The CAG’s comments shall be contained in the Core assessment block. The CAG’s remarks should concentrate on: (1) The CVW’s ability to conduct Major Combatant Operations (MCO) level of wartime missions. (2) The CVW’s ability to execute currently assigned missions such as FRTP training and contingency operations. (3) Any training or readiness issues that require TYCOM attention. d. Reporting Frequency. The CARR shall be updated upon completion of major readiness milestones (Tailored Ship’s Training Availability (TSTA), Advanced Readiness Program (ARP), Air Wing Fallon, C2X etc), when readiness changes in one or more squadrons affect the CVW’s overall warfighting capability, and no more than 30 days from the previous CARR assessment. The CARR is updated continuously regardless of the CVW’s phase in the FRTP.


2-1

Section 2 Unit Reporting Requirements

2.1 Reporting Units. To report in DRRS-N, a unit must possess a Unit Identification Code (UIC) that is registered in the Global Force Management (GFM) database and an NMETL associated with a Responsible Organization (RESPORG) in the Navy Training Information Management System (NTIMS) database. The following COMNAVAIRPAC/COMNAVAIRLANT units shall report assessments in DRRS-N. a. Aircraft Carriers. b. Carrier Airwing Staffs (CARR Only). c. Squadrons (Active and Reserve Component). d. Detachments (Active and Reserve Component). e. Fleet Replacement Squadrons. f. Commands that provide direct operational support (Fleet Readiness Center (FRC), Weapons Schools, Type Wings, etc). Note: Any unit listed above that does not have an NMETL registered in the Navy Training Information Management System (NTIMS) database shall not be required to report in DRRS-N until the NMETL and supporting PESTO metrics have been developed and approved. 2.2 Minimum Data Submission. COMNAVAIRPAC/COMNAVAIRLANT units shall review and update DRRS-N Core, Capability Area and Mission Essential Task (MET) commander assessments each time that a DRRS-N assessment is required as per paragraph 2.3. All units shall provide comments in the Core assessment blocks. These comments should focus on the unit’s ability to meet Major Combat Operations (MCO) mission requirements, ability to conduct its current mission, any external assistance required to meet mission requirements and expected future readiness milestones. All units shall provide amplifying comments for all “No” and “Qualified Yes” assessments or when the computed score is less than 80, in the Capability Areas assessment blocks. These comments should focus on the reason why the unit is not able to fully execute the NMETs associated with that Capability Area, when the unit will be able to execute the NMETs and what resources are required (if any) to fully execute the NMETs. See


2-2

Section 4.3 for more details on the Commander’s remarks. All COMNAVAIRPAC/COMNAVAIRLANT units shall review and update the Organization and Resources Status (OARS) data for accuracy and completeness each time a DRRS-N assessment is completed. The OARS page is described in sections 5 (squadrons) and 6 (CVN). 2.3 Frequency. A unit assessment must be submitted in DRRS-N under the following conditions: a. Within 24 hours of a significant change in readiness. However, if the readiness change is transitory (i.e., less than 24 hours due to material condition which may temporarily degrade operational effectiveness, but is on track to be corrected), a DRRS-N update is not required. Unit Commander judgment is a key enabler here. A significant change in readiness is defined as a change in any Capability Area (Yes, Qualified Yes, and No) assessment from the previously reported assessment as determined by the Unit Commander (e.g. commander’s assessment). Changes in PESTO data may occur daily or monthly and do not necessarily constitute a requirement for submitting a new readiness assessment. The determination of the need to submit an assessment resides with the Unit Commander. b. Upon unit commissioning or establishment. c. Prior to decommissioning or disestablishment. d. Upon turnover of rotational detachment crews and personnel. e. Within 24 hours of an unplanned change in underway or deployment status (e.g., fail to sail, hurricane sortie, Defense Secretary Operation Agency (DSCA) mission, surge deployment, RTP for emergent repairs). f. When directed by Immediate Superior in Command (ISIC). g. Following completion of major FRTP milestones to include Ship Helicopter Integration Program, ARP, TSTA, Air Wing Fallon and C2X. Units are not required to update DRRS-N assessments upon commencing major FRTP milestones unless one of the other requirements set forth in paragraph 2.3 is met. h. Upon reaching a milestone or get-well date as described in the unit commander’s comments.


2-3

i. When an equipment casualty results in transmission of a C3/C4 Casualty Reporting (CASREP) or after the restoration of a C3/C4 equipment casualty, the unit shall evaluate the need for a DRRS-N update, ensuring compliance with paragraph 4.1. At a minimum, the unit shall address the impact of any C3/C4 CASREPS in the remarks sections of the Core assessment block even if the CASREP does not change the Commander’s assessment. Ensure affected Navy Mission Essential Tasks (NMETS)/capabilities are updated. j. An updated unit assessment shall be submitted within 30 calendar days of the previous assessment even if there is no change in readiness.

2.4 Unit Point of Contact (POC). Currently DRRS-N does not contain a data field to enter a unit POC. Therefore, all COMNAVAIRPAC/COMNAVAIRLANT units shall include the unit POC rank, name, Defense Switched Number (DSN) telephone number and Non-classified Internet Protocol Router Network (NIPRNET) email address (Secret Internet Protocol Router Network (SIPRNET) email if available) at the bottom of the overall remarks section of the Core commanders assessment block. 2.5 Classification of Data. All data displayed in DRRS-N is classified SECRET and shall be handled accordingly.


3-1

Section 3 Navy Mission Essential Task List (NMETL) Management

3.1 Overview. DRRS-N facilitates reporting the readiness of Navy forces and the supporting infrastructure to accomplish assigned missions through the construct of Navy Mission Essential Tasks (NMETs). A NMET is a task that is necessary, indispensable, or critical to the success of a unit’s mission. An NMET includes the specific conditions and standards for successful task contribution to mission accomplishment. The list of Navy tasks is found in reference (c), Universal Naval Task List (UNTL). The UNTL is a single source document that combines the Navy Tactical Task List (NTTL) and the Marine Corps Task List (MCTL). The UNTL provides a common language that Commanders can use to document their warfighting requirements as METs. Conditions describe environmental variables that may affect task performance. They are linked to a task and may impact a unit’s ability to perform that task. They contain descriptors to refine the condition. The UNTL contains 343 conditions in three environmental categories: physical, military and civil. When linked to tasks, conditions help frame the differences or similarities between assigned missions. The Joint community and all services choose conditions from the UNTL. The relevant conditions are unique to each community or unit. Standards are composed of measures and criteria. A standard provides a way for the Commander to express the degree to which an organization or force must perform a task under the specified set of conditions. Standards set minimum performance expectations and provide a basis for assessment. A NMETL is a listing of NMETs that a command must complete in order to meet its mission or provide the selected capability. The assessment of NMETs is the foundation of capabilities-based reporting and the standardized reporting scheme directed for use by all services and Department of Defense (DoD) agencies. 3.2 NMETL Development Process. Each Lead Type Wing is responsible for developing, managing and updating the NMETL for each community under their administrative control. The key


3-2

steps in the NMETL development process include a comprehensive review of the community Required Operational Capabilities (ROC) Projected Operational Environment (POE) and tactical doctrine to capture the Navy Core Competencies. The next step is to cross reference the UNTL and develop an NMETL for its Responsible Organizations (RESPORGs) (e.g., VFA, VAQ EXP, HSC CVW). A RESPORG is the organization with the overall responsibility for executing the NMETL. Once the NMETL is drafted, the final step is to develop conditions and standards for each MET. Once reviewed by both Commodores (in the case of East and West coast Type Wings), the Lead Type Wing shall forward the draft NMETL or NMETL change request via SIPRNET to the COMNAVAIRPAC Aviation NMETL Manager for review. The TYCOM is the Cognizant Review Authority (CRA) for all aviation and aircraft carrier NMETLs. The TYCOM must ensure that draft and lower echelon NMETLs support higher echelon NMETLs. COMNAVAIRPAC N40 (Wings/squadrons) or COMNAVAIRPAC N7 (CVN) shall conduct an annual NMETL review and emergent reviews as required. When necessary and to ensure Navy-wide standardization, COMNAVAIRPAC/COMNAVAIRLANT will also convene working groups to address specific deficiencies or inconsistencies among NMETL tasks, conditions and standards. COMNAVAIRPAC/COMNAVAIRLANT will coordinate with commands that are developing performance metrics/performance standards to ensure that all measures are contained in an approved NMETL and reside in Navy Training Information Management Systems (NTIMS). COMNAVAIRPAC/COMNAVAIRLANT will also submit completion reports to USFF N7 no later than 1 December of each calendar year. 3.3 NMETL Change Process a. Type Wings and CVNs can recommend changes to NMETLs at any time. b. When conducting NMETL reviews and submitting changes to COMNAVAIRPAC/COMNAVAIRLANT, Type Wings shall follow Appendix G, RESPORG NMET Review Checklist. All squadron NMETL change requests shall be forwarded via SIPRNET to COMNAVAIRPAC/ COMNAVAIRLANT N40. All CVN NMETL change requests shall be forwarded via SIPRNET to COMNAVAIRPAC/COMNAVAIRLANT N71. c. After COMNAVAIRPAC/COMNAVAIRLANT conducts its review, NMETL change requests shall be forwarded via SIPRNET to USFF. USFF is the Primary Review Authority (PRA) and is responsible for final NMETL approval.


3-3

d. USFF publishes the approved NMETLs in NTIMS. Any NTIMS user can view the NMETL in NTIMS, but only the CRA can make changes. e. NTIMS pushes all approved NMETLs and modified NMETLs to DRRS-N. DRRS-N users can view NMETLs and assess MET readiness. 3.4 NMETL mapping to ROC/POE Warfare Areas (squadrons only). The community ROC/POE is still the definitive resource document that dictates the requirements for each community. The ROC/POE also dictates the Primary Warfare Areas each community is resourced to perform under MCO standards. When mapping tasks to DRRS-N Capability Areas within the NMETL, Type Wings shall only map tasks to those Capability Areas that match the Primary Mission Areas contained in the approved ROC/POE. When a draft ROC/POE is under review at the TYCOM or higher, the Type Wing may use the draft ROC/POE as a basis for developing or updating their NMETL. In all cases, COMNAVAIRPAC/COMNAVAIRLANT N40 shall make the final determination on which Capability Areas shall be mapped to the community NMETL and forwarded to USFF for approval. a. To minimize the redundancy of METs mapped across multiple Capability Areas, the following Navy Tactical Tasks (NTT) shall be mapped only to the MOB Capability Area: (1) NTA 1.1.2.3 Move Units (2) NTA 1.1.2.3.3 Conduct Flight Operations (3) NTA 1.1.2.3.3.2 Launch Aircraft (4) NTA 1.1.2.3.3.3 Recover Aircraft (5) NTA 4.2.1.2 Conduct Aerial Refueling (6) NTA 4.3.2.1 Perform Preventative Maintenance (7) NTA 4.3.2.2 Diagnose and Repair (8) NTA 4.3.2.3 Perform Quality Assurance (QA) (9) NTA 4.8.5 Maintain Cultural Awareness


4-1

Section 4 Reporting Requirements

4.1 Assessment Rules. DRRS-N contains four assessment types (Core, Capability Area, MET, and OARS). Each unit is responsible for assessing all four types each time a DRRS-N assessment is completed. Reference (a) defines the assessment values (Yes, Qualified Yes, and No) and provides guidance on how to apply them to MET, Capability Area and the Core assessments. a. Core Assessment. The Core assessment is the unit Commander’s qualitative assessment of the unit’s overall ability to execute its designed MCO mission(s). It should be consistent with the majority of the Commander’s Capability Area assessed values. Use the following rules when making Core assessments. (1) Core assessment shall not be green if either MOB or CCC Capabilities are assessed less than green. (2) (CVN Only) The commander’s assessment shall not be green in MOB and Core if an engineering casualty exists that limits speed or maneuverability. (3) (CVN Only) The overall MOB Capability Area shall be assessed as no better than the worst assessment of any individual MOB Capability Area (e.g., MOB is assessed yellow if MOB-S is green, MOB-N is green, MOB-D is green, And MOB-E is yellow). (4) (CVN Only) The commander’s assessment shall not be green in MOB and Core if onboard fuel percentage or days of provisions are less than prescribed by Fleet or Operational Commanders (as defined in Fleet or TYCOM guidance). (5) (CVN Only) The commander’s assessment shall not be green in any NMET or Capability Area affected by an active CAT 3 or CAT 4 CASREP. (6) The commander’s assessment shall not be green for any Capability Area if unit fails to complete the full training requirement for any phase of the FRTP or fails to achieve required certification for any phase of the FRTP. (7) (CVN Only) The commander’s assessment shall not be green for any NMET or Capability Area where shipboard ordnance


4-2

load is less than 80 percent of Ship Fill or other requirements directed by Echelon Two Fleet Commanders. Note: In cases where a unit is degraded purely by a MOB issue (unable to get underway due to an engineering casualty or more than 50 percent of aircraft NMC), the unit is expected to degrade the MOB Capability Area and the Core only. Degrading several or all Capability Areas for a mobility issue only disguises the real degradation and makes it harder for leadership to determine the critical readiness degraders for a unit. b. Capability Area and NMET Assessments. DRRS-N assessments shall be based on the Major Combat Operations (MCO) standard and not on the FRTP phase standards. The FRTP standards are designed to incrementally prepare a unit for its full wartime readiness. During an FRTP cycle, the expectations of readiness increase progressively from “No” (Red) in the maintenance phase to “Yes” (Green) at the beginning of a unit’s employability window. Units should strive to maintain a “Yes” (Green) throughout their employability window unless their mission forces a degradation in certain Capability Areas (single mission focus, non-wartime tasking, etc.). Certain Capability Areas however, may be assessed as “Yes” (Green) sooner than the employability window if the unit commander is certain that the unit can perform that capability to wartime standards. Note: Currently MOB is the only Capability Area that is intended to be green in all pillars or assessed as “Yes” prior to the employability phase. “Qualified Yes” (Yellow) assessments shall be made by a Unit Commander when he/she determines that the unit can perform the NMET or Capability Area under most conditions and can meet most standards. For most units, this should be on entry into the Integrated Phase. A “Qualified Yes” (Yellow) infers a unit is eligible/capable for special missions tasking by higher authority, but additional risk is assumed unless extra resources and training are provided. “Qualified Yes” may also be used as an indicator by the Unit Commander if a decrease in resources reduces readiness below full wartime standards. 4.2 Assessment Projections. Assessment projections should be based on any of the following conditions: a. Any significant change in assessed values.


4-3

b. Completion of the next FRTP milestone. c. When a projection date needs to be extended, corrected, or adjusted. 4.3 Assessment Remarks. Comments shall be concentrated in the Core assessment (also referred to as the Overall Commander’s assessment) block. Each assessment block allows the user to make Overall and PESTO comments in separate sections. The Overall comment section should be used by the Unit Commander to describe the unit’s ability to conduct wartime missions (MCO standard), ability to meet the current mission, resources required to achieve desired readiness and any operational impacts. Core assessment shall contain the following information. a. Current Fleet Response Training Plan (FRTP) month (Maintenance, Basic, or R+xx). b. The next major FRTP milestone (ARP, TSTA, CERTEX, C2X, etc). c. The expected deployment date. d. The Commander’s top readiness concerns. Individual PESTO comment blocks in the Core assessment should be utilized to highlight the major readiness impediments associated with that pillar. If the Core comments require supplemental remarks, then additional comments shall be made in the Capability Area assessment blocks when they are assessed as a “No” or “Qualified Yes”. Comments in the Capability Area should focus on a unit’s ability/deficiency in performing the NMETs under that Capability Area. Emphasize resourcing barriers and provide mitigation actions and/or timelines. Note: Comments should focus on readiness and resourcing concerns and should address any risks associated with tasking the unit at its current readiness state. Software, hardware and data accuracy problems should be directed to COMNAVAIRPAC/ COMNAVAIRLANT N40 via separate means. All comments should be written in sentence case. Capitalization shall be reserved for acronyms and to emphasize critical areas. We must fully understand and clearly articulate our operational and combat readiness to execute assigned missions and report appropriately


4-4

- no exceptions or surprises. While it may be admirable to maintain a "can do" attitude (i.e., I can still execute the mission with major equipment degradation), it is not desired, as it could jeopardize the Navy's ability to meet national tasking. Every unit must ensure that information in their readiness reports and databases such as DRRS-N is accurate, and clearly reflects their readiness to execute both current and future missions. Above all, ensure the DRRS-N commander's assessment is accurate, concise, timely and honest. 4.4 Information Assurance Reporting by CVNs. Since all CVNs report NTA 5.5.5 (provide Information Assurance), they are required to report specific data in the NTA remarks section and have some guidance on how to report the NTA commander’s Assessment. This section outlines how a CVN shall report NTA 5.5.5. a. The remarks block for NTA 5.5.5 shall report the standardized remarks required by USFF. This data is designed to be mined by USFF which requires that the units use the remarks template provided by USFF. The remarks template can be downloaded on the SIRPNET at http://www.fleetforces.navy. smil.mil/cyberfor/n4/default.aspx. b. The Commander’s Assessment for NTA 5.5.5 shall be per the following rule sets. (1) If the command’s site accreditation has expired, NTA 5.5.5 assessment can be no higher than red and an explanation is required. If the commander’s site reaccreditation has not started or is within 90 days of expiration; NTA 5.5.5 cannot be higher than yellow. (2) Latest Information Assurance Vulnerability Alert (IAVA) scan (either NIPRNET or SIPRNET) is greater than 30 days old, an explanation is required and the NTA 5.5.5. assessment cannot be higher than yellow.

(3) Percent of available patches fully applied (either NIPRNET or SIPRNET) is less than 90 percent: NTA 5.5.5 assessment cannot be higher than yellow.

(4) Percent of available patches fully applied (either NIPRNET or SIPRNET) is less than 70 percent: NTA 5.5.5 assessment cannot be higher than red.

http://www.fleetforces.navy.smil.mil/cyberfor/n4/default.aspx

http://www.fleetforces.navy.smil.mil/cyberfor/n4/default.aspx


4-5

c. The Unit Commander is not required to change the CCC Capability Area assessment (Y/Q/N) based on the NTA 5.5.5 assessment. However, commander’s remarks are required in the CCC Capability Area whenever NTA 5.5.5 is assessed as yellow or red. 4.5 Special Instructions for Detachment Reporting. For the purposes of readiness reporting, a detachment is defined as a unit identified in the DRRS-N database that deploys to a ship or land base without the parent command (PARCOM) structure (PARCOM remains at the designated homeport location). Detachments will be identified in DRRS-N with a CNO assigned UIC. This UIC normally has an NA or NB as the first two digits. The following detachment types meet the requirement for detachment DRRS-N reporting: a. VRC/C-2 detachments. b. HSC/MH-60S/HH-60H expeditionary detachments. c. HSM/MH-60R expeditionary detachments. d. HSL/SH-60B detachments. e. HM/MH-53E detachments. f. MQ-8 series VTUAV detachments. g. Other expeditionary or interim detachments as defined by COMNAVAIRPAC/COMNAVAIRLANT N40. Parent commands of detachment based squadrons will only see the “P” Pillar. The “P” Pillar shall be based on the entire squadron manning document (including both sea and shore UICs). Parent commands are required to report in DRRS-N at least every 30 days and provide comments on the ability of the squadron to source detachments. Detachments shall only maintain and display an “E” and “T” pillar in DRRS-N. Parent commands are responsible for detachment manning. Any personnel shortages shall be highlighted in the Parent command DRRS-N assessment. Detachment based squadrons shall conduct continuous Aviation Maintenance and Supply Readiness Reporting (AMSRR) reporting to support the detachment Equipment Pillar in DRRS-N. This means that in a detachment based squadron, aircraft shall be continuously assigned to detachments and reported as such in the AMSRR. A description of the “E” Pillar is contained in Appendix B. HSC (EXP) detachments may be required to train to tailored Capabilities based on specific deployment requirements. Capability Areas in DRRS-N that are not listed below should be assessed as RED with an associated comment that states the


4-6

detachment does not train to the Capability Area in their current assignment. The Capability Areas required by each T&R matrix along with the associated PMA Crew Requirements are shown in the below table:

HSC Detachment T&R Matrix

PMA Crew Requirement(s) Required Capability Areas

Non-Armed Helo SOF MOB, LOG, FSO, MOS, NCO, CCC, NSW Armed Helo SOF/ASU MOB, LOG, FSO, MOS, NCO, CCC, NSW,

STW, ASU CLF/HADR SOF MOB, LOG, FSO, MOS, NCO, CCC NAPLES SOF MOB, LOG, FSO, MOS, NCO, CCC, NSW


5-1

Section 5 Reporting Organization and Resource Status (OARS) Data for

Squadrons

5.1 Overview. The Organization and Resource Status (OARS) data allows the unit to report legacy readiness data sets required by Joint Staff through the DRRS-N application. This section contains the rule sets for completing the OARS data section in DRRS-N. OARS data is only visible to users who have a DRRS-N account with permissions to view or edit a draft report in a given unit. When a unit submits a DRRS-N assessment, the OARS data is updated at the DRRS-N server which, in turn, generates this legacy data for processing up line to Joint Staff. The DRRS-N generated OARS data is not transmitted via the Naval Message System and is only visible via the Navy Readiness Reporting Enterprise Business Intelligence Tool in DRRS-N Ashore. 5.2 C Rates Section. This section is manually filled in. The C Rates for each resource area shall be consistent with the unit’s DRRS-N commander assessments. Units may refer to the automated PESTO data to determine where resource areas are degraded, but it is important to note that it is the DRRS-N commander’s assessment that drives the legacy C Rates. Only use C1 in cases where the unit is resourced at 100 percent of the TYCOM MCO (deployed) requirement.


5-2

a. The Ordnance C Rate is not used by squadrons/ detachments and shall be reported as Not Applicable (N/A). b. The Supply C Rate is still required in the OARS data even though squadrons do not have a Supply Pillar in DRRS-N. Since the Supply C Rate is based on the number of in reporting aircraft vs Primary Aircraft Authorized (PAA), units should refer to the Flight line standard in the Equipment Pillar drill down to assist in determining the Supply C Rate. c. Reporting C Rates for squadrons in transition and Fleet Replacement Squadrons. These two scenarios meet the requirements for C5 reporting. To enable the C5 function in the OARS data, the unit shall first select the category 16 Activity Code Fleet Replacement Training (FRPTNG) which will display C5 in the Overall C Rate block. (1) All Fleet Replacement Squadrons shall enable the C5 overall function on every assessment. Use the Category 16 Activity code “FRPTNG”. (2) Deployable squadrons must be directed to enable the C5 function by COMNAVAIRPAC/COMNAVAIRLANT N40. Normally this is directed when the squadron has transferred all legacy aircraft and is ready to begin the FRS phase of the transition. Once the squadron has been designated Safe for Flight by their Type Wing and has stood up the second shift for maintenance, they shall no longer report C5 in the overall C Rate. This is enabled by selecting any Category of Activity Code that is not labeled as a C5 code. C5 ACTIV codes are displayed in red in DRRS-N. 5.3 Unit Status Data a. Activity Category. Use the pull down menu to select the Activity Code Category that best describes your current employment. Normally squadrons will select codes from Category 16 (Air Training) or Category 20 (Operations). During the entire deployment, units shall report the ACTIV code “Deploy” under Category 27 OTHER. b. Activity Code. Select the Activity Code from the categories mentioned above that best describes your current employment. c. Deployment Status. Select the appropriate deployment status from the pull down menu.


5-3

d. Embarked. When embarked, report the UIC of the ship on which your squadron or detachment is embarked. Leave blank when not embarked. CVN UICs are provided below. Surface or MSC ship UICs can be obtained from the ship’s Operations or Administrative Department or by searching for the unit in by name DRRS-N. UICs must be entered as displayed below. e. Category Level and Limitation. Report N/A for all COMNAVAIRPAC/COMNAVAIRLANT units. f. Percent Effective (PCTEF). PCTEF is the appropriate way for a Unit Commander to express readiness as it applies to the currently assigned mission (e.g., if your assigned mission is completion of FRTP phase training, you are assigned to a named exercise or you are engaged in a limited employment (Disaster Relief, etc). Use PCTEF to assess unit readiness to complete that mission, not the high-end MCO mission. Unit commanders shall update DRRS-N when a change to primary assigned mission occurs (e.g., ASW to Counter-piracy). Report a number from 1-4 in PCTEF using following criteria: (1) Unit possesses the required resources, is trained, and is in position or has the necessary mobility to undertake the mission it has currently been assigned. (2) Unit possesses the resources, is trained, and is in position or has the necessary mobility to undertake most of the mission it has currently been assigned. (3) Unit possesses the resources, is trained, and is in position or has the necessary mobility to undertake many portions, but not all; of the mission it has currently been assigned. (4) Unit requires additional resources and/or training or needs mobility assistance to undertake the mission it has currently been assigned.

SHIP UIC SHIP UIC CVN 69 EISENHOWER N03369 CVN 68 NIMITZ N03368 CVN 71 ROOSEVELT N21247 CVN 70 VINSON N20993 CVN 75 TRUMAN N21853 CVN 72 LINCOLN N21297 CVN 77 BUSH N23170 CVN 73 WASHINGTON N21412 CVN 74 STENNIS N21847 CVN 76 REAGAN N22178


5-4

g. Percent Effective (PCTEF) Remark. The remarks should briefly describe the currently assigned mission and articulate the reason why the unit selected the given PCTEF number. h. Unit Location (Latitude (LAT)/Longitude (LONG)). Enter LAT/LONG of your squadron’s homeport location when the unit is not embarked. Format is Deg, Min, and Direction (e.g. 37.00N 076.00W). See the table below for the LAT/LONG for homeports and duty stations of COMNAVAIRPAC/COMNAVAIRLANT units. Leave this field blank when the unit is embarked.

i. Chemical-Biological Defense Section (1) Chem-bio Defense Overview. Units must provide an overall assessment of their CBD Equipment/Supply status based on their possessed requirement as outlined in the appropriate Allowance Equipage List (AEL) or Table of Allowance (TOA). The CBD Equipment/Supplies status rating represents an independent assessment and shall not be factored into or related to the Equipment/Supplies on hand C Rate or CHEM-BIO C Rate. The specific type and quantity of CBD Equipment/Supplies that particular units/platforms are required to possess is stipulated in Equipment/Supplies allowance lists, as well as other appropriate OPNAV, Navy Component Commander, or TYCOM documents. CBD Equipment/Supply is limited to CBD personnel protective equipment only (suits, gas masks, gloves, boots etc). Aircrew related CBD equipment shall not be considered in the unit’s assessment. (2) Current Rate/Reason. The overall value is automatically calculated from the Equipment/Supply and Training C rates. The Overall Reason Code is a three digit letter code

Location LAT LONG Location LAT LONG NAS Oceana 36.29N 076.01W NAS Ventura County 34.07N 119.07W NS Norfolk 36.56N 076.17W NAS Fallon 39.25N 118.42W NAS Jacksonville 30.14N 081.40W NAS Whidbey Island 41.21N 122.39W NS Mayport 30.23N 081.25W NAS Lemoore 36.20N 119.57W NAS Key West 24.34N 081.41W NAS North Island 32.42N 117.13W JRB McGuire NJ 40.00N 074.35W NAF China Lake 35.41N 117.41W JRB New Orleans 29.49N 090.02W JRB FT Worth 32.46N 097.26W NAF Washington DC 38.48N 076.52W Tinker AFB, OK 35.24N 097.23W NAS Patuxent River 38.17N 076.24W MCAS Kaneohe Bay 21.27N 157.46W NAF Naples, Italy 40.53N 014.17E NAF Atsugi Japan 55.27N 139.27E Bahrain (airport) 26.16N 050.38E


5-5

that describes the degradation. The Overall Reason Code field automatically adopts the worst of the Supply and Training Reason Codes. (3) Supply Rate. Report C1-C4 per the CBD Supply/Equipment table below.

Does the unit possess an AEL/TOA for CBD equipment?

Has the unit been issued CBD equipment?

Supply C Rate

Yes No C4 Yes C1-C4

No No C4 Yes C4

(4) Supply Reason. Report the three letter code YZZ for all cases. (5) Training Rate. Report C1-C4 per the CBD training table below

Does the unit possess a TYCOM CBD Training

Matrix?

Has the unit been trained on CBD

equipment?

Training C Rate

Yes No C4 Yes C1-C4

No No C4 Yes C4

(6) Training Reason Code. Report the three letter code ZZZ for all cases. Note: CHEM-BIO Reason Codes can be found in Chapter 3 of Reference (a). j. Personnel Strength (PERSTREN) (1) Type. Report NC (Officers) and NE (Enlisted) as applicable. Add a new PERSTREN set for each personnel type. Reserve squadrons report Full Time Support (FTS) under the NC or NE type and Selected Reservist (SELRES) under the RC (Officers) or RE (Enlisted) type.


5-6

(2) Structured Billets Authorized (BA). Report BA from your Activity Manning Document (AMD) or Enlisted Distribution Verification Report (EDVR). (3) Authorized (BA). Report BA from your Activity Manning Document (AMD) or Enlisted Distribution Verification Report (EDVR). (4) Assigned Navy Manning Plan (NMP). Report the NMP number by personnel type as per the AMD or EDVR. (5) Possessed Current on Board (COB). Report the number of personnel in that type that are COB. Note: Detachments shall only report the Type and Possessed fields. All other fields shall be zeros. Numbers in the PERSTREN fields are not auto populated from DRRS-N and must be entered manually by the unit.


6-1

Section 6 Reporting Organization and Resource Status (OARS) Data for

Aircraft Carriers

6.1 Overview. The Organization and Resource Status (OARS) data allows the unit to report legacy readiness data sets required by Joint Staff through the DRRS-N application. This section contains the rule sets for completing the OARS data section in DRRS-N. OARS data is only visible to users who have a DRRS-N account with permissions to view or edit a draft report in a given unit. When a unit submits a DRRS-N assessment, the OARS data is updated at the DRRS-N server which, in turn, generates this legacy data for processing up line to Joint Staff. The DRRS-N generated OARS data is not transmitted via the Naval Message System and is only visible via the Navy Readiness Reporting Enterprise Business Intelligence Tool in DRRS-N Ashore. 6.2 C Rates Section. This section is manually filled in. The C Rates for each resource area shall be consistent with the unit’s DRRS-N commander assessments. Units may refer to the automated PESTO data to determine where resource areas are degraded, but it is important to note that it is the DRRS-N commander’s assessment that drives the legacy C Rates. Only use C1 in cases where the unit is resourced at 100 percent of the TYCOM MCO (deployed) requirement.


6-2

a. Reporting C Rates for Ships in Maintenance. Ships in maintenance availability normally report C5. The extent to which they report C5 is determined by the type of availability. The C5 function in the OARS section is enabled by selecting the corresponding Activity Code. Activity Categories 1-3 include the codes for the various ship maintenance availabilities. Category 1 and 2 codes are for dry dock and longer term maintenance and Category 3 is for post maintenance activities such as Sea Trials. Once the ship has completed the maintenance availability, the unit is no longer required to report C5. This is enabled by selecting any Category of Activity Code that is not labeled as a C5 code. 6.3 Unit Status Data a. Activity Category. Use the pull down menu to select the Activity Code Category that best describes your current employment. b. Activity Code. Select the Activity Code from the categories mentioned above that best describes your current employment. During the entire deployment, units shall report the ACTIV Code “Deploy”.

Note: Units that are in overhaul shall select Category 1, 2, or 3 Activity Codes. This will display C5 as the Overall C Rate and depending on the Category selected, C5 in the resources section. c. Latitude (LAT)/Longitude (LONG) (Unit location). Enter LAT/LONG of your ship’s homeport location or shipyard when the unit is at home. Report the approximate ocean location when the ship is at sea. Format is Deg, Min and Direction (e.g. 37.00N 076.00W). See the table below for the LAT/LONG for homeports.

Homeport Locations LAT LONG Norfolk, VA 36.57N 076.19W Newport News VA 36.59N 076.26W Norfolk Naval Shipyard, VA 36.49N 076.17W San Diego, CA 32.42N 117.11W Bremerton, WA 47.33N 122.39W Everett, WA 47.59N 122.13W Yokosuka Japan 35.17N 139.40E


6-3

d. Deployment Status. Select the appropriate deployment Status from the pull down menu. e. Embarked. This field in not used by Aircraft Carriers and shall remain blank. f. Category Level and Limitation. Not required, report N/A. g. Percent Effective(PCTEF). PCTEF is the appropriate way for a Unit Commander to express readiness as it applies to the currently assigned mission (e.g., if your assigned mission is completion of FRTP phase training, you are assigned to a named exercise, or you are engaged in a limited employment (Disaster Relief, etc), use PCTEF to assess unit readiness to complete that mission, not the high-end MCO mission). Unit Commanders will update DRRS-N when a change to primary assigned mission occurs (e.g., Anti-Submarine Warfare (ASW) to Counter-piracy). Report a number from 1-4 in PCTEF using following criteria:

h. Percent Effective (PCTEF) Remark. Add remarks which explain the reason for selecting the reported PCTF number. (1) Unit possesses the required resources, is trained, and is in position or has the necessary mobility to undertake the mission it has currently been assigned. (2) Unit possesses the resources, is trained, and is in position or has the necessary mobility to undertake most of the mission it has currently been assigned. (3) Unit possesses the resources, is trained and is in position or has the necessary mobility to undertake many portions, but not all; of the mission it has currently been assigned. (4) Unit requires additional resources and/or training or needs mobility assistance to undertake the mission it has currently been assigned. 6.4 Chemical-Biological Defense Section a. Chem-bio Defense. Units must calculate the Chemical and Biological Defense C Rates for Supplies and Training.


6-4

b. Current Rate/Reason. Automatically calculated from the Supply and Training C Rates and Reason Codes. The CBD C Rate is based on the lowest degradation for Supply and Training. c. Supply Rate. Units must provide an overall assessment of their CBD Supply status based on their possessed requirement as outlined in the appropriate Allowance Equipage List (AEL) or Table of Allowance (TOA). The specific type and quantity of CBD Supplies that particular units/platforms are required to possess is stipulated in Equipment/Supplies allowance lists as well as other appropriate OPNAV, Navy Component Commander, or TYCOM documents. Units should consider missing supplies (not available because it has been removed for repair, calibration, or on loan to another unit, equipment operability and shelf life data) when determining CBD supplies-on-hand status. CBD Supply includes CBD personnel protective equipment, personnel decontamination equipment, detection supplies, CBD medical items and decontamination supplies. Installed CBD systems may include CBD detection equipment, CBD warning and reporting systems, and collective protection systems, countermeasure wash-down and DECON systems, personnel DECON stations and personal protective equipment. Refer to the tables below to calculate the Supply C Rate.

Percentage of supplies Supply C Rate

90 -100% C1 80 – 89% C2 65 – 79% C3 00 – 64% C4

d. Supply Reason. Refer to reference (a), pages 3-6 through 3-7 for complete list of Chem-bio Supply reason codes. e. Training Rate. CVN: Units must provide an overall assessment of their CBD training status based on the specified

Supply Authorized Actual Percentage Supply C Rate

Personal Protective C1-C4 Personal DECON C1-C4 Personal Detection C1-C4 Medical C1-C4 Installed DECON C1-C4 Installed Protection C1-C4 Countermeasures Wash down C1-C4


6-5

requirement as prescribed in TYCOM or other applicable training manuals. CBD training requirements include as appropriate: (1) Individual Training – Individual CBD training includes CBD schools, CBD PQS, and unit course training. Applicable unit CBD Navy Officer Billet Classification (NOBC) and Navy Enlisted Classification (NEC) positions shall be filled by trained personnel. (2) Team Training - Personnel assigned to unit CBD teams shall have CBD Team Training for their assigned positions. (3) Unit Training - Unit has completed Unit CBD training, exercises, and drills, and demonstrated proficiency standards required by the unit’s chain of command. These exercises may include single service training or joint CBD training with other forces.

Percentage of Training Training C Rate

85 -100% C1 70 – 84% C2 55 – 69% C3 00 – 54% C4

f. Training Reason Code. Refer to reference (a) pages 3-6 through 3-7 for a list of Chem-bio training degradation codes. 6.5 Personnel Strength (PERSTREN) (1) Type. Report NC (Officers), NE (Enlisted) and NW (Warrants) as applicable. Add a new Personnel Strength set for each personnel type. (2) Structured (BA). Report Billets Authorized (BA) from your Activity Manning Document (AMD) or Enlisted Distribution Verification Report (EDVR). (3) Authorized (BA). Report BA from your AMD or EDVR.

Type Training Percent Trained Training C Rate Individual C1-C4 Team C1-C4 Unit C1-C4


6-6

(4) Assigned (NMP). Report the Navy Manning Plan (NMP) number by personnel Type as per the AMD or EVDR. (5) Possessed (COB). Report the number of personnel in that type that are Current on Board (COB). Note: Numbers in the PERSTREN fields are not auto-populated from DRRS-N and must be entered manually by the unit.


A-1

Appendix A Personnel Metrics Description

TYCOM Lead: COMNAVAIRPAC N1 1. Aircraft Carriers a. Overview. Personnel Figure of Merit (PFOM) calculations are measured by specific manpower and personnel data assigned to each mission using the PFOM methodology. Measurements in each MET include the assigned skills and job codes. Skills and job code measurements include officer manning, enlisted ratings, NEC skills, training & education (T&E) levels, and Nuclear-trained manpower (where applicable). T&E Requirements and Levels are extracted from the FLTMPS program which captures each unit's F, T, and D school training levels. DRRS-N has incorporated the Fleet Readiness Enterprise's (FRE) FIT metric measuring methodology into the DRRS-N PFOM calculation. DRRS-N organizes individual commands within groupings titled Responsible Organizations, or RESPORGS. In comparative terms, each RESPORG mirrors an aircraft Type Model Series (e.g. VFA, HSC EXP, VAQ CVW etc). The CVN has a stand-alone RESPORG. PFOM = (Rs – Gs) [Skill requirements – Skill Gaps] Rs [Skill Requirements] Note: The term M+1 is no longer used in PFOM. It was replaced by Billets Authorized (BA) as the top level personnel requirement. b. Data Flow. Data for PFOM comes from several sources, mostly Navy personnel databases. PFOM itself is a database that combines the personnel mapping (Skill to NTA) and the personnel data from the various personnel databases to calculate the Personnel Figure of Merit for each NTA in DRRS-N. The skill mapping is owned and maintained by the TYCOM or Type Wing manpower lead (N1). c. Frequency. Data is pulled from PERS 4 and other personnel databases (Fleet Management & Planning System (FLTMPS), Total Force Manpower Management System (TFMMS), Navy Enlisted System (NES), etc) every month. The TYCOM then calculates each unit’s PFOM scores and exports them to DRRS-N as the BUPERS data is updated in PFOM. The size of the data files and the method for DRRS-N updating currently prohibits near-real time data flow.


A-2

d. PFOM Data Management. PFOM management for squadrons shall be the responsibility of each Lead Type Wing. PFOM management for all aircraft carriers shall be the responsibility of COMNAVAIRPAC/COMNAVAIRLANT N1. Each Type Wing shall assign a primary and secondary PFOM RESPORG Action Official (AO) who will coordinate continual skills-to-task assignment, be responsible for PFOM data integrity and oversight, and identify job codes/ratings and skills to meet mission requirements. The skill-to-task assignments are completed within the PFOM module. The criticality, supervision, management and oversight of skills-to-task completion and control cannot be overemphasized. RESPORG PFOM Management Lead CVN COMNAVAIRLANT N1 CVW COMNAVAIRLANT N1 VFA/VFA EXP COMSTRKFIGHTWINGPAC VFC/VFA 204 COMTACSUPWING VAW/VRC COMACCLOGWING VAQ CVW/EXP COMVAQWINGPAC VAQ 209 COMTACSUPWING VP/VPU/VUP/VQ(E)/VP MTOC COMPATRECONGRU VQ(T) COMSTRATCOMMWING ONE VR COMFLTLOGSUPWING VX COMNAVAIRPAC/COMNAVAIRLANT N1 HSC (CVW/EXP) COMHSCWINGPAC HSC (NSW) COMHSCWINGLANT HSM/HSL COMHSMWINGPAC HM COMHSCWINGLANT VTUAV/HUQ COMHSCWINGPAC


B-1

Appendix B Equipment Metrics Description

TYCOM Lead: COMNAVAIRPAC N43 (CVN) COMNAVAIRLANT N422 (Squadrons and Detachments) 1. Aircraft Carriers a. Metrics. The PESTO E Pillar represents the ship’s ability to perform each assigned NMET based on equipment condition. Maintenance Figure of Merit (MFOM) computers calculate values for equipment readiness based on information contained in Work Candidates (also known as (a.k.a.)) Maintenance Action Forms (MAF)) in the Current Ship’s Maintenance Project (CSMP) and CASREPs. MFOM uses mathematical algorithms, and virtual CVN models, to calculate material condition readiness and screening values. Within the CVN model, systems are weighted by major component and sub-component and are mapped by a matrix to the each NMET in the NMETL. Computed readiness values are sent to DRRS-N via the PESTO E Pillar. Screening values are sent to TYCOM Maintenance Managers as recommended priorities for assigning work to repair activities. Calculated values are combined with historical maintenance cost data to generate cost of readiness. b. Data Flow. Ship’s personnel document equipment status (operational condition) by creating Work Candidates in the ship’s Approved Current Ship’s Maintenance Project (CSMP). CSMP changes are transmitted to MFOM via an up line process. MFOM applies CSMP data and CASREPs to a complex, hierarchically structured, virtual CVN equipment model. A Model-to-NMETL Matrix then calculates the impact of each degraded system against each readiness requirement defined by each NMET. c. Frequency. MFOM updates the DRRS-N “E” Pillar within a few hours of a CSMP ‘up line’ or a CASREP leaving the ship. Potential sources of “E” Pillar errors include: (1) Personnel entering incorrect Equipment Status Codes and/or selecting wrong equipment when creating a CSMP work candidate. Each work candidate is supposed to be scrutinized by multiple levels within the department before being authorized to be ‘up line’ reported off ship by the Organizational Maintenance Management System-Next Generation (OMMS-NG) Functional Area Supervisor (FAS).


B-2

(2) Structural discrepancies in the MFOM virtual carrier model or in the CVN Model-to-NMETL Matrix. These discrepancies are apparent when an equipment casualty causes too much negative readiness impact, or less impact than there should be. Report these anomalies to your TYCOM N43 MFOM coordinator via your Ship’s 3-M Officer. (3) Mismatches between CASREP and associated Work Candidate data. Maintenance Readiness Assessment System (MRAS) contains a mirror image of the data and programs used by MFOM Ashore. MRAS allows ships to test a CSMP up-line before the data leaves the ship. Testing will determine if something in the up-line data will result in an unintended change in MFOM readiness calculations. Using MRAS for this purpose may prove to be too cumbersome to be a routine part of a QA process. A diligent Work Candidate QA process is the best solution to ensure accurate material readiness reporting. Note: MRAS second purpose is to allow a Group Commander to view computed material readiness of each unit within the given group. 2. Aviation Squadrons a. Metrics. CNAF uses flight line entitlements and aircraft and mission systems tables to describe systems of points that are acquired as a unit receives aircraft and mission systems. CNAF also provides a mapping of the NTAs that are related to aircraft maintenance to the various equipment types. Each Type/Module/Systems (T/M/S) has their own equipment tables and NTA mapping based on their mission and the equipment required to perform that mission. The metrics are designed to show red in the Maintenance and Basic Phases, yellow in the Integrated Phase, and green in the Sustainment and Deployment Phases. RBA definitions for each TMS are outlined in CNAF Instruction 5442. The squadron lookup tables and equipment to NTA mapping tables are located in the Reference Library in the CNAF Readiness Reference Tool. b. Data Flow. The data source for the E Pillar is the unit’s AMSRR. Data from the AMSRR is collected in the Aviation Data Warehouse (ADW), where it is combined with TYCOM approved aircraft and mission systems metrics and equipment to NTA mapping.


B-3

c. Frequency. As the data is updated in the AMSRR, the “E” Pillar is updated (daily for most units). Of the three pillars available to a squadron in DRRS-N, the “E” Pillar has the shortest frequency of data refresh.


C-1

Appendix C Supply Metrics Description

TYCOM Lead: COMNAVAIRLANT N41 (CVN) 1. Aircraft Carriers a. Metrics. The Supply “S” Pillar represents the availability of supplies necessary for performing each assigned NMET and Capability Area. The “S” Pillar inputs its data into DRRS-N via the web input tool. This is managed by COMNAVAIRPAC/COMNAVAIRLANT Force Supply who receives inputs from the carriers through Relational Supply (R-Supply), Naval Aviation Logistics Command Management Information System (NALCOMIS), AMSRR and Operational Reports (OPREP-5) Feeders. The metrics in Supply Figure of Merit (SFOM) are the same for every CVN class. The weights assigned to the three major supply areas (Repair parts, Fuel and Provisions) are the same for all CVN classes.

Supply Pillar Weighting Repair Parts FUEL Provisions

52% 41% 7% b. Data Flow. All CVN Supply Departments are required to report supply data. Data, from reports, is entered into the Shore database via the Fleet Assistance and Shipboard Training (FAST) team, which is located at Naval Air Station North Island. SFOM itself (unlike PFOM and MFOM) is not a database. SFOM is a collection point on a server where the supply data is applied to the SFOM metrics to generate the SFOM values that are displayed in the S Pillar of DRRS-N. c. Frequency. DRRS-N queries the SFOM data source every 24 hours for updates. The Source data to update SFOM is fed weekly (normally submitted close of business (COB) each Friday) from each CVN via the Aircraft Material Supply Report (AMSR). This report contains the Aviation Consolidated Allowance List/Coordinated Shipboard Allowance List (AVCAL/COSAL) range and depth and other supply data required to calculate the SFOM scores. The FAST team updates SFOM using data from this report each Monday or as required.


C-2

2. Aviation squadrons. Aviation squadrons and detachments do not consider the Supply Pillar in their DRRS-N assessments. The “S” Pillar will display white cells indicating that no supply data is expected.


D-1

Appendix D Training Metrics Description

TYCOM Lead: COMNAVAIRPAC N7 (CVN) COMNAVAIRLANT N40 (Squadrons and Detachments) 1. Aircraft Carriers a. Metrics. The basic metric for the T Pillar is the Training Figure of Merit (TFOM). TFOM is a function of the unit’s Performance factor (Pf) times the unit’s Experience factor (Ef), i.e., TFOM = (Pf X Ef)/100 and is generated for each NMET. Pf (Performance) NMET Standards are the sub-event assessment scores given by Afloat Training Group (ATG) (or other designated assessment entity) when each sub-event is assessed per the CV Training Manual (TRAMAN) schedule. Ef credit is earned by completing sub-events within CV-SHARP per the CV TRAMAN schedule and with the associated Training and Assessment Card (TAC). b. Data Flow. The CVN “T” Pillar Ef data comes from sub-event completion data logged into CV-SHARP by watch team members. That data is sent to CV-SHARP Ashore where the Ef values are calculated using the inherent Training Matrix and then forwarded to the Navy Training Information Management system (NTIMS). Pf scores are manually entered into CV-SHARP Ashore (currently by the TYCOM) and sent to NTIMS. NTIMS combines the Ef and Pf metrics to generate the TFOM scores for DRRS-N. DRRS-N presents the results of the calculations as the TFOM for a given MET and the data is displayed in the ‘drill-down’. c. Frequency. Data logged in CV-SHARP is compiled on the ship and transmitted ashore every 24 hours dependent on bandwidth availability. DRRS-N queries the NTIMS database for TFOM updates every 24 hours. 2. Squadrons and Detachments a. Metrics. The single metric for the “T” Pillar is the TFOM equation TFOM (Tr)= (Pf X Ef)/100. This equation describes training as a function of Performance (Pf) and Experience (Ef). Each TYCOM decides how to calculate the Performance and Experience factor. For COMNAVAIRPAC/COMNAVAIRLANT units, that calculation comes from the Capabilities-Based T&R matrix. A TFOM is calculated for each NTA that is related to Aircrew Training.


D-2

b. Data Flow. SHARP is the initial data source for flight and training data that support the TFOM calculation. When the unit submits a Current Readiness Assessment (CRA), the data from SHARP is sent to the Aviation Data Warehouse (ADW) where Pf and Ef are calculated and forwarded to NTIMS. NTIMS calculates TFOM and sends the data to DRRS-N where the results are displayed in the “T” Pillar. c. Frequency. The TFOM is calculated when the unit submits a CRA at a minimum of every fifteen days. When the TFOM is calculated and sent to DRRS-N, DRRS-N will display this data in the T Pillar until a new CRA is submitted and a new TFOM is calculated. Requirements for submitting CRAs in SHARP are outlined in reference (d).


E-1

Appendix E Ordnance Metrics Description

TYCOM Lead: COMNAVAIRLANT N40 (CVN) 1. Aircraft Carriers a. Metrics. The Ordnance O Pillar reflects the standardized distribution load allowances available for performing each assigned NMET and Capability. Ordnance Figure of Merit (OFOM) captures the delta between the standardized CVN distribution load allowance and ordnance currently held onboard by Capability Area. All CVN standardized distribution load allowances are currently reflected in Ordnance Information System-Wholesale (OIS-W) and are accessible through DRRS-N. Much like the Equipment Pillar, ordnance is mapped to tasks that require ordnance resources. Mapping is done by RESPORG and also considers major end items and sub-assemblies. Simply stated, the OFOM for a given MET is the current on-hand quantity of ordnance divided by the authorized NAVSEA allowance. Note: Ordnance is not required for all METs and Capability Areas. White cells in DRRS-N represent such areas where ordnance is not required and thus not mapped. b. Data Flow. All CVN Ordnance Departments are required to report ordnance data to the Ordnance Information System (OIS) via Ammunition Transaction Reporting (ATR). OFOM, the data management and decision support system, collects and tracks the data received from OIS-W, maps it, and generates ordnance values that are displayed in the “O” Pillar of DRRS-N. c. Frequency. The data in OIS-W and OFOM are updated as Ammo Transaction Reports (ATR) as submitted by the units. DRRS-N queries OFOM every 24 hours for updates. 2. Squadron and Detachments. Aviation squadrons and detachments do not consider ordnance in their DRRS-N assessments. The “O” Pillar will display white cells indicating that no ordnance data is expected.


F-1

Appendix F CNAF Authoritative Data Sources

1. Authoritative Data Sources that feed DRRS-N 2. Authoritative Data Source Acronyms a. Personnel TFMMS Total Force Manpower Management System FLTMPS Fleet Training Manpower Planning System PFOM Personnel Figure of Merit b. Equipment CSMP Current Ships Maintenance Project MFOM Maintenance Figure of Merit MRAS Mission Readiness Assessment System OMMS-NG Organizational Maintenance Management System-Next Generation AMSRR Aircraft Maintenance Supply Readiness Report c. Supply SFOM Supply Figure of Merit CMP Consolidated Maintenance Plan

Pillar Authoritative Database

Metrics Owner

Personnel (CVN/Sqdn)

TFMMS/FLTMPS COMNAVAIRPAC N1

PFOM COMNAVAIRLANT N1 Equipment (CVN) CSMP USFF N43

MFOM USFF N43 Equipment (Sqdn) AMSRR COMNAVAIRLANT N422

Supply SFOM USFF N41 CMP COMNAVAIRLANT N41

Training (CVN) CV-SHARP COMNAVAIRPAC N7 Training (Sqdn) SHARP COMNAVAIRPAC N40

ADW COMNAVAIRPAC N40 NTIMS USFF N7

Ordnance OIS-W USFF N41 OFOM COMNAVAIRLANT N40


F-2

d. Training ADW Aviation Data Warehouse NTIMS Navy Training Information Management System e. Ordnance OIS-W Ordnance Information System - Warehouse OFOM Ordnance Figure of Merit


G-1

Appendix G RESPORG NMET Review Checklist

Has mission analysis identified new tasks not presently part of the NTTL/UJTL?

□ Has the new task been submitted to USFF/NWDC for inclusion in the NTTL/UJTL?

Is the NMET mission essential? □ Does the NMET meet Suitability/Feasibility guidance for the

mission?

□ Does the NMET support Force Protection/minimizing Collateral Damage?

□ Does the NMET support or command-link to another organization’s task?

□ Does the mission have a high probability of failure if task is not accomplished successfully?

□ Are Follow-on missions dependent on successful completion of this task?

□ Has the superior commander designated this task as essential?

Is the NMET assigned to the correct capability/mission/mission area? For each capability indicated:

Does the NMET contain at least one condition/condition descriptor?- (UNTL says 3-5 Conditions per NMET to help determine level of difficulty/ risk in meeting task standards)

□ Do the conditions/condition descriptors impact at least one standard?

□ Do the conditions reflect the perceived/expected operating environment?

□ Is there only one Descriptor in accordance with condition listed?

□ Are there required conditions that are not part of the NTIMS conditions list?

□ Have the new conditions been submitted to FFC for inclusion in NTIMS?

□ Do any threat conditions apply? □ Are Conditions consistent through the NMETL for the same

capability?


G-2

Does the NMET contain at least one standard (Measure + Criterion)? □ Do the measures and criteria reflect how a task contributes to

mission success?

□ Are measures consistent through all echelons of the mission thread?

□ Do measures focus on the outputs, results of performance (outcome), or on the process to achieve the task?

□ Are the measures sensitive to the impact of conditions on task performance?

□ Do measures distinguish among multiple levels of performance? □ Do some measures check for recent Lessons Learned issues? □ Is it feasible to collect performance data against this measure? □ Does each measure contain at least a T2 criterion?

□ Do the signs for each T value make sense? Remember, the system looks first for T2, if a higher number is better, then the sign should be > or >=. If lower, then signage should be < or <=. Make sure the signs for T1, T3, and T4 align to proper mathematical sense.

Does the NMET support a senior commander (Supported Task)? Does the NMET document the supported commander’s task?

Does the NMET require action from a supporting commander (Command-linked Task)?

□ Does the NMET document the supporting commander’s task? List any other issues for NMETs or NTIMS: *CRAs should use this sheet to check each NMET.

Date post:	20-May-2018
Category:	Documents
Upload:	vuongngoc
View:	222 times
Download:	0 times

COMNAVAIRPAC/COMNAVAIRLANTINST...

Documents