Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS
A lock ( ) or https:// means youโ€™ve safely connected to the .gov website. Share sensitive information only on official, secure websites.


Research to Operations

Multi-Project Transition Plan Template Instructions

(Version: November 15, 2023)

The Multi-Project Umbrella Plan is another type of umbrella plan which is simply a grouping of individual project transition plans grouped together by similar subject matter. For example, a NOAA program may decide to seek initial approval for a number of individual project transition plans and then group the programโ€™s social science or numerical weather prediction projects prior to seeking leadership approval. This approach does not affect the content of the individual transition plans and is simply done for efficiency and convenience. The projects included in this type of umbrella plan should be intended to transition to a common NOAA Line Office or external entity but may transition to different offices or subgroups within the larger organization. This type of umbrella plan is most effective for smaller (~1-3 year) R&D projects with relatively straightforward transition paths. It is recommended that complex transition projects develop standalone transition plans.

It is important to note that a transition plan is intended to provide the vision or roadmap for the proposed capability and guide transition efforts toward use, including operations. It is a living document to be amended with increasing detail as the project matures.  It will remain valid for the life of the corresponding development project, including its successful completion that it satisfies end user-defined Line Office metrics for success and operational constraints, and it clearly surpasses each of the associated gates or requirements for transition.

This is provided as a guide.  Not all sections that are identified in the template may be needed for all transitions. Key sections are derived from NAO 216-105B Handbook Appendix D[1].  Only sections relevant to the project should be completed.

The ultimate decision to transition this project to operations resides with the appropriate decision maker of the receiving Line Office or external end-user. The signing of a transition plan provides situational awareness of the work and review / acknowledgement to move forward.  It does not represent a binding agreement and/or funding availability. Signatures for the review and acknowledgement process will be dependent upon the maturity of the technology, type of transition, end users and their requirements If and when projects transition outside of NOAA, every attempt should be made to obtain letters of support from end user(s) as well as NOAA appropriate signatures.

Transition Plan Review and Acknowledgement


Stages: The NAO 216-105B Handbook describes the review and signature process through stages, and each stage involves both the R&D and adopter review/acknowledgement.

โ—       Stage 1: is the working level review/signing, which includes appropriate division chiefs, other resource managers or end users.

โ—       Stage 2: involves the review/signing by the affected LOTM(s).

โ—       Stage 3: involves the review/signing by the affected Line Office Assistant Administrators (AA(s)) or their delegate(s).

Applicability: It is reasonable to expect projects that are less mature and many years from implementation may only be required to undergo Stage 1 and 2 review and signing, unless otherwise specified by the LOTM(s), adopter(s), or funding program manager, who can request to elevate any Transition Plans to Stage 3 signing. Any projects that aim to exceed RL6 (regardless of their current RL) must undergo Stage 3 approval (unless otherwise specified by the affected LOTMs), and thus the Transition Plan must be fully reviewed and signed by the AA(s) or their delegates. See NAO 216-105 B Procedural Handbook: โ€œIt is reasonable to expect that projects that are less mature and many years from implementation may have less developed Transition Plans that may not require the full review or acknowledgement process.โ€

 A primary principal investigator (PI) that is a Federal employee should be identified on the title page. However, if the project PI is affiliated with a Cooperative Institute (CI) or other external entity, a designated NOAA point of contact (POC) or NOAA funding program manager should be named on the transition plan first, followed by the affiliated PI(s). External team members, (i.e. Co-PIs, collaborators, etc.) may be identified in the version control table as content contributors and reviewers. Please note that all transition plans are internal NOAA documents. Transition Plans shared outside of NOAA must have sensitive information redacted, including, but not limited to: vendor costs/estimates, vendor proprietary information (technical specifications, designs, blueprints, etc.), cooperative institute financial information, proposal/grant awards, personally identifiable information, or NOAA financial information.

If financial or other information is sensitive, it is recommended that you include this information in an appendix so that it can be easily redacted or removed prior to sending it to non-NOAA personnel. Note: No sensitive, personal identifiable information (PII) and/or proprietary information should be contained in a Transition Plan.

Please contact the Office of Research, Transition, and Application for additional questions on developing and customizing transition plans.

[1]NAO 216-105B Handbook: https://www.noaa.gov/sites/default/files/legacy/document/2020/Mar/Handbook_NAO216-105B_03-21-17.pdf