<?xml version="1.0" encoding="UTF-8" ?><!-- generator=Zoho Sites --><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><atom:link href="https://www.gsdworks.com.au/case-studies/data-master-data/feed" rel="self" type="application/rss+xml"/><title>Growth System Design - Case Studies , Data &amp; Master Data</title><description>Growth System Design - Case Studies , Data &amp; Master Data</description><link>https://www.gsdworks.com.au/case-studies/data-master-data</link><lastBuildDate>Fri, 07 Aug 2026 22:09:10 +1000</lastBuildDate><generator>http://zoho.com/sites/</generator><item><title><![CDATA[Master data cleanup]]></title><link>https://www.gsdworks.com.au/case-studies/post/master-data-cleanup</link><description><![CDATA[<img align="left" hspace="5" src="https://www.gsdworks.com.au/ERP inputs to outputs hero.png"/>Stabilised ERP purchasing and planning by cleaning up master data (products, locations, vendors, BoMs) and introducing standards (naming conventions, mandatory fields). Assigned clear data owners to prevent relapse. Result: more reliable system signals and less downstream rework.]]></description><content:encoded><![CDATA[<div class="zpcontent-container blogpost-container "><div data-element-id="elm_VFtO4T9VRTiEh1OWd9UeRQ" data-element-type="section" class="zpsection "><style type="text/css"></style><div class="zpcontainer-fluid zpcontainer"><div data-element-id="elm_6ith8KEZSleadGKYWakANQ" data-element-type="row" class="zprow zprow-container zpalign-items- zpjustify-content- " data-equal-column=""><style type="text/css"></style><div data-element-id="elm_7-rsvcirRWajhFJ5sHxI5A" data-element-type="column" class="zpelem-col zpcol-12 zpcol-md-12 zpcol-sm-12 zpalign-self- "><style type="text/css"></style><div data-element-id="elm_nALsyntxRlmaae0-XH5JfA" data-element-type="heading" class="zpelement zpelem-heading "><style></style><h2
 class="zpheading zpheading-align-center zpheading-align-mobile-center zpheading-align-tablet-center " data-editor="true"><span>Master data cleanup to stabilise ERP (products, locations, vendors, BoMs)</span></h2></div>
