
Inspect a support note, an assessment scope and a migration reconciliation.
Findings, scopes, reports and handover notes are written down. These synthetic examples show the format and the level of detail before you get in touch.
Four habits behind every engagement
Measure before changing
Timings, logs and reproducible steps come before recommendations, so decisions rest on facts.
Standard before custom
If the current release can do it without code, we'll recommend that, even when custom work would be more billable.
Agreed access only
We work through access methods your IT team approves, and keep notes where you tell us to.
Knowledge stays with you
Every piece of work ends with notes your administrators can use without us.
Findings note after a free support session
What you receive after the first session on a specific issue: what we looked at, what we found, and what to do next, in one or two pages.
Top-level CATIA V5 product slow to open at one site
- Issue
- Top-level CATProduct (about 410 unique references, 3,200 instances, 7 levels) takes around 20 minutes to open for all users at site B. Site A opens it in under 5 minutes.
- Conditions
- CATIA V5 [release / SP / HF]; dataset [ID]; same workstation model at both sites. Configured CGR cache path at site B: a network share. Tests used a separate local test cache directory: “empty” = new directory before CATIA start; “populated” = same directory after CGRs were generated, CATIA restarted between runs.
- Observed
-
Test (site B) Time Design Mode, configured (network) cache 19 min 40 s CGR Visualisation Mode, local test cache empty 6 min 10 s CGR Visualisation Mode, local test cache populated 2 min 05 s - Hypotheses
- Every reference opened in Design Mode by default (CATSettings), although designers edit only a few.
- The configured cache at site B is on a network share (Cache Management). Not yet isolated from operating-system file caching.
- Three purchased parts carry detail that isn't needed at product level.
- Next tests
- Point the configured cache to local disk at site B and repeat both CGR tests, to isolate the cache location.
- Trial Visualisation Mode as the default for this product, with Design Mode on demand.
- Replace the three purchased parts with lighter representations, re-measure.
Synthetic example written to show the report format. Not customer data and not a measured result.
What a paid Essentials assessment contains
When an issue or project needs more than a first session, the Essentials assessment turns it into a scope you can approve or take elsewhere. You approve its fee before it starts.
- Problem statementWhat is happening, who it affects and why it matters, in plain language.
- Current stateRelease, deployment, relevant configuration and customisations, and integrations.
- FindingsEvidence gathered, with causes ranked by impact.
- OptionsTwo or three ways forward, with pros, cons and risks.
- Recommended scopeWhat's in, what's out, assumptions and dependencies.
- Effort estimateEffort by work package, and what would change the estimate.
- Next stepsDecisions needed from you, and a suggested start.
Reconciliation after a trial migration
After every trial run we compare source and target, explain every difference and decide whether the cut-over can go ahead. Nothing is lost quietly.
| Object (reconciliation rule) | Source | Target | Diff | Status |
|---|---|---|---|---|
| References: identity + revision | 12,480 | 12,480 | 0 | Matched |
| Instances: identity, parent and child references, placement | 41,236 | 41,236 | 0 | Matched |
| Drawing documents: identity + revision | 8,912 | 8,905 | −7 | Rejected, owned |
| Drawing links: relationship and endpoints | 8,912 | 8,905 | −7 | Follows the 7 above |
| Released revisions | 15,604 | 15,604 | 0 | Matched |
Exceptions: product structure reconciled separately from documents. 7 drawing documents rejected by the loader's validation; their 7 links to products were therefore not created. Each rejected source ID, intended target type and the exact validation message are listed in the exception log.
Action: mapping rule changed, owner assigned, the 7 records re-run in trial load 3. Decision: trial load 3 goes ahead; cut-over is not approved while any exception is open.
Synthetic example written to show the report format. Not customer data and not a measured result.
Weekly status update for a partner's project lead
When we work inside a Dassault Systèmes partner's project, the project lead gets a short written update every week, in their template if they have one.
- Done
- Change Action maturity and approval Route configured in test; 14 of 16 test scripts passed, including refused-promote cases.
- Next
- Fix the 2 failing Route scripts (rejected approval returns to the wrong state); start the collaborative-space access tests.
- Risks
- Customer test users not yet created in 3DPassport, which blocks security-context testing from Thursday.
- Decisions needed
- Confirm whether the quality approval applies to all part types.
- Time
- Recorded against your project codes, as agreed.
About how we work
Are these real customer documents?
No. They're synthetic examples written for this page, so you can judge the format and depth of our written work before you contact us. The figures are illustrative, not test results.
How much access do you need to our systems?
As little as the work requires. We agree the access method with your IT team: screen sharing or a test environment first, and production access only when it's needed and approved.
Where are findings and project notes stored?
Where you choose. Usually in your own document system or ticketing tool, so the knowledge stays with your team.
Describe the failed operation, release and deployment.
Describe it in a few lines. If it's a good fit, we'll use up to 5 hours of free support to understand it and tell you plainly what to check or do next.