JANUS

JANUS buyer’s guide

Planning a Mobius or ViewDirect archive evaluation?

Updated 1 October 2026

An archive decision deserves more than a feature checklist. Start by understanding which records, business processes, and obligations must carry forward.

Where should an evaluation begin? Confirm the exact product, version, and deployment in use, especially when a team uses historical names such as ASG Mobius or ViewDirect. Then assess JANUS against the specific report-management workload. Migration feasibility and extraction methods must be validated for that environment.

Start with current product information

Rocket Software presents Mobius as an enterprise content services platform for modernizing and governing business information, and describes ongoing enhancements. Source: Rocket Mobius. This guide does not treat the product as end-of-life or assume it lacks governance, integration, or modernization capabilities.

Define the part of your environment under review

Some evaluations focus on a report repository. Others cover wider content services and connected business processes. JANUS should be considered for the report, document discovery, distribution, and records-governance requirements it can demonstrate. Identify additional capabilities separately so a narrower pilot is not mistaken for complete platform equivalence.

AreaQuestions to resolveAcceptance evidence
Archive inventoryWhich report families, formats, historical periods, and resources are in scope?An agreed inventory and representative samples.
Content accessHow can authorized owners export documents and associated metadata from the deployed environment?A supported, repeatable sample extraction and reconciliation.
Document contextWhich indexes, business identifiers, and relationships must remain usable?Representative records found using business-relevant details.
Users and channelsWho consumes reports, through which applications, and with what restrictions?An approved access map and demonstrated delivery journeys.
GovernanceWhich retention rules, holds, and recorded histories must be preserved or referenced?Policy mapping, hold tests, and an agreed evidence-retention approach.

A phased migration assessment

  1. Choose one meaningful report family. Select a bounded workload that includes real business requirements and representative historical records.
  2. Validate the exported package. Include documents, metadata, and required resources. Record missing or unsupported items as findings.
  3. Assess the JANUS experience. Test retrieval, presentation, access scope, retention, and the required distribution path.
  4. Reconcile and review. Establish record completeness and review exceptions with business, technology, and governance owners.
  5. Decide whether to expand. Agree on the remaining work, costs, rollback approach, and acceptance criteria before proposing a broader transition.

What a useful comparison should contain

A fair comparison separates documented capabilities, verified pilot results, configuration choices, and open questions. Request demonstrations against the same workload. Include export effort, historical data handling, integration work, support expectations, and operating costs in the evaluation.

JANUS does not promise an automatic Mobius or ViewDirect conversion in this guide. The assessment determines the practical approach and any work required.

Explore the requirements first

Understand content services and records management · Build a banking report-management pilot

This independent guide uses Mobius, ASG Mobius, and ViewDirect names only to identify systems a buyer may be evaluating. No vendor affiliation or endorsement is implied. Current Mobius positioning was checked against Rocket Software’s product page on 1 October 2026.