The result: QEWS minimizes manufacturing rework, delayed product shipments, warranty claims in recall of defective products--all of which can and do contribute to lost time, higher costs, and lower client satisfaction.
In 2012, QEWS was recognized by InformationWeek as a leading innovation.
Haye based her recommendation on the fact that the QEWS sits at the intersection of business analytics and the cloud across IBM's suppliers, its clients, and IBM itself.
Moreover, QEWS was already gaining interest as a "showcase" application, for demonstration to IBM's clients; moving it to the cloud could make it easier to use in future collaborations with clients, suppliers, and business partners.
In February 2013, the push to put the QEWS application on the cloud began in earnest.
Moreover, QEWS encompasses an abundance of quality performance data and information about supply chain risks.
The migration of QEWS to CMS took longer than expected; Ward's team--and the ISC executives--had hoped it would take weeks, but in fact it took several months.
ISC's early forays into harnessing cloud for the supply chain has given its leaders every confidence that the technology model can prove valuable in many other applications beyond QEWS.
One important takeaway from the longer than expected migration of QEWS is that ideally, such applications should be built on the cloud in the first place rather than trying to retrofit them onto the IaaS layer.
As noted earlier, the QEWS solution is of practical importance outside of IBM.
Essentially, new applications can be ported over to the cloud in just a few weeks, whereas the QEWS application took six months to reach that stage.