US Army: open %203rd deltas

8/14/2019 US Army: open %203rd deltas

http://slidepdf.com/reader/full/us-army-open-203rd-deltas 1/22

3rd Deployment DeltasAs of Thursday, August 11, 2005 of 22

Delta ID: 1002

Change Req ID: 841

ORIGINATOR J Pruitt PROJECT LMP STATUSOpen

IMPACT 3rd Deployment DATE 6 /8 /2004

TITLE 3rd Deployment Reqr-Automated Changes for Obligation/De-obligation on Projects

NARRATIVE(Entered by J Pruitt) Need automated changes to projects when there are quantity changes,

authorization changes and other various project changes. These changes are currently sent tothe controllers business workplace. Need also to review the the process to determine if the legacyProgram Notice needs developed or if the business workplace is sufficient to documentautomated changes to provide audit trail. See attached document for further requirementsdescription. Note: This issue has been partially documented by 2nd deployment Delta #210and Issue #811. The project changes need to be automated from the current labor intensivemanual method. 10Jun04 IRC opened this issue at Low priority, and assigned to J Pruitt.Assignee to ensure that appropriate personnel are advised of this potential gap prior to conduct

of third deployment SDLs. At that time, a delta requirement will be identified or it will bedetermined that there is no functionality gap; in either case, assignee will recommend closure of

NAME REMARK DATE REMARKS

Delta ID: 1003

Change Req ID: 842



TITLE 3rd Deployment Reqr-Missing Business Process Needed on Material Receipt on Closed Projects

NARRATIVE(Entered by J Pruitt) Material is received from NICP/DLA, while the project is closed. This

material must have a cost collector (overhead project) to accumulate the material info such asNIIN, NIIN price, quantity, total dollar involved, etc. in order to transfer from the overhead to adirect project. In legacy, this process covered A, Q or Z closed PRONs, which are temporarilyclosed, closed or final billed respectively. For example, material would be received against a Qclosed PRON and the information would be collected under in-direct JO/PCN Z94ZZ4. Actionwas then required by the material/parts manager to transfer the dollars/material to a benefitingdirect JO/PCN. Missing business process will impact depot financial status and materialmanagement. 10Jun04 IRC opened this issue at Low priority, and assigned to J Pruitt. Assigneeto ensure that appropriate personnel are advised of this potential gap prior to conduct of third

deployment SDLs. At that time, a delta requirement will be identified or it will be determinedthat there is no functionality gap; in either case, assignee will recommend closure of the issue.




As of Thursday, August 11, 2005 of 22

Delta ID: 1004

Change Req ID: 843



TITLE 3rd Deployment Reqr-ZPP01 Transaction Development Needed

NARRATIVE(Entered by J Pruitt) ZPP01 transaction provides for R-BOM update and also a Parts Analysis tool.

There are many other requirements that need to be addressed to make this process/reportcomplete, which have been previously provided to the developers such as roll-ups by PartsManager Code, additional legacy data migration needs and data elements that need to beadded. There is a Change Request CR#1015 on this process. This process also has commandimplications that have not been totally addressed, some of which the CR addresses. Impacts R-BOM updates and material management capability at depots and arsenals. Also has commandimpact on R-BOM for pre-positioning material. 10Jun04 IRC opened this issue at Low priority,and assigned to J Pruitt. Assignee to ensure that appropriate personnel are advised of thispotential gap prior to conduct of third deployment SDLs. At that time, a delta requirement willbe identified or it will be determined that there is no functionality gap; in either case, assigneewill recommend closure of the issue.


Delta ID: 1005

Change Req ID: 844



TITLE 2nd/3rd Deployment Reqr-Parts Analysis Report TYAD Report #72

NARRATIVE(Entered by J Pruitt) This report does not meet the requirements for 2nd/3rd deployment sites.

An example is that the Parts Manager Code needs to be added. In addition, the report needs tohave an option to sort by Parts Manager Code and provide roll-ups by the Parts Manager Code.The Depot Overhaul Factor (DOF) is not included as a data element, which is critical to depotsthat currently forecast material requirements. Other elements needed are total requirement andremaining requirement, based on the DOF. This report is going to need a full review at somepoint in time before 2nd/3rd deployment can have requirements met. 2nd and 3rd deploymentsites will not be able to manage material requirements for projects. 10Jun04 IRC opened thisissue at Low priority, and assigned to J Pruitt. Assignee to ensure that appropriate personnel areadvised of this potential gap prior to conduct of third deployment SDLs. At that time, a deltarequirement will be identified or it will be determined that there is no functionality gap; in either case, assignee will recommend closure of the issue.





Delta ID: 1006

Change Req ID: 845



TITLE 3rd Deployment Reqr-CATS Labor Reporting

NARRATIVE(Entered by J Pruitt) There is a need for a work center report/listing/table that will identify the

project, order, seq number, operation number, operation description, man-hour standard, etc. Areport/listing would be an ideal tool to assist supervisor/time reporting personnel to ensure/verifyentered data into CATS is accurate. This tool would also help reduce rejects, assistmanagement personnel reviewing CATS data/rejects. This could involve building some newtables to accommodate.There is also a need for single user input when a new/change employeedata is entered into CATS, rather than the current dual entry of new/change employee intoCATS and also adding/changing the employee data into ATAAPS. This could be accomplishedby changing the CATS/ATAAPS interface or by making the two systems interface on a real or near real time basis. Provide needed report, listing or table to assist time reporting peronnel.Also, eliminate dual reporting between CATS and ATAAPS on employee add/change, which isa very labor intensive process. 10Jun04 IRC opened this issue at Low priority, and assigned to JPruitt. Assignee to ensure that appropriate personnel are advised of this potential gap prior toconduct of third deployment SDLs. At that time, a delta requirement will be identified or it willbe determined that there is no functionality gap; in either case, assignee will recommend closureof the issue.


Delta ID: 1007

Change Req ID: 846



TITLE 3rd Deployment Reqr-Project/Program Decrease or Cancellation Business Process Required

NARRATIVE(Entered by J Pruitt) There is not a clear business process to cover the requirements for program

cancellation/transfer of costs (legacy X1 PRON process). This process is required when a programhas started, the program has costs incurred which could include man-hours, materials and/or other costs, and the program is subsequently cancelled by the command. The command issuesan X1 PRON to cover costs incurred for cancellation. Costs would then be transferred from thecancelled progam to the X1 PRON. Financial and inventory problems will result from thisbusiness process not addressed. 10Jun04 IRC opened this issue at Low priority, and assigned to JPruitt. Assignee to ensure that appropriate personnel are advised of this potential gap prior toconduct of third deployment SDLs. At that time, a delta requirement will be identified or it willbe determined that there is no functionality gap; in either case, assignee will recommend closure

of the issue.





Delta ID: 1008

Change Req ID: 847



TITLE 3rd Deployment Reqr-Screen Improvements Needed on Material Movement Actions

NARRATIVE(Entered by J Pruitt) When moving thru material movement screens, the NIIN, batch #’s, transfer

order #’s, and goods receipt #’s should be following thru so they don’t have to keep re-enteringand having to annotate all of these numbers on the work order. Note: Entered for Sherry PadillaSIAD SME. Improvements in screen data retention will improve productivity, reduce errors andalso reduce the current labor intensive manual effort of re-entering repetitive data. 10Jun04 IRCopened this issue at Low priority, and assigned to J Pruitt. Assignee to ensure that appropriatepersonnel are advised of this potential gap prior to conduct of third deployment SDLs. At thattime, a delta requirement will be identified or it will be determined that there is no functionalitygap; in either case, assignee will recommend closure of the issue.


Delta ID: 1009

Change Req ID: 848



TITLE 3rd Deployment Reqr-Screen Improvements needed as Related to Drill-down in Screens

NARRATIVE(Entered by J Pruitt) Have to drill down to many screens to process actions. Examples of the

number of screens to drill down are:Movement into Maintenance: Serial # - 55 Non serial # -42, Movement out of Maintenance: Serial # - 71 Non serial # - 60, Destruct document: Serial #'s- 80 Non serial # - 67, New Procurement/Field Return Receipt: Serial # - 32 Non serial # - 28,MRO/Delivery Processing, MRO - 35, Addresses: 38, Address override: 40, WH changes: 38,Consolidations: 37, FMS Changes: 37. Realize that in some MRO cases more than ontransaction will need to be done i.e., WH change plus consolidation, plus Address override.These totals just reflect one variable. Should have a pick screen to determine what types of transactions are required. When these are selected, a screen comes up with those items thatwere checked IE, condition change, NIIN change, ser #/Lot # change, stock transfer etc. Onescreen is filled out for the process and the data filters down to the required screens. Screen dataimprovements will improve productivity, reduce errors and reduce labor intensive effort to drill-down into various screens. Note: Entered for Sherry Padilla SIAD SME. 10Jun04 IRC openedthis issue at Low priority, and assigned to J Pruitt. Assignee to ensure that appropriate personnelare advised of this potential gap prior to conduct of third deployment SDLs. At that time, a deltarequirement will be identified or it will be determined that there is no functionality gap; in either

case, assignee will recommend closure of the issue.





Delta ID: 1010

Change Req ID: 849



TITLE 3rd Deployment Reqr-Serialized Inventory Quantity

NARRATIVE(Entered by J Pruitt) LMP has inventory by qty only. If the quantity matches record does not

require that serial numbers be verified. If qty does not match then LMP wants you to reconcilethe serial numbers offline and then make the adjustment to the quantity. Does not verify serialnumbers up front. To pull an inventory by serial numbers, serial numbers are copied and pastedto an excel spreadsheet then printed so they can be physically verified. After they are verified,then they need to be hand entered into LMP, which then creates more problems. LMP shouldallow a list of serial numbers by location to be selected, and then only select the serial number (s) that are erroneous, which would eliminate input errors and increase the process time. Note:Entered for Sherry Padilla SIAD SME. Would improve productivity by reducing input errors andalso reduce labor intensive manual methods. 10Jun04 IRC opened this issue at Low priority, andassigned to J Pruitt. Assignee to ensure that appropriate personnel are advised of this potentialgap prior to conduct of third deployment SDLs. At that time, a delta requirement will beidentified or it will be determined that there is no functionality gap; in either case, assignee willrecommend closure of the issue.


Delta ID: 1011

Change Req ID: 850



TITLE 3rd Deployment Reqr-Generated MRO SIAD

NARRATIVE(Entered by J Pruitt) When an MRO is generated, LMP system has only up to 23 partials (XAX-

XZX). For Sierra Army Depot (SIAD) this is not enough. SIAD has large items to ship that requiremore than 23 partials to ship one each. Talked with Joe Angelastro (CSC) MRO programmer and he stated that since we were 3rd out they would not address until then. Discussed how wecould make it work by using the TCN XXX from XAX thur XZX and then starting from XAA thruXAZ and so on. Note: Entered for Sherry Padilla SIAD SME. MRO requirements for SIAD willnot be met. 10Jun04 IRC opened this issue at Low priority, and assigned to J Pruitt. Assignee toensure that appropriate personnel are advised of this potential gap prior to conduct of thirddeployment SDLs. At that time, a delta requirement will be identified or it will be determinedthat there is no functionality gap; in either case, assignee will recommend closure of the issue.





Delta ID: 1013

Change Req ID: 851

ORIGINATOR PROJECT LMP STATUSOpen


TITLE 3rd Deployment Reqr-Serialized Item with System Generated Serial Numbers

