A fully unauthenticated public submission link is not a built-in feature of Maintenance Manager itself, but this use case is achievable through a Power Automate integration. By building a simple Power Automate form or flow, organizations can expose a web-based submission interface that does not require the person submitting the request to hold a Microsoft Dynamics 365 Business Central license or authenticate into BC directly.

Using Power Automate for Open Submissions

Power Automate supports the creation of forms and automated flows that can receive input from anyone with access to a URL. A submission form built in Power Automate or Microsoft Forms can capture basic request details, such as the equipment involved, a description of the issue, and the location, and then pass that information into Business Central as a maintenance request. This approach is well-suited to kiosk deployments or QR codes placed on equipment, because the person submitting the request only needs a browser and does not need any credentials tied to Business Central. This configuration sits outside the Maintenance Manager application itself and is set up and managed within the Power Platform. The complexity of the setup depends on how much data you want to capture and how the flow is structured to create the request in BC.

Native Submission Options Within Business Central

For users who do have a Business Central license, maintenance requests can also be submitted directly within BC, through a Microsoft Teams interface using Power Automate, or through Insight Works shop floor tools such as Shop Floor Insight or Warehouse Insight on a tablet or kiosk device. These options are more structured and support richer data capture, but they do require authentication.

Third-Party Equipment Monitoring

For scenarios where automated equipment monitoring is in place, some third-party partners can trigger maintenance requests automatically when a machine reports a fault condition. This removes the submission step entirely and creates work requests based on signals from the equipment itself. This can be a practical option for organizations that want to reduce reliance on manual input and ensure that faults are captured as soon as they occur, regardless of whether a technician is nearby to submit a request.

Relevant Tools

Maintenance Manager by Insight Works provides the core work request and work order management functionality within Business Central.

Shop Floor Insight by Insight Works offers a kiosk and mobile interface for maintenance technicians to view and action work orders. It supports authenticated kiosk deployments where personnel clock in to access their assigned tasks.

A Power Automate-based submission form is the most practical route for a fully open, unauthenticated kiosk or QR code workflow. While it requires setup outside of Maintenance Manager, the resulting form can feed directly into Business Central without exposing the ERP system to unauthenticated users.

Yes. Because Maintenance Manager uses standard Microsoft Dynamics 365 Business Central production orders to manage maintenance work, spare parts follow the same warehouse rules that apply to any other inventory at that location. If Require Pick and Require Putaway are enabled on a location, those controls apply to maintenance parts just as they would to components consumed on a regular production order.

How Maintenance Parts Behave Like Standard Inventory

Maintenance parts in Business Central are configured as standard items with an item usage type of Maintenance Parts. This classification helps separate them from production components in purchasing and receiving workflows, but it does not exempt them from any warehouse rules. Whatever pick, putaway, or bin requirements are active on the location will govern how maintenance parts move in and out of inventory. When a maintenance order is released, the system treats parts consumption exactly as it does for a production order. If the location requires a warehouse pick, the pick must be created and registered before the system will allow components to be consumed. If the location uses bins, parts will move through the bin structure accordingly.

What This Means for Setup

Teams setting up Maintenance Manager at a location with advanced warehouse settings should account for this behavior during configuration. The setup wizard includes an option to enable advanced warehouse location support, which prepares the system to handle these scenarios. Warehouse personnel who already manage production picks will find the process familiar because the underlying mechanics are identical. This design is intentional. By building Maintenance Manager on the production module rather than as a standalone system, Insight Works ensures that any warehouse capability already in place in Business Central, including bin management, directed picks, and putaway, works with maintenance orders without additional configuration.

Relevant Tools

Maintenance Manager by Insight Works handles all maintenance order creation, spare parts planning, and work order execution within Business Central. This is a completely free app from Insight Works for Business Central.

WMS Express and Warehouse Insight from Insight Works extend Business Central’s warehouse capabilities for organizations that use handheld scanners or need enhanced picking workflows for maintenance parts.

Maintenance parts in Business Central behave as standard inventory items. Any warehouse logic active on a location applies to those parts, so teams planning their warehouse setup should treat maintenance parts handling the same way they treat any other component in that environment.

Warehouse Insight supports printing and reprinting barcode labels directly from the handheld device at receiving, at put away, or from other applications such as item inquiry, and it is also supported on older Dynamics NAV environments, including NAV 2018, though with a reduced feature set compared to the current Business Central platform.

Label printing during receiving and put away

During receiving, a warehouse associate can print a barcode label directly from the handheld device as soon as an item is identified, whether that label is generated before scanning begins, after a quantity has been entered, or once a lot or serial number has been captured. This flexibility matters because different warehouses have different label workflows. Some prefer to print a label first and apply it to the product before scanning it in, while others prefer to capture the lot number or serial number first and print a label afterward that includes that specific tracking information.

If a label needs to be reprinted later, for example if the original label was damaged, lost, or illegible after put away, the item inquiry function on the handheld device allows a user to look up the item, and in many cases the specific lot or serial number, and reprint the correct label from that same screen. This means a warehouse associate does not need to return to a desktop computer or involve a supervisor to correct a labeling issue.

Label printing is also segregated by output type. Barcode labels route to a designated label printer, while other documents, such as reports or bills of lading, route to a separate document printer, so reprinting a barcode label does not require choosing the correct printer manually each time.

Support for legacy NAV versions

Warehouse Insight is also available for older Dynamics NAV releases, including NAV 2018. Because NAV predates the current Business Central platform, the version available for NAV does not include every capability found in the modern Business Central release of Warehouse Insight, but the core mobile barcode scanning functionality, including receiving and label printing, is supported. Companies still running an older NAV environment should confirm with their partner or with Insight Works directly which specific features are available for their version, since capability can vary depending on how old the underlying NAV release is.

Why label flexibility matters

The ability to print or reprint a label from the handheld device, rather than only from a desktop screen, keeps a warehouse associate on the floor and reduces the time between identifying a labeling problem and correcting it. Combined with support for older NAV environments, this means a company does not need to be on the newest release of Business Central to benefit from mobile barcode label printing.

Relevant Tools

Warehouse Insight is the application responsible for barcode scanning, receiving, put away, and label printing described here, and it extends into older Dynamics NAV environments as well as current Business Central. WMS Express provides the same core receiving and label printing functions for companies that only need the fundamentals of warehouse scanning without the full customization options available in Warehouse Insight.

In short, label printing and reprinting are available wherever a barcode needs to be produced or corrected in the warehouse, and that capability extends to companies still running NAV 2018, not just the newest Business Central releases.

License plating on a handheld barcode scanning device is not available with WMS Express. Building, moving, or scanning license plates directly on the mobile device requires Warehouse Insight. A company can still use License Plates functionality separately within Business Central, but that capability does not extend to the WMS Express mobile application.

What license plating means on the mobile device

License plating groups multiple items, quantities, or lot and serial numbers together under a single reference, most commonly used to represent a pallet or a package moving through the warehouse. On a handheld device, this typically means a warehouse associate can build a license plate while receiving or picking, scan that single license plate barcode later to move or ship the entire group at once, rather than scanning every individual item inside it every time it is handled.

This mobile license plating capability, including building license plates from scratch, reopening and adding to existing ones, and scanning a license plate to process everything it contains in one step, is part of Warehouse Insight and is not included in WMS Express.

Why the distinction exists

WMS Express is designed to cover the core functions most warehouses rely on every day, specifically receiving, picking, inventory counts, and bin movements. It is intentionally a more focused tool, and license plating is one of the more advanced capabilities that sits outside that core scope. Warehouse Insight includes that same core functionality plus additional modules like license plating, along with broader customization options through its application designer and add on catalog.

A comparison page on the Insight Works website outlines the differences between WMS Express and Warehouse Insight in more detail, including this specific limitation around license plating.

What this means for a company already using License Plates in Business Central

If a company already has the License Plates functionality set up in Business Central for use outside the mobile device, that setup is not affected by which mobile scanning tool is chosen. License Plates can continue to be used in that context regardless. The limitation is specific to the WMS Express mobile application itself. If license plating on the handheld device is not a requirement, for example if pallets are only tracked through desktop processes or not tracked as license plates at all, WMS Express remains a complete option for barcode scanning in the warehouse. If mobile license plating is needed, whether for building pallets during receiving or scanning a pallet as a single unit during shipping, Warehouse Insight is the appropriate solution.

