1 / 41

Using PowerLOG-J for Two Level Maintenance (TLM) and Logistics Management Information (LMI) System for TACOM LCMC Manage

Using PowerLOG-J for Two Level Maintenance (TLM) and Logistics Management Information (LMI) System for TACOM LCMC Managed Equipment. Bill Fuller, C.P.L. Camber Corporation 15 May 2007 . Agenda. TLM / LMI Overview Techniques Summary. Purpose of TACOM LCMC TLM/LMI Project.

stanislaus
Download Presentation

Using PowerLOG-J for Two Level Maintenance (TLM) and Logistics Management Information (LMI) System for TACOM LCMC Manage

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using PowerLOG-J for Two Level Maintenance (TLM) and Logistics Management Information (LMI) System for TACOM LCMC Managed Equipment Bill Fuller, C.P.L. Camber Corporation 15 May 2007

  2. Agenda • TLM / LMI Overview • Techniques • Summary PowerLOG Users Group May 2007

  3. Purpose of TACOM LCMC TLM/LMI Project • Establish a Standardized LMI System that supports TLM implementation • Establish a uniform process within TACOM LCMC for developing Logistics Products • Integrate with CCSS • MAC • MARC • BOIPFD • RPSTL • Two Level Technical Publications • Train the TACOM LCMC Practitioners • Align with DA TLM Initiatives Establish & Sustain a Seamless LMI System PowerLOG Users Group May 2007

  4. Some of the Challenges • Integrate existing logistics data from multiple independent sources into an LMI System • PMR • Technical Manuals • Task Frequency • Document Processes to Sustain the LMI system It Hasn’t Been Done Before PowerLOG Users Group May 2007

  5. TLM / LMI Program Overview Sustain System Develop TLM Processes and Procedures Update System Recom-mend Systems Identify Available Systems Identify Data Require-ments Select System Stand Up System PowerLOG-J Selected Update Logistics Support Package Update LMI Baseline to TLM Establish LMI Baseline Documented Detailed Processes Essential PowerLOG Users Group May 2007

  6. - - Updated MAC NMWR MARC Data - - BOIPFD PPL RPSTL Manuals/IETM TLM/LMI Process • TLM Checklist • Previous TLM Migration Panel Results (if available) • End Item Density Within South West Asia (SWA) (To Be Further Defined) • End Item Usage Within SWA (To Be Further Defined) • Average Monthly Demand History Within SWA (To Be Further Defined) • LMI Task Files (if available) • LMI Parts Files (CCSS Provisioning Master Record) • Fielded Version of Technical Manuals • Logistics Engineering "Hold-Files" (Logistics Package update To-Do-List) • Manpower Requirements Criteria (MARC) Data • Basis of Issue Plan Feeder Data (if available) • Objective Tables of Organization/Common Table of Allowances • Technical Data Package (TDP) UPDATE LMI BASELINE TO TLM UPDATE LOGISTICS SUPPORT PACKAGE ESTABLISH LMI BASELINE • Create Task List • Create LMI Task Files • Identify Discrepancies • Correct Discrepancies • Update Task Files and PPL IAW Latest Implementing Guidance for Maintenance and Supply Update of Logistics Support Packages Will be Based on an Agreed-Upon Strategy PowerLOG Users Group May 2007

  7. Test the Processes with Pilots • Heavy Combat PSID – Armored Vehicle Launched Bridge (AVLB) • Tactical Vehicle PSID – Semitrailer, 70T, M1000, ASV • Deploy PSID – 4K Fork Lift • Weapons PSID – Rifle, 5.56MM M4 • Field Artillery PSID – Howitzer Medium Self Propelled M109A6 • Tools PSID – Forward Repair System (FRS) • Chem/Bio Defense PSID – M58 Smoke Generator • Light Combat PSID – Fire SPT TM Vehicle BFIST • Soldier PSID – Containerized Field Kitchen PowerLOG Users Group May 2007

  8. Pilots In Progress • Pilot projects are nearing the Initial Baseline completed milestone • Every Pilot LIN has been different in some aspect affecting KEY data elements such as PCCN, PLISN, LCN, FGC in a fundamental manner • Many PCCNs contain multiple LINs with and/or without PCCN • Every LIN has displayed some or all of the seven deadly sins Pilot LMIS Are Expected to be Complete in Late June PowerLOG Users Group May 2007

  9. LMI System Government Sustained • TACOM LCMC Network • Two Environments • Development • Production • 500 GB Expandable • TACOM LCMC Portal • Ad Hoc Team Environment • Share Point Information Will Be Government Owned PowerLOG Users Group May 2007

  10. Logistics Product Update Issues • CCSS and PowerLOG-J synchronization • Recurring PTD Cycles • RPSTLs • CCSS or PowerLOG-J • Technical Publications • EMS Next Gen Seamless Integration PowerLOG Users Group May 2007

  11. Update Logistics Support Packages Packaging (LSAR-025) Facilities (LSAR-012) Update PPL (LSAR-036) Update MAC (LSAR- 004) LMI SYSTEMPowerLOG-J Update RPSTL (LSAR-030) Report to Update BOIP Report To Update MARC (LSAR- 001) ETM/IETM NMWR Manuals (Update) PowerLOG Users Group May 2007

  12. Some Techniques • Data Cleansing • Army Edits • Batch Load Templates • EZ MAC • Dealing with Legacy Problems PowerLOG Users Group May 2007

  13. Load Data into PowerLOG – • Assign LCN • PowerLOG can estimate where to assign orphaned PLISNs that are missing parents during import. It does this by analyzing the NHA, NHA IC, UOC, and indenture code, and assigning a Logistics Support Analysis Control Number (LCN) to each PLISN. The LCNs serves as the key data element within powerLOG to identify a product hierarchy. • Run PowerLOG Edits Cleanse Data Identified by Error List PowerLOG reports, utilities, and its user interface augment the powerLOG edit routines to assist in data cleansing Run PowerLOG Army Edits Cleanse Data Identified by Error List • Use Filters, Reports, PLISN View, and Utilities • Generate LSA-036 Report For Load into LMP Data Cleansing Process PowerLOG Users Group May 2007

  14. Army Edits PowerLOG Users Group May 2007

  15. Import: Tabular PowerLOG Users Group May 2007

  16. Flexible CSV Data Import Templates PowerLOG Users Group May 2007

  17. THE EZ-MAC Generating an “004 Report” (Maintenance Allocation Chart) with the EZ-MAC Application.

  18. EZ-MAC PROCESS Quality Review Quality Review INPUTS PowerLOG-J v1.5.1 loaded on the C:\ Drive and/or Server EZ-MAC application loaded on the C:\Drive and/or Server Current MAC (either in print or electronic) ENTER DATA to the 3 EZ-MAC worksheets (ezmac_ground.xls) REVIEW the MAC IMPORT A MAC 2361 to Power-LOG-J RUN the MAC EXPORT DATA to an .xmlfile COPY the templates to the LIN MAC Folder ERRORS REVISE the ezmac_ground.xls NO ERRORS RENAME REPORTS AND PLACE IN FILE PowerLOG Users Group May 2007

  19. EZ-MAC PROCESS – Inputs PowerLOG-J v1.5.1 loaded on your C:\ Drive or server. EZ-MAC does not work on any lower version. A printed or electronic copy of your MAC. EZ MAC loaded on your C:\Drive or server. EZ MAC has two files – ez-mac_ground.xls and mac2.xsl – that you will need to copy and paste into your LIN folder. PowerLOG Users Group May 2007

  20. EZ-MAC PROCESS – Enter the Data THE EZ-MAC TEMPLATE – Three Worksheets: mac, tools, and remarks PowerLOG Users Group May 2007

  21. 2.0 REPLACE EZ-MAC PROCESS – Enter the Data THE EZ-MAC TEMPLATE – The MAC Worksheet DO NOT rename the file. 2-digit Group Code heading. Will list as an error when importing. Ignore the error message – code will still import. Formatting Example: “0100” FGC has 3 separate task headings: Engine Assembly, Engine Mounts, and Lifting Brackets. Within the Engine Mounts and Lifting Brackets categories, several task lines appear. Note how the sequencing (-xx) and the Component/ Assembly column is input. Enter times un- der the appro-priate mainte-nance level. Enter the Function language accepted, per MIL STD 40051. PowerLOG Users Group May 2007

  22. EZ-MAC PROCESS – Enter the Data THE EZ-MAC TEMPLATE – The TOOLS Worksheet If more than 13 digits, the NSN will error out. Cells cannot be blank in this column; Use zeros as the default placeholder for missing NSNs. Do not wrap text in the Nomenclature column (Do not reformat any of the columns on any of the sheets.) PowerLOG Users Group May 2007

  23. EZ-MAC PROCESS – Enter the Data THE EZ-MAC TEMPLATE – The REMARKS Worksheet PowerLOG Users Group May 2007

  24. EZ-MAC PROCESS – Export the Data • Select Export MACWP • Select the Work Package Maintenance Level (as of this publication, select anything, per LOGSA; result will be the same). • Enter your Publication #, per the instruction. • Note the location of your file, read the Notes & Limitations, and click Okay. • Close the Excel file. You will get no notice that the file has exported. PowerLOG Users Group May 2007

  25. EZ-MAC PROCESS – Import the MAC Select Import | 2361 MAC and open the file. PowerLOG Users Group May 2007

  26. EZ-MAC PROCESS – Import the MAC into PowerLOG-J • An .html Error Report will open. The errors are grouped according to subject, and the Table of Contents displays hyperlinks to the groups. • Some common errors are listed here. • When you close the file, the files saves to the location of your MAC report • Correct your errors, either record-by-record within PowerLOG-J or in the EZ-MAC Excel file and import again (recommended).. PowerLOG Users Group May 2007

  27. EZ-MAC PROCESS – Run the MAC • Select Reports | Technical Manual | 004 Maintenance Allocation Chart from the menu. PowerLOG Users Group May 2007

  28. EZ-MAC PROCESS – MAC (.html) PowerLOG Users Group May 2007

  29. EZ-MAC PROCESS –MAC (.pdf) PowerLOG Users Group May 2007

  30. PowerLOG-J, TLM, LMI and Legacies • MAC – conforms to Mil-Std-40051 and is now based on task details in LMI System • Functional Group Codes vs LCN structure for RPSTL • Multiple PCCN/LIN combinations in single PMR • Multiple use items • Field and Sustainment SMR Codes in CCSS PowerLOG Users Group May 2007

  31. Summary • Provide a Standardized LMI System to Support Fact Based Logistics Decisions • Provide Processes To Assist in Conversion of Logistics Support Packages to TLM • Establish LMI System in TACOM LCMC Network available to all Equipment Managers • Seamless Integration to Logistics Support Packages Realizing the Dream of ILS PowerLOG Users Group May 2007

  32. TACOM LCMC TLM LMI Contacts • Steve Matthews, COR • TACOM LCMC ILSC Policies • (586) 574-7741 • DSN 786-7741 • steven.a.matthews@us.army.mi • Bill Fuller, Contract PM • Camber Corporation • (586) 795-5349 • wfuller@camber.com PowerLOG Users Group May 2007

  33. Questions? PowerLOG Users Group May 2007

  34. Back-Ups PowerLOG Users Group May 2007

  35. Army Edit Results with New Metrics PowerLOG Users Group May 2007

  36. PLISN Tree Audit Report PowerLOG Users Group May 2007

  37. BOM Output PowerLOG Users Group May 2007

  38. Seven Deadly Sins • Item SMR Coded Nonrepairable with Parts Breakdown – Alert the CIT Team • Part of the PCCN/Selected LCN Range but not attached to any Assembly or Part • No Indenture Code • SMR Code Blank or Incomplete • Recoverable Code in Error • SMR Coded Repairable Assembly with no Parts • Warning: Item Part of a Kit PowerLOG Users Group May 2007

  39. LSA-080 BOM Part II Error Listing PowerLOG Users Group May 2007

  40. Reports to help on Data review PowerLOG Users Group May 2007

  41. Establish Existing LMI Baseline Upload Existing PMR Existing PMR? Yes CROSSWALK(MAC/PMR/ RPSTL/ Tasks List/ TDP-BOM) Identify Available Data Build PMR in PowerLOG-J Existing LMI Baseline Established No Existing Task File? Build Task Records in PowerLOG-J Yes Define LMI LCN Structure No Create Task List The Existing LMI Baseline is “Established” after the PSID approved changes are input to the LIN file in PowerLOG-J. Technical Data Package? Create LCN Reparable Level PowerLOG Users Group May 2007

More Related