Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Baseline release of BOM

Baseline release of BOM

Baseline release of BOM


I am new to Configuration Management as well as this forum. I'm hoping you can help me with a basic question.

I have had several instances in my company where people want to change revisions on a part/drawing without changing the BOM it reports to. I now have a PM who is asking me to Baseline Release a top level BOM without releasing any of the reporting parts/documents/software/etc. He says we'll catch up with that later. Ugh!! I know this is not right however, he wants me to point him to a specification that says I can't do this. I've looked around but I don't have time to read books/standards. Can anyone point me to a specification (preferably a military spec) that says he needs to release "bottom up" as opposed to "top down"? Thanks in advance!

RE: Baseline release of BOM

Nope. Nothing states you can't. Just a lot of best practices and lessons learned say you shouldn't release top down.

I recommend that you have a release status in your BOM. That way, as you look through the top level BOM, you can quickly determine the components that are not yet released. Without this flag, it will be too easy to assume everything below it is released since that is, after all, best practice.

The best thing you can do is write your company's Configuration Management Plan and in it prevent releasing higher level components with unreleased constituents. Then you'll have something to point this PM to.


RE: Baseline release of BOM

On a program of any size there will be turbulence during development where one releases BOMs ahead of any drawings being created in order to create a manageable product structure. Even when you know the product structure cannot be correct, it's better to have it under control. Typical systems have reports that can be run against the CM database to verify the status all the way down. It's nice to do full bottom up, but it's not always possible and there will always be cases where lower levels will become unstable even if everything was released; for example a critical part cannot be obtained or a new method of fabrication is chosen. If the form/fit/function of the part isn't changed, the part number won't change and the BOM(s) it's called out on should not change.

The main problem would be if the PM is trying to hide the status of the job. In which case you wouldn't have a CM problem, you could have a politics problem.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members! Already a Member? Login


White Paper - How ESI is Helping Move New Medical Device Product to Market Quicker & More Cost Effic
Early Supplier Involvement has long been a strategy employed by manufacturers to produce innovative products. Now, it almost seems like a necessity. Because decisions made in the design phase can positively affect product quality and costs, this can help add value to OEM bottom lines. This white paper will discuss many facets of ESI, including why it’s so valuable today, what challenges limit the benefits of ESI, how cost is impacted, and more. Download Now
White Paper - Moving to a Driverless Future
This white paper describes what we see as the best practices to support a sustainable engineering process for autonomous vehicle design. It exposes how to use simulation and testing in common frameworks to enable design exploration, verification and validation for the development of autonomous cars at a system, software and full-vehicle level to drive a mature product development process for automated driving. Download Now
Research Report - How Engineers are Using Remote Access
Remote access enables engineers to work from anywhere provided they have an internet connection. We surveyed our audience of engineers, designers and product managers to learn how they use remote access within their organizations. We wanted to know which industries have adopted remote access, which software they are using, and what features matter most. Download Now

Close Box

Join Eng-Tips® Today!

Join your peers on the Internet's largest technical engineering professional community.
It's easy to join and it's free.

Here's Why Members Love Eng-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close