0% found this document useful (0 votes)
221 views20 pages

Lisa V5 PDF

The document provides an agenda and information about setting up and using LISA, a scheduling and pull system tool. Key points: - LISA levels production schedules across delivery trucks to optimize loading and facilitate supplier production. It is integrated with the FCS ERP system. - Implementing LISA for the first time typically takes 1-2 months as a mini-project. Materials data, transport data, and output parameters must be configured. - The weekly LISA process includes leveling calculations and validation, manifest generation for suppliers, and pickup/crossdock reports for logistics partners. Properly set up LISA aims to balance schedules across trucks.

Uploaded by

Rx Dentview
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
221 views20 pages

Lisa V5 PDF

The document provides an agenda and information about setting up and using LISA, a scheduling and pull system tool. Key points: - LISA levels production schedules across delivery trucks to optimize loading and facilitate supplier production. It is integrated with the FCS ERP system. - Implementing LISA for the first time typically takes 1-2 months as a mini-project. Materials data, transport data, and output parameters must be configured. - The weekly LISA process includes leveling calculations and validation, manifest generation for suppliers, and pickup/crossdock reports for logistics partners. Properly set up LISA aims to balance schedules across trucks.

Uploaded by

Rx Dentview
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 20

Scheduling & Pull system

LISA

6th of June 2016 (V5)


Agenda

 LISA purpose ---------------------------------------------------------------------------------------------------------------------------------------- 1:00 – 1:30 PM


 LISA 1st time implementation in a plant --------------------------------------------------------------------------------- 1:30 – 1:45 PM
 LISA launch process
 LISA access
 LISA parameter setup ----------------------------------------------------------------------------------------------------------------------- 1:45 – 2:15 PM
 Materials data
 Transportation data
 Output data
 LISA weekly process ------------------------------------------------------------------------------------------------------------------------- 2:15 – 3:15 PM
 1. Supplier backlog under control
 2. Transportation update
 3. Levelling calculation
 4. Levelling validation
 5. Manifest and EDI transmission
 6. Pick-up report and Cross dock matrix
 7. Manifest printing
 Plant LISA weekly process ------------------------------------------------------------------------------------------------------ 3:15 PM – 4:15 PM
 LISA New Generation presentation ------------------------------------------------------------------------------------ 4:15 PM – 4:30 PM

3
Functional macro process

PURCHASING SALES
Contract LOGISTICS Contract

Material Integration
Procurement of the
Levelling requirements PDP PIC
program customer
planning
demand
Supplier Customer
LOGISTICS PRODUCTION LOGISTICS

Transfer
Goods Production Production Shipment
to
receipt production declaration

METHODS / ENGINEERING
Inventory
Product mBOM Creation of
QUALITY definition management work centers Inventory CONTROLLING
in FCS in FCS and routings
in FCS

4
LISA purpose

LISA : Leveling Information for Supplier Application


 Functionnality integrated to FCS
 Processed after MRP run
 Goal = level Schedule lines across the trucks
Part # A 30-Nov 1-Dec 2-Dec 3-Dec 4-Dec 5-Dec Min lot size = 60
Stock 30 Rounding value = 60
Dependent requirements 150 150 Safety stock target = 20
Schedule lines 180 120 Delivery days: M to F, 1 truck per day
Available quantity 10 10 40 40 40 10

LISA

Part # A 30-Nov 1-Dec 2-Dec 3-Dec 4-Dec 5-Dec Levelling horizon = 1st to 5th December
Stock 30
Dependent requirements 150 150 MRP Schedule lines during levelling horizon = 180 + 120 = 300
Schedule lines 60 60 60 60 60 LISA Schedule lines = 300 / 5 trucks = 60 in each truck
Available quantity 10 70 -20 40 100 10

Levelling horizon

 Send levelled needs to Suppliers which optimizes truck loading rate and facilitates Supplier production
 Projected stock must be checked before validating LISA levelling

 LISA levelling game


5
LISA purpose

LISA : Leveling Information for Supplier Application


 LISA levels Schedule lines per parts family: LISA family
 Minimum required : 1 LISA family per plant
 Recommendation : 1 LISA family per supplier, per plant
 If packaging size and weight are very different between parts from the same supplier: 1 LISA family per packaging group
(distributes evenly weight and volume across the trucks)

 After levelling, the projected stock must be checked and corrected if a shortage is detected

 Outputs:
 Manifest (= expected delivery quantities) – for Suppliers,
 Pick up report – for Carriers in case of Cross Dock,
 Cross dock matrix – for Cross Dock personal.

-00 indicates it is the initial Manifest.


-01 if Shortage, Supplementary or
Emergency Manifests.

On Initial Manifest: Truck delivery number


YEAR MONTH DAY (if multiple deliveries per day).
of the delivery RR- for Shortage Manifest,
01- for Supplementary Manifest,
6 UU- for Emergency Manifest.
LISA 1st time implementation in a plant

LISA launch process


 Mini project – takes 1 to 2 months to implement

 Starting point: send an email to LEGOUPIL Benjamin, Faurecia Group LISA project manager to define:
 size of the project
 kick-off meeting date

 LISA implementation will be done for 5 suppliers

 You will then be able to add more by yourself

 FAU-F-LSG-2025: Gate Review Checklists for LISA Roll Out

7
LISA 1st time implementation in a plant

LISA launch process

8
LISA 1st time implementation in a plant

LISA access
 LISA transactions are granted to Material planners by default

 E-LISA, application where LISA documents are created & stored (previously Easylink) is accessible to all
Faurecia users
 http://e-lisa.app.corp/Default.aspx
 Detects the Windows login of the user connected to the computer

 LISA.net (only used for other ERPs than FCS – around 40 plants)
 Request access to LEGOUPIL Benjamin
9
LISA parameter setup

1. Materials data
 Pre-requisites: BOP/RM, packagings and scheduling agreements must exist in FCS
 Packaging creation work instruction: FCS-PE12-WI-SAP-Returnable_packaging.pdf

 Work instruction: FCS-PE18-WI-SAP-01-Lisa-parameters (printed):


 Adjust materials Master data – to conform to LISA process
 Transactions used: MM02 and ME32L
 Mass upload possible: FCS-PC01-WI-Material_Mass_Updates

 Assign Sebango and Storage bin – to make identification clearer


 Transactions used: ZPP_ZPU001 and MM02 (Plant data / stor. 1)

 Create packaging instructions - to inform FCS about relation part / box / activity
 Transactions used: POP1, POF1

 Decide on Mix pallet rule usage – if you accept Supplier to mix boxes using same pallet
 Transaction used: ZPP_PACK_MIX

 Check data consistency – to validate parts setup


 Transactions used: ZJM58
10
LISA parameter setup

2. Transportation data
 Pre-requisites: suppliers must exist in FCS
DIRECT

Route
FLOW

(Connection point) (Connection point)


MILK
RUN

(Connection point) (Connection point) (Connection point) (Connection point)

Route

Route (from A
to Faurecia)
CC / CD

(Connection point)
(Connection point) (Connection point)

(Connection point)
Route (from B
to Faurecia)
(Connection point)
11
LISA parameter setup

2. Transportation data
 Create Connection points - for departure, stops and arrival points of a route
 Transactions used: 0VTC for Faurecia and supplier points. For consolidation center and cross dock points: open Stratos
ticket.

 Create Routes - naming convention: plantcode + 1 alphabetical character + 1 digital character


 Transaction used: 0VTC (example: 1268A2)
 Whatever the complexity of the route you want to create, it is always initially created between a Supplier connection point
and Faurecia connection point. Other points can then be added.
BEFORE adding or deleting
any step in the route, if the Schedule is
 Create Schedule - to link BOP / RM to a route Already created, it is mandatory to
 Transaction used: VL51A delete and re-create it (VL52A)

 Create Transportation plan - to define arrival / departure date & time at each connection point and final
delivery date & time at Faurecia
 Transaction used: ZJM54N

 Check data consistency


 Transactions used: ZJM58 After creating 1 week worth of Transportation plan,
save your work to check for errors.
DO NOT LEAVE TRANSACTION:
 Work instructions: FCS-PE18-WI-SAP-Route.management extend through end of year and save again.

FCS-PE18-WI-SAP-04-Leveling and manifests (up to p11)


12
LISA parameter setup

3. Output data
 Work instruction: FCS-PE18-WI-SAP-Output management:
 Maintain Output parameters for EDI (ZJIT)
 Transaction used: MN24

 Maintain Output parameters for E-LISA (ZWEB)


 Transaction used: MN24

 Maintain tables for E-LISA (emails, MRP controller, etc.)


 ZMMCDFLOW - customize new LISA Cross Dock flow by plant (done by L2)
 OMD0 – maintain MRP controller email address (done by L2)
 ZLE_LISALOGID – maintain plant information send to E-LISA
 ZLE_LISACUSINF – maintain customer information send to E-LISA
 ZLE_LISASUPINF – maintain supplier information send to E-LISA
 ZMM_LISA_EMAIL – maintain suppliers and carriers email address

 Create LISA families – 1 minimum (naming convention: LISA_plantcode_xxxxx)


 Transaction used: MC84
 Work instruction: FCS-PE18-WI-SAP-01-Lisa-parameters (printed)

13
LISA weekly process

1. Supplier backlog under control


 Supplier backlog must be under control
 LISA process only takes into account Schedule lines in the levelling period you select – not Schedule lines
previous to this period
 Adjust previous Schedule lines with exceptional manifests:
 Shortage manifest = __________________________________________________________________
______________
 Emergency manifest = _________________________________________________________________
_______________________________________________________________
 Supplementary manifest = _____________________________________________________________
______________________________________________________________________________________
_________________________

2. Transportation plan update


 Work instruction: FCS-PE18-WI-SAP-08_Exceptional_Manifest_Management_(Manual and Automatic)
 If necessary, update the Transportation plan
After each update
 Update with the number of trucks needed of date or time, you
 Pay attention to supplier non working days MUST push “ENTER”
 Adjust transit time in case of special events button

 Work instruction: FCS-PE18-WI-SAP-04-Leveling and manifests (up to p11)


14
LISA weekly process

3. Levelling calculation
 Pre-requisites:
 MRP has been performed to create schedule lines,
 Schedule lines have been verified and approved by MRP controller – including Supplier backlog, which
must have been re-scheduled at agreed time,
 Transportation plan is created and updated,
 LISA parameters are OK when ZJM58 report is run.

 Transaction used: ZJM55N

 Levelling Horizon: 1 week, after the firm period – all requirements prior to that are either already in
preparation at Supplier, in transit or managed by Shortage/Emergency/Supplementary manifests.
Example: Agreed firm period = 3 weeks, 1 delivery per week, 1 week transit time.
Planned Planned Planned
delivery delivery delivery

Time line
Today Week 1 Week 2 Week 3
Needs in transit Needs in preparation Week to be processed
to Faurecia plant at the Supplier with LISA levelling
Firm period
 Work instruction: FCS-PE18-WI-SAP-04-Leveling and manifests (p11-12)
15
LISA weekly process

4. Levelling validation
 Transaction used: ZJM56N, option « Create Inbound Deliveries », select « Project stock »
 If Projected stock report shows a shortage : modify levelling and keep same total number of lots

‘Projected stock’ includes any available


safety stock.
- Green: projected stock > safety stock
- Yellow: projected stock < safety stock
- Red: projected stock < 0
 Levelling validation allows Inbound Delivery creation
 Work instructions: FCS-PE18-WI-SAP-04-Leveling and manifests (p12-14)
FCS-PE18-WI-SAP-Projected stock and other enhancements
16
LISA weekly process

5. Manifest and EDI transmission


 Transactions used:
 ZJMM02N - to send Manifest / EDI to suppliers.
 E-LISA - to check Manifest / EDI transmission status: “File report” to see if PDF was generated
(OK) or if an error occurred during treatment (NOK).

 Work instruction: FCS-PE18-WI-SAP-04-Leveling and manifests (p12-14)

6. Pick-up report and Cross dock matrix


 Transactions used:
 ZJMPRN - to create and send Pick-up report
 ZMMCDMTRIX - to create Cross dock matrix

 Work instruction: FCS-PE18-WI-SAP-Transport document

7. Print Manifests
 Through email or E-LISA
 E-LISA user guide: http://group.shareplace.faurecia/sites/bs_cc_cws/lisa/eLisa/User%20Manual%20V1.1.pdf
17
LISA New Generation

Purposes
 LISA New Generation Toolkit

 Integration of supplier ASN to react to mis-deliveries ahead of time:


 If discrepancy between ASN and Manifest, Material planners can confirm data with supplier and make
decisions (accept over delivery or prepare material return, accept under delivery or prepare shortage
manifest / addition to next delivery) and update Manifest accordingly.
 A report can be printed to remind Material planners of the actions they decided to do.

 Simplification of the reception process with scanning and 1 scan Poka-Yoke:


 If all scanned labels match the Manifest, delivery is booked in FCS directly with the RF gun by the receiving
operator.
 If a label is scanned but does not match the Manifest, the receiving operator must scan the part #, supplier
and quantity bar codes  added to discrepancy list.
 If a BOP / RM is missing when expected  added to discrepancy list.
 Receiving must call corresponding Material planner to review disprepancy list, make decisions and update
Manifest accordingly.
 Clerk can then book the validated quantities in FCS.

18
LISA New Generation

Implementation to a plant
 The Levelling process and steps are exactly the same than previous LISA version
(addition of ASN Vs Manifest comparison only)

 Implementation steps:
Read the general “2-Documentation”, then depending on the flow (Inter/Intracompany flows or external
suppliers), follow the retrofit process documentation: Retrofit LISA New Generation toolkit

 Work instruction: FCS-PE18-WI-SAP-09-LISA New


Generation
 GIS training course: FCS-TRN-PE18-LISA New Generation

 Pilot validated and on deployment phase


 New functionalities under validation process
LISA V5 19
LISA weekly process

1. Supplier backlog under control


 Supplier backlog must be under control
 LISA process only takes into account Schedule lines in the levelling period you select – not
Schedule lines previous to this period
 Adjust previous Schedule lines with exceptional manifests:
 Shortage manifest = _________________________________________________________________
Manifest created due to a supplier under delivery, to request the missing parts.
 Emergency manifest = Manifest created to request extra parts from supplier, which will be shipped via
________________________________________________________________________
expedite. The extra demand is due to a Faurecia mistake.
_______________________________________________________________________________________________________
 Supplementary manifest = _____________________________________________________________
Manifest created to request extra parts from supplier, which will be shipped via
regular transportation (addition to the current truck load). The extra demand is due to a Faurecia mistake.
___________________________________________________________________________________________

 Work instruction: FCS-PE18-WI-SAP-08_Exceptional_Manifest_Management_(Manual and Automatic)

2. Transportation plan update


 If necessary, update the Transportation plan After each update
 Pay attention to supplier non working days of date or time, you
MUST push “ENTER”
 Adjust transit time in case of special events
button
 Work instruction: FCS-PE18-WI-SAP-04-Leveling and manifests (up to p11)
21

You might also like