MSC Integration Docs
Onboarding requirements
Implementation takes four weeks from the date MSC provides the items below. The critical path is the schema, sample data, shared mailbox and first portal credentials.
Checklist
| Item | MSC owner |
|---|---|
| Name owners: program lead, IT integration lead, security reviewer, sourcing business owner | Program lead |
| Five-table sourcing schema and bulk template with sample rows | Sourcing data owners, IT |
| Twelve months of sourced lines with outcomes, vendor master with tiers, the two sample datasets | Sourcing data owners |
| Supplier hierarchy tiers and competitor exclusion list | Sourcing leads |
| Entra ID app registration for SSO and Graph | Entra ID admin |
| Shared sourcing mailbox, named | M365 admin |
| Consent for the Faction Teams app, added to the chosen channels | M365 and Teams admin |
| SFTP path, or approval to use Faction-hosted SFTP | MSC IT |
| Confirm the 19 fields and sign off ranking weights | Sourcing leads |
| Vendor portal list, credentials and MFA method | Vendor management |
| Approve the RFQ email template | Sourcing leads |
| Read access to EDI and SPS feeds | MSC IT |
| List Manager call-out and webhook receiver, built against the sandbox | List Manager developers |
| Quick Item Add handoff point and payload spec | MSC IT |
Faction provides
A sandbox from week 1 with the same contract as production, the API specification, credentials and a List Manager reference connector. Faction maps the schema with MSC IT, configures the hierarchy, exclusions, fields, template and weights, and monitors every integration. To arrange a working session with MSC IT, contact Kunal Barman or Danish Raza.