Build rich, smart HTML5 and JavaScript apps for any platform, browser or device
Use Angular, TypeScript or JavaScript to build truly native mobile apps
Deliver superior customer experiences with an AI-driven platform for creating and deploying cognitive chatbots
Deliver Awesome UI with the most complete toolboxes for .NET, Web and Mobile development
Automate UI, load and performance testing for web, desktop and mobile
A complete cloud platform for an app or your entire digital business
Detect and predict anomalies by automating machine learning to achieve higher asset uptime and maximized yield
Automate decision processes with a no-code business rules engine
Optimize data integration with high-performance connectivity
Connect to any cloud or on-premises data source using a standard interface
Build engaging multi-channel web and digital experiences with intuitive web content management
Personalize and optimize the customer experience across digital touchpoints
Build, protect and deploy apps across any platform and mobile device
Rapidly develop, manage and deploy business apps, delivered as SaaS in the cloud
I’ve been a McKinsey follower for 20 years and often used their insight as fodder for some of my presentations. I always try to blend a bit of business sense into what I say and a big part of what I have to do is bridge the business and technical value of what we have to offer. Emerging technology, where I’m often found, always has a sense of a solution looking for a problem and any time there’s a catalyst from an industry and market force such as McKinsey, I’ll take it.
I was intrigued by the title of the latest (January 2011) McKinsey Quarterly issue where “Building the supply chain of the future” was tackled. Now this piece, crafted by Yogesh Malik, Alex Niemeyer, and Brian Ruwadi, brings up some interesting points about meeting the challenges of the next generation supply chain. In particular, their points on splitting monolithic chains into smaller, more nimble segments and viewing the supply chain as a dynamic entity in an effort to hedge uncertainty. Both will require new thinking on the part of the business and both will require more from the technology in place. The focus then becomes not just visibility but one that emphasizes operational responsiveness.
Responsiveness in the supply chain requires heightened awareness of all segments in the chain. “Nimbleness” is achieved by being able to sense and respond to changing conditions and allow for immediate, in-flight, changes to the processes that run the chain. Siloed systems and management won’t work. Strictly relying on information gathered after the fact may be too late.
You’ll need to move from reactive to responsive. The good news is that it’s possible now – and with much of what you already have in place. We can do that with Progress RPM right now. If you’re re-thinking your supply chain, you might want to check it out: Progress Responsive Process Management (RPM) suite.
View all posts from David Olson on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Copyright © 2018 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.