SEDS + Common DoT



Schedule, prioritisation
Funding
Action Ownership
o Books
o Prototyping
o Testing
o Reviewing
Work Items


Schema
o Merge schemas (Kevin Rice)
1. SCISYS schema as baseline
2. Feature-by-feature merge of syntax from GSFC or Piotr schema
or replace with new syntax
 Ensuring the toolsets still work
3. Support both options & experiment?
o Collaborative Working (Sam Price to set up)
1. Track issues
 Discussion threads leading to consensus, including
o Split into multiple smaller schemas?
o Mandatory/optional features
o Use of ASN.1 or cut-down XTCE type system
(Felice)
o Bit field representation (Sam)
2. Configuration management
 3 repositories:
o Schema
o GSFC toolset
o SCISYS toolset
 NDA/teaming agreement
o Distribute small subsets to alpha user community (Jonathan Wilmot)
1. Objective:
 Experimental, likely to change
 Don’t build products on this
 Don’t distribute in uncontrolled fashion
 Get feedback
 Prevent replication of effort
2. Communities:
 ESA – SAVOIR WG
 NASA – JSC
 US Industry – SUMO
Use Cases for development purposes
o Use Cases
1. Software Components/smart devices (Sam Price)
2. Device drivers (SCISYS)
3. Modifying SDR Functionality in orbit (Sandra Johnson)


4. System Design tool (Ray Krosley)
5. Spacecraft Database Ingest (European Primes + SCISYS?)
o Devices
1. PS devices
 NPAL Camera
 GPS Receiver
 Software components
2. MAS devices
 ??? 1553 Sensor
o FOG Gyro
o Hydra Star Tracker
 ??? 1553 Actuator
3. RIU
 Not covered so far – ESA have an ongoing architectural
activity that may define a functional interface – let this
complete first
(Not?) Interoperability Testing (Who?)
o Determine what this means. Alternatives:
1. From same ICD
 make two device simulations
 used in two tool chains
 swappable between device simulations & tool chains?
2. Interoperability between a data sheet producer and a consumer
 Producer
o device manufacturer toolset
 Consumer
o Code generator toolset
o System Design or Spacecraft DB validator
3. Swappable between different toolsets
4. Simply exchange between different toolsets covering all
features
 Each toolset has an independent parser
5. Not testing the toolsets
o Yellow book for test plan and report
o Realistic, shareable reference devices/software components
1. Alternative is recorded telemetry?
2. Reuse in training material
o Cover all mandatory and optional features
Reference Toolset (Sam Price-led)
o Goal:
1. Training material & linked to green book
 Contain realistic reference devices
 E.g. for device manufacturers
2. Open source
o What does it contain?
1. GUIs (viewer, editor)
 Does something similar already exist from JSC?
(Jonathan Wilmot)
2. Import/export software library (Kevin Rice)


 Jaxb?
3. Code Generators? Must cover all major features
 Python (Sam Price)
 C++ / C (SCISYS?)
 Ada
 Java (Kevin Rice)
Standardisation
o Common DoT Blue Book & schema
1. Book Captain – Ray Krosley
2. WG Review draft book during teleconferences/email
o EDS Blue Book & schema (set of?)
1. Book Captain?
2. SCISYS-drafted book as a starting point
3. WG Review of RIDs raised
4. Maintain with schema is updated as we’re happy with each
update
5. Minimal informative, reference EDS Green Book
 Therefore complete draft EDS Green Book has to be
available when Agency Reviews occur
6. Want to be able to do minor, syntactic modifications to schema
without having to re-issue Blue Book
7. Action: Check with Tom Gannett as to best practise for CCSDS
as to where normative text should live. Should it be determined
by the XML SIG? E.g. Should we have
 Schema is normative, annotations are normative
 All descriptions are in Blue Book, schema references
sections of blue book
 Where normative cannot be captured in schema, e.g.
rules for use, then this will be in the Blue Book
o EDS Green Book
1. Book captain (Stuart Fowell) + other contributors
 We already have a lot of this material, some of it is in
old EDS Red Books, some rejected from SOIS Green
Book issue 2 as too detailed
2. Objectives:
 Handbook on EDS, covering
o Commentary on structure of EDS & best
practise on use for capturing information
o Examples EDS use cases
o Do’s & don’ts on writing toolsets & processes
 Training material
3. Contents List
Generic Functional Interfaces
o Should this be a CCSDS standard?
o Not doing within this WG
o ESA - SAVOIR-SAFI WG’s responsibility
o US – Jim Lyke is interested in this
Schedule
Fortnightly teleconferences/web-ex of 30 minutes to 1 hour for on-topic status
updates
 Issues primarily dealt with by discussion threads
 Augmented by teleconferences - if there are specific topics we can pre-arrange
a longer meeting
November 2013:
 Collaborative working environment set up
End of 2013:
 Baseline (set of?) merged schema
Spring 2014:
 Report back on updated toolsets & alpha community
 Updated Red Books and Draft Green Book ready for WG review
 WG Review of Red Books and Draft Green Book
 Interoperability Test Plan (Yellow Book)
Fall 2014:
 Interoperability Test complete
 1st Agency Review of Red Books
 Reference Toolset
End of 2014:
 CESG Poll to publish Blue Books and Green Book
End of 2015:
 Schema version 1.1
Actions
1. Sandra Johnson to produce use case of modifying SDR radio functionality in
orbit. 31/01/2014.
2. Sandra Johnson to provide SDR ICD to NASA and Ray Krosley. 30/11/2013
3. Chris Taylor to provide contact to Sandra Johnson on ESA contact for
reprogrammable FPGAs. 01/11/2013.
4. Stuart Fowell to doodle for regular date for teleconferences. Preferred day of
the week is Wednesday (Glenn struggles for Tuesday, Chris for Thursday,
Stuart for Monday, no-one wants to do Friday).
a. WebEx rather than telecon?