Attachment_11_-_Shore_Infrastructure_Guidebook.pdf

MILITARY SEALIFT COMMAND

Shore Infrastructure Guidebook

Table of Contents

INTRODUCTION

OBJECTIVE

REQUIRED BACKGROUND

GSIP WAY AHEAD

PROJECT PLANNING

TRACKING PROJECTS

PROJECT SCORING

CONGRESSIONAL ADDS

Introduction The overall shore infrastructure vision of Military Sealift Command (MSC), as stated in the Global Shore Infrastructure Plan (GSIP) is, “Cost Effective Infrastructure Aligned with Mission Requirements.” This vision is employed through five guiding principles that guide MSC decisions on infrastructure: (1) Wherever possible, leverage existing infrastructure; (2) Align, size, and configure infrastructure to support worldwide MSC operations; (3) Promote a positive quality of service for MSC personnel; (4) Explore alternative operational concepts that could reduce overall infrastructure requirements; (5) Enable the future MSC fleet. With this vision in mind, MSC’s GSIP outlines capability gaps in shore infrastructure around the world that need to be resolved to establish optimal infrastructure to support the MSC mission. Additionally, MSC will increasingly affect Navy shore infrastructure due to a variety of operational influences including new platforms, basing decisions, new missions, and mission realignments.

All these influences have and will continue to result in projects initiated by MSC or the impacted installation in support of the MSC mission. Therefore, it is in MSC’s interest, to be directly involved in the Shore Infrastructure Investment Planning and Programming process that moves these projects from planning, development, and funding. This guidebook is a tool to assist in that effort.

Objective The objective of this guidebook is to provide a foundation of information and procedures, on the military programming process to allow a project officer to effectively get involved and provide oversight of MSC shore infrastructure interests. The programming process is fluid with changes occurring throughout the year. Therefore, regular/continual involvement is required to maintain a current knowledge base that will be effective for representing MSC and overseeing interests.

Required Background To establish a working knowledge on the Navy Shore Infrastructure Investment process, the following recommended sources of information apply:

� MSC Global Shore Infrastructure Plan � Applicable POM/PR-XX Warning Order (WARNORD) and any subsequent

Fragmentary Orders (FRAGOs).

� Facilities Projects Instruction (OPNAVINST 11010.20G) � Electronic Project Generator (EPG) and Internet Navy Facility Assets Data Store

Integrated Priority List (iNFADS IPL) Military Construction (MILCON) User Guide � EPG- iNFADS IPL Special Projects User Guide � Naval Facilities Engineering Command (NAVFAC) Public Works Department

Management Guide � NAVFAC Shore Facilities Planning Guidebook

GSIP Way Ahead To ensure GSIP requirements are included in the Navy shore infrastructure plan, a process is required. In order to maintain an awareness of MSC needs and infrastructure conditions in the field, MSC shore infrastructure project officer should maintain communication with MSC representation (action officers) at installations worldwide throughout the year. The project officer should report all new shore infrastructure requirements that were not included in the GSIP to action officers, and vice versa. If action officers discuss requirements to the Installation and/or Region, they should inform the project officer.

A process is also required to assure shore infrastructure capability gaps have solutions. The project officer should follow-up with the Regions the capability gaps in the various AORs. The project officer needs to stay current with the status, changes, and other pertinent information regarding shore infrastructure. At a minimum, the project officer will:

1. Verify that the Regions are integrating the capability gaps outlined in the MSC GSIP in their shore infrastructure planning.

2. Get on Fleet Forces Command (USFF), Naval Installation Command (CNIC), Regions, and NAVFAC shore infrastructure email distribution lists, and watch for information, updates, and guidance.

3. Attend the annual MILCON Stakeholders Conference, usually held in February/March.

4. Attend Regional briefings throughout the year. The Regions do not know the MSC mission or maritime operations as well as MSC.

The GSIP should be reviewed by the project officer with the action officers (annually) for a validity assessment in a workshop setting. Recommended changes/updates will be forwarded to MSC Headquarters leadership for review/approval. The leadership will endorse the changes and forward to USFF.

Project Planning In general, MSC does not initiate projects--MSC communicates requirements. As a Fleet Provider, MSC is a “requirements generator” in the military construction planning and programming process. USFF is the integrator for Fleet requirements. Warfare Enterprise (WFE) and MSC GSIPs roll up into the FRE GSIP. The capability gaps and excess capacity opportunities from these GSIPs are integrated into the FRE GSIP. The Regions and Installations develop more detail plans based on GSIPs via Regional Integration Plans (RIPs) and Installation Plans. CNIC is the integrator for Shore Installation Management and Planning.

If it is determined that a project needs to be developed because it is a special project or MILCON, the Region will then task a NAVFAC Public Works Department (PWD) to scope, estimate, and develop the project. For small projects, below the special project threshold, MSC will work directly with the Installation. Each PWD receives a certain amount of sustainment funds annually to use at the Installation’s discretion. This money is used to fund the Sustainment, Restoration, and Modernization (SRM) requirements. However, for small projects, it may be possible for MSC to use its own funds.

The following tools are used in the project development process:

The EPG is the Navy’s one and only application for entering a MILCON Project Data Sheet (DD Form 1391). A DD Form 1391 is a construction project-programming document used to scope, estimate, and justify all types of construction. In order for a project to be considered, a DD Form 1391 must be prepared in EPG with all required fields completed. The appropriate DD Form 1391 in EPG must be linked to the iNFADS IPL Module. If there is a MILCON or Special

Project that supports MSC, the required data fields must be completed by USFF in the iNFADS IPL Module, so that the project can be scored.

The iNFADS is the Real Property Inventory (RPI) for the Department of the Navy. This enterprise system includes all the data necessary to support RPI, Planning, and Acquisition for the Navy and Marine Corps. iNFADS includes a facility module, an activity module, category codes, a base loading module, a planning module, an IPL module, and much more. For the Shore Infrastructure Programming Process, the only part of iNFADS that is of concern to MSC is the IPL module.

Regional Shore Infrastructure Management System (RSIMS) is an Internet-based facility data and mapping application. It provides the capability to view, report, and analyze shore installation facility data via a map interface. RSIMS consists of a suite of applications used to create and visualize maps and business tools in a Web-enabled environment. Currently RSIMS has the capability to pull up facility data such as the property data card, facility number, initial cost, utility consumption, equipment data, and work orders associated with a facility.

The Facility Readiness Evaluation System (FRES) provides an unclassified overview of current facility readiness in terms of condition, configuration, and capacity. FRES can be used to monitor the readiness of a given Navy facility. FRES is updated automatically with iNFADS data on a weekly basis. That is, when iNFADS is updated, FRES will be updated by the end of that week. Updating facility conditions is primarily a responsibility of the installation.

The NAVFAC Portal is an online resource through which users can connect with NAVFAC personnel, processes, information, and eTools. It contains a wealth of information on facility planning, programming, and execution. Information includes presentations, manuals, policy, and Standard Operating Procedures (SOPs).

The CNIC Gateway is an online resource through which users can connect with people, processes, and information such as file sharing, business plans and post documents or pertinent information within CNIC. Specifically, users can access POM/PR documents, WARNORDs, FRAGOs, and other information posted by CNIC N4, as well as, look up CNIC points of contact.

In such a competitive environment, a project submission must include good justification that is consistent with the shore investment guiding principles for the current program review cycle.

Tracking Projects Once a project is in progress, MSC needs to take ownership and follow up projects. Some fundamental actions to be taken in order to oversee a project as it goes through the military project programming process, and ensure MSC equities and interests are met include:

1. Understand the MILCON process. Follow-up all MSC MILCON projects and update the respective PM/FD/SA.

2. Ensure a DD Form 1391 exists in the EPG for all MILCON projects to be included in POM-XX, and that all required fields are completed, including “project scope”, “impact if not provided”, and Shore Investment Guiding Principle scores and statements.

3. Review DD Form 1391 submissions in EPG and ensure specific requirements are included.

4. Search for projects listed on the IPL. An “IPL” column is included in the Project List screen, to allow for searching of EPG projects that linked to the IPL. A project cannot exist in IPL, unless linked from the EPG.

5. Notify the respective Installation or Region Project Manager of any discrepancies.

6. Coordinate with CNIC/Regions/Installations in the Shore Investment Process development and have an understanding of the changes made to the POM Capital Improvements Program.

7. Attend the annual MILCON Stakeholders Conference, usually held in February/March.

8. Attend Regional planning meetings.

9. Get on USFF/CNIC/OPNAV/NAVFAC MILCON/Special Project email distribution lists, and watch for information, updates, and guidance.

10. Review current Project Programming WARNORDs/FRAGORDs. The POM/PR-XX

