Plan for the management of project
Data are forms of documentation required to
support a project in all of its areas (e.g., administration, engineering,
configuration management, finance, logistics, quality, safety,
manufacturing, procurement). The data can take any form (e.g., reports,
manuals, notebooks, charts, drawings, specifications, files,
correspondence). The data may exist in any medium (e.g., printed or drawn
on various materials, photographs, electronic, or multimedia).
Data may be deliverable (e.g., items identified
by a projectís contract data requirements) or data may be nondeliverable
(e.g., informal data, trade studies, analyses, internal meeting minutes,
internal design review documentation, lessons learned, or action items).
Distribution can take many forms, including electronic
Data requirements for the project should be
established for both data items to be created and their content and form,
based on a common or standard set of data requirements. Uniform content
and format requirements for data items facilitate understanding of data
content and help with consistent management of data resources.
The reason for collecting each document should
be clear. This task includes the analysis and verification of project
deliverables and nondeliverables, data requirements, and customer-supplied
data. Often, data are collected with no clear understanding of how they
will be used. Data are costly and should be collected only when
- Data management plan
- Master list of managed
- Data content and format
- Lists of data requirements for acquirers and
- Privacy requirements
- Security requirements
- Security procedures
- Mechanisms for data retrieval, reproduction,
- Schedule for the collection of project
- List of project data to be
- Establish requirements and procedures to
ensure privacy and the security of data.
Not everyone will have the need or clearance
necessary to access project data. Procedures must be established to
identify who has access to which data as well as when they have access
to which data.
Requirements and procedures may cover service staff
who will have the responsibility for the security of data under the
terms of a service agreement.
- Establish a mechanism to archive data and to
access archived data.
Accessed information should be in an understandable
form (e.g., electronic or computer output from a database) or
represented as originally generated.
- Determine the project data to be identified,
collected, and distributed.
- Determine the requirements for providing
access to and distribution of data to stakeholders.
A review of other elements of the project
plan may help to determine who requires access to or receipt of project
data as well as which data are involved.
- Decide which project data and plans require
version control or more stringent levels of configuration control and
establish mechanisms to ensure project data are