Phase 1: Discovery, Requirements & Architecture Blueprint
ERP sources, spreadsheet workflows and manual financial reports are inventoried before the EDW architecture is designed.
Three pillars. Twelve focused engagements.
DevNord builds EDW architecture and ETL pipelines that feed Power BI dashboards & financial reporting, Power Apps (Canvas & Model-driven), Power Automate and Dataverse connected to D365/AX. We add SharePoint integration, custom portals and automated document workflows, with one governed reporting model and Playwright regression coverage for the journeys that finance relies on.
This is the service-specific architecture we design and operate. Inspect any node to see its role, the engineering or QA control around it, and how risk is contained.
Tap any node to inspect it.
Hover over a node to inspect it.
Node inspectorSelect any component to see what it does, which control protects it and how we hand it over.
An indicative 12-week cadence for a full engagement. The exact calendar, milestones and price are fixed in your EUR (€) or SEK (kr) proposal after discovery.
Indicative cadence — finalised in your fixed-scope proposal
ERP sources, spreadsheet workflows and manual financial reports are inventoried before the EDW architecture is designed.
One governed reporting model and the first ETL pipelines land with row counts and source reconciliation.
Dataverse connected to D365/AX carries workflow state for Power Apps (Canvas & Model-driven), Power Automate and automated document workflows.
Power BI dashboards, custom portals and SharePoint integration pass manual UAT and a Playwright QA gate; 30 days of hypercare follow go-live.
Every engagement runs with the same operating model: senior squads, transparent ownership and written evidence at every gate.
Two-week sprint cadence with demoable increments and a written decision log.
Transparent Git repository ownership — repositories land in your organisation from day one.
Infrastructure-as-code (Terraform or Bicep) for every environment, reviewed and reproducible.
Fixed-scope proposals in EUR (€) or SEK (kr), with capped B2B consulting retainers when scope is still emerging.
Bilateral NDA signed before source code, architecture data or credentials are shared.
Reporting fails when every team defines its own metric. DevNord establishes EDW architecture with one governed reporting model, then builds ETL pipelines that validate schemas, count rows and reconcile against the ERP before anything is published. Power BI dashboards & financial reporting read that model, so finance and operations work from the same figures.
Workflows are implemented inside the platform: Dataverse connected to D365/AX holds state for Power Apps (Canvas & Model-driven) and Power Automate, while SharePoint integration and custom portals deliver automated document workflows to partners. Playwright E2E covers the reporting and approval journeys. Proposals are fixed scope in EUR (€) or SEK (kr), with one governed reporting model as the first milestone.
ERP data is exported into spreadsheets, copied into reports and emailed between teams. Every month-end close repeats the same manual reconciliation, and workflow approvals leave no trace outside an inbox. Without a governed reporting model, nobody can say which figure is authoritative.
We define EDW architecture and one governed reporting model, then build ETL pipelines with validation and reconciliation from D365/AX and other ERP sources. Power BI dashboards & financial reporting read that model; Dataverse connected to D365/AX carries workflow state for Power Apps (Canvas & Model-driven) and Power Automate, while SharePoint integration and custom portals handle documents.
Power BI dashboards & financial reporting use the same governed figures, ending spreadsheet version wars.
Power Automate and automated document workflows record every approval where an auditor can find it.
Dataverse connected to D365/AX, SharePoint integration and custom portals give teams one place to work.
These are service-specific, reviewable assets — not status reports. Your team owns each one.
Still unsure? Write to us at [email protected] — we reply in plain language, without a sales script.
We build ETL pipelines from Dynamics 365 F&O, AX 2012 R2/R3, SQL sources and file drops into an EDW architecture. Dataverse connected to D365/AX carries workflow data without replacing the ERP as the system of record.
We move financial reporting into Power BI dashboards & financial reporting on one governed model. Existing spreadsheet logic is documented first so the close keeps the checks it relies on.
Yes. We deliver Power Apps (Canvas & Model-driven) with Power Automate for automated document workflows, backed by SharePoint integration and custom portals where partners need a single entry point.
ETL validation and reconciliation run with every load, while Playwright covers critical reporting and approval journeys to reach 90%+ automated regression coverage on the paths finance uses.
Start with a fixed-scope review of sources, reports and workflows, and receive an EDW architecture and Power Platform sequence your finance and operations teams can approve.