I've failed to meet Requirement ' G. Needs to be available… fast! (ideally within 24 hours)'!
Have to say, when searching for an engineering material, it's not good to limit choices with purchasing considerations and colour restrictions.
However, on the face of it, an Austenic Stainless steels comes close to meeting Donald's needs. Unfortunately, he rejects Carbon Fibre, suggesting he's doing something very special because Carbon fibre magnetically outperforms most Austenic Stainless Steels.
It would help to know if the sheet's purpose is to protect a permanent (or electro-) magnet from dirt and dings, or to allow a magnetic field to reach a sensitive detector. The attenuation caused in the first situation can be overcome by using a more powerful magnet. The second case is more difficult. Having to join the dots in Donald's partial requirement is unhelpful: I guess the unstated need is to protect a big magnet rather than a sensor because electric fields haven't been mentioned – yet! Could be wrong.
Anyway, if 'A. Completely non-magnetic' really is important, then Donald needs a particular grade of Stainless and it needs to be worked carefully. Not 316, or 316L, but 316LN. 316LN is formulated to minimise it's magnetic effect, and to be less susceptable to having it's magnetic properties trashed by cold-working, flame-cutting, or welding. It's not just the material, it may be import to use it properly. (A few other grades like 304LN, 305, or 310 would perform as well as 316LN.)
But I suspect Donald's requirement may be carelessly worded and ordinary 316L is fine. If so that's a good thing because 'almost non-magnetic' stainless steels are easier to find and use than 'Completely non-magnetic'.
Not throwing rocks at Donald, the point is Requirement Writing is difficult! Sadly, what's crystal clear in the mind of the writer is often morphed by the written word and the reader trying to decode it into an ambiguous, contradictory muddle. Some advice on Requirement Writing, here and here. Note the second link kicks off by saying: 'It has become clear that enormous numbers of engineering design errors originate in the requirements document.' Too true!
In formulating requirements I recommend:
- Giving as much information about goals as possible. (Writing requirements when the goal is secret is exceptionally difficult because the writer has to get everything right. He cannot rely on the reader to second guess what he's after. If the writer doesn't get it spot on, the reader loses confidence in him.)
- Ideally, requirements should concentrate on what things have to do, not how they should do it. Avoid steering towards particular technical answers.
- Always use the word 'must' or 'should'.
- Aggressively self-criticise 'Must' requirements before release because they severely cramp the solution, often in unexpected ways.
- Word 'Must' requirements to get clear yes/no answers. Reword the requirement if 'yes but' or 'no but' answers are acceptanble: it's either badly worded or is a 'should' requirement.
- 'Should' requirements are only desirable and should be weighted to indicate their relative importance. The requirement must be worded such that the response is measurable.
- Numbers should be used wherever possible.
- Avoid unquantifiable words like reasonable, easy, fast, quality, good, strong. They don't help!
- Don't use show-stopper words like 'completely' unless absolutely essential. Many projects fail because over tight requirements carelessly commit them to expensive, unattainable, or time-wasting solutions.
- Get someone else to review the draft and don't take offence when one's pride and joy comes back plastered in red-ink!
Dave