Brief
Start from the application problem and the material that exists today. For an aramid route, say whether the reference is a fiber, a yarn, or a protective fabric, and which hazard is driving the change: cut, heat, flame, abrasion, or a combination that still needs to be split. For a carbon fiber route, say whether the current item is a tow, a woven reinforcement, or a prepreg, and which process step is failing or untested.
Record linear density or construction, mass per unit area when the item is a fabric, and usable width when cutting yield matters. If the current reference is only a trade name, add the physical description you can see: filament appearance, weave, or package type. A development conversation stalls when the starting point and the desired point are written as one sentence.
- Use environment, including heat, cut, or composite cure context
- Processing conditions such as cutting, sewing, layup, or consolidation
Explore
Discuss construction and finishing routes only after the brief names one change. An aramid fabric might be reviewed for a different weave, a different mass, or a finish that changes handle, while the fiber family stays the same. A carbon fiber question might compare fabric architecture or resin state, and that comparison should not borrow tensile language from an aramid yarn data sheet.
The output of this column is a sample question, not a statement that a sample exists. Describe the difference you want to see and the difference you want to hold constant. If shade is irrelevant to a protective or reinforcement grade, leave color out. If a coating or resin is part of the item, name it as its own layer rather than folding it into the fiber name.
- Input
- One target change, written as a requirement
- Output
- A sample question with the unchanged attributes listed
Evaluate
Agree the evidence required before further development. A protective evaluation might need an abrasion method, a tear method, or a heat exposure condition, each with its specimen state. A reinforcement evaluation might need fiber grade, areal weight, and the dry or prepreg condition. Results from those methods are not interchangeable, and a single pass-fail word should not replace the method name.
Keep the approval record next to the specimen. A dated swatch, a yarn package label you can describe, or a previous report reference is enough to start. Do not treat a logo on a document as proof that this website holds the certification. When the method or the specimen condition is unknown, the evaluation step is to request that context, not to fill a number.
Three limits sit on every review. A numeric target is not a measured result. A method for tear strength does not answer pilling, seam slippage, or abrasion resistance. A document that names another certificate holder does not become a credential of this website. Street address, founding year, headcount, output, and price are unknown here and stay blank. Colorfastness to staining is often reported on a 1–5 gray scale, and lightfastness on a 1–8 blue-wool scale; both are method conventions, not Teijin results. Hydrostatic head, water vapor transmission, and air permeability stay off an aramid brief unless a coating or a lamination is part of the specimen. Warp, weft, yarn count, and dimensional stability belong on the cloth. Denier and dtex stay on the yarn, using dtex = denier × 0.9.
Worked example, not a customer record. Background: a brief asked for a lighter protective cloth and cited an existing aramid weave. Process: GSM in g/m² and usable width in cm were split into “current reference” and “requested target,” and the abrasion method was left open. Result: the target mass was not copied into the reference column, and no delivery date was inferred from the quantity line.
Share the development brief