Do you know your patch compatibility?

A pending ISA99 technical report defines a standard XML format for automation vendors to publish patch compatibility information.

03/01/2010


Managing dozens of software applications on dozens of servers with supporting software elements, such as browsers, office tools, and virus protection can be an overwhelming task. There are numerous compatibility issues for patches and updates from multiple vendors. On the first Tuesday of every month, Microsoft releases a new set of OS (operating system) and application patches, and automation vendors start testing the supported versions of their software against the patches.

Other vendors also release their patches and updates regularly or as needed. Virus updates may come out several times a week; database patches and updates may be released every few months; automation application patches and updates may be released quarterly. Manufacturing IT staff need to keep track of all these changes and all the compatibility dependencies across all of their applications. For example, your vendor’s HMI may require a specific version and minimum patch level for an OS, your data historian may require a different patch version, and your database may require a different maximum patch level. It can be a fulltime job just collecting the compatibility information from all of your vendors and building a compatibility network.

Managing patch and update compatibility across vendors is difficult, but managing patch and update compatibility within a vendor suite can be even more complicated. Most of the large automation vendors have constructed application suites by buying software companies and collecting the software into a commonly named suite, even if the software doesn’t integrate. It’s not uncommon to hear “… well, that version of the HMI doesn’t work with the latest version of our database” from your vendor’s support staff.

Because of compatibility issues, many organizations will get one application and operating system configuration working and then will not install any new patches or updates. While this strategy minimizes your support effort, it does add a significant amount of risk.

The ISA99 committee on industrial automation security is working on solutions to the problems of patch management in industrial systems. One new work product of the committee is a pending technical report that defines a standard XML format for vendors to publish their patch compatibility information.

Vendors currently publish the information in PDF files, spreadsheets, databases, and Microsoft Word documents. The formats for publication are not common, and it is sometimes difficult, if not impossible, to find detailed information on: what was tested for compatibility; if testing is planned; and the results of the tests (success and failure). The ISA99 patch compatibility format addresses these issues.

Each vendor would provide a set of patch compatibility files for their products. Each file identifies the vendor’s product and version, the patch that was tested, and the test results. Patches are identified by the patch vendor’s name (such as Microsoft, Adobe or Oracle), the patch ID (which in the case of Microsoft is Patch KB-Number), the version of the patch, and the release date of the patch. The test results can specify if the patch applies to the vendor’s product, if a test was performed or is still in progress, and test results.

When vendors provide this information in a common format, it is possible to construct a compatibility network that shows the impact of implementing a patch or update on all of your systems. Vendors that provide this information across their own suite will also reduce their support and service calls.

In patch management, knowing compatibility dependencies helps you make intelligent decisions about what to patch and when to update. Ask your vendors to support the new format and make your job easier.




References

www.isa-99.com

 


Author Information

Dennis Brandl is president of BR&L Consulting in Cary, NC, www.brlconsulting.com . His firm focuses on manufacturing IT. Contact Dennis at dbrandl@brlconsulting.com .




No comments
The Top Plant program honors outstanding manufacturing facilities in North America. View the 2013 Top Plant.
The Product of the Year program recognizes products newly released in the manufacturing industries.
The Leaders Under 40 program features outstanding young people who are making a difference in manufacturing. View the 2013 Leaders here.
The new control room: It's got all the bells and whistles - and alarms, too; Remote maintenance; Specifying VFDs
2014 forecast issue: To serve and to manufacture - Veterans will bring skill and discipline to the plant floor if we can find a way to get them there.
2013 Top Plant: Lincoln Electric Company, Cleveland, Ohio
Case Study Database

Case Study Database

Get more exposure for your case study by uploading it to the Plant Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.

These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.

Click here to visit the Case Study Database and upload your case study.

Bring focus to PLC programming: 5 things to avoid in putting your system together; Managing the DCS upgrade; PLM upgrade: a step-by-step approach
Balancing the bagging triangle; PID tuning improves process efficiency; Standardizing control room HMIs
Commissioning electrical systems in mission critical facilities; Anticipating the Smart Grid; Mitigating arc flash hazards in medium-voltage switchgear; Comparing generator sizing software

Annual Salary Survey

Participate in the 2013 Salary Survey

In a year when manufacturing continued to lead the economic rebound, it makes sense that plant manager bonuses rebounded. Plant Engineering’s annual Salary Survey shows both wages and bonuses rose in 2012 after a retreat the year before.

Average salary across all job titles for plant floor management rose 3.5% to $95,446, and bonus compensation jumped to $15,162, a 4.2% increase from the 2010 level and double the 2011 total, which showed a sharp drop in bonus.

2012 Salary Survey Analysis

2012 Salary Survey Results

Maintenance and reliability tips and best practices from the maintenance and reliability coaches at Allied Reliability Group.
The One Voice for Manufacturing blog reports on federal public policy issues impacting the manufacturing sector. One Voice is a joint effort by the National Tooling and Machining...
The Society for Maintenance and Reliability Professionals an organization devoted...
Join this ongoing discussion of machine guarding topics, including solutions assessments, regulatory compliance, gap analysis...
IMS Research, recently acquired by IHS Inc., is a leading independent supplier of market research and consultancy to the global electronics industry.
Maintenance is not optional in manufacturing. It’s a profit center, driving productivity and uptime while reducing overall repair costs.
The Lachance on CMMS blog is about current maintenance topics. Blogger Paul Lachance is president and chief technology officer for Smartware Group.