The problem
Modernization planning runs into the same wall every time: the business logic that matters is buried in decades-old COBOL, TAL, SCOBOL, and TACL. The people who understood it are retiring, and the documentation either does not exist or no longer matches the source.
NavigatorHow Navigator helps
Point Navigator at representative programs or the full codebase and it generates, from your actual source:
- Generates program documentation from source code
- Extracts business rules and validation logic
- Builds searchable knowledge across analyzed programs
- Supports plain-English Q&A through Chat Navigator
- Exports documentation packages for review, audit, onboarding, and modernization planning
AtlasHow Atlas helps
Navigator gives you the narrative. Atlas gives you the structural reality underneath it: architectural clusters, orphan programs, shared files, dependencies, and risk areas that shape modernization sequencing.
The workflow
- Run Navigator across representative programs or the full codebase.
- Generate source-based documentation and business-rule summaries.
- Use Chat Navigator to fill knowledge gaps before SMEs retire.
- Use Atlas to identify dependencies, orphan programs, shared files, and migration risk.
- Build a modernization roadmap grounded in both business logic and code structure.
Example scenario
Illustrative A typical workflow, not a specific customer result.
-
01
Trigger Two senior developers are retiring
An insurer preparing to modernize a claims system on HPE Nonstop (Tandem) needs the logic captured before the people who wrote it leave.
-
02
Navigator Document the codebase
Navigator runs across several hundred COBOL and TAL programs, generating documentation and extracting the premium-calculation business rules.
-
03
Chat Navigator Capture what only the experts know
Plain-English questions about the legacy logic get answered while the experts are still available, so the knowledge is held in the system rather than in people.
-
04
Atlas Map the real dependencies
Atlas flags orphan programs and shared Enscribe files that the documentation alone would not reveal.
-
05
Outcome Sequenced by dependency, not guesswork
The team plans the migration against the codebase's actual structure instead of assumptions about it.
