When it comes to adding, administering, sustaining, documenting the changes around an assembly's router (or traveler). Is this, or is this not part of the Configuration Management Departments job to document this activity and speak to it? Seems to me that they would want to be able to control how router steps get changed and could potentially affect the product. Making sure the configuration release process includes not just the material configuration documented, but also the router steps configuration documented under CM control at the time of release? Meaning that for any given BOM material configuration baseline for a "Make" in-house assembly, also has its own independent Router Revision configuration that speaks to the major milestones of the build, in association to the BOM material configuration baseline.
Making so, from there on, any changes are managed by CM department when the major milestones of the build or steps of the build are changed. I have a CM department trying to convince me that they do not only manage, make not e, or do any of the router changes, they also do not associate themselves or notate the request for the router to get loaded at the around same time as CM loads the BOM, on new assemblies. This leaves a gap in our process if CM does not own this configuration sustainability. What are your thoughts, is Router process configuration something with its own revision, needing to be tracked by CM since it is directly related to the configuration to the parts on the BOM?
The decision of whether a router is included in the configuration management of a product is taken by the company per the customer and legal requirements for the product. As this document is often the instructions on how to assemble and test a product it is often considered to be part of the configuration listing for the final product that is shipped, and also often maintained by the configuration management department. However, this requirement is not necessarily the case for every customer or company that creates parts for aerospace. If you perceive a gap in your system then I suggest you refer to the customer requirements for configuration management and reporting to ensure that there is no specific requirement from them as to how this is done and reported.
For more information on what is included in AS9100 Rev D see this whitepaper, “Clause-by-clause explanation of AS9100 Rev D”, https://info.advisera.com/9100academy/free-download/clause-by-clause-explanation-of-as9100-rev-d