ERP SELECTION INSIGHT AND BEST PRACTICES

A route-based specialty distributor outgrew its systems, selected Acumatica, and ran a business-transformation program with John Hannan LLC leading cutover and change workstreams to go-live.

The last step of an ERP selection: an independent check of scope, data, integrations and go-live criteria before you sign the contract and SOW.

Most stalled ERP programs are recovered, not restarted. What the first sixty days of a reset look like, from the inside of a national distributor's Dynamics 365 program.

When a partner-led Dynamics 365 program fell behind, a national distributor brought in an independent leader to reset methodology, plan and governance. Here is how it went.

Most ERP implementation problems start during software selection. The ten selection risks leaders should never ignore, from weak requirements to sales-led demos and hidden costs.

Project mobilization is the phase between contract signing and execution where ERP outcomes are decided. This guide breaks down the mobilization actions that reduce go-live risk across program governance, data migration, testing, cutover, hypercare, and change adoption, plus a practical checklist to keep teams aligned and accountable.

Learn how to validate an ERP system for FDA 21 CFR Part 11 and GxP without bloating scope. This guide shows a risk‑based path through IQ/OQ/PQ, the exact Part 11 controls to prove (e‑signatures, audit trails, timeouts, lockouts), and the evidence auditors expect for backup and restore. Includes concise test snippets you can copy. A checklist, risk traceability matrix and test-case template are available on request.

ERP projects rarely fail because the software doesn’t work—they fail because no one owns the whole picture. When multiple vendors, ISVs, and integration partners are involved, coordination gaps multiply. An outsourced internal ERP project manager acts as the owner’s representative, bridging systems, timelines, and decisions across teams. This post explores why neutrality, structure, and focus often make the difference between drift and delivery.

Radiopharmaceutical therapy manufacturers must track radioactive material (RAM) possession in real time—by nuclide, form, location, and time—to stay within NRC/Agreement State license limits. This post shows where generic ERP fails, what purpose-built RAM tracking must do (decay math, location gates, Part 37 aggregation, 10 CFR 30.51 records), and how to evaluate software and partners.

RPT manufacturers often need both ERP and MES. This post shows how to split responsibilities—put batch truth and eBR in MES, and commercial/financial truth in ERP—then wire them with event‑based, validated integrations. Learn the boundary for labels, QA release, RAM license gates, and waste; how to avoid double entry and time‑of‑calibration drift; and what to demand in scenario‑based demos. Scale dose‑to‑door without audit risk.

ERP touches the core of the business. When stakeholder input is too narrow, companies often select systems based on polished demonstrations, executive preference, vendor familiarity, or incomplete requirements.

The Drug Supply Chain Security Act (DSCSA) is pushing the industry toward an interoperable, electronic way to identify and trace certain prescription drugs at the package level as they move through the supply chain.

21 CFR Part 11 must provide complete documentation of process controls, record and data integrity safeguards, accuracy assurances, and user authentication and authorization processes.

Validation is proving that a system meets the intended purpose it was designed for by confirming that the system works properly. Validating an ERP system involves testing and validating its various components, including security controls, configuration settings, processes, functions, and reports.

ERP implementations run late for predictable reasons: change management, unrealistic estimates, weak governance, bad data and thin resources. Here is how to avoid each one, and why most of them are set during selection.

Metal service centers strain mainstream ERP in predictable places: fluctuating material prices, theoretical vs. actual weight, cut remnants and multi-stop deliveries. What to test before you choose.

Recall readiness is not a single feature. It is the ability to detect an issue, contain it quickly, and prove what happened with an audit ready trail.

Before replacing your ERP, determine whether the real problem is the software, implementation partner, business processes, data, or user adoption. An independent ERP assessment can clarify whether optimization, a partner change, or a new ERP selection is the right move.

A CRO sells a service, not a product, so its ERP needs differ: project accounting, milestone invoicing, prepayments and deferred revenue, and time tracking.