<div data-element-id="elm_AlAL0Td9RpqZ9dRloEtagg" data-element-type="text" class="zpelement zpelem-text "><style></style><div class="zptext zptext-align-center zptext-align-mobile-center zptext-align-tablet-center " data-editor="true"><p style="text-align:left;"><strong>Client&nbsp;</strong></p><p></p><div><div><p style="text-align:left;">Manufacturing and warehousing businesses using ERP for purchasing and planning.&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><strong>The challenge&nbsp;</strong></p><p style="text-align:left;">Poor master data breaks purchasing and planning. When product records, locations, vendors, and BoMs are inconsistent, the ERP cannot produce reliable signals. Teams then revert to manual workarounds.&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><strong>What we did&nbsp;</strong></p><p style="text-align:left;">We stabilised ERP performance by cleaning up master data and introducing standards.&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><strong>Standards introduced:&nbsp;</strong></p><p style="text-align:left;">• Naming conventions&nbsp;</p><p style="text-align:left;">• Mandatory fields&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><strong>How we prevented relapse&nbsp;</strong></p><p style="text-align:left;">• Clear owners of information were assigned&nbsp;</p><p style="text-align:left;">• Ongoing responsibility to maintain data quality was made explicit, so master data did not become “everyone’s problem and no one’s job”&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><strong>Results&nbsp;</strong></p><p style="text-align:left;">• Purchasing and planning became more reliable because the system inputs were consistent&nbsp;</p><p style="text-align:left;">• Teams spent less time correcting errors downstream&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><strong>Why it matters&nbsp;</strong></p><p style="text-align:left;">Master data is not an admin task. It is operational infrastructure. When it is owned and maintained, the ERP becomes a tool for decision-making rather than a source of confusion.</p></div></div></div>
</div><div data-element-id="elm_Aro4JRUOtY3bBDIbKpyyOA" data-element-type="buttonicon" class="zpelement zpelem-buttonicon zscsutom-banner-btn "><style> [data-element-id="elm_Aro4JRUOtY3bBDIbKpyyOA"].zpelem-buttonicon{ border-radius:1px; } </style><div class="zpbutton-container zpbutton-align-center zpbutton-align-mobile-left zpbutton-align-tablet-left "><style type="text/css"></style><a class="zpbutton-wrapper zpbutton zpbutton-type-primary zpbutton-size-lg zpbutton-style-oval zpbutton-icon-align-right " href="javascript:;" title="Book a free intro call" title="Book a free intro call"><span class="zpbutton-icon "><svg viewBox="0 0 24 24" height="24" width="24" xmlns="http://www.w3.org/2000/svg"><path d="M10.5253 5.49475L10.5206 7.49475L15.0782 7.50541L5.47473 17.0896L6.88752 18.5052L16.5173 8.89479L16.5065 13.5088L18.5065 13.5134L18.5253 5.51345L10.5253 5.49475Z"></path></svg></span><span class="zpbutton-content">Let's Talk</span></a></div>
</div></div></div></div></div></div> ]]></content:encoded><pubDate>Sun, 12 Jul 2026 00:54:49 +0000</pubDate></item><item><title><![CDATA[Routing and work centres]]></title><link>https://www.gsdworks.com.au/case-studies/post/routing-and-work-centres</link><description><![CDATA[<img align="left" hspace="5" src="https://www.gsdworks.com.au/Capacity planning routing hero.png"/>Implemented realistic routing and work-centre data (setup/run times) using motion studies. Capacity plans reflected real constraints, reducing overtime and rescheduling. Work was split into linked high-skill and low-skill steps, easing bottlenecks and increasing output.]]></description><content:encoded><![CDATA[<div class="zpcontent-container blogpost-container "><div data-element-id="elm_fhJ2ZXhBTAapETW2SZ5hjQ" data-element-type="section" class="zpsection "><style type="text/css"></style><div class="zpcontainer-fluid zpcontainer"><div data-element-id="elm_MkDO1LsdRnG-PZGn2Q3S1Q" data-element-type="row" class="zprow zprow-container zpalign-items- zpjustify-content- " data-equal-column=""><style type="text/css"></style><div data-element-id="elm_tkzrKKjQRZKJHUqtR3FjKw" data-element-type="column" class="zpelem-col zpcol-12 zpcol-md-12 zpcol-sm-12 zpalign-self- "><style type="text/css"></style><div data-element-id="elm_lSpa8jy_RD-vvMEqhAOv3w" data-element-type="heading" class="zpelement zpelem-heading "><style></style><h2
 class="zpheading zpheading-align-center zpheading-align-mobile-center zpheading-align-tablet-center " data-editor="true"><span>Routing and work centre setup for realistic capacity planning</span></h2></div>
