# Job Shop ERP Go-Live Readiness Assessment > Source: https://netray.co/tools/job-shop-erp-go-live-readiness-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Nine questions to score whether your data, people and cutover plan are ready for an ERP go-live. ## Category erp-migration ## Industry Job Shop Manufacturing ## Audience - Shop owner - Project manager - ERP administrator ## Tool **Kind:** assessment **Questions:** #### How clean is the part, routing and customer data you plan to load? **Options:** ##### Not reviewed yet **Score:** 0 ##### Reviewed but known problems remain **Score:** 1 ##### Cleaned and validated in a test load **Score:** 2 ##### Cleaned, validated and signed off by data owners **Score:** 3 #### Have you run a trial import into a test environment? **Options:** ##### No **Score:** 0 ##### One partial trial **Score:** 1 ##### Full trial with errors still open **Score:** 2 ##### Full trial reconciled with no open errors **Score:** 3 #### Is there a named internal project owner with time set aside? **Options:** ##### No named owner **Score:** 0 ##### Named, but on top of a full-time job **Score:** 1 ##### Named with part of the week protected **Score:** 2 ##### Named with a backup and protected time **Score:** 3 #### How much training have the office users completed? **Options:** ##### None **Score:** 0 ##### Vendor overview only **Score:** 1 ##### Role-based training done **Score:** 2 ##### Role-based training and practice on real jobs **Score:** 3 #### How ready are shop floor operators to use data collection? **Options:** ##### Not discussed with them **Score:** 0 ##### Informed but not trained **Score:** 1 ##### Trained on terminals or tablets **Score:** 2 ##### Trained and piloted on one work center **Score:** 3 #### Is the cutover plan written, including open jobs and open orders? **Options:** ##### No plan **Score:** 0 ##### Verbal plan **Score:** 1 ##### Written plan without rehearsal **Score:** 2 ##### Written plan with a rehearsal **Score:** 3 #### Have accounting integration and opening balances been tested? **Options:** ##### Not tested **Score:** 0 ##### Planned only **Score:** 1 ##### Tested in the sandbox **Score:** 2 ##### Tested and reconciled with the accountant **Score:** 3 #### Do you have a fallback plan if go-live fails in the first two weeks? **Options:** ##### No **Score:** 0 ##### Informal idea **Score:** 1 ##### Documented fallback **Score:** 2 ##### Documented fallback with a decision point and owner **Score:** 3 #### Is the go-live date set around your busiest delivery period? **Options:** ##### Date chosen during peak shipping **Score:** 0 ##### Date chosen without checking workload **Score:** 1 ##### Date chosen in a quieter period **Score:** 2 ##### Date chosen with reduced load and extra support scheduled **Score:** 3 **Bands:** #### Not ready **Min:** 0 **Max:** 39 **Verdict:** Major gaps in data, people or planning mean a go-live now would likely disrupt shipping. **Recommendations:** - Assign a project owner with protected time - Start data cleanup and run a first trial import - Delay the go-live date until the basics are done #### Partly ready **Min:** 40 **Max:** 64 **Verdict:** Some foundations exist but several areas could cause a painful first month. **Recommendations:** - Close the lowest-scoring areas first, usually data and training - Run a full trial import and reconcile it - Write the cutover plan and rehearse it #### Nearly ready **Min:** 65 **Max:** 84 **Verdict:** You are close. Remaining gaps are manageable with focused effort before the date. **Recommendations:** - Rehearse cutover end to end including open jobs - Pilot shop floor collection on one work center - Document the fallback decision point #### Ready **Min:** 85 **Max:** 100 **Verdict:** Data, people and plan are in good shape. Focus on execution and support in the first weeks. **Recommendations:** - Schedule extra support for the first two weeks - Track daily issues and decide fixes fast - Review KPIs weekly in the first month ## Content **Intro:** Most failed job shop ERP go-lives were predictable: unclean data, an overloaded project owner or no cutover plan. This assessment scores those areas in a few minutes. **Sections:** #### How to use the assessment **Body:** Answer each question honestly, ideally with the project owner and the office lead together. The score is a percentage of the maximum, and the band tells you what to fix first. Retake it every two weeks as the project proceeds and aim to bring the lowest areas up before the go-live date is locked. **Bullets:** - Score as a team, not alone - Lock the go-live date only after a score above 65 - Retake after each milestone #### What the questions cover **Body:** Data readiness, trial imports and accounting tests address technical risk. Project ownership, training and operator readiness address people risk. The cutover plan, fallback and date choice address timing risk. Weakness in any one area can overturn strength elsewhere. #### Common mistakes **Body:** Treating go-live as an IT event instead of a shop-wide change is the most common one. Teams also skip rehearsals, assume operators will adapt on the day, and schedule go-live in a month with heavy shipments. **Cta:** If your score shows gaps, Netray can review your data and cutover plan, and help set up read-only reporting so you can see problems early. **Faq:** #### What score should I aim for before go-live? **Answer:** A score above 65 percent is a reasonable minimum, and above 85 percent is better. Any answer of zero on data, cutover or fallback should be fixed before you proceed. #### How long before go-live should I take this? **Answer:** Take it about two months before the planned date, then every two weeks. That leaves time to fix gaps without moving the date. #### Do small shops need a full cutover rehearsal? **Answer:** Yes, in a smaller form. Load a copy of data into the sandbox and process a sample of open jobs from quote to invoice. It finds issues cheaply. #### Should we run old and new systems in parallel? **Answer:** Short parallel runs on a subset of jobs can build confidence, but full parallel entry doubles workload and often tires the team. Define the end date for the old system in advance. ## Search terms ERP go live readiness, ERP implementation readiness checklist, job shop ERP implementation, ERP cutover plan small manufacturer, ERP go live checklist, machine shop ERP rollout --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json