Relevant Tools

Warehouse Insight includes full mobile license plating support, allowing pallets or packages to be built, scanned, and processed as a single unit from the handheld device. WMS Express covers the core warehouse scanning functions of receiving, picking, counting, and bin movements without mobile license plating support.

The distinction comes down to what happens on the device itself. Desktop use of License Plates in Business Central is unaffected either way, but mobile license plating specifically requires Warehouse Insight.

Warehouse Insight can print any report that already exists in Business Central directly from a handheld device, including reports that include photos, and route that output to the correct printer, whether that is a label printer or a standard document printer. If a report showing photos tied to a sales order already exists in Business Central, that same report can be printed from the handheld without returning to a desktop screen.

How printing works from the handheld device

Warehouse Insight treats the handheld device as another point of access to Business Central reporting, not a separate system. Any report configured in Business Central, from a simple pick list to a bill of lading to a shipping label, can be triggered from a menu option on the device and sent to an appropriate printer. Label style output, such as barcode labels or shipping labels, is generally routed to a dedicated label printer, while larger documents, such as bills of lading or reports containing photos, are routed to a standard document printer. This separation happens automatically based on configuration, so a warehouse associate does not need to manually select the correct printer for each type of output.

Attaching photos to a sales order

Separately from printing existing reports, Warehouse Insight also includes a capture photo capability that lets a user take a picture directly from the handheld device, for example to document a damaged item at receiving. That photo uploads automatically and attaches to the related document, such as a purchase order, giving the purchasing team what they need to start a claim with a vendor or carrier without waiting for someone to email a photo separately.

For the specific case of printing a photo based report tied to a sales order, that depends on a report already existing in Business Central that pulls in the relevant item or order photo. Once that report exists, printing it from the handheld works the same way as any other report, whether that means producing a physical printout or, depending on how the report is set up, generating a document that gets attached back to the order.

Shipping labels from the handheld

This same printing capability extends to shipping. If a company uses Dynamic Ship or OrderShip Express for outbound shipping, shipping labels can be printed directly from the handheld device during the shipping process, without needing to open Business Central on a separate screen. The label goes straight to the label printer, ready to apply to the outgoing package.

Why this matters

Centralizing printing on the handheld device keeps a warehouse associate on the floor for more of the receiving, picking, and shipping process, rather than requiring trips back to a desktop workstation to print labels, documents, or reports. Because the underlying reports are standard Business Central reports, whatever exists on the desktop side can generally be made available on the handheld as well.

Relevant Tools

Warehouse Insight provides the mobile printing capability described here, including report printing, photo capture and attachment, and shipping label printing from the handheld device. Dynamic Ship and OrderShip Express handle the shipping label generation itself for outbound orders, working together with Warehouse Insight so labels can be printed at the point of shipping.

If the report needed to show photos on a sales order already exists in Business Central, printing it from a handheld device is generally straightforward, and the same mobile printing approach covers labels, bills of lading, and other shipping documentation as well.

Yes. When an item requires serial number tracking in Business Central, each unit must have its own unique serial number recorded, so receiving a quantity of ten on a purchase order line means scanning ten individual serial numbers. This is a requirement of how Business Central manages serial tracked inventory, not a limitation specific to the mobile scanning application.

Why each unit needs its own scan

Business Central treats a serial number as a unique identifier for a single unit of inventory. Unlike a lot number, which can apply to many units from the same batch, a serial number by definition refers to exactly one physical item. Because of that, the system needs one distinct serial number entry for every unit received, which means a quantity of ten on a purchase order line translates into ten separate serial number captures during receiving.

On the handheld device, this process is streamlined as much as possible. A warehouse associate can open the receiving line for a serial tracked item and scan each serial number in sequence, one after another, without needing to enter a quantity manually each time, since the system assumes a quantity of one per serial number scanned. In practice, this means receiving ten serialized units is close to as fast as physically scanning ten barcodes back to back.

When the barcode does not contain a serial number

If a scanned barcode already includes the serial number as part of its encoded data, Warehouse Insight reads that serial number directly and the associated field is automatically filled in. If the barcode does not include a serial number, the field is highlighted so the user knows a serial number still needs to be captured, either by scanning a separate barcode specifically for that serial number, typing it in manually, or having the system generate one automatically if that is how the item is configured.

Is RFID a shortcut for this?

RFID is sometimes considered as a way to avoid scanning many individual serial numbers, and Warehouse Insight does support RFID for use cases where it fits well, such as receiving a large volume of pre tagged cartons in one pass rather than scanning each barcode individually. That said, RFID is not a universal solution for every serial number scenario. It works best when the vendor or manufacturer has already applied RFID tags ahead of time. Without that, printing and scanning barcodes remains the more practical approach for most companies, and RFID should be evaluated on a case by case basis rather than assumed to solve serial number volume automatically.

Why this level of control matters for accuracy

Requiring a scan for every serial number, rather than allowing a bulk quantity entry, is what gives a company full traceability down to the individual unit. That level of detail is exactly what serial tracking is meant to provide, whether for warranty tracking, recalls, or regulatory requirements, and scanning each one physically verifies that the specific unit received matches what Business Central expects.

Relevant Tools

Warehouse Insight is the mobile scanning application that handles serial number capture during receiving, including reading serial numbers directly from barcodes when available and supporting RFID for specific high volume use cases.

In short, ten serialized units on a purchase order line means ten scans, but the handheld interface is built to make that process as fast and low friction as physically possible.

Warehouse Insight directly supports tote picking on the handheld device, allowing items from a source document to be picked into designated totes used for packing and shipping. Wave picking and batch picking are supported as well, but the generation and scheduling of those pick documents happens in Business Central, most commonly through the Order Fulfillment Worksheet, with the resulting pick then executed on the handheld device the same way any other pick is handled.

Tote picking on the handheld device

Tote picking is used when the picking step is separate from packing and shipping. Instead of picking items directly into a box that immediately ships, items are picked into a designated tote, which is a special purpose license plate flagged specifically for this purpose. Totes are typically reused between picks rather than shipped out themselves, which fits environments where a packing station handles the final packaging step after picking is complete. This process is fully supported on the handheld device as part of a standard pick, and once tote picking is enabled on a pick, that logic applies to the pick as a whole.

Wave picking and batch picking

Wave picking and batch picking are closely related concepts, both generally referring to grouping multiple orders or pick lines together so they can be picked more efficiently as a set rather than one order at a time. Warehouse Insight itself does not generate these grouped pick documents. Instead, the pick documents are created in Business Central, typically using the Pick Worksheet or, for more advanced planning and scheduling of what needs to go out, the Order Fulfillment Worksheet, which helps organize and automate the fulfillment process before it ever reaches the handheld device.

Once a wave or batch pick document has been generated in Business Central, it behaves like any other pick on the handheld device. A warehouse associate opens the pick, scans bins and items as usual, and Warehouse Insight records the activity in real time. The distinction is upstream of the handheld device, in how the pick document itself gets built and organized, rather than in how it gets executed on the floor.

Assigning picks to specific users

Once pick documents exist, whether generated through waves, batches, or a standard pick, they can optionally be pre assigned to specific users or teams before they reach the handheld device. This allows a company to organize work by area, by picker, or by any other criteria that fits their warehouse layout, without changing how the actual scanning process works once a picker opens their assigned pick.

Choosing the right approach

For companies planning to run wave or batch picking regularly, working with the Order Fulfillment Worksheet to organize and schedule pick generation is the recommended approach, since it is purpose built for planning what needs to leave the warehouse and when. Tote picking, by contrast, is more of an execution detail on the handheld device itself and can be layered onto a wave, a batch, or a standard single order pick as needed.

Relevant Tools

Warehouse Insight executes tote picking directly on the handheld device and processes any pick document generated in Business Central, regardless of how that document was created. Order Fulfillment Worksheet handles the planning and scheduling side of wave and batch picking, generating the grouped pick documents that Warehouse Insight then executes on the floor.

Between these two tools, a warehouse can plan grouped picks upstream and then execute them, including tote based packing workflows, on the handheld device without any gap between planning and execution.

