Attachment 12 Navy ManTech Code 33 Monthly Report Guidance.pdf

PDF 621 KB Posted

Attached to
EOC 4
Solicitation number
N0001425R7001
Issued by

About this file

This document is a guidance document for the Navy ManTech Program's Code 33 Monthly Report, providing detailed instructions for Centers of Excellence (COE) to submit monthly activity reports to the Code 33 Division Director.

The guidance specifies that COEs must submit reports by the 20th day after each month using a provided PowerPoint template. Key required elements include: month/year, contract period of performance, project status metrics (active, completed, initiated, under development), key accomplishments, issues requiring elevation, supporting images with captions, and funding status (expected funding, expenditure estimates and actuals). The process involves the Navy ManTech Support Team providing templates, COEs updating sections marked in red (to be changed to navy blue), submission to Program Officers/CORs for review, and final upload to the Navy ManTech Projects Database. The document includes strict formatting requirements prohibiting template modifications and specifies the file naming convention as "{COE acronym} Code 33 Monthly Report {MMMYY}". An example report from the Energetics Manufacturing Technology Center (EMTC) is included showing proper formatting and content structure.

View the file

Other files

File Type Posted
EOC RFP 28 Feb 2025 Amemndment 1.pdf PDF
EOC RFP 28 Feb 2025 Amemndment 2.pdf PDF
Attachment 1 EOC 4 SOW_2-25-2025.pdf PDF
Attachment 27 Cost Information 2.xlsx XLSX spreadsheet
Questions for EOC 4 24 Feb 2025.xlsx XLSX spreadsheet
Questions for EOC 4 24 Feb 2025 2.xlsx XLSX spreadsheet
Attachment 27 Cost Information 2.docx DOCX document
Attachment 26 Cost Proposal Cost Plus Fixed Fee.xlsx XLSX spreadsheet
Solicitation - N0001425R7001 Page 1.pdf PDF
Attachment 27 Cost Information.docx DOCX document
Attachment 25 B Project CDRLS.pdf PDF
Attachment 8 Final Report Guidance.pdf PDF
Attachment 24 A COE CDRLS.pdf PDF
EOC RFP 13 Feb 2025.pdf PDF
Attachment 22 Trip Report Guidance.pdf PDF
Attachment 20 Success Story Guidance.pdf PDF
Attachment 18 Quarterly Report Guidance.pdf PDF
Attachment 19 Rapid Response and Special Projects Guidance.pdf PDF
Attachment 23 CDRL Instructions for Distribution.pdf PDF
Attachment 9 Funding Allocation Spreadsheet Guidance.pdf PDF
Attachment 5 Instructions to Complete Review Forms.pdf PDF
Attachment 4 Annual Review Project Briefing Template.pdf PDF
Attachment 10 Implementation Risk Assessment Guidance.pdf PDF
Attachment 7 COE Transition Implementaion Guidance.pdf PDF
Attachment 21 Technology Transition Plan Guidance.pdf PDF
Attachment 15 Project Quad Chart Guidance.pdf PDF
Attachment 6 Benefits and ROI Guidance.pdf PDF
Attachment 1 EOC 4 SOW.pdf PDF
Attachment 3 Navy ManTech Program Annual Data Call.pdf PDF
Attachment 13 Project Book Guidance.pdf PDF
Attachment 14 Project Briefing Guidance.pdf PDF
Attachment 16 Proposal Pipeline and ONR Contratracts Action Spreadsheet Guidance.pdf PDF
Attachment 17 Public Release Tool Guidance.pdf PDF
Attachment 2 Affordability Assessment Guidance.pdf PDF
Attachment 11 Key Personnel.pdf PDF
Show all 35

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Navy ManTech Program

REV G OCT24

Code 33 Monthly Report Guidance

Attachments:

1. Code 33 Monthly Report Template

2. Monthly Report Example

A. PURPOSE

