Own analysis toolset · On-site package · 2-day assessment · Fixed price

IT landscape analysis with COMPIDDA: fixed-price 2-day assessment

When nobody knows exactly any more which program depends on which data, every change becomes a risk. In two days on site I make this visible, and your team gets an overview with a source location for every connection.

Databases, stored procedures, SSIS packages, agent jobs and applications that grew over decades can turn into a “black box”. When that happens, or when key people retire, guesswork is not enough. With my locally running software toolset COMPIDDA I make all technical dependencies of your system landscape visible deterministically – down to the exact line of code.

Request a COMPIDDA assessment See the process

100% local on your premises deterministic no cloud no AI Non-disclosure agreement (NDA) in advance
Triggers

When a landscape analysis pays off

Before a rebuild

Before grown or orphaned databases and applications are rebuilt, it must be clear which procedures, views, jobs, SSIS packages and C# application accesses are affected.

Legacy replacement & migration

Nobody dares to touch the grown procedures and systems any more? The assessment reads all dependencies automatically and documents them on site – the basis for disentangling step by step.

Retirement & island knowledge

Protection against knowledge loss when key staff retire or leave (“island knowledge”); new requirements become plannable again.

Process

Two days on site

Day 1 · On-site scan & connection Runs locally on your systems (100% on-premises, no cloud, no AI). Reads up to 19 source types (MS SQL, T-SQL AST, views, procedures, jobs, SSIS, C#/.NET, configuration files).
Day 2 · Impact analysis & handover Exact typing (read R, write W, execute X), joint review of the critical nodes, briefing of your team and handover of the interactive documentation.
What you receive

See what depends on what – with source location

COMPIDDA reads database objects and source code and documents the dependencies as a diagram with exact source locations.

  • Dependency diagram: read/write/call typing down to the source location – which procedure calls which, where views, jobs or C# applications access data.
  • Interactive documentation, handed over to your team with a briefing.
  • Joint review of the critical nodes.
  • Open points visibly marked: anything that cannot be resolved unambiguously stays visibly marked; the business assessment remains with the people responsible on your side.
Dependency diagram of a grown software and database landscape, created with COMPIDDA
Dependency diagram · read/write/call typing down to the source location Full view ↗
Fixed price · Comparison in person-days

In my experience, it saves 30 to 40 internal person-days

A product in its own right, initiated by me: COMPIDDA is not part of my freelance day rates but a separate product with its own offer and fixed price. I recognise in a project where a landscape analysis is needed, initiate the assessment and carry it out on site.
What it costs, in your currency: If one of your own IT staff reviewed and documented a typical area (around 20 programs, 20 data stores) by hand, that would, in my experience, tie up 30 to 40 person-days, spread over weeks or months. They would first have to build a documentation method, would be unavailable for their actual work all that time, and the result goes stale without upkeep. The assessment is the opposite of a drawn-out project: two days on site, and your staff are needed only for the business interpretation. The result is more reliable than any manual survey, because every relationship has a source location and every gap is visibly marked. The fixed price is deliberately below the value of those person-days; I name the figure in the initial call.
Security

100% local, deterministic, no cloud, no AI

The analysis runs entirely on your premises and works deterministically, without AI hallucinations. Anything that cannot be resolved unambiguously stays visibly marked; the business assessment remains with the people responsible on your side.

How COMPIDDA reads T-SQL, SSIS packages, SQL jobs, SSRS reports and C#/.NET data access is described in detail under database optimisation. Technical details on COMPIDDA →

In practice: how I was responsible for a 24/7 platform as technical app owner is shown in the NXP Semiconductors case study.

Is a rebuild, a replacement or a retirement coming up?

Briefly describe which systems are affected. In the initial call (20 minutes) we clarify whether the assessment is worthwhile.

Request a COMPIDDA assessment → View profile

Should your team ship releases itself? DevOps coaching · Is the database slowing you down? Database optimisation