EPMS·Data Model Explorer
seco_Pass 3

Data & Analytics architecture

Where the data comes from, where it lands, and where we report from.

100%
SourcesWhere the data comes fromMigrationPhase 1 · CSPEPMS platformPhase 1 · CSPIntegration (Azure)Phase 1 · CSP + SECOAnalytics — Phase 1Live for DecemberAnalytics — Phase 2Sandvik Data & Analytics2raw landing3validation bythe business4process and shape6attachmentsactive onlyhistory stays puthosted in9Phase 1 reportingaction log read-writepull, not pushsemantic modelPhase 2 reportingSmartsheetBeing decommissionedDynamics 365OneCRM · cmnt prefixM3ERPExtractionSmartsheet API pullSharePointDocument storeADLS Gen2 — BronzeAzure Data Lake StorageGen2Bronze explorerWeb app on BronzeAzure SQLReplicated DataverseschemaAzure Data FactoryPush SQL → DataverseActive projects→ DataverseInactive projectsstay in SQL / lakeEPMS Dataverseseco prefix · 128 tablesExternal portalPower Pages ReactSPAEPMS All UsersPower Apps CodeAppEPMS AdminPower Apps CodeAppAzure Synapse Linkfor Dataverse — NOT FabricAzure Synapse WorkspaceIntegration workspaceADLS Gen2Storage account · hierarchicalnamespacePower BI — operationalPlatform 4Power BI — financialPlatform 5DatabricksSandvik data platform · businessaccesses M3Data productPower BI semantic modelPower BI — Phase 2Repointed at DatabricksPhase 1 / Phase 2 boundary
Phase 1 must be live for the mid-December Smartsheet decommission. Phase 2 follows, at the Data & Analytics team's priority — Rodrigo confirmed on 25 August that his team has no current capacity and is hiring three people.
Limited activity pattern
The Smartsheet → SQL → EPMS and Azure SQL → Data Factory → EPMS paths are only needed while Smartsheet is still the source of active projects. Once Smartsheet is decommissioned, no further SQL pushes into EPMS are required — the migration is complete and ongoing active projects live directly in Dataverse.
They pull. They do not accept pushes.
Sandvik Data & Analytics pull data; they do not accept pushes. The final architecture decision rests with Suresh, their data architect. This diagram is the input to that decision, not a substitute for it.