The intent of the Code 33 Monthly Report is to provide a concise, high-level snapshot of Center of Excellence (COE) activities for the reporting month. The intended audience is the Code 33 Division Director.

B. TIMELINE

All COEs should update and submit the Code 33 Monthly Report on or before the 20th day after every month of the fiscal year.

C. PROCESS

The following steps outline the process for the submittal and approval of the Code 33 Monthly Report:

1. Navy ManTech Support Team provides the initial Code 33 Monthly Report template to each COE.

2. COE updates the sections of the template that are displayed in red font. Do not include information or images that are restricted, sensitive, or marked Controlled Unclassified Information.

3. COE emails the Code 33 Monthly Report to its respective Program Officer (PO) / Contracting Officer’s Representative (COR) and the Navy ManTech Support Team (navymantech@bcsallegient.com).

4. PO/COR and the Navy ManTech Support Team review the Code 33 Monthly Report, working with the COE to adjudicate any questions or comments, if necessary.

5. COE uploads the final Code 33 Monthly Report to the COE page of the Navy ManTech Projects Database (NMPD) if available. The Navy ManTech Support Team uploads a copy of the Code 33 Monthly Report if the database is unavailable.

6. The Navy ManTech Support Team combines the monthly reports for all of the COEs and Naval Surface Warfare Center – Carderock Division into one slide deck, emails the combined file to the ManTech POs / CORs, and uploads the report to the Program page of the Navy ManTech Projects Database and ONR ManTech R:\drive site.

D. FORMAT

The Navy ManTech Support Team will provide each COE with a PowerPoint template from which to update each month. Do not change the font, style, or format of the template. Do not add words to the template headings. Do not submit the report as a PDF.

The following items, which are shown in red font on the template, should be updated each month. Note that the red font color should be changed to navy blue font in the monthly report.

Month / Year – Include the month year that the report covers, e.g., Feb 2024.

Contract POP – Provide in Mon Year – Mon Year format. The contract period of performance only needs to be updated if it changes. If the COE doesn’t execute under a contract, include something comparable.

Status for the month – Add the current number for the following:

o projects active o projects completed o projects initiated o projects under development

Key COE/project accomplishments for month – Provide succinct, high-level accomplishments achieved during the reporting month. The project number, project name, and platform should precede the accomplishment in italic if the accomplishment is project-related, e.g., M2854

– Automated Pipe Fitting Scriber (DDG 51). See the example on page 4. Do not provide technical data or information that is restricted, sensitive, or marked Controlled Unclassified Information. Be brief.

Issue – Only include an issue if ManTech can’t address it and the issue needs to be elevated. If no issues, include “None.”

Image – Insert an image that supports one of the listed accomplishments. Do not include images that are restricted, sensitive, or marked Controlled Unclassified Information.

Caption – Write a brief caption that describes the accomplishment. The project number should precede the caption, e.g., M2854 - Successful demonstration of the prototype at BIW validates the unit for future production use on DDG 51. See the example on page 4.

COE Funding Status – Add the current amounts for the following. Funding received to date for the current fiscal year is not required.

o Expected ManTech Funding in FYXX – Include the expected ManTech funding for the current fiscal year.

o ManTech Expenditure Estimate (Mon Year) – Include the month and year for the expenditure estimate. The month and year are the same as the month and year of the Code 33 Monthly Report.

o ManTech Expenditure Actuals (Mon Year) – Include the month and year for the expenditure actuals. The month and year are the same as the month and year of the Code 33 Monthly Report.

Footer Information – Update the Month and Year of the report in the footer.

E. FILE NAME

The file name for the Code 33 Monthly Report should represent the most recent update. The file name should use the following format: {COE acronym} Code 33 Monthly Report {MMMYY} i.e., EMTC Code 33 Monthly Report SEP24.pptx

Attachment 1: Code 33 Monthly Report Template

Attachment 2: COE Monthly Report Example

File details come from the government source that posted it. Updated .