Attachment 13 Project Book Guidance.pdf

Navy ManTech Program

REV O OCT23

Project Book Guidance

Attachment:

1. Sample Project Book Write-Up

2. Stakeholders’ Document Release Concurrence Form

3. Project Book Template

A. PURPOSE

The Navy ManTech Project Book is an annual publication used to support the outreach activities of the Navy ManTech Program. It includes the status and accomplishments of Navy ManTech projects for which Navy ManTech funds were expended in the previous fiscal year. To ensure the usefulness of this publication, it is essential that all Project Book data be current, accurate, and well written. This document outlines the data that is collected, the process steps, the responsible parties, and the required timelines.

B. REQUIRED TIMELINE

Project Book data is due on or before 15 August of each year. The Project Book is published in November prior to the annual Defense Manufacturing Conference (DMC).

C. PROCESS / APPROVAL CYCLE

All Centers of Excellence (COEs) are responsible for preparing, updating, and sending to the Navy ManTech Support Team Project Book data that will be submitted to the Public Release Request Tool (PRRT) for approval. For projects conducted in support of another COE (-B projects), the lead COE should work with the supporting COEs to prepare a single write-up that reflects the efforts of all COEs.

The Navy ManTech Support Team will review the write-ups for format and completeness and will assist in obtaining the appropriate approvals. The process steps are outlined below:

1. Navy ManTech Support Team emails existing Project Book write-ups and a Project Book Word template to the COE.

2. COE updates existing Project Book write-ups and creates new write-ups by using the template to provide the information described in Section D of this guidance. It is imperative that COEs ensure that the write-ups are well written, grammatically correct, clear, and consistent.

3. If required, COE obtains stakeholder concurrences for all write-ups that will be included in the Project Book, using the Stakeholders’ Document Release Concurrence Form shown in Attachment 2 (reference the Public Release Request Tool Guidance for instructions on completing the form).

4. COE uses a secure method, such as encrypted email, DoD SAFE (https://safe.apps.mil/), or a COE SharePoint site, to submit all Project Book write-ups and completed Stakeholders’ Document Release Concurrence Forms to the Navy ManTech Support Team at navymantech@bcsallegient.com. COE also submits a representative manufacturing image or graphic that preferably has not been used in previous Project Books and that is approved for public release for each Project Book write-up. The file name of all images and graphics should include the corresponding project number. The COE will also notify the Navy ManTech Support Team (navymantech@bcsallegient.com) of the secure method that was used to submit the Project Book write-up files.

5. Navy ManTech Support Team reviews and edits the write-ups for completeness and format and emails the COE to address comments made to the write-ups.

6. COE revises the write-ups to address the comments and emails the Navy ManTech Support Team that write-ups have been updated.

7. The Navy ManTech Support Team reviews the write-ups. After the comments have been satisfactorily addressed, the Navy ManTech Support Team emails the secure location of the Project Book write-ups to the applicable Program Officer (PO) / Contracting Officer’s Representative (COR) and requests review and approval.

8. The PrOf / COR reviews the write-ups and e-mails the COE and the Navy ManTech Support Team with comments that need to be addressed.

9. COE addresses the PrOf / COR comments and e-mails the PO / COR and the Navy ManTech Support Team after revisions have been made.

10. PrOf / COR reviews and approves the write-ups.

11. ONR Corporate Strategic Communications edits the write-ups to bring into compliance with the AP Style Guide.

12. COE creates one Word document that contains all of its write-ups and works with the Navy

ManTech Support Team to seek public release approval of the write-ups (see the Public Release Request Tool Guidance).

13. Once public release approval is obtained, the Navy ManTech Support Team works with ONR’s Corporate Strategic Communications to format the Project Book.

14. Navy ManTech Support Team reviews and edits the formatted Navy ManTech Project Book.

15. Navy ManTech Support Team completes a Clearance Request for Public Release of

Department of Defense Information NAVONR 5510/7 form for the entire Navy ManTech Project Book.

16. Navy ManTech Support Team uses the Public Release Request Tool to obtain approval of the Navy ManTech Project Book from ONR’s Public Affairs Office and Information Security Officer.

17. When final approval is received, the Navy ManTech Support Team publishes the Navy ManTech Project Book, posts it on the ONR website, and uses it for outreach activities.

D. DEFINITIONS OF DATA COLLECTED

The data collected is listed below.

Objective: The objective will give a brief background of the project with emphasis on the problem that needs to be solved and how the project will solve it. Include the weapon systems or other platforms to which the project is directed.

Payoff: This section will describe in narrative and quantitative terms the benefits of the project, including cost reduction, cost avoidance, performance enhancements, reduced manufacturing cycle time, and any direct benefits to the Warfighter.

Implementation – Plan and Target Dates: Describe the plan, as well as how, where, and when the results of the project will be implemented. Include specific implementation site names and quarter and fiscal year whenever possible.

Project Book Header: Describe the project by writing a short newsworthy title.

Period of Performance / Start and End Dates: The period of performance as specified in the contract or revised by modifications.

Platform(s): The specific ship or air focused initiative platform(s) that the project intends to affect.

COE Point of Contact: The name, phone number, and email of the COE Director.

Stakeholder: Typically, this is the Program Office sponsoring the project and whose weapon system will benefit from the results of the project.

Total ManTech Investment: The total ManTech funds, rounded to the nearest thousands, supplied by the Office of Naval Research, planned to be expended over the duration of the project excluding Cost Share / Leverage and other funding sources.

Project Graphic / Image: Image(s) supplied by COE or subcontractor illustrating technology being developed in the project.

E. FILE NAME

File names for Project Book write-ups should be in the following format: {COE acronym} Project Book {official project number} {complete official title of project} {MMMYY}.

i.e., EMTC Project Book A2720 Development of DNPD Manufacturing Process AUG 21

Attachment 1: Sample Project Book Write-up

Attachment 2: Stakeholders’ Document Release Concurrence Form

Attachment 3: Project Book Template