Many of the Assemblies module reports print details for a range of assemblies. This allows you to limit the amount of information listed. You should be careful when selecting the ranges for reports, as assembly explosions can be lengthy. Note that to start from the beginning of a range the word FIRST should be entered as the ‘from’ value. To go to the end of a range enter the word LAST as the ‘to’ value.
The Reports In Detail
An assembly explosion report lists the component items for a given range of assemblies. This explosion can be at top level only, or the assemblies can be exploded down through all levels. The report shows whether each component is purchased, a phantom, and its issue type. A graphical indication of the level of any sub-assemblies is given. This report is useful for checking and reference purposes. The report can be exported as a CSV file or Excel spreadsheet:
Note the option to "save co-ordinates as an Excel file" will create a file of co-ordinate information for use in PCB assembly. For example, an assembly line with a reference of C1,2,6-8,D4,E4 would be exported as:
C1
C2
C6
C7
C8
D4
E4
A where used report will list the assemblies in which an partnumber or a range of partnumbers appear. This report is useful for determining the effect of changing a component item:
An assembly file details report lists the details for a range of assemblies and is useful for reference and checking purposes:
If an assembly occurs somewhere in its own assembly (due to a mistake during entry) then when Herschel tries to explode through the layers of the assembly it will keep exploding to a lower level each time. A structure like this is known as a “looped” assembly. The assembly loop check report checks all the assemblies on file for looped structures. Note that a looped structure will not cause your computer to crash or hang - Herschel will stop exploding once it reaches fifteen levels of sub-assemblies. However, as a looped structure could be exploded into a large number of component items it is wise to run this report periodically, especially if you are using the Plan module:
The assemblies not OK to make report is a useful list of those assemblies that still require approval before they can be manufactured:
The obsolete assemblies report is a list of those assemblies that are marked as obsolete:
The roll up costs reports can list a complete breakdown of how rolled up costs are calculated (detailed), or a summary of costs only (summary), for a range of assemblies. These reports are ideal for checking and reference purposes. The newly calculated costs can overwrite the existing costs if required. Scrap can be included if required and tooling items may be excluded from the roll ups:
The transfer route costs into assemblies report works in the same way as the transfer route costs option - except it will calculate the route costs for a given range of assemblies at once:
If you are using the Shop module you may have a manufacturing route on file for your assemblies. If so it is possible to calculate automatically the overhead and labour costs of producing a range of assemblies by running the transfer route costs into assemblies report. This can save you a lot of work. The details of each assembly contain the routing number to transfer and the assumed typical batch size that Herschel will use when doing its calculations:
Once the rolled-up costs have been checked they can be transferred to the stock file in the Store module by running the transfer assembly costs to stock file report. The standard, average or latest cost can be updated:
