# Engineering modernization introduction email | SourceX

Canonical: https://refer.sourcex.si/resources/engineering-system-modernization-introduction-email
Last updated: 2026-11-05

Yes, often, and that is what the email tells the owner: since a given year, each released engineering change carries an effectivity date or serial range that the ERP uses to separate production orders built before and after it, and the modernization plan may break that bridge. Send three short paragraphs to the person who can authorize a review, disclose your referral interest, and ask only for a description. The draft and notes on every paragraph follow.

This draft is part of the [introduction email worksheet](/resources/a-reusable-worksheet-for-introduction-email-preparation). It follows the [engineering system modernization meeting agenda](/resources/engineering-system-modernization-meeting-agenda); the [moment guide for PLM partners](/guides/moment-engineering-system-modernization-plm-partners) explains how the question arises during a migration.

## The draft

Illustrative. Fill the braces from your meeting notes and the owner's team. Keep it under 200 words and plain enough for a reader who has never opened the PLM.

> Subject: {company}'s change history before {legacy_plm} is retired in {retirement_month}
>
> Hi {owner_first_name},
>
> When we scoped the migration, {plm_admin} and {erp_lead} confirmed that every released engineering change since {first_year} carries an effectivity {date_or_serial} that the ERP uses to tell orders built before a change from orders built after it. The new system will import current revisions only, so that link between design changes and real production would stay in the legacy system when it is switched off.
>
> If that history is worth a conversation, SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. You decide what is in scope, and nothing moves without a signed agreement. I should say plainly that I am a SourceX referral partner and may receive a reward from SourceX if a qualifying license completes; SourceX pays it separately, it never reduces what {company} would receive, and it has nothing to do with our migration fees.
>
> SourceX would begin with a description only: years covered, roughly how many changes, which systems hold them and who can approve. Reply "yes" for an introduction, or "not now" and I will leave it.
>
> {your_name}

## Paragraph-by-paragraph notes

**Subject line.** It names the company, the system and the retirement month, because that is the only real deadline. Leave out "opportunity", any figure and the word "data monetization"; an engineering leader will file that as spam.

**Paragraph one, first sentence.** It credits two people, the PLM admin and the ERP lead, because the bridge has two ends and neither can vouch for the other. It states the year and the effectivity type, nothing more. Never add a change number, part number, customer program or plant name, even as an example.

**Paragraph one, second sentence.** It explains why the decision has a date: the new PLM imports current revisions, so closed changes and their effectivity stay behind. Say what the plan does, not who chose it. If closed changes are being archived, say where instead.

**Paragraph two, first two sentences.** One accurate description of SourceX and one line on control. Do not name buyers or AI labs, and do not claim demand for engineering history in general.

**Paragraph two, disclosure.** The FTC's guidance on its Endorsement Guides says a payment or commission should be disclosed clearly and conspicuously, and that vague labels do not meet that bar. So the email names SourceX as the payer, says when a reward might arise and separates it from migration fees. Do not quote a figure here.

**Paragraph three.** The ask is a description: years, rough counts, systems and an approver. It gives a one-word way to decline. Never ask for an export, a BOM report, CAD files or a test login.

## A glossary for the reader who is not an engineer

The owner may forward the email to the CFO or another executive. If they ask what the words mean, these one-line answers are consistent with vendor documentation.

| Term in the email | Plain meaning | Vendor wording it rests on |
| --- | --- | --- |
| Engineering change | An approved change to a part, assembly or bill of materials | Windchill runs change requests, change notices and change tasks |
| Effectivity | The date, lot or serial number from which the new version is used in production | PTC defines effectivity as the planned date, lot or serial number at which old versions are replaced with new ones; planned effectivity becomes actual when the change notice is approved |
| Valid-from date | The date a change takes effect for everything assigned to it | SAP: a change number's valid-from date sets when the change takes effect for all objects allocated to it |
| Before and after states | The old and new bill of materials kept side by side | SAP stores a BOM changed with a change number in a pre-change state ending at the valid-from date and a post-change state starting there |
| Version stamped on transactions | Each order records which design version it used | Microsoft Dynamics 365 can stamp the engineering version on each transaction when version tracking is on |

The [engineering change order process](/data-types/engineering-change-order-process) explains the records in more depth.

## Checks before you press send

- [ ] The PLM admin confirmed the first year of released changes with effectivity.
- [ ] The ERP lead confirmed orders can be told apart by effectivity, version or serial range.
- [ ] The migration lead confirmed what the new system imports; you did not rely on the statement of work.
- [ ] The recipient is the CEO (in an owner-run company, the owner), who can authorize a licensing discussion.
- [ ] Nothing in the draft identifies a part, customer, program or plant.
- [ ] You have signed the Channel Partner Agreement.

If any box is empty, finish the [engineering system modernization checklist](/resources/engineering-system-modernization-archive-context-checklist) first; the [metadata packet for change-to-effectivity records](/resources/engineering-change-to-effectivity-metadata-packet) gives the owner's team a template.

## Adjusting the draft for the reader

| Recipient | Change to the draft |
| --- | --- |
| COO or plant leader copied as sponsor | Replace "released engineering change" with "approved design change" in the first sentence |
| CEO of a founder-led company | Shorten paragraph one to two lines and name the VP Engineering as the person SourceX would work with |
| PE-backed company | Add that the board may need to approve, if the owner said so |
| Carve-out or acquired plant | Address the CEO of the entity that will own the records after separation |

The CRM version of this draft is the sibling [CRM reimplementation email](/resources/crm-reimplementation-introduction-email); compare the two to see which lines change with the project.

After a yes, submit the authorized contact through your partner account and step back. The reward, if any, on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; the USD 50,000 floor applies once per referred company, and further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Illustrative only: a $400,000 Actual Supplier Payout would mean a USD 70,000 reward (USD 50,000 plus 5%, which beats 15%). Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. Fit: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Buyer interest and any offer stay unknown until SourceX reviews the application. For the project side, see the [PLM migration consultant guide](/guides/plm-migration-consultant).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When both ends of the change-to-order bridge are confirmed and the owner wants to hear more, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [terms](/terms) before sending.

## Sources

- https://help.sap.com/docs/SAP_ERP/9d59d0a6bdd14004adc69f4367d36a50/6324bd534f22b44ce10000000a174cb4.html
- https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/18ee18df146f46e9a7738186eebceaa7/5e07c453f57eb44ce10000000a174cb4.html
- https://support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_Help_Center/ChgMgmtEffectivityAbout.html
- https://support.ptc.com/help/windchill/cloud/r12.0.2.0/en/Windchill_Help_Center/CCMOviewChangeMgmtIntro.html
- https://learn.microsoft.com/en-us/dynamics365/supply-chain/engineering-change-management/engineering-versions-product-category
- https://www.ftc.gov/business-guidance/resources/ftcs-endorsement-guides-what-people-are-asking
- https://refer.sourcex.si/terms
