Pete Bonasso Mark Boddy (Adventium) Dave Kortenkamp Scott Bell
1
Slide 3
procedure We have PRIDE & PRL for procedure authoring,
display and execution planning We have augmented PRIDE & PRL to
author & display planning information associated with
procedures that can be used by automated planners capturing and
maintaining the domain models The major stumbling block to
realizing the widespread use of automation techniques for
operations is capturing and maintaining the domain models needed to
support such techniques This project seeks to develop a framework
for consistent ontological modeling across domains, that can be
exploited by planners and executives currently being developed for
NASA 2
Slide 4
3 Ontological Development Environment PRIDE Plan Actions
TranslateTranslate PRL Procedure info to executives Procedures
& Planning Actions Planning Aid Planning Algorithms Ontology
Editor OWL Database Design Docs * Telemetry (ISS Configuration)
Goals Planning Actions Configuration snapshots http * CAMMP &
IMS (ORU locations) XML,RDF Procedures Plan Actions Models
Plans
Slide 5
Develop an authoring system for domain models (PRONTOE PRIDE
ONTOlogy Editor) Develop the ORU location kernel for EVA/ROBO (use
core kernels from Phase 1) Develop interfaces to online model data
Develop the ORU LOCation (ORLOC) application Identify methods to
integrate data with the models Test PRONTOE and ORLOC 4
Slide 6
Classes, subclasses and relations among them truss-segment,
ORU-bag, ceta-light can-hold (medium-ORU-bag, ceta-light) Class
instances LAB-ceta-light1, S1 located (LAB-ceta-light1) = S1
Directives Preconditions and effects, e.g., crew must possess a PGT
before unbolting a CETA light Axioms for bookkeeping and physics,
e.g., if a container is located at A, so are its contents
Constraints (includes flight rules), e.g., if a ceta-light heater
is not on then its lamp must be on Data - facts that represent a
specific configuration of all the instances, e.g., switch settings,
modes, locations 5
Slide 7
The base Floor of the ontology = classes and relations based on
modeling choices, e.g., Includes axioms Not editable by users We
have an all domains base & an ISS-base The kernel extensions
Per flight discipline, e.g., EPS, C&DH, EVA A starting set of
classes and instances of the ISS to be edited and expanded by users
The ontological data Collection of facts that represent a specific
configuration of all the instances Can be updated both manually and
electronically 6
Slide 8
User doesnt need to know about ontologies Add/delete/modify
data to support procedure authoring Navigate graphically through
the ontological hierarchy Invoke ontological reasoners to speed
relation entries Author and save what-if snapshots to use for
planning future activities Integrate with PRIDE Planning Wizard
Classes, instances and relations Axioms for bookkeeping and
constraint management Output to OWL files To be read and updated by
planning systems To be read and updated by procedure execution
systems 7
Slide 9
Ontology Editor
Slide 10
DC Switching Unit DCSUs Main bus switching unit MBSUs DC-to-DC
Converter Unit DDCUs Remote power controller module RPCMs
Multiplexer/Demultiplexer MDMs Flex hose rotary coupler FHRCs
InterFace Heat Exchanger IFHXs Battery Charge Discharge Unit BCDUs
Control Moment Gyro CMGs Cargo Transport Container CTCs Nitrogen
tank assembly NTAs Ammomia tank assembly ATAs Trailing Umbilical
System Reel Assembly TUS-RAs Pump Module Assemblies PMAs Utility
Transfer assembly UTAs YAW Joints YAW-Jts Solar Array Wings SAWs 9
Big 12 ORUs
Slide 11
OTSD ORU Temporary Stowage Device MUT-EE multi-use tether end
effector FGB/AGB fixed/adjustable grapple bar Ballstack LDTDT Long
Duration Tie-Down Tether RET/adjustable Retractable Equipment
Tether, also adjustable CETA-swing arm configuration WIF worksite
interface ORU tethers SPDM OTP (ORU and tool platform) APFR
articulating portable foot restraint SPD Spool Positioning Device
Safety tether Thermal booties/FPP (floating potential probe) QD
(quick disconnect)/Vent tools (bags) Toolbox MLI (multilayer
insulation) shrouds Tool bag Truss stowage bin capacity, contents,
launch locks GAP spanner Fluid jumper OIH On-orbiter Installable
Handrail Tether shuttle OIWIF On orbiter installable WIF Rail stop
(MT mobile transporter, ETR ( EXPRESS Transportation Rack), tether
shuttle Scoop D-handle 10 Not in 1074 Not in ExCATT Needs work
Slide 12
Quick graphical/textual search for items by class/subclass User
editing of item state, e.g., location, settings, anomalies Include
URI to Mission Integration Database Applications System (MIDAS)
(https://iss- www.jsc.nasa.gov/midasagnt/plsql/midas_home_oas/)
Include on-orbit media links (io.jsc.nasa.gov/app) Single locus of
ORU data Flight controllers prepare EVA activities and associated
equipment location changes (EVA Xfer Cue Card) Flight controllers
update models via completed EVA tasks Changes auto-generated and
sent to external databases (IMS, EXCATT) and others (ROBO,
Pointing, etc.) Auto-generation of reports by equipment type or
location Author and save what-if snapshots to use for planning
future ROBO/EVA activities 11
13 ExCATT OWL Database Query for differences JSON Event Files
JSON Event File Post after validating Changes from EVAs IMS API
Query for differences Change Form Post after validating ORLOC
Changes from EVAs
Slide 15
14 Base - Abstract Entity - Commands - PRIDE:CDRSarmCmd -
PRIDE:MDMrtEnable - Telemetry - PRIDE:smokeDetActiveBitStatus -
PRIDE:MDMframeCount Derived from PRIDE sysref
16 TASKS Quarters Principal STAFF 123456 Bonasso,Boddy, All 78
Year 1* Task 1: Refine Phase 1 base ontology Task 2: Develop editor
with Phase 1 Models Task 3: Design and develop data interfaces Task
4: Extend editor to support data editing Task 5: Iterate editor
development with SMEs Task 6: Build AP interface with OWL models
Task 7: Test models using Phase 1 scenario Year 2 Task 1: Use
editor to complete ORU models Task 2: Work with SMEs to select a
new scenario Task 3: Demonstrate plan generation for new scenario
Task 4: Develop ORLOC tool with SMEs Task 5: Demonstrate ORLOC in
new scenario Task 6: Document results and deliver software Demo
Test Final Report All Bonasso Bonasso, Boddy, SMEs Bonasso All
Bonasso, SMEs All Rpt All Editor1 Editor2 ORLOC- alpha ORLOC-beta
All Bonasso, SMEs *Overrunning resources
Slide 18
Ontologies Phase 1 ontology for core systems verified Redesign
of location modeling for Big 12 ORUs complete Phase 2 initial
modeling complete PRONTOE 0.5 complete Completed first round of
PRONTOE demos to interested parties IWPSS paper accepted/presented*
Modeling changes made based on user feedback ExCATT Phase 2
ontology used ExCATT part catalog and event files Can compare
ontology with ExCATT files IMS waiting on API (Russell Knights
work?) ISP have a preliminary design *Jeremy wants to meet 17
Slide 19
Develop PRIDE interfaces to Phase 2 ontology 1) Commands and
telemetry 2) Procedure editing 3) DOUG develop 1 st cut interface
(todays show and tell) Integrate with planner Develop I/O API for
Phase 2 ontology Initial OWL->PDDL completed and translation
plans achieved Working on axioms next PPW integration deferred to
next year ExCATT, IMS attend stakeholders meetings Paper to AI in
Space workshop 18
Slide 20
Limit one user read/write at a time User uses PRONTOE to edit
kernel and run reasoner Launching PRONTOE will trigger reasoner
Inferences to other kernels are posted User corrects problems to
achieve a consistent ontology Other users use svn status to check
for changes to their kernels Review the changes in PRONTOE If
accepted commit to repository If rejected => meet with other
users to resolve differences 19
Slide 21
Updates affect all kernels Reasoners must reach a fix point
=> no more inferences can be made Updates from planners can
expect to be logically ordered Asynchronous updates (e.g., ISP)
will be problematic Define a logical endpoint to an update (e.g.,
some quiescent state of the ISS) Run reasoner to a fix point and
check for consistency Accept inconsistencies from soft constraints
Run hard constraint violations to ground Is this an SBIR topic?
20
