The document outlines the criteria and features for evaluating a supplier relationship management tool within the context of the EMEA region. Key aspects covered include supplier measurement methods, deployment timelines, system functionality such as document capture and reporting, and user security measures. It emphasizes the importance of real-time data tracking and oversight for effective supplier relationship management.

1. Criteria
Weighting
Baseline Survey Form
EMEA Archer
Tool
Category Criteria
Supplier relationships are measured on a
percentage basis
0
Supplier relationships are measured on actuals
(e.g., Volume)
0
Outsourcing is defined & measured as Supplier
sites only
0
Outsourcing is defined and measured as
Supplier sites and <Company> Service Centers
(not performed by the core business unit)
0
Audit Trail
System provides an audit tral of configuration
and/or data changes
0
Is the tool a current <Company> approved and
deployed tool?
0
Redevelopment is necessary to deploy the tool
for <Program>
0
Changes can be requested and deployed
within 24 to 48 business hours
0
The time to deployment is less than 2 to 3
weeks
0
Database
Does the system provide automated back end
query functionality?
0
Analysis and
Measurement
<Company>
Deployment

2. Does the system provide ability to capture
service provider documents?
0
The system provides the ability to capture sub
process volumes?
0
Can the system capture SOW and COB specific
details?
0
End users (Supplier Relationship Managers)
are responsible for information submittal
0
The system provides direct ability for Supplier
Relationship Manager management to
approve information prior to submittal
0
Management
Oversight
Supplier Relationship Management has the
ability to track real-time survey response
statistics
0
Does the system provide default reports out
of box?
0
The system provides the ability to collect and
present information by sector, country, and
line of business
0
Basis of the risk analysis is the overall Supplier
relationship
0
Basis of the risk analysis is the individual SOW
0
Users access the system by single-sign-on
capability
0
Are there information protection
mechanisms?
0
User security architecture exists 0
SecurityFunctionality
Information
Submittal
Reporting
Scope of
Risk
Analysis

3. System Credibility
The system is a commercial OTS application
(e.g., tested in multiple Production
environments)
0Taxonomy
The system has, or can maintain common
definitions of Process Criticality
0
Technical Support
Are resources available to support the tool on
a continual basis?
0