S1000D

1
S1000D SCORM Integration Update
Steven Grant, Boeing Jennifer Brooks,
ADL Travis Carlton, Boeing Advancing ADL
through Global Collaboration Melbourne,
Australia October 3, 2005
2
S1000D Status and Roadmap

• Steven Grant
• Technical Data Service Manager
• Boeing Australia

3
What is S1000D?

• S1000D is the governing specification for
  Military Maintenance and Technical Publications.
• The specification adopts principles from
• International Organization for Standardization
  (ISO).
• Continuous Acquisition and Lifecycle Support
  CALS). (Formerly Computer-aided Acquisition and
  Logistic Support)
• A set of military specifications originating from
  the US military and is being taken up by several
  other allied nations.
• World Wide Web Consortium(W3C) standards,
• for example, S1000D uses the CALS philosophy of
  "create once use many".

4
Global Cooperative Trends

• In the 80s, DoD set the standards used for
  support
• Currently, ISO, ANSI and significantly the W3C
• Groups like AIA, ATA,ADL/SCORM and ASD are
  defining application standards from commercial
  industry baselines and technologies
• Memorandum of Understanding between AIA, ATA,
  ADL/SCORM and ASD represents a good working model
  of this future
• With the latest initiative of Network Centric
  Operations, data tagging and exchange standards
  become more and more important.
• US Joining the standards work
• Training joining the collaboration
• ATA/Airlines joining the standards work.

5
Why S1000D?

• Original IETM Mil-Std was never updated in order
  to stay abreast of numerous technology
  enhancements
• Mil-Std 87268 and 87269 released in 1993
• S1000D covers Both Type I and Type II Data
  (replaces Class I to V IETMs)
• Data Formatting Allows For
• Data Exchange Across Platforms (S1000D Tagging
  Influence)
• Data Reuse (87269e Influence)
• Data Formatted Using S1000D Enforces Viewer
  Commonality

6
Collaborative History

• 2000
• AIA and US DoD and industry joined forces in
  developing a truly Worldwide technical data
  specification.
• 2003
• Formal MOU signed between AIA and AECMA,
  signifying formal collaborative working agreement
  on S1000D incorporating the best of the US
  standards into S1000D.
• 2004
• Formal MOU between signed ADL and AECMA,
  signifying formal collaborative working agreement
  on S1000D and the ADL/SCORM initiative.
• Australia Industry and Government form S1000D
  Working Organization (this organization and
  structure reflects the structure the US has in
  place)
• 2005
• Formal MOU signing amongst ATA, AIA and AECMA to
  develop the civil aviation needs to be
  incorporated into the S1000D specification.

7
ASD and AIA Joint Effort
8
Progress to Date

• More than 150 US Change Proposal Forms (CPFs)
  have been generated, discussed, analysed,
  dissected and some rejected
• 1000 CPFs have been accepted and included
• The Spec has become a tri-service spec to include
  Land, Sea, Air, Ground based equipment,
• The spec has been completely restructured
• Best of US Specs have been incorporated
• Awarded 2003 Honorary Defense Standardization
  Program (DSP) Achievement Award by DoD's
  Standardization Program Office (2004)

9
S1000D The Roadmap 2003
10
S1000D The Roadmap 2005 and onwards
Change 2.1
Change 2.X Etc.
S1000DIssue 2
Change 2.2
Change 2.3

• Cleanup

• Land and Sea Added
• Introduction of US IETM Functionality
• Functionality Matrix
• TYPE II Introduced

• Training Integration (ADL)
• Parts Data Integration

• Linking Capabilities to External Applications
• Logic Engine For Process Data Module
• Configurable/Reusable Graphics

• Commercial Aviation Collaboration

Release of Change 2.1
Release of Change 2.2
Release of Change 2.3/3.0
Release of Issue 2.0
Oct2003
Feb2004
May2005
2006
11
What Has Jointness Brought To S1000D
12
ASD - CPSC Customer Product Support Committee
AIA Product Support Committee
ATA Air Transport Association
TPSMG ChairCo-chair EUCo-chair USCo-chair
ATA SecrChair EPWG Chair CAWG Chair LPWGChair
SPWGGermany indFrance indItaly indUK MoDUSA
DoDATA repr
S1000D User Forum
TPSMG Tech Pubs Spec Maint Group
TPSMG Exec
EPWG Electronic Publications WG
Land Publ WG(LPWG)
Sea Publ WG(SPWG)
Air Publ WG(APWG)
Civil Aviation WG(CAWG)
Chair (and co-chair) appointed by TPSMG Exec
workers appointed by the chair/co-chairs
13
Countries with current S1000D Programs

• Australia
• France
• Germany
• Italy
• Singapore
• South America
• Spain
• Sweden
• United Kingdom
• United States of America

14
Australian Involvement
15
Australian Involvement

• Australia first showed interest in S1000D in
  1999 when the Australian Defense Force (ADF)
  started a dialogue with AECMA.
• In 2001 the Royal Australian Navy (RAN) was
  granted observer status by the S1000D SPWG. This
  meant for the first time a body from within the
  ADF could voice their views and any concerns they
  might have in relation to developments of the
  S1000D specification affecting sea vehicles.

16
continued

• In 2003 the ADF became more involved with S1000D
  commencing talks with both the TPSMG and JLSA. In
  2003, S1000D became adopted as Australian Defense
  Force policy (not formally signed and released
  until 2005).
• In 2004 the first user forum was held at the
  Laverton RAAF Base in Victoria. This was attended
  by defense and industry based organizations.
• From this forum the Australian Specification
  Management Group was Formed.
• Current S1000D Projects include UAV, Air Warfare
  Destroyer, M113 Armoured Vehicle, Tiger and NH90
  Helicopters

17
AU Progress
18
Defence Industry Stakeholder Group
19
Where does this all lead?
20
Network Centric Logistics Solution

• Maximize Readiness
• Minimize Cost of Ownership
• Minimize Logistics Footprints
• Minimize Maintainer Training Requirements

Ensures the Recipient is Supported with the Right
Information, Parts, Supplies, and Training at the
Right Places All the Time
21
Network Maintenance Environmentsof The Future

• Challenges of network environments of the future
• Integration of hundreds of different maintenance
  systems, tools and processes
• Integration into centralized interface without
  sub-optimizing individual maintenance system
• Protection of intellectual property in an open
  environment
• Backward integration with the dominance of legacy
  systems
• Integration of the network maintenance
  environment with the network centric operation
  environment

22
Future Integration of the Information Supply
Chain
23
Overview of SCORM S1000D Integration Efforts

• Jennifer Brooks
• ADL Co-Lab

24
Outline of Presentation

• The problem were trying to solve
• ADL perspective
• S1000D perspective
• Characterizations of the 2 communities
• Training
• Tech Pub
• Status of efforts
• Next Steps

25
Boeing Use Case

• Interoperable Seamless
• Training
• Sequencing
• Remediation
• IETMS

26
Issues

• Viewer
• We want the same viewing experience across
  multiple learning management systems
• Workflow / Process Management
• Update once, access from anywhere
• Get the right material to the right person at the
  right time
• Seamlessly

27
The Flip Side
Cody has an Origami book (Technical Manual) that
has a series of steps to complete there are some
folding patterns that occur rarely and Cody would
need to step out to ask for help (Training).
28
Issues

• Viewer
• We want the same viewing experience across
  multiple learning management systems
• How do I seamlessly step out of an IETM to get
  training in the form of a SCO or aggregation?
• Workflow / Process Management
• Accessing the right content at the right time

29
Different Specs for Different Purposes

• One does not replace the other!
• S1000D is a model for content, so it's
  complimentary to SCORM, which is silenton
  content
• S1000D was developed primarily by the aviation
  industry in Europe to describe detailed
  procedures in Technical Manuals (e.g., how to
  change a part in an engine)

30
Technical Data (S1000D)
Specification S1000D International Specification
for Technical Publicationsutilizing a
Common Source Data Base

TM
31
SCORM and Job Performance Support
Delivery ToolsS1000D ViewersSCORM LMSsOther
(Inmedius) (Syberlogic) (3dSolve) (MORE)
JPTC Repository
Global Hawk USAFFuture Combat System
ArmyF-18 USNF-117 USAFRB-M USCG
S1000D Tech DataIETMsIETPsSimulationsGames
32
US DoD Convergence SCORM S1000D
DoD Personnel and Readiness
DoD Acquisition, Technology Logistics
Emerging Guidance DODI 8000.xx
Guidance DODI 1322.xx
Technical Spec SCORM
Technical Spec S1000D
ADL Registry
Tech Data Registry
Repository Spec CORDRA/Handles
Repository Spec ?
Tim Tate
DoD S1000D-SCORM TESTBED
33
In Summary The Problem Were Trying to Solve

• Tim observed a lot of instructor-led training and
  a lot of it involved a guided path through the
  Technical Manuals
• 9 out of every 10 references in the instructor
  guides referenced the Technical Manual the other
  was to a game or web-based training module
• We need a way to allow Training (SCORM) to
  reference the Technical Manuals and
• We need a way to allow a Technical Manual to
  reference Training materials for remedial
  guidance (e.g., if a worker doesn't know how  to
  perform the step.)

34
The Shared Vision Driving the SCORM-S1000D
Testbed

• A unified model for describing and accessing
  content
• A single, authoritative source for content so you
  can automatically update your Technical Manual
  and your Training, Games, Simulations, etc.
• Simple example a change in the recommended PSI
  in your tires
• Integration of all aspects of training
• e.g., competency records and job skill
  requirements so that a person gets the right
  training before starting a job and the most
  up-to-date technical manuals while performing the
  job (including access to remedial training
  whenever required)
• Automatic notification of updates to procedures

35
Connect the Dots
SCORM
Intelligent Tutoring Systems
Job Skill Requirements
Training
Digital Assets
Simulations / Gaming
Data Management
Performance Support
S1000D
Competencies
36
What is the Problem?

• Right now intersection points are isolated
• i.e., given Boeings case, we cant pull an
  S1000D data module into an advanced distributed
  learning environment seamlessly

37
Considerations / Obstacles

• Different metadata schemas
• Different identifier schemas
• Different philosophies
• S1000D is about identifying a specific piece of
  equipment in a specific context
• SCORM is about removing context from a learning
  object and then giving it context in a course
• Job performance support vs. training

38
In a Nutshell, err Pyramid
Testbed
Intersection Points
SCORM S1000D

• Seamlessly integrate technical publications and
  advanced distributed learning

39
Back to Folding Paper

• Real world example When I was at camp, I was
  trying to get a bunch of kids to do origami I
  didn't know what skills they already had and
  obviously they had a variety of backgrounds some
  of them needed basics in folding and should have
  had a more basic pattern to begin with some were
  more advanced and could go forward furthermore,
  I didnt know what competencies were required for
  the different objects

40
Status of Efforts

• Status of efforts
• In midst of serious analysis of architectural
  issues in both environments
• Seeking to identify integration points
• Supporting (funding) testbed to examine technical
  implications of seamlessly integrating the
  environments
• Seeking to collaborate with the S1000D community
  to better understand their requirements and
  harmonize them with ours
• Tim Tate has established the SCORM-S1000D testbed
  co-funded by OSDPR on the ADL side and DDRE
  (responsible for performance support)
• Tim has signed a MOU with S1000D TPSMG community
  and hes a co-chair on the S1000D USSIG so that
  he can effect change in S1000D

41
Feedback from Community on Requirements / Issues

• Travis Carlton
• The Boeing Company

42
Why Should We integrate ?
Enhance Performance Support
Improved Life Cycle Management
43
Enhance Performance

• Delivery of the right information at the right
  time to the right individual
• Access to Training anytime/anywhere
• Reduce initial training time
• Reduced time on task
• Reduced errors

44
Improved Life Cycle Management

• Reduce Life Cycle Cost
• Reduced Initial Data Development Cost
• Reduce Life Cycle Maintenance Cost
• Improved Configuration Management
• Training and Technical Data from delivered from
  same data source
• Reduced time/cost to update data

45
Issues associate with integration
46
Integration Issues

• Philosophical Issues
• Business Processes and Rules
• Technical Issues
• Data Management
• Data Delivery

47
Philosophical Issues

• Different Purposes
• Training is designed to teach concepts
• Introduce and reinforce concepts
• Provide Feedback and Remediation
• Measure Performance
• Technical Data focused on providing procedural
  information
• All Data must be verified
• Focus on step by step procedural information
• Different Design
• Training
• Multimedia
• Focus on highly interactivity
• Technical Data
• Textual/documentation driven
• CGM wire diagrams with hotspots

48
Business Rules and Processes
Design
Analysis
Develop
Procurement
Implement

• Performance Support Environment impacts all
  phases of the process

49
Procurement Phase

• Business rules (2 levels)
• Data Requirements
• Requirements for Shared Data Environment
• Tools/Interfaces
• Learning Management System
• Learning Content Management System/Content
  Management System
• Maintenance Management System
• Metadata
• Define Schema
• Identify Required/Optional Elements

50
Traditional Analysis Phase
Current Process
Support
Maintenance
Training
System
Task Analysis
Analysis
Detailed
Detailed
Training
Task
Task
Needs
Analysis
Analysis
Analysis

Narrative

Narrative

Narrative

Support

Support

Support
Equipment
Equipment
Equipment

Spares

Illustrated

Personnel

Personal
Parts
Requirements

Training
Breakdown

Graphics

Facilities

Graphics
CBT
Maintenance
IETM
Delivery
Plan Delivery
Delivery
Source Data Shared Manually With Automated Spares
Link
51
Analysis Phase
Integrated Analysis
Support System Analysis
Task Analysis Outline


Narrative Outline

Support Equipment

Spares
Data Management

Personnel

Training

Facilities

Training
Training Needs Analysis


Personnel Requirements

Knowledge/Skill Requirements

Contextual Analysis


Graphics


Metadata

Metadata
Data Management
Integrated Data Flow
52
Design Phase

• Training/Performance Objectives
• Media Analysis
• Performance Support requirements
• Training/Support Taxonomies
• Data Reuse requirements
• Granularity
• Object Identification
• Content Metadata definition
• Design Shared Data Environment

53
Development Phase

• Develop Content
• Assets
• Content Objects
• SCOs
• DMs
• Develop Shared Data Environment
• Content Metadata

Animation
Image
Text
Text
Image
Text
54
Implementation Phase

• Create Package Manifests
• Create Relationship Metadata
• Content Delivery Mechanisms

55
Technical Issues

• Data Management
• Granularity
• Structured vs Unstructured data
• Identification of Data (Metadata)
• Data Delivery
• Need for viewers
• Interface with Learning Management System
• Performance Tracking

56
Next Steps

• Near term requirements and scope
• Functional requirements
• Establish a test plan that addresses requirements
  and scope for the two testbeds
• Australia testbed (i.e., the Demonstrator)
• Boeing Australia and DEST
• HarvestRoad
• ADL testbed
• Formulate recommendations to both the S1000D
  community and ADL community for technical
  integration of the respective environments
• Technical roadmap would result