Experis
Johnson & Johnson · Proposal

Mid-October to early December.
54 man-days, three roles.

The engagement replicates and industrialises the business's own Power BI mockup on a governed Azure data foundation. Effort is shown in man-days only; commercials sit outside this document.

Timeline
  1. Early October 2026

    Architect engages J&J IT Infrastructure

    Ahead of the delivery start, the Enterprise Architect works with J&J IT Infrastructure to get Azure platform provisioning and source system access approvals moving.

  2. Mid-October 2026

    Delivery starts - Phase 1

    Platform stood up, ADF pipelines connected to ESQRP, Comet, M7 and the remaining systems, sources landing raw in Bronze. Daxia deployed so the business can start its data mapping.

  3. November 2026

    Phase 2 - Silver, Gold and serving

    Supplier entities conformed in Silver, performance, risk and action models built in Gold, published to Azure SQL Database and wired into the Lighthouse reports.

  4. Early December 2026

    Complete model delivered

    The Lighthouse reports replicate the business's Power BI mockup on governed data, signed off by the nominated business owner.

Effort by role
54 man-days total
Enterprise Architect

Platform design, J&J IT Infrastructure engagement from early October, security and access, Synapse / Fabric decision.

9 days
Senior Data Engineer

ADF pipelines per source, ADLS Gen2 medallion, Synapse transformations, Azure SQL serving layer, Daxia deployment.

10 days
Data Analyst

Works with the business on the data mapping and reporting grain, builds Silver / Gold logic and replicates the Power BI mockup.

35 days
Prerequisites and access

What J&J needs in place

Architect-led preparation from early October

The Enterprise Architect engages J&J on this checklist from the beginning of October - Azure provisioning, source system access, identity and the business inputs - so everything here is prepared before the delivery team onboards in mid-October.

Azure platform
  • Azure subscription
    One to two weeks
  • ADLS Gen2 storage account
    Hierarchical namespace enabled
  • Azure Synapse Analytics workspace
  • Azure SQL Database
    Serving layer for the reports
  • Power BI workspace
    Hosts the Lighthouse reports
  • Microsoft Fabric
    Only if a Fabric workspace already exists - used in place of Synapse
    Not requested - existing workspace only
Source system access
  • ESQRP
    Read access and service account
  • Comet
    Read access and service account
  • M7
    Read access and service account
  • Remaining supplier quality systems
    Read access and service accounts
  • Network paths and approval routes
    Confirmed for every source
Identity and security
  • Entra ID service principals
  • Managed identities
  • Key Vault for secrets
  • Data classification and handling rules
    As they apply to supplier data
Business inputs
  • Data mapping
    Owned by the business - which data points are pulled from each source system
  • Existing Power BI mockup
    The reporting specification
  • Nominated business owner
    For sign-off
  • Agreed reporting grain
Assumptions and risks

What this plan relies on

The October runway is the principal risk

Azure subscription provisioning (one to two weeks) and source system access approvals are the two lead-time dependencies. That is why the architect engages J&J IT Infrastructure from the beginning of October, ahead of the delivery start.

Azure is the target platform

Azure Synapse Analytics is used for transformation unless an existing Fabric workspace is available, in which case it is used instead. No new Fabric workspace is requested.

Supported connectors

Source systems can expose data through supported connectors that Azure Data Factory can reach.

AI and Copilot out of scope

AI and Copilot capability is explicitly out of scope for this phase and deferred to a later phase.

Daxia stays with J&J

Daxia is delivered into J&J's own Azure tenant with usage billed locally. There is no ongoing licence dependency on the delivery partner.