Begin with the repository’s jobs
Inventory transaction-linked documents, records-controlled content and working or reference material. A repository can contain one or several of these; do not assume the workload mix. Identify the business owner, interfaces, security, retention requirements and retrieval expectations for each group.
The browser readiness check can organize discovery questions. It does not read a live repository or certify a replacement design.
Keep the shortlist evidence-based
Possible candidates include a supported WebCenter upgrade, a hosted WebCenter deployment, another ECM product, a domain-specific system or an existing collaboration service. Product categories do not determine capability. Ask each candidate to demonstrate the required configuration and integration, including any separately licensed modules or custom work.
Managed Attachments, Records controls and Content storage options provide concrete incumbent capabilities to inventory. Their existence does not prove every estate uses them or that an upgrade needs no adaptation.
Score every candidate on the same dimensions
| Dimension | Evidence to request |
|---|---|
| ERP integration | Supported interfaces, record-key mapping, authorization and tested user actions |
| Historical continuity | Required documents, revisions, metadata and audit evidence remain retrievable |
| Security | Allowed and denied access, identity integration and administrative controls |
| Records | Approved retention, holds, disposition and evidence preservation |
| Processing | Required intake, extraction, workflow and exception behavior |
| Migration | Method, reconciliation, downtime, coexistence and recovery plan |
| Operations and cost | Ownership, support, monitoring, licensing, infrastructure and maintenance |
Score unknowns as unknowns. Do not give the incumbent automatic full marks because its configuration exists, or a replacement full marks because its datasheet names the same feature.
Test the uncertain requirements
Select representative documents, record associations, permission cases and integration failures. Ask for the same demonstrations from each candidate. Include migration and recovery feasibility rather than evaluating only a new empty repository.
Decide whether one platform or separate systems better meets the workload requirements. Any split needs explicit ownership and cross-system retrieval; consolidation needs evidence that the combined controls remain workable.
ECMWorks can help produce a requirement inventory and comparison with recorded gaps. The WebCenter modernization overview places the repository decision alongside capture, recognition, workflow and ERP plans.