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

Handover Views #13

Closed
jaysencpp opened this issue Oct 12, 2022 · 8 comments
Closed

Handover Views #13

jaysencpp opened this issue Oct 12, 2022 · 8 comments
Assignees
Labels
data Some application in need of new API, more data, new views etc.

Comments

@jaysencpp
Copy link
Contributor

jaysencpp commented Oct 12, 2022

Handover Views (WIP)

The Handover App needs to migrate from Fusion Dataproxy using ProCoSys Views to FAM Views. Below is a proposal for the different data the App will need to consume.

Handover main app

  • projectIdentifier
  • projectDescription
  • commpkgNo
  • commpkgId
  • system
  • progress
  • area
  • commpkgStatus
  • mcStatus
  • priority1
  • priority2
  • priority3
  • plannedStartDate
  • actualStartDate
  • plannedFinishDate
  • ActualFinishDate
  • phase
  • responsible
  • hasUnsignedActions
  • forecastFinishDate
  • volume
  • forecastTacDate
  • mcPkgsCount
  • mcPkgsRFCCShippedCount
  • mcPkgsRFCCSigned
  • mcPkgsRFOCShipped
  • mcPkgsRFOCSigned
  • tacIsAccepted
  • tacIsShipped
  • tacIsRejected
  • plannedTacDate
  • forecastStartDate
  • mcDisciplineCodes
  • mcDisciplines
  • IsDemolition
  • demolitionPlannedStartDate
  • demolitionForecastStartDate
  • demolitionActualStartDate
  • demolitionPlannedFinishDate
  • demolitionForecastFinishDate
  • demolitionActualFinishDate
  • remark
  • rfocIsShipped
  • rfocIsRejected
  • rfccIsShipped
  • rfccIsAccepted
  • rfccIsRejected
  • demolitionDCCAcceptedDate
  • demolitionRFRCShippedDate
  • tacIsActualDate
  • rfccShippedDate
  • rfocPlannedDate
  • rfocForecastDate
  • rfocActualDate
  • rfocShippedDate

Handover/Details

  • nextToSign

Handover/MCPackages

  • commpkgId
  • mcPkgNo
  • mcPkgId
  • mcStatus
  • rfccShippedActualDate
  • rfccIsAccepted
  • rfccIsRejected
  • rfccIsShipped
  • rfocIsAccepted
  • rfocIsRejected
  • rfocIsShipped

Handover/NCR

  • documentNumber
  • documentId (?)
  • title

Handover/Workorders

  • workOrderNumber
  • workOrderId
  • description
  • projectProgress
  • workOrderStatus
  • materialStatus

Handover/Unsigned Tasks

  • taskNumber
  • title
  • documentId?
  • taskId?

I need to be able to generate this URL: [...]/Documents/Document#id=114212839&content=TASK!aa7e60c4-2d6d-424a-a83d-6a2ee8f209d9&tab=content

Handover/Unsigned Actions

  • actionNumber
  • title
  • description
  • commPkgId
  • actionId?

I need to be able to generate this URL: [...]/Completion#CommPkg|112647990?bf=1&content=MAINACTION!2fc767f3-7421-15e3-3a66-316e2d3a21fc

Handover/Punch

  • tagNumber
  • status
  • description
  • toBeClearedBy
  • sorting
  • punchId?
  • tagId?

I need to be able to generate this URL: [...]/Completion#PunchList|23674669?itemId=3743342

Handover/SWCR

  • swcrNumber
  • status
  • description
  • priority
  • swcrId

Handover/Query

  • queryNumber
  • queryId?
  • title
  • status
  • nextToSign
  • type

I need to be able to generate this URL: [...]/Documents/Document/#id=114890226

New fields that have been requested and not yet implemented in current solution

  • open PA
  • open PB
  • not signed MCCRs
  • open work orders (< 100%)
  • not signed CPCLs
  • open SWCRs
  • not signed tasks
  • not signed actions
  • open queries
  • remaining mhrs on open work orders

New Issues is requested to deal with these.

@jaysencpp
Copy link
Contributor Author

Suggested changes to Handover/MCPackages

At the moment we need to resolve each MC packages' RFOC and RFCC status based on the fields

  • rfccIsAccepted -> "RFCC Accepted"

  • rfccIsRejected -> "RFCC Rejected"

  • rfccIsShipped -> "RFCC Sent"
    If none of the above -> "OS"

  • rfocIsAccepted -> "RFOC Accepted"

  • rfocIsRejected -> "RFOC Rejected"

  • rfocIsShipped -> "RFOC Sent"
    If none of the above -> "OS"

The frontend should be served with these two properties:

  • rfccStatus: string with value either "RFCC Accepted", "RFCC Rejected", "RFCC Sent" or "OS"
  • rfocStatus: string with value either "RFOC Accepted", "RFOC Rejected", RFOC Sent" or "OS".

Since the frontend should go via dataproxy, it should probably be resolved in dataproxy so FAM view doesn't contain this logic?

Resulting in this:

  • mcPkgNo
  • mcPkgId
  • Description
  • mcStatus
  • rfccStatus
  • rfocStatus

@jaysencpp
Copy link
Contributor Author

jaysencpp commented Oct 12, 2022

Suggested change to Handover/Workorders

At the moment we need to resolve each workorder's status based on

  • projectProgress = 100 -> "WO Finished"
  • materialStatus containing m12, m13, mn & workOrderStatus containing w04-w10 -> "Material and Workorder OK"
  • materialStatus containing m7, m9, m10, m11, m12, mn & workOrderStatus containing w03-w10 -> "Material and Workorder Available"
  • if none of above -> "Material and/or Workorder not Available"

The frontend should be served with this property:

  • woStatus: string with value either "WO Finished", "Material and Workorder OK", "Material and Workorder Available" or "Material and/or Workorder not Available"

Resulting in this:

  • workOrderNumber
  • workOrderId
  • description
  • projectProgress
  • status

@jaysencpp
Copy link
Contributor Author

Suggested changes to Handover/Main app

Placeholder

This was referenced Oct 12, 2022
@jaysencpp jaysencpp added the data Some application in need of new API, more data, new views etc. label Oct 12, 2022
@jaysencpp
Copy link
Contributor Author

Missing data for:

  • hasUnsignedActions
  • volume
  • Everything about NCR
  • Everything about task
  • Everything about actions

Maybe?
IsDemolition
demolitionPlannedStartDate
demolitionForecastStartDate
demolitionActualStartDate
demolitionPlannedFinishDate
demolitionForecastFinishDate
demolitionActualFinishDate
nextToSign

@ken-mellem
Copy link
Contributor

Is the entire history here up-to date? Or can we trust the OP?

@jaysencpp
Copy link
Contributor Author

Is the entire history here up-to date? Or can we trust the OP?

The data that is missing (not the DB views) should be: NCR, DocumentID for Tasks, NextToSign

@ken-mellem
Copy link
Contributor

@jaysencpp documentID for URL to PCS is now in PROD according to FAM.

@ken-mellem
Copy link
Contributor

ken-mellem commented Sep 25, 2023

Closing this - the nextToSign is considered a nice-to-have - but put on hold. See comment

NCR require a lot more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data Some application in need of new API, more data, new views etc.
Projects
None yet
Development

No branches or pull requests

3 participants