Attch 20 Success Story Guidance.pdf

Navy ManTech Program

REV O OCT24

Success Story Guidance

Attachments:

1. Success Story Example

2. Success Story Template

3. NAVONR Form 5510/7 - Clearance Request for Public Release of Department of Defense

Information

4. Stakeholders’ Document Release Concurrence Form

A. PURPOSE

Success Stories are used by the Navy ManTech Program Office to brief the Chief of Naval Research (CNR), Office of Naval Research (ONR), Office of the Chief of Naval Operations (OPNAV), Department of Defense (DoD) / Office of the Secretary of Defense (OSD), Congressional staffers, and other government agencies to inform on a project’s success. These stories help capture the attention of senior management and provide outreach support for the Navy ManTech Program.

In most cases, Success Stories contain information that can be found in project Quads charts.

However, Success Stories should be presented in Microsoft Word format and contain information that is easily understood by all readers. Success Stories should be written in a style that is concise with emphasis on technical achievements and implementations. The title should be an attention-getting headline rather than the project name. Finally, Success Stories must be publicly releasable, marked “Distribution Statement A – Approved for Public Release,” and include the ONR contract number affiliated with the project. Therefore, the story should be written in a manner in which it can be released publicly.

B. REQUIRED TIMELINE

1. Initial Submission

Success Stories should be submitted as appropriate. A project does not need to be completed to submit a Success Story. Whenever a technical achievement or partial implementation has occurred or an implementation is pending, a Success Story should be submitted in accordance with Section C below in either the “Implemented,” “Pending Implementation,” or “Technical Success” category as defined in Section D below.

2. Annual Update All previous Success Stories for which new information is available should be updated by 1 Aug and submitted as outlined in Section C. Success Stories should continue to be updated annually after project completion until the status is either “Implemented” or “Technical Success” (As defined in Section D below).

C. PROCESS / APPROVAL CYCLE / PUBLIC RELEASE REQUEST TOOL (PRRT)

Success Stories, which are deliverables for Centers of Excellence (COE) with contracts, are required for all projects regardless of the type of project, unless the project results are restricted. If a COE supports another COE under a “-B” project, the lead COE will prepare the Success Story, and no Success Story is required from the supporting COE. However, the lead COE is required to work with the supporting COE to draft the Success Story and ensure that the Success Story reflects the technical efforts and achievements of both COEs.

See the Public Release Request Tool Guidance for instructions on how to submit the Success Story for public release. The materials listed below are required for each request:

• Story for release approval

• Clearance Request for Public Release of Department of Defense Information NAVONR 5510/7 form (see Attachment A)

• Stakeholders’ Document Release Concurrence Form (see Attachment B)

Once a Success Story has been approved for public release, COEs should upload it to the to appropriate folder under the Projects tab of the Navy ManTech Projects Database (NMPD). If the

NMPD is unavailable, it should be emailed to the PO/COR and the Navy ManTech Support Team (navymantech@bcsallegient.com). The Navy ManTech Support Team will upload the Success Story to the database.

D. TYPES OF SUCCESS STORIES

In developing needed manufacturing technology for key acquisition platforms, Navy ManTech ensures that technologies to be implemented are both producible and affordable. ManTech alone, however, cannot ensure implementation in a system. In order to delineate what Navy ManTech will accomplish as contrasted to what others must accomplish to achieve implementation, the following definitions are used:

• Transition: Point when the technology meets customer (Program Office / industry) criteria for implementation and the technology has been transferred to the industrial / naval organic facility.

• Implementation: Actual use of the ManTech results for the manufacture or repair of a platform / weapon system.

Consistent with these definitions, the Navy ManTech Program categorizes Success Stories into three types:

1. Implemented: The technology or process has been implemented or partially implemented and is in use in a production environment. Actual cost reduction or other benefits have been realized and are reported in the Success Story write up. (Note: An “Implemented” Success Story is appropriate whether or not the project has been completed.)

2. Pending Implementation: Transition has occurred and implementation is pending. The manufacturing technology or process has been successfully demonstrated, and there is a documented commitment to implement at an industrial facility and/or in a specific platform / weapon system. (Note: A “Pending Implementation” Success Story is appropriate whether or not the project has been completed.)

3. Technical Success: The project has achieved a technical milestone while the project is active or completed, or the project has successfully demonstrated the technology at the prototype level; however, the technology has not and is not expected to be implemented for any number of reasons including loss of stakeholder or platform support, missed window of opportunity, selection of another process or technology, etc.

E. FORMAT

Success Stories should be brief but “hard hitting” and submitted in Microsoft Word format with the general text font of Times New Roman 11 (font often reduced to 10 to fit text on one page – see Attachment 1). Indicate the benefit to the warfighter whenever applicable. Keep it simple so that the non-technical reader can easily understand. Be specific and quantitative. Include specifics on why, when, and where. Describe benefits quantitatively if possible.

All Success Stories should be marked “DISTRIBUTION STATEMENT A. Approved for public release: distribution is unlimited.” and include the ONR contract number affiliated with the project.

Success Stories should include the following information:

1. Status Indicate the appropriate type of Success Story as outlined above: Implemented, Pending Implementation, or Technical Success.

2. Problem / Objective Clearly state the problem solved or to be solved and the significance to the platform / weapon system. Clearly and simply state what has been or is being accomplished by the project, why it is important (the benefit to the Navy), who the customer is (the Program Office or sustainment activity and/or industrial facility that has implemented or is planning to implement the resulting manufacturing technology), and when (quarter and fiscal year) the implementation has occurred or is planned. Provide quantitative data whenever possible, such mailto:navymantech@bcsallegient.com as cost reduction, increase in strength, reduction in weight, improved cycle time, sustainability, etc.

3. Accomplishments / Payoff

• Process Improvements Concisely describe the approach used to successfully investigate the problem, develop the solution, and transition the results.

• Implementation and Technology Transfer Identify where and when implementation has occurred or will occur. Include the specific platform / weapon system(s) and/or industrial facility that have implemented or plan to implement this technology. Include any potential opportunities for implementation in other platforms / weapon systems or industrial facilities.

• Expected Benefits and Warfighter Impact Describe the results of the project and the benefits to be accrued by the implementing activity and/or the platform / weapon system. In the case of completed implementation, specify the benefits that have already been realized. Quantitative and/or qualitative benefits may include cost reduction, cost avoidance, reduced cycle time, and/or improved capability. Information presented could include cost reduction per platform / weapon system (with the total number that will utilize the technology), percent weight reduction per component or platform / weapon system and any associated cost reduction, environmental compliance, etc. Quantify the benefits whenever possible. Include the specific impact(s) the results of this project have had or will have on the warfighter. With current Navy ManTech Program emphasis on affordability, it is expected that the majority of new Success Stories will focus on cost-reduction benefits.

4. Timeline / Milestones Include the start and end dates (month and year) of the project. If the project included more than one phase, use the start date of Phase 1 and the end date of the final phase. You may include a timeline of any significant milestones or, for an active project, a short description of any significant milestones recently reached.

5. Funding Total Navy ManTech Investment Cost Leverage / Share – include funding source and dollar amount of funding. (Do not include this line if the cost leverage / share is $0.)

Additional funding categories may be included if they support the success of the project.

6. Participants List all significant participants (government entities, partners, contractors) who contributed to the project, including ONR Navy ManTech, which should be listed first.

7. Graphic Include a photo, drawing, or graphic appropriately depicting the manufacturing process or the product being developed or used to accomplish the project objective. Include a caption that explains the graphic.

F. REVISION REQUIREMENTS AND FILE NAME

1. Revision Requirements:

For improved document management, all Navy ManTech Success Stories will have both a Rev letter and MMMYY “stamp” in the left footer as shown in the template. Update each subsequent revision accordingly. As shown in the template, this footer should also contain the official Navy ManTech project number and the complete project title. Please submit Success Stories in Microsoft Word format.

2. File name convention:

File names for Success Stories should be in the following format: {COE acronym} SS {official project number} {complete official project title} Rev {letter} {MMMYY}.

• i.e., CMTC SS A2535 F-35 High Fidelity Fastener Feature Measurement REV B

JUL16.docx

Attachment 1: Success Story Example

Attachment 2: Success Story Template

Attachment 3: Clearance Request for Public Release of Department of Defense Information (NAVONR 5510/7 Form)

Attachment 4: Stakeholders’ Document Release Concurrence Form

Note: If more than one Success Story is being submitted, only one NAVONR 5510/7 form is required. In that case, Block 2 should contain “Various (COE Name) Success Stories,” and Block 3 should contain the number of Success Stories attached.