04.07.2013 Views

Supplier Extended Enterprise Claims System (SEECS) - Chrysler

Supplier Extended Enterprise Claims System (SEECS) - Chrysler

Supplier Extended Enterprise Claims System (SEECS) - Chrysler

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Supplier</strong> <strong>Extended</strong> <strong>Enterprise</strong><br />

<strong>Claims</strong> <strong>System</strong> (<strong>SEECS</strong>)


What is <strong>SEECS</strong>?<br />

<strong>Supplier</strong> <strong>Extended</strong> <strong>Enterprise</strong> Claim <strong>System</strong> (<strong>SEECS</strong>) is a<br />

system designed to reduce manual processing of<br />

supplier claims.<br />

• Communicates excess material to other <strong>Chrysler</strong> areas<br />

• Provides information to supply partners regarding:<br />

• <strong>Chrysler</strong> releases<br />

• Shipping figures<br />

• Program numbers used in the analysis of their<br />

claims<br />

2


What is the goal of <strong>SEECS</strong>?<br />

To provide a process and control for the submission,<br />

review, tracking, audit and approval of valid part claims<br />

arising from engineering product change and/or<br />

cancellation of production parts.<br />

Note: Tooling claims are now processed through SCRS.<br />

3


What IS a Claim for <strong>SEECS</strong><br />

Processing?<br />

• Parts not yet in production: Maximum of 300 pieces; anything<br />

above needs written authorization by Purchasing and proof of<br />

part cancellation.<br />

• Anything less than or equal to the Raw and Fab 830 release<br />

authorization with proper authorization (Standard PO term 2-6<br />

week or <strong>Extended</strong> Authorization from Production<br />

Programming & Scheduling).<br />

• Service Parts – Must be submitted to Mopar.<br />

4


What IS NOT a Claim for <strong>SEECS</strong><br />

Processing?<br />

• Anything above RAW & FAB authorization for production<br />

parts (ie, banks, build ahead for tool change). <strong>SEECS</strong> only<br />

pays for claims within the 830 release high commitment.<br />

Commercial agreements made outside of the 830 release high<br />

commitment must be paid via SCRS.<br />

• Temporary Substitution Allowance (TSA) – this should be<br />

covered through a Change Notice (CN).<br />

• Production Parts without a valid Purchase Order (PO).<br />

• Advance Product Change Notices (APCN’s).<br />

• F1 parts – this should go through Advanced Product<br />

Procurement.<br />

• Re-work charges on parts and/or tooling.<br />

• Non-production parts.<br />

• Tooling claims.<br />

5


<strong>Supplier</strong> Benefits & Requirements<br />

<strong>Supplier</strong> Benefits<br />

• Streamlined approach for filing claims<br />

• Historical Data Available<br />

• Improved Cycle Time for <strong>Claims</strong> Processing<br />

• Eliminates Manual Processing of <strong>Claims</strong><br />

• Quality - Continuous improvement claims processing<br />

<strong>Supplier</strong> Requirements<br />

• <strong>Extended</strong> <strong>Enterprise</strong> Network User<br />

• Must have access to SPIN region<br />

• Must have security set-up with PSC authority<br />

• Meet basic requirements for claim eligibility<br />

• Has 90-days to submit claim<br />

6


Valid <strong>SEECS</strong> Claim Types and<br />

Reasons<br />

Claim Types: Claim Reasons:<br />

Production Part Cancelled (going from AA to AB level)<br />

Part Changed (release part number does not change)<br />

<strong>Supplier</strong> Resource<br />

Non Carryover (model year end)<br />

Mopar Part Cancelled<br />

Part Changed<br />

<strong>Supplier</strong> Resource<br />

Release Cutback<br />

7


Valid <strong>SEECS</strong> Claim Types and<br />

Reasons<br />

<strong>Supplier</strong><br />

Spin Edit = S<br />

Hold = H<br />

SDRM<br />

Mopar<br />

Inprocess = I<br />

<strong>Supplier</strong> Delivery<br />

Risk Management<br />

Audit = A<br />

SDRM<br />

<strong>Supplier</strong> Delivery<br />

Risk Management<br />

APC/PO<br />

Closed<br />

8


Responsibility of <strong>Supplier</strong><br />

Since all communication will be by electronic means via<br />

Notepad, it is imperative that suppliers check the status of their<br />

claims frequently. We suggest three times per week. The<br />

supplier has ownership of this responsibility until the claim has<br />

reached a status of “In Process”. Please be advised that if your<br />

claim entered a status of “Hold” after submission, the claim may<br />

be sent back to the supplier. At this point the status can change<br />

to “Spin Edit” which means that we are asking for additional<br />

information or clarification. The claim could remain in a “Hold”<br />

status for an unspecified amount of time, which is why the<br />

Notepad should be reviewed to determine the reason for return.<br />

Monitoring of claims should continue until the claim has<br />

reached the “In Process” Status. Additionally, all claims added<br />

by the supplier (as “SPIN EDIT”) must be submitted (action code<br />

“S”) within 10 days. All claims in SPIN EDIT beyond 10 days will<br />

be deleted from the system. Prior to deletion, an e-mail will be<br />

sent to you.<br />

9


Sample 10 Day Warning Delete Note<br />

Claim Number 2010-9999 is in Spin-Edit (S) Status for <strong>Supplier</strong> 99999<br />

<strong>Supplier</strong> Name- XXXXXXXXXXX INC<br />

Release Part Number- XXXXXXXXAA PART DESCRIPTION<br />

This Claim has been in Spin Edit Status for more than 7 days!<br />

The Claim was Submitted by- S99999X<br />

The Claim was Requested by- SUPPLIER NAME<br />

and the phone number is- 999-999-9999<br />

10


Access <strong>SEECS</strong> from Covisint<br />

Once in the <strong>Chrysler</strong> Portal in Covisint, click on ‘Applications’.<br />

There are 2 <strong>SEECS</strong> links. One for Documentation and one for the Application.<br />

11


Documentation Web Site<br />

12


<strong>Supplier</strong> <strong>Extended</strong> <strong>Enterprise</strong> <strong>Claims</strong><br />

<strong>System</strong> (<strong>SEECS</strong>) - 3270<br />

Enter your S-ID and password<br />

Click on Normal Mod2<br />

13


<strong>SEECS</strong> Main Menu<br />

<strong>SEECS</strong> navigation can be found in the <strong>SEECS</strong><br />

Help on Covisint. It is on the last page of the<br />

Claim Entry Detail Documentation.<br />

14


<strong>SEECS</strong> Claim Header Detail<br />

<strong>Supplier</strong><br />

Request<br />

Claim Type<br />

Claim Status<br />

Reason<br />

<strong>Chrysler</strong><br />

Calculated<br />

Obligation<br />

(Appears when<br />

Submitted to<br />

<strong>Chrysler</strong>)<br />

15


<strong>SEECS</strong> Part Detail<br />

A finished part number is required for all claims. The quantity<br />

available can be zero. Only one finished part per claim. Finished and<br />

WIP are calculated against fab auth. Raw and Purchased are<br />

calculated against raw auth.<br />

16


<strong>SEECS</strong> Part List<br />

This is a case where the supplier is requesting payment for purchased components only.<br />

17


<strong>SEECS</strong> Notepad<br />

When the claim is created, if there is anything else <strong>Chrysler</strong> should<br />

know about the claim, it should be entered on the notepad. (ie., if you have<br />

<strong>Extended</strong> authorization, state that comment in the notepad.)<br />

<strong>Supplier</strong>s can you use notepad to monitor the status of the claim.<br />

18


<strong>SEECS</strong> Contacts<br />

Production <strong>Claims</strong><br />

Chuck Kelly - Analyst (248) 512-1016 cak26@chrysler.com<br />

Anna Zanger - Manager (248) 576-8713 amz2@chrysler.com<br />

Mopar <strong>Claims</strong><br />

Diane Underwood – Analyst (586) 497-9161 dfu@chrysler.com<br />

James Garden – Manager (586) 497-9944 jrg8@chrysler.com<br />

19

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!