ENTERPRISE DATA LIFECYCLE™

A framework for managing
information according to
what it requires.

Enterprise Data Lifecycle™ defines a technology-independent framework for understanding information state, governance requirements, policy, and lifecycle transitions across the enterprise.

DOCUMENTS

Start with the overview.
Request the full specification.

The overview document is available directly. The full Enterprise Data Lifecycle™ Specification is distributed by request so Savartus can send the appropriate download link.

Download Overview

CORE PREMISE

Information lifecycle is
not storage lifecycle.

Traditional lifecycle models often infer information state from infrastructure characteristics such as age, access frequency, or storage tier. Enterprise Data Lifecycle™ separates the business state of information from its operational storage state.

LIFECYCLE STATE

What the information means to the business.

Business purpose, governance status, value, risk, obligations, and lifecycle stage.

OPERATIONAL STATE

How the information is currently managed.

Protection, availability, storage, security, retention, location, and other operational characteristics.

CANONICAL LIFECYCLE

One lifecycle.
Multiple operational states.

01Created
02Active
03Collaborative
04Managed
05Protected
06Archived
07Preservation
08Disposition Eligible
09Disposed

Lifecycle stages describe the business state of information—not where that information is physically stored.

ENTERPRISE DATA STATE VECTOR

Understand the state
before making the decision.

The Enterprise Data State Vector captures the dimensions required to evaluate information in context.

01Retention
02Protection
03Security
04Compliance
05Classification
06Integrity
07Availability
08Identity
09Relationships
10Storage
11Business Value
12Risk
13Confidence
14Provenance
15Location

POLICY-DRIVEN TRANSITIONS

Information moves when
its requirements change.

Lifecycle transitions are determined by policy and continuously reevaluated as information context, obligations, value, risk, and operational requirements change.

01

Deterministic

Decisions are based on explicit policy rather than hidden heuristics.

02

Continuous

Information state can be reevaluated as requirements change.

03

Explainable

Every lifecycle decision should have a clear policy basis.

04

Auditable

Lifecycle transitions and decision context can be recorded and reviewed.

WHAT EDL IS — AND IS NOT

A governance framework,
not a storage schedule.

EDL IS
  • An information lifecycle framework
  • Technology independent
  • Policy driven
  • Metadata aware
  • Business-state focused
EDL IS NOT
  • A storage-tiering algorithm
  • An age-based archive schedule
  • A vendor-specific storage model
  • A replacement for business governance
  • A synonym for data movement

ENTERPRISE DATA LIFECYCLE™

Manage information
according to what it requires.

Contact Savartus to discuss the Enterprise Data Lifecycle™ framework, reference architecture, and specification.