Descriptive standardization of materials in practice

The material master is where data governance meets its toughest test. There are many items, many areas involved, technical vocabulary specific to each family, and constant pressure to release the purchase.

The descriptive standard is the central tool. And the standard that works has one trait that manuals tend to forget: the operation can follow it under pressure.

The structure that holds it up

The structured description always follows the same order: noun, modifier, attributes, and nothing else.

The noun names what the thing is, in the singular and without a brand: SCREW, BEARING, CABLE. The modifier narrows the type: HEXAGONAL, RIGID, FLEXIBLE. The attributes carry the characteristics that tell one item from another within the same type, always in the same sequence and with the same unit.

SCREW HEXAGONAL; STAINLESS STEEL 304; M8; 40MM is readable, sortable, and comparable. "Stainless screw 8x40 hex" is none of the three.

Rules that prevent most of the rework

• One unit of measure per attribute, defined in the family dictionary. Millimeter or inch, never both.
• Leading zeros prohibited, decimal places fixed. 8MM and 08MM cannot coexist.
• Abbreviations only from a closed list. Free abbreviation is the main generator of duplicates.
• Brand and supplier code stay out of the description. They go in their own field, because the item remains the same when you change supplier.
• No characters that carry invisible meaning: inconsistent accents, inch quote marks, double spaces.

The dictionary by family

The global standard defines the structure; the dictionary by family defines the required attributes and their order. A bearing has inner diameter, outer diameter, width, and seal type. A cable has cross-section, number of conductors, insulation, and voltage.

Without a dictionary by family, the standard becomes interpretation, and two well-intentioned people produce different descriptions for the same item.

Start with the three families of highest volume or highest spend. A complete dictionary for everything is a project that never ends.

Migrating the existing database

Don't rewrite everything. Prioritize by activity: items purchased in the last year first.

Work by family, not by code order, so the person stays in the same vocabulary for the whole batch: context switching is where errors creep in.

Keep the old description in its own field. Someone will search for the old text, and for a long time.

What makes the standard stick

Validation at record creation, not auditing afterward. If the system accepts what is out of standard and someone fixes it the following week, the standard is a suggestion.

Example before rule. One page with ten correct descriptions teaches faster than forty pages of policy.

And a person with the authority to reject. Without that, the first urgent request opens the exception that becomes the rule.