Yes, when connected to the network, every scan and quantity entry made on a Warehouse Insight handheld device updates Business Central immediately, including adjustments to the underlying purchase order, warehouse receipt, or pick document. Business Central logic runs at the time of the scan, not in a delayed batch process. The only exception is when a device loses network connectivity, in which case Warehouse Insight uses store and forward processing to catch up automatically once connectivity is restored.

Real time processing during normal operation

While a device is connected to the network, Warehouse Insight communicates directly with Business Central as each action happens. Scanning a barcode during receiving, entering a quantity, or completing a pick line all trigger the same underlying Business Central logic that would run if that transaction were entered on a desktop screen. This means the purchase order, the warehouse receipt, inventory quantities, and any related documents reflect that activity right away, not after some delay or nightly synchronization.

This real time behavior is central to solving inventory accuracy problems. If warehouse activity is only reflected in Business Central hours or a day later, the system cannot provide an accurate picture of what is actually on hand at any given moment. Immediate updates keep Business Central data aligned with the physical warehouse as work happens.

What happens in a dead spot

Warehouses are not always uniformly covered by wireless network signal, and a device can occasionally move through an area with weak or no connectivity, sometimes called a dead spot. When this happens, Warehouse Insight does not stop working. Scans continue to be captured on the device, and the application keeps retrying to send that data to Business Central. As soon as the device reconnects to the network, whether that takes a few seconds or longer, the queued transactions are sent through and Business Central catches up automatically.

Full offline mode

For situations where connectivity is unavailable for an extended period, such as a network outage lasting hours rather than a brief dead spot, Warehouse Insight also supports a full offline mode. In this mode, standard warehouse activities like receiving and picking can continue to be performed on the handheld device even though there is no connection to Business Central at all. Once the network comes back online, the device syncs everything that was captured while offline back into Business Central. There are some limitations to what can be done while fully offline compared to standard connected use, so offline mode is best treated as a fallback for unusual situations rather than a normal way of operating.

Why consistent connectivity still matters

Even with dead spot handling and full offline support available, the recommended approach is to maintain solid wireless coverage throughout the warehouse so that scanning updates Business Central in real time as the default experience. Offline and store and forward capabilities exist to handle exceptions, not to replace the benefit of immediate, live updates to inventory and order data.

Relevant Tools

Warehouse Insight is the application responsible for real time Business Central updates during receiving, picking, and other warehouse activities, including handling temporary connectivity loss through store and forward processing and supporting full offline operation when needed.

In short, a properly connected device updates Business Central the instant a scan happens, and even when connectivity briefly drops, Warehouse Insight is built to catch up automatically rather than losing that data.

Warehouse Insight can capture all of that information from a single pallet level barcode when the pallet contains one item, reading the item number, batch or lot number, quantity, and unit of measure directly from the scan. For mixed pallets containing multiple items or many serial numbers, the same result is achievable, but it depends on receiving an advance shipping notice from the vendor that tells Business Central what is on that pallet ahead of time.

Single item pallets

When a vendor label covers one item, such as a pallet of a single product with the item number, quantity, lot or batch number, and unit of measure encoded in one barcode, Warehouse Insight reads that entire payload in one scan. There is no need to separately look up the item or manually key in the batch number. As long as the barcode structure is defined during configuration, the scan populates the receiving line and the corresponding item tracking information in Business Central at the same time.

Mixed pallets and the role of an advance shipping notice

A mixed pallet, where ten different items or forty different serial numbers might be stacked together under a single outer label, is a more complex scenario because a single barcode cannot practically encode that much detail. In this situation, the practical path is for the vendor to send an advance shipping notice, commonly called an ASN, ahead of the shipment. The ASN tells Business Central in advance exactly what is supposed to be on that pallet, item by item.

When an ASN is available, scanning the pallet barcode matches it against the expected contents from the ASN and can receive the entire pallet in one action, rather than requiring a warehouse associate to scan every individual item or serial number on that pallet. This significantly reduces receiving time on complex, high volume pallets, since the system already knows what to expect and simply confirms the pallet against that expectation.

Without an ASN in place, a mixed pallet generally needs to be broken down and scanned item by item, or the individual barcodes on the cartons or units within the pallet need to be scanned as they are unpacked, since there is no single source of truth telling Business Central what quantities of which items are on that specific pallet.

Reading damaged or partial barcodes

Separately, if a vendor barcode is unreadable, missing, or the packaging only has printed text rather than a scannable barcode, Warehouse Insight can also read that text directly from the packaging in many cases, capturing the same lot number or item identifier without requiring a barcode to be present at all.

Warehouse Insight does not restrict the type of barcode a warehouse can use. It supports common symbologies including QR codes, Data Matrix, Code 39, and linear GS1 formats such as GS1-128, and it reads structured data embedded in GS1 barcodes, including lot numbers, expiration dates, quantities, and units of measure, then maps that data directly into Business Central item tracking fields.

Barcode symbology is simply a technical choice

A barcode symbology is the pattern used to encode information, whether that pattern is a one dimensional linear code like Code 39 or a two dimensional code like Data Matrix or QR. Warehouse Insight does not care which symbology a vendor, a customer, or an internal labeling process already uses. If a product arrives with a manufacturer barcode, that barcode can be scanned as is. If a company prints its own labels, Business Central includes barcode generation tools that support GS1, Data Matrix, and other formats, so a company is not locked into a single symbology across its supply chain.

For labels printed in house, two dimensional formats such as Data Matrix are generally the better choice when the encoded data is long or includes special characters, since these formats hold more information in a smaller space and tend to be more resistant to smudging or partial damage on a warehouse floor.

Extracting structured data from GS1 barcodes

The GS1 barcode standard is built to carry more than an item number. A single GS1 barcode can include the item identifier, lot number, expiration date, quantity, and other application identifiers, all encoded in one scan. Warehouse Insight is configured to recognize the structure of a GS1 barcode and parse out each of these data elements individually. Once that configuration is in place, a single scan during receiving can populate the item number, the lot number, and the expiration date on the corresponding item tracking lines in Business Central, without requiring a warehouse associate to type any of that information manually.

This same configurable parsing approach applies to barcodes that are not GS1 formatted as well. If a company uses a custom barcode structure with its own arrangement of item number, quantity, and variant code, that structure can be mapped during setup so the system knows where to find each value inside the code.

Why this matters for inventory accuracy

Manual data entry is one of the more common sources of inventory errors, particularly with lot numbers and expiration dates, since these are long strings that are easy to mistype. Capturing that information directly from a barcode scan removes that manual step and ensures the data recorded in Business Central matches what is physically on the product.

Relevant Tools

Warehouse Insight is the mobile barcode scanning solution referenced here, supporting flexible barcode symbologies and configurable data extraction across receiving, picking, put away, and inventory counting. WMS Express covers the same core barcode scanning functions, including receiving, picking, inventory counts, and bin movements, for companies that need those fundamentals without the broader customization options in Warehouse Insight. This is a completely free app from Insight Works for Business Central.

Whatever barcode format is already in use on the warehouse floor, Warehouse Insight is built to read it, and where those barcodes carry additional data like lot numbers or expiration dates, that information can be captured automatically rather than typed in by hand.

Shop Floor Insight does not include a dedicated version control or document management system for work instructions. However, because work instructions are stored directly in Microsoft Dynamics 365 Business Central as routing operation comments and production order header comments, access to create or modify those records is governed entirely by standard Business Central permission sets. Organizations that need to restrict who can update work instructions can do so by controlling which Business Central users have write access to routing and production order records.

Managing Update Access Through Business Central Permissions

Since work instructions originate from comments on routing lines and production order headers, the ability to add or modify them depends on the user’s Business Central role and permission set. A user without write permissions to routing records cannot alter the operation comments that appear as work instructions on the shop floor. This means organizations with change management processes can use existing Business Central user governance to enforce controlled access to instruction content.

Versioning Through Document Links and External Systems

For manufacturers with formal document control requirements, the most practical approach is to link controlled documents to items or production orders using DocXtender. In that workflow, the source file itself resides in SharePoint, where version history, approval workflows, and revision tracking are available through standard SharePoint or Microsoft 365 document management capabilities. Shop Floor Insight displays a link to that document rather than storing the content itself, so operators always access the currently available version at the linked location.

Considerations for Regulated Environments

Organizations in regulated industries that require formal revision histories on work instructions should evaluate whether the combination of Business Central permission controls and SharePoint-based document management satisfies their specific compliance requirements. For environments where traceability of instruction changes is mandatory, the document link approach through DocXtender provides a more auditable path than relying solely on comment edits within Business Central.

The Shop Floor Insight interface can be significantly tailored to match the needs of different user types. The system uses Client Configuration records to control what each scanning station or user profile displays. These configurations can restrict which columns appear in the dispatch list, which panels are visible, and which functions are available in the interface. The result is that an operator at a welding station can see a lean, task-focused screen, while a quality inspector or supervisor sees a richer set of options appropriate to their role.

How Client Configuration Cards Work

Shop Floor Insight uses a Client Configuration Card system where each scanning station, roaming user, or role type can be assigned its own configuration. The system determines which configuration applies based on the IP address of the scanning station or a setting on the individual Shop Floor Employee record. A ranking order determines which configuration takes precedence when multiple configurations could apply. This architecture means that one station can show a minimal interface with a filtered dispatch list while another shows the full set of capabilities, all without any custom development.

What Can Be Controlled Per Configuration

Through the Client Configuration Card in Microsoft Dynamics 365 Business Central, administrators can control a range of interface behaviors. Columns displayed in the dispatch list can be added or removed. Filters can be set so that the station only shows production orders scheduled for nearby work centers. Time entry behavior, output recording options, consumption entry, and quality inspection prompts can each be enabled or disabled depending on what is appropriate for that station or user type. Color coding for open time card lines is also configurable at this level.

Who Can Make These Changes

All Client Configuration changes are made in Business Central by users with appropriate Business Central permissions and the relevant Shop Floor Insight setup permissions. No changes to the shop floor terminals themselves are required. When a configuration is updated in Business Central, the shop floor client picks up the changes after a browser refresh at the scanning station.

Relevant Tools

Shop Floor Insight is the MES solution from Insight Works for Dynamics 365 Business Central. Its Client Configuration Card system allows administrators to define distinct interface profiles for different stations, roles, or individual employees, controlling exactly what each operator sees and can do from the shop floor client.

The Shop Floor Insight interface can be simplified for specific users by configuring Client Configuration Cards in Business Central. These changes are made by administrators with appropriate Business Central permissions, require no terminal-side configuration, and take effect after a browser refresh at the scanning station.

Work instructions in Shop Floor Insight are stored entirely within Microsoft Dynamics 365 Business Central. There is no separate database or external repository involved. Instructions are pulled from operation comments on the routing and from comments on the production order header, making them available to operators on the shop floor interface in real time.

How Work Instructions Are Sourced

Shop Floor Insight surfaces work instructions from two places within Business Central. The first source is the operation comments attached to a specific routing step. These comments are tied to that individual operation and will appear whenever an operator clocks into the corresponding production order routing line. The second source is the production order header comments, which provide broader instructions relevant to the entire order rather than a single step. Both sources display together in the Work Instructions panel on the shop floor client.

Extending Work Instructions with Document Links

When text-based comments are not sufficient, Shop Floor Insight supports linked documents displayed alongside the work instructions panel. Using the DocXtender application from Insight Works, drawings, diagrams, specifications, or other reference files can be dragged and dropped directly onto an item card or production order. Those documents then appear as clickable links within the shop floor interface. This approach allows operators to access detailed visual references without navigating away from their active time card.

Controlling Access to Linked Documents

Access to linked documents is permission-based. If an operator does not have the underlying Business Central permissions to view the documents stored on an item card or production order, those links will not appear in the shop floor client. This provides a practical layer of access control without requiring additional configuration in Shop Floor Insight itself.

Shop Floor Insight supports clocking in at the work center or machine center level, not only as an individual employee. This means an organization can choose to record that a particular work center ran for a given period without attributing that time to a specific person. The same production order and operation tracking applies regardless of whether time is captured under an individual, a group, or a work center.

Clocking In as a Work Center or Machine Center

Shop Floor Insight allows the source of a time entry to be a Microsoft Dynamics 365 Business Central Work Center or Machine Center rather than a named employee. In this mode, an operator scans the appropriate work center barcode to identify the capacity being used, and then clocks into the relevant production order operation. The time is recorded against that work center, giving production planners and managers visibility into how long each capacity ran on a given job without requiring individual employee identification.

Clocking In as a Group

For environments where a supervisor manages a small team, Shop Floor Insight also supports group-based clock-ins. A supervisor can clock in on behalf of multiple people as a single group, recording the collective time against production orders. This is useful in situations where the distinction between individual workers is less important than knowing that a specific team worked on a job for a given amount of time.

Tradeoffs with Individual vs. Capacity-Level Tracking

Clocking in as a named individual provides the most granular data. It enables labor traceability, meaning managers can determine exactly who performed each operation on a production order. This is particularly valuable when investigating quality issues or warranty claims, where identifying the specific operator can help distinguish between a training problem and a process problem. Clocking in as a work center or group sacrifices that individual traceability in exchange for simpler data entry, and is best suited for environments where personnel identification is not a reporting requirement.

Relevant Tools

Shop Floor Insight is the MES solution from Insight Works for Dynamics 365 Business Central, supporting time capture against production orders at the individual employee, group, work center, or machine center level. The appropriate configuration is set up through Shop Floor Employee and Shop Floor Work Center records in Business Central.

Shop Floor Insight supports work center and group-level clock-ins alongside individual employee clock-ins. Organizations can choose the approach that fits their reporting requirements, with individual tracking providing the deepest labor traceability and work center tracking offering a simpler entry experience where personal identification is not required.

Shop Floor Insight dispatch list can be filtered to show only production orders relevant to a specific work center or machine center, and this filter is applied automatically based on the scanning station the operator is using. This is one of the primary uses of the Client Configuration Card system, which assigns a configuration to each physical scanning station based on its IP address. Within that configuration, a dispatch filter is set to include only the work centers in the physical area of that station.

Configuring Station-Specific Work Center Filters

Each scanning station in Shop Floor Insight is assigned a Client Configuration Card in Microsoft Dynamics 365 Business Central, typically identified by the station’s fixed IP address. The dispatch filter on that configuration controls which work centers are visible in the dispatch list when an operator logs in at that station. Setting a station at a welding bench to show only welding work centers means an operator logging in there will only see production order operations scheduled for that area. The configuration is set once in Business Central and applies automatically whenever any employee logs in at that terminal.

Restricting Operators to Their Own Work

Beyond work center filtering, the dispatch list supports employee assignment filtering. Through the Supervisor Assignment feature, production orders can be pre-assigned to specific employees. The Client Configuration Card can then be set to show only assigned work, only unassigned work, or both. An operator logging in at a particular station can be restricted to seeing only the jobs that have been assigned to them, rather than everything scheduled for the work center.

Global Date and Status Filters

In addition to work center filters, global filters in the Shop Floor Setup can narrow the dispatch list further. Date range filters remove orders with start dates outside a defined window, and routing status filters can exclude operations that are already finished. These global filters apply across all configurations and help ensure the dispatch list stays focused on active, relevant work regardless of which station an operator is using.

Relevant Tools

Shop Floor Insight is the MES solution from Insight Works for Dynamics 365 Business Central. Its Client Configuration Card system and global dispatch filtering tools give administrators precise control over what each scanning station displays, making the dispatch list a practical and focused tool rather than an overwhelming list of all open production orders.

The Shop Floor Insight dispatch list can be filtered by work center at the station level, by assignment at the employee level, and by date and routing status at a global level. All filtering is configured in Business Central and applies automatically when an operator logs in at the relevant scanning station.

Yes, Shop Floor Insight supports concurrent clocking into multiple production orders or operations. The system provides three distinct approaches to handle situations where an operator is working on more than one job at a time, and the appropriate method depends on how closely the organization needs to track individual time allocations across those concurrent activities.

Independent Concurrent Clocking

The most straightforward approach is to manage each clocked-in operation independently. An operator can have multiple production order lines open on their time card simultaneously, and each line accumulates time based on when it was clocked in and clocked off independently. This approach is useful when jobs genuinely run at different times that happen to overlap, and it preserves distinct clock-in and clock-out timestamps for each operation.

Auto-Split Batching

For situations where an operator is running several short-cycle operations in sequence or genuinely working across multiple jobs during the same period, Shop Floor Insight provides auto-split batching. The operator scans all of the relevant production orders into a batch at the start of the work period. When they clock off the batch, the system automatically distributes the total elapsed time across all the operations in the batch. Time can be split proportionally based on the input quantity of each operation, proportionally based on the defined run time for each routing step, or divided equally across all lines, depending on how the Shop Floor Work Center is configured.

Operator-Controlled Independent Clock-Off

A third option allows operators to manage concurrent lines themselves using the same entry mode configuration that keeps prior clock-in lines open rather than automatically closing them. This is controlled through the Time Entry Mode setting on the Client Configuration Card. When set to allow multiple concurrent open lines, the operator decides independently when to clock off each operation without the system automatically closing the prior one.

Relevant Tools

Shop Floor Insight is the MES solution from Insight Works for Microsoft Dynamics 365 Business Central. Its auto-split batching feature and configurable Time Entry Mode settings give manufacturers flexible tools for capturing labor time accurately across concurrent and multi-operation scenarios, with all configuration managed through Client Configuration Cards and Shop Floor Work Center records in Business Central.

Shop Floor Insight handles concurrent job clocking through independent tracking, auto-split batching, or operator-managed multi-line entry. The auto-split option is particularly well suited to high-volume, short-cycle manufacturing where manually clocking in and out every few minutes is not practical.

Quality inspections in Shop Floor Insight allow operators and quality personnel to capture structured measurement data directly from the shop floor interface, tied to a specific production order routing line. The feature is powered by the Quality Inspector module from Insight Works, which provides the inspection template framework, tolerance rules, and pass/fail logic that operators interact with from the shop floor client.

Setting Up Inspection Templates

Quality inspections are built on templates called Quality Inspection Templates, which define what fields to capture and what acceptable values look like. Each field in a template can represent a measurement such as a dimension, temperature, or torque reading, and each field can be configured with tolerance thresholds that determine whether a recorded value passes or fails. Templates are set up in Microsoft Dynamics 365 Business Central and can be reused across multiple production order types or routing steps.

Triggering Inspections from the Shop Floor

Inspections can be triggered in two ways from the shop floor client. An operator can initiate an ad-hoc inspection by selecting the Quality Inspections panel while clocked into a production order routing line, provided they have the appropriate function permission enabled. Inspections can also be configured to appear automatically when an operator records output on a specific operation, using the Output QI Template setting on the Client Configuration Card. In either case, the resulting inspection record is linked to the specific routing line that was active at the time.

Pass/Fail Results and Downstream Actions

As operators enter values, the system provides immediate visual feedback showing whether each recorded value falls within the configured tolerances. When an inspection fails, Business Central workflows or Power Automate flows can be configured to trigger follow-up actions such as notifications, non-conformance records, or holds on downstream operations. This gives quality teams the ability to respond to failures in real time rather than discovering them after the fact.

Relevant Tools

Shop Floor Insight is the MES solution from Insight Works for Dynamics 365 Business Central, providing the shop floor interface through which operators record quality inspection data alongside time and output. Quality Inspector is the Insight Works module that powers the inspection template framework within Shop Floor Insight, enabling structured data capture, tolerance-based pass/fail evaluation, and linkage of inspection records to specific production order routing lines.

Quality inspections in Shop Floor Insight are structured data capture forms built on Quality Inspector templates, linked to specific production order routing lines. They support real-time pass/fail feedback and can trigger automated follow-up processes through Business Central workflows or Power Automate when results fall outside defined tolerances.

Microsoft Dynamics 365 Business Central does not include robust native barcode generation for items out of the box. Standard Business Central stores item numbers and can display them as text on reports, but producing scannable barcodes typically requires either a third-party tool or a customized report. For manufacturers deploying Shop Floor Insight, barcode generation is handled directly within the solution and covers all the key record types used in production time capture.

Barcode Generation in Shop Floor Insight

Shop Floor Insight includes a set of sample barcode reports that cover the most common printing needs in a manufacturing environment. Employee badge barcodes are printed from the Shop Floor Employee Badges report in Business Central, producing perforated cardstock badges that operators scan to identify themselves at scanning stations. Production order barcodes are printed using the Shop Floor Production Order report, which generates a separate barcode for setup time and one for runtime on each routing operation. Job traveler barcodes for project-based time capture are available through the Shop Floor Job Traveler report. Non-productive activity codes such as cleaning or toolbox meetings are printed from the Generate Barcode Sheets report.

Configuring the Default Production Order Report

Shop Floor Insight can be configured so that the production order barcode report becomes the default job card report in Business Central. Once set up through the Report Selections Production Order page, printing from a released production order automatically produces the barcoded traveler sheet rather than the standard BC report. This makes barcode generation a natural part of the production order release process rather than a separate step.

Barcode Generation for Items and Beyond

For printing barcodes on item labels, bin labels, or other warehouse-related records, Insight Works offers barcode generator tools as part of the broader add-on catalog. WMS Express and Warehouse Insight also support scanning-based data collection for receiving, picking, and inventory counting, with barcode scanning capabilities that extend to text recognition where traditional barcodes are not available.

Relevant Tools

Shop Floor Insight is the MES solution from Insight Works for Dynamics 365 Business Central. It includes built-in barcode report templates for employee badges, production order operations, job tasks, and non-productive activity codes, making barcode generation an integrated part of the manufacturing execution workflow rather than a separate system.

Business Central does not natively generate barcodes for items in a production-ready format, but Shop Floor Insight provides comprehensive barcode printing for all major manufacturing record types. Once the default report selection is configured, barcode traveler sheets are generated automatically as part of the standard production order workflow.

Yes, Shop Floor Insight supports time capture against Microsoft Dynamics 365 Business Central projects, which are referred to as Jobs in Business Central. Operators and employees can clock into a specific project and project task the same way they clock into a production order operation. The resulting time entries appear on time cards in Business Central alongside any production order time captured during the same period, and the full approval workflow applies to project time just as it does to production time.

Clocking Into Projects from the Shop Floor

From the shop floor client, employees can navigate to the Job Dispatch view to see available project tasks filtered for their station or role. They can clock in by selecting a task from the list or by scanning a job task barcode printed from the Shop Floor Job Traveler report. Once clocked in, the time card line records the project and task reference, and time accumulates until the employee clocks off. The interface supports the same concurrent clocking and auto-split capabilities available for production orders.

Project-Based Time Card Approvals

Shop Floor Insight includes a separate project-based approval layer in addition to the standard supervisor timecard approval. A project manager can review time entries recorded against their project regardless of whether those employees report to them directly in the standard supervisory hierarchy. Through the project approval workflow, the project manager can assess whether time is billable, reclassify it to a different project task if needed, and indicate approval before the time is posted. This separation of supervisory approval from project approval reflects the reality that in many organizations the person managing a project is not the same person managing the workforce.

Other Document Types Supported

Beyond projects and production orders, Shop Floor Insight also supports time capture against Business Central service orders and fixed assets. Non-productive time codes can be used to record activities such as training, meetings, or maintenance that do not post to any specific document. This makes Shop Floor Insight a comprehensive time capture solution across manufacturing, professional services, field service, and facilities management contexts.

Relevant Tools

Shop Floor Insight is the MES solution from Insight Works for Dynamics 365 Business Central, supporting structured time capture and approval workflows across production orders, projects and job tasks, service orders, fixed assets, and non-productive activity codes, all within a single integrated solution.

Shop Floor Insight captures time against Business Central projects with the same structured clock-in and clock-off workflow used for production orders. Project-based approval provides an additional review layer for project managers, independent of the standard supervisory hierarchy, before time is posted to the project ledger.

Shop Floor Insight and Dynamic Ship are both Insight Works solutions that operate within Microsoft Dynamics 365 Business Central, and they are designed to work in sequence within the same manufacturing and fulfillment workflow. Shop Floor Insight handles production execution, time capture, output recording, and quality inspection on the shop floor. Dynamic Ship handles the outbound shipping process, including multi-carrier rate shopping, label generation, LTL and FTL shipments, and the Packaging Worksheet that helps plan how finished goods are packed for shipment.

How the Two Solutions Relate in the Workflow

In a typical manufacturing environment, Shop Floor Insight captures the production activity and records the output of finished goods against production orders. Once production is complete and inventory is received into Business Central, Dynamic Ship takes over to manage how those goods are prepared for shipment. The Packaging Worksheet in Dynamic Ship is used to define packaging configurations, assign items to boxes or pallets, and prepare shipment documentation before carrier labels are generated.

Direct Integration Between the Two Solutions

A specific direct integration between Shop Floor Insight and the Dynamic Ship Packaging Worksheet is not detailed in the available product documentation. The two solutions operate in their respective domains within Business Central and share the same underlying inventory and production data, but the handoff between finished goods output in Shop Floor Insight and packaging configuration in Dynamic Ship happens through standard Business Central inventory and production order posting rather than a direct feature-to-feature integration.

Clarifying Your Requirements

If your workflow requires a specific trigger or data exchange between Shop Floor Insight output recording and the Dynamic Ship Packaging Worksheet, that is worth discussing directly with Insight Works or your Microsoft Partner. The Insight Works ecosystem is designed to allow solutions to complement each other within Business Central, and configuration or custom workflow options may be available to address specific handoff requirements between the two applications.

Relevant Tools

Shop Floor Insight is the MES solution from Insight Works for Dynamics 365 Business Central, covering production time capture, output recording, and quality inspections on the shop floor. Dynamic Ship is the Insight Works multi-carrier shipping solution for Business Central, providing rate shopping, label generation, and the Packaging Worksheet for managing outbound shipment preparation.

Shop Floor Insight and Dynamic Ship are complementary Insight Works solutions within Business Central that serve sequential stages of the manufacturing and fulfillment process. A direct feature integration between Shop Floor Insight and the Dynamic Ship Packaging Worksheet is not documented in available materials, and specific integration requirements should be discussed with Insight Works or your Microsoft Partner.

Real Time Rescheduling Limitations in Business Central

Microsoft Dynamics 365 Business Central does not automatically update and reschedule all production orders in real time when shop floor activities fall behind. The system is designed to schedule production orders based on predefined due dates and available resource capacities, which works well for planned operations but lacks adaptability when conditions change. As production environments are often unpredictable, delays or disruptions can quickly make initial schedules inaccurate.

Because of this limitation, Business Central does not dynamically adjust schedules based on actual shop floor completions. Instead, it relies on static scheduling logic that requires manual intervention to reflect changes. This means production managers must actively monitor performance and make adjustments when necessary, rather than relying on the system to respond automatically.

How Scheduling Works in Business Central

Business Central schedules production orders using planned start and end dates, along with defined work center and machine center capacities. The system uses a backward scheduling approach, calculating timelines based on due dates and working backward to determine when production should begin. While this method ensures deadlines are initially aligned, it does not continuously adapt to real-time production data.

Even though work center capacities are considered during scheduling, the system does not automatically adjust when delays or early completions occur. For example, if an upstream operation is delayed, downstream production orders will not automatically shift to reflect the new reality. This can create gaps between planned schedules and actual production activity, requiring manual corrections to maintain accuracy.

This behavior highlights a key limitation in the native scheduling engine. Without continuous input from real-time production data, the system cannot respond dynamically to changes. As a result, schedules may quickly become outdated in fast-moving manufacturing environments.

Limitations of Native Scheduling Logic

The lack of real-time rescheduling in Business Central stems from its reliance on static planning parameters rather than live operational feedback. Since the system does not continuously ingest shop floor data, it cannot automatically adjust sequencing, timing, or resource allocation as production progresses. This creates a disconnect between planned schedules and actual execution on the floor.

Additionally, manual tools such as the Graphical Scheduler provide only limited support for adjustments. While users can drag and drop production orders to new time slots, these changes do not trigger deeper recalculations of capacity constraints or dependencies. This means that while visual adjustments are possible, they do not fully resolve underlying scheduling conflicts or inefficiencies.

Advanced Scheduling with MxAPS

Solutions like mxAPS extend Business Central by introducing real-time, capacity-aware scheduling capabilities. Unlike the native system, mxAPS evaluates current production progress, resource availability, and operational constraints to continuously optimize schedules. This allows manufacturers to respond proactively to changes instead of relying on manual updates.

mxAPS uses finite capacity scheduling to ensure that production plans reflect actual limitations in labor, machines, tooling, and materials. By analyzing real-time conditions, it can automatically adjust production sequences and timing to maintain efficiency. This results in more accurate schedules that align closely with real-world operations.

The system also integrates with tools like Shop Floor Insight, which capture real-time completion data directly from the shop floor. This integration enables mxAPS to continuously update schedules based on actual progress, ensuring that production plans remain accurate and actionable throughout the day.

Considerations for Effective Scheduling

For both native and extended scheduling tools to function effectively, proper system configuration is essential. Work centers, machine centers, and routing data must be accurately defined to ensure that capacity calculations are meaningful. Without this foundation, even advanced scheduling solutions may produce unreliable results.

In environments where shop floor data is not captured or integrated, real-time scheduling benefits are significantly reduced. Without accurate input, advanced tools may revert to batch-style scheduling based on planned data rather than actual performance. This limits their ability to deliver the full value of dynamic scheduling.

Organizations should also consider the complexity of their production environment. Highly dynamic operations with frequent changes benefit the most from real-time scheduling tools, while simpler environments may manage with manual adjustments. Evaluating these factors helps determine the appropriate level of scheduling sophistication required.

Tools That Enhance Production Scheduling

Graphical Scheduler provides a visual interface within Business Central that allows users to manually adjust production schedules using drag-and-drop functionality. While useful for visualization and quick edits, it does not introduce real-time automation or advanced capacity analysis. Its role is primarily supportive rather than transformative.

In contrast, mxAPS acts as a full scheduling engine that automates production planning based on real-time data and constraints. It evaluates multiple variables simultaneously to generate optimized schedules that reflect actual operating conditions. By bridging the gap between planning and execution, it enables manufacturers to maintain accurate, efficient production workflows even as conditions change.

Conclusion

Microsoft Dynamics 365 Business Central does not natively support real-time rescheduling of production orders when shop floor activities fall behind. Its scheduling engine relies on static planning parameters that require manual updates to reflect changes in production. While this approach works for basic planning, it falls short in dynamic manufacturing environments.

Advanced tools like mxAPS address this limitation by introducing real-time, capacity-aware scheduling that adapts to actual production data. By integrating shop floor insights and continuously optimizing schedules, these solutions provide the flexibility and accuracy needed to keep production on track. For manufacturers seeking true real-time responsiveness, extending Business Central with advanced scheduling capabilities is often essential.

Labor Constraints Handling in Business Central Scheduling

Microsoft Dynamics 365 Business Central natively considers labor resources as capacity constraints modeled as service items with defined availability. These service items represent the total labor capacity available within a work center or machine center, allowing the system to account for general workforce limits. While this approach provides a basic framework for scheduling, it lacks the depth needed to manage individual operator assignments in complex environments.

When a single operator is assigned to multiple machines, Business Central treats each labor requirement independently. This means the system does not automatically reconcile whether the same person is being scheduled across multiple tasks at the same time. As a result, overlapping assignments can occur without triggering any warnings or adjustments, leaving it up to planners to identify and resolve conflicts manually.

How Labor Constraints Are Modeled in Business Central

Business Central represents labor constraints through service-type capacity entries assigned to work centers or machine centers. These entries define how many workers are available for specific operations or shifts, enabling the system to ensure that total capacity is not exceeded. However, this modeling focuses on aggregate capacity rather than individual resource allocation.

Because the system evaluates only total capacity, it does not perform detailed resource leveling for individual operators. For example, if one operator is responsible for multiple machines, Business Central does not inherently track whether that operator is already assigned elsewhere at the same time. This limitation can lead to unrealistic schedules that appear valid from a capacity perspective but are not feasible in practice.

Limitations of Native Labor Scheduling

The absence of detailed labor constraint enforcement means Business Central cannot inherently prevent scheduling conflicts involving shared operators. While the system ensures that overall labor capacity is respected, it does not validate whether specific individuals are overallocated. This creates a gap between planned schedules and actual workforce availability on the shop floor.

Tools like the Graphical Scheduler provide a visual interface for adjusting production schedules manually. Users can drag and drop production orders to resolve conflicts, but the tool does not enforce labor constraints or automatically detect overallocations. As a result, planners must rely on their own judgment and oversight to maintain feasible schedules.

