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

CLONE - Configuration of Stations / TPMs

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

Details

    • 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.5
    • 2.5
    • 40
    • 16
    • Team_MCCS
    • Sprint 5
    • Hide

      Configuration of TPMs required work on the low-level support libraries (MCCS-969) and the MccsTile device (MCCS-970). This work provided for full configuration and the necessary command paths.
      The top level downward flow of configuration required changes to accommodate the ADR-51 decision. The necessary investigative work was completed (MCCS-1166) but the implementation (MCCS-1058) was incomplete and it will be necessary to resume this work in PI17.
      Work on station initialization (MCCS-971) was not completed and will also require attention in PI17. Note that the "thin slice" control script is performing this function currently.

      Show
      Configuration of TPMs required work on the low-level support libraries (MCCS-969) and the MccsTile device (MCCS-970). This work provided for full configuration and the necessary command paths. The top level downward flow of configuration required changes to accommodate the ADR-51 decision. The necessary investigative work was completed (MCCS-1166) but the implementation (MCCS-1058) was incomplete and it will be necessary to resume this work in PI17. Work on station initialization (MCCS-971) was not completed and will also require attention in PI17. Note that the "thin slice" control script is performing this function currently.
    • 16.6
    • Stories Completed, Integrated, Outcomes Reviewed, NFRS met, Satisfies Acceptance Criteria, Accepted by FO

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

          • 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

          Structure

            Activity

              People

                v.mohile Mohile, Vivek
                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: 2.5

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete314.0
                  Total314.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel