Articles

Talking with technology providers can sometimes feel like hitting a brick wall. This is due to the heavy use of abbreviations and IT jargon, which can be hard to grasp if you’re not familiar with the industry. That’s why we’ve put together a list of key concepts to help you become an equal partner in discussions at your next meeting with an IT company. How to Approach an ERP Implementation? An ERP implementation might initially seem like an investment primarily based on buying and installing software. Appearances can be deceiving. In reality, it is a complex business project, much like building a house. It starts with architectural plans, moves through technology selection, all the way to installation testing and the final move-in. According to data from this year’s “Digital Manager” report (publication for Polish readers), an ERP system implementation takes an average of 9 months. However, it’s worth keeping in mind that this process can take longer depending on the scale of the organization and the functionalities the system needs to have. That is exactly why this process requires a high level of attention and engagement. A glossary of basic terms that you will undoubtedly hear from your implementers can help you navigate it. ERP Glossary Pre-Implementation Analysis The absolute foundation of any implementation — whether it’s an ERP, WMS, CRM, or any other system. It should usually be the first, comprehensive stage of the project. This is when the IT firm deeply analyzes your organization’s business processes and needs before writing a single line of code. As-Is / To-Be A description of business processes. “As-Is” presents the current state, which is often chaotic with clear room for improvement. “To-Be,” on the other hand, illustrates the beautiful vision of what your company’s environment will look like after the system is implemented. Best Practices Market standards. Instead of reinventing the wheel, the provider suggests ready-made processes that have been proven in your industry, drawing on previous projects and the experiences of other clients. Bug An error or flaw in the software that prevents or hinders its operation. It can be caught during testing or (which can be stressful) shortly after the system goes live. Cloud (SaaS) One of the system variants where the provider hosts the software on their own servers. You gain access to it from anywhere and on any device. The SaaS (Software as a Service) model usually involves recurring subscription fees. Customization In other words, “tailor-making.” These are any modifications and changes to the system’s code that allow the software to be adapted to your unique and highly specific processes. GAPs Gap analysis, during which implementers look for differences between what the system offers in its standard version and your actual needs. This results in a corrective plan with specific steps and a strategy to bridge those gaps. Go-Live Day zero. The moment the system is officially launched and you start working on the “living organism.” Usually, on this historic day for the company, the provider acts as your faithful companion, remaining present in the office and keeping a finger on the pulse alongside you. Integration Building bridges between the new system and other software you already use. This includes e-commerce platforms, courier systems, or accounting software. Key User The implementer’s right hand. This is an employee in your company who knows a given department best and helps implement the ERP system. Right after the rollout, they become the first line of support for other employees. Data Migration One of the most important stages of the project. It’s a rather difficult process akin to moving houses. It involves transferring your historical data (from Excel spreadsheets or other programs) into the new system. Module One of the “building blocks” that makes up the entire ERP system. Although it functions independently of other components, it remains continuously integrated through shared, high-quality data. Each module supports a specific company department, e.g., Accounting, Warehouse (WMS), or Sales. Workaround A temporary trick. A clever, non-standard solution to a software problem that allows employees to keep working until developers prepare a final system patch. On-premise The classic approach to ERP implementation. The system is physically installed and maintained on your company’s own servers and local IT infrastructure. This gives the organization full control over configuration and data. However, it also comes with greater responsibility for server maintenance, data backups, and updates. Out-of-the-box (Standard) Ready-made system features you can use right away, without the need to write additional (and often expensive) custom code. This is a proven, secure solution that allows for a relatively quick implementation. Roadmap A detailed plan of the implementation project. It defines key stages, priorities, and specific deadlines for building and launching subsequent elements of the system. Scalability The flexibility that should be a hallmark of any modern ERP. It means the system is designed to grow alongside your enterprise. It’s a promise that the ERP won’t “clog up” when your company hires 100 new people and doubles its sales. SLA (Service Level Agreement) A service contract that clarifies the rules and parameters for services provided by the implementation vendor. It specifies things like guaranteed software uptime, repair procedures, and potential penalties for failing to meet conditions. Test Environment The system’s “sandbox.” A copy of the software where you can freely click around, learn, and test business scenarios without the fear of messing up real data. UAT (User Acceptance Testing) The last rehearsal before going live. The moment when your Key Users verify whether the system is working according to the original assumptions.