NARRATIVEProblem encountered during the entry of serialized items. SAP applies system generated serial

numbers when actions are not completed during a processing day. Ex: Rec'd shipment of 5,000serial numbered items, in work day could only input 3,000. SAP populated other 2,000 serialnumbers with system generated serial numbers. Those 2,000 serial numbers have to be changedto correct serial number. Note: Entered for Sherry Padilla SIAD SME. Would improveproductivity, reduce errors and reduce labor intensive manual rework. Propose that system holdthe receipt document by saving and when all serial numbers were loaded, then push the buttonfor actual posting to the system. This would then transceive to the UIT and NICP with the correctserial numbers and would alleviate any rework. 10Jun04 IRC opened this issue at Low priority,and assigned to J Pruitt. Assignee to ensure that appropriate personnel are advised of thispotential gap prior to conduct of third deployment SDLs. At that time, a delta requirement willbe identified or it will be determined that there is no functionality gap; in either case, assigneewill recommend closure of the issue.


Delta ID: 1014

Change Req ID: 852


IMPACT 3rd Deployment DATE 6 /18/2004

TITLE 2nd/3rd Deployment Reqr-Improved Requisitioning Process

NARRATIVE[Entered by jpruitt, 6/18/04] Attached LMP Purchase Requisitioning Process has 3 options.

Visiting Depot SMEs at TYAD reached consensus that option 2 was not acceptable for our depots, although option 2 supports TYAD stabilization. All visiting SMEs agreed that option 3was the requirement for future deployments, with option 3 development required "prior to 2nddeployment suspense date". Requisitioner actions would be improved with a front-end screenthat will automate the process. Improvements will increase productivity, reduce errors and reducelabor intensive manual efforts, as estimated to be 10 minutes per in LMP to 1 minute. 24Jun04IRC opened this issue at Low priority, and assigned to J Pruitt. Assignee to ensure thatappropriate personnel are advised of this potential gap prior to conduct of third deploymentSDLs. At that time, a delta requirement will be identified or it will be determined that there is nofunctionality gap; in either case, assignee will recommend closure of the issue.





Delta ID: 1015

Change Req ID: 853



TITLE 2nd/3rd Deployment Reqr-Mapping from MSM003 Maint Material Req Suspense File

NARRATIVE[Entered by jpruitt, 6/18/04] Need to address mapping from the legacy Maint Material Request

Suspense File MSM003, which primarily maintains an on-line suspense of items that have beenrequisitioned. Once an item is received through supply, the suspense is then cleared. I checkedwith data sources (latest MDR info) and there has not been any mapping from the MSM003 toLMP. These requisition suspense requirements need to be addressed for 2nd/3rd deployments,along with applicable mapping from legacy and any related training development. If mappingand any required development required is not performed, significant legacy data contained inMSM003 will be lost during 2nd and 3rd deployments. 24Jun04 IRC opened this issue at Lowpriority, and assigned to J Pruitt. Assignee to ensure that appropriate personnel are advised of this potential gap prior to conduct of third deployment SDLs. At that time, a delta requirementwill be identified or it will be determined that there is no functionality gap; in either case,assignee will recommend closure of the issue.


Delta ID: 1016

Change Req ID: 854



TITLE 3rd Deployment Reqr-Screens, Tables, Files for Maintaining Various Controller Codes

NARRATIVE[Entered by jpruitt, 6/18/04] Attended a workshop at TYAD related to Program Acceptance.

Workshop included a review of controller codes for TYAD plant 1201. CSC is currentlymaintaining tables/files in SAP. Depots need applicable screens, tables, files built so the depotcan maintain the data. This data can change on a daily basis. Currently, there are many files inlegacy that need to be reviewed to determine if CSC has addressed all our businessrequirements related to controller codes. The current legacy files include DPM004 Mutual DataFile, PCM021 Manager's Pending Actions File and MSM011 Parameter Control File. There maybe other files that need to be reviewed. Besides development required, the files need to bereviewed for applicable mapping from legacy to LMP and also applicable training development.Depots need to control the applicable controller code tables, with very limited access.Additionally, there will be a loss of important legacy file information that actually needs to bemigrated to SAP. 24Jun04 IRC opened this issue at Low priority, and assigned to J Pruitt.Assignee to ensure that appropriate personnel are advised of this potential gap prior to conduct

of third deployment SDLs. At that time, a delta requirement will be identified or it will bedetermined that there is no functionality gap; in either case, assignee will recommend closure of the issue.





Delta ID: 1017

Change Req ID: 855



TITLE 2nd/3rd Deployment Reqr-Benchstock Development, Mapping and Training

NARRATIVE[Entered by jpruitt, 6/18/04] Bench stock was originally addressed during Regression Testing with

PTR #3791 and CR #1360. TYAD went live with only limited bench stock development usingROP (Re-order Point) functionality in SAP. Bench stock was not captured as a delta during theAMCOM SDL, based upon my information. Subsequently, we held several meetings/sent emailsafter the AMCOM SDL, where the requirements were being identified. I checked with CSC,finding no TYAD bench stock documentation (Go-By or other). 2nd and 3rd deployment sites willrequire further bench stock development in the LMP solution. This will include legacy datamigration from MSM038 Bench Stock History File and MSM039 Bench Stock Cross ReferenceFile. There may be other sources. See also PTR #3791 and CR #1360. Adequatedocumentation and training will also need to be addressed. There will be a loss of importantlegacy file information that needs to be migrated to SAP. Also, functionality and managementcapability will be diminished. Training will not be available. 24Jun04 IRC opened this issue atLow priority, and assigned to J Pruitt. Assignee to ensure that appropriate personnel are advisedof this potential gap prior to conduct of third deployment SDLs. At that time, a delta requirementwill be identified or it will be determined that there is no functionality gap; in either case,assignee will recommend closure of the issue.


Delta ID: 1018

Change Req ID: 856



TITLE 3rd Deployment Reqr-Process Costing for Depots and Arsenals

NARRATIVE[Entered by jpruitt, 6/21/04] Process costing is a method for distributing direct labor

charges/production counts from process work center operations, i.e., as painting, plating,cleaning, abrasive cleaning, inspection, heat treat and foundry melt operations where it isimpractical to identify direct effort on numerous job orders. Rather than charge these operationsto overhead and include in the standard overhead rate, a capability to distribute these labor hours, prod counts and costs back across active job orders is required in the LMP solution.Process Costing needs developed/configured for depots and arsenal requirements. This willinclude any applicable legacy data migration. Documentation and training will also need to beaddressed. Output reports will also be required for development. Note: Process Costing is amajor local unique at ANAD while RIA's functionality is embedded within their MRP system. If

Process Costing is not developed, depots and arsenals must rely on very labor intensive manhour and production reporting or add the operations to overhead. Neither method is acceptablealternative since manual methods are prone to error and/or non-reporting and adding these typeoperations to overhead rates impacts ability to properly estimate work and also the work center scheduling/capacity requirements that must be developed. Process Costing was developed/usedto improve labor and production reporting and to also answer audit findings. 24Jun04 IRCopened this issue at Low priority, and assigned to J Pruitt. Assignee to ensure that appropriatepersonnel are advised of this potential gap prior to conduct of third deployment SDLs. At thattime, a delta requirement will be identified or it will be determined that there is no functionalitygap; in either case, assignee will recommend closure of the issue.





Delta ID: 1019

Change Req ID: 857

ORIGINATOR J Pruitt PROJECT LMP STATUS

Open


TITLE 3rd Deployment Reqr-Indicator "Y" or "N" DPM004 for DOF Material 10% or Lower

NARRATIVE[Entered by jpruitt, 6/21/04] Missing business process for requistioning area (ISA), controlled by

Maint Mutual Data File DPM004. DPM004 file S/S 0611 provides a "Y" or "N" indicator thatcontrols forecasted repair parts with DOF of .10 or less. Indicator "Y" equals requisitions for materials with DOF of .10 or less will pass to ISA, on to source of supply. Indicator "N" equalsrequisitions for materials with DOF of .10 or less will not pass to ISA, then on to source of supply.Process control in the legacy system helps the depot reduce excess new material with low DOF,thereby reducing operating expenses/overhead rates. The DOF of .10 allows the material/partsmanager to create backorder for material only when needed, allows the low DOF material to beentered into the Mortality Data History File PCM004 which also provides a cost estimate for these

items. Allows better mgmt of materials during project execution, better control of excess andimproved project closure. Estimates for projects are more accurate to include all items on BOM,better control of excess by submitting firm purchase order/req for low DOF items and improvedlabor rates by not adding excess material into rates. 24Jun04 IRC opened this issue at Lowpriority, and assigned to J Pruitt. Assignee to ensure that appropriate personnel are advised of this potential gap prior to conduct of third deployment SDLs. At that time, a delta requirementwill be identified or it will be determined that there is no functionality gap; in either case,assignee will recommend closure of the issue.


Delta ID: 1020Change Req ID: 858



TITLE 3rd Deployment Reqr-Flagging BOM/NIIN of Mandatory Replacement Parts in DMWR

NARRATIVE[Entered by jpruitt, 6/21/04] Need improved control of mandatory replacement parts as specified

in the Depot Maint Work Requirement, usually the Statement/Scope of Work reference for overhaul. This business need could be accomplished by "flagging" the NIIN, or by other methodology. I do not believe the requirement was documented as I had requested during 2nd

deployment SDL. This type of improved control would be of great benefit to depots/arsenals andthe commands. Improved BOM for mandatory replacement parts listed in DMWR, or other.There would also be improved provisioning by the command and improved availability of mandatory replacement parts. 24Jun04 IRC opened this issue at Low priority, and assigned to JPruitt. Assignee to ensure that appropriate personnel are advised of this potential gap prior toconduct of third deployment SDLs. At that time, a delta requirement will be identified or it willbe determined that there is no functionality gap; in either case, assignee will recommend closure





Delta ID: 1021

Change Req ID: 859



TITLE 3rd Deployment Reqr-Travel Orders

NARRATIVE[Entered by jpruitt, 6/21/04] LMP in conj with ODS was not set up properly for Travel Orders

having more than one(1) JO Number, i.e., Travel Order Number HUG9928TC40561 is issued withJO Number 180001324; $2000.00: JO Number 180004562; $3000.00: Two 21T2s areestablished for HUG9928TC40561 as an Undelivered Order. SDS would accumulate the 21T2and when a voucher is filed and disbursement made ODS would disburse against theaccumulated if same EOR. LMP gives each a separate invoice number. Disbursement is madeby DFAS lets say for $4,000.00. ODS picks up the first invoice for $2,000.00 and will obligateanother $2,000.00. Records are over obligated by $2,000.00. The records must be adjusted bythe $2,000.00. Over obligation is considered an Antidefiency Act Violation and should bereported. Workaround is to call DFAS and have them correct the disbursement.(Not a GoodBusiness Practice and will not pass GAO/AAA audit.) LMP needs JO Numbers under the sameEOR and document number to accumulate. Need improved financial management to avoidaudit findings. Note: Entered for Richard Hughes RRAD SME. 24Jun04 IRC opened this issue atLow priority, and assigned to J Pruitt. Assignee to ensure that appropriate personnel are advisedof this potential gap prior to conduct of third deployment SDLs. At that time, a deltarequirement will be identified or it will be determined that there is no functionality gap; in either case, assignee will recommend closure of the issue.


Delta ID: 1022

Change Req ID: 863



TITLE 3rd Deployment Reqr-Accrual Accounting

NARRATIVE[Entered by jpruitt, 6/21/04] Need LMP designed to properly address accrual accounting. See

attached document. Improve accrual accounting and avoid possibe problems with auditors.Note: Entered for Richard Hughes RRAD SME. 24Jun04 IRC opened this issue at Low priority,and assigned to J Pruitt. Assignee to ensure that appropriate personnel are advised of thispotential gap prior to conduct of third deployment SDLs. At that time, a delta requirement willbe identified or it will be determined that there is no functionality gap; in either case, assigneewill recommend closure of the issue.





Delta ID: 1023

Change Req ID: 864



TITLE 3rd Deployment Reqr-Backorder Transfer Automated Capability

NARRATIVE[Entered by jpruitt, 6/21/04] Depots and arsenals need automated rather than manual backorder

transfer capability from one project/order to another. See attached document. Improvements arenecessary for the current manual method of transferring backorders which is currently very labor intensive, increases errors and leaves managers not knowing the real backorder requistionrequirement from a maintenance depot or arsenal. 24Jun04 IRC opened this issue at Lowpriority, and assigned to J Pruitt. Assignee to ensure that appropriate personnel are advised of this potential gap prior to conduct of third deployment SDLs. At that time, a delta requirementwill be identified or it will be determined that there is no functionality gap; in either case,assignee will recommend closure of the issue.


Delta ID: 1024

Change Req ID: 865



TITLE 3rd Deployment Reqr-Quality Re-Inpect Characteristic Needs Automated

NARRATIVE[Entered by jpruitt, 6/22/04] When a reject is written, an Inspector has to manually enter a

Characteristic for a re-inspection. This creates room for error and incompletions for the correctionof that reject if the inspector forgets to add a re-inspect characteristic. A function needs to beadded in SAP to automatically create a re-inspection characteristic when a reject characteristic iscreated. Current method is manual, can cause errors or can leave incomplete data as related tore-inpection characteristics. Note: Entered for Doug Crisp RRAD SME. 24Jun04 IRC opened thisissue at Low priority, and assigned to J Pruitt. Assignee to ensure that appropriate personnel areadvised of this potential gap prior to conduct of third deployment SDLs. At that time, a deltarequirement will be identified or it will be determined that there is no functionality gap; in either case, assignee will recommend closure of the issue.





Delta ID: 1025

Change Req ID: 866



TITLE 3rd Deployment Reqr-Quality Production Order Access

NARRATIVE[Entered by jpruitt, 6/22/04] Only one user can access a production order on the system at a time.

This creates down time when others need to access the same production order. Need to improveproduction order access to improve productivity. Note: Entered for Doug Crisp RRAD SME.24Jun04 IRC opened this issue at Low priority, and assigned to J Pruitt. Assignee to ensure thatappropriate personnel are advised of this potential gap prior to conduct of third deploymentSDLs. At that time, a delta requirement will be identified or it will be determined that there is nofunctionality gap; in either case, assignee will recommend closure of the issue.


Delta ID: 1026

Change Req ID: 867



TITLE 3rd Deployment Reqr-Quality Need Capability to Track Defects on Complex Orders

NARRATIVE[Entered by jpruitt, 6/22/04] Defects are not tracked on complex order for subassys of major assy

other than by inserting defective subassy comments in long text. If prod order no./system serialno. or next higher assy number not known, then it will be near impossible to find data on subassy

in long text. Need design change so search criteria can be met on subassys to end item.Trigger/field could be added to prod order so when subassy NIIN/PN was entered, it would beaccepted by prod order. Due to this being a sub-component of the prod order/end item, a qty onthe prod order would not be generated, just the sub-field that data would be entered into andwould be searchable by subassy NIIN/PN. List of sub-comp NIIN's/PN's would be generated by thematerial master that could be directly related to the major end item NIIN/prod order. Only whenprod order NIIN is entered to record would it generate count added to that prod order qty. Wewould then have capability to search for historical defect/comments data. Inability to search or manual method to search for defects/comments on subassemblies to end item. Note: Enteredfor Doug Crisp RRAD SME. 24Jun04 IRC opened this issue at Low priority, and assigned to JPruitt. Assignee to ensure that appropriate personnel are advised of this potential gap prior toconduct of third deployment SDLs. At that time, a delta requirement will be identified or it willbe determined that there is no functionality gap; in either case, assignee will recommend closureof the issue.





Delta ID: 1027

Change Req ID: 870



TITLE 2nd/3rd Deployment Reqr-Project/Order Closure Processes Missing or Need Automation

NARRATIVEDescription of issue:Need to address missing business processes related to Project/Order Closure

and need to address automation needs for project/order closure business processes. Seeattached document.Impact of issue:Improve productivity, reduce very labor intensivemanual methods, ensure thorough project/order closure process and reduce errors. Improvedprocess will reduce future audit findings related to funding violations. 24Jun04 IRC opened thisissue at Low priority, and assigned to J Pruitt. Assignee to ensure that appropriate personnel areadvised of this potential gap prior to conduct of third deployment SDLs. At that time, a deltarequirement will be identified or it will be determined that there is no functionality gap; in either case, assignee will recommend closure of the issue.


Delta ID: 1028

Change Req ID: 871



TITLE 3rd Deployment Reqr-ANAD Parts Mgmt System

NARRATIVEDescription of issue:The ANAD Parts Mgmt System is a local unique at Anniston which contains

modules that include Excess Material Mgmt, DSTOPS (Depot System To Optimize Parts),Inquiries PARS Mortalities and PRON Mgmt. The various modules provide automationenhancements to various controllers and managers at the depot. The modules need review for inclusion into LMP.Impact of issue:Productivity improvement is realized by grouping varioustransactions that run in mass, queries in mass and updates in mass. Reduce labor intensivemanual methods. 24Jun04 IRC opened this issue at Low priority, and assigned to J Pruitt.Assignee to ensure that appropriate personnel are advised of this potential gap prior to conductof third deployment SDLs. At that time, a delta requirement will be identified or it will bedetermined that there is no functionality gap; in either case, assignee will recommend closure of





Delta ID: 1029

Change Req ID: 882



TITLE AP1 Manual Accrual Process

NARRATIVEDescription of issue:AP1 Manual Accrual Process has the organizations to hold doing accruals

until the end of the month, which will be included in the end of the month billing cycle. Theaccruals are then reversed out the 1st of the following month.Impact of issue:Problems andimpact will be forwarded by email to Glenn Booker. Note: Entered for Richard Hughes RRADSME. 12Aug04 Issue left as pending until the procedures from issue 874 are in place.


Delta ID: 1030

Change Req ID: 883



TITLE MIPRs & Contracts Obligated as Undelivered Orders

NARRATIVEDescription of issue:All travel and most MIPR's & Contracts are obligated as Undelivered Orders

in LMP. They are being costed when payment is made.Impact of issue:Problems andimpacts will be forwarded by email to Glenn Booker. Note: Entered for Richard Hughes RRADSME. 12Aug04 Issue left as pending until the procedures from issue 874 are in place.





Delta ID: 1031

Change Req ID: 884



TITLE Ability to Link Multiple WBS Projects

NARRATIVEDescription of issue:Need ability to link multiple WBS projects when projects are worked in

conjunction with each other, i.e. overhaul program WAC A1 linked with multiple programs for various MWO applications WAC H2. This requirement is necessary to maintain the schedules insnychronization within the system. This linking requirement is also for end item inductions,completions and scrap reporting in order to maintain the assets with synchronized counts for alllinked projects. The requirement needs to address the automated schedule and asset reportingto key from, i.e. when schedule or assets are reported on the overhaul WAC A1, projects that arelinked to this overhaul will automatically be updated with schedule changes and asset reporting.Requirement has been coordinated with Gina Muss CSC.Impact of issue:Without theautomated requirements being met, intensive manual efforts will be required. Also, errors inscheduling and asset reporting can result if linked WBS projects are not kept in synchronization.12Aug04 Issue left as pending until the procedures from issue 874 are in place.





Delta ID: 1032

Change Req ID: 535

ORIGINATOR Christie Carrington PROJECT LMP

STATUS Open


TITLE FIT Review of RIA AIT BPR&A

NARRATIVEDescription of issue:Entered for DDunlap. The RIA task order (TO) requires CSC to synchronize

the ERP and Automated Identification Technology (AIT) programs to ensure that they arecomplimentary and optimize the AIT hardware procurements (Attachment 3, para 3.1, 3.2, and3.6). CSC is preparing a BPR&A and ROM for RIA AIT that will provide the foundation for procurement of AIT hardware. The ROM is to include those elements outside of the CoreContract and RIA Task Order.Impact of issue:RIA has FY03 funding which it must obligateASAP in order to procure the AIT hardware that is critical to LMP deployment success. Delivery of the RIA AIT BPR&A is being delayed due to unavailability of FIT members to review the draftBPR&A. Without the BPR&A, RIA will be forced to procure AIT hardware without benefit of knowledge of requirements to insure full integration with LMP. 29Jan03 IRC Mtg: IRC openedand assigned to DUrban and RDeluca. Workshop for RIA early March to demonstrate the RIAsolution as it exists today and determine the appropriate steps to move forward. Update 11Mar03:

CSC provided AIT info and govt awaiting ROM. If ROM is in agreeable range, the issue will beresolved. RIA AIT VTC scheduled for 1300 on 17 Mar. AMC conference is occuring this week inAlabama. Lou Rebecca and Bob Snodgrass (Bob is the Team CSC AIT person from theIndustrial Base Task Order) are attending. (DUrban) Update 30Apr03: The ROM provided by CSCis not economically feasible. RIA must proceed to engage a third party AIT integrator.Contractual requirement for CSC to support deployment of AIT in conjunction with the ERPremains in dispute. RIA is finalizing the government position regarding the issues in dispute sothat we can move toward resolution.(DDunlap) 31July2003 Recommend closure since RIA has noAIT program. Need DUrban to confirm. 17 Oct 2003 Contacted DUrban via email. No updateshave been provided to date. 14 Nov 2003 Contacted Durban via email requesting and update for this issue. 5 April 04 Assignees changed to Dleavy. New Assignee contacted. Update requested.14 April 04 per DLeavy: RIA will provide an update for this Issue. In general: RIA has movedforward and contracted with a certified SAP AIT provider to deploy a complete AIT solution toRIA in their legacy enviroment with design considerations to minimize efforts to move toSAP/LMP. It will be necessary to integrate this capability into the LMP solution when RIA is

deployed. 15Apr04 IRC update: forward issue to LRebecca and BMartin.





Delta ID: 1033

Change Req ID: 656

ORIGINATOR Denise Allred / PROJECT LMP

STATUS Open


TITLE 3rd Deployment - Small Arms Serialization Interface (SASI)

NARRATIVEDescription of issue:Bridges & Uniques-Applies to Anniston Army Depot only. SASI (Cat 4)

originally to be subsumed thru B&U review. Per discussion with FIT, this is not subsumed. SASIis the primary automated tool used by the Small Arms shop at ANAD to process weapon serialnumbers into DODSASP. Tool provides all the necessary functions for accurately processing andrecording weapons in the shop and interfacing with DODSASP. Allows the shop better visibilityand control of the weapons in process. The user located in the shop inputs data by scanningbarcodes on packing lists and weapon tags.Impact of issue:Required for TACOM/ANADdeployment. Issue entered per direction of Tech Dev Goverment lead, M. Berger. Without SASI,data would have to be manually input, increasing errors and increasing labor required. SASI hasfull functionality of data entry using barcode labels and packing lists, which includeweapon/serial number receiving, weapon/serial number scrap parts shipped, changes to weaponNSN/serial number and the ability to recall shipments. SASI also allows the user to print reports,

