Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Effective date filter for ProjectBOM should ignore End items
Effective date filter for ProjectBOM should ignore End items and dont filter them out based on their creation dates. Right now, if the end item was created after the Effective date (assigned in Project settings), it does not display any of those items under the ProjectBOM for the Effective date filter.
could you please give us a use case or example when end item creation date would be past the projects effective date? What would be the reason for end item to be created past effective date that was assigned to the project? To take this end item in effective date filter, a responsible user (a PM of a project) would need to update the project date to some later date. Is there a reason why this would not be a desired behaviour?
Our projects take several months from start (design start) to completion (ship to customer). Because of the nature of our business, Engineering changes can occur up until the end of the project . The intent of Effective Date is not to be set to the ship date of the project, but to set it at the time most of the design is issued to production, which is roughly 1/3 of the time into the project duration. This allows for automatically incorporating the latest revisions up until that time of the bulk of the release, but any revisions after that date needs user action to incorporate them into that particular machine build. Although not common, is it very possible for end items (electrical packages in particular) to be added to the machine after that date.
The biggest risk is that if we set the default filter to effective date, significant pieces of the design may be not shown and they have no indicator they are missing information.
Even if the use case is "User set the Effective date incorrectly", if the default filter is set to Effective Date, it would be a high impact error that could be hard to detect.
Their is also the use case of Retrofit projects where we open up a new project with new end items but would set the effective date to the historical projects effective date (because we are not going to refit the entire machine with latest revisions, but would need the effective revision levels to match what is on the physical machine)
