value performance spec-revisied

7/27/2019 Value Performance Spec-Revisied

1/13

VALUE PERFORMANCE REPORT

CALIPER LS

Author: Maureen Sateriale

Creation Date: January 11, 2011

Last Updated: February 4, 2011Version: 2.0


2/13

Document Control

Change Record

3

Date Author Versio

n

Change Reference

11-Jan-2011 Maureen Sateriale 1.0 Original, no previous document.4-Feb-2011 Maureen Sateriale 2.0 Changed DFF from vendor site to vendor

Reviewers

Name Organization

Jackie GiaquintoMaurice PlourdeSandeep Adapala

Distribution

CopyNo.

Name Location

1 Caliper LS US2

Value Performance Report

MD050 Caliper Value Performance Report


3/13

Contents

Document Control.......................................................................................ii

Introduction................................................................................................4

Basic Business Needs............................................................................4Major Features .....................................................................................4Assumptions..........................................................................................4

Descriptive Flexfield Purchasing / Vendors.............................................5

Layout of the existing Report ....................................................................6

Data Requirements / Mapping....................................................................7

Open and Closed Issues for this Deliverable.............................................13

Issues..................................................................................................13

Value Performance Report



4/13

Introduction

This document will describe and define the requirement to create a ValuePerformance Report in Oracle that can be run on demand. This report iscurrently done in MS Access after extracting the data needed from reportsdeveloped in Discoverer.

Basic Business Needs

Vendor Performance Report can be run on demand for specific vendors thatare classified as Tier 1 performers. In doing so the goal is to eliminatehaving to do multiple data extracts and calculations outside of Oracle.

Major Features

1. Planner / Buyers will be able to run the Vendor Performance Reportfor any specified period of time, for all tier 1 or individual tier 1vendor / suppliers.

Assumptions

1. Existing discoverer reports described in this document will beleveraged to achieve the final results.

2. Vendor / Suppliers that this report can be used for will be identifiedat the vendor site level. A descriptive flexfield will be set up to

define attributes that are constant values for the vendor/supplier. The Value Performance section of the output will be defined usingvalue sets and descriptive flexfields. The users will be responsiblefor the Value Performance Available Pts. Value and the ValuePerformance Actual Pts. Value given to the vendor/supplier.

~ 4 ~



5/13

Descriptive Flexfield Purchasing / Vendors

Added 3 segments and none are required on the vendors descriptive flexfield

Only vendors that this report can be run for will have these segments populated on the vendors DFF

~ 5 ~



6/13

Layout of the existing Report

The goal is to produce the same report. One page per vendor/supplier.

~ 6 ~



7/13

Data Requirements / Mapping

Report Parameters:

1. Organization - Required

2. Beginning Date - Required

3. Ending Date - Required

4. Vendor / Supplier (name) or All- Optional

5. Evaluation Period - Required

Report Heading = Value Performance Report

Evaluation Period: (from report parameter 5)

A. Fundamentals

Quality Performance - Based on the report value below this number would appear as9,316 DPM (6/644) Rejected

Quality performance data is currently being extracted from the Discoverer reportCaliper Receiving Rejection Code Listing Report.

We need to use the same logic that is used to produce this report today to arrive atthe values we need for the quality performance. The parameters we are using forthis Vendor Performance Report should be valid to produce the data for the QualityPerformance.

The selection criteria on the Rejects and Return to vendor only should always beNO. This will include both rejected material and return to vendor material.

CALIPER RECEIVING REJECTION CODE LIST: SUMMARY SEARCH

~ 7 ~



8/13


9/13

Actual Pts. 10 The actual points will be based on the Quality Performance Value. Thevalue set defines the sequence to evaluate the value. For the example provided in thisdocument the Quality Performance is 9,316, the Actual Pts. would equate to #3 or 10 pts. 10pts. =


10/13

8.82% On time = On time / total deliveries * 100 = 8.82% from the report

(3/34) on time

~ 10 ~



11/13

Available Pts. 40 Setup a Value Set called Value Delivery Performance CriteriaAvailable Pts. will always default to the highest value which is 40

Actual Pts. 0 The actual points will be based on the Delivery Performance Value. Thevalue set defines the sequence to evaluate the value. For the example provided in thisdocument the Delivery Performance is 8.82% the Actual Pts. would equate to #4 or 0 pts. 0pts. =


12/13

Available Pts. print the value from the vendor site descriptive flexfield attribute 2

Actual Pts. print the value from the vendor site descriptive flexfield attribute 3.

Hardcode the Note that appears at the bottom of the page:

Note: A score of zero (0) points in any category requires submittal of a written CorrectiveAction Plan within 2 weeks.

TOTAL SCORE: = 100 pts. -Total of the Available Pts. from the Quality Performance,Delivery Performance and Value Performance columns. Actual Pts. from the QualityPerformance, Delivery Performance and Value Performance columns and in this example itwould be 10

~ 12 ~



13/13

Open and Closed Issues for this Deliverable

Issues

ID Issue Resolution Responsibility Target Date ImpactDate

123

~ 13 ~


value performance spec-revisied

Documents