WARNORD and any subsequent FRAGORDs provide essential information on the applicable Budget Year’s military construction programming process, including procedures, timeline, required actions, and project scoring criteria. A review of these documents is vital to understanding the details of the applicable year’s programming process.

11. Coordinate with the Regions to integrate all MSC requirements within the various AOR's for submission of all capital improvement Projects, MILCON and Special projects, consolidation and footprint reduction.

12. Coordination is required with the installation Public Works Department (PWD) to ensure there is clear understanding of the project.

13. Coordinate input from subordinate organizations/local stakeholders within MSC (MSFSC, SSUs, SEALOGs, and MSCOs).

14. Communicate infrastructure requirements directly to Regions. They will help to develop the best solution that is efficient, economical, and in the best interests of everyone involved. The Region will also task an Installation PWD to scope, estimate and develop a project if that is the selected alternative.

15. Ensure all MSC projects are uploaded into NAVFAC's EPG/IPL Module. The expectation is that now that the large project database has been loaded, the focus will be on refining a smaller subset of projects (those that MSC expects to be competitive for the BY and BY+1) to improve submission quality in terms of scope development, facility data/project justification and evaluation.

16. Understand the process to push MSC projects for Congressional Adds.

17. Monitor the EPG/IPL Module to ensure MSC projects are properly scored by the Shore

Mission Integration Group (SMIG).

18. Go to Annual Stakeholder’s Meeting, and any briefings with the SMIG Working Group.

MSC should have someone at these meetings to ensure their interests/projects are represented properly.

19. Review FRAGORDs and WARNORDs for PR-XX Shore Program Review and use as additional regional guidance for PR-XX Capital Improvement Project Submission and Scoring.

20. Understand PR-XX Project Scoring.

Project Scoring MSC assists USFF in the Enterprise score of the project. The project scoring process is where each project is rated according to how closely it meets current Navy’s criteria for project scoring.

The project scoring criteria changes each year, with each new Program Review cycle, according to SECDEF, SECNAV, and CNO guidance.

It is important to understand project scoring because it helps in knowing the Navy priorities are in a given program cycle, with respect to shore infrastructure projects. This knowledge can help project facilitators within MSC to know projects that are competitive for funding. It also helps in developing justifications for projects as part of DD1391 input.

Projects are scored by the Region, then by the Regional Mission Integration Group (RMIG), and lastly by the Shore Management Infrastructure Group (SMIG). Results are in the iNFADS IPL Module. Project scoring criteria is based on: (1) Strategic Guiding Principles, (2) Shore Capability Area, and (3) Installation Figure of Merit (IFOM). Detailed explanations of each project-scoring element can be found in the EPG-IPL MILCON, or EPG-IPL Special Project User Guides, the NAVFAC portal, or in the POM/PR-XX WARNORD, located on the CNIC Gateway Portal. However, strategic Guiding \

Projects are scored on a 0-4 scale, where: (0) No Contribution, (1) Marginal, (2) Important, (3) Very Important, and (4) Critical. An expanded explanation of each score number can be found in the applicable WARNORD. Project scores are in iNFADS IPL Module. It is important to note that the SMIG only reviews the Project Data Sheets (PDS) from iNFADS, not the entire DD Form 1391. This is important, because there is not as much space on Project Data Sheets for justifications (only 100 characters). Therefore, justification statements must be succinct and accurately communicate the essential points. SMIG will not accept general statements that provide no specifics, such as, “Savings will be realized over a 2 year period.” Rather, they want to see something like, “Savings will be realized due to decreased use of commercially leased facilities.”

Congressional Adds Congressional Adds are MILCON projects that are added by members of Congress to the program year MILCON list. Congressional add projects must be executable in the next fiscal year. It is common for congress members or staff to ask Installation COs for their top “Congressional Add” MILCON candidates.

1. After reviewing the list of projects in PB-XX (President’s Budget), Congress may call for Congressional Adds.

2. Only Congress calls for Congressional Adds, not Enterprises or Providers.

3. The general rule is for projects to cost $7M – $10M.

4. Generally, the Region and higher authority decides on which projects to submit for

Congressional Add consideration.

5. If a project is a Congressional Add, MSC can make their case through the respective

Region, and ensure the project is on the IPL. The last part is simple, but critical. The project must be on IPL to be a Congressional Add, not just in EPG.

6. MSC can also look for and be sure to respond to any data calls relating to Congressional Adds.