DynamicsOps
    ISV · Manufacturing

    Production Shop Floor

    Turn the shop floor into live data. Every operation, machine hour and output is captured the moment it happens, directly inside Business Central or Finance & SCM — no paper travelers, no double entry.

    Runs on:Dynamics 365 Business CentralDynamics 365 Finance & SCM

    Product screens

    DynamicsOps Shop Floor · Dynamics 365 Business Central

    Shop floor operator tablet

    Job list, operation details and start, pause and report-output actions

    Operator job listDowntime trackingLarge touch controls

    Representative DynamicsOps product screen with fictional sample data; not an official Microsoft screenshot.

    Document Summary

    What this solution document covers

    Production Shop Floor is a DynamicsOps ISV product running on BC and F&SCM. This page is a structured digest of the product brief: from the business problem to the solution architecture, module capabilities, an implementation plan and measured outcomes.

    An embedded MES layer where operators run production orders from a touch terminal while every action posts back to the ERP instantly — consumption, output, time and quality in one flow.

    Category
    Manufacturing
    Platform
    BC / F&SCM
    Capabilities
    6
    Phases
    4
    Overview

    Real-time manufacturing execution (MES) layer for Dynamics 365

    Live Data Capture

    Operators register start, stop, output, scrap and consumption from a touch terminal in real time.

    Order Execution

    Production orders, routings and operations are driven and updated straight from the floor.

    Time & Machine Tracking

    Automatic labor and machine time logging against each operation and work center.

    Production Insight

    Live WIP, OEE and throughput dashboards give managers an always-current picture.

    The Challenge

    Why the current approach falls short

    Most manufacturers still run the floor on paper travelers and end-of-shift data entry. By the time numbers reach the ERP they are hours old, error-prone and impossible to act on.

    No real-time visibility

    WIP and order status are only known after manual posting at shift end.

    Manual, error-prone entry

    Hand-written times and quantities are re-keyed into the ERP, creating errors and delays.

    Blind on OEE & downtime

    Machine stoppages and losses go unmeasured, so bottlenecks stay hidden.

    Costing lags reality

    Actual labor and machine costs land late, distorting margins and planning.

    The Solution

    Embedded in Dynamics 365, production-ready.

    An embedded MES layer where operators run production orders from a touch terminal while every action posts back to the ERP instantly — consumption, output, time and quality in one flow.

    Operator touch terminal

    Simple kiosk UI for start / pause / stop, output, scrap and material consumption.

    Driven by ERP orders

    Reads released production orders, BOMs and routings; writes journals back automatically.

    Real-time posting

    Output, consumption and capacity ledger entries post the moment they happen.

    Reason-coded downtime

    Stoppages captured with reason codes to feed OEE and continuous improvement.

    Native extension architecture

    100% AL on BC and X++ extension on F&SCM — no middleware, AppSource-ready.

    Capabilities

    What the module does

    Job Start / Stop

    Operators clock on and off operations with one tap; labor time logs automatically.

    Output & Scrap

    Register finished output and scrap with reason codes against each operation.

    Machine Time

    Track machine run, setup and idle time per work and machine center.

    Material Consumption

    Backflush or manual pick of components with lot / serial capture.

    Downtime Reasons

    Log stoppages and micro-stops with structured reason codes for OEE.

    In-line Quality

    Operation-level quality checks and pass / fail capture before the next step.

    Deep Dive

    Designed for the floor, not the office

    A full-screen, touch-first terminal any operator can use in minutes. It shows only the released orders and operations relevant to that work center — and turns every action into a posted ERP transaction.

    01.Touch & barcode driven

    Runs on tablet, kiosk or industrial PC; everything driven by large touch buttons.

    02.Multi-language operator UI

    Language by shift and operator profile; simple, mistake-proof flow.

    03.Offline-tolerant

    Keeps capturing during short network drops and syncs back to the ERP automatically.

    Use Cases

    Who is it for, and where?

    Discrete Manufacturing

    • Assembly lines with multi-operation routings
    • Serial / lot tracking on output
    • Operator labor and machine time split

    Process & Batch

    • Backflushed bulk consumption
    • Batch output with quality gates
    • Yield and scrap analysis by run

    Subcontracting

    • Send / receive subcontract operations
    • Track external work-center progress
    • Cost capture on outsourced steps
    Detailed Scenarios

    Real-world scenarios from the field

    The scenarios below show how Production Shop Floor operates across different operation types — the steps involved and the capabilities each one exercises.

    For Discrete Manufacturing operations, Production Shop Floor lets field teams assembly lines with multi-operation routings in a single flow. Every transaction is captured directly on BC / F&SCM with no double entry.

    Flow steps

    • 01Assembly lines with multi-operation routings
    • 02Serial / lot tracking on output
    • 03Operator labor and machine time split

    Key capability used

    Job Start / Stop

    Operators clock on and off operations with one tap; labor time logs automatically.

    Business Value

    Measured outcomes

    −90%
    data-entry lag
    +15%
    OEE visibility gain
    Real-time
    WIP & cost
    1 day
    operator onboarding
    Implementation

    Live in weeks

    Phase 1 · 1–2 wks

    Discovery

    Review floor flows, work centers and current integrations.

    Phase 2 · 2–3 wks

    Configure

    Terminal setup, reason codes, routings and barcode design.

    Phase 3 · 2 wks

    Pilot

    Parallel validation against real production on one line.

    Phase 4 · Ongoing

    Rollout

    Roll out to more lines, operator training and continuous improvement.

    DynamicsOps · Technical Details

    Architecture, integration and security

    100% native AL extension on BC and native X++ extension on F&SCM — no middleware, no external database. Installs straight into your existing ERP environment.

    External systems
    • Machines (OPC UA, MQTT, PLC)
    • Operator tablets
    DynamicsOps

    Production Shop Floor

    DynamicsOps Shop Floor app and edge gateway; Business Central: API pages and web services · Finance & SCM: data entities / OData and business events

    Microsoft Dynamics 365
    • Dynamics 365 Business Central
    • Dynamics 365 Finance & Supply Chain

    Data flow

    • ERP → floor: production orders, routes and BOMs
    • Floor → ERP: output, consumption, scrap and downtime
    • Machine → floor: counter and status signals

    Role-based access

    Through Dynamics 365 permission sets and Microsoft Entra ID.

    Encrypted connections

    All transfers run over TLS.

    Audit trail

    Every transfer and approval is logged with user and time.

    Error queue

    Failed records stay queued and are resent after correction.

    Requirement Matrix

    Function coverage, module by module

    Fit-gap matrix for Production Shop Floor: delivery method, AI support and implementation phase.

    IDRequirement
    CORE-01
    Job Start / Stop

    Operators start/stop operations with a single tap; labor time is logged automatically.

    MustAI · YesPhase 1
    CORE-02
    Output & Scrap

    Finished output and scrap are recorded against each operation with a reason code.

    MustAI · YesPhase 1
    CORE-03
    Machine Time

    Run, setup and idle time are tracked by work/machine center.

    MustAI · YesPhase 1
    CORE-04
    Material Consumption

    Components are consumed via backflush or manual picking with lot/serial capture.

    MustAI · YesPhase 1
    CORE-05
    Downtime Reasons

    Downtime and micro-stops are logged with structured reason codes for OEE.

    MustAI · YesPhase 1
    CORE-06
    In-Line Quality

    Operation-level quality checks; pass/fail captured before moving to the next step.

    MustAI · YesPhase 1
    ENT-01
    Production

    Full integration with BC production order, BOM and routings.

    MustAI · PartialPhase 2
    ENT-02
    Costing

    actual labor/machine time flows into BC costing.

    MustAI · PartialPhase 2
    ENT-03
    Quality

    capture and reporting of in-line quality control results.

    MustAI · PartialPhase 2
    ENT-04
    Power BI

    ready-to-use data model for OEE, downtime and yield analytics.

    MustAI · PartialPhase 2
    AI-01
    AI Assistant

    An embedded AI assistant helps planners and operators run production orders, explain routings and resolve consumption errors

    MustAI · YesPhase 1-2
    AI-02
    AI Control Checklist

    The AI generates and runs a checklist over BOMs, routings, work centers and costing, so production data is correct before orders are released

    MustAI · YesPhase 1-2
    AI-03
    AI Test Execution Steps

    The AI writes and runs test steps for order release, consumption, output and cost roll-up — proving shop-floor flows before go-live and on every change

    MustAI · YesPhase 1-2
    AI-04
    AI Migration Tool

    The migration tool ports items, BOMs, routings, work centers and open work orders from legacy MRP/ERP; validates structures and

    MustAI · YesPhase 1-2
    SEC-01
    Role-based authorization

    Role and data access control via BC permission sets

    ShouldAI · PartialPhase 1
    SEC-02
    GDPR/KVKK compliance

    Data inventory, retention, audit log and data subject request management

    ShouldAI · PartialPhase 1
    SEC-03
    AI governance

    AI actions are logged, reversible and subject to human approval

    ShouldAI · PartialPhase 1
    RPT-01
    Power BI data model

    Ready-to-use KPI and analytics data model

    ShouldAI · YesPhase 3
    RPT-02
    BC native reports

    Integration with standard financial and operational reports

    CouldAI · NoPhase 3
    Documents

    Downloadable resources

    The original product brief and requirement matrix that source this page.

    See a live demo of Production Shop Floor

    Let's plan scope, deployment time and pricing for your BC or Finance & SCM environment.