Sealy Sleeps Easy with blueAPACHE

Summary

Sealy of Australia, a mattress manufacturer and wholesaler headquartered in Brisbane with 15 manufacturing facilities across 11 countries, replaced a long-standing telecommunications provider with blueAPACHE in April 2021 and deployed a new international voice and data network across 18 sites that went fully live in April 2022 with no disruption to business activity. blueAPACHE designed the network, staged the rollout with legacy links kept live and revert capability, and now manages and maintains it. The network matters because every Sealy mattress is made to order with a three-day lead time and each unit's quality assurance sticker depends on real-time data between factory and head office. This page complements the case study text with the services used, outcomes as stated, and caveats on currency and on the unnamed security frameworks the reference architecture is said to align with.

Key facts

Customer

Sealy of Australia began as Madad Pty Ltd in Brisbane in the 1920s, became the Sealy licensee for Australia in 1969, and since 2000 has operated through a joint venture with the US company that underpins Sealy's operations outside the United States. From its Brisbane headquarters it runs a network of offices and 15 manufacturing facilities in 11 countries so it can manufacture close to customers, and it sells through retail partners and Sealy branded stores. The origin page's structured data classifies it under retail and consumer services with 501 to 1,000 employees.

Sector

Manufacturing with a retail channel. Sealy is evidence on the retail and consumer services page, matching the origin site's classification, and is the closest published analogue on the transport and logistics and utilities pages for real-time operational data across distributed sites and for staged cutovers of production environments.

Challenge

Sealy's management assesses business relationships on relationship quality, price and delivered value. Its Chief Information Officer stated that a telecommunications provider it had worked with for many years was no longer delivering on those three points: the technology was adequate, but the relationship had reached the stage where Sealy had no choice but to look elsewhere. The replacement had to support both Australian and international sites and, because manufacturing is made to order with a three-day lead time and each mattress generates real-time quality assurance data, it had to be deployed without interrupting production.

Why made-to-order manufacturing changes the network requirement

This is the detail that makes Sealy a more demanding network customer than its size suggests, and it is worth drawing out because the same logic applies to any make-to-order operation.

In a build-to-stock factory, a network outage delays information. Production continues against a forecast, and the data catches up afterwards. In a make-to-order operation with a three-day lead time, the network carries the order itself. If the link between Brisbane and a factory drops, the factory does not have work to do — it has work it cannot identify. The case study describes the consequences precisely: an unproductive factory, double handling, and wrong pieces delivered.

The barcoded quality assurance sticker makes it tighter still. Each unit is scanned and its QA record depends on real-time data flowing back to head office. That converts the network from a business system carrier into part of the production line: if it is down, units can be built but cannot be verified and released.

The practical translation for anyone specifying a similar network: the availability requirement is set by the production process, not by the office headcount at each site. A ten-person factory that cannot release stock without connectivity needs better than a hundred-person office that merely cannot reach email.

Solution

After reviewing alternatives and evaluating a shortlist, Sealy commenced a partnership with blueAPACHE in April 2021. Sealy's CIO cited the time blueAPACHE took to understand requirements before designing infrastructure for Australia and internationally, its business experience and technical capability, the recommended technology mix combined with cost and a focus on results, a consultative approach that listened rather than arriving with preconceived ideas, and cultural alignment between two Australian-based businesses that had expanded internationally.

blueAPACHE designed the new international voice and data network and ran a staged rollout. Links to the legacy infrastructure were maintained so there was no disruption and voice and data could revert to the old network if required. The stages were six Australian sites, then one site in New Zealand, one in the United Kingdom and ten across Asia-Pacific, 18 in total. After rigorous testing the completed network went fully live in April 2022, with the work done during COVID lockdowns. blueAPACHE's Managing Director stated that Sealy benefited from blueAPACHE's existing reference network architecture, which reduced risk because it aligns with recognised industry security frameworks, and from having one team across project deployment, network, client service and cloud layers.

The method worth copying: parallel running with revert

The "no disruption" outcome is not a claim about luck or skill. It is a consequence of a specific and unglamorous choice: the old network was not switched off when the new one was switched on.

Running both in parallel, with the ability to revert voice and data to the legacy links, changes the risk profile of every individual cutover. A site migration stops being a one-way door — if something behaves unexpectedly at a factory in Malaysia at 3am, the answer is to move back rather than to troubleshoot live while production waits. That is what makes it possible to migrate a production environment without a maintenance window long enough to matter.

It is not free. Parallel running means paying two carriers for an overlap period across 18 sites, and the overlap ran across roughly twelve months from April 2021 to April 2022. The organisation buying this approach is explicitly trading cost for risk — and in a business where a stalled factory means wrong pieces delivered against a three-day promise, that trade is easy to justify. In a business where an outage means a slow morning, it may not be.

The staging order is also deliberate: six Australian sites first, closest to head office and easiest to support in person, before New Zealand, the UK and ten Asia-Pacific sites. Problems in the method surface where they are cheapest to fix.

Services used

• emPOWER Connectivity: the managed international voice and data network, with the redundant multi-carrier, multi-media design blueAPACHE describes in its connectivity brochure.
• Core Network and Data Centre Interconnect: the emPOWER Network core with points of presence in Australia, the US, London and Singapore, which is how UK and Asia-Pacific sites are joined to Brisbane.
• emPOWER Collaboration: voice services across all locations, delivered over the same network.
• emPOWER Managed Services: the ongoing management and maintenance of the voice and data links, and the proactive technology suggestions Sealy's CIO describes.
• emPOWER Security: the security elements of the reference network architecture; the source does not itemise them.

The Singapore and London points of presence are the structurally relevant ones here: they are what allow ten Asia-Pacific sites and a UK site to reach Brisbane over blueAPACHE's own core rather than over the public internet with a tunnel across it.

Outcomes

Outcomes below are as stated in the published case study.

What this case does and does not establish

What it supports. That blueAPACHE can design and deliver a multi-country voice and data network across 18 sites in three regions, and can execute a production cutover without interrupting a make-to-order manufacturing operation. That it did so over roughly twelve months during COVID lockdowns, which removed the option of flying engineers to sites. That the customer's stated experience of blueAPACHE's conduct — proactive, taking ownership, honest — was positive enough to put on the record by role.

What it does not support. Any quantified benefit. The source gives no cost saving, no uptime figure and no latency improvement — the outcome claimed is the absence of disruption, not a measured gain. Nor does it support a compliance claim: blueAPACHE's Managing Director says the reference architecture aligns with "recognised industry security frameworks" but does not name them, so that sentence carries no verifiable content on its own. blueAPACHE separately states ASD Essential Eight Maturity Level 3 and NIST alignment in its brochures, which is where a framework question should be taken.

What it does not establish about today. The source is undated and describes an April 2022 go-live, so it is more than four years old. The footprint (15 facilities, 11 countries) and the relationship status both need confirming before reuse.

What to ask if you are evaluating this. Whether your production process makes the network part of the line or merely a carrier of information; whether you can fund a parallel-running overlap and for how long; which of your sites can be reached over blueAPACHE's own core rather than the public internet; and which named frameworks the reference architecture is assessed against.

Client-side contacts are referred to here by role only.

Turning parallel running into a transition plan

Sealy’s staged change connects migration with continued operations. For another project, record cutover sequence, acceptance and the conditions for returning to the previous arrangement. Establish costs while services run in parallel and who authorises switching. The case supports the described method and outcome, not a standard dual-running period or price. Those decisions belong in the new project and service documents.

Sources and scope

This section connects the sources identified on this page with the KB service-scope catalogue and the terms and conditions guide. Comparison and planning points describe matters to settle for a proposed engagement, not additional service inclusions or new case-study results.

Frequently asked questions

