4.3 Vendor onboarding & framework agreements: LTA/SLA

Managing indirect suppliers requires a structured approach to maintain operational stability. Facilities management, external IT support, and calibration labs are significant operational dependencies. While the verification criteria differ from those applied to electronic component manufacturers, indirect suppliers should be onboarded with a focus on service continuity, legal compliance, and liability management.

Onboarding requirements

Adding a vendor to the ERP master data creates a formal corporate relationship. This process should outline expectations clearly.

Legal & financial verification

Tax ID: Standard documentation (e.g. W-9 or VAT equivalent) must be collected for corporate tax reporting.
Bank Verification: Bank wire instructions must be verified through a secondary channel (such as a voice call to a known company number) to mitigate the risk of Business Email Compromise (BEC) and wire fraud.
Insurance (COI): It must be ensured the vendor provides a Certificate of Insurance (COI) that meets corporate requirements, often listing the company as “Additional Insured.”
- Typical Coverages: General Commercial Liability, Worker’s Compensation, and Cyber Liability (if the vendor accesses internal network data).

Commercial terms

Payment Terms: Corporate default terms (e.g. Net 45 or Net 60) must be standardized on. Shorter terms or “Due on Receipt” for services should typically require Finance approval.
Incoterms: Delivery terms, such as DDP (Delivered Duty Paid) for consumables or DAP (Delivered at Place) for larger equipment deliveries, must be standardized.

Operational scope

Service Level Agreement (SLA): Expected outcomes, response times, and service metrics must be clearly defined.
Escalation Path: Technical contacts for off-hours support or urgent operational emergencies must be documented.

Framework agreements (LTA / MSA)

Processing individual POs for frequent, repetitive indirect expenditures generates unnecessary administrative overhead. Long Term Agreements (LTA) or Master Services Agreements (MSA) should be leveraged to establish fixed rates and liability frameworks for recurring spend.

When to consider an LTA:

Recurring Spend: High projected annual spend (e.g. > $$$10,000).
Critical Services: Essential continuous services such as IT Support, Metrology Labs, Facilities Maintenance, or Freight Forwarding.
High Volatility Consumables: Items with fluctuating commodity costs where a locked-in rate benefits budgeting.

The blanket PO strategy:

The Method: A single overarching ERP PO for the fiscal year or contract period (e.g. a $$$12,000 PO covering annual janitorial services) must be issued.
The Execution: The vendor submits monthly invoices referencing this master PO number.
The Benefit: Reduces administrative workload significantly and helps prevent service interruptions caused by internal PO generation delays.

Service KPIs & performance management

A contract is most effective when its terms are actively measured. Clear performance indicators must be included within the agreement.

1. Response time (the SLA)

The Metric: Time elapsed from the creation of an issue ticket to the vendor’s technical acknowledgement.
The Target: Clear expectations (e.g. < 4 Hours for critical line-down issues; < 24 Hours for standard support) must be defined.
The Structure: Negotiating service credits for consistent failure to meet agreed-upon response times should be considered.

2. On-time delivery / system uptime

The Metric: Percentage of physical deliveries meeting the requested dock date, or percentage of continuous IT system availability.
The Target: Typically aiming for > 95% or 98% consistent performance.

3. Support & rework

The Metric: Tracking the frequency of recurring issues or “callbacks” for the same problem.
The Clause: Expectations for the vendor to correct defective work within a certain timeframe at no additional cost must be defined.

Contract renewal & expiry logic

Proactive contract management prevents unfavorable auto-renewals and allows time to explore market alternatives.

A Suggested Renewal Protocol:

T-90 Days to Expiry: The ERP or Contract Management System must be configured to trigger an alert.
- The Action: The incumbent vendor’s performance and current market rates must be reviewed. It must be determined if a renewal or a new sourcing effort is needed.
T-60 Days to Expiry: If transitioning to a new vendor, it must be ensured any required formal legal Termination Notices are issued in accordance with the existing contract constraints.
- The Constraint: Many indirect service contracts contain “Auto-Renewal” clauses that require formal cancellation well in advance of the expiry date.

The vendor file & contract register

A clear, centralized registry of all indirect vendor relationships and their governing contracts must be maintained, ideally within the ERP.

Vendor Name	Indirect Category	Legal Contract Type	Start Date	End Date	Notice Period	Internal Owner
CleanCo Inc.	Facilities	MSA + SOW	Jan 1	Dec 31	60 Days	Facilities Mgr
TechOps LLC	IT Support	SLA Agreement	Jun 1	May 31	30 Days	Global IT Dir
Pack-Right	Packaging	Blanket LTA	Jan 1	Dec 31	N/A	Logistics Mgr

Final Checkout: Vendor onboarding & framework agreements (LTA/SLA)

Control Point	Engineering Requirement	Target Goal
Financial Auth	Bank Wire Details are verified via secondary channel.	Standard fraud prevention
Legal Liability	Required COIs are active and on file.	Reviewed annually
Payment Terms	Agreements align with standard corporate terms.	Maintained
Blanket POs	Utilized for predictable recurring services.	Implemented where beneficial
Review Cycle	System provides alerts prior to contract expiry.	E.g. at T-90 Days
SLA Definition	Response times and quality metrics are documented.	Tracked for key vendors