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

Fully configure/control multiple TPMs from MCCS

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

Details

    • Feature
    • Must have
    • PI14
    • 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 iitialization 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 iitialization and configuration on TMC command (ON command, subarray allocation/deallocation & configure commands)
    • 4
    • 4
    • 40
    • 10
    • Team_MCCS
    • Sprint 5
    • Hide

      This feature focued on refining and clarifying the proposals and plans to achieve the configuration and control of multiples of TPMs. As such coming out of PI14 MCCS now have a far clearer understanding and documentation of how this function should be realised.
      Confluence pages created through this feature include:

      As PI14 concludes planning stages of this feature have been completed and preparations are under way to refactor the pyaavs.Station and pyaavs.Tile classes to accommodate the proposals made. This activity can then continue through SP-2484 in PI15.

      Neither could the stretch of this feature be attained due to MCCS software bugs which prevented its deployment and so a demonstration could not be prepared.

      Show
      This feature focued on refining and clarifying the proposals and plans to achieve the configuration and control of multiples of TPMs. As such coming out of PI14 MCCS now have a far clearer understanding and documentation of how this function should be realised. Confluence pages created through this feature include: MCCS 874 - Monitor hardware connection status for Tile MCCS-968 - pyaavs Station modification plan Scenario for Turn-On Remote Deployment As PI14 concludes planning stages of this feature have been completed and preparations are under way to refactor the pyaavs.Station and pyaavs.Tile classes to accommodate the proposals made. This activity can then continue through SP-2484 in PI15. Neither could the stretch of this feature be attained due to MCCS software bugs which prevented its deployment and so a demonstration could not be prepared.
    • 14.6
    • Stories Completed, Integrated, Solution Intent Updated, Outcomes Reviewed, Accepted by FO

    • PI24 - 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

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

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

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

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 4.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete47.0
                  Total47.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel