Skip to main content

Where in the world is Robert Madge?

Many people emailed me to ask what is Robert Madge doing these days...

Robert Madge is the President of IDtrack (the European Association for Secure Identification), a non-profit organisation based in Barcelona, Spain, which provides information, guidance and coordination for the secure implementation of radio-frequency identification (RFID) and other techniques of automatic identification.Mr. Madge is also the founder of Xifrat Daten AG, of Zug in Switzerland, which develops software technology for large scale database implementations, and which produces solutions for process flow and for data-intensive product tracking and tracing applications (arising from the use of RFID and other data gathering technologies).
In addition, Mr. Madge is the founder and International Director of FoodReg AG, which provides automated record-keeping and controls for the food industry and which is a pioneer in food traceability solutions and computerised food safety programmes. Furthermore he is the founder and Chairman of Olzet Solutions SA, which provides consultancy and project implementation services across Europe to companies implementing product traceability and supply chain execution projects, and the founder of Olzet Seguridad Alimentaria SA, which provides similar services to the food industry in Spain.
From 1986 to 2001, Mr. Madge was the Chairman and CEO of Madge Networks NV, a company in the field of networking technology and products. Under Mr. Madge’s leadership, Madge Networks grew to become one of the world’s leading network product companies in the mid-1990s, producing innovative products based on the technologies of token ring, ATM, multi-media, and wireless networking. The company’s operations extended to offices in more than 40 countries, and annual sales of $500 million.
Prior to 1986, Mr. Madge was the Technical Director of Intelligent Software Ltd, an R&D company in the UK, and in 1981 was the inventor of the world’s first electronic organiser (which were the forerunners of PDAs).

https://www.linkedin.com/pulse/my-top-10-posts-pulse-ronald-bartels/
 

Comments

Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

A checklist for troubleshooting network problems (22 things to catch)

  Assumptions! What is really wrong? Is it the network that is being blamed for something else? Fully describe and detail the issue . The mere act of writing it down, often clarifies matters. Kick the tyres and do a visual inspection. With Smartphones being readily available, take pictures. I once went to a factory where there was a problem. Upon inspection, the network equipment was covered in pigeon pooh! The chassis had rusted and the PCB boards were being affected by the stuff. No wonder there was a problem. In another example, which involved radio links. It is difficult with radio links to remotely troubleshoot alignment errors. (I can recall when a heavy storm blew some radio links out of alignment. Until we climbed onto the roof we never realised how strong the wind really was that day!) Cabling. Is the cable actually plugged in? Is it plugged into the correct location. Wear and tear on cabling can also not b