Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
The structure and procedures for implementing a revision and version control system for documents and parts in a production environment. It covers the roles and responsibilities of different teams, definitions, and guidelines for revision levels, interchangeability rules, and renumbering rules.
What you will learn
Typology: Lecture notes
1 / 4
This page cannot be seen from the preview
Don't miss anything!
Revision History Rev Description Originator ECO Updated Date
1.0 Purpose
Define the structure of the revision and version level control system. Specify rules to track changes of parts and documents. Specify methods of assignment and control.
2.0 Scope
This document applies to all documents, components, assemblies, and materials required in the production, testing, shipment, and support of all documentation controlled products.
3.0 Owner
3.1 This document is owned and maintained by Components Engineering who will be responsible for assuring that this document is adhered to. Documentation Control Services will be responsible for permanent archives.
3.0 Definitions
3.1 CCB - Configuration Control Board.
3.2 Change Owner - Engineering or Project manager responsible for originating and assuring the technical integrity of the change.
3.3 F/F/F - Form/Fit/Function.
3.4 Revision Level - Used to identify current level of and track changes to documentation.
3.5 Version Level - Used to identify current level of and track changes to components and assemblies.
3.6 Active - Current revision.
3.7 Inactive - Previous revisions.
4.0 Responsibility
4.1 Components and Engineering and Engineering Services with responsibilities for Documentation Control will assign and track revision and version levels of released documents and parts.
4.2 Components Engineering and Engineering Services will maintain this document. CE will be responsible for part level revisions and Documentation Engineering Services for assembly level changes.
4.3 Change Owner, supported by other functional members of the product team, shall make decisions on interchangeability and renumbering involving legal, safety, and obsolete part control requirements.
4.4 Change Owner shall make recommendations to CCB for renumbering efforts involving business requirements.
If there is F/F/F impact or some other reason for distinguishing the existing version from the new, a new part number must be assigned. A new part number, at minimum, will include advancement of the version number and may require as much as the assignment of a new base number as required to maintain configuration management.
5.5 Renumbering Rules
5.5.1 Part number changes are not required for vendor changes to standard commercially available component parts or to revise documentation to reflect the “as-built” part. Revision levels shall be used to track the above conditions.
5.5.2 When renumbering, a component or assemblies next higher assembly shall be considered for renumbering based on F/F/F or interchangeability guidelines. The next assemblies shall continue to be considered for possible renumbering until a document revision level only revision decision is made.
5.5.3 All modifications to a PCB FAB (changes to artwork, layout, etc.), shall be identified as such by the assignment of a new version number and the revision level shall revert back to Rev. A.
5.5.4 On PCB assembly parts, if an assembly is modified by additions of jumpers, cutting of traces, removal or addition of components, component value changes, etc., the version and revision shall advance while the base number of the board shall remain unchanged.
If the PCB board changes (FAB), a new board part number shall be used designated by the last three digits advancing by “1”. Hence 021-00022-001 REV A moves to 021-00022-002 Rev. A
5.5.5 Changes to custom parts and assemblies shall be tracked by advancement of version number and revision level. When revising parts and assemblies to an extent that a new product is created, a new base number must be used along with a Rev. A assignment. See section 5.5.4.
*Note to fellow Components Engineers
Each company has their own revision control philosophy. Yours is no different. Some companies use a two digit revision control. If the Bill of Materials or Schematic changes but the PCB board does not, then there is no need to bump a revision level on the PCB. One way to control this is to say that the BOM/Schematic is designated with an Alpha character, while the PCB is a numerical character. So A1 would be the first version of the BOM and the first version of the PCB. B1 would designate a BOM change without a PCB change etc. It is important to remember that the top level or subassembly has to bump a revision level in order to track lower level changes. Also, some company’s use a technique for revision level control by which an unreleased product can be distinguished from a released product. So instead of A1 being a released product indicating BOM 1 and PCB 1, the digits are transposed to show the numerical in front of the Alpha. Hence, a document with 1A indicates the product is unreleased and the PCB is at REV 1 while the BOM is at its first revision as well. If a factory person sees 1A, or 2A etc. on a document, they will know immediately that the product has not been released to manufacturing.
Douglas
