ARC Logo
Home
About ARC
Industries
Domains
Research
Services
Events
Regions
  
Other Blogs
There are no items in this list.
Links
Images
Home > Domains > Manufacturing IT > Bob Mick's Blog
Welcome to Bob's Blog!
Will Windows 7 be Manufacturing’s Operating System of Choice?

Rumors are that Microsoft is working on the next version of Windows, internally referred to as “Windows 7”.  There is little information about Windows 7 from Microsoft, allowing a lot of speculation about its focus and features.  Some say it is based on Vista.  Others say it is a new more modular OS, enabling it to run well on existing hardware that is memory limited, and I believe that this is essential.  Let me try to explain why.

 

PC resource demands have been steadily growing with each new Windows version.  The pattern is that Microsoft warns us that we will need more computing resource, everyone complains, and then uses it as an excuse to buy a new PC – Corporate IT decisions tended to follow a similar pattern with politics mixed in.  Often, things ran faster and everyone loved the new features and capabilities when it was all over.

 

But something very different happened with XP and Vista.  More people felt that they had pretty much what they needed in their existing OS and were finding it difficult to motivate themselves to toss their existing hardware, and deal with the disruption of getting all their apps to work again.  Adding to this dilemma, applications have also been getting larger, more tightly coupled, more complex and slower in general.  The combination of OS and application trends has recently left us with the feeling that, in spite of our investment, we have not really progressed.

 

My observation is that each OS version has met with increasing resistance to adoption, and it is almost a certainty that a bigger and more feature rich Windows 7 will receive a weaker reception than Vista.  More importantly, it will open the door further to alternative platforms.  IT and end users alike are looking for ways to make their existing hardware and applications serve the purpose a little longer, and sometimes new hardware is not an option.  If supported versions of Windows will not run on existing hardware, more will start looking elsewhere.

 

Linux is the most likely alternative, because it has strong support for server-based applications – IBM, Oracle and SAP support Linux in various ways.  However, most desktops are Windows-based largely because of the popularity of Microsoft Office.  Sun’s Open Office has had minimal impact, but times are changing.  A relatively new challenge to Microsoft Office is emerging.  Web-based versions of word processors, spreadsheets, etc.  are now available from Google, ZOHO, IBM and others.  These applications are still evolving, and many are very comfortable with a Web-based use model. 

 

These new tools are no match for Office, but a significant portion of Microsoft’s market share – those with basic needs - is vulnerable to this new generation of web-friendly office applications.  Even large businesses are spending more time in portal environments where formatting capabilities are minimal.  It is worth noting that these Web-based applications have little or no dependency on the client operating system; Linux will do just fine.  Consequently, a larger, slower Microsoft Windows 7 could further open the door to Linux for a large segment of the Windows market.

 

Manufacturing systems are a different story.  They run many applications - HMI and controller configuration software for example - which are built with the Windows APIs, and there are no good alternative applications on Linux.  Consequently, manufacturers must run Windows 7, but a larger, slower Windows 7 will definitely extend the already slow adoption rates of new OS versions in manufacturing. 

 

The biggest risk to Microsoft in manufacturing is the potential lost market share and ISV mind-share for Operations Management software.  With SAP and Oracle moving aggressively into this market, Java becoming commonplace, and Corporate IT taking a stronger role in decisions about on-site systems, Microsoft’s dominance is likely to erode anyway, and a bigger, slower Windows 7 will only accelerate this process.

 

To be clear, my intent is to argue that the market requirement – even beyond manufacturing - for Microsoft 7 is to consume substantially less computing resources and result in significantly faster applications.  (Yes, there are other requirements.)  This makes sense for Microsoft in general even though it will take some time for Web-based office tools to seriously threaten Office’s dominance.  It will help Microsoft accomplish one of their important objectives, which is to enable manufacturers to keep their operating systems current and thereby mitigate many security concerns. 

 

Is this a good time to bring up “no re-boots” for patches as well?

Security Patch Management in Manufacturing Needs Standards