shipment packing lists and barcode labels. Program was developed using MicrosoftAccess/Visual Basic for Applications. Complete description of product tool is available. 16Apr03IRC Mtg: IRC opened and assigned to KCorcoran. DUrban to schedule meeting for robustmeeting by end-June. 31July2003 IRC changed title from second to third deployment. 30 Sept2003 Contacted Kcorcoran via email requesting an update for this issue. 14 Nov 2003 ContactedDurban via email requesting an update for this issue. No response has been provided to date. 18Nov 03 Update per Jerry Pruitt: This issue should remain open. 20Nov2003 IRC update: needKCorcoran and JPruitt to agree upon category of this B/U. 4 Dec 2003 IRC Update: Issue shouldremain open pending Anniston Delta Requirment determination and disposition requirementreview. 5 April 04 Assignees changed to Rbourgeois.


Delta ID: 1034

Change Req ID: 657

ORIGINATOR Jerry Pruitt PROJECT LMP

STATUS Open


TITLE ANAD - 3rd Deployment - MAP ANAD Data Warehouse & PDMSS Data

NARRATIVEPer end user Email, 16 Aug 04:1. Request that AHD Ticket be opened pertaining to IRC

closing of Issue #657, per direction of Gary Lindsay LAISO and Georgia Dugan Maint Domain

Manager. 2. Copy of Issue #657 is attached.3. Request also that all be furnished with theAHD Ticket number as soon as possible.Thanks,Jerry PruittMaint Domain Mgr RepMoorestown, NJ ¿ Phone: (856) 252-5244Description of Issue: B&U - Outcome of B&U reviewthat the requirement would be subsumed and covered in Integrated Scenarios development.(PMDSS review in Apr 02). This issues applies only to Anniston Army Depot. Entire Project IssueReport is attached. Click on attachment to view.





Delta ID: 1035

Change Req ID:


STATUS Open

IMPACT 3rd Deployment DATE 11/3 /2004

TITLE Component Routing Tracking

NARRATIVEComponent Routing/Tracking module: Provides capability to store pre-defined process routes for

components in a history file by EIC & WPC, ability to establish an active shop number recordunder a PCN by EIC & WPC. The system builds the active record with all component stocknumbers and associated work areas and automatically assigns the next shop number(s) insequence. Also provides inquiry/report capability. Need ability to record inductions andcompletions directly from the shop floor or bar-code scanning device. Requires ability toestablish a "custom routing" for a specific component on the Active File without in any wayaffecting the History File, the ability to inquire into the Active Shop Number File at program,shop number, component stock number, or work area level, and need automatic closeout anddeletion of shop numbers of which PCN has been closed. Provides ability for determining thelocation and projected completion date of selected components in a user-defined process route.A move ticket with a bar-coded shop number and stock number is used for reporting inductions

and completions of components. Note: This capability is also replicated in various PDMSSapplications, CCAD DEX and ANAD Routing Tool.


Deborah Hovis 10/22/2004 Jerry Pruitt Note: References in the issue to CS Module inSAP has been overtaken by events. PP Module is the presentsolution.

Delta ID: 1036

Change Req ID:


STATUS Open


TITLE End Item Routing Tracking

NARRATIVEEnd Item Routing/Tracking module: Provides capability to store pre-defined process routes of

work areas in a history file by EIC & WPC along with various route option code(s), ability toestablish an active shop number record under a PCN by EIC & WPC along with route optioncode. The system builds the active record from the history file and assigns the next shopnumber(s) in sequence. Also provides inquiry/report capability. Need ability to record inductionsand completions directly from the shop floor or bar-code scanning device. Requires ability toestablish multiple "custom routing" for EIC/WPC in the history file. Routings can be further modified in the active record by adding, changing or deleting work areas. Need the ability to

inquire into the Active Shop Number File by PCN, shop number or work area level. Requiresautomatic closeout and deletion of shop numbers of which PCN has been closed. Providesability for determining the location and projected completion date of selected end items in auser-defined process route. A move ticket with a bar-coded shop number and stock number isused for reporting inductions and completions of components. Note: This capability is alsoreplicated in various PDMSS applications, CCAD DEX and ANAD Routing Tool.





Delta ID: 1037

Change Req ID: 630


STATUS Open


TITLE 3rd Deployment - Parallel Complex Routing in PP

NARRATIVEDescription of issue:CR0680 (See DOC) entered to analyze legacy routes to determine best

methods of conversion to SAP. This was as a result of using PP Module for 1st deployment. Theanalysis is on-going and is requiring changes to legacy routing in order to migrate to SAP or manual load of data. Need to apply this analysis to 2nd and 3rd deployments to assess themagnitude of the problem. The use of the PP Module is desireable at maint depots rather thanuse of CS Module, except for Life Cycle Tracking. CS works best when quantity is 1. Task lists inCS result in scheduling problems and require manual intervention when quantity is greater than1. Also, CS has workaround on recording type 8 production counts. Advantages of using PP isadditional functionality such as splits and overlaps. Also allows for same SAP tool to be used for manufacturing and remanufacturing. Additionally, the Reman Team has taken a complex routefrom ANAD, reformatted and entered into SAP. Not all problems solved. Impact of issue:This impacts all deployment sites. Need to resolve for 1st deployment site. The 2nd and 3rd

deployment sites need to be working this problem to reformat complex routing problems toresolution. Significant resources at depots will be needed to accomplish.19Mar03 IRC Mtg: IRCopened and assigned to RBourgeois. 31July2003 IRC changed title prefix from "Post 1st GoLive" to "3rd Deployment". Oct 03 Notification: Update request from RBurgeois. 08Jul04 IRCclosed this issue; it will be addressed as part of design decisions and data migration approachesfor second and third deployments.


Delta ID: 1039

Change Req ID:ORIGINATOR Jerry Pruitt - Sherry PROJECT LMP

STATUS Open


TITLE Technical Manual Configuration

NARRATIVETM Configuration File – Need the ability maintain requirements for the Technical Manual

Configuration Reference File stored in MSM037. Stock Numbers are currently loaded in theMSM037 file, which include TM figure number and TM item number. In addition, there are 3transfer options (copy capability) to build new records in mass. This process provides certainrequisitioning controls that identifies stock number requisition records to be matched against theTM Configuration File. If requisitioned stock number is not on the TM Configuration file, a

message is displayed “Stock Number not on TM-File”. This aids the depot Parts Manager controlpurchased materials for a given end item. Various reports/queries are required. ReferenceADSM 18-LOA-KEY-ZZZ UM, Vol 2. The requirement was also coordinated with Andy BubakILSO, Chambersburg. This delta is entered at the request of Sherry Banks RRAD/TACOM.





Delta ID: 1040

Change Req ID:



TITLE Prepositioning and Requisitioning in Excess of DOF D2 Delta #139

NARRATIVED2 DELTA # 139 – PREPOSITIONING AND REQUISITION IN EXCESS OF DOF, Issue # 806

closed on 10/7/2004, LEAD AMCOM originally submitted Delta # 139 for purchasing componentsabove the depot overhaul factor (DOF), i.e. purchasing items above the forecasted MortalityData/BOM plan. AMCOM requirement was later withdrawn after LMP functionality wasdemonstrated by CSC to AMCOM/CCAD reps. Demonstration does not meet TACOMrequirements and still requires the functionality within LMP. In legacy, a control is in placewhere the material ordered above the forecasted DOF is sent to the Managers Pending ActionFile as a suspensed requisition awaiting Parts Manager review/approval/disapproval. Thisprovides material managers with a method to control material costs during program execution.LMP needs to add this type of management control, such as a SAP requisition release strategy.


Delta ID: 1041

Change Req ID: LMP



TITLE Arsenal Workload

NARRATIVE1. Need capability to budget arsenal workload (from MSC perspective)2. Need capability tobudget arsenal workload (from performer perspective)3. Need ability to execute arsenalworkload Contractor (GOCO facility) Contractor (COCO facility) Organic (GOGOfacility) Organic (COGO facility)4. Need ability to report Arsenal workloadHeadquarters directed AD HOC/mandatory reports DMOPS 50/50 reports Generationof 1397 data requirements Asset visibility 5. Requirement PreviouslyDocumented/Identified: Addressed under the IBO and RIA TOEntered for: MadaleneMasem, Maintenance Domain Management, DSN 793-8240, COMM (309) 782-8240





Delta ID: 1042

Change Req ID:



TITLE Single Entry for all Maintenance Data

NARRATIVENeed to develop a single entry point/transaction for depot and below depotmaintenance data,

which will become the basis to allow improved edits(tailored sub table/drop down choices andvalidations (required vs. notrequired).Entered for: Madalene Masem, Maintenance DomainManagement, DSN 793-8240, COMM (309) 782-8240


Delta ID: 1043

Change Req ID:ORIGINATOR JPruitt PROJECT LMP STATUSOpen


TITLE WBS Schedule Info for AMCOM Delta #94

NARRATIVEWe need to make sure we have the start/finish dates in line with the end item delivery schedules.

In order to make sure this happens, we need to add that when the delivery schedules arechanged by the depot, with an alert is provided back to the workloader for renegotiation/approval.1. The start and finish dates identified for the WBS must match the enditem delivery schedules (known as schedules in legacy). This will help reduce repair part storagecosts.2. Depot schedule changes needs to be documented and have command/depot

agreement. This will facilitate the end item delivery changes required to keep the start/finishdates current with the schedule. These types of actions are required for management control atboth command and depot level. Entered for Katrina Fuller 3/14/05.





Delta ID: 1044

Change Req ID: 482

ORIGINATOR PROJECT LMP STATUSOpen

IMPACT 3rd Deployment DATE 12/10/2002

TITLE PTR 839 TCN Determination Logic Re-Visit

NARRATIVEDescription of issue:

TCN Determination logic for Single / Multiple delivery requirements need to be re-visited w/Gov't representation w/ focus on Ammo design. Main Issue: In the current SAP design - the leadTCN will be determined by the lowest sales order number among the mutiple deliveriesgenerated from the sales orders for the same customer . Therfore, in shipment consolidationcreation the user-exit will determine the TCN logic. We just need to validate the logic. Welogged the PTR so we do not lose sight of it.

Impact of issue:Large - major part of the distribution process requirement for shipments. The TCN travels with theNSN in the shipments. The correct TCN determination is important. AMC uses the number tohelp track their shipments. A DOD regulation. IRC Mtg 11 Dec: IRC Opened and assigned to

JAngelastro and GMyers. EFarler primary as FDay left project. 31July2003 IRC changed titlefrom second to third deployment. 29 Sep 2003 Contacted EFarler for an update. 08Jul04 IRCupdate: issue will remain open until 3rd deployment SDLs are conducted and it is determined if this is or is not a valid requirement. 3Feb05 IRC: Ray Davison will work with Joe Angelestro todetermine the extent that activitiies in support of missile requirements at Toby satisfy thisrequirement. Any additional requirements not already covered will be submitted to STARS andthis issue closed.


US Army: open %203rd deltas

Documents

Transcript of US Army: open %203rd deltas