Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-1662

Review and consolidate EDA data management needs for early releases

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • Enabler
    • Should have
    • PI13
    • None
    • None
    • Obs Mgt & Controls
    • Hide

      See SS-53.

      Show
      See SS-53 .
    • Hide

      Results recorded in a single place in confluence: https://confluence.skatelescope.org/display/SE/SS-53+consolidate+design+for+Data+Management+in+early+array+releases with a short description of the source of the data and assumptions made for scaling.

      Show
      Results recorded in a single place in confluence: https://confluence.skatelescope.org/display/SE/SS-53+consolidate+design+for+Data+Management+in+early+array+releases  with a short description of the source of the data and assumptions made for scaling.
    • 1
    • 1
    • 1
    • 1
    • Team_MCCS
    • Sprint 5
    • Hide

      An initial investigation was conducted during the second half of PI13 by MCCS to begin to understand what the Engineering Data Archive requirements are, specifically for MCCS data. This is the first time such an investigation has been undertaken and it was intended that what was learnt through this exercise would help other areas of the SKAO software community to follow suit and contribute to the continuous refinement of the process and method to capture the data storage requirements. To support this, this feature delivers a spreadsheet containing scalable estimates of the EDA data requirements attributable to Low MCCS. Additionally, accompanying documentation outlines the procedure used to produce the estimates.  See Confluence page https://confluence.skatelescope.org/x/VrINCg

      Show
      An initial investigation was conducted during the second half of PI13 by MCCS to begin to understand what the Engineering Data Archive requirements are, specifically for MCCS data. This is the first time such an investigation has been undertaken and it was intended that what was learnt through this exercise would help other areas of the SKAO software community to follow suit and contribute to the continuous refinement of the process and method to capture the data storage requirements. To support this, this feature delivers a spreadsheet containing scalable estimates of the EDA data requirements attributable to Low MCCS. Additionally, accompanying documentation outlines the procedure used to produce the estimates.  See Confluence page  https://confluence.skatelescope.org/x/VrINCg
    • 13.6
    • Stories Completed, Solution Intent Updated, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI22 - UNCOVERED

    Description

      This enabler is in support of capability SS-53.

      Capture the top level (size, periodicity, availability, distribution/replication requirements) characteristics of the EDA data that is expected to be required for early system releases (PSI Mid/Low, AA0.5, AA1.0,...)

      Record the information at https://confluence.skatelescope.org/display/SE/SS-53+consolidate+design+for+Data+Management+in+early+array+releases

      Mostly this should be a review based on existing documents, with scaling for the estimated needs of the early releases.

      Separate estimates should be given for both Mid and Low.

      Note that this work is mainly intended to inform Storage and Network Hardware procurement for AA0.5 and AA1.0 , so we do not need exact numbers but a strategy that allows to procure the necessary storage as early as possible with good confidence that it's going to be sufficient for early array release and easy options for expand-ability if needed. 

      Attachments

        Issue Links

          Child Of

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SS-53 Consolidate design for Data Management in early array releases

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Done
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                v.mohile Mohile, Vivek
                a.bridger Bridger, Alan
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 1.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete26.0
                  Total26.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel