Introduction to Backflushing

Backflushing is an alternative method of allocating components or materials to manufacturing, whereby stock is deducted only after production has been completed.

Backflushing makes it easier to work with quantities that would otherwise be highly impractical to ‘pick’ for use on Works Orders, and is a particularly useful technique when:

    • Components are too small or numerous to be ‘counted out’ in a sensible timeframe. (e.g.: screws, nuts, bolts, other low-cost parts used in volume.)
    • When materials are divisible, liquid, molten, gaseous, in lengths, weights, or otherwise issued ‘approximately.’ (e.g.: paint, ingredients, chemicals etc.)
    • Where a ‘spare’ quantity needs to be returned to stock after manufacturing is finished. (e.g.: scrapings, leftovers, recycled material.)

In SQLWorks every component on a Bill of Material (BOM) has a default allocation method – either ‘Standard’, ‘Backflush’ or ‘Return’ which defines how stock of this item will be ‘used up’ in the Stock Ledger. These work as follows:

    • ‘Standard’ – This is the default, and is used for all items that need to be counted out in advance of production. Components will be removed from stock when the user clicks ‘Take’ on the Works Order, before production begins.
    • ‘Backflush’ – Components will only be removed from stock after the Works Order is built, and the user is then asked to specify how much has been used.
    • ‘Return’ – Similar to backflushing, however components will only be removed from stock after the Works Order is built, and the user is then asked to specify a ‘spare’ quantity that gets returned to stock.

By changing a component stock item to ‘Backflush’ on a BOM, nothing will be removed from stock at the ‘Take’ stage, instead being deducted only after that BOM has been ‘built’ on a Works Order. The user can then specify how much has (or hasn’t) been used.

This is significantly more practical for certain items – although production managers may need to initially estimate the stock quantity of a Backflush item that they expect to use on its BOM (e.g.: how much paint an item typically needs.)

The user can edit a component’s default type by right clicking on it in a BOM, and choosing ‘Change Component Type.’ Components set to Backflush will be marked with a small ‘B’ symbol in the BOM.

When ‘Taken’ within a Works Order, only Standard items will listed as being removed from stock, and Backflush items will always show a taken quantity of zero (with the user then prompted after the ‘build’ stage for the correct quantity used for Backflush, or quantity excess for Return.)

backflushing

For many manufacturers, drawing down stock ‘post-production’ in this way may be the only way to accurately update your usage of resources. Using backflushing is an efficient way of tracking manufacturing using more fluid components, and allows SQLWorks to keep your production precise.

SQLWorks Live on Microsoft Windows 11

SQLWorks Version 10 is officially live on both Microsoft Windows 11, with early tests suggesting a significant performance improvement.

Microsoft Windows 11 is the first major Windows release for six years, and introduces a raft of visual, technical and security updates to the world’s most widespread desktop operating system.

Our SQLWorks Software Development Team – which uses both Apple macOS and Microsoft Windows for development – works hard to ensure our software maintains the best possible lifespan and interoperability, without the need for companies to spend on paid version upgrades. This includes advance testing on preview build/upcoming operating systems via virtual machine, to ensure our customers won’t experience compatibility issues.

You can learn more about upgrading to Windows 11 here, including the require minimum specifications. Uptake across industry PCs is expected to be somewhat slower than for Windows 10, as many pre-2018 processors prior to the Spectre and Meltdown incidents won’t support the update – meaning that the adoption of Windows 11 will be driven predominantly by new devices.

SQLWorks is still fully operable on any 64-bit version of Windows 10, which itself remains fully supported by Microsoft until October 2025.

Video: Manufacturing Brilliance

 

[subscribe_to_unlock_form]

 

Managing Assets & Machinery

Asset Register


If a business harnesses important physical assets, keeping track of these over time quickly becomes essential.

Whether it’s your own machinery, or a piece of equipment you maintain for a client, attributing costs to these accurately is an key part of your business financial planning – and helps you make smarter decisions about future investment.

SQLWorks supports this process with a dedicated asset register – allowing the user to save a range of information (including make, model, warranty and more) for both in-house and client assets to aid day-to-day business operations. Asset Register can be found in the Stock Ledger, and helps the user build a centralised and definitive list that can be controlled with permissions groups, like any other SQLWorks Ledger.

For in-house assets, SQLWorks users can also link these assets to Purchase Orders – ensuring that asset’s data contains a detailed maintenance history that includes financials.

Helpfully, this also works across multiple Purchase Ledger suppliers, so that maintenance costs (such as repairs or replacement parts) remain accurate even if an asset’s service contract changes hands. This helps a company stay flexible, since accounting and contract periods may be much shorter than machinery lifecycles.

Assets may also be optionally enabled as a special tab in a customer’s Sales Ledger account – ensuring a service engineer can easily access known information about a client’s asset as a part of routine account maintenance. This might include location, serial numbering for identification, or notes on past repair work.

SQLWorks ensures business managers can properly document and maintain a full asset register – itself an asset to a well-informed team.

 

For expertise and software assistance, please contact our SQLWorks Team today

SQLWorks a Made Smarter UK Technology

Made Smarter Update:

Lineal’s SQLWorks Software is officially registered as a specialist UK digital technologies provider for manufacturing.

Made Smarter is a UK-Government backed initiative launched in 2017, following a nationwide review of the manufacturing sector – and includes a number of private and public sector organisations helping to modernise industry and drive adoption of productivity-boosting technology in the sector.

Recognised fields include a wide range of next-generation technologies for manufacturing such as robotics & process control, data and systems integration, mobile and wearable devices, sensor innovations, machine learning, additive manufacturing and augmented reality technology.

sqlworks on made smarter site

“We’re delighted to see SQLWorks listed among some of this country’s most advanced and cutting-edge technology solutions for manufacturing” said Lineal’s Managing Director Mike Matthews. “The Made Smarter review highlights adoption of modern technology as a keystone for industry in this country, and we want SQLWorks to underpin real advancement and strength in the industry.”

Businesses can read the original findings of the Made Smarter Review here, and learn more about Made Smarter UK here.

 

For Business Software expertise and support, please contact our team today.

Getting Started with Dispatch Planner

Dispatch Planner


Managing outbound goods often requires an overarching view of business operations ‘as-a-whole’ – looking across all sales accounts, orders and products. We’ve given users the power to do this via SQLWorks Dispatch Planner.

Dispatch Planner gives order managers and warehouse teams a comprehensive dashboard to maximise visibility and control over orders. Dispatch Planner is accessible within the Stock Ledger, and (by default) loads a comprehensive list of all outstanding customer sales Orders with key information about each order.

dispatch planner

Double clicking on an order allows a drill-down to the exact order, meaning shopfloor teams don’t need to access individual customer sales accounts to understand workloads and even check line-level detail.

Simple ‘traffic-light’ statuses indicate whether the required stock quantity is available for each order to be shipped in full. By selecting an order, dispatch managers can also view the same information for each order line of the order – with the same status indication based on free stock availability. Orders will only be considered ready to ship in full once every line on that order is available to ship.

When ready to ship, dispatches can be sent to dispatch and invoiced (and emailed automatically to the customer) in one smooth workflow, removing the outstanding order from the Dispatch Planner list.

dispatch planner

High volume companies may lengthen or shorten the time horizon of the viewed orders, or filter by warehouse. Where goods are not ‘Ready to Ship’, SQLWorks will make the user aware of why an order is delayed – for example, showing Purchasing Delays.

For companies that use Delivery/Dispatch Notes prior to invoice, the Dispatch Planner will also allow the generation of new delivery notes from here, list any valid delivery note numbers for each order for cross-referencing, and require the user to select an existing delivery note before invoicing a previous dispatch.

Dispatch Planner shows the real power of SQLWorks: as the ability to cross-reference stock control and ordering globally across the business allows you to manage operations quickly, efficiently, and with confidence.

 

You can find more detail about how to use Dispatch Planner here

Lineal join Omnis for Web Engineering Day

Members of Lineal’s Software Development Team were recently invited to join the Omnis Software Engineering Team for a special 2-day visit focusing on development work regarding web features within SQLWorks.

Software engineers from both companies focused the dedicated day on the implementation and deployment of Lineal’s recent online work including business-to-business (B2B) trade ordering portals and online user survey systems.

The SQLWorks Team at Lineal wanted to thank the staff at Omnis for being excellent hosts and helping to craft an extremely useful and informative visit.

Omnis Software recently celebrated 40 Years in the industry, having been founded in 1979 by Blyth Computers Ltd. Co-founder Paul Wright.

Omnis technology has underpinned Lineal’s SQLWorks Business Management Software (integrating accounting, stock control, CRM and manufacturing) since the early 1980s. Lineal’s Managing Director Mike Matthews is a part of the international Omnis Technical Committee, and Lineal staff regularly help coordinate and take part in EurOmnis, the international Omnis software developer conference.

 

For Software development advice and expertise today, please contact our team today.

Introduction to Stock Audit and Stock Taking

Stock Audit allows businesses to perform a comprehensive stock take, record variances, verify the results, report on valuation, and automatically adjust stock levels for accuracy.

Stock takes can be initiated, or continued, by clicking on ’Stock Audit’ under ‘Products’ in the Main SQLWorks Navigation Bar (1). To begin a new stock take simply click ‘Create New’ or load an unfinished stocktake via ‘Load Existing’. Each stock take is warehouse specific, and can be given a reference ID.

Users must choose whether the final results will ’Save Quantity’ (adjust the actual quantity to a fixed number established from the stock check) or ’Save Variance’ (adjust the actual quantity according to a variance from the theoretical quantity, incorporating quantity changes which may have taken place during the stock take.)

stock audit type

Clicking ‘Print Sheets’ generates a series of stock take forms, listing the stock items and locations under review, which can be printed and assigned to stock counters for counting. Printed stock take sheets include a notes field for stock counters to record additional information, but do not list the theoretical quantity, so as not to prejudice the accuracy of the stock take.

stock audit sheets

Once stock counters have returned their stock take sheets, stock controllers can enter counted values in the ‘Count’ column next to each item by entering the name of the counter in the ‘Counted By’ dropdown (2) at the top of the window. The ‘Variance’ Column automatically calculates the variance, and a note of the counter’s name is recorded in the ‘Count By’ column (3)

If required, stock controllers can print “check sheets” in order to have questionable variances verified by a second counter, and enter a revised quantity in the same field by using the ‘Checked By’ dropdown at the top of the window (2). The ‘Variance’ Column automatically calculates the variance, and a note of the checker’s name is recorded in the ‘Check By’ column (3). When printing check sheets you may enter a single product code or a csv of codes, each product including its current values for all bin locations are printed on their own page.

To review the records, clicking the ‘Print Variance’ button at the top of the window produces a report on the results of the stock take, grouping the variances on each item across all monitored locations, and calculating a monetary value for the overall positive or negative variance.

By clicking ‘Finish’, the results of either the ’Save Quantity’ or ’Save Variance’ stock take are applied to the SQLWorks Stock Ledger to bring the stock levels back into alignment with the stock take.*

 

For additional information on stock control, contact our team today.

 

 

*If the ‘Free Qty’ tickbox is ticked at the top of the theory column, the theoretical values for the stock audit are shown excluding any allocated quantity. SQLWorks will not accept a variance which adjusts the quantity of an item below the quantity of that item which is already Allocated to Sales Orders, and will instead adjust the Actual quantity as close to the recorded variance as allowed numerically.

stock free

Team SQLWorks at EurOmnis 2017

This year Lineal’s SQLWorks Team traveled to Arnhem, The Netherlands, for the 4-day European Omnis Developers Conference – EurOmnis 2017.

Conference workshops offer the opportunity for developers from more than a dozen countries to exhibit their latest work, seek advice from other programmers and share best practice. A primarily educational event, EurOmnis brings together the brightest and best to further develop software projects and draw on a wider pool of knowledge.

EurOmnis workshop

Members of the Omnis Executive Team also attended to discuss the very latest developments of the platform, explain new features (such as remote debugging technology working live from the developer console) and gather valuable feedback from the wider Omnis developer community.

Managing Director of Lineal Software Solutions, Mike Matthews explained: “Over the many years during which we’ve helped organise EurOmnis, both the software itself and the Omnis Developers Group (ODEV) have gone from strength the strength.”

omnis developers

“This year’s conference studied some exciting breakthroughs in web development, mobile/tablet-friendly user interfaces, internet-of-things (IOT) examples, future API technology, and much, much more.”

“SQLWorks is designed to be a highly flexible business management software, and we greatly value contributions from the extraordinarily diverse range of industry sectors, creative skills and technical knowledge represented each year at EurOmnis.”

In addition to coding, EurOmnis 2017 attendees had the chance to visit and dine at the Kasteel Doorwerth, a medieval chateaux dating from before the 13th Century, and literary home of the Beaulieu restaurant, where Erik Hazelhoff Roelfzema wrote Soldier of Orange.

See you next year!

 

Lineal are Omnis and business software development specialists – learn more here.

Euromnis venue

SQLWorks V8 – your thoughts?

With SQLWorks Version 8 debuting later this year, we’re gathering feedback on what our clients would like to see after the upcoming major upgrade.

Version 8 will be our opportunity to make considerable improvements to both the technical capabilities and user experience of SQLWorks.

Our team’s development priorities have been shaped by the feedback our users have given us in recent weeks and months – please let us know your thoughts below: