Deployment models
Choose processing/storage locations against data, devices, operations and agreed responsibilities.
Reference options
Managed digitization services; organizational deployments; private environments; hybrid station Edge and central services. These are assessment-dependent design options, not verified catalog SKUs.
Selection conditions
Define residency, site connectivity, content/metadata/evidence locations, operating permissions, signing/timestamp services where needed and export/exit. Each integration needs rights and compatibility verification.
Evidence-based NFR
Design/measure availability, latency, throughput and RTO/RPO against project loads/failures. No universal commitments are supplied; use the architecture NFR matrix to define measures/evidence.
Continue the workflow
Two journeys, one records lifecycle
Connect paper and born-digital records through persistent identifiers, policies and evidence.
Read detailsIntegration quickstart
Exercise ingest → job tracking → registration → verification with synthetic data.
Read detailsIntegrity, provenance and evidence
Each evidence type answers a different question; hashes, timestamps and approvals are not interchangeable.
Read detailsStart with a verifiable scope.
Agree record classes, quality criteria, permissions and evidence before scaling.
Plan assessment