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

Deliver DSH LMC and GUI to commission first dish structure, SPF and SPFRx

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

Details

    • MID ART
    • Hide

      Enable testing of the first dish structure onsite to identify issues and optimisations.

      Show
      Enable testing of the first dish structure onsite to identify issues and optimisations.
    • Hide

      A - FAT of Dish Structure Controller and LMC in the ITF

      B - FAT of LMC to SPFC in ITF

      D - FAT LMC to SPFRx in ITF

      DSH.LMC Reviewed, demo'ed, released for DS Qualification

        • Critical and Major severity bugs addressed
      Show
      A - FAT of Dish Structure Controller and LMC in the ITF B - FAT of LMC to SPFC in ITF D - FAT LMC to SPFRx in ITF DSH.LMC Reviewed, demo'ed, released for DS Qualification Critical and Major severity bugs addressed
    • Inter Program
    • 9
    • 18
    • 0

    • Component Version REL-1282 DS Qualification software release 0.3.0

      Component Version REL-1131 DiSQ : Provide Dish GUI initial version

      Sub-system Version REL-1112 Dish LMC 3.0.0 - Archive attributes to EDA + ADR-9 Tango device name update

    • Team_KAROO
    • Sprint 5

    • PI22 - UNCOVERED

    • Team_KAROO
    • Mid G1 Mid G2 Mid G2

    Description

      The first dish is expected to be onsite (TPO-733) during PI21.

      Dish Structure assembly will take place:

      • Pedestal, Turnhead, Elevation Assembly, Indexer, Plant Installation, Control System

      Network Connectivity needs to be established (TAIV-841)

      • Dish Fibre Network (DFN)
      • Dish NSDN Switch
      • Dish LMC (HW and SW)
      • Connectivity to KAPB and Dish Verification System (DVS)

      Dish Structure testing will then commence (TPO-861). 

      Two GUI products are required to support dish structure testing during PI21:

      • DS Qualification SW & GUI (DiSQ) (TAIV-842) is available (Wombat)
      • Dish AIV Test GUI (DAIGu) (TAIV-788) is available (Karoo)

      Dish Structure Qualification is expected to commence late in PI22. 

      This feature must ensure that:

      • Both Dish GUI products are fit for purpose to support Dish Structure Testing and Qualification
      • Dish LMC-DS testing in the ITF (A) (TAIV-790)
      • Dish LMC.SPFC testing in the ITF (B) (TAIV-789)
      • Dish LMC.SPFRx testing in the ITF (D) (TAIV-830, TAIV-831)

      The following commands in the Dish LMC are currently outstanding and are expected to be implemented as part of this Feature:

      • Slew
      • Scan
      • Desired Pointing
      • AchievedPointing

       

      Attachments

        Issue Links

          Child Of

          Capability - SAFe program capability SS-114 Mid-C1: Complete first Mid system integration at the ITF (TAIV-101) and execute the Basic Health and Functionality Verification Event (TAIV-818)

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Implementing
          Is delivered by

          Component Version - Component/module/library releases REL-1282 DS Qualification software release 0.3.0

          • Draft

          Sub-system Version - A version of a sub-system, used in the Release Management and Configuration Management process REL-1112 Dish LMC 3.0.0 - Archive attributes to EDA + ADR-9 Tango device name update

          • Released

          Component Version - Component/module/library releases REL-1131 DiSQ : Provide Dish GUI initial version

          • Released
          relates to

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-2960 Integrate CETC54 Dish Structure Simulator with Dish LMC

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Program Backlog

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-3742 DISH AIV: Expose required SPFC attributes via Tango

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Program Backlog

          PI Risk - Program Increment risk for ROAMing ROAM-439 If SPFRx cannot be registered in the Dish.LMC Tango DB  THEN Dish.LMC integration with SPFRx will not be completed

          • Active Risk

          PI Risk - Program Increment risk for ROAMing ROAM-444 IF SPFC is not able to be started and registered in the dish.LMC Tango DB in the ITF THEN Dish.LMC integration efforts will be unachievable

          • Active Risk

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-3225 Support Dish LMC - SPFRx integration in ITF

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Program Backlog

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-2722 Dish engineering user interface

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-3226 Support Dish LMC - SPF integration in ITF

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Spike - A time limited investigation to get some knowledge SP-3432 Develop Dish Structure Qualification software - basic functionality

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-3202 Dish LMC time-out for long running commands

          • 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.
          • Discarded

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-3338 Dish LMC implements Slew command

          • 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.
          • Discarded

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-3203 Existing MeerKAT Dish Proxy runs in Gitlab repo

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Discarded
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                s.vrcic Vrcic, Sonja
                r.brederode Brederode, Ray
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (84.15%)

                  Feature Estimate: 9.0

                  IssuesStory Points
                  To Do612.0
                  In Progress   11.0
                  Complete3769.0
                  Total4482.0

                  Dates

                    Created:
                    Updated:

                    Structure Helper Panel