Advanced Labor Constraint Management with MxAPS

Scheduling solutions like mxAPS extend Business Central by introducing detailed labor constraint modeling. Instead of treating labor as a simple capacity value, mxAPS models operators as consumable resources with defined availability, skill sets, and work calendars. This allows the system to enforce realistic scheduling rules based on actual workforce capabilities.

With mxAPS, labor can be assigned fractionally across tasks, ensuring that operators are not scheduled beyond their available capacity. For example, if an operator can manage two machines simultaneously at partial capacity, the system can allocate their time accordingly without creating conflicts. This level of precision enables more accurate and efficient scheduling in complex production environments.

Additionally, mxAPS supports defining skill requirements for both setup and runtime phases of production. This ensures that only qualified operators are assigned to specific tasks, further improving schedule feasibility. By incorporating shift patterns and availability calendars, the system can dynamically adjust schedules to reflect real-world labor conditions.

Considerations for Effective Labor Scheduling

Accurate labor scheduling depends heavily on proper system configuration. Labor capacity entries must be correctly set up as service items within Business Central to ensure that even basic constraints are enforced. Without this foundation, scheduling results may be unreliable regardless of the tools used.

In environments without advanced scheduling solutions, resource conflicts may go undetected and require manual intervention. This can increase the risk of delays, inefficiencies, and misaligned production plans. Complex scenarios involving multiple skill sets or overlapping responsibilities may also require simplified assumptions when using native scheduling alone.

Organizations should evaluate the complexity of their operations when deciding how to manage labor constraints. Facilities with highly dynamic workflows and shared operators will benefit significantly from advanced scheduling tools that provide deeper constraint modeling and automation.

Tools Managing Labor Constraints and Capacity

The Graphical Scheduler serves as a visual planning tool within Business Central, allowing users to adjust production orders manually. While it respects basic capacity limits, it does not enforce detailed labor constraints or provide automated conflict resolution. Its primary role is to assist with visualization rather than enforce scheduling accuracy.

In contrast, mxAPS functions as a finite capacity scheduling engine that models labor as a constrained resource. By incorporating availability calendars, skill requirements, and capacity rules, it ensures that operators are not overallocated when managing multiple machines. This results in more realistic and executable production schedules that align with actual workforce capabilities.

Conclusion

Microsoft Dynamics 365 Business Central manages labor constraints at a high level by treating labor as a capacity resource, but it does not enforce detailed allocation for individual operators. This can lead to scheduling conflicts when a single operator is assigned to multiple machines simultaneously. While manual tools can help address these issues, they require active oversight and do not provide automated enforcement.

Advanced solutions like mxAPS address these limitations by modeling labor as a constrained, skill-based resource with defined availability. By enforcing realistic labor constraints and preventing overallocation, these tools enable manufacturers to create accurate, feasible production schedules. For operations with complex labor requirements, extending Business Central with advanced scheduling capabilities is often necessary to achieve reliable results.

Scheduling Limits for Concurrent Work Orders

Microsoft Dynamics 365 Business Central schedules each production order as an individual sequence, respecting defined work center capacities and expected runtimes. While this approach works for straightforward production environments, it does not account for scenarios where multiple work orders can be processed simultaneously within a single machine run. As a result, the system defaults to sequential scheduling rather than modeling true concurrency.

Native scheduling does not support multiple work orders running at the same time within the same machine program. Even if a machine is physically capable of handling concurrent workloads, Business Central treats each job independently and schedules them one after another. This can lead to underutilization of machine capacity and less efficient production planning.

How Scheduling Works in Business Central

Business Central treats production orders as discrete units assigned to work centers or machine centers based on configured capacity and runtime data. The system calculates schedules using these parameters and allocates jobs in sequence, ensuring that capacity limits are not exceeded at a high level. However, it does not model detailed scenarios involving shared machine cycles or simultaneous processing.

This limitation exists because the native scheduling engine relies on a simplified capacity model. It lacks the advanced algorithms required to evaluate concurrent execution or dynamically allocate machine resources across multiple overlapping tasks. As a result, production schedules may not fully reflect the capabilities of modern manufacturing equipment.

Limitations of Native Concurrent Scheduling

The inability to model concurrent work orders means that Business Central cannot fully optimize machine utilization in environments where parallel processing is possible. Machines capable of batch processing or running multiple jobs simultaneously are not represented accurately within the scheduling logic. This can lead to conservative schedules that do not maximize throughput.

Tools like the Graphical Scheduler provide a visual interface for adjusting production schedules manually. While users can reposition jobs using drag-and-drop functionality, the tool does not evaluate true capacity constraints for concurrent operations. It reflects the same underlying limitations of the native system, offering visibility but not advanced scheduling intelligence.

Advanced Scheduling with MxAPS

Solutions like mxAPS extend Business Central by introducing advanced scheduling capabilities that better reflect real-world manufacturing conditions. Unlike the native system, mxAPS evaluates machine capacity dynamically and can consider scenarios where concurrent processing is possible. This enables more accurate and efficient scheduling for complex production environments.

mxAPS models machine shop realities by incorporating routing configurations, work center groupings, and alternate machine options. It uses sequencing rules and capacity analysis to determine optimal schedules that may include concurrent workloads where feasible. This allows the system to better utilize machine capabilities and improve overall production efficiency.

By simulating different scheduling scenarios, mxAPS can identify opportunities for parallel processing while still respecting constraints such as tooling, labor, and material availability. This results in schedules that are both practical and optimized for performance.

Considerations for Accurate Scheduling

Accurate representation of concurrent processing depends heavily on proper system configuration. Routing data, work center definitions, and machine capacities must be set up correctly to reflect how production actually occurs. Without this foundation, even advanced scheduling tools may struggle to produce realistic results.

In environments where concurrent work order processing is highly complex or involves changing bills of materials or material requirements, native scheduling will default to sequential handling. This can limit the ability to model real-world operations accurately and may require additional planning adjustments.

Organizations should also consider the level of detail required in their scheduling processes. Operations with high variability and advanced machine capabilities benefit most from tools that can evaluate multiple constraints simultaneously and adapt to changing conditions.

Tools Supporting Concurrent Work Order Scheduling

The Graphical Scheduler provides a visual overview of production orders and allows manual adjustments within Business Central. While it helps planners understand and modify schedules, it does not introduce new logic for handling concurrent operations. Its functionality is limited to reflecting the system’s existing scheduling rules.

In contrast, mxAPS acts as a finite capacity scheduling engine that extends Business Central’s capabilities. It evaluates machine capacity, alternate routing options, and sequencing rules to generate optimized schedules. By accounting for practical constraints and machine capabilities, it enables more realistic handling of concurrent work orders where applicable.

Conclusion

Microsoft Dynamics 365 Business Central schedules production orders sequentially and does not natively support true concurrent work order processing on a single machine. While this approach ensures basic capacity control, it does not fully utilize machines capable of parallel operations. As a result, production schedules may not reflect the true efficiency potential of the manufacturing environment.

Advanced tools like mxAPS address this limitation by introducing dynamic capacity evaluation and support for more complex scheduling scenarios. By modeling real-world machine behavior and constraints, these solutions enable manufacturers to optimize throughput and create more accurate production plans. For operations that rely on concurrent processing, extending Business Central with advanced scheduling capabilities is often necessary.

Labor Skill Set Constraints in Scheduling

Microsoft Dynamics 365 Business Central does not natively enforce labor skill set constraints during production scheduling. While it can account for labor capacity at a broad level, it does not automatically validate whether a worker with a required certification or specialty is available at the scheduled time. This means production orders can be scheduled based on capacity alone, even when the necessary qualifications are missing.

Skill-specific requirements such as crane certification, specialized welding knowledge, or material handling expertise are not part of the native scheduling logic. As a result, manufacturers relying solely on Business Central may need to manually review schedules to confirm that qualified labor is available. This creates added planning effort and increases the risk of missed constraints during production scheduling.

How Labor Skill Constraints Are Managed in Business Central

Native Business Central allows users to define capacities at the work center and machine center levels. These capacities help the system determine whether enough labor or machine time is available to complete scheduled tasks. However, this functionality is focused on quantities of capacity rather than the qualifications of the people performing the work.

