Critical operating knowledge is concentrated in a few people
One or two people know how the nightly jobs interact, which files are safe to touch, and why a program was patched in 2009. When they retire, the knowledge leaves with them.
Capture the system knowledge before it leaves with the people who hold it.
We map RPG programs, DB2 for i files, jobs, screens, interfaces, and operator knowledge into a practical modernization sequence without pretending IBM i itself is the problem.
- Duration30 days
- AccessRead-only discovery
- Agent in pre-productionNone installed
- You receiveA written roadmap
Program map · IBM iIllustrative
- ORD100R RPG
- PRCCHK RPG
- PRCMAST DB2
- INVUPD RPG
- INVMAST DB2
- CUSTLKP RPG
- CUSTMST DB2
- PRCCHK RPG
Nightly batch window
ARCHIVEINVBLDGLPOST?
Not written down: which job waits for which
Call tree traced from sourceBatch order surfaced
What the modernization map captures
Built from the system, its logs, and its operators
RPG programs & call chainsMapped to business capabilities
DB2 for i files & logicalsTraced to producers and consumers
Jobs, queues & transfersSequenced with timing and dependencies
Concentrated knowledgeScored by succession risk
Questions the readout answers
Which capabilities are one retirement away from being unmaintainable?
Where can an API seam expose data without changing RPG?
Which 5250 workflows are worth a modern interface?
What should stay on IBM i indefinitely?
The platform is rarely the whole problem.
Business rules, integrations, operator knowledge, support clocks, and unknown consumers determine the safest path. We map those constraints before recommending retention, integration, incremental replacement, or retirement.
Batch and file dependencies are poorly documented
Batch jobs, file transfers, and data queues form dependencies nobody has drawn. A change in one job can break a downstream process hours later.
Replacement plans confuse platform age with business risk
IBM i is not the risk. Undocumented programs, single points of knowledge, and closed interfaces are. The map separates the two so investment goes to the right place.
A decision-ready modernization blueprint.
Every engagement ends with a traceable estate view, a prioritized sequence, and explicit uncertainties your team can resolve.
Program and file map
Calls, files, jobs, screens, queues, transfers, and external consumers connected.
Succession-risk view
Capabilities with concentrated knowledge and fragile operating procedures prioritized.
Modernization map
A sequence for retaining, exposing, improving, or replacing capabilities based on evidence.
Scope. Scan. Verify. Roadmap.
The exception path comes before the happy path. Recommendations stay reversible until the evidence supports commitment.
Kickoff and scope
We show you our in-house analysis system, which scans code, repositories, and databases, and agree the estate, the people, and what you will receive.
NDA, access, and the scan
NDA signed and read-only access granted. Our system runs: data lineage traced, workflows identified, dependencies and consumers mapped.
Verify and weigh the options
Engineers verify the findings with your team. Retain, integrate, wrap, replace, or retire: practical paths compared with their tooling.
Roadmap and readout
Architecture, workflows, recommendations, risks, and a timeline with durations, documented and walked through with your decision makers.
30day assessment
Thirty days of read-only discovery and working sessions with your team. You finish with evidence, options, and a roadmap, not a sales proposal.
Start a 30-day assessment Scope: Fixed · Access: Read-only · Output: Written findings you keepA 30‑day modernization assessment. Six answers in writing.
Where your estate stands
Applications, code, data, jobs, interfaces, and the knowledge concentrated in a few people, documented from evidence.
What you can do about it
Retain, integrate, wrap, replace, or retire: options per capability with their trade-offs stated plainly.
Which tools will help
Where AI-assisted code analysis, test generation, and migration tooling speed the work up, and where they do not.
What to improve in the process
Release, testing, support, and ownership practices that decide whether a modernization sticks.
How to upgrade the legacy system
A target architecture and a reversible path to it, without betting operations on one cutover weekend.
How long it takes, and the roadmap
Phases, durations, dependencies, and decision points your board or steering group can approve.
See exactly what the 30 days deliver.
We email you the 2-page specification and a 13-page sample report written for a fictional company: findings, options compared, recommended tools, target architecture, risks, and a 40-week roadmap.
- Assessment specification
- 13-page sample report
- Architecture, risks, roadmap
Other enterprise assessmentsThe same 30-day method, tuned to a different platform.
Built and delivered by Trobus Technologies.
A Maryland-based engineering company. AICO Services is how we package our AI automation, modernization, and assessment work. Our engineers have delivered for organizations including these.
Organizations represented in the broader Trobus Technologies delivery history. Engagement scope and team role vary; reference details are shared where authorized.
Delivery recordRepresentative production engineering record. Details available where authorized.
4systems in production4 yrscontinuous operation990+automated tests1,361commitsCompany qualifications
Verified credentials maintained by Trobus Technologies, LLC
MBE
MDOT
SBA WOSB
WOSB
E-Verify
Build a defensible path beyond IBM i / RPG.
Bring the estate, the deadline, and the uncertainty. We’ll explain what can be learned safely before a modernization program begins. We will tell you when not to modernize it, and the assessment says so in writing.