Summer heat can take its toll, as we have recently experienced firsthand. But what about people working physically in a production hall where machines can heat up to over a thousand degrees Celsius? One of the largest iron foundries in Europe – Vald. Birn – operates in such conditions. Vald. Birn is a Danish company with a century-old tradition; its origins date back to 1893. Currently, the enterprise employs 1,000 workers across four factories, producing up to 3,000 different assortment items in the field of metal castings. Their clients include key automotive brands such as Volvo and Mercedes. The metal products themselves – often critical from a safety point of view – must absolutely meet rigorous quality requirements. In such a demanding and (especially during the summer) extreme environment, there is no room for errors. That is why the digitalization of production turned out to be crucial. Replacing Binders with an IT System For many years, production management at Vald. Birn relied on sheets of paper. Leif Jensen, the company’s Financial Director, admits that “sticky notes and kilometers of binders” piled up everywhere on the desks. This significantly slowed down the documentation process and also caused limitations in data access. Furthermore, the company made the decision to completely overhaul its ERP system. However, it turned out that the previous program was too much of a challenge for the operators working directly on the foundry floor, who were not accustomed to handling complex IT interfaces. Therefore, they needed something more intuitive to use. An MES System Resistant to 1500 Degrees To solve this problem, in parallel with the implementation of the main ERP system, the company launched the Operator MES software. Currently, it acts as an agile extension of the Infor M3 business system in a harsh production environment. Block Quote The implementation itself was a massive logistical undertaking. Inside the foundry, among crucibles heated to 1500°C and heavy machinery, a staggering 170 terminals were successfully deployed. The analysis department, located directly on the production hall, became the central point to which samples flow continuously via a special pneumatic tube system. In the laboratory, the composition of 20 different alloys is verified (including the content of elements such as titanium, lead, copper, and zinc). All results of these measurements immediately go to the Operator Platform, where they are automatically linked to specific customer orders. How to Achieve a Defect Rate Below 2% The management of Vald. Birn considers the implementation of the Operator system a “great success from day one”. The project brought results that permanently revolutionized the daily functioning of the foundry. Among the greatest benefits the company noticed were: Paperless approach – the paper documentation system was completely eliminated. Instead, the registration of orders, processes, and quality measurements was automated. Full Traceability – by ensuring strict quality control, the defect rate (scrap rate) was maintained at a level below 2%. Error identification – this process was significantly simplified and accelerated, facilitating an immediate reaction to irregularities. Audits – the company reached a completely new level of process documentation. This resulted in an official commendation from the Bureau Veritas auditors during certification. Intuitiveness That Builds Data Discipline Importantly, the success of the project was determined not only by the technology itself, but by its reception by the employees – including those who were not previously used to IT solutions. Vald. Birn operators received a precisely personalized interface. Only data and registration options strictly corresponding to their current tasks appear on their screens. The system gained tremendous appreciation, and today the employees themselves actively submit requests for new improvements and shortcuts. They understood how important correct documentation is, which translated into tremendous discipline in entering information into the Operator Platform. This is also proven by the implementations carried out in other plants of the group, including Kockums. Block Quote Thanks to the combination of advanced MES technology with intuitive operation, Vald. Birn proves that full quality control is possible even in the hottest industrial environment.

Holidays are approaching, which for many management boards mean a long-awaited rest. However, cybercriminals and hardware failures do not take vacations. What should you remember before setting your “Out of office” status? The holiday season is a time when companies are most vulnerable to data leaks or loss. This is due to both complex cyberattacks and human error. Sometimes a single click on a fake message is enough. That is why this article was created. Although most of us know security methods from IT training and lectures, it is worth periodically reminding ourselves of them. Especially since in the pre-holiday rush, we might miss a few key aspects. Manage Access, But Be Careful Who You Give the “Digital Keys” To Who has access to key information when the main manager is basking on the beach? Delegating permissions is an almost mandatory process before any vacation. Although we go through this regularly, we often repeat the same mistakes. We lock cabinets, but we pass passwords to third parties on sticky notes. Instead, you should carry out this process directly in the system you work on. Remember the possibility of granting temporary access — indicating a specific date when a given user will lose permissions to a specific module or login details. Check The Data Backup in the ERP System A backup is a key pillar of any company’s operations. Without it, the loss of documents or passwords can halt the team’s work for hours. Although creating backups should be an everyday routine, rather than an occasional activity, it is worth checking its effectiveness before your vacation. Make sure that the data backup is performed correctly and that it can be restored without any problems. In the case of an ERP system, the backup should cover databases, contractor files, and any documents related to sales and warehouse processes. You should also check whether the procedure for restoring this information in the software runs flawlessly. Update Your Software and Devices Before leaving, make sure you have updated your operating system (Windows or macOS). Do the same for all the programs you use in your daily work (e.g., ERP, CRM). Why is this so important? Even the best programmers can leave some vulnerabilities in the code that cybercriminals can easily exploit. The only reliable protection in this situation is to install updates on an ongoing basis. What is extremely important — if your ERP system runs in a browser, simply updating the software is not enough. During trips, absolutely avoid using open, public Wi-Fi networks (e.g., at airports, shopping malls, or hotels). They can be constantly monitored by hackers. Instead, use a company VPN connection. It encrypts all network traffic, creating a secure, closed tunnel for your data. By the way, if you have not yet implemented two-step verification for your account, make up for it before handing over permissions to your deputy. This additional layer of protection will ensure that even in the event of a password leak, an unauthorized person will not log into company resources. Educate and Secure Your Coworkers Against Phishing It is worth alerting the employees who stay in the office to potential threats lurking in their email inboxes. An increasingly popular attack method is spear phishing. It involves sending personalized emails that look deceptively like messages from a supervisor or a client. You should remain highly vigilant and verify every time whether the sender’s address is reliable and actually comes from a known domain. Use the Audit Trail After Returning You are leaving, but the company keeps working — contracts are negotiated, invoices are paid, and inventory levels are updated. To make your post-holiday return to reality easier, use the audit trail available in your ERP software. An audit trail is a digital record that acts like a “black box.” The system automatically registers every operation in the database. Thanks to this, you gain full insight into who made edits and when, as well as what exactly was modified. You don’t have to ask your coworkers for details — you just need the full, objective timeline right in front of you.

In the Polish Business Central landscape, compliance with KSeF is only part of the story. The real challenge for many customers begins after the invoice is received: how to process it efficiently within existing purchase invoice workflows.  For organizations using both Localization for Poland and Continia Document Capture, this has typically meant dealing with a gap between compliance and operational automation. While Localization for Poland ensures correct retrieval and handling of KSeF invoices, Continia provides advanced tools for processing and posting purchase invoices. Connecting these two areas in a clean, repeatable and efficient way has not been straightforward before.  Companial addresses this with a dedicated integration application that links Localization for Poland with Continia Document Capture, enabling automatic transfer of incoming KSeF invoices via the Continia Delivery Network.  This creates a practical bridge between compliance and automation – without introducing custom integrations that are difficult to maintain over time.  From compliance to process continuity  KSeF defines how invoices are exchanged and structured, but it does not define how organizations handle them internally. Each customer has their own processes, approval flows and operational requirements.  Localization for Poland covers the compliance layer – including KSeF communication and data structures – ensuring that invoices are correctly retrieved and stored as e‑documents. However, this is only the starting point of the purchase invoice lifecycle.  The integration with Continia extends this standard flow by ensuring that once a document is processed in Localization for Poland, it can seamlessly continue into the Continia Document Capture process.  How the integration works  The integration focuses on incoming purchase invoices retrieved from KSeF and follows a structured, automated flow:  Localization for Poland retrieves purchase invoices from KSeF into Business Central.  Each document is created as an e-document with the related XML file imported from KSeF attached to it.  The XML file is then automatically forwarded to the Continia Delivery Network.  The invoice becomes available in Continia Inbound E-Documents.  Further processing – including recognition, matching and posting – is handled within Continia Document Capture, based on the relevant Continia configuration.  The transfer is triggered automatically once the integration is enabled, assuming the required setup is in place on both sides.  A standard approach instead of custom integration  A recurring challenge in KSeF-related implementations is the need to connect compliance processes with customer-specific workflows. This could lead to custom integrations that increase complexity and make future updates harder to manage.  This application follows a different approach.  It does not replace the standard KSeF process delivered by Localization for Poland, nor does it modify Continia functionality. Instead, it acts as a dedicated, standard bridge between the two, allowing both solutions to remain aligned with their respective update cycles.  If the integration is disabled, the standard KSeF flow in Localization for Poland continues unchanged.  What this means in practice  For customers, the key benefit is process continuity:  KSeF invoices are automatically transferred into the Continia processing flow,  no separate handover or manual intervention is required once the integration and required Continia setup are in place,  existing Continia-based automation can continue to be used,  the overall purchase invoice process remains consistent and scalable.  For partners, this simplifies solution design. Instead of building and maintaining custom “connectors”, they can rely on a predefined integration scenario that aligns with standard Business Central architecture.  Observability and control  Automation does not remove the need for visibility.  The integration provides a dedicated setup and logging mechanism, allowing users to:  enable or disable the transfer process,  review document transfer history,  monitor success and failure statuses,  manage retention of upload logs.  This ensures that the transfer process is not only automated, but also traceable and easier to support.  Where this fits in customer scenarios  The integration is particularly relevant in environments where:  KSeF is already used or being implemented in Business Central,  Continia Document Capture is part of the purchase invoice process,  customers want to avoid process-specific integrations (processes may change in time),  long-term maintainability is a priority.  In such cases, the application provides a clean transition from regulatory compliance to operational processing.  Closing the gap between systems  As KSeF adoption became mandatory, more organizations are moving toward fully digital invoice processes. At the same time, they expect these processes to remain efficient and integrated.  By connecting Localization for Poland with Continia Document Capture, this application addresses a specific but common challenge: how to move KSeF invoices into an existing automation workflow without adding unnecessary complexity.  It reflects a broader shift in how Localization for Poland supports customers – from isolated compliance handling toward integrated, end-to-end process design.  Availability  The application is available on Microsoft Marketplace as Localization for Poland – Continia Integration. For organizations already using both Localization for Poland and Continia Document Capture, it provides a ready and maintainable way to connect KSeF invoice retrieval with purchase invoice automation, while keeping each solution responsible for its own part of the process. 

“If you can’t measure it, you can’t improve it.” It is hard to disagree with the words of the CEO of one of the factories we have worked with. Without precise data regarding the time and money spent on production downtime, it is difficult to maintain control over the performance of your machinery park. Moreover, simply having an ERP system will not solve the problem if the production floor lacks MES-class tools. True control over production begins with properly defining downtime categories. It is also necessary to distinguish between key performance indicators – OEE and TEEP. OEE and TEEP Indicators – What Do They Measure and How Do They Differ? Understanding the current equipment effectiveness at the level of a production shift requires the use of appropriate indicators. In the case of the Operator Platform, the Machine Status Monitoring module allows for an in-depth analysis using two key measures: OEE (Overall Equipment Effectiveness) – This indicator is based exclusively on the scheduled production time. It shows the utilization of a machine during the time it was actually scheduled to run. OEE consists of three components: availability, performance, and quality. If a machine runs for one shift (8 hours) and achieves ideal parameters during this time, its OEE will be 100%. Thus, the indicator allows not only for the optimization of production but also for the identification of losses during the shift. TEEP (Total Effective Equipment Performance) – A measure that takes into account the total calendar time – 24 hours a day, 7 days a week, 365 days a year. Therefore, it shows the maximum potential of the factory, taking into account so-called planned losses (e.g., holiday breaks). Because of this, a machine that runs for one 8-hour shift a day will have a TEEP of only 33%. This is due to the fact that it is turned off for the remaining 16 hours. Why is this so important? OEE shows where we are losing money due to breakdowns, changeovers, and micro-stops. TEEP, on the other hand, reveals the hidden capacity of the factory. It often proves that instead of spending millions on new production lines, it is enough to invest in an additional shift or optimize planning in the ERP system. How to Properly Categorize Downtime? Before we start analyzing the smallest micro-stops, the main groups of line stoppages must be properly defined. Implementing a system like Operator MES forces an organization to structure its losses. The foundation is a clear division into planned and unplanned downtime. Planned downtime includes machine changeovers, scheduled maintenance, or employees’ breakfast breaks. Unplanned downtime, on the other hand, includes mechanical failures, speed losses, and shortages of production materials. Thanks to the Operator Datalogger module, connected to terminals on the shop floors, the system gains full context: Cause tree – Downtimes are categorized hierarchically, which allows for the analysis of the sources and frequencies of individual events. Context from the operator – Using a terminal, the operator manually assigns a detailed cause code. They can also add notes, which may concern, for example, the machine operating at a reduced speed. The truth about changeovers – The system precisely separates actual production time from machine setup time. This is often the largest area of hidden losses in manufacturing plants. A Step into the Future with AI Once manufacturing plants master the basics – defining downtimes and starting to measure OEE and TEEP – they can reach for the most advanced tools. The Operator OEE solution, integrated with the Manufacturing Intelligence platform, offers support at the level of artificial intelligence. Machine learning algorithms provide optimization recommendations based on historical data and performance patterns. The ACIP (Automated Continuous Improvement Process) mechanism uses AI to predict potential quality problems and anomalies in machine operation. Are you looking for a technology partner who can help with the proper implementation of an MES system and a precise downtime grid? We encourage you to contact us and schedule a software demo.

This employee will perform all repetitive tasks for you and, at lightning speed, without any breaks, finalize the concept as well as the initial stages of a technological project. Sounds familiar? Using AI has become a habit for entrepreneurs — from popular conversational assistants (ChatGPT, Gemini) to advanced agents built into their supported ERP, WMS, CRM, and other systems. According to the latest No Fluff Jobs report, “AI in the IT Job Market,” as many as 68% of IT professionals use generative solutions every single day. At the same time, the role of artificial intelligence has long surpassed passive advising in copywriting, content marketing, or basic IT. For several months now, AI has been becoming an active agent capable of performing tasks on a computer. Anthropic remains a pioneer in this area, developing its Claude model to achieve the greatest possible autonomy. Claude Can Control Your Computer Claude is an autonomous AI agent that can step outside the browser window, reach for the mouse and keyboard, and actually make changes in your separate applications. Using a feature called “computer use”, Claude views a screenshot of the computer and interprets it. Then the magic happens: opening applications, clicking through various functions, and executing commands. Moreover, API integration is not even necessary, which provides a massive advantage when working with accounting systems or official government portals. This functionality can be utilized in programming. Claude Code then becomes an advanced “pair programming” partner, helping, among other things, with unit code creation and refactoring. Thus, it can significantly accelerate programming right from the concept stage. It almost instantly translates the client’s general business requirements into a database structure and the final technological stack. Opportunity or Threat? Let’s return for a moment to the No Fluff Jobs report. Respondents admitted that despite the enormous potential and dynamic development of artificial intelligence, they genuinely fear for their job security. Furthermore, as many as 40 percent of Polish IT specialists declare a lack of trust in AI technology. Among the main concerns hindering the complete handover of control to artificial intelligence is the risk of errors in generated code, which was pointed out by as many as 60 percent of respondents. Moreover, doubts regarding the security of company data still persist. Some experts continue to highlight the risk of leaks due to the unpredictable nature of LLM models. On the other hand, for the SME sector, models like Claude are a true financial revolution. For the price of a monthly subscription (starting at $20, depending on the selected version), small organizations can secure automation capabilities at least on par with a junior-level position. Will Claude Push The Programmer Out From Behind The Desk? Claude’s functionalities, especially in “computer use” mode, may cause some employees to feel replaced to some extent. However, the reality is slightly more optimistic. Claude might be able to create a simple recruitment application. Yet, it will not lead the implementation of a massive, deeply integrated WMS system. For that, human hands are still needed. Claude has probably already settled onto the desks of many specialists, but it has become more of a desk-mate than a permanent replacement. Companies still need experts who are able to control the code and apply corrections. Therefore, knowing Python or JavaScript — even at a basic level — remains immensely valuable on a CV. Thanks to this, a specialist no longer blindly copies code but can additionally improve it. One key thing is changing — employees cannot pretend that AI isn’t around them. They, too, should learn to supervise LLM models and manage agents. It is worth keeping in mind expert recommendations and the EU’s AI Act. Implementing artificial intelligence should begin with automating the lowest-risk processes. This will allow for discovering the strengths and weaknesses of the solution while the model operates within a designated permission “sandbox.” Source: https://nofluffjobs.com/insights/ai-na-rynku-pracy/, businessinsider.com.pl

Compliance is the floor. Partner work picks up from there.  One compliance standard, no two customer processes  Every partner working with Microsoft Dynamics 365 Business Central in Poland runs into the same tension: strict regulatory compliance on one side, highly individual customer processes on the other. Localization for Poland covers the core compliance areas, including KSeF, VAT-EU and SAFT/JPK, in line with current Polish regulatory requirements and official reporting structures. But regulations define what has to be reported, not how a company runs the process around it, and no two customers run that process the same way. One runs split payments across two currencies. Another handles purchase corrections in ways that do not fit a universal default approach. That gap between compliance and operational reality is where most implementation friction lives.  For a long time, closing that gap meant choosing between two bad options: bend the customer’s process to fit the standard, or fork the localization and lose the ability to update cleanly. Neither holds up over a few release cycles. Localization for Poland provides the standard compliance processes required for Polish regulations, while also exposing extension points for customer-specific scenarios that go beyond the standard scope. Integration events are how that works in practice: customer-specific logic can be implemented through extensions, helping partners avoid modifications to the standard localization and making future updates easier to manage.  Extending correction handling for purchase credit memos  Take a concrete case: purchase credit memos that carry before-and-after correction lines, common in line-level price or quantity corrections. KSeF provides structured data for these documents, but it does not define a single required way to reconstruct them in Business Central. For complex purchase correction scenarios, including documents with before-and-after line structures, the standard localization prioritizes safe and consistent import behavior. Where customer-specific handling is required, partners can use available extension points in purchase document creation and data mapping logic instead of modifying the standard solution.  Reusing the invoice preview instead of rebuilding it  A smaller example, but one that comes up constantly in multi-system environments: invoice visualization. Localization for Poland already provides invoice preview capabilities inside Business Central, including preview based on KSeF data and XSLT-based rendering. In customer-specific projects, partners can build on these existing preview capabilities instead of recreating the entire presentation layer from scratch. That helps keep document presentation consistent across systems without duplicating functionality that already exists.  VAT-EU and VIES: where to check before scoping  Both examples point to the same shift. Localization for Poland handles KSeF schemas and communication with the official system, so partners do not have to rebuild that layer themselves, while partner extensions are meant to complement the standard scope where customer-specific process logic is needed. The same logic applies to VAT-EU and VIES qualification, where partners may need to adjust how transactions are classified or apply customer-specific rules. Depending on the scenario, partners should verify early whether the required VAT-EU / VIES functionality and related extension options are available in the relevant Localization for Poland scope, as this can affect solution design and licensing.  Where this leaves partners  None of this requires forking anything or maintaining a parallel version of the localization. It requires knowing which extension points exist and where to use them. For partners building out their Polish practice, that is increasingly the more useful question: not whether the standard covers every scenario, but where the right hook is to extend it.  Curious which extension points fit a specific customer scenario? Worth a conversation. 

