3/3/2009 1 Topics • Standards as a pursuit • What (really) is SPA and is the world waking up to SPA-like strategies • The “GIST” of it • Teaching SPA through cubes Surface Effects and Glue: Illusion of Standardization • Standards often address “surface effects” • Do not guarantee rapid Payload Bus integration • “Glue” and/or code rewrite required to integrate the pieces • Developing the “glue”, code, and debugging the interface kills prospects for rapid integration Physical Illusion of “Plug-and-play” External “Plug” but no Internal “Play” rapid integration True “plug-and-play” appeals to deeper concepts than simply standardization Custom Hardware/Software required! Standards are great to choose from (there are so many!), but they are NOT enough
Transcript
3/3/2009
1
Topics
• Standards as a pursuit• What (really) is SPA and is the world
waking up to SPA-like strategies• The “GIST” of it• Teaching SPA through cubes
Surface Effects and Glue: Illusion of Standardization
• Standards often address “surface effects”
• Do not guarantee rapid Payload Bus
gintegration
• “Glue” and/or code rewrite required to integrate the pieces
• Developing the “glue”, code, and debugging the interface kills prospects for rapid integration
Physical Illusion of “Plug-and-play”
External “Plug” but no Internal “Play”
rapid integration• True “plug-and-play”
appeals to deeper concepts than simply standardization
Custom Hardware/Software required!
Standards are great to choose from (there are so many!), but they are
NOT enough
3/3/2009
2
What is SPA?
• A set of principles that facilitate the automatic resource description resourceautomatic resource description, resource discovery, network self-organization of systems, and facilitates the automatic management of components (“care and feeding”) and relationships between those componentscomponents
• I think this is really just taking steps to guarantee semantic alignment
SPA Status• SPA Workshops (eight from 2004-2006)• Creation of Responsive Space Testbed to support creation of
“responsive technologies” like SPA (late 2006)g ( )• Development of key SPA technologies
– Supporting avionics (SPA-U hubs, high current breakers, SPA-S routers, SDM-capable hosts) 2005-2008
– XTEDS schemas established 2005-2008– SDM open source development 2006-2008– Test bypass 2006-2008Test bypass 2006 2008– Push-button toolflow demonstration 2005-2007 (Mission Spacecraft
Design Tool or “MSDT”)• Flight developments
– RESE (SPA-U, 4-port) – Launched and operated September 2007– TacSat 3 (SPA-U, 4-port) – Integration into TacSat 3 (Launch in 2009)– PnPSat (SPA-S, 48-ports) – Full PnP-based spacecraft (Launch in
2009?)
3/3/2009
3
Core Technologies• Space Plug-and-play Avionics (SPA) is
– a set of technologies– a “brand” of plug-and-play (PnP) focussed on shortening the time to
construct a complex system
• Key technology elements– Hardware
• Self-describing components and self-organizing networks• Interfaces and interface modules (ASIMs)
– SoftwareEl t i d t h t (“XTEDS”) d th i b l• Electronic datasheets (“XTEDS”) and their vocabulary
• Automation of component discovery and exploitation (SDM)– Tools
• Design (push-button toolflow)• Test / integration (test bypass)
3/3/2009
4
Some important parts of SPA
• The interfaces (not just SPA-S)• The software that facilitates discovery • The provisions for semantic alignment• The tools to ensure the generation of
constructible system configurations• Other things
“platform”
“platform”
Plug-and-Play ComponentsBlack-Box Objects
plug-and-play plug-and-play
driver
USB interface chip
plug and playcomponent
electronicdatasheetcomponent
App
liqué
Sens
or
Inte
rfac
e M
odul
e (A
SIM
)
interface module
component
3/3/2009
5
high data rate (< 620 Mbit/sec)
SPA-S
Very high data rate <10 Gbit/sec
“SPA-10” (future)om
pone
nts
low data rate (< 1 Mbit/sec)SPA-UP
erfo
rman
ce o
f co
Very low data rate (< 10 kilobit/sec)“SPA-1” (future)
Number of components
SPA-y Network
Heterogeneity
Bridge Node
SPA-x Network
3/3/2009
6
Application#1
Application#2
Application#N
Mission Code / Scripts
Application#iod
el
The Satellite Data Model (SDM) – Building Awareness into Plug-and-play
#1 #2 #N#i
Sensor Manager (SM) SM SMSMProcessorManager
Task Manager Data Manager
Sate
llite
Dat
a M
o
CameraThermometer
GNC CompCurrentMonitor
RF CPU
eXtended Transducer Electronic Datasheet
• Primary mechanism for self-description
XTEDS
p– Embedded in hardware and software
applications– Describes “knobs” and
“measurands”• Conveys “semantic precision”
through a common data dictionary (CDD)
(facet)
Interface Interface
M M
(facet)
y ( )• Enforces order in the “LEGO
universe” of SPA (features only exist if known through XTEDS)
Message
Variable
Message
Variable
CDD
3/3/2009
7
Applique sensor interface module
SPA (plug-and-play) thermometer
To simplify the testing of complex systems, a “test bypass” feature is integrated in the SPA plug-and-play interfaces. Test bypass allows an external control (simulation) to provide substituted values during test, similar to the test/debug methods used in developing software. Test bypass is particular useful in cases where an actual test involving a device’s native sensors and actuators is impractical.
Mission Goals and Requirements Component Capabilities
A2. 3.
AUTODrag & Drop Design
************************************************************************** CATEGORY RULES ************************************************************************** En
• Form working groups to integrate web-based design flows based on (e.g.) Drupal.org content managementflows based on (e.g.) Drupal.org content management system (CMS). This will allow the use of scalable web-enterprise solutions to be used to define, procure, and otherwise coordinate a large number of Cubeflow-related developments. We are hopeful of awarding at least three Phase 1 projects through the current AFRL SBIR solicitation that will result in MOSA-compliant PnP nanosat modules for radio and deorbit functions. Many other modules will likely emerge from the proposed outreach initiative.
Example XTEDS builder
3/3/2009
9
Example ASIM code generator
Example SDM application builder
3/3/2009
10
A Web-based tool flow!?Drupal CMS distributed CubeFlow
Electronic Data ASIM code wrapper SDM application Configurator/Electronic Data sheet creator
ASIM code wrapper/ generator
SDM application builder
Configurator/ package generator
Replace “Design by Committee” by “Design with Community”
SpacecraftDesign
SpacecraftBus Wizard
SpacecraftPayload Wizard Interaction
a – on shelfb “ dd t h i t”
a b cb – “add to shopping cart”c – use “instant RFI” to acquire
3/3/2009
11
Automated Spacecraft Design
Mission CaptureOrbit Design
/ Launch Selection
Design VerificationSpacecraft
Design
SpacecraftBus WizardInteraction
9K 9K 9K 9K
9K
9K
9K
a c zb
GNC SubsystemDesign Wizards
Power SubsystemDesign Wizards
Thermal SubsystemDesign Wizards
Mech SubsystemDesign Wizards
Component Libraries
Web-based Design Flow• Supports user-defined modules (like add-ins for web
browser) to assist component purchase and subsystem ) p p ydesign
• Core and contributed modules are drag-and-drop• Design flow engines can be distributed (along with
• Selection of command and data handling system componentssystem components
• Tools would understand computation challenges of mission and guide user to the selection of useful components
• Network simulations could be bundled with t l t id bl di ti ftool to provide reasonable prediction of on-board processing, storage, and bandwidth / interface needs
Propulsion
• Mission needs for propulsion understood by toolStation keeping– Station keeping
– Executing changes in mission phase (to include de-orbit)
– Etc• Simulation / scheduling could be integrated in
mission design process for sizing / componentmission design process for sizing / component selection
• Set of modular components, algorithms, etc chosen
3/3/2009
16
Guidance, Navigation, and Control
• Needs for GNC inferred from mission i trequirements
– Attitude knowledge– Attitude control
• Complex analyses done under the hood• Component and algorithm selections are• Component and algorithm selections are
generated (if solutions can be found)
Power, Management, and Distribution
• Launch, orbitology determine visibility to sun (i.e. integrate Joules for energy supply)integrate Joules for energy supply)
• Mission characteristics determine the need for energy– Peak, sporadic, vs. continuous
• The set of components allow an energy balancing act to be performed driving selection
f fof components and generation of algorithms, etc that implement the “charge management policies” of a spacecraft
3/3/2009
17
Radio Subsystem• The topology of spacecraft, relation of spacecraft to
other “objects” knownj– Other spacecraft– Ground control– Ground users
• Intersection geometries, data rate needs can be extracted from mission specifications link analyses can be done automatically
• Waveforms can be inferred or established• Waveforms can be inferred or established• Radio architecture can be specified as a collection of
fixed and configurable components along with bitstream specifications of software-definable radio equipment
Mission > Space WeatherMission Selection Orbit Design Spacecraft Synthesis
Tactical Comm Comm Space MiscSurveillance Relay BFT Weather (ad hoc)
Tactical Comm Comm Space MiscSurveillance Relay BFT Weather (ad hoc)
SelectMissionClass
Pick payload
Constel-lation
SatAdmin/
op
1 satellite (no constellation)
2 satellites
3 satellites
4 satellites
5 satellites
6 satellites
The “GIST” of it• Problem: there are significant barriers to
the promoting operationally responsive spacespace– Globalization: what can we say publically
(ITAR-free)?– Internationalization: how can we effectively
work with foreign companies / governments?S ff– Standards: what is important and effective to standardize and how do we do it
– Technology: it’s the thing we are operating onORS (and the US) needs an effective “GIST”
Strategy!
3/3/2009
20
Plans for Developing and Distributing StandardsDevelop
StandardsDevelop ORS Standards for Spacecraft, Comm, Launch, etc.
Nationalize
Internationalize
GlobalizeDetermine/develop publicly-releasable versions and publish
Collaborate on developing &codifying international standards w/ select countries
Develop collaborative consortium in US; widely distribute standards
39
Preliminary discussions with legal counsel and DoS indicate that ORS standardsare most likely export-controlled “Technical Data” (see 22CFR120, §120.10 )
Scope of “Develop Standards”
• Develop Standards for…– Spacecraft
• e.g., SPA, ISETComm Links– Comm Links
– Launch Vehicle/Integration– Ground/Launch Ops
• e.g., GMSEC
• Facilitate Adoption of Standards– Workshops, Coursework, etc.
H l D k
40
– Help Desk
3/3/2009
21
Internationalizing ORS
Near-TermTime
Mid-Term Longer-Term
CompleteProject
Agreement
CompleteTechnical
AssistanceAgreement& New PAs
InitiateTechnology DevelopmentCollaboration& International
Agreement
D i ti
41
Descriptions• Project Agreement: USG co-funds R&D at foreign entity• TAA: US & foreign entities exchange export-controlled info• Export License: US & foreign entities exchange h/w, s/w details• International Agreement: Treaty with one or more foreign countries
to collaborate on specific system or technology development
Approach to Internationalize ORS Standards & Technology
• Start with SPA—develop processes to be used for other technologies– Develop strong working relationships with DDTC & DTSAp g g p– Establish SPA Technology Assistance Agreement
• Identify desired “partners” in US and abroad• Establish “Licensee” and “Sub-licensee” relationships
– Minimize number of Licensees to expedite approval• Obtain approval of initial Agreement• Periodically modify Agreement (existing agreement in effect)
– Add new “partners” to AgreementConvert select Sub licensees to Licensees
42
– Convert select Sub-licensees to Licensees– Move beyond Standards—Initiate collaboration on SPA technology
• Use similar but tailored process for other technologies– Structures, thermal, software, etc
3/3/2009
22
Potential Overarching Solution
• Explore establishing an International Agreement (Treaty) with European countries for “small” or(Treaty) with European countries for small or “responsive” satellite technology– There are many IAs in defense-critical technologies
• e.g., MDA MOUs with UK, Japan, etc.
– Could help reduce the serious ITAR obstacles for the US space industry
43
• Companies or industry associations might assist
– Would require Congressional support
Globalization• ITAR significantly impairs all of from developing open
standardsstandards– Recent Economist articles provide excellent synopsis of this
• ITAR is like a knife’s edgeW i il d d id h h d i il ll• We are imperiled to decide where the edge is unilaterally
• Past precedence in public release do not equal to legal precedence
• We ultimately must negotiate a position with the US State Department (for USAF, we must involve SAF/IA)
3/3/2009
23
Can’t we do …anything?
• Sure, globalize the XTEDSGl b li i thi• Globalize generic things
• Standards can be protected as US only, even classified (e.g. CDL is a classified standard) standards can be OPEN– Try not to be more restrictive to necessary– None of us (in this room) can trump the US
State Department (but if ORS is willing to clear our documents, go for it?)
What can we standardize?
• Plenty • Let’s even do something simple
– Define your radiation requirements• More ambitious
– Go ahead and standardize all of the SPA conceptsconcepts
• Don’t standardize things unnecessarily (e.g. ASIMs)
3/3/2009
24
Let’s Look at a Good Real World Example: the USB interface (www.usb.org)
Example: the USB interface (www.usb.org)The ubiquity of USB in no way alleviates the need to support
a community of interested users / developers
3/3/2009
25
Example: the USB interface (www.usb.org)
Information about USB products*, training, certification, logos
* Includes a searchable knowledgeable base of compliant USB products, components, tools,etc.
Example: the USB interface (www.usb.org)
Information/resources for USB developers
3/3/2009
26
Example: the USB interface (www.usb.org)
Identifies the “interested” community*
*the website itself was setup by a non-profit 401(c)(3): the USB Implementers Forum, supported by paid memberships
Example: the USB interface (www.usb.org)
Press releases, news, upcoming events
3/3/2009
27
Example: the USB interface (www.usb.org)
Then, the various “products” are identified which includes USB standard, hi-speed, “on-the-go”, wireless USB, USB 3.0
Example: the USB interface (www.usb.org)
Oh, and don’t forget the standards
3/3/2009
28
Observations
• USB, Lonworks, and other successful i t f t h l i h d thinterface technologies have used the “foundation” concept to establish a “go-to” place for the standards and their associated infrastructure
• A standard by itself is simply a complianceA standard by itself is simply a compliance document
Other issues
• We have no “go-to” place to deal with standards that are embryionic nonstandards that are embryionic, non-existent, just an oral tradition (see “Jim”, see “Don”)
• Some parts of plug-and-play technology have a “live” nature (examples include the common data dictionary electroniccommon data dictionary, electronic datasheet templates, and the OpenSat database)
3/3/2009
29
Approach• Establish a foundation within a non-profit to
serve as a go-toserve as a go to• Support needed for
– Secretariat administrative roles for brokering the standards to a publishable form
– Supplemental IT support to create the public and member only sections of the website and support the databases necessarydatabases necessary
– Manpower to create the documents, evolve to a useable form (ex. In PnP, anyone smart enough to create the document is dedicated to creating the technology – sound familiar?)
An outreach concept
• Based on simple idea: learn SPA by doing SPASPA
• Focus on CubeSats as a teaching tool that can be scaled or even applied directly to simple flight missions
• This is the closest thing to a stimulus k I thi k f li it d b d tpackage I can think of on a limited budget
(combined with a web toolflow development)
3/3/2009
30
Miniaturization CubeFlow = SPA+CubeSat
• Targeting PnP platforms as small as pcubesats (100mm)
• Supports increased payload mass fraction and creation of PnP nanosatellites
• Compact nanosat modular form factormodular form factor (NMF)standard (70mm x 70mmx12.5mm)
A MOSA for Cubesats• Goal (Summer 2008) was to break “Swiss watch”
effect and promote interchangeability of components between different development groups
• More than that, we want plug-and-play components• The advent of a “table-top” satellite that could be as
easily integrated as a personal computer.personal computer.
If Dell were building satellites, we think they’d be this way: “CubeFlow”
3/3/2009
31
Nanosat Modular Format (NMF)
• Promoting interchangeability requires breaking down the cube into modular partitions This 1U cube has seven “spaces”partitions. This 1U cube has seven spaces , six being NMF panels (70x70x12mm) with an interior compartment.
1x1 Panel
Exterior Rails to
Interface with P-Pod
Electronics Bay SizesModule Size (mm) Structural Side
(mm)
70 x 70 x 12.5 100 x 100 x 10
70 x 160 x 12 5 100 x 200 x 1012.5
160 x 160 x 12.5 200 x 200 x 10
3/3/2009
32
Flexible Sizes and Shapes
1x1x11x1x1 1x1x1 Card Cage1x1x1 Card Cage 1x1x2 Card Cage1x1x2 Card Cage 1x1x1 with 1x1x2 1x1x1 with 1x1x2 Card CageCard Cage
2x2x22x2x2 1x2x21x2x2 1x1x21x1x2 1x1x2 with 1x1x1 1x1x2 with 1x1x1 Card CageCard Cage
CubeFlow devices / systems• Using Space PnP avionics
(SPA) approach, cubes can be decomposed into
lf d ibi1x1 NanoSPA computer 1x1 NanoSPA radio 1x1 NanoSPA power module self-describing
components, just as in PnPSat
a oS po e odu e
1x1 NanoSPA GNC module1x1 NanoSPA payload module
1x2 NanoSPA payload module RXN Y
RXN X
RXN Z
HubC&DH
HubTherm
Hub SimpleCamera
Therm
Software Radio
3/3/2009
33
RecommendationsCubeFlow ShortCourse
• Create 12 CubeFlow bus kits to be furnished to selected groups in a special short course (slated for March 2009)groups in a special short course (slated for March 2009) timeframe. In the 2-day course, each participant will assemble and develop simple SPA devices and SDM applications under guidance of subject matter experts. The kits will contain all the pieces necessary to assemble the shells of two (1U and 2U) CubeFlow busses, complete with at least four ASIMs, a SDM-enabled host, cables, panels, and supporting software infrastructure. Attendees will make a "soft MOU" with AFRL/ORS to develop at least one non-trivial CubeFlow bus component over the next 12 months. If the first course is successful, we will seek to repeat for two more cycles of 12 kits each on 4-6 month intervals.
Outreach – a bold (?) idea• 1 class = 12 groups• 10 classes = 120 groups (within one year if we can get10 classes 120 groups (within one year if we can get
the support, by running multiple workshops in Albuquerque and other sites)
• Establish the CubeFlow network to create a ready supply / coordination network (a Web-based “ChileWorks”
• Even if only ¼ of the participants do something, we should have at least 30 SPA components that can be f l dfreely procured
• If ORS can support launch for even 10% of the teams (by reserving dispenser slots on ORS missions), we’ll probably quadruple the number of components
3/3/2009
34
Summary• GIST: the best way to energize the internationalization of
ORS standards and technologiesORS standards and technologies– Globalize
• Develop publicly-releasable “standards”• Encourage publishing—provide guidelines (a la CANEUS)
– Internationalize• Facilitate/expedite existing and future PAs (DoD process)• Establish and update a Technology Assistance Agreement to allow
US and foreign firms to collaborate on Responsive Space (RS)US and foreign firms to collaborate on Responsive Space (RS) standards (DoS process)
• Facilitate export licensing to allow US and foreign firms to jointly develop RS technologies (DoS process)
• Explore/facilitate establishing a RS International Agreement– Standarize
• Much of SPA already is standard, we may not be able to globalize it “as is” 67
Summary• SPA is the response of one application domain (space)
to perennial problems relating to complex systems built ithi l b iwithin complex bureacracies
• Standardization is by itself nothing• We must focus on purpose
– Waiting for someone to “embrace” standards may be a vain hope• Teaching and outreach seem to be overlooked as the
single best way to spread MOSA concepts• We are attempting to pursue an approach that teaches p g p pp
SPA in a way that promotes a bottoms-up disruption• Today’s students are tomorrow’s satellite builders• Today’s satellite builders don’t have to wait
![[Document Title] - CCSDS.org Documents... · Web viewKFKI Research Institute for Particle & Nuclear Physics (KFKI)/Hungary. Korea Aerospace Research Institute (KARI)/Korea. MIKOMTEK:](https://static.documents.pub/doc/80x56/5aa679907f8b9a7c1a8eb9fb/document-title-ccsdsorg-documentsweb-viewkfki-research-institute-for-particle.jpg)
