ACMSO ACMS common mistakes
ACMSO ACMS · Understand the traps and how to avoid them.
Selecting a machining or forming process based on what the shop already owns rather than matching process capability to the part's material, geometry, and tolerance requirements.
Candidates anchor on familiar processes from their own background and skip the capability comparison the question is actually testing.
What to do instead
For every process-selection item, first extract the governing requirements (material, feature geometry, tolerance, surface finish, lot size), then eliminate processes whose inherent capability cannot meet each one before choosing among survivors.
Treating a design-for-manufacturability change as automatically acceptable because it lowers cost, without checking whether it violates a functional, fit, or interface requirement.
Cost pressure and habit make candidates equate 'cheaper and easier to make' with 'better design' and ignore the constraint the change may break.
What to do instead
Evaluate each proposed DFM change against the stated functional requirements and interfaces first; only endorse it if all requirements still hold, and note any requirement it compromises.
Reading a sampling plan or inspection result as if a zero-defects sample proves the lot is defect-free, or as if AQL is a target defect rate the process is allowed to produce.
Candidates conflate acceptance sampling with process control and misread AQL as a permitted quality level rather than a risk-tradeoff boundary.
What to do instead
State explicitly that acceptance sampling controls the risk of accepting bad lots, not the process defect rate; treat AQL as the quality level tied to a defined consumer/producer risk, and reserve defect-rate claims for process capability data.
Stacking tolerances by simple arithmetic addition (worst-case) when the question implies statistical assembly, or using root-sum-square when a guaranteed worst-case fit is required.
Candidates memorize one tolerance-stack method and apply it regardless of whether the item asks for guaranteed interchangeability or expected assembly yield.
What to do instead
Decide from the wording: use worst-case arithmetic when 100% interchangeability is required, and RSS only when statistical assembly and a stated defect risk are acceptable; label which assumption you applied.
Choosing a material by a single headline property (e.g., highest strength) while ignoring the secondary property the application actually depends on, such as corrosion resistance, machinability, or thermal expansion match.
Candidates latch onto the most prominent number in the scenario and treat material selection as a one-criterion optimization.
What to do instead
List the two or three properties the application truly constrains, screen candidates against all of them, and reject any material that fails a hard constraint even if it wins on the headline property.
Building a production schedule that loads work centers to 100% of available capacity with no allowance for setup, changeover, downtime, or scrap.
Candidates treat capacity as nameplate hours and forget that effective capacity is reduced by setups and unplanned downtime.
What to do instead
Compute effective capacity as available time minus planned setup/changeover and an explicit downtime allowance, and schedule against that figure rather than raw hours.
Prioritizing jobs purely by earliest due date without checking whether a higher-priority or short-setup job would free capacity and improve overall on-time delivery.
Candidates apply a single dispatching rule mechanically instead of evaluating the schedule against the actual objective (e.g., total tardiness or throughput).
What to do instead
Identify the stated scheduling objective first, then compare candidate sequences against it; use EDD only when minimizing maximum lateness is the explicit goal.
Assuming a hazard is controlled because a guard or procedure exists, without verifying the control matches the specific energy source or failure mode described.
Candidates pattern-match 'guard present' or 'training provided' to 'hazard resolved' and skip the hierarchy-of-controls reasoning.
What to do instead
For each hazard, identify the energy source and failure mode, then check that the cited control interrupts that specific path; prefer engineering controls over administrative ones and flag any gap.
Quoting a price from material and labor only, omitting burden, setup amortization, scrap/yield loss, and the overhead or margin the scenario specifies.
Candidates build a direct-cost estimate and stop, treating overhead and yield as implicit rather than computing them.
What to do instead
Structure every estimate as material (adjusted for yield/scrap) + labor (adjusted for efficiency) + setup amortized over lot size + burden/overhead + margin, and show each line so omissions are visible.
Applying a flat markup percentage to total cost when the question specifies margin on selling price, or confusing markup-on-cost with gross-margin-on-price.
The two formulas look similar and candidates substitute one for the other without checking which basis the scenario states.
What to do instead
Identify the basis explicitly: price = cost/(1 − margin) for margin on price, versus price = cost × (1 + markup) for markup on cost, and sanity-check that the resulting margin matches the stated figure.