Preparing Linear Network Data for SAP Ehp5 Functionality

Transcription

1 Preparing Linear Network Data for SAP Ehp5 Functionality Stacy Sauer BNSF Railway Supported by: Produced by:

2 Overview Section 1- BNSF Background Section 2- Legacy System Challenges Section 3- Ehp5 Linear Functionality Section 4- Comprehensive Linear Network Goals Section 5- SAP Ehp6 Network Functionality Section 6- Linear Features on Master Data Section 7- Linear Features Maintenance Transactions Questions

3 Takeaway Lessons How to best take a hierarchical structure and design a linear network How to make best use of linear feature extensions and linear distributive characteristics Utilizing the linear features on work management transactions with linear assets

4 Section 1 BNSF Background Information BNSF Network Statistics BNSF System Map BNSF Engineering Asset Management Roadmap Supported by: Produced by:

5 BNSF Network Statistics Count (approx.) Employees 40,000 Miles of Track 40,000 Yard Facilities 300 Switches and Signals 44,000 Road Crossings 26,000 Bridges and Culverts 67,000 Track Repair Equipment 17,000 Locomotives Freight Cars 6,000 (owned) 40k (owned) 220k (on track avg.) EAM System Records 15,000,000

6 BNSF System Map

7 Engineering Asset Management Roadmap Step 1 Single Asset Repository Step 2 Common Work Management Step 3 Improved Planning & Scheduling / Analytics -Services Turnout # lbs BOM Template Turnout Asset -Material Number -Quantity Required -Item Text Work Order Switch Frog Switch Ties Switch Type Switch Panel Switch Points Stock Rail Frog Type Guard Rail Frog Insert 30 Day Turnout Inspection Maintenance Plan Template -Services -Maintenance Plan description -Task List Associated -Frequency -Tolerances -Order Generation Factor -Completion Requirement -Calendar -Maintenance Plan Sort Field 30 Day Turnout Inspection Task List Template -Services -Task List description -Operation Description -Craft Required -Duration -Number of Resources -Description -Linked Document -Materials - Work Steps - Detailed Procedures - Cost - Requirements - Labor - Material - Equipment - Services Consolidate all Engineering asset data into Asset Repository Replace legacy systems with new Engineering work management systems using SAP PM New Engineering Planning, Scheduling & Analytical Tools

8 Section 2 Legacy Systems Master Data Challenges Legacy Network Data Challenges Validating Data Conversion of Data to SAP Supported by: Produced by:

9 Legacy Network Data Challenges Significant number of legacy systems developed over 100+ year history FLOC and Equipment records in separate systems Not always a tie between the records End state would result in a single system of record Location specificity was a key driver of the project Affects safety Affects planning / scheduling Long term goal was the elimination of as many legacy network and fixed equipment data repositories as possible 8

10 Validating Data- Lessons Learned Subject Matter Experts Important What data is essential What is not value add What never fully realized Clean Slate with New Linear Model Escape poor processes, execution, data quality and unnecessary complexity Standardize! Standardize! Standardize! Develop critical standard building blocks o Turnout, Road Crossing, Pipe Segment, Junctions & Transmission Towers etc. Design Tactically, Implement Strategically Break design teams into business units with similar equipment/processes Have project team work to fold all designs together after sessions 9

11 Conversion of Data to SAP NRX Asset Hub was selected for data work prior to uploading master data in SAP: Linear network Linear Distributive Characteristics Loading of point assets Master data interfaces Creation of BOMs, Task Lists & Maint. Plans NRX Asset Hub Manager Viewer 10

12 Section 3 Ehp5 Linear Functionality Linear Field Extensions Marker Definitions and Linear Reference Patterns Distributive Characteristic Functionality Distributive Characteristic Examples Supported by: Produced by:

13 Linear Field Extensions 12

14 Marker Definitions and Linear Reference Patterns Markers are used to describe relative position of linear object as opposed to absolute position Markers are critical in adoption by field resources given their obvious impact on work order identification, routing and completion Linear Reference Patterns can be used to string together markers, FLOCs and Equipment in a sequence to represent a network It is NOT true linear object linking however 13

15 Linear Distributive Characteristic Functionality Linear characteristics can now have multiple single values as prescribed by linear length This allows very large linear objects to be created and maintained where the only reason to break continuity is based upon attribution changes 14