<div data-element-id="elm_n7I5j9RbT9GZ7tkJTP8lfA" data-element-type="text" class="zpelement zpelem-text "><style></style><div class="zptext zptext-align-center zptext-align-mobile-center zptext-align-tablet-center " data-editor="true"><p style="text-align:left;"><span><span style="font-weight:bold;">Client&nbsp;</span></span></p><p style="text-align:left;"><span><span>Manufacturing businesses that needed realistic capacity planning and better labour utilisation.&nbsp;</span></span></p><p style="text-align:left;"><span><span><br/></span></span></p><p style="text-align:left;"><strong>The challenge&nbsp;</strong></p><p style="text-align:left;"><span><span>When run times, setup times, and work centre capacity are not defined properly, schedules become optimistic and delivery promises become unreliable. Teams compensate with overtime and constant rescheduling.&nbsp;</span></span></p><p style="text-align:left;"><span><span><br/></span></span></p><p style="text-align:left;"><span><span style="font-weight:bold;">What we did&nbsp;</span></span></p><p style="text-align:left;"><span><span>We implemented routing and work centre data that reflected real work.&nbsp;</span></span></p><p style="text-align:left;"><span><span><br/></span></span></p><p style="text-align:left;"><strong>This included:&nbsp;</strong></p><p style="text-align:left;"><span><span>• Defining run times and setup times&nbsp;</span></span></p><p style="text-align:left;"><span><span>• Using motion studies to validate time assumptions What became visible Once routing data was realistic, it became clear that some tasks could be split into two linked activities:&nbsp;</span></span></p><p style="text-align:left;"><span><span>• A higher-skilled portion of the work&nbsp;</span></span></p><p style="text-align:left;"><span><span>• A lower-skilled portion of the work This maintained one-piece flow while allowing higher-skilled workers to focus their energy where it created the most value.&nbsp;</span></span></p><p style="text-align:left;"><span><span><br/></span></span></p><p style="text-align:left;"><span><span style="font-weight:bold;">Results&nbsp;</span></span></p><p style="text-align:left;"><span><span>• Higher output with less overtime</span></span></p><p style="text-align:left;"><span><span>&nbsp;• Reduced bottlenecks because labour allocation matched the true constraint&nbsp;</span></span></p><p style="text-align:left;"><span><span><br/></span></span></p><p style="text-align:left;"><strong>Why it matters&nbsp;</strong></p><p style="text-align:left;"><span><span>Capacity planning is only as good as the data behind it. When routing and work centre assumptions match reality, scheduling becomes a practical tool instead of a constant negotiation.&nbsp;</span></span></p></div>
</div><div data-element-id="elm_-vqMiMZ27N9C5bByBoVJCA" data-element-type="buttonicon" class="zpelement zpelem-buttonicon zscsutom-banner-btn "><style> [data-element-id="elm_-vqMiMZ27N9C5bByBoVJCA"].zpelem-buttonicon{ border-radius:1px; } </style><div class="zpbutton-container zpbutton-align-center zpbutton-align-mobile-left zpbutton-align-tablet-left "><style type="text/css"></style><a class="zpbutton-wrapper zpbutton zpbutton-type-primary zpbutton-size-lg zpbutton-style-oval zpbutton-icon-align-right " href="javascript:;" title="Book a free intro call" title="Book a free intro call"><span class="zpbutton-icon "><svg viewBox="0 0 24 24" height="24" width="24" xmlns="http://www.w3.org/2000/svg"><path d="M10.5253 5.49475L10.5206 7.49475L15.0782 7.50541L5.47473 17.0896L6.88752 18.5052L16.5173 8.89479L16.5065 13.5088L18.5065 13.5134L18.5253 5.51345L10.5253 5.49475Z"></path></svg></span><span class="zpbutton-content">Let's Talk</span></a></div>
</div></div></div></div></div></div> ]]></content:encoded><pubDate>Sun, 12 Jul 2026 00:32:42 +0000</pubDate></item><item><title><![CDATA[BoM cleanup in ERP]]></title><link>https://www.gsdworks.com.au/case-studies/post/bom-cleanup-in-erp</link><description><![CDATA[<img align="left" hspace="5" src="https://www.gsdworks.com.au/BoM cleanup ERP hero.png"/>Cleaned up ERP Bills of Materials and aligned them with clear, complete work instructions to stop production errors, rework, and costing drift. Introduced PLM-style control (ownership, sign-offs, approvals) so changes were governed, improving inventory accuracy and margin visibility.]]></description><content:encoded><![CDATA[<div class="zpcontent-container blogpost-container "><div data-element-id="elm_R41_phbTRdOS_qLI9ylFUg" data-element-type="section" class="zpsection "><style type="text/css"></style><div class="zpcontainer-fluid zpcontainer"><div data-element-id="elm_6fOC0kJTTlOFJPoW1sfjrw" data-element-type="row" class="zprow zprow-container zpalign-items- zpjustify-content- " data-equal-column=""><style type="text/css"></style><div data-element-id="elm_oQwSeFKuQcSv3rKQd5DYCQ" data-element-type="column" class="zpelem-col zpcol-12 zpcol-md-12 zpcol-sm-12 zpalign-self- "><style type="text/css"></style><div data-element-id="elm_l0_dmcRVRkiaiMySn8JoLA" data-element-type="heading" class="zpelement zpelem-heading "><style></style><h2
 class="zpheading zpheading-align-center zpheading-align-mobile-center zpheading-align-tablet-center " data-editor="true"><span><span>BoM cleanup in ERP to prevent production errors and improve costing&nbsp;</span></span></h2></div>
<div data-element-id="elm_yhGRQ8xGTUKOyqxRkUUuaQ" data-element-type="text" class="zpelement zpelem-text "><style></style><div class="zptext zptext-align-center zptext-align-mobile-center zptext-align-tablet-center " data-editor="true"><p style="text-align:left;"><strong>Client&nbsp;</strong></p><p style="text-align:left;">Manufacturing businesses using ERP systems to manage product data and production execution.&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><strong>The challenge&nbsp;</strong></p><p style="text-align:left;">Bills of Materials (BoMs) and work instructions often drift apart. For example, the BoM might specify one quantity or component, while the instruction on the floor specifies something different. When instructions are unclear or incomplete, teams compensate with workarounds.&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><span style="font-weight:bold;">That creates:&nbsp;</span></p><p style="text-align:left;">• Production errors and rework&nbsp;</p><p style="text-align:left;">• Inventory discrepancies that are difficult to explain&nbsp;</p><p style="text-align:left;">• Unreliable product costing What we did We cleaned up BoMs and aligned them with clear, complete production instructions.&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><strong>How we controlled changes&nbsp;</strong></p><p style="text-align:left;">We implemented a product lifecycle management approach:&nbsp;</p><p style="text-align:left;">• BoMs and instructions were maintained through product management, not informally on the floor&nbsp;</p><p style="text-align:left;">• Sign-offs and approvals were required from relevant parties before changes went live&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><strong>Results&nbsp;</strong></p><p style="text-align:left;">• Increased inventory accuracy&nbsp;</p><p style="text-align:left;">• Fewer questions and less time spent investigating discrepancies&nbsp;</p><p style="text-align:left;">• More accurate costing because consumption and structure were consistent&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><span style="font-weight:bold;">Why it matters&nbsp;</span></p><p style="text-align:left;"></p><p style="text-align:left;">BoM accuracy is foundational. When BoMs and instructions match the real process, everything downstream improves, including purchasing, planning, inventory, and margin visibility.&nbsp;</p></div>
</div><div data-element-id="elm_woZTYlvG-6uYbG8HfI-nQw" data-element-type="buttonicon" class="zpelement zpelem-buttonicon zscsutom-banner-btn "><style> [data-element-id="elm_woZTYlvG-6uYbG8HfI-nQw"].zpelem-buttonicon{ border-radius:1px; } </style><div class="zpbutton-container zpbutton-align-center zpbutton-align-mobile-left zpbutton-align-tablet-left "><style type="text/css"></style><a class="zpbutton-wrapper zpbutton zpbutton-type-primary zpbutton-size-lg zpbutton-style-oval zpbutton-icon-align-right " href="javascript:;" title="Book a free intro call" title="Book a free intro call"><span class="zpbutton-icon "><svg viewBox="0 0 24 24" height="24" width="24" xmlns="http://www.w3.org/2000/svg"><path d="M10.5253 5.49475L10.5206 7.49475L15.0782 7.50541L5.47473 17.0896L6.88752 18.5052L16.5173 8.89479L16.5065 13.5088L18.5065 13.5134L18.5253 5.51345L10.5253 5.49475Z"></path></svg></span><span class="zpbutton-content">Let's Talk</span></a></div>
</div></div></div></div></div></div> ]]></content:encoded><pubDate>Sun, 12 Jul 2026 00:24:40 +0000</pubDate></item><item><title><![CDATA[Reorder rules in ERP]]></title><link>https://www.gsdworks.com.au/case-studies/post/reorder-rules-in-erp</link><description><![CDATA[<img align="left" hspace="5" src="https://www.gsdworks.com.au/Replenishment timeline flow cover.png"/>We rebuilt ERP replenishment by fixing lead times and reorder rules so ordering became consistent and data-driven. Stockouts dropped, fill rates improved, and teams spent less time expediting and firefighting.]]></description><content:encoded><![CDATA[<div class="zpcontent-container blogpost-container "><div data-element-id="elm_8Jd9PsxKRNuorfz_36u2NQ" data-element-type="section" class="zpsection "><style type="text/css"></style><div class="zpcontainer-fluid zpcontainer"><div data-element-id="elm_caiRWZWVQHaAIr_8pg2sJA" data-element-type="row" class="zprow zprow-container zpalign-items- zpjustify-content- " data-equal-column=""><style type="text/css"></style><div data-element-id="elm_tfQNy6qjQx6SuH_pkRZWGA" data-element-type="column" class="zpelem-col zpcol-12 zpcol-md-12 zpcol-sm-12 zpalign-self- "><style type="text/css"></style><div data-element-id="elm_dS7lcoa1G3ma8JeRfWsNxw" data-element-type="heading" class="zpelement zpelem-heading "><style></style><h2
 class="zpheading zpheading-style-none zpheading-align-center zpheading-align-mobile-left zpheading-align-tablet-left " data-editor="true"><span>Reduced stockouts by fixing reorder rules and lead times in ERP</span></h2></div>
<div data-element-id="elm_cxY3fY4WSDmLItVUqxYd8g" data-element-type="text" class="zpelement zpelem-text "><style></style><div class="zptext zptext-align-center zptext-align-mobile-center zptext-align-tablet-center " data-editor="true"><p style="text-align:left;"><span style="font-weight:bold;">Client&nbsp;</span></p><p style="text-align:left;">Multiple businesses across chemical manufacturing, furniture, building supplies, and small retail.&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><strong>The challenge</strong>&nbsp;</p><p style="text-align:left;">These businesses had an ERP in place, but replenishment still behaved like a manual process. Stock decisions were often driven by gut feel, firefighting, or whoever noticed a problem first.&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;">That created predictable symptoms:&nbsp;</p><p style="text-align:left;">• Stockouts and backorders that disrupted customer service&nbsp;</p><p style="text-align:left;">• Expediting and urgent purchasing that increased cost and stress&nbsp;</p><p style="text-align:left;">• Low confidence in lead times and availability,&nbsp;which made planning unreliable&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><strong>What we did&nbsp;</strong></p><p style="text-align:left;">We rebuilt replenishment so the ERP functioned as a true inventory control system, not just a record-keeping database.&nbsp;</p><p style="text-align:left;">Depending on the environment, the work typically included:&nbsp;</p><p style="text-align:left;">• Correcting and standardising lead times so planning reflected reality&nbsp;</p><p style="text-align:left;">• Implementing reorder logic and replenishment rules that matched actual consumption&nbsp;</p><p style="text-align:left;">• Establishing clearer stocking targets so ordering decisions were consistent and repeatable&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><strong>How we approached it&nbsp;</strong></p><p style="text-align:left;">We focused on operational behaviours as much as system configuration. The goal was to change ordering habits so decisions were driven by data and agreed rules, rather than intuition.&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><span style="font-weight:bold;">That meant:&nbsp;</span></p><p style="text-align:left;">• Making replenishment signals visible and trustworthy&nbsp;</p><p style="text-align:left;">• Ensuring the rules were practical enough that teams would actually follow them&nbsp;</p><p style="text-align:left;">• Reducing reliance on a single person “keeping an eye on things”&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><strong>Results&nbsp;</strong></p><p style="text-align:left;">Across these engagements, the most meaningful outcome was improved serviceability.&nbsp;</p><p style="text-align:left;">• Fill rates improved because stock was available and ready to ship when customer orders were placed&nbsp;</p><p style="text-align:left;">• Teams spent less time reacting to shortages and more time executing planned work&nbsp;</p><p style="text-align:left;">• Replenishment became more consistent, which reduced avoidable urgency in purchasing and production&nbsp;</p><p style="text-align:left;"><br/></p><p style="text-align:left;"><strong>Why it matters&nbsp;</strong></p><p style="text-align:left;">Many small and mid-sized manufacturers and distributors already have an ERP. The difference between constant stockouts and stable fulfilment is usually not the software. It is whether replenishment rules, lead times, and day-to-day behaviours are aligned</p></div>
</div><div data-element-id="elm_Yr-ta6yvvXH958G037ILuw" data-element-type="buttonicon" class="zpelement zpelem-buttonicon zscsutom-banner-btn "><style> [data-element-id="elm_Yr-ta6yvvXH958G037ILuw"].zpelem-buttonicon{ border-radius:1px; } </style><div class="zpbutton-container zpbutton-align-center zpbutton-align-mobile-left zpbutton-align-tablet-left "><style type="text/css"></style><a class="zpbutton-wrapper zpbutton zpbutton-type-primary zpbutton-size-lg zpbutton-style-oval zpbutton-icon-align-right " href="javascript:;" title="Book a free intro call" title="Book a free intro call"><span class="zpbutton-icon "><svg viewBox="0 0 24 24" height="24" width="24" xmlns="http://www.w3.org/2000/svg"><path d="M10.5253 5.49475L10.5206 7.49475L15.0782 7.50541L5.47473 17.0896L6.88752 18.5052L16.5173 8.89479L16.5065 13.5088L18.5065 13.5134L18.5253 5.51345L10.5253 5.49475Z"></path></svg></span><span class="zpbutton-content">Let's Talk</span></a></div>
</div></div></div></div></div></div> ]]></content:encoded><pubDate>Sun, 05 Jul 2026 01:07:35 +0000</pubDate></item></channel></rss>