Sometimes things disappear without a trace—simply gone. You can console yourself with statements like, "There's always a little loss!" This disappearance of things also wreaks havoc in development projects. When developing embedded systems with multiple developers, it's often difficult to keep the materials together. Developers' demand for batteries, sensors, accessories, devices, simulators, and measuring instruments always seems to be high.
In my current project, we're trying to get to grips with this phenomenon. The idea is so simple and obvious that I'm surprised it isn't used more often. Therefore, I decided to write a blog post about it.
Device management
Before I write about the tool for combating entropy, I would like to say a few words about device management. Managing devices during development is a very important task that should be overseen by the systems engineer. Functional models or prototypes under development should be clearly identifiable by a unique serial number and release label. These labels allow statements to be made about the installed components, the software used, and the current status or patch status with the help of device documentation. Database-driven tools or classic Excel spreadsheets can be used for this. Particular attention must be paid to devices used for qualification and testing. The hardware and software used in test reports must be documented in such a way that the test is traceable and repeatable at any time. This makes it necessary to document which device, in which state of construction, and with which software a test was conducted.
|
|
| Dipl.-Ing. Goran Madzar, Partner, Senior Systems Engineer E-mail: madzar@medtech-ingenieur.de Phone: +49 9131 691 240 |
|
Do you need support with the development of your medical device? We're happy to help! MEDtech Ingenieur GmbH offers hardware development, software development, systems engineering, mechanical development, and consulting services from a single source. Contact us. |
|
The magic remedy to combat entropy
But I don't want to keep you in suspense any longer. The magic cure for combating entropy is a box. This box must be large enough to contain the system, including accessories and simulators. Furthermore, the box must have a lid. An open box offers no protection, and the contents will diffuse away over time. The entire set, consisting of box and contents, is labeled with the serial number of the system it contains. Before the set is distributed to the developers, the systems are tested, and the results are recorded. The system in the box is then marked with a "tested" seal and may be used for development purposes from now on. It is important that the set is handed over to a person responsible for it. This responsibility is documented in the device management record.
Advantages of this approach
For me, this approach offers several advantages that definitely justify the effort and cost.
- Everything has its place, so things don't disappear into drawers or get lost.
- Developers get a complete set and don't waste time searching for parts.
- Everyone who has received a set is responsible for keeping their pieces together.
- A set can be easily transported and shipped.
- A high-quality box encourages more conscious handling of the prototypes. High-quality products don't belong in tattered boxes or plastic bags from discount stores.
- A set can be archived after qualification, allowing for retests later.
- Pre-testing the sets ensures that the prototypes are fully functional, at least at the time of testing.
I don't want to miss out on these advantages in this and future projects. And perhaps this insight will help you in your projects as well. I'm very happy to receive feedback and engage with you. Feel free to comment on this article. If you know someone who might also be interested in the blog, I would be very happy if you would recommend it.
Best regards
Goran Madzar