Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨: Loop improvements #897

Open
4 tasks
Gustav-Eikaas opened this issue Mar 1, 2024 · 4 comments
Open
4 tasks

✨: Loop improvements #897

Gustav-Eikaas opened this issue Mar 1, 2024 · 4 comments
Assignees

Comments

@Gustav-Eikaas
Copy link
Contributor

Gustav-Eikaas commented Mar 1, 2024

Loop improvements

Feedback from JC Loop testing team

They like the new version of loop better than the old one. Some much needed columns were added.
Some of the work they do cannot be done using the tool atm. They showed us an excel sheet they had made. This sheet is updated manually every 24hrs.
They are sourcing data from Fusion. After reviewing the Excel sheet we identified some key fields we should aim to include in our application

  • LUN status. (Livening up notice)
  • Energy source
  • McPkg for Energy source
  • Holding code A-G

LUN is a certificate on a loop tags mc pkg
Energy source is the tag that is powering the loop
Holding code is a calculated field on what is holding it back. E.g C for construction

@ken-mellem ken-mellem self-assigned this Aug 27, 2024
@ken-mellem
Copy link
Contributor

I want to raise the awareness of this.

@Gustav-Eikaas
Copy link
Contributor Author

I agree but we need PO involvement in investigating the business aspect of this

@ken-mellem
Copy link
Contributor

@JoneUE please evaluate. There were some really nice findings from Edward.

@JoneUE
Copy link
Contributor

JoneUE commented Sep 10, 2024

There is no easy way to set this up, Still not sure if it's possible to do the way PCS is set up now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants