COMNECCINST 3501.1 N8

COMNECC INSTRUCTION 3501.1 Subj:

READINESS AND COST REPORTING PROGRAM (RCRP)

Ref:

(a) 2009 Navy Expeditionary Combat Enterprise (NECE) Strategic Plan (b) OPNAVINST 3501.360 (c) DoDD 7730.65 (d) COMUSFLTFORCOMINST 3501.4 (e) RCRP Concept Document (f) DoDD 8320.02 (g) RCRP Business Rules Document (h) RCRP Configuration Control Board (CCB) Charter (i) COMNECCINST 3500.1A (j) COMNECCINST 4015.1 (k) COMNECCINST 7700.1 (l) COMNECCINST 3502.1 (m) COMNECCINST 4400.1 (n) RCRP Figure of Merit (FOM) Management Charter for Personnel, Equipment, Supply, Training and Ordnance Readiness Pillars (o) RCRP Roles and Permissions Document

1. Purpose. To promulgate force wide supplemental guidance regarding the roles and responsibilities, implementation, sustainment and system life cycle management for the Readiness Cost and Reporting Program (RCRP). 2. Scope. This instruction applies to the Navy Expeditionary Combat Command (NECC) and Navy Expeditionary Combat Enterprise (NECE), to include all components, staffs, and supporting commands and organizations. 3. Policy. This instruction provides guidance and policy on the development, implementation, and operation of RCRP across NECC/NECE, and supplements previously promulgated guidance. RCRP supports the enterprise objective of attaining the right readiness at the right time at the right cost.

COMNECCINST 3501.1 9 Apr 09 a. RCRP supports the intent of NECE Strategic Goal Number seven specified in reference (a) to establish a capabilitiesbased, adaptive, near-real time readiness reporting system for NECC. RCRP will serve as the authoritative data source to provide the Defense Readiness Reporting System-Navy (DRRS-N) the Personnel, Equipment, Supply, Training, Ordnance(PESTO) Figure of Merit (FOM) readiness indicators for all Navy Mission Essential Tasks (NMETS) and capabilities for NECC readinessreporting units. Units responsible for DRRS-N reporting are outlined in reference (b). Unit Commanders and Officers-in— Charge (OIC) responsible for reporting in DRRS-N will do so IAW references (b) through (d). b. RCRP delivers a NECE management tool designed to define and manage the elements of the PESTO resource categories in a standardized and consistent way to provide a metrics-based measure of readiness for each unit assigned to the force. RCRP will provide all stakeholders with the metrics and information to better understand and manage readiness and cost across the force. c. RCRP will serve as an enterprise planning tool to optimize and support decision making processes regarding the capability, readiness, employability, cost and capacity of NECC forces. 4.

Discussion

a. An essential element to NECC’s success is the implementation of Navy Enterprise processes and behaviors at every level of the enterprise, which will help to ensure effective implementation for a cost-wise readiness and a metrics-based approach. In order to deliver an effective and efficient force, NECE requires an analytical capability to provide timely decision making to support the optimum expenditure of constrained resources, and to assess the current capability, readiness, employability, cost and capacity of the NECC Force. As amplified in reference (e), RCRP provides the standardized and analytically-based readiness tool required to fully manage readiness and cost across the force. b. RCRP will deliver the capability and the process that will enable NECE to implement, measure, and manage cost-wise readiness; support force planning; and serve as a central component of the NECC readiness model. This tool will represent a significant advance in NECC’s ability to assess and report readiness to higher authorities via DRRS-N.

2

COMNECCINST 3501.1 9 Apr 09

c. RCRP will be consistent with Navy Readiness Reporting Enterprise (NRRE) principles. RCRP will integrate with authoritative databases, where available, as prioritized by the RCRP Configuration Control Board (CCB). In accordance with reference (f), RCRP will establish a net-centric system using the latest web and integration technologies to make RCRP data available for enterprise reuse, automate consumption and synchronization of authoritative data, and leverage existing enterprise capabilities, as required. RCRP will be developed in periodic spiral releases with enhanced, expanded or refreshed functionality. d. Reference (g) provides detailed information on the RCRP Business Rules used to develop the system. This document will be a living document, updated with each RCRP release. The business rules provide the background, construct, approach, methodology, assumptions, and constraints for levels at which readiness indicators will be computed; the methodology and approach for how PESTO resources will be associated to tasks and capabilities; the weighted prioritization to determine what and by how much resources will impact PESTO readiness indicators; and provides the background, purpose, construct, assumptions, constraints, algorithms (equations), and metrics for calculating each PESTO Pillar FOM. Each Pillar has a unique construct and approach of which the PESTO FOM will determine where and how the transition from insufficiency to sufficiency occurs. e. Reference (h) establishes the RCRP CCB. The CCB is comprised of key program stakeholders who are responsible for communicating and coordinating change factors; and evaluating, approving, and prioritizing configuration changes to the program. The CCB will be the primary conduit to receive and evaluate force recommendations for RCRP program improvements and modifications. The CCB will document all final decisions and recommendations. Configuration Change Request (CCR) forms are required to formalize the recommended change process. f. Nothing in this instruction shall supersede the reporting requirements established in reference (i). Transition from current SORTS reporting processes will be accomplished by incorporating SORTS reporting functionality with the DRRS-N application. Readiness reporting will remain a requirement; however, the method by which readiness will be reported will be transitioned to DRRS-N. NECC transition to DRRS-N will be published by separate correspondence once finalized.

3

COMNECCINST 3501.1 9 Apr 09 g. The primary point of contact for RCRP within COMNECC is the Assistant Chief of Staff for Warfare Program and Readiness (N8). Any questions regarding this instruction will be directed to the N8 staff. 5. Action. Once fully implemented, RCRP will be used throughout NECE as the authoritative readiness and resource management tool, and will ultimately populate the PESTO pillars within DRRS-N. Current resource management functions specified in references (j) through (m) will either be fully captured, or be directly supported by RCRP functionality. Enterprise resource management and readiness legacy systems may continue to be employed as needed pending the incorporation and implementation of equivalent functionality within RCRP. As RCRP is introduced to the enterprise, ensuring full understanding of system capability and functionality by the entire chain of command is critical. Specific actions include: a.

NECC (N8):

(1) Provide RCRP program management. This includes but is not limited to the RCRP development and implementation management. Manage the integrity and continuity of the RCRP development process including requirements analysis, design, development, test, systems engineering, and deployment. (2) Establish and chair the CCB. Assign appropriate representatives to the CCB. Execute the CCB in accordance with reference (h). (3) Establish and chair Organization Change Request boards. Design the process for convening boards and ensure compliance. Identify Leads and Action Officers for each of the six areas of interest as follows: Personnel – N1; Operations – N3; Supply – N41; Equipment – N43; Training – N7 and Readiness/Alignment – N8. (4) Establish and chair the PESTO FOM Management Team. Identify Leads and Action Officers for each of the five PESTO pillars to comprise the FOM Management Team as follows: Personnel – N1; Equipment – N43; Supply – N41; Training – N7; and Ordnance – N43. (5) Establish and chair PESTO FOM Working Groups in accordance with reference (n).

4

COMNECCINST 3501.1 9 Apr 09 (6) Provide RCRP user and technical support. This includes system Tier I, II and III system technical support, user help desk support, and user training. (7) Develop information sharing agreements (Memorandums of Understanding/Memorandums of Agreement) between NECC and authoritative database owners. b.

RCRP Configuration Control Board (CCB):

(1) Provide formal governance and structure for RCRP Change Management. Ensure visibility and mutual understanding of internal and external factors which affect the RCRP configuration to include policy, organization, processes and systems. (2) Ensure the effectiveness and efficiency of a complete, accurate, timely, and controlled process for identifying and adjudicating RCRP requirements. (3) Provide a decision making body to approve/ disapprove/defer proposed RCRP configuration changes, to include managing CCRs. (4) Provide a formal process for prioritizing development requirements based on time availability and cost trade-off decisions made between technical performance, functionality, operability, and supportability. Document RCRP management and configuration change decisions and recommendations. c.

NECE Cross-Functional Teams:

(1) Provide oversight and assistance to the RCRP PESTO FOM Management Team as outlined in reference (n). (2) Support the alignment of PESTO processes, resource data, and metric definition in accordance with reference (a). (3) Submit recommended RCRP Configuration Change Requests to the CCB, as appropriate. d.

PESTO FOM Management Team:

(1) Support the definition of FOM metrics, balancing consistency with USFF, NECC Force requirements, data availability, and manual entry vs. integration timelines.

5

COMNECCINST 3501.1 9 Apr 09

(2) Identify authoritative databases, applicable to the Pillar to support FOM metrics. (3) Design a strategy for near, mid and long-term approaches to include transition / use of supporting applications relevant to PESTO Pillar. (4) Serve as the conduit of RCRP information and change management for NECE CFTs, coordinating directly with appropriate CFTs to ensure aligned requirements are being identified and processed for future RCRP version implementation. (5) Develop functional requirements / processes for RCRP to meet PESTO FOM Metrics to fit best business practices of the Force to include requirements generation and aggregation for the Pillars, while also serving as an information conduit for issues/barriers. (6) Collaborate efforts with USFF counterparts in DRRS-N FOM construct to ensure concurrence on RCRP approach, and awareness/visibility of DRRS-N and other developments that affect Pillar data development. (7) Nominate proposed RCRP configuration changes, via the appropriate CFT, to the RCRP CCB as required, for adjudication. e.

Organization Change Request boards:

(1) Provide oversight and assistance to Component Commands initiating change requests. (2) Review and validate requests ensuring change timeline is feasible, change of UIC/RESPORG is the best response to meet operational demand, and administrative milestones are established. (3) Forward changes to the appropriate authority for approval. (4) Track change requests from inception to implementation within the enterprise. f.

Echelon IV Commanders:

6

COMNECCINST 3501.1 9 Apr 09 (1) Implement, employ, and manage RCRP in accordance with COMNECC READINESS AND COST REPORTING PROGRAM (RCRP) INITIAL /IMPLEMENTATION, EXPECTATIONS AND MILESTONES (dtg 101912Z Mar08) to support all readiness reporting units. Amplifying information regarding specific build and milestones are: EOD and MDSU: MESF: NCF:

291737Z JAN 09 291924Z JAN 09 301234Z JAN 09

Other forces within NECC will receive additional information as their builds progress. (2) Provide reporting and data management guidance to subordinate units to ensure the accuracy, timeliness and completeness of required data to collect and align the PESTO resources to the correct readiness reporting unit. For east and west coast, Echelon IV Commanders shall produce a consolidated instruction. All guidance will be reviewed by COMNECC for adjudication before promulgation. (3) Monitor the data management, maintenance and compliance of subordinate units. Data must be maintained as frequently as necessary to ensure accurate PESTO readiness for unit capabilities and Mission Essential Tasks while reflecting unit status additions, changes or deletions. (4) Provide representation to the RCRP CCB and RCRP PESTO FOM Working Groups. (5) Designate personnel, to effectively manage the RCRP Program. As outlined in reference (o), system roles are functionally organized, and are updated as necessary with each RCRP release. Continuity of personnel is critical to ensuring RCRP is best postured to support enterprise objectives, and accordingly personnel assigned RCRP support billets should have at least one year remaining at their currently assigned command. (6) Forward RCRP enhancement or modification recommendations to NECC N8 for consideration/action by the CCB. Recommendations for RCRP changes should be fully vetted by Echelon IV Commanders on both coasts (ie, EOD Group ONE and TWO or Maritime Expeditionary Security Group ONE and TWO) and represent a consolidated and jointly approved recommendation prior to submission to N8.

7

COMNECCINST 3501.1 9 Apr 09 6. Technical Support. An RCRP technical staff will be established at NECC to provide essential RCRP information and support. The staff will be available for general questions and technical support Monday thru Friday during normal business hours Eastern Standard Time (EST). 7. Review. Understanding the basic policy, and the roles and responsibilities at all levels of command is vital to RCRP’s success. It is anticipated that this instruction will be updated as required based on evolving readiness and resource reporting requirements. Updates shall draw heavily from NECE users, and recommendations to improve the RCRP system are highly encouraged. Forward all recommendations to the NECC N8 RCRP Program Manager.

M. E. KOSNIK By direction Distribution: (COMNECCINST 5216.1) Lists I, II, and III (Electronically)

8