Industry News, Trends and Technology, and Standards Updates

We live in a world where cell phone upgrades have become a way of life. Some people upgrade every time a new phone is available so that they can have the latest, greatest features and gadgets. Others prefer to keep their old phone since they are familiar with how it works and are satisfied with the phone’s functionality. While others still may upgrade because they have encountered a problem with their current phone that either can’t be fixed or has been addressed in the new model.

There are similar reasons to upgrade to a new version of a Cimetrix product. Here are a few sample questions that will help an OEM determine when is the best time to do so:

1. Is there an issue my customers are currently facing that has been addressed in the new version of the product?

Cimetrix works to fix customer-reported issues as well as issues found during internal testing. It is not possible to make these fixes in all previously released versions of the product, so they are made as a fix in the latest released version of the product. Upgrading to the latest version benefits the OEMs by providing fixes to issues they may have reported or, more often, to issues they haven’t seen but have been reported by other OEMs.

2. Are there added features or capabilities in the new version of the product that will improve my ability to support my customers and/or allow me to provide new functionality to my customers?

Cimetrix strives to support our customers by providing high-quality software products. As new technologies emerge and as scenarios in which our products are used evolve, we discover new ways to provide additional benefits to our OEM customers. These new capabilities are made available in new releases of our products. These improvements can include things like enhanced logging and diagnostic capabilities, new utilities for managing configuration files, or new screens for making setup easier.

3. Am I planning a new release of my equipment control software?

Like Cimetrix, OEMs are continually looking for ways to improve their equipment and provide new features and functionality to their customers. This means that they will periodically release new versions of their equipment that may contain new hardware and/or software functionality. This is an ideal time for OEMs to also upgrade their Cimetrix software so that their new platform can take advantage of the latest fixes and enhancements that are available.

This is by no means meant to be an exhaustive list of questions to be asked/answered when determining the right time to upgrade to a new version of a Cimetrix product, but it does give you an indication of the type of things that should factor into your decision-making process. Each new software release has a set of Release Notes that describe the software fixes and new features that have been added in that release. These Release Notes are there to help you make the best determination as to when to upgrade, so be sure to read them carefully. And, as always, the Cimetrix Support team is available to answer any questions and provide additional information if you should need it.♦

I recently read The Martian by Andy Weir. Since this information comes out on the first page of the book, I don’t think I’m spoiling too much to say that it is the story of an astronaut, Mark Watney, who is lost in a space storm on a mission to Mars. He is presumed dead by his crewmates and abandoned on the planet. Of course he is not dead and he has to use training, skill, ingenuity, and luck to survive long enough to be rescued. Several times throughout the adventure, he has to connect life supporting utilities, tanks, airlocks, and vehicles together using the connecting valves supplied on each component. Watney says, “I’ve said this many times before, but: Hurray for standardized valve systems!” This is obviously a work of fiction, but what would have happened if he had tried to attach a holding tank to the ascent vehicle but the valves had changed between versions?

Software customers should be able to have the same expectation as Mark Watney that the valves don’t change during the mission. In the case of software, we aren’t talking about physical valves. Rather we are talking about software interfaces and API method signatures. In a real sense, the consistency of these software signatures are as mission critical as the standardized valve connections were for the astronaut in The Martian. Changing the method signatures, at the very least, requires that the users of the software have to rebuild their applications. Often times such changes require software users to have to requalify their entire tool. This places undue burden on the users of the software. Software users should be able to reasonably expect that the interfaces and API remain constant through the life of the mission (i.e. within the version of the software including minor releases and patches). A side note on this topic: If Cimetrix product management determines that a piece of software has a bug or does not conform to the SEMI standards on which our products are based, changes will be made to correct the problem. Similarly, if NASA determined that one of their connectors did not conform to the spec, they would immediately resolve the issue for the item that was out of spec.

The Cimetrix release versioning process (see our January 14, 2016 blog) allows Cimetrix personnel and Cimetrix software users to be aware of what backward compatibility guarantees are made for a specific version of Cimetrix software.

We would like our software users to be able to say, “Hurray for compatible software versions!”♦

Last November Linkgenesis Corporation, based in Seoul, became the official Korean distributor of Cimetrix’ EDA/Interface A solution CIMPortal Plus.

This partnership was a perfect fit as we at Linkgenesis have been providing software products and development services in manufacturing information automation systems and the software testing area since 2001. In November of 2014, Linkgenesis merged with IT-Innovation, a communication software solution provider for semiconductor and LCD factories.

In cooperation with Cimetrix, Linkgenesis will be delivering the globally-proven EDA solution to Korean customers, and will also provide enhanced XGem/XGem300 GEM Driver harnessed with CIMPortal Plus so that customers using XGem/XGem300 can easily adapt their equipment to provide EDA capabilities. XGem/XGem300 GEM Driver is a Linkgenesis’ software driver supporting SEMI 300mm standards and is based on XCom SECS Driver that has been proven reliable for more than 200 customers. Linkgenesis’ software testing tool, MAT (Machine Auto Tester), has also been largely used by Korean mobile companies and automotive companies such as Samsung Electronics, LG Electronics, and Hyundai automotive groups.

SEMI EDA/Interface A standards were originally established in 2006 with Freeze-I and then updated with Freeze-II in 2010, but Korean chipmakers have not actively adopted Interface A standards in their production processes. However this is beginning to change as Samsung Electronics released its plan to introduce Interface A on its pilot line last August and SK hynix also started discussion of introducing Interface A.

In addition, Samsung Electronics plans to build a new line at its Pyeongtaek, South Korea and SK hynix’ plants to increase its production line at Cheongju and Yicheon, South Korea. However, according to Gartner’s forecast, semiconductor equipment spending by Samsung Electronics and SK hynix are going to slightly decrease this year. Samsung Electronics will invest $11.4 billion, which is a 13.5% decrease from 2014, and SK hynix will invest $4.8 billion this year, which is a 10.6% decrease from 2014.

We believe this new partnership between Linkgenesis and Cimetrix will provide a great deal of advantages to Korean customers in this emerging market, and will promote the increased interest in EDA/Interface A technology for chip manufactures.

Linkgenesis will be exhibiting at SEMICON Korea 2016, which will be held in Seoul on January 27-29. Please stop by our booth in Hall C #1739 to see our product line as well as Cimetrix’ CIMPortal Plus, and discover how our software brings the latest innovations to the semiconductor manufacturing industry.♦

There are times in life when a surprise is a good thing. Like when you get a box of chocolates. We all remember the line from the movie Forrest Gump, “Life is like a box of chocolates, you never know what you’re gonna get.” When you install a new version of software however, surprises aren’t as enjoyable. With a new software release, customers need to be able to assess the effort and impact the new release will have on their current systems and procedures. Then they can evaluate whether the new features and functionality will be worth the effort to deploy the new software release. One way software companies can help communicate the impact a new software release may have on customers is by using a clearly defined release versioning procedure.

Change is good and software products that grow and mature over time, adding new features and eliminating unwanted behaviors, can remain healthy and viable over a long period of time. However, consistency and predictability are also important characteristics of good software products. So how do software companies balance these two seemingly competitive objectives?

Many software companies can do this is through the way they use software versioning. It is common for software companies to use a major.minor.patch.build software versioning scheme, for example iTunes 12.3.1. This type of software versioning allows the software company to communicate the scale and impact of the changes in the release to their customers. A change in the “major” release number indicates to customers that there are some significant changes in this release that may impact the way it interacts with the product. The customer will likely need to make code changes or procedural changes when upgrading to such a release. A change to the “minor” release number denotes that there are multiple changes in the release, but customers should see only minor, or possibly no changes, in the way they use the product. A minor release may include some small new features that could potentially require code changes if the customers wants/needs those new features. A “patch” release is generally used to address a specific issue and should not change the customer experience with the software. The build number is most often provided to help the software company when researching a question or customer reported defect.

Software versioning provides a way to set expectations with the customer about what is in the release and how it might affect the way they use the product. It can help take the surprise out of the process of installing a new software release. Life may be “like a box of chocolates,” but software releases shouldn’t be.♦

If you would like to learn more about the semiconductor industry, software best practices, and other topics related to new technologies, please subscribe to our email updates using the form in the upper right corner of this page.

We here at Cimetrix are excited that we are implementing a new process that will both benefit our clients and the environment. We have always delivered our software runtime license orders to our clients on CDs along with hardcopies of their Certificates of Authenticity (COA). Well, starting January 1^st, we will begin delivering orders to our clients through emails that will include a digital COA for each runtime license and instructions on how to download their software.

As a company, we have always prided our self on providing the finest quality customer experience possible so we feel that this new process is just one more step in improving our service. There are a number of benefits of this change:

• Most of our clients integrate Cimetrix’s software with their own software by using the Software Development Kit (SDK), most runtime license CDs are simply thrown away, which in today’s world is really not acceptable. By making this simple change, we will be eliminating thousands of pounds of potential waste.

• We are constantly improving our software products and the latest version should always be obtained from our Support website (cimetrix.com/online-support)—not from a CD stored on a shelf somewhere for who knows how long. This change ensures that the latest version of our software will always be used.

• The shipping cost and time delay by sending CDs by a carrier will be eliminated which will be a direct cost savings to you. 

• The proof-of-purchase for our runtime license is the COA, not the CD. The COA number is what is used to obtain the license code using our online license generator. 

So the only thing we need our clients to do is to make sure we have an email address on file of where they would like their future orders sent. It’s that simple. We do foresee a period of adjustment for some clients, so for those that still want CDs and hardcopy COAs delivered, we will have this option available for an additional fee.

Of course, if you have any questions or comments regarding this policy, we are always happy to hear from you.  You can contact us at Orders@Cimetrix.com.