1 / 21

PM PRC Submitting a Proposed DLMS Change (PDC)

PM PRC Submitting a Proposed DLMS Change (PDC). August 2, 2011. Scroll to the page bottom. Process Change Page. At Page Bottom, Click Change Proposal . MS Word Document Opens. View Hidden Text. MS Word Document Opens. Print Hidden Text. In MS Word…. Click Word Options.

dillian
Download Presentation

PM PRC Submitting a Proposed DLMS Change (PDC)

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. PM PRC Submitting a Proposed DLMS Change (PDC) August 2, 2011

  2. Scroll to the page bottom Process Change Page

  3. At Page Bottom, Click Change Proposal

  4. MS Word Document Opens View Hidden Text

  5. MS Word Document Opens Print Hidden Text

  6. In MS Word… Click Word Options

  7. In MS Word… Select Display

  8. In MS Word… Print Hidden Text

  9. Preparing a PDC The form is protected, except for text fields required to complete the PDC. Instruction appear in blue text. Entry points on the PDC are clearly marked - Next: Navigating PRC Process

  10. Editing PDC Template Here is an example of entering the Technical Point of Contact (POC). - Next: Navigating PRC Process

  11. Reviewing the PDC When all the data is entered, reverse the hidden text option in “Word Options” to display the completed form. - Next: Writing A good PDC

  12. Writing a Good PDC • The development of a PDC is important The following will show bad and good examples of how to prepare a PDC - Next: Description

  13. “Description of Change” • This only requires a short summary. Enough to outline the scope of the work. For example: • “This change documents the procedures needed to add time stamp information (in addition to the current date information) to the LMARS database and the transactions that feed it. This will enable LMARS to report more accurate segment times. ” - Next: Background

  14. “Background” • Bad example: • Only date information currently provided to LMARS. Good example: In assigning logistics response time (LRT) for wholesale orders, there is a significant difference between 0.1 days and 1.0 days. Adding a time element to the current date requirement will allow greater granularity in measuring segment performance, especially, when the performance is less than one day. - Next: Procedure

  15. “Procedures” • Bad example: • Add time stamp to LMARS data. Good example: The following procedures will enable LMARS to calculate and report segment times with greater granularity: Enable LMARS database to store time information. For transactions capable of conveying time information (DLMS enhancements) populate the time conveyed in the transaction. For transactions that cannot convey time data (DLSS), DAAS to add “time transaction was received” data to LMARS database. Ensure systems sending DLMS transactions include time information. - Next: Advantage

  16. “Advantages” • Bad example: • Better granularity of LRT data. Good example: This change will enable LMARS to calculate and report segment time in hours (or fractions of days) , providing more accurate segment times for LRT metrics, and better consistency of data across the DoD supply chain.

  17. “Impact” • Bad example: • Unknown. Good example: Coordinate with SPRC to update processes and transactions needed to incorporate time stamp data into the appropriate DLMS transactions. For inbound transactions that do not include time stamps, DLA Transaction Services will develop and implement procedures to capture the time that transactions are received and store that information in the time field of the LMARS database. - Next: Publication

  18. “Publication” • Bad example: • No change. Good example: This change will impact the DLMS manual maintained by DLA Logistics Management Standards. - Next: ADC Process

  19. DLMS Manual Change Example Enclosure 1, SDR Procedures, DLMS Manual, Chapter 17 Revisions DoD 4000.25-M, Volume 2 (as revised by published ADCs) Revise as follows and renumber subsequent paragraphs. C17.3.2.10. Technical Data. Report missing and/or incomplete item technical information, e.g., name plate, operating handbook, logbook, precautionary markings, warranty data, engineering drawings and associated lists, specifications, standards process sheets, manuals, technical reports, catalog item identifications, and related information that are missing, illegible, incomplete and/or incorrect regardless of dollar value. When reparables are returned and the appropriate historical information/documentation, operator/maintenance logbooks, engine oil analysis, etc., as required by Government regulations, and/or technical manuals are not included, the receiving activity shall submit an SDR regardless of dollar value. Any additional costs incurred by the repairing depot/arsenal because of the missing data shall be charged to the originating activity. Submitter will ensure that the specific description of what documentation is missing is included in the remarks section. Report as an incorrect part number when technical data markings for the part number appear to be inconsistent with the specified NSN. Incorrect part discrepancies shall be submitted directly to the item manager. (Do not use to report an incorrect item received as described below. Refer to W-series discrepancy codes for most appropriate discrepancy code.) Use Strikethrough to indicate existing text to be deleted Include Paragraph Numbers Cite Manual Name, Number, Volume, & Chapter - Next: ADC Process

  20. Questions ? 20

  21. Thank You! 21

More Related