The repository shall have identified and documented critical processes that affect its ability to comply with its mandatory responsibilities.

This is necessary in order to ensure that the critical processes can be monitored to ensure that they continue to meet the mandatory responsibilities and to ensure that any changes to those processes are examined and tested.

Traceability matrix between processes and mandatory requirements.

Examples of critical processes include data management, access, archival storage, ingest, and security processes. Traceability makes it possible to understand which repository processes are required to meet each of the mandatory responsibilities.

Per bagging specification SIP must include bagit.txt, bag-info.txt, aptrust-info.txt and are verified before ingest.

Pharos records PREMIS event data and provides reporting on preserved objects

Fixity checks on objects in High Assurance every 180 days

Multiple storage locations and copies of AIPs are kept. 

5.1.1.2 Adequate hardware and software support for backup functionality sufficient for preserving the repository content and tracking repository functions

Double Fault Deletion Procedures

Extensive Logging and audit trails Technical Documentation

APTrust software code is kept in version control. Minor updates and changes are documented with every “commit” to the version control system.

Processes and infrastructure are monitored; see Monitoring and Alerting.

Restoration Spot Tests, 4.2.7.2 Execute testing process of Content Information of AIPs

Original Documentation Original Documentation OASIS

These are Key Performance Parameters. Let’s work on a better mapping matrix that identifies the functionality to meet this, as well as the specific processes in place. Some of these are functional requirements, and some are non-functional. But the above does do the basic trick. We DO need to update the pages in many case.