Program (Project) Plan - example

FOREWORD
The 'Program Plan shall be used to initiate a project and shall be maintained to provide an executive view of the system. The plan shall contain the project organizational structure and the objectives necessary to satisfactorily direct and manage the project.

CONTENT

1. SCOPE

1.1 Identification.

Identify the name of the project and any identifying abbreviation.

1.2 Purpose.

State the purpose of the system

1.3 Overview.

Provide a brief introduction to the project a summarize the contents of the document

1.4 Relationship to other plans.

Briefly describe the relationship of this plan to any other project or realizing system which affects this program.

2. REFERENCED DOCUMENTS

Reference the applicable documents and reports pertinent to the instigation or relevance to the project.

Examples

• MIL-STD-499A
• EIA IS-632
• DEF STAN 05-123
• ISO 9000
• etc.

3. ORGANIZATION AND RESOURCES

The program plan shall initially be prepared identifying the proposed project plans e.g., SEMP, SEMP, DMP, RMPP, etc.
The project plan shall contain organizational data. Include a diagram showing the project organization structure by title and name and a functional relationship to show lines of authority and communications.

Include here:

• Program organization diagram;
• A diagram showing the organizational structure by title and name;
• Identify the project/program office, partner companies, and any major suppliers/subcontractors.

Also provide:

• Project/functional organization relationship diagram;
• A diagram showing the relationship of project functions to functional organizations indicating lines of authority and communications.

4. OBJECTIVES

The objectives of the plan are defined in the following paragraphs

4.1 Criteria for evaluating engineering planning and output.

The following list the criteria by which the systems design, development, production, etc., shall be evaluated. This criteria shall be the basis for evaluation of individual program engineering planning and output.
Conformance shall be confirmed by review and audit when advised by the acquirer:

• Technical objectives: Technical objectives shall be established for the program so that meaningful relationships among need, urgency, risks, and worth can be established.
• Baselines: Functional, allocated, and product baselines shall be developed progressively. Appropriate documents shall be prepared in accordance with the "Documentation Standard".
• Technology: Specification requirements shall be delineated in light of acceptable technological risks defined by risk assessment;
• Realistic system values: Realistic Reliability, Maintainability, and other such system values shall be established prior to the start of the Engineering and Manufacturing development phase;
• Design simplicity: The concept of design simplicity and standardization shall be evident;
• Design completeness: The design shall be complete from a total system element viewpoint (hardware, facilities, personnel, computer software, procedural data);
• Documentation: The concept of minimum documentation shall be evident. Where possible stipulated plans, reports, and other data items shall be used to record the engineering outputs. The repository of this accumulated data will be defined. Engineering data shall be the sole source of performance requirements used in the design and production of the system;
• Engineering decision studies Engineering decisions regarding design alternatives and technical program shall reflect consideration of system cost effectiveness analysis based on the specified figure(s) of merit, performance parameters, program schedule, resource constraints, producibility, and life cycle cost factors;
• Cost estimates Cost estimates shall include acquisition and ownership costs. This shall include any established "design to" cost goals and current estimate of these costs;
• Technical task and work breakdown structure compatibility Elements of the Contract Work Breakdown Structure and associated technical tasks shall be identified and controlled in accordance with this plan and MIL-STD-881;
• Consistency and correlation of requirements System and technical program requirements shall be consistent, correlatable, and traceable throughout the Contract Work Breakdown Structure so that the impact of technical problems can be promptly determined and accurately appraised;
• Technical performance measurement Progress in achieving technical requirements shall be continually assessed. Problems and risk areas shall be identified;
• Interface design compatibility Intra-system and intersystem design compatibility of engineering interfaces shall be delineated as interface requirements in appropriate specifications. Interface control requirements and drawings relate to:
  1. the major system elements of the prime contractor's contractual responsibility (design responsible);
  2. other equipment, computer software, facilities, and procedural data furnished by the acquirer (customer);
  3. other program participants, shall be coordinated, established and maintained (Configuration Management).
• Clear lines of communication and timely dissemination of changes to these documents shall be maintained.
• Engineering specialty integration Engineering efforts such as Integrated Logistics Support (ILS), test engineering, production engineering, transportability, reliability and maintainability engineering, value engineering, safety engineering, electromagnetic compatibility, software engineering, standardization, etc., shall be integrated into the mainstream effort;
• Engineering decision traceability Significant engineering decisions shall be traceable to the system engineering process activities on which they were based;
• Historical data Historical engineering/operational data available to system designers shall be identified;
• Responsiveness to change Changes to system and program requirements in response to direct changes by the procuring activity, or problem solutions identified shall be evaluated for total program impact with respect to performance, cost, and schedules;
• Compatibility with related activities Engineering Management activities shall be compatible with related program management activities such as cost schedule control system criteria, contract administration, production management, etc.

At the request of the acquirer the contractor or a supplier shall make available the engineering management plans and procedures (PMS) and data for review to determine his capability to satisfy the requirements of this 'Program Plan'. The review shall comprise of demonstration and analysis of those features which are pertinent to the successful completion of the contractual requirements.

4.2 Engineering effort and SEMP.

A fully integrated engineering effort meeting the criteria defined in 4.1 above shall be planned an executed.

The contractor shall prepare an System Engineering Management Plan (SEMP) which will provide the necessary; Technical program planning and control; System engineering processes; and the integration and coordination of the project engineering efforts.

4.3 Tasks.

Detail the required tasks necessary to facilitate successful design and production of the system:

• Configuration Management
• Documentation Standard
• Project Risk Management
• Add additional tasks or programs required as necessary

5. ACTIVITIES AND SCHEDULE

Identify the Program Plan activities and provide timescales using PERT or similar graphical critical path method to show the estimated times for the tasks identified.
Provide the best estimate at the time of issue or revision of this plan

6. NOTES

(This Section contains information of a general or explanatory nature that may be helpful, but is not mandatory).

6.1 Intended use.

This @project Plan' identifies and defines the project requirements to establish engineering effort, SEMP, Criteria for review and audit, and additional management tasks.

6.2 Definitions used in this document.

6.3 Abbreviations.

6.4 Changes from the previous issue.

Under construction.

Back to Home page MANAGING STANDARDS Home page

Please send any beneficial comments, enquiries, or identification of errors using the following form to: kenr@wysywig.airtime.co.uk
.

Logmdion