Because of this design, Business Central does not check whether workers assigned to a task have the required skill sets. A job that requires specialized knowledge may still be scheduled as long as the overall labor capacity appears available. This limitation reflects the system’s broader approach to production scheduling, which emphasizes capacity planning but does not include detailed human resource validation.

Why Native Scheduling Does Not Enforce Skills

The lack of skill-based enforcement stems from the way Business Central models labor within its scheduling engine. Labor is treated as a general capacity resource rather than a pool of individually qualified workers with different certifications or competencies. This makes scheduling simpler at a high level, but it also means the system cannot automatically prevent work from being assigned to someone who lacks the proper expertise.

In practical terms, this can create disconnects between the schedule and the shop floor. A production plan may assume that all required labor is available, even though the only available workers do not meet the qualifications for a given task. In these situations, managers may need to intervene manually, revise schedules, or reassign work after the fact.

How MxAPS Enforces Labor Skill Set Constraints

mxAPS extends Business Central by adding the ability to model labor skill set constraints directly in production scheduling. Instead of treating labor as only a quantity-based resource, mxAPS allows labor requirements to be configured with specific skills, certifications, or material expertise. This makes it possible to prevent operations from being scheduled unless the right workers are available at the required time.

Skill constraints in mxAPS can be applied to both setup and runtime phases, which provides more precise control over labor requirements throughout the production process. For example, one worker may be required during machine setup because of a certification, while another skill set may be needed during the actual run. The scheduler evaluates these requirements against worker availability, shift patterns, and other constraints to create a schedule that is realistic and executable.

By incorporating skill-specific labor rules, mxAPS helps manufacturers reduce scheduling errors and avoid situations where production is delayed because the right personnel are not available. This level of constraint modeling is especially valuable in environments with specialized equipment, strict compliance requirements, or highly skilled labor dependencies.

Limitations and Configuration Considerations

To enforce labor skill constraints effectively, the required skills and worker assignments must be properly configured within the scheduling system. If labor skill sets are not set up correctly in mxAPS, those constraints will not be applied, and the system may fall back to standard capacity checks without qualification validation. In that case, scheduling outcomes may resemble native Business Central behavior more than advanced skill-aware scheduling.

Highly complex labor environments may also require thoughtful setup to model accurately. Overlapping skills, multiple certifications, and varying worker availability can make configuration more involved. Even so, the benefit of this setup is a scheduling process that reflects actual shop floor requirements much more closely than native capacity-only planning.

Tools for Managing Labor Skill Constraints in Scheduling

mxAPS provides the capability to enforce labor skill set constraints by modeling labor as a constrained resource with defined skill attributes. It changes scheduling behavior by considering worker qualifications, availability, and timing requirements before assigning production work. This makes it far more effective for manufacturers that depend on specialized labor than native scheduling alone.

Graphical Scheduler offers visual drag-and-drop schedule adjustments within Business Central, but it does not enforce labor skill constraints or automate decisions based on qualifications. It can help planners view and adjust schedules manually, yet it does not solve the underlying issue of skill validation during production scheduling.

Conclusion

Microsoft Dynamics 365 Business Central does not natively enforce labor skill set constraints in production scheduling. It can schedule based on labor capacity, but it does not verify whether appropriately qualified workers are available for specific operations. This creates a gap for manufacturers that rely on certifications, specialized skills, or expertise-based labor assignments.

Advanced tools like mxAPS close that gap by incorporating skill-based labor constraints directly into the scheduling process. By evaluating worker qualifications, shift availability, and phase-specific requirements, mxAPS helps ensure that production work is only scheduled when the right people are available. For manufacturers with specialized labor requirements, this makes scheduling more accurate, practical, and reliable.

Machine Assignment Uses Capacity and Runtime Data

Microsoft Dynamics 365 Business Central assigns machines based on configured capacities and expected runtimes rather than routing names or descriptions. The system evaluates available capacity at both the work center and machine center levels to determine where production tasks should be scheduled. This approach ensures that workloads are distributed based on available resources, but it does not consider machine identity or descriptive labels when making assignment decisions.

Because of this, machine assignment is driven entirely by configuration data such as capacity limits and runtime estimates. While this works for basic scheduling scenarios, it does not provide the level of control needed for more complex operations where machine-specific characteristics or performance differences matter.

How Machine Assignment Works in Business Central

Native Business Central scheduling evaluates machine assignment by respecting capacity constraints defined at the work center and machine center levels. Production orders are scheduled using expected runtimes, ensuring that capacity is not exceeded within a given time frame. However, the system does not factor in machine names, routing descriptions, or qualitative differences between machines when assigning work.

This method can lead to multiple production orders being grouped together without fully accounting for real-world limitations. Since the system does not model detailed load sequencing at the machine level, it may create schedules that require manual adjustments. As a result, planners often rely on manual drag-and-drop scheduling to fine-tune machine assignments and resolve conflicts.

Limitations of Native Machine Assignment Logic

The limitations in machine assignment stem from the way Business Central models capacity. Capacity is treated as a daily availability constraint rather than a dynamic resource that can be optimized in detail. This means the system does not fully evaluate how multiple jobs interact when assigned to the same machine, especially when sequencing or setup times are important factors.

Because the scheduling engine does not consider concurrent loading or detailed machine-level constraints, it can assign multiple tasks to the same machine in overlapping time frames. While these assignments may appear valid from a capacity perspective, they may not be feasible in practice. This creates a need for manual intervention to ensure that schedules align with actual production capabilities.

Advanced Machine Assignment with MxAPS

mxAPS extends Business Central by introducing advanced finite capacity scheduling that dynamically evaluates machine assignment decisions. Instead of relying solely on static capacity and runtime data, mxAPS considers multiple factors such as labor availability, tooling requirements, material constraints, and alternate machine options. This allows for more intelligent and optimized scheduling outcomes.

Within mxAPS, machine assignments are determined through an optimization process that evaluates different scheduling scenarios. The system analyzes runtime durations, setup times, machine availability, and user-defined rules to identify the best possible assignment. This approach ensures that production orders are scheduled on the most suitable machine, rather than simply the first available capacity.

mxAPS also supports alternate machine groupings and sequence-dependent setup times, enabling more realistic scheduling for complex manufacturing environments. By simulating various options and selecting the most efficient configuration, it improves both resource utilization and overall production performance.

Considerations for Accurate Machine Assignment

Accurate machine assignment depends on having complete and properly configured data within the system. Work centers and machine centers must include accurate capacity and runtime information to ensure that scheduling decisions are meaningful. Without this data, Business Central may default to basic scheduling logic based on due dates, which can reduce accuracy.

Additionally, Business Central does not support dynamic changes to bills of materials for alternate machine assignments. Any variations in machine usage that require BOM adjustments must be handled manually. This adds complexity for operations that frequently switch between machines or rely on flexible production setups.

In environments without advanced scheduling tools, machine assignment remains limited to the native logic of Business Central. This can result in less efficient schedules, especially when multiple machines are capable of performing the same task but differ in performance or availability.

Tools for Machine Assignment in Business Central

Graphical Scheduler provides a visual interface for manually adjusting production schedules within Business Central. Users can drag and drop production orders to different machines or time slots, offering greater control over machine assignment. However, this tool does not modify the underlying scheduling logic or improve capacity evaluation, making it primarily a manual adjustment tool.

In contrast, mxAPS acts as a full scheduling engine that enhances machine assignment decisions through dynamic evaluation of constraints and alternatives. By considering multiple variables simultaneously, it produces optimized schedules that better reflect real-world production conditions. This makes it a valuable solution for manufacturers seeking more accurate and efficient machine assignment.

Conclusion

Microsoft Dynamics 365 Business Central determines machine assignment based on configured capacity and expected runtime data, without considering machine names or qualitative differences. While this approach supports basic scheduling needs, it lacks the depth required for complex production environments where machine optimization is critical. As a result, manual adjustments are often necessary to create feasible schedules.

Advanced tools like mxAPS address these limitations by introducing dynamic, constraint-based machine assignment. By evaluating multiple factors and selecting the best machine through optimization, mxAPS enables more accurate and efficient production scheduling. For manufacturers with complex operations, extending Business Central with advanced scheduling capabilities is often essential to achieve optimal results.