The requirements for security patch management in manufacturing operations (sites, factories, plants) has not changed for several years, but there has been slow improvements in practices and no improvements in tools.  In fact, some large companies are living with high risks, because they simply cannot keep up with patches.  Some gamble by taking too long to apply patches, and others are forced to apply patches without adequate testing, potentially creating "land mines", where operators might encounter problems as they invoke infrequently used functions.  Most companies are left to improve things on their own, because there is no consistent context to share and re-use practices and experiences.

 

I sometimes hear manufacturers justify weak patch management practices by arguing that system isolation or security infrastructure (firewalls, appliances ...) protects un-patched systems.  Indeed they do reduce the risk of incidents and are necessary.  But we actually need good patch management as well, because there are too many ways (some yet to be developed) for virus, worms, attackers, etc. to enter manufacturing systems.

 

Two of the underlying inhibitors to rapid progress are the complexity of patch management in existing manufacturing environments - a large number of diverse and obsolete system configurations - and lack of standardized industry practices and tools.  The latter are needed to reduce the cost and time required.  For example, desktop patch tools cannot be used in a manufacturing environment without customization.  The unfortunate reality is that excellence in patch management offers no obvious competitive advantage.  Consequently, budgets will never be adequate unless we can finds ways to reduce complexity, cost, time required.

 

Patch management is a good candidate for collaborative community efforts, because it offers no competitive advantage, even though it is expensive, disruptive and associated with high risk.  However, there are few standards activities associated with patch management needs, and only one of those (ISA99) addresses the needs of manufacturing.

 

When ISA99 asked its community about the seriousness of the problem, there was tremendous interest and loud agreement that standardization was needed.  ISA99 created Working Group (WG) 6 in conjunction with the Microsoft Manufacturing User Group (MS MUG) which was already working on patch management.  However, when WG6 was created, everyone except Bill Cotter (3M) who is the WG lead, Troy Embree (P&G), Bruce Honda (Weyerhaeuser) and few other believers "took one step backward".  The resulting small ISA99 WG6 has good ideas but has been struggling to make progress.  The group is now doubling the rate of working sessions and this will help, but WG6 is below critical mass.  What WG6 needs is more help - people and companies that will donate significant time to make rapid progress before it becomes a crisis.

 

It is not hard to find areas for improvement.  The groups work includes topics such as semantics, information exchange standards, practices, patch tools and others.  All are intended to reduce cost and risk by cutting the time it takes to monitor, evaluate, prioritize and apply patches.

 

Please contact me, or any of the ISA99 Patch WG6 team, if you will donate your time and skills or have questions.

 

Bob Mick's Blog for Technology Related Topics
ARC already publishes Insights (the 4 pagers), Strategy Reports (16-20 pages), ARCwire news, ARCwire reports (briefings, events ...), slide sets and others.  These cover most of our formal publications, but occasionally there is a need for smaller and less formal communication. As such, individual Analysts now have a personal blog site where they can informally talk about their specific areas of expertise.
 
In my case, this blog is mostly about the technology related topics I research, and this includes things like:
  • Integration, Interoperability
  • Standards, Communities
  • Architecture, SOA
  • Security
  • Data Management
  • Business Process Management
  • Intelligence and analytics
  • User interface
  • Operating systems
  • Software development (tools, IDEs, ...)

Very little of this is industry or company size specific, but SMB needs and strategies are often distinct from their larger counterparts and need to be considered.

What content will this blog add that is not already in Insights?  A blog format gives me the opportunity to publish shorter pieces about the technologies and their use:

  • Use cases, project wins, emerging practices
  • Emerging technologies and their applications
  • Vision, models, strategy, initiatives
  • Commentary on supplier technical strategies

To be clear, the content that is being published as Insights and ARCwire pieces will continue and will not be duplicated here.  They will be included here by reference only. 

Categories will be added as the number of entries grows, probably structured by technology topic (as in the first list above).

Feedback is sincerely welcomed, either directly to me by email, or by adding comments to individual blog entries. 

 
 

 ‭(Hidden)‬ Admin Links

 Recent Reports Published

For some time now businesses have been taking a business process perspective, solving data quality issues as they are encountered. ...

The high cost of poor quality product data in retail and other areas is generally acknowledged and reasonably well known.  <...

Business performance initiatives continue to address a large variety of problems. One key to success is using technology that is appropriate for the need,...

The many costs associated with poor data quality have been well documented.  Master Data Management (MDM) strategies can imp...