The occurrence of defective items in production is an everyday reality for every factory. The key to maintaining profitability is not only preventing errors, but also the ability to properly manage them when they do occur. This process is supported by modern MES (Manufacturing Execution System) class systems, which enable advanced defect handling. Thanks to this, operators can classify and manage non-compliant products without interrupting ongoing production. Precise Classification of Defective Products Traditional systems often force employees to simply mark damaged parts as “defects”. This, however, blurs the picture of what is actually happening on the production line. This approach is prevented by Production Execution in the Operator platform. The Production Execution module is an MES terminal that becomes a communication channel between the production hall and the system. In addition to comprehensive production reporting capabilities, the terminal enables advanced waste reporting (so-called outsort management). It supports the disposal process while simultaneously allowing for the introduction of all corrections, performing repairs, and handling so-called re-work products. The result? Operators gain the ability to accurately determine the causes of errors. Because of this, subsequent quality analysis becomes a solid foundation for minimizing material losses. 5 Paths for Dealing with a Defective Product Managing defects on the fly requires a flexible approach. The Operator system offers five main classification paths for units that require additional intervention: Direct Repair – a feature that enables direct repair of a defective part without interrupting ongoing production. The operator can repair the product on the spot and immediately return it for further processing. Repair – involves repair actions at the production workstation, but they are performed at a later time. This can occur, for example, after the completion of the current production run. Rework – otherwise known as reworking defective goods. This allows you to modify products and give them a new material code or create entirely new products. Scrap – the final classification of a product as waste that is unsuitable for further processing or repair. By-products – these are elements or semi-finished products created during the manufacturing of the main product. Parts classified this way can be effectively utilized in future production processes. Defects on the Fly – How to React Quickly? When we free operators from the necessity of working at stationary terminals, quality management becomes much faster. The Operator Mobile App enables the registration and classification of production waste directly at the workstation. In turn, the Quality Control module guarantees immediate quality monitoring at all stages of production. Mobile solutions also facilitate access to data on quarantined products. Thanks to this, it is possible to report test results and streamline their release process. Why Is This So Important for the OEE Indicator? Entering the causes of rejections and errors in real-time provides invaluable information for the entire factory. It allows for a comprehensive analysis of production quality on an hourly or shift basis. Furthermore, the precise identification of defective batches will allow for targeted product recalls and cost reduction. Treating quality defects as an inherent element of the process and implementing tools to manage them on the fly is a huge step towards Industry 4.0. Instead of stopping the entire line, employees can act in a planned manner. In the future, the data collected in the MES system will allow for the elimination of bottlenecks in the area of quality. Do you want to check how such a solution will work in your factory? If you are in the process of looking for a system to optimize production, we invite you to contact us and schedule a demo.

Large online marketplaces such as Amazon or eBay are hotspots for online retail. These platforms play a key role in e-commerce. Here you will find what is often searched for in vain in traditional brick-and-mortar retail. On the other hand, for many trading companies, these marketplaces are a valuable addition to their existing sales channels. Can online platforms also be integrated directly into an ERP system? Yes, as long as the following points are taken into account. The Effective Multichannel Principle A common feature of various online marketplaces is the ability for sellers to quickly and professionally achieve a broader reach or target a larger number of potential customers. That is why many successful providers use this opportunity to complement their existing sales channels. Brick-and-mortar points of sale, their own online store, or other sales channels are supplemented by participation in e-commerce platforms. Appropriate concepts must take into account the specifics of individual channels and guarantee that the online marketplace will not take away the primacy of other sales channels. But there is one more obstacle to overcome: the plate-spinning problem. The Annoying Juggling Balls Problem You probably know circus performers who deftly juggle many balls or plates at the same time. This requires the utmost concentration and skill. If you want to master this feat, you have to focus on it completely. This phenomenon also occurs in a similar form in multi-channel distribution concepts. Known as the “plate-spinning problem”, an online store, an online marketplace, etc. must be kept in motion constantly and, above all, evenly. If one channel is neglected, turnover drops. In practice, this means that all channels must be fed simultaneously with the same data (e.g. product descriptions, prices, inventory levels, etc.). The fact that this data is also interdependent further complicates its handling across different systems. The Ideal Integration Concept If juggling is too burdensome for you, you can resort to a simplified version. Instead of handling individual plates, a central system is used to coordinate all plates or channels. ERP systems are predestined for this. They connect all business areas via a unified database. However, today’s multi-channel requirements set even higher demands. Alongside internal applications, an e-commerce connection in the form of an online marketplace and an online store is gaining in importance. Those who strive for perfect integration of their business processes and sales channels should already pay attention to the integration of all online and offline processes when evaluating a suitable ERP system. A seamless connection ensures a smooth exchange of data even across company boundaries. A virtuous process layout In order to be able to sell via an online platform, you naturally need appropriate and, above all, up-to-date article data. This is usually already managed in the ERP system. Those who do not want to store data twice will look for a way to cover everything centrally using a single software. Therefore, an ERP system is needed with an integrated option to connect the online platform, online store, and ideally other areas such as pop-up stores, POS checkouts, etc. In this way, a virtual process layout can be designed that covers the following areas, especially in conjunction with an online platform: Central data storage and management (items, customers, orders, inventory, etc.) Providing the relevant data for the online marketplace and the online store Mapping and synchronizing order transactions Further processing of incoming orders in downstream processes (e.g. logistics, customer service, etc.) A Broader Way of Thinking About e-Commerce The platform economy is on a growth curve. Social networks and online search engines also sense big business in online shopping. Merchants can join in and make their presence felt with little effort. An online store remains important, but it is no longer the only sales channel in e-commerce. Even if the competition in the online market is fierce and margins are low, it is worth being there. However, the business will only be profitable if processing costs do not eat up the profits. A broader mindset regarding e-commerce is key to long-term success. Selling products is important, but through additional offers and services, up- and cross-selling activities, etc., the business can really be strengthened. Here again, e-Commerce and ERP integration come into play. Whether it is for a targeted approach to the customer, promotions, services, and much more.

Managing production without precise data is like building machines without a technical blueprint. At the heart of a modern ERP system lies the BOM (Bill of Materials). In this article, we will discuss what a BOM is and how it impacts production processes. You will learn how a properly constructed product structure integrates with IT systems, supporting process control and enterprise optimization. What is a BOM? A BOM (Bill of Materials) is a comprehensive and structured list of all parts, raw materials, subassemblies, and components necessary to manufacture a final product. However, it is not merely a “shopping list.” A professional manufacturing BOM contains precise technological data, including: Exact unit quantities needed for assembly, Technical specifications facilitating identification, Positioning of elements in individual phases of the technological process, Information regarding assigned suppliers for a given raw material. How does BOM affect production processes? The relationship between BOM and production is absolutely crucial for maintaining operational fluidity. A precisely defined and updated bill of materials affects comprehensive production management, enabling: Material Requirements Planning (MRP) – Allows calculating the quantities of necessary raw materials, making it possible to place orders with suppliers and control inventory levels. Quality Control – Preparing a precise list helps minimize errors resulting from the use of incorrect parts or materials. Costing (TKW – Technical Manufacturing Cost) – It forms the basis for calculating production costs, covering both used materials and incurred labor. Coordination of Activities – It is an information source for various company departments, such as purchasing, production, logistics, or quality control. BOM and ERP systems A simplified bill of materials can function in spreadsheets, but IT systems integration elevates the enterprise to a higher level. ERP class systems integrate production, logistics, and finance. Meanwhile, the BOM constitutes the core element of data flow in this puzzle. System-based structure management allows for: Process Automation – The ERP system uses the BOM to automate processes such as generating orders or production planning. Optimization – The ERP system enables the analysis of BOM data to reduce operational costs and significantly shorten manufacturing time. Decision Support – ERP software integrated with a BOM provides data necessary for making strategic decisions, e.g., regarding investments or product development. BOM management in a manufacturing company Implementing the solution is just the first step. Effective BOM management in production requires: Maintaining Up-to-Date Data – Updating the BOM with changes in projects, specifications, or suppliers is crucial for maintaining business continuity. Interdepartmental Communication – Exchanging knowledge among engineering, purchasing, and production guarantees the reliability and consistency of data and processes within the company. Information Centralization – Creating a single, easily accessible source of information about the BOM helps avoid data duplication and errors resulting from a lack of consistency. Establishing Responsibilities – Assigning responsibility for maintaining and updating the BOM allows for better control over management processes and data quality maintenance. Benefits of effective BOM management The successive implementation of a product structure in a digital environment translates into measurable key performance indicators (KPIs) for the plant: Cost Reduction – Precise material requirements planning allows for the optimization of purchasing and warehousing costs. Shortening Production Time – The BOM enables better organization of production processes, which leads to shorter order fulfillment times. Increasing Product Quality – The Bill of Materials serves as the foundation for quality control, translating into a higher quality of final products. Better Process Control and Monitoring – Integrating the BOM with an ERP system provides the ability to easily monitor and control processes.