RGT - Request Generation Tool

Course Description

The Request Generation Tool (RGT) course provides students with knowledge of how to use the RGT system to submit cataloging requests for action. These actions include requesting the establishment of new National Stock Numbers (NSNs), NSN maintenance/update requests, cancellation of NSNs, and reinstatement of NSNs, among other actions. After the completion of the course the students will know how to register for an RGT account and successfully navigate through the RGT product.

As part of the FLIS Transformation initiative, the Electronic Cataloging (E-Cat) is now RGT. 

Request Generation Tool (RGT) FAQs

1. How often do I need to log into RGT to keep my account active?

ANSWER: You must log into your account every 30 days to keep it active.

2. Do the DD180 forms still need to be attached when submitting related requests?

ANSWER: No

3. Is there a complete list of return codes with definitions?

ANSWER: Yes. The list of return codes can be viewed at: Return Codes

4. Are supervisors able to see their employees’ request within the system or are case numbers required?

ANSWER: No. The only things users can use to look up a request in RGT under “My Requests” are the following: Case, Task, NIIN, DEMIL Case Number, and DEMIL Task Number. Users would need to have this information in order to find their employees’ request.

5. What is the retention time for closed cases? In other words, are they ever deleted from RGT?

ANSWER: Currently no requests will be deleted from RGT. That could change in the future.

6. Do customers need to re-submit requests lost from E-Cat transition?

ANSWER: Technically no requests from E-Cat were lost. All requests were either worked and completed or rejected because there was an issue. Users are encouraged to resubmit requests in RGT should this apply to their situation.

7. For roles to access RGT, will each request require a new role (i.e., NSN, Characteristics, DEMIL).

ANSWER: For access to submit requests that impact NSN, DEMIL, or Characteristics, one will need only one access in AMPS. There are several roles to choose from based on user workload requirements. The roles and brief definitions can be viewed at: AMPS ROLES 

8. Does the Originating and Submitting Activity Codes auto-populate based on AMPS credentials?

ANSWER: OAC is populated based on your credentials.

9. For those that require access to RGT, but do not have access to AMPS, how will someone be able to request the proper role (i.e., FAA, etc.)?   

ANSWER: Everyone must have an AMPS account. Directions on how to register for an AMPS account can be found at https://amps.dla.mil

10. The priority on requests is either Routine or Emergency. Will Accelerate still be something that can happen to a request?

ANSWER: No, Accelerate is not a valid entry in the future. Only two priorities that are allowed  are routine and emergency.

11. Will there be an update to the H6?

ANSWER: The H2 and H6 sites have been sunset. Users can query this information either within the H2 and H6 tabs within FED LOG®, or can download the H2 and H6 data from the following site: https://www.dla.mil/Information-Operations/Services/Catalog-Tools-Tables

12. Does RGT allow for a duplicate check on part numbers?

ANSWER: Currently, RGT does not check for duplicate part numbers n a New NSN request. Part Numbers will be validated after the Case is created.

13. In the drop down for INC, 77777 is no longer available. What do we do when that is required for our submissions?

ANSWER: If an INC is not found for the item, type in an Item Name in the Item Name field. Once an Item Name is entered, the INC will auto populate 77777 in the INC field.

14. What is the difference between the Request Number and the Case Number?

ANSWER: The Request Number is the overarching number that is given by the system and the Case Number is the number generated from the request file. Eventually, it will lead to a task number associated to the request.

15. Are there requirements regarding the types of technical data Log Info SVC is looking for as we submit our requests?

ANSWER: The data that is most helpful in order to enter an item into the supply chain is as follows:

15. 1. 1. The data must contain Form/Fit/Function Data.
       2. The data must provide a procurable CAGE code (or multiple procurable CAGE codes), and in alignment with the Provisioning Parts List. 
       3. The data must represent a stable design.
       4. The data must accurately portray the Design Control Authority (or Activity) (DCA). 
16. Are JLCs going away with the upgrade?

ANSWER: The Form itself will go away. However, the types of action that prompted the JLC’s will persist but will be handled systemically via collaboration requests generated from ServiceNow® based on customer requests. For example: If the Navy asks to be added as a user to a USMC NSN, the system has business rules that will trigger a collaboration and notification of all impacted users that their responses are needed. If additional information is required during collaboration the collab requests will be designed to gather it.

17. Is Medical ECAT (DD1277) going away with RGT?

ANSWER: Medical ECAT is the medical electronic catalog for searching medical items of supply and ordering them. A form DD1277 is an online cataloging action request used by the services to initiate a request to Clothing and Textiles (C&T) or Subsistence (they review and approve before sending to Log Info SVC for codification). Subsistence, Clothing and Textiles and Medical FSC will still go to Troop Support after the new system as they do today.

18. Does Inquiry show who submitted the transaction?

ANSWER: Yes. It does show who submitted the transaction and each step of the Case Number’s life.

19. Are existing collaborations being transferred to RGT?

ANSWER: We have ways to continue working collaborations after going live just as we do today since it’s handled manually. However, we will work to minimize the amount of open collabs that are lingering at go live.

20. Is the process of emailing Tech Data and drawings to mailbox: LogInfoSVCLibrary@dla.mil still going to be a requirement with RGT?

ANSWER: No. Please ensure technical data is applied to the submitted requests vs being emailed to a mailbox.

21. Will Tech Data still be uploaded to the applicable repositories?

ANSWER: Yes, all tech data will be uploaded to the applicable repositories.

22. Will RGT screen for duplicate requests?

ANSWER: RGT will not have on-screen checks for duplicates, BUT upon submission the new “FLIS” will check duplicates. Based on those business rules, the system will decide where the requests go (i.e., reject).

23. Will DEMIL requests only be submitted through RGT in the future? Will the email inbox go away?

ANSWER: No. RGT is one option someone with a CAC and approved AMPS Role can submit a challenge. The mailbox will stay open for individuals that do not have CACs.

24. Will the tech data field be marked as required (since it is) for new NSN submissions? Currently there is no red asterisk even though it is a requirement. Will this requirement be linked to the DAC that is submitted to know if tech data was marked as available/provided or not?

ANSWER: It is required. Since the requirement is either tech data location, tech data justification, or attachment, the system couldn’t show all of them as mandatory since it is different sections in RGT. If the user selects “Submit” without filling out one of those three fields, an error message will appear at the top of the screen.

25. How will collaborations be handled within RGT?

ANSWER: A cataloging request needs to be submitted first and then a collaboration can be triggered. They are manually triggered from the case and tasks. Once generated for the collaborators, collaborators get an email. Then go into RGT “My approvals” to answer. The automated portion of Collaboration will be available after go-live.

26. Will RGT allow for Various file types for uploading?

ANSWER: Yes. The following file types will be allowed:

26. 1. 1. “.BMP”; “.C4”; “.CSV”; “.DOC”; “.DOCX”; “.GIF”; “.JPEG”; “.JPG”; “.MSG”; “.PDF”; “.POTX”; “.PPTX”; “.PPSX”; “.SLDX”; “.TIF”; “.TIFF”; “.TXT”; “.XPS”; “.ZIP”
27. How will the Cataloging Team receive requests in RGT?

ANSWER: After a request is successfully submitted within the RGT system it will be assigned to a technician/cataloger who will work the request.

28. How does the collaboration process work now?

ANSWER: All the collaboration will be sent through RGT and the Point of Contact (POC) needs to respond through the RGT portal of concur or non-Concur.

All requests will be submitted by users directly through the RGT system, and users must have the Collaborator role to submit a request. Separate collaboration forms will no longer be required. Each request will be routed to the appropriate POC, who will be responsible for all required collaboration actions.

Following collaboration, the request will be closed as either concurring or non-concurring, with appropriate action taken and any additional instructions or guidance provided as applicable.

29. How will request processing status be identified?

ANSWER: Requests are processed in the order they are received. Requests’ status must be checked manually in RGT using the case number, NIIN, or other applicable tracking category until closure, at which time a notification is sent. A pending status means processing has not yet started, while any other status generally means the request is being reviewed or worked.

30. Is there a suspense date for a submitted request?

ANSWER: All requests have a due date. These due dates have been established for each service through the Federal Cataloging Committee (FCC), which vary by service.

31. Will there be a POC to reach if a request goes unanswered for an extended period?

ANSWER: Contact the DLA Cataloging Liaison for your Service or Agency. You may also submit a DLA Service Ticket via the DLA Contact Center at dlacontactcenter@dla.mil.   

Target Audience

Department of War (DOW) personnel, Military Services, and government agencies submitting requests to Logistics Information Services Catalogers for action. Defense Logistics Agency (DLA) Logistics Information Services personnel performing cataloging actions against National Stock Numbers (NSNs).

Delivery Methods

Classroom and Webinar Instruction (3 hours)
Webinar

Please direct any questions regarding the transition from E-Cat to RGT to the Federal Catalog Committee at: federalcatalogcommittee@dla.mil. 

*This will not affect the ECAT Medical Ordering Platform*

Contact us

For questions or additional interest in Training, contact the Customer Support Training at:

E-mail:   dla.tng@dla.mil