Customer Profile
People & Organization
Challenges
- Desire to standardize on Revision and Naming Schemes.
- Need to manage design variations and progressions as well as understand the active status of every item.
- Occasionally Collaborate with External Stakeholders.
- No Formal Approval Processes or Data Migration requirements.
Adoption Strategy
Customers that land around this scenario you are likely the most familiar with as they are your typical SOLIDWORKS Customer using PDM Standard/Basic Pro with a quick start implementation. They will typically have more organizational hierarchy than those only requiring basic cloud storage therefore should have defined platform admins who are the only ones allowed to make platform configuration changes. Most will have minimal to no official documented design to release guides which makes them the perfect candidate for a Pre-configured Implementation. Our recommendation is to work out your own "flavors" of quick starts that both your sales and technical staff becomes very familiar with and can be sold, deployed, and supported with minimal effort. It is important to understand data flow throughout each organization and make sure processes are defined to share design information needed with purchasing, manufacturing, etc. System and process changes likely won't have to go through an extensive validation/approval process so starting simple and expanding is a best practice here. An appropriate engagement strategy should be agreed upon that encourages future growth. Some customers may be familiar with PDM workflows and desire to have multiple workflows that relate to different approval processes. This is possible on the 3DEXPERIENCE platform with Routes and Change Actions but those require further training and configuration so it's important to categorize the customer appropriately. An official Statement of Work (SOW) should be created and signed by every customer. Since most of the customers in this scenario will be similar a boiler plate SOW may be able to be developed and re-used.
Everything in the Cloud Storage section of the Outcome worksheet will need to be discussed as well as topics in the Revision & Lifecycle sections.
Implementation & Onboarding
1. Kickoff
This kickoff meeting is setup to review desired outcomes and fill in any gaps that may have not been addressed. It's also a time to make sure that admins are identified. At least two admins is recommended, ideally from different departments to ensure the platform is configuration accounts for every ones needs. A roadmap and timeline should be discussed and documented as well as milestones set and commitment from both parties to hit targets and maintain an open line of communication if anything comes up.
2. Admin Training
There will be platform configuration requirements, so it's recommended that the admins go through training first to obtain fundamental knowledge of platform features and functionality before scheduling any workshop sessions.
3. Admin Workshop
Workshops are 1 on 1 or small group consulting sessions. They are great opportunities to review outcomes, get users/groups set up and roles assigned, configure collaborative spaces and walk through how users will complete their assigned tasks in the new system. If possible, and time permits, this is also a great time to review any platform concepts that may not be clear to admins and enforce your role as a trusted advisor. A Pilot Project should also identified and completed before going live to validate workflows and platform configurations.
4. User Training
In addition to the single day add on user training, tailored training may be required to address any customer specific configuration and/or specific working practices.
5. Go Live
Ongoing Engagement
This customer is a perfect fit for Mid-Touch Engagement strategy. Monthly/quarterly status reviews will prove valuable. The Pre-Configured Implementation leaves a lot of room for expansion into formal process management which is the natural next step. IFWE Experience Communities also might make sense. Express the value of having a private community where they can ask questions, develop a specialized knowledge base, and document Standard Operating Procedures with representatives from you (reseller) and technical employees at Dassault Systemes.
See below for an example roadmap illustrating the engagements you might have with a medium 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.
| Medium Touch | ||
|---|---|---|
| ||
Feedback
Was this page useful?
Hit the Like Button or let us know what we can improve in the comments section below.
