THE PROBLEM

The requirements left with the people who wrote them

Core federal systems still run on code written decades ago, amended thousands of times, documented inconsistently and maintained by a shrinking group of people. The authoritative statement of what the system does is the source itself.

That is why modernization programs overrun. The discovery phase is a manual archaeology project, estimates are built on guesses, and the rules nobody found surface during testing — or after cutover.

What Changes
Discovery in weeks, not quarters

Automated analysis of the full codebase replaces a hand-read sample of it.

Estimates built on evidence

Complexity, coupling and dead code are measured, so scope and sequencing rest on real numbers.

Rules found before cutover

Business logic is extracted and reviewed while there is still time to decide whether to keep it.

CAPABILITIES

What Transkode does

Data lineage mapping

Traces every field from input through transformation to output, across programs, copybooks, files and tables.

Business rule extraction

Recovers the conditional logic that drives eligibility, calculation and routing, stated in terms an analyst can review.

Dependency analysis

Shows which programs call which, where the coupling is tightest, and what can be carved off first.

Dead code identification

Separates what still executes from what has not run in years, so you do not pay to migrate it.

Documentation generation

Produces the system description, data dictionary and process flows the program should have had all along.

Conversion support

Feeds the recovered specification into target-language implementation, with traceability back to the original program.

DEPLOYMENT

From kickoff to production

01
Assemble the source

Programs, copybooks, JCL, schemas and whatever documentation exists.

02
Analyze in your boundary

Source never leaves your environment; analysis runs on premises or in your cloud region.

03
Review with your SMEs

Extracted rules are validated by the people who still know the system.

04
Modernize

Prudent engineers carry the specification into the replacement build.

SECURITY

Source code never leaves

  • Analysis runs entirely inside your authorization boundary. No source, schema or data is transmitted externally.
  • Agency source code is never used to train or tune models.
  • Read-only access to repositories and libraries; Transkode analyzes, it does not modify production code.
  • Role-based access to findings, federated with your identity provider.
  • Air-gapped deployment supported for classified and restricted environments.
SPECIFICATIONS

Technical summary

Deployment
On premises, agency data center, authorized government cloud, air-gapped
Source languages
COBOL, PL/I, JCL, Natural, Assembler
Data stores analyzed
VSAM, DB2, IMS, flat files, relational targets
Target languages
Java, Python, .NET / C#
Outputs
Lineage maps, rule catalogs, dependency graphs, data dictionary, system documentation
Codebase scale
Million lines of code scaling linear
Licensing
Annual subscription or per-engagement, multi-year discounts available

Point it at the system nobody wants to touch

Give us one application. We will come back with its data lineage, its rules and an honest assessment of what replacing it would take.