Microsoft Manufacturing Austria

Poloplast

Supply Chain Optimization

Poloplast needed to replace monthly spreadsheet forecasting and disconnected ERP processes that made supply-chain planning reactive, labor intensive, and poorly aligned with production.

Once a month
one and a half years of forecasting with a single click
the next three months

Reported impact

Business outcome

Poloplast extended its planning horizon from three months to one and a half years with a single click, reduced external storage costs, improved purchasing precision, and kept customer service levels high with less wasteful stock and ordering.

  • Cost Reduction
  • Customer Experience
  • Productivity Improvement

Solution

Poloplast adopted Dynamics 365 Supply Chain Management and the new Demand planning capability to turn forecasting into a collaborative, data-driven process rather than a rearview-mirror exercise. Key components include Dynamics 365 Supply Chain Management anchors ERP, item availability, and downstream supply-chain execution on the same platform as forecasting; Demand planning provides the forecasting algorithms, reports, and collaborative user experience for forward-looking planning; Power Platform underpins the low-code demand-planning experience used by business teams. Poloplast extended its planning horizon from three months to one and a half years with a single click, reduced external storage costs, improved purchasing precision, and kept customer service levels high with less wasteful stock and ordering.

Data flow

Sales managers build forecasts in Demand planning, the resulting outlook feeds directly into Dynamics 365 Supply Chain Management, and downstream teams use the same data to decide raw-material purchases, item availability, storage allocation, and production quantities with much tighter alignment than before.

Solution architecture

3 components · 2 layers
  1. Compute
    • Demand planning provides the forecasting algorithms, reports, and collaborative user experience for forward-looking planning
  2. Orchestration
    • Dynamics 365 Supply Chain Management anchors ERP, item availability, and downstream supply-chain execution on the same platform as forecasting
    • Power Platform underpins the low-code demand-planning experience used by business teams

Architecture clues

  • Demand planning was adopted through a Microsoft private preview and refined collaboratively.
  • Forecasting and supply-chain management now share one source of truth on the ERP platform.

Evidence from the source

By using demand planning within Microsoft Dynamics 365 Supply Chain Management, Poloplast achieved its goal of a more connected process.
One issue we had was that the forecast was not directly implemented into our enterprise resource planning system.
Today, Kreisel and Wogerbauer can project one and a half years of forecasting with a single click.
Transparency Evidence & methodology 65/100 reference value · 82% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value65/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence82%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence15/20
    3 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Microsoft

    Poloplast customer story

    First-party
    https://www.microsoft.com/en/customers/story/1752163541659183955-poloplast-dynamics-365-supply-chain-management-discrete-manufacturing-en-austria
    Source type
    Vendor-published customer story
    Published
    Mar 28, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Mar 28, 2024 · Microsoft · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.