Who is Sealy of Australia?

A Brisbane-headquartered mattress manufacturer and wholesaler that began as Madad Pty Ltd in the 1920s, became the Sealy licensee for Australia in 1969, and since 2000 has operated through a joint venture that underpins Sealy's business outside the United States. It runs 15 manufacturing facilities across 11 countries and sells through retail partners and Sealy branded stores.

What did blueAPACHE deliver?

A new international voice and data network for 18 sites, designed by blueAPACHE, deployed in stages from April 2021 and fully live in April 2022, with ongoing management and maintenance. The rollout covered six Australian sites, one in New Zealand, one in the United Kingdom and ten across Asia-Pacific.

Why did Sealy leave its previous provider?

Sealy's Chief Information Officer said the long-standing telecommunications provider was no longer delivering on relationship quality, price and value; the technology was acceptable but the relationship had reached the point where Sealy had to look elsewhere.

How was the network cut over without stopping production?

By not switching the old network off. blueAPACHE staged the rollout region by region and kept the legacy links live so voice and data could revert if needed, then tested rigorously before go-live. Each site migration became reversible rather than a one-way door.

What does parallel running cost?

Two carriers across 18 sites for the overlap period, which here ran about twelve months. It is an explicit trade of cost against risk, and it is worth it where an outage stops production rather than merely slowing an office.

Why were the Australian sites migrated first?

They are closest to head office and easiest to support in person, so any problem in the method surfaced where it was cheapest to fix — before the same approach was applied to New Zealand, the UK and ten Asia-Pacific sites.

Why is the network so important to Sealy?

Every mattress is made to order with a three-day lead time, and each unit is scanned and given a barcoded quality assurance sticker that depends on real-time data between the factory and Brisbane head office. Without the link a factory does not have work it can identify, which the case study describes as unproductive time, double handling and wrong pieces delivered. The network also carries ERP, accounting applications and voice.

Which security frameworks does the network align with?

The case study does not say. blueAPACHE's Managing Director states the reference network architecture aligns with recognised industry security frameworks but names none, so no compliance claim should be drawn from it. blueAPACHE separately states ASD Essential Eight Maturity Level 3 and NIST alignment in its brochures.

Does the case study quantify any savings?

No. There is no cost saving, uptime figure or latency improvement in the source. The headline outcome is the absence of disruption during an 18-site migration, which is a real result but not a measured gain.

Why did Sealy choose blueAPACHE?

Sealy's CIO cited the time blueAPACHE took to understand requirements before designing, its business experience and technical capability, a workable combination of technology mix and cost, a consultative approach, and cultural alignment between two Australian-based companies that had expanded internationally.

How current is this case study?

The source is undated and describes a network that went live in April 2022, so it is over four years old. Confirm Sealy's current footprint and relationship status before reuse.

Related

• Retail and consumer services — where Sealy is published evidence
• Transport and logistics — the distributed real-time data analogue
• Utilities — the other staged-cutover analogue
• emPOWER Connectivity — the service delivered
• Core Network and Data Centre Interconnect — the PoPs that reach the UK and Asia-Pacific
• emPOWER SASE — the security-led alternative topology
• emPOWER Managed Services — the ongoing management
• emPOWER Security — where framework questions belong
• Lovisa case study — the other multi-country rollout
• Honan Insurance case study — a network replacement comparison
• Archers case study — the other Queensland reference
• ARN: Sealy sleeps easy with blueAPACHE global data network deal — the coverage
• Intelligent CIO: Sealy deploys new international data network — further coverage
• All case studies — the full evidence set

Source

Origin page: https://www.blueapache.com/case-studies/sealy-of-australia

The analysis of make-to-order network dependency and of parallel-running cutover economics is general operational context offered to make the case transferable; it is not attributed to blueAPACHE or to Sealy. The point-of-presence detail is from blueAPACHE's emPOWER Network material. No quantified outcome is claimed because the source states none.

Knowledge Base