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

Configuration of Stations / TPMs

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

Details

    • Feature
    • Must have
    • PI15
    • None
    • Obs Mgt & Controls
    • Hide

      Additional integration of hardware into MCCS, enables setting up full beamformer and monitoring. 
      Essential for supporting PSI, AAVS deployments. 

       

      Show
      Additional integration of hardware into MCCS, enables setting up full beamformer and monitoring.  Essential for supporting PSI, AAVS deployments.   
    • Hide

      Demonstration of configured registers, resource allocation/control of multiple TPMs from MCCS
      (stretch) integrate with TMC dashboard to show initialization and configuration on TMC command (ON command, subarray allocation/deallocation & configure commands)

      Show
      Demonstration of configured registers, resource allocation/control of multiple TPMs from MCCS (stretch) integrate with TMC dashboard to show initialization and configuration on TMC command (ON command, subarray allocation/deallocation & configure commands)
    • 2
    • 2
    • 40
    • 20
    • Team_MCCS
    • Sprint 5
    • Hide

      Work on defining the architecture for configuration was completed. Implementation work has not been completed and has been relocated to clone SP-2788.

      Show
      Work on defining the architecture for configuration was completed. Implementation work has not been completed and has been relocated to clone SP-2788 .
    • 15.6
    • Stories Completed, Outcomes Reviewed, NFRS met, Demonstrated, Accepted by FO

    • PI22 - UNCOVERED

    • mccs_software

    Description

      Fully configure/control multiple TPMs from MCCS (Simulated and/or real devices)

      Presently, control of TPM is limited to basic on/off and firmware bitfile load.  To use the hardware in a system, additional configuration steps must be done to set register values (gains, beamformer setup,  alarm limits). This feature also relates to enabling data-capture to file and supporting additional external processes as well as actions driven by TMC commands.

      Attachments

        Issue Links

          clones

          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-2486 Install/run hardware-facing k8s deployment

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

          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-2788 CLONE - Configuration of Stations / TPMs

          • 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
          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-1722 Plan MCCS Deployable on AAVS at site

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • 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-1564 Implement MCCS control of data capture from TPM

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Discarded

          Spike - A time limited investigation to get some knowledge SP-1604 MCCS Pointing Control Initial implementation of

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Discarded
          mentioned in

          Page Loading...

          Structure

            Activity

              People

                a.bridger Bridger, Alan
                v.mohile Mohile, Vivek
                Votes:
                0 Vote for this issue
                Watchers:
                4 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
                  Complete36.0
                  Total36.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel