All configurations and Test steps below based on Configuration done in SAN (Sandbox client 100) in ILUKA Landscape

1. Create Equipment Master Record for Fleet Transaction code: IE01 (Create Equipment) Purpose: To create a Fleet Equipment (New Equipment category configured with enhanced Tab views meant for Fleet objects Equipment Category F: Fleet Enter Relevant field details in the available views View : General In the field Object Type, Choose Object type FLEET from dropdown. This object type has been configured to activate 2 additional tabs for Views - Vehicle ID/Measmnts, Vehicle Technology (Detailed later) Fill in other fields in General view as relevant

View : Location Enter Location details as relevant with fields such as Maint Plant, Location, Plant Section

View : Organization Enter details in Fields as relevant such as Business area, Cost Center, WBS Element, Planning Plant, Planner Group, Main work center etc.

View : Structure Enter details in Fields as relevant Technical Identification No, Installation Functional Location , Construction Type (If linked to material/assembly code)

View : PRT Data Enter details in Field Task List Usage 004 Only Maintenance Task Lists. If there is a Fixed Maintenance plan for this vehicle, it can be enetered in Default values for maintenance --> Maintenance Plan

Tab: Measuring points/counters Enter measuring counters DISTANCE, TIME, FUEL (have defined characteristics DISTANCE, TIME, FUEL in Sandbox 100). These counters would help in posting the vehicle usage data including Distance run, Time usage, Fuel consumed

Tab: SerData If relevant only Maintain Material + Serial No combination

Tab: Warranty New feature Logbook Duty added If Logbook is ticked a Logbook is simultaneously created for the object Features and usage of Logbook detailed later in this document. However to get the actual transaction LBK1 active with full log entry, a Log entry subscreen BADI : LGETY_SUBSCR_ACL needs to be activated

Tab: Documents To attach Document info records (if required) such as Vehicle manual, Operation guides, Safety procedures, Design documents, Warranty manuals, Regulatory Maintenance norms, Licenses and Regulatory documents etc. Tab: Vehicle ID/Measurement - **NEW TAB FOR FLEET EQUIPMENTS In this new tab you will have a whole new set of fields under views including Identification data - Vehicle Type (prepopulated as FLEET to activate the Fleet functionality) - Fleet Object No. (18 character free text) - License Plate (15 character free text) - Validity End date (of License plate) - VIN (Manufacturer Vehicle Identification No 28 characters long)

Replacement data (Optional) - Replacement date - Odometer Reading Replacement - Hour Counter - replacement Transport Relevant data - Weight Weight of Fleet object - Total Weight permitted weight of Fleet object including Load - Max Load weight Max load of Freight object it may carry - Load volume - Load Height - Load width - Load length - No. of compartments (2 digit - numeric)

After making all entries save the master data. A 2XXX. Series Equipment will be generated

Tab: Vehicle Technology - **NEW TAB FOR FLEET EQUIPMENTS In this new tab you will have a whole new set of fields under views including Dimensions - Fleet Object Height - Fleet Object width - Object Length - Unit of length

Engine Data - Engine Type - Engine Serial No - Engine Power - Engine Capacity - Maximum speed - Revs. Per min. - No. cylinders

Fuel and Lubricants - Primary Fuel At the moment for prototype only 2 Fuel types created: Primary and Secondary, but it can be added - Secondary Fuel - At the moment for prototype only 2 Fuel types created: Primary and Secondary, but it can be added - Oil Type Can be added in configuration to reflect in dropdown as per user requirement - Calculation Method: This method will be used to calculate vehicle performance on basis of DISTANCE/TIME (whichever is chosen as Primary counter) and FUEL (Secondary counter always). Currently 2 standard Calculation methods have been configured in SAP (SAN Sandbox environment) - Material consumption key : Default key for consumption to Cos Center/Order/WBS a. If you want the Fuel postings to be Debited to the Equipments Cost Center (Defined in Equipment master --> Organization --> Cost Center), set the Material consumption key as K from drop down b. If you want the Fuel postings to be Debited to a Project WBS element linked to Equipment (Defined in Equipment master --> Organization --> WBS Element), set the Material consumption key as P , from drop down c. If you want the Fuel postings to be Debited to a Standing Maintenance Order linked to Equipment (Defined in Equipment master --> Organization --> Standing Order), set the Material consumption key as F, from drop down. Ensure that based on the default key chosen, the object Cost center/WBS element/Standing order is maintained in Equipment master. In the test scenario shown in this document, default posting has been set to an Equipment cost centre (for testing purpose cost center 1065249 was set in Organization tab of Equipment master 20000000.

Consumption Tolerance key : Controls how system will react when Fuel consumption is exceeding by a certain % limit (as defined in tolerance key) against Average consumption (as calculated by system based on past postings). In test scenario, W- Warning on +5% above average consumption has been set. Note: To Edit (Change)/Display this Fleet Equipment use, same transaction code as Equipment Change/Display IE02/IE03

2. List Report for Fleet Vehicles - Transaction code OIFL

3. Set annual usage for counters- DISTANCE, TIME, FUEL (at startup only) Transaction code: IK02 Purpose: To set an approximate annual estimate for the characteristics

4. Initialize counter reading to zero (or as relevant) Transaction code: IK11 Purpose: To enter initial counter reading that would generate a measurement document

Distance relevant counter entered first reading as 0 or difference (from last reading) assuming its a brand new fleet (else enter first read as relevant) Repeat similarly for counters relevant to Fuel and Hour usage

5. Single Transaction for Consumption (Fuel) + Distance, Hour run counter postings Fleet Process Specific Transaction IFCU Pre-requisite: There should be adequate stock of Primary Fuel (to be posted through FUEL Counter) in the Gas station Check if Fuel is in stock Transaction code MB52

Execute Transaction code: IFCU (For all counter postings- DISTANCE, FUEL, TIME)

In the initial screen, system would ask you to enter Equipment No (of Fleet Equipment) and Gas Station (from which Fuel is to be posted) and press enter

In the main screen you will find 2 sections Section 1 Consumption, in which you fill in the Quantity of fuel consumed, Fluid Type (Select from dropdown the dropdown can be customized to contain all the material codes that are associated to Fuel consumed by Fleet equipments). For testing purpose in Sandbox just 2 Fuel type will appear in dropdown Primary and secondary each of which has been mapped to a material code in background configuration. Use Primary Fuel for your testing.

The field calculation method would get defaulted to what is set in Fleet Equipment master. But you can choose between Usage volume/Time or Usage volume/distance as per your analysis requirement. But it is better to stick to one of them. After making the Counter reading entries save the document. System will issue out a message Documents were produced successfully Message no. ITOBFLTCON000

Section 2 Counter readings for Distance travelled and Hours run to be filled.

6. Check Counter reads posted in Report = IK07, Measurement document List

It will show you the details of Fuel consumed, Distance run, Hours run for a Fleet vehicle or Multiple Fleet vehicle 7. For planned maintenance on Fleet objects Counter based (say on Distance run, Fuel consumed or Hours run) Follow the same process as currently followed for Counter based planning Create Task List --> Create Counter based plan/plans based on counters already --> Keep updating the counters (Transaction IFCU) --> Plans scheduled (IP10/IP30Deadline monitoring) -> Order created and processed --> Settlement of orders --> Closure of orders