Yes, I remember the difficulties with component tracking and part numbers. For some reason REACH didn't see to cause the same consternation. At least not that I noticed. I guess it's becasue REACH was more of a reporting function.
Actually, among the high-end embedded board-level products we covered, RoHS seemed to affect most the manufacturers that served both mil and commercial customers, since they often ended up running two separate lines for two different versions of the "same" product. Mil-only board manufacturers were not affected much until later. One thing that did affect them both was the nightmare of components tracking and part numbers changing.
Since there were only two of us, myself and the editor-in-chief, I did a little of everything. Mostly we did not address distribution, but design and development technologies for HW and SW, comms, and a lot of board-level products and technologies. I wrote several features on RoHS, too.
As I learned working for COTS Journal, COTS doesn't just mean actual end-system computers and apps software. It can also refer more broadly to both software and hardware design and development platforms, specifically for creating end-system hardware and software used in the field. Ruggedization is taken for granted for military field use; that feature doesn't determine whether a machine is COTS. A COTS-based machine may also be further tweaked--and usually is--for specific apps. The big difference is that the military is no longer spending zillions of dollars on proprietary, entirely customized systems.
What I've heard is that the COTS stuff is used for office and support functions. When it comes to electronics out in the field, the electronics are ruggedized (and leaded) so they can withstand a difficult environment over many years.
The COTS systems, platforms, networking technologies, and software are, as the term says, commercial off-the-shelf hardware and software, meaning stuff that's originally designed and built for the rest of us. Basically, that means the military is using Windows-based laptops and other standard commercial hardware and software, as well as standard networking protocols, which is actually kind of scary. This is instead of spending zillions of dollars on designing their own stuff, like in the "good old days." Even the NSA buys a lot of standard signal-processing equipment.
Interestingly, many of the older "antiques"--more like family heirlooms--in my house are made of bio-based materials, such as wood and paper (which also used to be considered sustainable materials until we nearly used them up), or ceramics and brick, which are sustainable. Even metals were sustainable, and still are. Most of these materials are commonly found in the rubbish heaps of our ancestors, and give archaeologists a lot to study. Much of the problem with materials becoming non-sustainable has occurred in more recent times because of overuse (due in part to enormous population growth), as well as because of newer materials with complex processes and polluting wastes.
In an age of globalization and rapid changes through scientific progress, two of our societies' (and economies') main concerns are to satisfy the needs and wishes of the individual and to save precious resources. Cloud computing caters to both of these.
For industrial control applications, or even a simple assembly line, that machine can go almost 24/7 without a break. But what happens when the task is a little more complex? That’s where the “smart” machine would come in. The smart machine is one that has some simple (or complex in some cases) processing capability to be able to adapt to changing conditions. Such machines are suited for a host of applications, including automotive, aerospace, defense, medical, computers and electronics, telecommunications, consumer goods, and so on. This discussion will examine what’s possible with smart machines, and what tradeoffs need to be made to implement such a solution.