Sample outputs

See the shape of the assessment before scoping access.

These examples show the kind of inventory, dependency evidence, warnings, confidence, scoring, and planning outputs a pilot assessment is intended to produce.

380

Assets discovered

Systems, containers, reports, datasets, packages, jobs, models, tables, and selected components.

920

Dependency edges

Direct, parsed, and inferred relationships across reports, jobs, packages, models, views, and tables.

74

Warnings

Coverage gaps, unresolved references, redaction, circular patterns, and partial metadata signals.

3/5

Portfolio complexity

Simple external scoring with the drivers and caveats visible.

Mixed

Chain confidence

Direct and parsed evidence separated from inferred links, missing access, and ambiguous names.

Open

Investigation backlog

Unknowns are explicit follow-up questions, not hidden assumptions.

Deliverable types

The homepage output list maps to these sample surfaces.

A walkthrough should not only show counts. It should show how the inventory, dependency map, coverage report, complexity scorecard, recommendation signals, and readout pack work together.

Estate inventory

Source systems, containers, assets, components, schedules, and selected raw artifacts.

Dependency map

Direct, parsed, and inferred relationships with evidence IDs, confidence, and caveats.

Coverage report

Partial scans, inaccessible surfaces, unsupported patterns, and reduced-confidence areas.

Complexity scorecard

1-5 complexity and risk signals with explainable drivers rather than false precision.

Modernization recommendation

Retain-and-investigate, phased modernization, priority planning, rationalization candidates, and open questions.

Readout pack

CSV exports, printable summaries, and review notes for stakeholders, partners, or planning workshops.

Asset levels

One asset count can hide several layers.

  • Source system: SQL Server instance, SSRS server, SSISDB catalog, SQL Agent, SSAS Tabular server
  • Container: Database, schema, SSRS folder, SSIS project, SSAS model
  • Asset: Report, shared dataset, package, job, table, view, stored procedure, partition
  • Component: Report dataset, parameter, job step, package parameter, measure, partition query

Dependency reality

Chains are rarely straight lines.

A real estate may have tens or hundreds of reports, packages, datasets, tables, jobs, and models. Dependencies can be deep, repeated, ambiguous, or nearly circular. TangleMap is meant to expose that shape with caveats, not flatten it into a neat migration list.

Screenshot-style previews

Representative output surfaces.

These static previews show the kind of review surfaces a walkthrough should cover. Real client output should be redacted or synthetic before it becomes downloadable material.

Dependency review confidence-aware
SSRS report Finance / Month End Flash Uses shared dataset and stored procedure High
SSIS package Load_GL_Actuals Package parameter points to staging database Medium
SQL Agent job Nightly Finance Refresh Triggers package and validation procedure High
SSAS partition Actuals_Current Query reads view also used by report High
Warehouse view vw_FinanceActuals Referenced by model and report chain Medium
Caveat summary review required
  • Circular or near-circular dependencies may appear when reports, jobs, packages, models, and SQL objects reference the same business process from different directions.
  • Counts are not effort estimates by themselves. One report can hide several datasets, data sources, parameters, expressions, and downstream dependencies.
  • The output should help a reviewer decide where to trust the evidence, where to investigate, and where a business owner needs to validate use.

Example planning pack

A redacted output can support downstream planning or AI-assisted delivery frameworks with source systems, key assets, dependency edges, confidence, caveats, and follow-up questions.

Downloadable pack

A downloadable checklist or sample-output pack is a good lead-capture candidate, but the launch site currently uses a public checklist page. The gated download flow should be added once the form, consent copy, privacy wording, and follow-up process are decided.

Next step

Want to see the output shape?

Use a walkthrough to review sample deliverables, caveats, and interpretation before scoping a real pilot.