Assistance ratings, runtime, user limits and certification claims: the questions that turn a specification sheet into a procurement document.
ExoSelect researchWeiterlesen
Redaktionelle QA
Geprüft auf belegte Parameter, interne Links und unzulässige Aussagen.
Showing English original
Quick answer. Assistance ratings, runtime, user limits and certification claims: the questions that turn a specification sheet into a procurement document.
An exoskeleton datasheet is a marketing document until it is specific enough to test. The difference is not length; it is whether each claim has a defined test condition, a unit and a scope.
Assistance figures are often quoted as a maximum. Ask for the test condition: which joint, which posture, which user, which assistance mode. A peak torque at a single angle is not the same as assistance through a working range.
Is the quoted weight with or without battery, harness, tools and clothing? A 1.2 kg exosuit and a 7.6 kg powered frame are not comparable unless the boundary is identical.
Battery runtime depends on assistance level, user weight, terrain and temperature. Ask for the test profile and the end-of-life capacity. A hot-swappable battery changes the operational model, not the underlying runtime.
CE marking can refer to machinery, medical devices or personal protective equipment. Ask which directive or regulation applies, which standards were used and who issued the conformity assessment. For medical claims, ask for the intended-use statement and clinical evidence.
Not every maker publishes every parameter. The correct response is to mark the value as not disclosed or unknown, record the question and request it in writing. Inferring a value from a similar product is how bad procurement decisions begin.
Our dossiers use four states — known, not disclosed, unknown and not applicable — so that gaps stay visible. Use the same vocabulary in your RFI.
Send the same eight questions to every shortlisted maker. The quality of the answers is often more informative than the datasheet.
An exoskeleton analysis is only useful if it changes what a buyer does next. The purpose of a dossier is not to declare a winner in the abstract, but to make the next conversation more specific: which task, which users, which environment, which constraints and which evidence is still missing.
The first step is to translate the task into a written requirement. Describe the posture, load, repetition, duration, reach height, floor surface and clothing. Add the practical constraints that decide adoption: donning time, heat, tool clearance, cleaning and storage. A system that performs well in a demonstration but interferes with the actual workflow will not be worn after the pilot team leaves.
The second step is to separate the system from the deployment. A device can be well engineered and still fail because the service network is thin, the training is inadequate or the spare-parts lead time is measured in months. Ask for the service model in writing, including response time, replacement units and the cost of consumables.
Data quality should be scored explicitly. A dossier that publishes weight, runtime, user limits and certification scope is easier to pilot than one that leaves those values unknown. Missing values are not automatically disqualifying, but they are a cost: someone has to resolve them before a purchase order, and that work belongs in the project plan.
Use the product index to narrow the field by category, drive type, weight, runtime and region. Treat the filters as a way to structure the question, not as a substitute for reading the parameter states. A system that disappears from a weight band because its weight is not disclosed is telling you something about the dossier.
Place the shortlisted systems side by side in the comparison tool and focus on the rows where they diverge. Differences are useful; similarities are useful too. If two systems are identical on the parameters that matter, the decision may turn on service, fit or commercial terms rather than engineering.
Check the manufacturer profile for verification level, product line and company documentation. A maker with a clear primary source for each claim is easier to audit than one whose brochure is the only available reference. Where a claim matters to safety, ask for the declaration of conformity and the technical file summary.
Finally, write the brief. Include the task, environment, user profile, deployment volume, region and budget range. A good brief lets the research desk separate sourced values from open questions, so the next conversation starts with evidence rather than a demonstration.
Training is part of the system, not an afterthought. Ask who delivers the first session, how competency is assessed and what happens when a new operator joins the team. A device that requires a specialist to fit it every morning has a different operating cost from one that a trained supervisor can deploy independently.
Keep a decision log beside the shortlist. Record what was verified, what was assumed and who owns each open question. When the recommendation goes to a capital committee, the log is often more persuasive than another product demonstration because it shows exactly which risks have been retired.
Send the requirement when the shortlist is ready. The response should make the gaps visible, not hide them behind a polished recommendation. That is the standard this index is built to support.
Start with the intended use, the certification scope and the service model. Those three items decide whether a system can be deployed, not just demonstrated.
No. Published parameters support shortlisting, but fit, comfort, training quality and local service response require a structured evaluation with the intended users.
Missing values are recorded as Unknown or Not disclosed and are never inferred from a similar product. Each dossier shows the date of the last update and links to its primary sources.
Editorial note
Diese Analyse basiert auf veröffentlichten Spezifikationen und benannten Quellen. Es wurde keine eigene physische Bewertung durchgeführt.
Geprüft von der ExoSelect-Redaktion
Quellen und Hinweise
