Customer Profile
People & Organization
- Cross department collaboration
- Dedicated administrator
- End users will be trained on the configured platform
Challenges
- Process specific admin and user training
- Controlled access to design data
- Track design changes and issues
- Formal design release process
Adoption Strategy
Customers with needs for formal processes are often larger organizations or strategic accounts and require sufficient testing, validation, and approval sometimes at multiple levels before making system changes. This along with the need for more configuration leads to much longer go live times. It is critical to be very detailed in upfront planning and agree upon outcomes. Taking a phased approach is often best practice. Creating Gannt charts with explicit milestones that everyone agrees to is a proven technique to ensure success. IFWE Communities are a great way document meeting minutes, configuration decisions, and progress updates. Recurring meetings should be set up with specialists from the reseller and admins to ensure progress and address questions. As Value Added Resellers the value you can add here is expertise and experience aligning industry needs with our products capabilities. It's important to remember that the customer doesn't know what they don't know so even though they might say things need to be done a certain way don't be afraid to challenge them with best practices reiterating your industry knowledge and referencing past successes or experiences. A formal custom built SOW must be created and signed by both you partner/reseller and the customer and referred to frequently to prevent scope creep.
Everything in the Cloud Storage and Lifecycle & Revision sections of the Outcome worksheet will need to be discussed as well as topics in the Manage & Control sections.
Data migration is an important topic to discuss with any existing SOLIDWORKS customer adopting 3DEXPERIENCE. Migration of customer data to 3DEXPERIENCE should be treated as a separate activity to user onboarding, and must be planned and costed accordingly. In order to plan successfully, a thorough discussion must take place between partner and customer to ensure that the right strategy is put in place, and the right expectations set with both parties before any migration activities are started.
The 3DEXPERIENCE Platform is not an archiving solution. Attempting to move every SOLIDWORKS design going back years will only serve to use up a customer’s platform storage allowance. Instead, it’s recommended that where possible only required content should be moved to 3DEXPERIENCE, for example current projects and component libraries.
Implementation & Onboarding
1. Kickoff
The kickoff meeting for Mid-Size to Large Enterprise customers should include all of the items from Scenario 1 & 2. The meetings will likely be more formal and have more attendees. Additional agenda topics should be added to discuss phased implementations and if agreed upon appropriate roadmap/rollout schedules prepared for each phase. Larger teams will often have Power Users who should be brought in early on and consulted with throughout the implementation process to gain insight into inefficiencies higher level positions may not be aware.
2. Admin Training
Admins should go through the standard training first but it will also require further training which can be be handled in the workshop sessions.
3. Admin Workshop & SOP Development
The Admin workshops will probably require multiple sessions over an extended period of time, weeks to months. Agenda items may include:
- Additional Training
- Platform Configuration
- Process Mapping Workshops
- Standard Operating Procedure (SOP) Development
- Because of the highly configured environment and need to minimize production down time, developing SOPs is most likely the best approach here. SOPs should be created for documenting processes at the business level including how and where our software solutions are involved. Also documenting all the tasks that users need to complete and creating step by step instructions will significantly improve the adoption rate.
4. Pilot Project
Every process, workflow, and configured functionality should be tested and validated before going live. A small team should be tasked in completing this to eliminate the possibility of admins unknowingly making assumptions.
5. SOP Documentation
Once all functionality and processes have been tested and validated Standard Operating Procedures should be formalized and published. Adding dates and revisions will assist in adoption of any future updates. WIKI Posts within a Swym community are a great place for storing any type of official documentation.
6. User Training
Users will benefit from going through the standard training but will also require separate sessions to cover any customization and become familiar with the prescribed Standard Operating Procedures.
7. Go Live
Ongoing Engagement
Mid-Size to Large Enterprises will thrive with a High-touch engagement strategy. The will often have individuals or teams with dedicated roles for improving processes and efficiencies. These people should be your best friends. They are typically very enthusiastic about improving and expanding the use of software solutions and after a few wins have the potential to become your best advocates. The largest opportunities here are expanding into new roles and/or other departments within the organization.
See below for an example roadmap illustrating the engagements you might have with a high touch customer. Remember, this is just an example and should always be modified to suit both your customers needs and your internal strategies. Other reasons for meeting/types of engagement are displayed in the second image.
| High Touch | ||
|---|---|---|
| ||
Feedback
Was this page useful?
Hit the Like Button or let us know what we can improve in the comments section below.
