VYRCOWho it is for and what is included
Engineering, mold shop, quality and document-control personnel.
Level: Intermediate. Includes instructions, recording fields, a fictional example and reference sources.
How to use it
- Identify request, requester and current configuration. Describe the problem separately from the proposed change; attach references.
- List affected components, documents, batches, spare parts and teams. Record impacts awaiting review, including interfaces, inspection and training.
- Document the decision, authority and conditions before implementation. A registered request is not an approval.
- Record what was implemented, by whom, when and at which revision or batch it becomes effective. Preserve links to previous versions and withdrawn documents.
- Verify against previously agreed criteria. Record results, evidence, open items and follow-up before closing the change.
Fictional example
FICTIONAL: EC-DEMO-11 requests connection identification changes from revision B to C. Drawing, inventory and workstation copy need updating. The proposal is approved, but verification of installed labels is pending; the change stays open.
Scope and limitations
Does not authorize modifications by itself or replace design validation, risk assessment, customer requirements or applicable contractual approval.
Sources consulted
- NASA · Configuration Management
Principles for identifying, reviewing and verifying changes. VYRCO formats are original, not NASA forms.
Editorial review: 2026-10-10 · Original forms and general guidance. Always apply the drawing, manual and authorized procedure for your case.