16 Linear Distributive Characteristic Examples 15

17 Section 4 Comprehensive Linear Network Goals Composite Hierarchy Linear Attribution Level Common Operational View Level Flexible Structure for Maintainers Supported by: Produced by:

18 Composite Hierarchy Hierarchy composed of linear and point assets maintained by, but not limited to, one of three departments Track, Signal, Structures All structures follow the same uniform design to level 4 with network owned by Track Department 17

19 Linear Attribution Level Linear assets & attributes are commonly maintained in GIS or other spatial applications A beneficial common hierarchy to: Modify attributes in GIS Interface to SAP Maintained in SAP at a superior level & cascaded down to children records Examples: Planner Group, Work centers, Cost Center, Speeds, Geo Political Boundaries 18

20 Common Operational View Level TMDS is an operational view of the network. A common structural view of a network with maintenance and operations Simplifies future integration between departments Communication of these windows between maintenance and operations applications is critical from a compliance and safety perspective. 19

21 Flexible Structure Track Department owns to level 4. Other groups have flexible design below level 4 Use plug and play approach for point assets 20

22 Section 5 SAP Ehp6 Network Functionality Ehp6 Improvements & Comparison Network Modeling Advantages Supported by: Produced by:

23 Ehp6 Improvements & Comparison Delivered in EHP5 Enhancement of technical objects functions (functional location and equipment) and classification system to support the definition of a linear asset Enhancement of work order processing to support linear work definition, including work orders, confirmations, and maintenance plans Enhancement of notifications, measurement points, counters, and measurement documents to support linear information Reports for all of the above Account assignment on work order operation level Planned in EHP6 New linear network reference object that is a peer of FLOC and EQUIP True network object to network object (peer) relationships. Ability to proportion costing based on linear fields New transactions to create / change/display Object Networks New List Report for Networks New Graphic Display for Networks New Multi Level List Report for Networks New transaction to create / change / display Network Attribute Values

24 Network Modeling Advantages True peer to peer relationships can be represented by associating linknode-link-node assets in series Multiple networks can be constructed utilizing different (but not unique) groupings of functional locations, equipment or both Multiple parentage can be supported in the case of rail diamonds or pipeline junctions or transmission towers. o This has long been a problem with a traditional hierarchical view of the maintenance landscape 23

25 Section 6 Linear Features on Master Data Functional Locations / Equipment Maintenance Plan Items Measurement Points Supported by: Produced by:

26 Functional Locations/Equipment Linear Data Tab on Reference Objects Linear Data Screen Object on Location Tab 25

27 Maintenance Plan Items Addition of Linear Fields on Maintenance Items allows for linear definition to factor into segregation of work order generation Change in attribution drives change in frequency Change in responsible party drives change in maintenance work center 26

28 Measurement Points Allows for linear definition of the absolute position of the point on the linear record Allows for the relative position of a measurement point along a linear record 27

29 Section 7 Linear Features on Maintenance Transactions Notifications Orders Time Confirmations Supported by: Produced by:

30 Maintenance Notifications Linear Fields on Maintenance Notifications can be configured to copy from the reference object by default If entire FLOC or Equip record is covered by the notification request, then nothing further is required. If defect is a point feature, the maintenance request can be modified to represent a specific absolute or relative point on the object. 29

31 Maintenance Orders Linear Data Screen Object on Location Tab Linear Data Fields on the Operation Tab Allows for single operations to now have linear definition applied based on Attribution or Responsible Party Changes 30

32 Time Confirmations Completions can now be expressed in distance as additional information on work confirmations Items like: Corrected/Repaired Distance Inspected Distance Installed Distance etc. 31

33 Lessons Learned Standardize building blocks for your hierarchy Visualize and build the network as maintainers in the field see it Insist on a common hierarchy for all users of the maintenance system Use linear reference pattern where none exists today Engage field personnel for what is important about network asset Maintain linear distributive features on a single level Make the network hierarchy levels mean something Default reference object info onto orders and modify as required

34 Questions? 33

35 Stacy Sauer Senior Manager, Engineering Systems BNSF Railway Supported by: Produced by:

36 Noel Fagan Vice President, Vesta Global Supported by: Produced by: