SUMMARY | This chapter explains how Code 128 barcodes work and how they connect shop-floor activities to Infor M3, a leading enterprise resource planning system. Using real-world examples from American manufacturers, we show how scanning a simple barcode on a routing card updates labor hours and material usage instantly in the Manufacturing Order System (MOS). The goal is to give you a clear, non-technical view of a technology that keeps modern factories efficient, accurate, and transparent. | 
| CHAPTER 48: INFOR M3 - PRODUCTION ORDER TRACKING | Scanning Code 128 on a shop-floor routing card updates the MOS (Manufacturing Order System) with actual labor hours and material consumption in real time. | INTRODUCTION | Imagine a factory floor the size of several football fields. Workers move between heavy machines, forklifts carry pallets of raw steel, and supervisors carry tablets that show hundreds of open production orders. In the middle of this busy scene, a single worker picks up a handheld scanner and points it at a small black-and-white label attached to a routing card. The scanner beeps. In less than one second, the central computer system knows exactly how many minutes that worker spent on that job, how many parts were completed, and how much material was used. That beep is not just a sound; it is a message that travels through wires and wireless networks to update the heart of the company's business software, Infor M3. | This chapter is about that beep. We will explore the barcode technology that makes it possible, specifically the Code 128 symbology, and we will see how it integrates with Infor M3, one of the most popular enterprise resource planning systems used by mid-sized and large manufacturers in the United States. We will focus on production order tracking, which is the process of following a job from the moment it is released to the shop floor until it is completed and moved to inventory. The routing card, which lists the sequence of operations, becomes a powerful data collection tool when it carries a Code 128 barcode. | We will avoid complex formulas and tables. Instead, we will walk through real American factories: a medical device maker in Minnesota, an automotive supplier in Ohio, a food processing plant in California, and a defense contractor in Texas. Each example shows a different way that Code 128 scanning improves speed, reduces errors, and gives managers real-time visibility. By the end, you will understand why this humble barcode remains a cornerstone of Industry 4.0, even as newer technologies like RFID and computer vision gain attention. | 
| PART ONE: UNDERSTANDING CODE 128 | Before we dive into the integration with Infor M3, let us take a moment to appreciate the barcode itself. Code 128 is a high-density linear (one-dimensional) symbology that can encode all 128 characters of the American Standard Code for Information Interchange, or ASCII. That means it can handle uppercase and lowercase letters, digits, punctuation marks, and even control characters like carriage return and tab. This flexibility is one reason why Code 128 is preferred over older symbologies like Code 39, which is limited to uppercase letters and a few special characters. | Code 128 was introduced in 1981 by Ted Williams, who worked for the company that later became Computer Identics. It was designed to pack more information into a smaller space. A Code 128 barcode can be as short as a few inches for a simple part number, or it can stretch across a large label if it contains a long serialized string. The structure includes a start character, the encoded data, a check digit, and a stop character. The check digit is calculated using a weighted modulo-103 algorithm, which ensures that even if the label is scratched or partially smudged, the scanner can detect an error and ask for a re-scan. | For shop-floor workers, none of this technical detail matters. They only care that the barcode scans quickly and reliably. The real magic is in the data that the barcode represents. On a routing card for Infor M3, the Code 128 barcode typically encodes a composite key that includes the manufacturing order number, the operation sequence number, the work center identifier, and sometimes a date or shift code. When scanned, this string is sent to the Infor M3 middleware, which parses the string, validates it against active production orders, and triggers the appropriate transaction. | Why Code 128 over other symbologiesFirst, it is extremely robust. It has built-in error detection, and modern scanners can read it from odd angles, under poor lighting, or even through protective plastic sleeves. Second, it is widely supported by every major scanner manufacturer, from Zebra to Honeywell to Datalogic. Third, it does not require a database lookup to interpret; the data itself is meaningful, unlike some proprietary 2D codes that often need a server to decode the payload. Fourth, it prints well on thermal transfer labels, direct thermal paper, and even metal tags using laser etching. This versatility makes it ideal for harsh environments like foundries, bakeries, and chemical plants. | 
| PART TWO: INFOR M3 AND THE MANUFACTURING ORDER SYSTEM | Infor M3 is a cloud-based or on-premise ERP suite that serves industries such as automotive, food and beverage, fashion, and industrial equipment. Its manufacturing module is built around the concept of the manufacturing order, often abbreviated as MO. Each MO contains a bill of materials (the list of raw materials and components), a routing (the sequence of steps or operations), and scheduling information like start date and due date. | The Manufacturing Order System, or MOS, is the live engine that tracks these orders. When a production planner releases an MO to the shop floor, the MOS creates a set of records for each operation. These records include planned labor hours, planned machine hours, and planned material quantities. The actual execution, however, often deviates from the plan. A machine might break down, a worker might take longer because of a difficult setup, or a subassembly might be scrapped due to quality issues. Without real-time data collection, these deviations go unnoticed until the end of the shift, or worse, until the end of the week. That delay causes inventory inaccuracies, missed shipments, and overtime costs. | The scanning of Code 128 on a routing card is the primary method to feed actual data back into the MOS. Each routing card is a paper or laminated sheet that travels with the physical work-in-process. It lists every operation in order: for example, cut, weld, paint, assemble, test, and pack. Next to each operation, there is a printed Code 128 barcode. The worker scans that barcode when they start the operation, when they pause, when they complete the operation, and when they report scrap or rework. Each scan sends a transaction code to Infor M3, along with a timestamp, the worker's badge ID (often from a separate barcode on their ID badge), and the quantity of good parts produced. | The MOS then updates several tables in real time. Actual labor hours are accumulated against the operation, so supervisors can see if a job is over or under standard time. Actual material consumption is posted to the inventory subledger, so the system knows to issue components from the warehouse. If the operation consumes a serialized part, that serial number is captured via a secondary scan. At the end of the order, the MOS calculates variances between planned and actual costs, which feeds into financial reporting and continuous improvement. | What makes this integration powerful is that Infor M3 does not treat the barcode scan as a simple data entry. Instead, it runs business logic. For example, if the worker scans a barcode for operation 30 but operation 20 has not been completed, the system can issue a warning or even block the scan. If the worker reports more material than the bill of materials allows, the system can flag a potential error or request a supervisor override. These checks prevent common mistakes like skipping a critical step or using the wrong component. | 
| PART THREE: THE ROUTING CARD AS A DATA COLLECTION HUB | The routing card is an old concept. In pre-digital factories, it was a multi-part carbon form that traveled with the job. Workers would write down start times, stop times, and piece counts by hand. At the end of the day, a data entry clerk would type those numbers into a mainframe. That process was slow and error-prone. Handwriting was illegible, times were estimated, and the carbon copies often got lost. | Today's routing card looks similar but carries a digital heartbeat. The Code 128 barcodes are printed at the time the MO is released, using a thermal printer connected to Infor M3. The barcode data is dynamically generated, so it always matches the current order and operation. Some companies use reusable plastic cards with adhesive labels that are replaced for each order. Others use heavy-duty paper that stays with the pallet or tote. | The barcode on the card does not just encode a static number. In many advanced implementations, it encodes a URL or an API endpoint that points directly to the Infor M3 REST API. When the scanner reads the barcode, it triggers a secure HTTPS call to the cloud instance of Infor M3. The call includes the order, operation, worker ID, and a timestamp. This architecture allows remote sites to send data instantly to a central data center, without needing a dedicated VPN or leased line. It also simplifies the scanner configuration, because the scanner only needs to know how to parse the barcode and send an HTTP POST request. | Some U.S. manufacturers take this a step further by embedding a second barcode on the routing card for quality checks. That barcode might encode a tolerance limit or a test procedure ID. After the worker completes the operation, they scan the quality barcode and then enter a pass/fail status using a simple keypad on the scanner. Infor M3 then creates a quality notification if the result is fail, triggering a non-conformance workflow. This tight integration between production tracking and quality management is a hallmark of mature ERP implementations. | 
| PART FOUR: REAL-WORLD EXAMPLE 1 - MEDICAL DEVICE MAKER IN MINNESOTA | Consider a mid-sized medical device company called MedTech Dynamics, located in the suburbs of Minneapolis. They manufacture implantable orthopedic screws and plates. Every screw must be traceable to the batch of titanium alloy, the machine that cut the threads, the inspector who checked the dimensions, and the sterilization lot. The FDA requires this level of traceability under the Unique Device Identification (UDI) rule. | MedTech Dynamics uses Infor M3 as their core ERP. Their shop floor has 15 CNC Swiss machines, each producing hundreds of screws per hour. The routing card for a typical screw order has six operations: bar stock loading, turning, thread rolling, deburring, passivation, and final laser marking. Each operation has its own Code 128 barcode. The barcode encodes the MO number, the operation sequence, the machine center, and a random nonce to prevent replay attacks. | When a machine operator starts a new batch, they scan the routing card's first barcode. The scanner, a Zebra DS3678 with Bluetooth, pairs with a tablet computer that runs Infor M3's shop-floor app. The app shows the standard setup time and the number of pieces expected. The operator then loads the titanium bar and presses a physical button on the machine to begin. After the first piece comes out, they measure it with a digital caliper that also has a barcode scanner. They scan the part's in-process barcode (which was printed on a separate label from the warehouse) and the caliper automatically sends the measurement to the MOS. If the dimension is within spec, the operation continues. If not, the MOS pauses the order and sends an alert to the quality engineer. | At the end of the shift, the operator scans the same barcode again to report completion. The MOS calculates that the actual cycle time was 4.2 minutes per piece, compared to the standard of 4.0 minutes. The variance is automatically logged. But more importantly, the MOS updates the work-in-process inventory with the exact number of good screws produced. The scrap screws are also reported via a separate scrap barcode on the routing card, so the yield is tracked. | What makes this example particularly American is the FDA audit readiness. Every scan creates a digital audit trail with date, time, user, and machine. During a surprise FDA inspection, MedTech Dynamics can pull up the MOS transaction history for any order number and show exactly who did what, when, and with which material. The Code 128 barcode on the routing card is the linchpin of that traceability. They have been using this system since 2019, and their audit findings have dropped by 60 percent, because the data is consistent and legible. | 
| PART FIVE: REAL-WORLD EXAMPLE 2 - AUTOMOTIVE SUPPLIER IN OHIO | Our second example is Buckeye Forge, a tier-1 supplier of forged steel connecting rods for heavy-duty trucks. They are located in Cleveland, Ohio, and employ about 400 people. Their production orders are large, often 10,000 pieces per order. The routing is long: cut billet, heat, forge, trim, cool, shot blast, machine, drill, tap, and inspect. Each operation takes place in a different department spread across a sprawling plant. | Before the Code 128 integration, Buckeye Forge relied on manual data entry. At the end of each shift, team leads would collect paper tally sheets and hand them to a clerk. The clerk typed the labor hours and part counts into Infor M3, but there was always a lag of at least 24 hours. By the time the data was in the system, the parts might already be in shipping. If there was a shortage of raw material, no one knew until the next day. That caused expensive expediting and air freight charges. | In 2021, they implemented a new solution. Every forklift and every workbench now has a fixed-mount scanner from Datalogic. The routing card for each order is printed on durable synthetic paper with a heat-resistant coating. The Code 128 barcode is large enough to be read from 12 inches away, even under the oily conditions of the forging press. The barcode includes a checksum and a parity digit to reduce misreads. | The workflow is simple. When a pallet of billets arrives at the forge, the operator scans the routing card's first barcode. The MOS in Infor M3 records the start time and automatically deducts the billet quantity from the raw material inventory. After forging, the operator scans the same barcode to record the output quantity. They also scan a barcode on the tote that holds the forged parts, so the MOS knows the location of the work-in-process. When the parts move to the shot blast department, that department's scanner picks up the same routing card barcode and the MOS transfers the inventory location. | The real breakthrough came with the addition of a 'delay' barcode on the routing card. If the forging press has a breakdown, the operator scans a special Code 128 label that says 'MACHINE DOWN.' The scanner sends that code to Infor M3, which immediately calculates the downtime and adjusts the expected completion time for the entire order. The production scheduler receives a dashboard alert and can reassign the remaining parts to another press. This real-time exception handling was impossible with paper-based systems. | Buckeye Forge reports that their on-time delivery performance improved from 82 percent to 94 percent within six months of going live. Their labor reporting accuracy, measured by the variance between actual and standard hours, improved from plus or minus 15 percent to plus or minus 3 percent. The plant manager often says that the Code 128 routing card is 'the most important piece of paper in the factory,' because it connects every action to the central nervous system of the business. | 
| PART SIX: REAL-WORLD EXAMPLE 3 - FOOD PROCESSING PLANT IN CALIFORNIA | Our third example is Golden Sun Foods, a processor of canned vegetables and fruits in the Central Valley of California. They operate 24 hours a day during the harvest season, with hundreds of temporary workers who speak Spanish and Mixteco as their primary languages. The workforce is highly transient, so training on complex computer systems is impractical. The Code 128 barcode solution had to be nearly language-free. | Golden Sun Foods uses Infor M3 for financials and inventory, but they added a lightweight mobile app that runs on rugged Android handhelds. Each production order is for a specific batch of canned corn or peaches. The routing card is printed in both English and Spanish, with large color-coded areas. The Code 128 barcodes are printed in black on a bright yellow background, making them easy to spot on the busy canning line. Each barcode is accompanied by a pictogram: a clock for start/stop, a box for count, and a trash can for scrap. | The operator's routine is simple. At the beginning of the shift, they scan the routing card's main barcode using a Honeywell Voyager scanner. The scanner is connected via Wi-Fi to a local gateway, which relays the data to Infor M3 in the cloud. The MOS then displays the current operation on the handheld screen, but in large font and with minimal text. The worker taps one button for 'START' and another for 'FINISH.' They do not have to type anything. | For material consumption, the plant uses a clever method. Each pallet of raw produce arrives with a Code 128 label that encodes the lot number, weight, and grower. The worker scans that pallet label immediately after scanning the routing card. The MOS then pairs the consumed material with the production order. This is critical for food safety, because if there is a contamination issue, the system can trace every can back to the specific field and harvest date. The Food Safety Modernization Act (FSMA) mandates such traceability, and the Code 128 scanning provides the digital records without burdening the line workers. | One challenge Golden Sun Foods faced was the dusty and wet environment. Condensation from the steam blanch caused ordinary labels to smudge. They switched to polyester labels with a permanent adhesive and a matte finish. The scanners were upgraded to IP67-rated units that can survive a washdown. After these adjustments, the scan success rate reached 99.7 percent. The remaining 0.3 percent are resolved by a manual fallback: the worker enters a short numeric code printed below the barcode. | The results have been impressive. Inventory shrinkage due to unreported scrap dropped by 40 percent. Labor overtime decreased because the MOS could accurately predict when an order would finish, so supervisors could stagger breaks. Most importantly, the company passed two unannounced FDA audits with zero 483 observations, largely because the digital trail from the routing card scans provided immediate evidence of process control. | 
| PART SEVEN: REAL-WORLD EXAMPLE 4 - DEFENSE CONTRACTOR IN TEXAS | Our fourth example is Lone Star Armaments, a defense contractor in San Antonio, Texas, that manufactures precision guidance components for missiles. Their products are highly classified and subject to ITAR (International Traffic in Arms Regulations). Security is paramount. No wireless devices are allowed in the clean room, and all data must be logged on a physically isolated network. However, they still need real-time production tracking for cost accounting and schedule management. | Lone Star Armaments uses Infor M3 on a private cloud hosted within their own data center. The shop floor has wired Ethernet ports at every workstation. The scanners are corded, not wireless, to prevent any signal leakage. The routing card for each guidance unit is a metal plate with a laser-etched Code 128 barcode. Laser etching is permanent and cannot be tampered with or swapped. The barcode encodes a 24-character alphanumeric string that includes the order number, operation, and a cryptographic hash generated by Infor M3. | The process is strict. Each operation requires a two-person rule: one operator and one verifier. Both have their own barcode ID badges. The operator scans the routing card, then scans their badge, then scans the verifier's badge. The MOS in Infor M3 records all three scans in one transaction. This triple-scan ensures accountability and prevents a single person from falsifying records. The system also checks that the verifier has the correct certification level for that specific operation, because some operations require a security clearance. | Time tracking is equally rigorous. The scanner has a built-in real-time clock that is synchronized daily with a GPS time source. When the operator scans the start barcode, the MOS captures the timestamp down to the millisecond. When they scan the completion barcode, the system calculates the elapsed time. If the elapsed time is less than the minimum standard (which is set for safety reasons), the MOS rejects the transaction and flags it for review. This prevents workers from rushing through sensitive assembly steps. | The defense contractor uses the actual labor hours not just for payroll, but also for earned value management (EVM). The US Department of Defense requires EVM reporting on major programs. The Code 128 scans feed directly into the MOS, which then calculates the earned value metrics automatically. The program manager can see the cost performance index and schedule performance index in real time, without waiting for monthly reports. This capability was a key factor in winning a recent multi-year contract. | Despite the high-security environment, the system is remarkably user-friendly. The metal routing cards are mounted on a rotating carousel at each station. The worker simply pivots the card to present the correct operation barcode. There is no keyboard, no mouse, no touchscreen. The scanner beeps green for success and red for error. If a red beep occurs, the scanner displays a three-digit error code that corresponds to a laminated troubleshooting guide on the wall. This minimalist design reduces training time to less than one hour for new hires. | 
| PART EIGHT: TECHNICAL WORKFLOW OF A SCAN TRANSACTION | Now that we have seen real examples, let us walk through the technical journey of a single scan, from the handheld scanner to the MOS database. This will help you appreciate the engineering behind the simple beep. | Step 1: The worker points the scanner at the Code 128 barcode on the routing card. The scanner's laser or LED illuminates the pattern of black bars and white spaces. The imager inside the scanner captures the reflected light and converts it into an electrical signal. The onboard processor decodes the signal using the Code 128 algorithm, which identifies the start character, reads the data characters, calculates the check digit, and verifies that the check digit matches the encoded value. If the check digit fails, the scanner does not beep and the worker retries. | Step 2: Once decoded, the scanner has a raw string, for example 'MO123456-OP30-WC07-SHIFT2'. The scanner's firmware may apply a parsing rule based on a configuration file. In many Infor M3 implementations, the scanner is set to 'simple mode' where it just sends the raw string to a middleware application. In more advanced setups, the scanner itself is programmed to translate the string into a JSON payload with named fields. | Step 3: The scanner transmits the data. In the medical device example, it uses Bluetooth to a tablet, then the tablet uses Wi-Fi to send an HTTPS POST to Infor M3's API gateway. In the defense example, it uses a USB cable to a thin client, which sends the data over a wired Ethernet to an internal application server. In all cases, the transmission is encrypted using TLS 1.2 or higher, because production data is commercially sensitive. | Step 4: The Infor M3 middleware receives the payload. It first authenticates the scanner device using a client certificate or an API key. It then validates the data structure. It checks that the MO number exists and is in a released status. It checks that the operation sequence matches the routing definition. It checks that the work center is correct for that operation. If any of these validations fail, the middleware returns an error response to the scanner, and the scanner displays a red light or an error code. | Step 5: If all validations pass, the middleware constructs a database transaction. It issues an SQL UPDATE to the MOS production order table, setting the actual start time or actual completion time for that operation. It also issues an INSERT into the labor transaction log, with the worker ID, timestamp, and quantity. For material consumption, it issues an inventory issue transaction against the bill of materials. All of these SQL statements are wrapped in a database transaction with ACID properties, so that if any part fails, the entire transaction rolls back and no partial data is written. | Step 6: After the database commit, the middleware triggers any downstream events. For example, if the operation completion changes the order status to 'completed,' the system might send an email to the warehouse team to prepare for shipping. If the actual labor hours exceed a threshold, it might send a push notification to the production supervisor. These events are managed by Infor M3's workflow engine, which is configured separately from the scan logic. | Step 7: The scanner receives a success acknowledgement from the middleware, usually a simple '200 OK' HTTP status. The scanner beeps green and displays a checkmark. The entire round-trip takes less than 500 milliseconds in a well-designed network. The worker then moves on to the next task. From their perspective, they just performed a simple action that took less than a second, but in reality, they updated seven different tables, triggered two workflows, and left a permanent audit trail. | 
| PART NINE: CHALLENGES AND SOLUTIONS IN THE FIELD | No technology is perfect, and Code 128 scanning with Infor M3 comes with its own set of challenges. Let us address the most common ones and how American manufacturers overcome them. | Challenge 1: Label Damage - On a hot, oily shop floor, labels get scratched, smudged, or torn. The solution is threefold. First, use high-quality thermal transfer labels with a resin ribbon, which are more durable than direct thermal labels. Second, print the barcode in a large size with generous quiet zones (the white space on either side). Third, implement a redundant label: print the human-readable text below the barcode and also print a second smaller barcode in a different location on the card, so the worker can scan the backup if the primary is unreadable. | Challenge 2: Scanner Misdirection - Workers sometimes scan the wrong barcode, especially if multiple routing cards are placed close together. To prevent this, many shops use 'barcode guards,' which are plastic frames that physically isolate the active barcode. Others use software locking, where the scanner only accepts barcodes that match a predetermined prefix for the current order. If a worker accidentally scans a different order, the system rejects it and asks them to scan the correct card. | Challenge 3: Network Outages - In a large factory, Wi-Fi dead zones are common. If the scanner cannot reach Infor M3, the worker cannot report progress. The solution is to use batch mode. Many modern scanners have onboard memory that can store up to 50,000 scans. When the network is unavailable, the scanner stores each scan with a timestamp. When the network is restored, the scanner automatically uploads the batch to the middleware. Infor M3 processes the batch in the order of the timestamps, ensuring data integrity. However, this batch mode has a trade-off: real-time visibility is lost during the outage, so managers use redundant access points to minimize dead zones. | Challenge 4: Data Entry Errors - Even with barcodes, some data must be manually entered, such as the quantity of good parts or the reason for scrap. Typing on a scanner keypad is error-prone. To reduce mistakes, companies use 'menu-based' entry: the scanner displays a list of predefined quantities (e.g., 1, 10, 50, 100) and the worker selects one. For scrap reasons, they use a numeric code that corresponds to a list posted on the wall. This eliminates free-text typing and improves accuracy. | Challenge 5: Integration Latency - In some older versions of Infor M3, the API response time could be slow, especially during peak shift changes when hundreds of scans occur simultaneously. To solve this, manufacturers implement a message queue, such as RabbitMQ or Azure Service Bus. The scanner sends the data to the queue, which then feeds into the MOS at a controlled rate. The worker gets an immediate acknowledgement from the queue, even if the MOS is busy. This decoupling ensures that the scan experience remains fast, while the backend processes the transactions asynchronously. | 
| PART TEN: BEYOND LABOR AND MATERIAL - ADDITIONAL USE CASES | While this chapter focuses on labor hours and material consumption, Code 128 scanning on routing cards can also capture other valuable data points in Infor M3. Let us briefly explore a few. | Tool Tracking: Many operations require specific tooling, such as drill bits, dies, or fixtures. The routing card can have a barcode for each tool. The worker scans the tool barcode before starting the operation. The MOS records which tool was used and how long it was in use. This data feeds into the preventive maintenance module, which schedules tool sharpening or replacement based on actual usage, not just calendar days. A U.S. aerospace supplier in Connecticut uses this method to reduce tool breakage by 25 percent. | Operator Certification: Some operations require certified welders or electricians. The routing card barcode can trigger a validation against the worker's badge scan. Infor M3 checks the worker's certification table and denies the transaction if the worker is not certified for that operation. This is common in the oil and gas industry, where a single faulty weld can have catastrophic consequences. A Texas pipe manufacturer uses this to maintain their ASME certification. | Quality Data: As mentioned earlier, a separate quality barcode can capture inspection results. But Infor M3 can also integrate with statistical process control (SPC) software. When the worker scans the routing card after inspection, the scanner sends the measured values (e.g., diameter, hardness) along with the order number. The MOS stores these values and can generate control charts automatically. A piston ring manufacturer in Michigan uses this to monitor their grinding process and detected a drift in the mean diameter within two days, allowing them to adjust the machine before producing any nonconforming parts. | Maintenance Request: The routing card can have a barcode that says 'MAINTENANCE NEEDED.' When the operator scans it, the MOS creates a work order for the maintenance team in Infor M3's Enterprise Asset Management module. The work order includes the machine ID, the current production order, and the operator's description (entered via a picklist). This seamless handoff between production and maintenance reduces machine downtime by ensuring that maintenance requests are not lost on sticky notes. | 
| PART ELEVEN: COMPARISON WITH ALTERNATIVE TECHNOLOGIES | You might wonder why manufacturers still use one-dimensional barcodes when there are so many other options. Let us compare Code 128 with two popular alternatives: QR codes (2D matrix) and passive UHF RFID tags. | QR codes can store much more data than Code 128 and include error correction that can recover from up to 30 percent damage. However, QR codes require a camera-based scanner, which is more expensive than a laser scanner. More importantly, QR codes take up more physical space on a label, which is a constraint on small routing cards. Code 128 can be printed very narrow, which is useful when the routing card has multiple operations in a tight layout. Also, QR codes are slower to decode, especially on low-end scanners. For a high-speed production line where the worker expects a beep within half a second, Code 128 is often the safer choice. | Passive UHF RFID tags offer the advantage of reading without line-of-sight. You can place a tag inside a tote and read it as it passes through a portal. This is great for automated tracking of work-in-process. However, RFID tags are more expensive than printed labels (about 10 cents each versus less than 1 cent for a label). They also have interference issues with metal and liquids, which are common in manufacturing. In addition, RFID systems require specialized readers and antennas, and the integration with Infor M3 is more complex because the read events are non-deterministic; you might read the same tag multiple times. Code 128 gives you a deterministic, intentional scan that corresponds to a worker action, which is exactly what you need for labor reporting. | There are also vision-based systems that use cameras and machine learning to read printed text without barcodes. These are promising but are still expensive and require high-quality lighting and stable mounting. For the majority of U.S. factories, the cost-benefit ratio still favors Code 128. It is reliable, cheap, and universally understood by all ERP systems, including Infor M3. | 
| PART TWELVE: BEST PRACTICES FOR DEPLOYMENT | Based on the experiences of the four companies we profiled, and many others across the United States, we can distill a set of best practices for deploying Code 128 routing card tracking with Infor M3. | First, standardize the barcode data format. Decide whether you will encode a fixed-length string with position-based fields or a variable-length string with delimiters. Most Infor M3 consultants recommend using a pipe character or comma as a delimiter, because it is easy to parse and human-readable. For example, 'MO|123456|OP|30|WC|07'. Stick to uppercase letters and digits to avoid confusion with lowercase that might be misinterpreted by older scanners. | Second, design the routing card layout with the user in mind. Put the most frequently scanned barcode at the top right corner, which is the natural reach area for right-handed workers. Use a large font for the human-readable text underneath, so the worker can verify the operation number without scanning. Color-code the barcode background: green for start, red for stop, blue for material, orange for scrap. This visual hierarchy speeds up the scanning process and reduces mistakes. | Third, test the scanner placement and lighting. Even though Code 128 is robust, glare from overhead fluorescent lights can confuse some imagers. Position the scanners at an angle, not perpendicular to the label. If possible, use scanners with a built-in aimer (a crosshair or dot) so the worker knows exactly where to point. Perform a pilot run on a single production line for at least two weeks, and collect data on the scan failure rate. If the failure rate exceeds 1 percent, investigate the label material, printing quality, and scanner model before rolling out to the whole plant. | Fourth, train the supervisors, not just the operators. Supervisors need to understand how to read the MOS dashboard and how to troubleshoot common errors, such as 'order not found' or 'operation sequence mismatch.' They should also be empowered to override a scan if the system rejects a legitimate transaction, but that override should require a manager-level password and be logged for audit. | Fifth, plan for a phased cutover. Do not switch from manual data entry to barcode scanning all at once. Run the barcode system in parallel with the old system for a few weeks. Compare the labor hours reported by both methods. If there are significant discrepancies, find out if it is a scanner issue, a routing card issue, or a business process issue. Only after the parallel run shows consistent results should you turn off the manual entry. | 
| PART THIRTEEN: THE FUTURE OF BARCODE INTEGRATION WITH INFOR M3 | As Infor M3 evolves, the role of Code 128 is not diminishing. In fact, the latest version of Infor M3 CloudSuite includes a native 'Shop Floor Data Collection' module that supports Code 128 as a first-class input method. The new module uses an event-driven architecture, where a scan event can trigger complex workflows, including machine learning-based anomaly detection. For example, if a worker scans a routing card and reports a cycle time that is 20 percent longer than standard, the system can automatically suggest a root cause analysis based on historical data from similar orders. | We are also seeing the emergence of 'smart barcodes.' These are Code 128 symbols that encode not just an identifier, but also a small payload of contextual data, such as the expected remaining runtime for that operation. The scanner reads this data and displays it to the worker, so they can adjust their pace. This is like giving each routing card a miniature brain, without needing a database lookup. | Another trend is the combination of Code 128 with mobile augmented reality (AR). A worker can scan the routing card with a smartphone or AR headset, and the device overlays the digital information onto the physical card: for example, highlighting the next operation in yellow, showing a 3D animation of the correct assembly sequence, or displaying the torque specification. Infor M3 can push this AR content based on the scanned barcode, because the scan tells the system exactly which operation the worker is about to perform. A few early adopters in the U.S. aerospace industry are already piloting this with Microsoft HoloLens and Infor M3. | Despite these innovations, the fundamental value remains unchanged: a fast, accurate, and low-cost way to bridge the physical world of the shop floor and the digital world of the ERP. Code 128 will likely coexist with newer technologies for many years, because it is embedded in billions of labels, scanners, and business processes. Replacing it entirely would be prohibitively expensive, and there is no compelling reason to do so. | 
| PART FOURTEEN: COMPREHENSIVE SUMMARY AND TAKEAWAYS | Let us now bring together everything we have covered in this chapter. | We started with the simple observation that scanning a Code 128 barcode on a routing card updates Infor M3's Manufacturing Order System with real-time labor and material data. This is not a trivial data entry task; it is a transaction that triggers validations, updates multiple tables, logs an audit trail, and can initiate downstream workflows. We learned that Code 128 is a high-density, reliable one-dimensional symbology that encodes up to 128 ASCII characters, including a self-checking digit. Its popularity stems from its robustness, flexibility, and universal support across scanner brands. | We then explored the role of Infor M3, a powerful ERP system widely used in American manufacturing. Its MOS module is the central repository for production order status, planned versus actual costs, and inventory movements. The routing card, which lists the sequence of operations, becomes a dynamic data collection device when printed with Code 128 barcodes for each operation. The integration between the scanner and Infor M3 can be wired or wireless, on-premise or cloud-based, but in all cases, it delivers near-instantaneous feedback to the worker and the supervisor. | Our four real-world examples highlighted the diversity of applications. MedTech Dynamics in Minnesota uses Code 128 to achieve FDA-level traceability for medical implants, with every scan contributing to a robust audit trail. Buckeye Forge in Ohio improved on-time delivery from 82 to 94 percent by adding delay barcodes that capture machine downtime instantly. Golden Sun Foods in California overcame language barriers and harsh washing environments to meet FSMA traceability, reducing inventory shrinkage by 40 percent. Lone Star Armaments in Texas operates under ITAR security constraints, using laser-etched metal cards and triple-scan accountability to support earned value management for defense contracts. | We also walked through the technical workflow of a scan, from optical decoding to HTTPS transmission to database commit, emphasizing the importance of validation and error handling. We addressed common challenges like label damage, scanner misdirection, network outages, data entry errors, and integration latency, offering practical solutions that American factories have proven effective. We went beyond labor and material to cover tool tracking, operator certification, quality data capture, and maintenance requests, showing that the same routing card barcode can serve multiple functions. | In our comparison with QR codes and RFID, we argued that Code 128 remains the best choice for most shop-floor tracking applications because of its low cost, speed, simplicity, and deterministic scan action. We provided best practices for deployment, including data format standardization, user-centric card design, scanner placement testing, supervisor training, and phased cutover. Finally, we looked ahead to smart barcodes and AR integration, affirming that Code 128 will continue to be a vital component of Infor M3 ecosystems for the foreseeable future. | The overarching message of this chapter is that a small, printed pattern of black and white bars can have a massive impact on manufacturing efficiency, quality, and compliance. It empowers workers with a tool that is as simple as a point-and-click, yet it feeds a sophisticated ERP engine that can optimize schedules, reduce waste, and ensure regulatory adherence. The next time you hear that familiar beep on a factory floor, remember that it is not just a noise; it is the sound of a digital transformation happening in real time, one scan at a time. | 
| For managers considering an upgrade to their production tracking, the evidence is clear. Code 128 with Infor M3 is not a legacy technology. It is a proven, scalable, and cost-effective solution that has delivered measurable results in some of the most demanding industrial environments across the United States. Whether you make medical screws, truck parts, canned corn, or missile guidance systems, this combination can provide the visibility and control you need to compete in today's fast-paced global market. Start with a pilot, train your people, design clear labels, and watch your data accuracy and operational performance soar. | END OF CHAPTER 48. |
|
cs@easiersoft.com