Scope
| Google Drive Live Link |
|---|
| url | https://drive.google.com/file/d/19gK8sn5qSIDFG8LMmlMzEiY3moyryzz0pc3N-uQFJbo/view |
|---|
|
High level user flow (BA & business stakeholders)
https://miro.com/app/board/uXjVN5MF2XQ=/#tpicker-content
Data flow (BA and Architect)
https://app.diagrams.net/#G1mfwQh_gsmV1lNLwc9OfvJrRAWPaZyTYm#%7B%22pageId%22%3A%22jheWgB9ikYpCB23Nlwa9%22%7D
Web app requirements
Production: https://solvayagile.atlassian.net/browse/EBR-20 ->Done
Laboratory: https://solvayagile.atlassian.net/browse/EBR-31 →Done
Quality: https://solvayagile.atlassian.net/browse/EBR-32 ->Done
Logistic: https://solvayagile.atlassian.net/browse/EBR-30 -> Done
...
Handling inconsistencies:
| Jira |
|---|
| server | Jira |
|---|
| serverId | bbf5f9ee-7f3e-3274-bb6e-be12673f2166 |
|---|
| key | EBR- |
|---|
|
24
...
→ Done
Header page
| Jira |
|---|
| server | Jira |
|---|
| serverId | bbf5f9ee-7f3e-3274-bb6e-be12673f2166 |
|---|
| key | EBR-37 |
|---|
|
→ DoneSummary page: https://solvayagile.atlassian.net/browse/EBR-37-> Done
Access management: https://solvayagile.atlassian.net/browse/EBR-36 -> Done
Versioning: https://solvayagile.atlassian.net/browse/EBR-38-> In progress
Data model requirements
Refresh frequency: | Jira |
|---|
| server | Jira |
|---|
| serverId | bbf5f9ee-7f3e-3274-bb6e-be12673f2166 |
|---|
| key | EBR-45 |
|---|
|
→ to be discussed with technical team
SAP source
Silo number: Batch attributes derived from SAP (MTP & Torrelavega)
| Jira |
|---|
| server | Jira |
|---|
| serverId | bbf5f9ee-7f3e-3274-bb6e-be12673f2166 |
|---|
| key | EBR-43 |
|---|
|
→ DoneBatch attribute table:
| Jira |
|---|
| server | Jira |
|---|
| serverId | bbf5f9ee-7f3e-3274-bb6e-be12673f2166 |
|---|
| key | EBR-80 |
|---|
|
DoneLab parameters derived from SAP
| Jira |
|---|
| server | Jira |
|---|
| serverId | bbf5f9ee-7f3e-3274-bb6e-be12673f2166 |
|---|
| key | EBR-42 |
|---|
|
→ Done Packaging attributes from SAP (MTP and Torrelavega)
| Jira |
|---|
| server | Jira |
|---|
| serverId | bbf5f9ee-7f3e-3274-bb6e-be12673f2166 |
|---|
| key | EBR-81 |
|---|
|
Test data in BQ views→ In progress
Other sources
Reference table
| Jira |
|---|
| server | Jira |
|---|
| serverId | bbf5f9ee-7f3e-3274-bb6e-be12673f2166 |
|---|
| key | EBR-44 |
|---|
|
→ In progress (technical decision making) ProdX data view (Data model)
| Jira |
|---|
| server | Jira |
|---|
| serverId | bbf5f9ee-7f3e-3274-bb6e-be12673f2166 |
|---|
| key | EBR-41 |
|---|
|
pending the meeting with the owner of the app (Technical info to connect)
PI source
PI data model Dombasle | Jira |
|---|
| server | Jira |
|---|
| serverId | bbf5f9ee-7f3e-3274-bb6e-be12673f2166 |
|---|
| key | EBR-47 |
|---|
|
→ pending tag names from business
PI data link with BQ
| Jira |
|---|
| server | Jira |
|---|
| serverId | bbf5f9ee-7f3e-3274-bb6e-be12673f2166 |
|---|
| key | EBR-25 |
|---|
|
...
→ Pending PI data ingestion in BQ Batch manufacturing time (start/stop time) calculations | Jira |
|---|
| server | Jira |
|---|
| serverId | bbf5f9ee-7f3e-3274-bb6e-be12673f2166 |
|---|
| key | EBR-20 |
|---|
|
Logistic form
Laboratory form
Quality form
Versioning requirements
...
→ Requirements specification is pending stakholders decision making on the excluding nonconformity period from the calculation. Pending decision making on where to host the calculation. Web app or BG. If web app.
Source batch 21 & PI sheet
| Jira |
|---|
| server | Jira |
|---|
| serverId | bbf5f9ee-7f3e-3274-bb6e-be12673f2166 |
|---|
| key | EBR-27 |
|---|
|
