Attachment J-12 - Project Plan Template.docx

Attachment J-12 Sample Project Plan N0002423R5108

PROJECT PLAN

FOR

BFTT FY23

DATE

Prepared for:

Naval Sea Systems Command

PEO IWS 1IT

Prepared by:

PEO IWS 1IT Support Team

SAMPLE

WARNING -This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et. seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 et. seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25."

Distribution Statement D: Distribution authorized to DoD and DoD contractors only, Critical Technology (XX July 2022). Other U.S. requests shall be referred to the Program Executive Office, Integrated Warfare Systems 7C and 2E for concurrent approval.

UNCLASSIFIED

TABLE OF CONTENTS

UNCLASSIFIED

Use or disclosure of data contained on this page is subject to the restriction on the title page of this document.

UNCLASSIFIED

Document Change Control This section provides control for the development and distribution of revisions to the Project Plan up to the point of approval. The Project Plan does not change throughout the project life cycle, but rather is developed at the beginning of the project (immediately following project initiation approval, and in the earliest stages of project planning). The Project Plan provides an ongoing reference for all project stakeholders. The table below includes the revision number (defined within your Documentation Plan Outline), the date of update/issue, the author responsible for the changes, and a brief description of the context and/or scope of the changes in that revision.

Project Overview This project plan is for BFTT Build 5.X series. This project plan will define the project goals and objectives, resources, budgets and timelines for the project.

This version aligns with TASK 2 the following Task Planning Sheet (TPS) Numbers:

· TPS IWS1.0NSWCDD0034611 rev 1 dated 6/3/2022 Purpose, Scope, and Objectives Efforts associated with the developmental efforts of BFTT Build 5.X series. This includes Requirements Definition Phase (Requirements documentation and Engineering Change Proposals, (ECP), Software Development Phase, IA Compliancy, Safety Engineering, Test and Evaluation Phase and Fielding plan coordination and SCD development to meet milestone scheduled events in support of AEGIS and SSDS combat systems planned upgrades The following ECPS will be implemented this year.

· Insert list of ECPs

The following fielded BFTT software basslines will be supported under the project:

· Insert list of BFTT baselines that require support Assumptions, Constraints and Risk s Define assumptions, constraints and risks for the project.

Project Metrics The financial project metrics will include planned, projected, and actual financial information.

Project Execution The project plan is the overarching planning document that will provide data to develop Task Planning Sheet (TPS), Technical Review Action Plan (TRAP).

The project technical and funding execution will align to the most current approved TPS.

The project reviews will be in accordance with (IAW) the Technical Review Manual Version 3 and the BFTT TRAP.

The project will follow Model Based System Engineering (MBSE) practices.

Stakeholders Stakeholder involvement is critical to the success of the project. The following are stakeholder organizations that must be included during the development of this project. This includes coordination with the following organizations in working groups and reviews.

· List stakeholders here (example below).

· OPNAV

· NAVSEA 05 Technical Warrant Holder

· PEO IWS 1

· PEO IWS 1IT

· PEO IWS 2E

· Surface Combat Systems Training Command (SCSTC)

· Naval Surface and Mine Warfighting Development Center (SMWDC)

· Fleet Forces Command (FFC)

· Navy Continuous Training Environment (NCTE)

· Naval Information Warfare Systems Command (NAVWAR) Evolution of the Plan As the project evolves, plans may requires a change. It is the responsibility of all personnel to periodically assess the project, in the context of their respective area of effort, to determine areas for improvement, and formally suggest changes to policies, plans, and procedures to Technical and/or Project Leads via written memorandum.

A Process Improvement Review will be convened no less than quarterly for the review of all Process Improvement Change submissions and implementation recommendations.

A record of change recommendations and disposition is to be maintained as part of the project archives.

The revised plan will be submitted and signed by PEO IWS 1IT and CSDA DNA.

Project schedule The following defines the high level project schedule. (example below).

· High level development schedule (milestone chart) something like the below or list with dates

Project budget Total Funding Requested: The table below defines the overall project budget.

Task Planning Sheet (TPS) included: TPS IWS1.0NSWCDD0034611 rev 1 dated 6/3/2022

$2,475,247

*1 FTE = 1880 hours.

The table below defines the breakout between direct cite and reimbursable.

$ 1,558,347

$ 916,900

*1 FTE = 1880 hours.

The following table details the planned travel for the project.

The following table details the planned subtasks, funding and FTEs across all TPSs associated with the project.

Subtask Category

Project Organization CDSA DNA will provide the technical and financial oversight for execution of BFTT. The following sections will detail the subtasks, staffing and financial posture. The follow sections detail the Project Team structure and tasking per TPS.

Project Team Personnel Structure - TPS IWS1.0NSWCDD0034611 Task Planning Sheet (TPS) included: TPS IWS1.0NSWCDD0034611 rev 1 dated 6/3/2022, TASK 2 BFTT 5.x FOS The project team is comprised of government and contractor personnel. The following table details the staffing, deliverables, and travel per subtask.

Subtask 2.1 BFTT PM/FM Manage efforts required to plan, award, administer, organize, staff, direct, control, and approve program financial and programmatic objectives and requirements. The following tables illustrate requested funding and deliverables.

$ 0

$ 0

$ 0

$ 0

$ 52,000

$ 52,000

Subtask 2.2 BFTT SE Provide System Engineering support to analyze if the requirements development for BFTT 5.X ECPs and requirements artifacts are applicable to AWS BL and SSDS fielding plans. Develop Specification Changes if there is new requirements identified in the revision. The following tables illustrate requested funding and deliverables.

$ 0

$ 0

$ 0

$ 6,700

$ 405,516

$ 412,216

**Direct Cite company is Huntington Ingalls, Inc (HII), Contract #N00178-14-D-7650 / N0017818F3011, Start Date 8/28/2022, End Date 8/27/2023, Insert option year info

Subtask 2.3 BFTT SSA Conduct the management of tasks and resources related to new capability software design and development for Battle Force Tactical Training (BFTT) software. Maintain software development plans, schedules, and risks related to new capability software development. The following tables illustrate requested funding and deliverables.

$ 0

$ 0

$ 0

$ 3,500

$ 905,419

$ 908,919

* Direct Cite company is Lockheed Martin, Contract #N0017804D4079/N0017819F3001, Start Date 3/20/2022, End Date 3/19/2023, Insert option year info

Subtask 2.4 BFTT T&E Provide Test and Evaluation engineering efforts associated with BFTT Build 5.X FoS. Deliverables support the Test and Evaluation Phase to include technical and cost reviews of Engineering Change Proposals (ECPs) supporting BFTT 5.x milestones. The following tables illustrate requested funding and deliverables.

$ 0

$ 0

$ 0

$ 18,000

$ 608,316

$ 626,316

2.44

**Direct Cite company is Huntington Ingalls, Inc (HII), Contract #N00178-14-D-7650 / N0017818F3011, Start Date 8/28/2022, End Date 8/27/2023, Insert option year info

Subtask 2.5 BFTT CS Provide IWS 1IT Program Management with Cybersecurity Engineering. This includes: Develop Defense in Depth Reference Architecture, Validation/Vulnerability Scans, IA Risk Database, RMF Package Preparation and Document/Evaluate Cross Domain Interfaces for BFTT FoS (AN/USQ-T46, AN/USQ-T47, AN/USQ-T48, VTBsr, etc.). The following tables illustrate requested funding and deliverables.

$ 0

$ 0

$ 0

$ 3,000

$ 209,396

$ 212,396

**Direct Cite company is Huntington Ingalls, Inc (HII), Contract #N00178-14-D-7650 / N0017818F3011, Start Date 8/28/2022, End Date 8/27/2023, Insert option year info

Subtask 2.6 BFTT Safety This tasking supports a MIL-STD-882E compliant safety program for the BFTT engineering effort to support the Training Systems Directorate (PEO IWS 1IT) in the area of System Safety Engineering. Provide Principal for Safety (PFS), system safety engineering. The following tables illustrate requested funding and deliverables.

$ 0

$ 0

$ 0

$ 2,500

$ 169,400

$ 171,900

**Direct Cite company is SAIC, Need contract number, Start Date, End Date, Insert option year info

Subtask 2.7 Contract Fee CONTRACT FEE. The following tables illustrate requested funding and deliverables.

$ 0

$ 0

$ 91,500

$ 0

$ 0

$ 91,500

Project Tracking Project tracking will be accomplished via monthly report and periodic status reviews.

Monthly Reporting The monthly report will contain Technical Progress Report and a Financial Report. See Appendix A for technical progress report template. See Appendix B for financial progress report template.

The Technical Progress Report will consist of:

Narrative of technical accomplishment during the reporting period.

Narrative of travel performed during the reporting period.

Narrative of meetings attended/supported during the reporting period.

Narrative of technical accomplishment planned for the next reporting period.

Summary of current risks as well as mitigation plan.

Project deliverables completed.

The Financial Report will consist of:

Planned Funding for the Project.

Actual Funding Received.

Planned Expenditure.

Actual Expenditure.

Deliverable Acceptance Deliverables will be submitted for formal acceptance via deliverable memo to include artifact name, TPS number, Task Number, Subtask number, and comments requested by date (if applicable). See Appendix C. Deliverables will be placed in a PMO designated location for archiving.

Product Acceptance Deliverable acceptance occurs when the item is part of a baseline that is formally qualified and demonstrated with customer approval. Testing, demonstration, analysis, and inspection are all acceptable methods in qualifying requirement completion. Formal acceptance will be required by the PMO for acceptance.

Status Reviews Status reviews will be conducted IAW with the BFTT TRAP.

Acronyms list

Appendix A – Monthly Techincal Report Outline Embedded is an example of the expected contents for the monthly Technical Report.

Appendix B – monthly financaial Report Outline Embedded is an example of the expected contents for the Monthly Financial Report.

Insert financial report example

Appendix C – Deliverable acceptance example Embedded is an example of the expected contents for a deliverable acceptance letter.

image1.jpeg image2.emf image3.emf

BFTT%20Project%20Plan%20Monthly%20Report%20Example%20.docx

Monthly Report

For

BFTT 5.x Family of Systems

Submitted on xx xx xxxx

Prepared for:

Program Executive Office, Integrated Warfare Systems

Training System Directorate (PEO IWS 1IT)

1333 Isaac Hull Ave. S. E.; Washington Navy Yard

Washington, DC 20376

Prepared by:

Naval Surface Warfare Center, Dahlgren Division, Dam Neck Activity Surface Training Systems Branch, Code R24

1922 Regulus Avenue

Virginia Beach, VA 23461

DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD contractors only; critical technology use; Date. Further dissemination only as directed by NSWCDD R20, 17214 Avenue B Suite 123, Dahlgren, VA 22448

FOR OFFICIAL USE ONLY

SYSTEMS ENGINEERING PLAN

DESTRUCTION NOTICE: For classified documents follow the procedures in DoD 5220.22-M, Industrial Security Manual, Section II- 19, or OPNAVINST 5510.1H, Chapter 17. For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document

FOR OFFICIAL USE ONLY

FOR OFFICIAL USE ONLY

BFTT 5.x FAMILY OF SYSTEMS

MONTHLY REPORT

SUBMITTED TO

Mr. Thomas Brady

IWS 1IT, Integrated Training Chief Engineer (CHENG)

Program Executive Office, Integrated Warfare Systems

Training System Directorate (PEO IWS 1IT)

1333 Isaac Hull Ave. S. E.; Washington Navy Yard

Washington, DC 20376

SUBMITTED BY

BFTT 5.X Lead

Naval Surface Warfare Center, Dahlgren Division (NSWCDD) Dam Neck Activity (DNA), R20 Project Lead, CIAT to Sea (C2S)

Date

TABLE OF CONTENTS

1 Summary of Effort 1

2 Work Performed 1

2.1 TASK 2 – BFTT 5.x FoS 1

2.1.1 Subtask 2.1: BFTT PM/FM 1

2.1.2 Subtask 2.2: BFTT SE 1

2.1.3 Subtask 2.3: BFTF SSA 1

2.1.4 Subtask 2.4: BFTT T&E 1

2.1.5 Subtask 2.5: BFTT CS 1

2.1.6 Subtask 2.6: BFTT SAFETY 1

2.1.7 Subtask 2.7: Contract Fee – N/A 1

3 Travel Conducted 1

4 Project watch items, risks, and issues 2

4.1 Project Watch Items 2

4.1.1 Watch Items 2

4.1.2 Watch Item Mitigation Strategy 2

4.1.3 Watch Item Impacts 2

4.2 Project Risks Items 2

4.2.1 Risk Items 2

4.2.2 Risk Mitigation Strategy 2

4.2.3 Risk Impacts 2

4.3 Issues 2

4.3.1 Issue Identification 2

4.3.2 Issue Impacts 2

5 GFE/GFI Requests 2

6 Artifacts Delievered 2 v

Summary of Effort

Insert summary of work performed

Work Performed

TASK 2 – BFTT 5.x FoS

The follow sections detail the work performed for each subtask under Task 2 for the reporting period.

Subtask 2.1: BFTT PM/FM

Summary of work performed under the subtask for this reporting period.

Subtask 2.2: BFTT SE

Summary of work performed under the subtask for this reporting period.

Subtask 2.3: BFTF SSA

Summary of work performed under the subtask for this reporting period.

Subtask 2.4: BFTT T&E

Summary of work performed under the subtask for this reporting period.

Subtask 2.5: BFTT CS

Summary of work performed under the subtask for this reporting period.

Subtask 2.6: BFTT SAFETY

Summary of work performed under the subtask for this reporting period.

Subtask 2.7: Contract Fee – N/A

This section is left blank.

Travel Conducted

List the travel dates, subtask supported, purpose of trip and outcome for this reporting period.

Travel Dates

Subtask Supported

Purpose of Trip

Outcome

Project watch items, risks, and issues

Project Watch Items

The following sections will detail watch items, mitigation strategies and impacts identified for this reporting period.

Watch Items

Describe any project watch items identified for this reporting period.

Watch Item Mitigation Strategy

Describe the project watch items mitigation strategies.

Watch Item Impacts

Describe the project watch items impacts.

Project Risks Items

The following sections will detail risks, mitigation strategies and impacts identified for this reporting period.

Risk Items

Describe any project risks items identified for this reporting period.

Risk Mitigation Strategy

Describe the project risk items mitigation strategies.

Risk Impacts

Describe the project risk items impacts.

Issues

The following sections will detail project issues and impacts identified for this reporting period.

Issue Identification

Describe any project issues identified for this reporting period.

Issue Impacts

Describe any project issues impacts for this reporting period.

GFE/GFI Requests

List any GFE/GFI Requests for this reporting period.

Artifacts Delievered

List artifacts and delivery dates that occurred for this period.

C-1 image4.emf

Deliverable%20submission%20example.docx

(Date here)

Naval Sea Systems Command

PEO IWS 1IT

1333 Isaac Hull Avenue, SE

Washington Navy Yard, DC 20376-4601

Attention: Mr. Thomas Brady

Subject: Submission (name of artifact) under TPS:XX ,Task XX, Subtask XX.

Dear Mr. Garcia, CDSA DNA has delivered the (artifact name here).

(No comment is required or comments are requested by xx date). At your earliest convenience, please sign and date the bottom of this letter to acknowledge receipt of the above stated document. Email the signed acceptance to my attention at email address here.

Please don’t hesitate to contact me if I can be of any further assistance.

Regards, PM Name or digital signature

ATD Project Manager cc:

IWS 1IT support staff

Transmission Receipt Acknowledged By: Date:

Thomas Brady, IWS 1IT CHENG

Training Systems Engineer