A. What is your idea?
1) Classification
Opportunity for improvement
2) Brief description
In 26R1, the Requirement visibility function was implemented for CROs, but it currently only allows viewing Requirements if the Site matches the Removal Site. At JAL, parts removed at overseas stations (e.g., New York) are shipped to our repair bases in Japan (Site: NRT/HND). When the NRT repair shop tries to create a CRO via the Component Return Page (which links Ship information and shows Requirements), they cannot do so because the Site is fixed to the Removal Site and cannot be changed to NRT. Consequently, users must create the CRO manually at the NRT site. However, manually created CROs lack the "Assign Task" field, meaning Requirements cannot be viewed or processed. Additionally, this causes issues for inventory maintenance. When a part in the Store needs re-treatment (e.g., nearing anti-rust expiration), a manual CRO is created, but the Requirement cannot be checked or updated. We need a process where Requirements can always be viewed and processed on a CRO, regardless of the Site or whether it was created manually.
B. Context and scope 1) Who is affected?
Internal users
2) Frequency
Daily
C. Value and impact 1) What is the business outcome?
Supports compliance or reduces risk Improves productivity or efficiency Reduces cost or manual effort
2) Impact scale
5 — Enterprise-wide
3) Workaround
Users must manually check the Requirement from the "Rotable Inventory" page by searching for the P/N and S/N. However, this manual search is prone to human error (e.g., typos). A search mistake can lead the user to falsely assume that no Requirement exists, resulting in missed Requirement updates.
D. Evidence and examples
(Please attach relevant screenshots when posting.) Business Impact Example: If a missed Requirement expiration goes unnoticed, the part might be issued and installed on an aircraft (Ship). Once the expired Requirement is discovered, the part must be removed again, and a replacement must be allocated. If no alternative part is available, this leads to an AOG (Aircraft on Ground) situation, causing massive financial and operational losses for the enterprise.
E. Additional details 1) Enter support ticket ID reference (If applicable)
CS0546563
2) Would you like to participate in validation or early testing?
Yes