person Author: Process Fellows
Not every file is automatically considered a Configuration Item (CI). To determine which item should be managed as a CI, clear criteria should be defined. These criteria help identify what qualifies for configuration management. As a result, different levels or degrees of configuration management may be established, depending on the importance, complexity, or impact of the items being managed.
Examples:

1. Level 1: Archiving Only: No version control, no formal change process.
   Purpose: The item is stored for reference or traceability.
   Examples: Meeting minutes, internal memos.
2. Level 2: Version Control: Each change creates a new version; changes are tracked and documented.
   Purpose: The item is actively maintained and updated over time.
   Examples: Specifications, plans, user manuals, source code.
3. Level 3: Baseline Inclusion: Changes require formal approval; baselines are used for configuration audits and traceability.
   Purpose: The item is part of a formally approved configuration baseline.
   Examples: Requirements baselines, software releases.