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

Scheduling Block definitions

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

Details

    • Hide

      Elaborating the models in key areas supports activities that are required to de-risk the proposed software architecture, in particular interfaces between OSO (OET) and TMC and also the interface between TM (OSO) and SDP.

      Show
      Elaborating the models in key areas supports activities that are required to de-risk the proposed software architecture, in particular interfaces between OSO (OET) and TMC and also the interface between TM (OSO) and SDP.
    • Hide

      To be updated

      Document describing processing blocks and JSON Processing Block Schema developed, reviewed and agreed by stakeholders from:

      • SDP architects
      • SDP SIP team
      • SDP DALiuGE team
      • SKAO Feature Owner.

      Document format confluence page.

      Show
      To be updated Document describing processing blocks and JSON Processing Block Schema developed, reviewed and agreed by stakeholders from: SDP architects SDP SIP team SDP DALiuGE team SKAO Feature Owner. Document format confluence page.
    • 1
    • 1
    • 5
    • Team_SARCH
    • Sprint 4
    • Show
      https://confluence.skatelescope.org/pages/viewpage.action?pageId=74731324
    • 4.6
    • PI22 - UNCOVERED

    • SARCH_Interest SOW9_ObsMgtControlsSupport Team_SARCH

    Description

      OUTCOME:

      https://confluence.skatelescope.org/pages/viewpage.action?pageId=74711226

      https://confluence.skatelescope.org/pages/viewpage.action?pageId=74731324

       

      The SB definition will continue to evolve over the first few years of construction, significantly and quickly in the earlier period.

      What is needed at this point is sufficient elaboration in order to support System CDR de-risking activities, especially in these main areas:

      1. Prototyping of SB execution, at a minimal level (relates to SP-40, --SP-80--)
      2. Elaboration of the SB definition also relates to the more detailed M&C data model elaboration that is needed.
      3. What are the use cases for Observing Groups and can they be supported in the wider architecvture? (See final comments in --TMCDR-537--).

      For (1) a possible approach is sufficient elaboration of the SB that would allow a first OET prototype to be able to use and SB and its associated observing script to configure a receiver band and point the telescope(s) and set them tracking.  This could be extended to other configuration setups later / as needed.

      For (2) this could be extended to include elaborating the M&C data model - but that is not part of this ticket. Implementing something for (1) simply allows (3) to go ahead.

      Item (3) requires a wider analysis, and science input.

      Lastly, in support of (1)-(2) some thought should be given to the data exchange and local persistence format of SBs and PBs.   Is this JSON?     The long term persistence (in the ODA) is a separate concern.

       

      OLD TEXT

      This task would be in support of ----SP-41---, SP-50  and SP-51. It will expand the current definition of a Scheduling Block in the Project Data Model to provide a simple but realistic version 1 that may be used in the evolutionary control prototype for section -----SP-41----, and to provide inputs to the planning tools in SP-50 and SP-51 and enable the creation of Processing Blocks that may be used for the sub-task of SP-51 that utilises the SDP planning interface. In order to do this an initial definition of PBs will also be developed. 

      SoW Chapter 3.16

      Attachments

        Issue Links

          Structure

            Activity

              People

                n.rees Rees, Nick
                m.miccolis Miccolis, Maurizio
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 1.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete12.0
                  Total12.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel