# SAP Variant Configuration Readiness Assessment: Is Your Product Model Ready to Build? > Source: https://netray.co/tools/sap-variant-configuration-readiness-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Nine questions about product structure, rules, data ownership and testing give a readiness score and the priorities to fix before a VC build starts. ## Category sap ## Erp SAP S/4HANA ## Audience - SAP VC consultant - Product manager - ERP project lead ## Tool **Kind:** assessment **Questions:** #### How well are your product options and rules documented today? **Help:** Think of the document an engineer would use to answer what can be combined with what. **Options:** ##### Only in a few experts' heads **Score:** 0 ##### Scattered spreadsheets, partly out of date **Score:** 1 ##### One maintained document per product family **Score:** 2 ##### A complete rule catalogue reviewed by engineering **Score:** 3 #### Do you have a clean list of characteristics and allowed values? **Options:** ##### No, the same option has different names across teams **Score:** 0 ##### Partly, with known conflicts **Score:** 1 ##### Yes for most families **Score:** 2 ##### Yes, with naming standards and owners **Score:** 3 #### Is there a single super BOM structure or is each variant a separate BOM today? **Options:** ##### Every variant has its own BOM **Score:** 0 ##### A few families share a structure **Score:** 1 ##### Most families have a master structure on paper **Score:** 2 ##### A master structure with selection logic is already defined **Score:** 3 #### How many valid combinations does your largest product family have? **Options:** ##### We do not know **Score:** 0 ##### We estimate but have not checked **Score:** 1 ##### We have counted and know the invalid ones **Score:** 2 ##### We have counted and modelled constraints for them **Score:** 3 #### Who owns the product model after go-live? **Options:** ##### Nobody has been named **Score:** 0 ##### IT will handle it by default **Score:** 1 ##### Engineering owns it, informally **Score:** 2 ##### A named model owner with a change process **Score:** 3 #### How will you test configurations before go-live? **Options:** ##### Ad hoc, in the sales order **Score:** 0 ##### A short list of typical configurations **Score:** 1 ##### A test matrix covering rules and each option **Score:** 2 ##### A test matrix plus regression after every model change **Score:** 3 #### How do sales, pricing and BOM line up for configured items? **Options:** ##### Quoting is separate and manual **Score:** 0 ##### Some options are priced, some are not **Score:** 1 ##### Pricing follows characteristics for most options **Score:** 2 ##### Pricing, BOM and routing follow the same characteristics **Score:** 3 #### How do you handle engineering changes to configurable products? **Options:** ##### Changes are made directly with no history **Score:** 0 ##### Change notes are kept outside the system **Score:** 1 ##### Change numbers are used for BOMs only **Score:** 2 ##### Change numbers cover BOM, routing and dependencies **Score:** 3 #### Does the project team include someone who has built VC models before? **Options:** ##### No **Score:** 0 ##### Only through occasional external advice **Score:** 1 ##### One experienced consultant, no backup **Score:** 2 ##### Experienced lead plus trained internal owners **Score:** 3 **Bands:** #### Not ready to build **Min:** 0 **Max:** 34 **Verdict:** The product knowledge is not yet written down well enough to model. Starting now would turn the build into a discovery exercise. **Recommendations:** - Document options, rules and valid combinations for one family first - Standardise characteristic names and value lists - Name a model owner before any build work #### Foundations partly in place **Min:** 35 **Max:** 59 **Verdict:** There is enough to start a pilot on one family, but gaps in rules, testing or ownership will cause rework if the scope is wide. **Recommendations:** - Pilot one product family end to end - Count valid combinations and list constraints - Write a test matrix before building dependencies #### Ready for a controlled build **Min:** 60 **Max:** 79 **Verdict:** Your documentation and ownership are solid. Focus on testing discipline and change control to keep the model healthy. **Recommendations:** - Extend change numbers to dependencies and routings - Automate regression tests after model changes - Align pricing with characteristics #### Well prepared **Min:** 80 **Max:** 100 **Verdict:** You have the knowledge, ownership and testing approach a VC project needs. The main risks are scope creep and skill continuity. **Recommendations:** - Lock scope per release - Train backup model owners - Review model performance with real order volumes ## Content **Intro:** Variant configuration projects rarely fail on the SAP side. They fail because the product rules were never written down, nobody owns the model, or testing was an afterthought. This assessment scores those risks in nine questions. **Sections:** #### How to use the assessment **Body:** Answer each question for the product family you plan to configure first, not for the whole company. If different families differ, run the assessment once per family and compare. Each answer scores from zero to three, and the total is shown as a percentage band. The result lists the priorities for that band. It is meant for a project lead and an engineering lead to answer together, because the honest answers usually differ between IT and the product team. #### What the questions test **Body:** The questions follow the build in order. Rules and characteristics cover whether the model can be specified at all. Super BOM structure and combination counts show the size of the modelling job. Ownership and change handling determine whether the model survives after go-live. Testing and pricing alignment determine whether it works end to end. The last question looks at experience, because VC is a specialist skill where early design errors are costly to undo. None of the questions is about technology choice; the same readiness applies to classic and advanced variant configuration. **Bullets:** - Specification: rules and characteristics - Size: BOM structure and combinations - Lifecycle: ownership and change control - Quality: testing and pricing alignment #### Reading the result **Body:** A low score is not a verdict against the project; it tells you where to spend the first weeks. If you land in the lowest band, a requirements and rule-capture phase is cheaper than a failed build. In the middle band, a one-family pilot proves the approach and reveals gaps early. In the higher bands, the work is about discipline: keep the test matrix current, put every model change under a change number, and make sure a second person understands the model. Repeat the assessment after the pilot to see what changed. **Cta:** If the result shows gaps in rules, structure or testing, Netray can arrange an expert review of your product model before you build. **Faq:** #### Is this specific to classic SAP VC? **Answer:** No. The questions apply to any rules-based product configuration, including classic variant configuration, advanced variant configuration in S/4HANA and configure-price-quote tools. Readiness is about product knowledge and process, not about the specific module. #### What is a good score? **Answer:** A score of about 60 percent or more means the basics are in place for a controlled build. Below 35 percent, a documentation phase should come first. The bands are guidance, not a pass or fail grade. #### How long does variant configuration take to implement? **Answer:** It depends on the number of product families, the number of characteristics and the complexity of the rules. A single family pilot is commonly a matter of weeks to a few months, while a full portfolio can take much longer. Rule capture is often the slowest part. #### Who should answer the questions? **Answer:** Ideally the project lead, an engineer who knows the product rules and someone from sales or pricing. Answers from a single role tend to be optimistic. Compare scores between roles to see where the real gaps are. ## Search terms sap variant configuration readiness, sap vc project assessment, configurable product readiness, sap vc implementation checklist, variant configuration project risks, sap cpq vc readiness, product configuration maturity, sap vc scope assessment --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json