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

CSP.LMC implements the correct DISH ID format (ADR-32)

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

Details

    • True
    • Obs Mgt & Controls
    • Hide

      Adopt use of the correct Dish IDs.

      Why now:  DISH ID is used in virtually all M&C components in the MID Telescope.  Current implementation uses numerical only DISH IDs which does not align with the actual DISH ID defined  by the SKA documents and used by the Telescope Delivery Teams,  Contractors and Operations. 

      All user interfaces, including logs, alarms, and dashboards,  should use the correct DISH ID  to avoid misunderstanding.   A maintenance person in the desert should see the same DISH ID painted on the dish, shown in technical documents and diagrams,  and displayed on the screens.

      DISH ID is embedded in the digitized data flowing from the DISH (more specifically SPFRx) to CBF, if we use different IDs internally and externally that will inevitably lead to confusion.

      If implemented early, this is a small change that affects many components.

      If we continue using numeric-only Dish ID, user interfaces and other interface software will need to be updated later when the Meerkat dishesare integrated, i.e. when  the bulk of M&C software has been developed, integrated and released. By that time we will develop  many more software components and user interfaces and the change will require more resources.

      Show
      Adopt use of the correct Dish IDs. Why now :  DISH ID is used in virtually all M&C components in the MID Telescope.  Current implementation uses numerical only DISH IDs which does not align with the actual DISH ID defined  by the SKA documents and used by the Telescope Delivery Teams,  Contractors and Operations.  All user interfaces, including logs, alarms, and dashboards,  should use the correct DISH ID  to avoid misunderstanding.   A maintenance person in the desert should see the same DISH ID painted on the dish, shown in technical documents and diagrams,  and displayed on the screens. DISH ID is embedded in the digitized data flowing from the DISH (more specifically SPFRx) to CBF, if we use different IDs internally and externally that will inevitably lead to confusion. If implemented early, this is a small change that affects many components. If we continue using numeric-only Dish ID, user interfaces and other interface software will need to be updated later when the Meerkat dishesare integrated, i.e. when  the bulk of M&C software has been developed, integrated and released. By that time we will develop  many more software components and user interfaces and the change will require more resources.
    • Hide

      CSP LMC acceptance tests demonstrate propagation of the correct Dish ID through CSP LMC to CBF as per ADR-32.

      Note:  CSP.LMC currently does not implement interface with PST and PSS. When implemented, that interface will use the correct DISH ID.

      All user interfaces: CLI, logs, and Dashboards display the correct DISH ID.

       

       

      Show
      CSP LMC acceptance tests demonstrate propagation of the correct Dish ID through CSP LMC to CBF as per  ADR-32 . Note:  CSP.LMC currently does not implement interface with PST and PSS. When implemented, that interface will use the correct DISH ID. All user interfaces: CLI, logs, and Dashboards display the correct DISH ID.    
    • 2
    • 0.5
    • 0
    • Team_CREAM
    • Sprint 1
    • Hide

      The assign resources can now assign receptor id in ascii format according to ADR32.
      The receptor id is propagated to the subsystem.
      MR: https://gitlab.com/ska-telescope/ska-csp-lmc-mid/-/merge_requests/80

      The new template for assignment of resources is: https://developer.skatelescope.org/projects/ska-csp-lmc-mid/en/latest/templates/templates.html#assign-resources

      Released ska-csp-lmc-mid v0.14.0 (https://jira.skatelescope.org/browse/REL-534)
      The new chart will be integrated into SKAMPI as soon as CSP.LMC clients have implemented the new format.

      Show
      The assign resources can now assign receptor id in ascii format according to ADR32. The receptor id is propagated to the subsystem. MR: https://gitlab.com/ska-telescope/ska-csp-lmc-mid/-/merge_requests/80 The new template for assignment of resources is: https://developer.skatelescope.org/projects/ska-csp-lmc-mid/en/latest/templates/templates.html#assign-resources Released ska-csp-lmc-mid v0.14.0 ( https://jira.skatelescope.org/browse/REL-534 ) The new chart will be integrated into SKAMPI as soon as CSP.LMC clients have implemented the new format.
    • 18.6
    • Stories Completed, Outcomes Reviewed, Accepted by FO

    • PI22 - NOTRUN

    • Team_CREAM
    • SOL-G4

    Description

      CSP LMC  MID consistently uses DISH ID  in the format defined by ADR-32.

      CSP.LMC MID accepts commands that provide DISH ID  in ADR-32 format.

      The commands CSP.LMC MID uses to assign resources and configure CBF and PST resources use ADR-32 compliant DISH ID.

       

       

       

      Attachments

        Issue Links

          relates to

          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-2909 TMC implements the correct DISH ID format (ADR-32)

          • 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-3034 DISH.LMC implements the correct DISH ID format (ADR-32)

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

          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-3469 MID TMC provides API for the DISH to VCC Mapping Table and correctly handles initalisation and updates

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

          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-3777 MID CSP.LMC provides API for the DISH to VCC Mapping Table and correctly handles initalisation and updates

          • 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-1795 Mid.CBF and SPFRx Implement ADR-32 DISH ID

          • 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

          Architectural Decision - Software Architectural Decision ADR-32 SKA MID Telescope: DISH ID

          • decided
          mentioned in

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                s.vrcic Vrcic, Sonja
                s.vrcic Vrcic, Sonja
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete13.0
                  Total13.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel