AskAnS1000DExpert Tour - San Diego CA - June 2011 - Draft 1downloadcenter.sdl.com/tridion/S1000D/AskAnS1000DExpertTour_Sa… · document production and data exchange. Mike is a ppg

Ask an S1000D Expert™ TourSan Diego, CA

Lou IuppaVP Strategic Business Development and SDL S1000D Business Owner

Michael CookS1000D Business Analyst

Michael DavisP i i l B i C lt tPrincipal Business Consultant

Agenda: Ask An S1000D Expert™ Tour

12:00 – 12:30 – Conference Registration, Networking and LunchNetworking and Lunch

12:30 – 13:30 – Introductions and S1000D Specification OverviewSpecification Overview

13:30 – 14:30 – Keynote Presentation.Curtis Blais, Naval Post Graduate SchoolCurtis Blais, Naval Post Graduate School“Should S1000D be Required by the Department of Defense?”

14:30 – 14:45 – Break, Snack, Network14:45 – 15:30 – S1000D in Action15:30 – 16:30 – Interactive Q&A/Roundtable

Objectives of this Conference

Overview of the S1000D specification Understanding the basics of the specification Understanding the importance of a CSDB (Common Source Data Base)

and the publishing process to S1000DLearn from Naval Post Graduate School Research Report Findings

S1000D in Action SDL LiveContent and SDL Contenta S1000D SDL LiveContent and SDL Contenta S1000D

Roundtable: Ask, Share, Learn Ensure you walk away with the answers to your questions

Introductions

Lou Iuppa, VP Business DevelopmentVP, Business DevelopmentSDL, Structured Content Technologies

Lou Iuppa is the VP of Business Development for pp pSDL, Structured Content Technologies.

In January 2011, Lou took on the responsibility as SDL’s S1000D Business OwnerBusiness Owner.

He manages strategic business relationships with the US Navy and Northrop Grumman as well as new business within the aerospace, defense and commercial technical publication industries.

Lou has over 20 years of experience associated with publishing and content management technologies within a variety of industries from content management technologies within a variety of industries from the perspective of vendor, end user, and consultant.

Introductions

Mike Cook, S1000D Business AnalystS1000D Business AnalystSDL, Structured Content Technologies

Mike has a 30 year history within the aerospace y y pand defense community and has been working with real world S1000D project needs for the past 6 years.

Mike provided S1000D Information Architecture services for the Mike provided S1000D Information Architecture services for the Boeing 787 Dreamliner documentation system.

His experience includes roles within Boeing Flight Test, test labs, and as an Instructor of Systems Analysis, Structured Analysis, Computer Aided Software Engineering, and Project Planning and Controls.

Mike developed SDL’s S1000D Specification Education Series and Mike developed SDLs S1000D Specification Education Series and created SDL’s BREX Builder application.

Introductions

Mike Davis, Principal Business Analyst and Principal Business Analyst and S1000D SpecialistSDL, Structured Content Technologies

Mike has 20 years of experience with complex computing environments, specializing in databases and XML.

H ’ k d ith XML i it’ i ti f d XML d ithi He’s worked with XML since it’s inception focused on XML used within document production and data exchange.

Mike is a programmer, familiar with most SGML/XML data standards p g , /and has over 15 years serving the aerospace and defense industry.

Mike also plays an important role at SDL as a customer advocate by providing input and guidance to SDL’s S1000D product strategy providing input and guidance to SDLs S1000D product strategy.

Introductions

Curtis Blais, Research Associate ProfessorResearch Associate ProfessorMOVES InstituteNaval Post Graduate School

Mr. Blais has 37 years of experience in modeling and simulation instruction, management, design, development, and application in the domains of military analysis and training.

Mr. Blais has a BS and MS in Mathematics from the University of Notre Dame and has been at the Naval Postgraduate School for the past 11 years, with prior experience in government and industry. p y , p p g y

From late 2009 to early 2010, Mr. Blais worked with colleagues Dr. Mike McCauley and Mr. John Falby to examine the question, “Should S1000D be Required by the Department of Defense?”Should S1000D be Required by the Department of Defense?

SDL Group

Recognized Leader in Global Information ManagementPublicly traded company with $250m+ annual revenues$Over 2000 employees in 50 offices across 32 countriesAward-winning and profitable

ith l t fi i l t bilitwith long term financial stability 1000+ deployments of enterprise technologies80% of the global translation80% of the global translation supply chain use SDL software

SDL St t d C t t T h l iSDL Structured Content Technologies SDL is a leader in the design, creation, delivery and support of technical data systems in the aerospace and

defense community SDL offers award winning component content management, CSDB, PS and PDF Publishing and

IETM/IETP generation and delivery technologies as well as professional services, including system design, g y g p g y gproject management, implementation planning and execution, XML data and workflow modeling, custom programming and system integration.

A sampling of companies and defense organizations who rely on SDL Technologies are US Navy, US Air Force, Northrop Grumman, Raytheon, Boeing, Gulfstream, Pratt & Whitney, and many more.

S1000D Trends

• Strong desire for Vendor Neutrality

• Opportunity for Cost Savings • Significant budgetary pressure to reduce sustainment costs

Business reduce sustainment costs

• Government Data Acquisition Strategy: S1000D deliverables more frequently mandated in contracts

Drivers

• Multi-format, multi-device delivery ready

• Configuration Management• Interactive Electronic Technical Manuals (IETM’s)

• Proven interoperability between d l ti

Technical Drivers vendor solutionsDrivers

V St A ti St d d• Very Strong, Active Standards Community

• Government Spending is Down!

• Technical data management services becoming more competitive

• Tools are readily available to

Market Drivers

achieve the benefits of S1000D

Next Generation Content Delivery Platform

Li CLiveContent

S1000D OverviewS1000D Overview

Mike Cook, S1000D Business Analyst

S1000D Overview Slides

S1000D basics History Terminology Important activities Support files Marketplace overview

How do you get there?• Crossing the road to adoption• Crossing the road to adoption

The Larger context Challenges of adoption Best of Breed S1000D Implementations Best of Breed S1000D Implementations The myth of the end-to-end solution The best of breed solution Th CSDB tt The CSDB matters Why publishing matters

S1000D History

The S1000D specification is used to produce technical publications. It is co-owned by the following groups:

European Association of Aerospace Industries (ASD) Aerospace Industries Association (AIA)

Ai T t A i ti (ATA) Air Transport Association (ATA)

The S1000D specification is available from: www.S1000D.org

An outgrowth of the ATA 100 and ATA iSpec 2200

Anyone with experience in ATA 100 or ATA iSpec 2200 has someAnyone with experience in ATA 100 or ATA iSpec 2200 has some degree of familiarity with S1000D

S1000D supports air, land, or sea systems – and can be adapted to pp , , y psupport others. It can support any product requiring publications for maintenance, operation, and configuration of parts and supplies.

S1000D History

The specification is managed by working groups who represent various industries or users. Prominent working groups are “U.S. Specification Management Group” (USSMG) and the Civil Aviation Working Group (CAWG). These groups have contributed to developing and maintaining the S1000D specification.

To assist the USSMG in defining and submitting U.S. interests, the “U.S. Specification Implementation Group” (USSIG) was established as a sub group of the USSMG to recommend detailed technicalas a sub group of the USSMG to recommend detailed technical solutions, perform feasibility reviews, submit change proposals, and advise USSMG on future areas of interest.

Aerospace Industries Association (AIA) manages the USSMG and the USSIG.

History - Why was S1000D created?

European Issues (ASD)• No standard existed to support more than the aviation industry• ATA 100 and ATA iSpec 2200 are considered to be a good start,

but do not incorporate many capabilities needed for other product or industry types

• Partners and customers have different requirements languages• Partners and customers have different requirements, languages, and viewing technologies – no single standard supports all these needs

US DoD Issues (AIA)US DoD Issues (AIA)• Too many different specifications across the services• Millions spent every year on publication maintenance or

conversion to support updates to each of the various standardsconversion to support updates to each of the various standards• Interoperability and data exchange is problematic between the

services and partners – no common method• Data re-use is inconsistent or impossible between publications (noData re use is inconsistent or impossible between publications (no

prescribed recycle paradigm)

History - Why was S1000D created?

Civil Platform Support Issues (ATA)• Aircraft manufacturers and airline customers may not be using the

same documentation standards. When aircraft manufacturers provide maintenance data to customers it must be transformed into whatever specification the customer is using.

• Aircraft manufacturers and customers want to move from Document Centric Publications to Information Centric Publications

• Data re-use is becoming more important as new technology influences how new products are maintained and how the information to support these activities is presented to technicians

• Aircraft manufacturers and customers want to exchange data gusing a formal supported format

S1000D Terminology – Abbreviations

DMC – Data Module CodePMC – Publication Module CodeICN – Information Control NumberDMRL – Data Module Requirements ListCSL – CSDB Status ListCSL – CSDB Status ListDDN – Data Dispatch NoteSNS – Standard Numbering System DC – Disassembly CodeIC – Information Code (aka infocode)CSDB Common Source Data BaseCSDB – Common Source Data Base BREX DM – Business Rules Exchange Data ModuleLOAP – List Of Applicable PublicationsLOEDM – List Of Effective Data ModulesIETP – Integrated Electronic Technical Publication

S1000D Terminology – Data Modules

The smallest self contained information unit within a technical publication. The equivalent of a “topic” or the most granular piece of information about a task or descriptive “How to” of a system.Data modules are created using “schemas” Schemas are used asData modules are created using schemas . Schemas are used as the framework for an “information set”. The various core schemas are:

• Procedural – proced.xsdD i ti d i t d

Data module file<dmodule>• Descriptive - descript.xsd

• Process – process.xsd• Crew – crew.xsd• Fault Isolation – fault.xsd• Illustrated Parts Data – ipd.xsd

Metadata about the data module’s content<identAndStatusSection>

Content – procedure, process, Illustrated Parts Data ipd.xsd• Schedule – schedul.xsd (yes the “e” is missing on purpose)• Technical Information Repository – techrep.xsd• Wiring Data - wrngdata.xsd• Container – container.xsd

p , p ,how to, etc - all based on the information code and schema of the data module<content>

• Learning – learning.xsd• Checklist – checklist.xsd• Business Rules – BREX – brex.xsd• Publication Module – pm.xsd• Applicability Cross reference Table appliccrossreftable xsd• Applicability Cross-reference Table - appliccrossreftable.xsd• Product Cross-reference Table – prdcrossreftable.xsd• Conditions Cross-reference Table – condcrossreftable.xsd• SCORM Content Package – scormcontentpackage.xsd

S1000D Important activities

Adopting S1000D usually consists of the following pieces• Make Business Rule decisions - identifying how various features

of the specification will be used for the given project• Create or flesh out a Standard Numbering System (SNS)• Add information code variants (if needed)Add information code variants (if needed)• Create a Data Module Requirements List (DMRL) (optional)• Implement a Content Management System - referred to as a

Common Source Data Base (CSDB)Common Source Data Base (CSDB)• Author content - using XML, graphics, and multimedia• Assemble Publication Modules• Publish – digital distribution or paper

• Publishing for digital distribution may include selecting an Interactive Electronic Technical Publication (IETP) viewer, creation of a website, or hosting an FTP site for distribution of raw XML data modules directly to customerssite for distribution of raw XML data modules directly to customers

S1000D Support file - DMRL

Data Module Requirements List Used to define and create the data modules for the Product (optional) Data modules are usually defined by the SMEs and authors and can be inserted

into a DMRL. The DMRL can be used to create skeleton XML files.

CSDB Empty Data ModulesDMRL file

DMRL can produce

S1000D Support file – Publication Module

CSDB - Project D t M d l

Publication Module Aircraft Maintenance

Manual (AMM) Data ModulesManual (AMM)

Publication Module Publication Module System Description

Section (SDS)

Crew door latch – Description of functionDMC-PROD1-A-52-11-05-00A-042A-A

=

System Description SectionPMC-PROD1-AAAAA-04001-01

=

S1000D Support file – Data Dispatch Note

S1000D provides a method to transfer data modules using a data interchange method – also known as a transfer package The transfer package must have a Data Dispatch Note (DDN) and at least one data module. Other S1000D files can also be included, for example: Illustrations and multimedia files Publication Modules a CSDB Status List (CSL)( )

CSDB files (DMC, ICN, etc) Transfer Package

Export CSDB content (files)

S1000D Marketplace Overview

S1000D adoption is growing much faster than expected in the Military and Civil Aviation industryThe U.S. Air Force has standardized all new projects to use S1000D Spec 4.0.1. Aerial refueling tanker is a case in point.po t U.S. Air Force is undergoing S1000D trials to replace 38784 and

electronically manage publications and Technical Work Orders

Mil-STD 3031 – U S Army has created standardizedMil-STD 3031 – U.S. Army has created standardized business rules for new projects to use S1000D Issue 4.0.1Joint Chiefs have also issued a draft memo from the U d f D f f A i i i T h l dUndersecretary of Defense for Acquisition, Technology and Logistics, recommending S1000D as the standard of choice for documentation associated with all new weapon systems

The Larger Context

S1000D enables collaboration of content, interchange of files, and content reuse Collaboration:

• Contracts are generally written to indicate the use of a specific issue of the specificationA D t M d l R i t Li t (DMRL) ll d t d l t b d fi d• A Data Module Requirements List (DMRL) allows data modules to be defined before authoring occurs. This is part of the business rules decision making process and allows multiple manufacturers to participate in the definition process

• Data Dispatch Note (DDN) files are used as part of the file transfer process to help create transfer packages (also known as revision packages). Content migrated from the CSDB for delivery to partner companies and for delivery to digital only recipients uses a simple method which is easily implemented.

• If S1000D is used by multiple organizations, the data created in each CSDB can be imported and exported between partners with relative ease

Content Reuse:• Content is authored at the data module level and is referenced by publication

modules. Reusing the data module in another publication is as easy as creating a reference to the data module within the publication module.

S1000D: How Do You Get There?S 000 o o ou Get e e

Crossing the road to adoption

S1000D: Challenges of Adoption

What is Needed Details Impediments to successDeep knowledge of the • Knowledge of terminology,

understanding of S000DLearning curve

specification understanding of S000D concepts and coding rules

Defining the business rules so as to manage

• Learning to write to the datamodule paradigm

• New workflow methods to

Psychology of change, new methods, identifying

changes to the authoring environment

New workflow methods to support authoring, review, editing, and publishing cycle

what needs to change in an existing environment

Technical know-how • Knowing how to work with XML,publishing basics and IETP

Human resources, access t i ti i f tipublishing basics, and IETP

experience• Experience with a CMS

to existing information on the spec, etc

Technology infrastructure • Authoring Tools• CSDB

Flexibility, support, programming/macro• Publishing Engine

• APIs to Integrate with Other systems (LSAR/Parts/Wiring)

programming/macrolanguage capabilities, compliance to spec

File/data exchange • Subcontractors, OEMs, and Seamless data exchangeFile/data exchange between partners

, ,Service organizations must all adopt S1000D

Seamless data exchange between organizations

Best of Breed S1000D Implementation

PublishingProduct Lifecycle Management

Technical Content Development

Logistics Management

P d t

Client Applications

P t d tProduct information

PLM digital content

Part data

CSDBIETP

LSAR

Each of these applications representpp pcomplex processes and specific

expertise. No single vendor has the expertise to do all of it well.

The Myth of the End-to-End Solution

Single Vendor, In Theory Single Vendor, In Reality

• One vendor can provide all components • Each component is complex in its own right• One vendor can provide all components of the solution

Each component is complex in its own right• No single vendor can do all parts equally well• You will feel pressure to buy components you don’t need• Components created to fill a perceived product gap are

designed to sell a suite of products rather than to meet customer production requirements with an industrial-strength solution

• All components are made by the same vendor and will integrate “out of the box” with each other

• Software components are developed and maintained by different business units with different development centersIntegration is rarely “one size fits all”; so “out of the box”with each other • Integration is rarely “one-size-fits-all”; so “out-of-the-box” integration is not likely to meet your needs and will require customization anyway

• In most cases, integration is not a difficult or time-consuming effort; it doesn’t justify forcing a single-vendor solution

Th “ i l d ” th hid d k i• You get all the functionality you need • The “single vendor” theory hides gaps and weaknesses in products; vendors focus on their best components (e.g., Arbortext Editor)

• Demonstrations of the worst components are avoided (e.g., publishing to paper and/or IETP)

• Some point solutions are better than others; with a single• Some point solutions are better than others; with a single vendor, you do not have the flexibility to choose the solutions that best meet your specific needs

The Best of Breed Solution

Specialization breeds focus and expertiseYou get to work with top of the line applications in each g p ppsegmentYou get to keep the parts of your infrastructure that are already workingalready workingYou can more easily adopt newer and better technology and standards“All your eggs are not in one basket”; you can swap out software components without disrupting your entire operationoperation

Authoring is not Content Management

Some vendors try to simplify the requirements around S1000D by focusing on authoring toolsAuthoring is important, but does not address the major requirements associated with S1000D: DMRL creation DMRL creation DMC and ICN creation and management Publication module creation and management Data interchange using a DDN Data interchange using a DDN Multi-channel publishing outputs (PDF, IETP)

These tasks are performed by the IT department and ll i i t i i t ti ith th CSDBgenerally require intensive interaction with the CSDB

Find a good XML Editor for authoring and a good CSDB for the management of S1000D content—focus on built-in gfunctionality to handle the major requirements listed above

Why the CSDB Matters

The CSDB is the focal point of all your data A CSDB is the primary storage location for all content Without a central location for organizing and tracking information,

important information can be lost or overlooked

What you need in a good CSDB:y g Ability to work in the S1000D formats you choose Workflow management (editing cycle) Intuitive method for importing or exporting content using a DDN Intuitive method for importing or exporting content using a DDN

(automated DDN creation, DM export and import) Capability to manage DMCs and ICNs, not just the codes, but also any

associated nomenclature Capability to create and manage Publication Modules as “virtual

documents” so links to XML objects are not entered manually Capability to publishing to multiple output formats (aka Multi-channel

publishing) from the same content IETP “preview functionality” for authors

Why Publishing Matters

The publications your company creates can be the difference between life and death for users of your products! Publishing your content determines how internal and external customers use your contente te a custo e s use you co te tS1000D IETPs should provide state-of-the-art functionality: Run-time applicability filtering Support for CGM, TIFF, SVG, Flash, 3D images, wire tracing, animations,

simulations, virtual task training, digital photographs, and more Locator graphics (graphical navigation); Graphic-to-graphic, graphic-to-

text text to text and text to graphic linking capabilitiestext, text-to-text, and text-to-graphic linking capabilities Customizable “skins” and styles; open architecture Support for Process Data Modules and links to external applications R i i hi hli ht d i t l d t f ti lit Revision highlights and incremental update functionality Annotations and built-in problem reporting Audit trails and forms capabilities

S1000D Best Practices for Deployment

1 2 3 4Primary Responsibility

SDL W k hSDL W k h I l t tiI l t ti

Months

S t fi ti S t fi ti SDL Workshop(out-of-the-box)SDL Workshop

(out-of-the-box)Implementation

WorkshopImplementation

WorkshopSDL

Adoption, content reuse,Adoption, content reuse, Client Client

System configuration and deployment

System configuration and deployment

L S1000DL S1000D

Style sheetsfinalized

Style sheetsfinalized

Adoption, content reuse,and change managementAdoption, content reuse,and change management

CustomerBusiness Rule decisions (document and apply to BREX DM)Business Rule decisions (document and apply to BREX DM)

Setup and Setup and

Client sign offClient

sign offLearn S1000DLearn S1000D

LiveRelease!LiveRelease!

Install Configured SDL Install Configured SDL IT / Admin Setup and Configure Server

Setup and Configure Server

SDL or Consultant S1000D S1000D

Content Creation and ConversionContent Creation and Conversion

Install Configured SDL Server

Install Configured SDL Server

IETM StylesIETM StylesS1000D

Author TrainingS1000D

Author Training

Curtis Blais, [email protected]

Prof Michael McCauley, [email protected]

Report Briefing

John Falby, [email protected]

Report Briefing

Curtis L. Blais, Research AssociateMOVES Institute, Naval Postgraduate SchoolMOVES Institute, Naval Postgraduate School

Should S1000D Be a DoDShould S1000D Be a DoD Requirement?

Curtis Blais, Michael McCauley and John Falbyy yMOVES Institute

Naval Postgraduate SchoolMonterey CaliforniaMonterey, California

28 June 2011

YYes.

Questions?Q

However…O “Fi di ”Our “Findings:”

For S1000D to be required DoD needs to beFor S1000D to be required, DoD needs to be prepared to:• Manage/Govern itManage/Govern it• Promote it• Support it• Enforce it

This must not be a blind mandate, but supported from the top and founded on the business case!!!

Management/Governance

Establish a management organization for di ti / i ti ll D Dcoordination/communication across all DoD

organizationsDevelop guidelines for useDevelop guidelines for use

• New acquisitions• Legacy systems

B i i h l i f h d dBe active in the evolution of the standard• Joint Service IETM Technology Working Group• S1000D Defense Working Group (S1000D-DWG)g p ( )• Ensure defense requirements are brought forward to the

S1000D Steering Committee and Council

Promotion

Develop a transition/adoption planFacilitate adoption through

• Training & educationGuidance• Guidance

• Business rules• Tools

Begin developing an enterprise solution, across Services, Organizations and Acquisition, O ti L i ti M i t T i iOperations, Logistics, Maintenance, Training Communities

Support Activities

Develop mechanisms to upgrade materials d l d d li S1000D i tdeveloped under earlier S1000D issues to current issue

Be ti e in e g o p nd fo mBe active in user groups and forumsPublish issues/concerns and DoD-supported

changes to S1000Dchanges to S1000DMonetary support to reach uniformity

Enforcement

Legacy systems: Do not convert to S1000D unless a business case is made to do so

New acquisitions: Require S1000D unless a business case can be made for not using S1000D

R i S1000D f t f ll i t h dRequire S1000D format for all interchange and sharing of technical publications

Ens e compatibilit ac oss soft a e toolsEnsure compatibility across software tools

Basis for the Findings

Background ResearchBackground ResearchStructured InterviewsWeb-Based QuestionnaireWeb Based QuestionnaireAnalysis and Synthesis

Background ResearchPrior Study: An Analysis of S1000D and Its Adoption by the Department of

Defense, LMI Government Consulting, November 2008• Response to AIA White Paper recommending DoD adoptionResponse to AIA White Paper recommending DoD adoption• “Many of the challenges associated with adopting the more complex aspects

of S1000D are directly related to the lack of definition about the enterprise…”

• …”we believe the applicability of S1000D to information management within DoD must be considered within the framework of the goals and objectives of the broader enterprise.”“ d h ( ) h h l• “We recommend that OUSD(AT&L), in cooperation with the military services, determine a structure for developing a comprehensive approach to product data.”

• Limitations of the LMI study: In principal, we agree• Limitations of the LMI study: • Short term study• Input only from Navy organizations

In principal, we agree that an Enterprise-wide solution is needed, but perhaps differ on how b t t ti l t tibest to stimulate action toward that solution.

The NPS Study:Structured InterviewsStructured Interviews

20 interviews / 25 interviewees0 te e s / 5 te e ees• All services represented• Approximately 1 hour per interview• Court reporter generated transcripts (570 pages)

Questions/discussions primarily addressed Q / p yperceived benefits, challenges, whether S1000D should be required, and responsibilities of DoD if it is requiredresponsibilities of DoD if it is required

Structured Interviews: S1000D BenefitsS1000D Benefits

• Data reuse… it should reduce the lifecycle of that yinformation because you’re only creating it once and using it many [times]

• The capability of reusing the data creating data once• The capability of reusing the data, creating data once and using it multiple times for various products.

• The fact that my systems change so rapidly, I have to come out with new versions of IETMs on a very rapid, repeatable basis. S1000D enables me to reuse the portions of the IETMs that are applicable tothe portions of the IETMs that are applicable to earlier versions without having to redevelop them.


• …the neutral format has allowed content to be used in different formats The neutral format allows us toin different formats. The neutral format allows us to use it in different viewers.

• …it can be used on multiple different software t lti l d t b d lti l l tfsystems, multiple databases and multiple platforms,

without having to alter or modify the actual information itself, so there’s no locking to a particular

f i l fsoftware view or platform.• Economy of scale; just have one S1000D tool – the

“Golden Spike” of technical information. The tool that pwe have provides the means to display multiple versions of S1000D data modules at the same time.


Integrate the production of technical manuals and training courses… with integration, there will be a reduction in the cost of producing future tech manuals and then training courses… the integration would reduce the possible incidence of disparate i f i i i h i l l d i iinformation given in technical manuals and training courses

…integration may speed up the production of technical manuals and training courses, and therefore that may reduce the

ibilit i i i i t thpossibility -- or give insurance, some insurance against the possibility of lags in the fielding of new systems and equipment upgrades, and the delivery of up-to-date technical manuals and training courses to the fleet the benefits in terms of reductiontraining courses to the fleet. …the benefits in terms of reduction in future costs far outweigh the investment and implementation costs.


• …once I’ve developed it in S1000D, if I have an engineering change or any other modernization or update it’s a muchchange or any other modernization or update, it s a much smaller piece of the equation [than] to actually do a complete IETM update.

• the ability to reuse data and not have to recreate data on a• …the ability to reuse data and not have to recreate data, on a very small scale, has saved me between 15 and 25 percent of my overall development cost. I see that that should go up significantly once all of my programs are doing S1000D.significantly once all of my programs are doing S1000D.

• …You may not save any money initially, but over the lifecycle• I can see where the standardization would be beneficial for all

of DoD because as we go forward we know our budgets areof DoD because, as we go forward, we know our budgets are going to get tighter and tighter, and if we’re out there using different software and different procedures to do the same job, it’s only going to cost DoD more money overall.it s only going to cost DoD more money overall.


So S1000D not only permits content reuse for training deliverables, it borrows content itself from engineering databases that are further back in the product lifecycle process. So it's an integral part of a wider set of specifications that, when you bring them ll h f d h h f ld f hiall together, are focused on the threefold support of this system

from its inception and design and manufacture through to its in-service and ultimately demilitarization phases. …the use of these complementary standards is now becoming what’sthese complementary standards is now becoming what s considered best practice in the U.S.

Structured Interviews:S1000D Risks/DownsidesS1000D Risks/Downsides

• …definitely a ramp-up cost to support the conversion y p p ppor the transition over to an S1000D implementation. Learning curve, lack of project business rules. There’s probably a lack of data module coding strategy… but p y g gythe big one is the learning curve and the business process piece.

• There is definitely a learning curve with S1000D It’sThere is definitely a learning curve with S1000D. It s a very big document, it’s a process, it’s a standard of handling tech data that’s different than what programs are used to doingprograms are used to doing.


• …like all standards, you need to make an investment up f t t t th t t d d it d ifront to move to that standard…it does require an investment in personnel, training, and infrastructure, because it’s a very advance information process and it’s y pnot until later on down the line you start to realize those benefits. … like all content reuse standards, the payoff comes downstreamcomes downstream.

• …there needs to be infrastructure in place to be successful, and that is IT infrastructure, software tools, and personnel and training… that’s probably the biggest challenge facing an organization who is looking at adopting S1000D.adopting S1000D.


• Policy has not caught up with use…. the y g precommendation that it be looked at for the capability of reducing lifecycle costs.

ith t OSD DOD li h• …without OSD or DOD policy, programs can choose not to implement the specification. There’s noting saying that they should look at it.

• What we in the industry have run into is that when we get to a certain level of leadership within the services the lack of understanding or knowledge ofservices, the lack of understanding or knowledge of the specification and what it can do has hindered that policy decision.


• The specification has been changing at a very rapid rate p g g y pin the last few years…the scope is expanding too fast to keep upM lti l i th UK i j t i t it h t 2 3• Multiple versions – the UK is just going to switch up to 2.3

• Two problems: One is the maturity of the tool sets. [Two] Not all vendors use it, support it.Not all vendors use it, support it.

• We've selected a tool set, we've developed business rules, we have style sheets or schemas that the program is

i Wh t t h I ti i t h iusing. Where you start -- or where I anticipate having some difficulties or possibly some issues is when we start interfacing with other programs or other communities.g p g

Structured Interviews:Requiring Use of S1000DRequiring Use of S1000D

• Enthusiastic “yes.” y• I think it would make sense for … new content. Anything

above ACAT Level II should be using S1000D. • [re enterprise-wide solution first] We don’t want to wait.

This is something that should occur simultaneously, so that the enterprise-wide approach can evolve using bestthat the enterprise wide approach can evolve using best practices from those programs with a head start, while launching the S1000D requirement to be phased in using logical stepslogical steps.


• …such a requirement would make sense for all new qsystems…by mandating or requiring that with the new systems, what the DoD is doing is they’re setting themselves up for success in the futurethemselves up for success in the future.

• …why not start today and why not start with S1000D• I think that after a while you’re going to see more andI think that after a while you re going to see more and

more programs using it, and at that time, I think it would be very sensible to mandate something like this.


• … before I would recommend it becoming a requirement, g q ,I would again make sure it does everything that we think it is going to do.

t thi i t b bl t Y ld d t it f• …at this point, probably not… You could mandate it for new system. I think that would be more of a logical step as far as mandating anything. Mandating for legacy systems is going to be a big price tag that they’re not going to be able to pay for.

• The mandate is harsh Guidance yes you should look• The mandate is harsh. Guidance, yes, you should look into it and see if it makes sense.

Structured Interviews:What Must DoD DoWhat Must DoD Do

What we’ve struggled with, the industry has struggled gg , y ggwith, is that there are committees that both have industry representation and leadership as well as slots for Department of Defense and OSD leadership p pwithin those organizations, working groups, etc. for the S1000 work. And those DoD or OSD positions have basically been held temporarily by individuals, y p y y ,but no formal appointment has been assigned for those services or OSD. …we have no concurrence from the government in either one of the positions, g p ,whether they represent the entire DoD, OSD, or they represent their service.


• …mandating’s okay if you’ve got your …ducks in a row… g y y g yif you have a set of government business rules.

• ..if you had an OSD set of S1000 business rules, it really works At the top you would have the OSD set ofworks… At the top you would have the OSD set of business rules, and then that gets handed down to the services. And the services may have some unique

f h l f h d f hrequirements for their platforms, so they modify those business rules, and then they pass it down to the program. And the program may have a modification that p g p g ythey may be tightening the specification requirements you have, not loosening them up.


• If you’re doing something new, go ahead and use S1000D. If you are a legacy program that has a legacy system in place, consider a g y p g g y y p ,migration path, but there’s no reason for you to stop the presses and switch courses midstream

• But the business case tells me if I’ve got 5 years left on a weapons platform that I’m going to migrate all my data there’s no return onplatform that I’m going to migrate all my data, there’s no return on investment. That’s why the business case should be performed, to show if there is a return on investment or not.

• everything that we do whether it be in OSD or in industry should• …everything that we do, whether it be in OSD or in industry, should be backed up by a solid business case… I think there is a pretty solid business case to use S1000D for new programs, and for those programs going through midlife update or modernization. …make th t d i i b i b i th th d t it ththat decision on a business case basis, rather than mandate it. … the problem with a mandate is that if a mandate exists, then people follow it blindly, and it might not necessarily be the most sensible or cost effective decision to simply blindly follow a mandate.cost effective decision to simply blindly follow a mandate.

Business Case

Difficult to obtain actual data on the business case for or against use of S1000Dor against use of S1000D• Some industry users provided anecdotal evidence of 40-80%

savingsDifficult to identify all programs that are using S1000D and• Difficult to identify all programs that are using S1000D and to determine the business case basis for their decision?

• What is the cost of non-uniformity / proliferation of inconsistency across DoD?inconsistency across DoD?

• In Europe, Germany adopted one issue, UK another – barrier to sharing (unless the content is transformed)

Evolution of the standard can be influenced by DoDEvolution of the standard can be influenced by DoD needs• Army successfully introduced significant changes (Issue 4.0)

Cost Benefit Analysis• Former “Cost Estimator of the Navy” Dan Nussbaum

working at NPS• Sees the lack of CBA is a surprising analytical gap• CBA compares time-phased, economically-adjusted costs

and benefits of alternatives for a defined objectiveand benefits of alternatives for a defined objective• What is the problem that needs to be addressed or resolved?• What is the range of alternatives that could address this problem?• What are the costs, benefits, and risks associated with each

alternative?• Based on the above, what is the recommended course of action?,

CBA for S1000D Requirement• Develop a Work Breakdown Structure to provide the

framework for detailed cost estimating and, later, cost control

• Define the Basis of Estimate, the cost estimating methodologies and underlying datasets from which themethodologies and underlying datasets from which the S1000D cost estimates are developed

• Delineate the benefits and benefits structure: the qualitative and quantitative results expected in return for costs incurred for a chosen alternative

• Perform analysis to provide the link between cost and• Perform analysis to provide the link between cost and benefit data and the decision to be made

• Provide recommendation for decision

Web-Based Questionnaire

Developed after completion of structured interviewsp pQuestions based on the structured interview as well as

from insights obtained from intervieweesWeb link to the questionnaire was distributed to:

• S1000D User Group• All intervieweesAll interviewees• Both of the above were encouraged to distribute it to

colleagues knowledgeable in S1000D

Web-Based Questionnaire Results

Navy/USMCAir ForceArmyCoast GuardOther

Note: We did not collect data from 7 respondents who indicated their knowledge of S1000D was “weak”

Benefits from Using S1000D

Efficiencies from Reuse of Data: 83%

Links between Logistics/Technical Data and Training: 75%75%

Other Benefits: 71 respondents suggested one or more additional benefitsadditional benefits• Most commonly mentioned was standardization across

systems and military services• Potential cost savings also was mentioned frequently

Should S1000D be Required?

DoD Should Require S1000D for: Agree or q f gStrongly Agree

ALL DoD systems? 40.8%A o systems? 40.8%

New Acquisitions but not legacy? 64.2%

Large (ACAT I/II) but not small Acquisitions?

51.7%q

DoD Policy

In my opinion, DoD should: Agree or Strongly AgreeStrongly Agree

Allow Program Managers to decide whether to require S1000D

42.2%

Allow each Service to establish policy on whether to require S1000D

42.1%

Promote and encourage the use of S1000D but NOT require it

46.3%

Require S1000D but allow an “opt out” if the business case is not supported for specific program or system

76.3%

Risks or Downsides

Please rate your agreement with the following items: Agree or Strongly Agreeg y g

Software tools for implementing S1000D can create i ibili i

60.1%

incompatibilities

S1000D is changing rapidly; let’s wait until it becomes more stable

28.4%

The DoD should avoid using a Standard that is controlled by an International body

20.5%

DoD has not sufficiently investigated the adoption of the entire “S‐series” of Standards

38.8%

DoD/OSD ActivitiesSome people feel that DoD should participate more vigorously in activities related to the management of

t h i l d t Pl i di t t ith th

Agree or Strongly Agree

technical data. Please indicate your agreement with the following potential DoD/ OSD activities

Promote an enterprise‐wide solution to managing 83.8%p g gtechnical data

Advertise and promote the use of S1000D 81.8%

Participate actively in S1000D international policy 89.1%Participate actively in S1000D international policy boards

89.1%

Provide funding for training and transition to S1000D usage

86.6%

S1000D usage

Promote the consistency and compatibility of S1000D Business Rules (BREX) across services

89.2%

Limitations of Our Study

We did not have contact with many people y p popposed to S1000D

We did not conduct a cost/benefit analysisWe have insufficient familiarity with the range

of US technical publication standards available

How an S1000D Requirement Can FailCan Fail

Weak management/governance by DoDWeak management/governance by DoD• Programs opt out of providing materials in S1000D

for interchange format• Inadequate interaction with DoD organizational users

and failure to strongly represent their interests

Lack of resources for management, governance, promotion and coordination

What has been done since theWhat has been done since the report came out?

As far as we know, ,results have been briefed at various levels, but no specific actions have been taken.but o spec c act o s a e bee ta e

What have you seen or heard??What have you seen or heard??

Questions?Points of Contact:

C ti Bl i lbl i @ dCurtis Blais, [email protected]

Prof Michael McCauley memccaul@nps eduProf Michael McCauley, [email protected]

John Falby falby@nps eduJohn Falby, [email protected]

Report is available at: http://edocs.nps.edu/npspubs/scholarly/TR/2010/NPS-MV-10-002.pdf

S1000D in ActionS1000D in Action

Mike Davis, Principal Business Analyst and S1000D Specialist

What we’re going to demonstrate

Deliver Electronically

PublishManage and Automate

Author

Publishing Output

Type 2 Interactive Electronic Technical Manuals

LiveContent P bli hi

CCM/CSDB

LiveContent

Publishing Server

XML Professional

Publisher

Contenta S1000D

ORACLE

Editorial W kfl

Check in/outXML DB

ArbortextWorkflow

Type 1 Paper/PDF Technical Manuals

Data Module(s)

XSL-FO

Arbortext Editor

RoundtableRoundtable

Moderator: Lou Iuppa

Panelists: Mike Cook, Mike Davis, Curtis Blais, and YOU!

Webinars, Workshops and Wrap UpWrap Up

Lou Iuppa, VP Business Development

Where can I go from here?

SDL – “Your Source for S1000D Information” SDL S1000D Resources Page (handout) SDL S1000D Resources Page (handout)

• http://www.sdl.com/S1000DResources SDL’s Educational S1000D Recorded Webinars Series/Archive

SDL S1000D S ifi i Ed i S i SDL S1000D Specification Education Series Ask an S1000D Expert™ Tour Upcoming Events – Webinars, Conferences, Tours p g

• http://www.sdl.com/en/xml/events/• July, 2011 – “A best practices approach to S1000D data conversion.”

On-Site S1000D Workshop On Site S1000D Workshop

[email protected]

SDL S1000D Online Webinar Recordings

5 Part SeriesPart 1 – S1000D Alphabet Soup: Introduction to S1000D Concepts

Part 2 S1000D Content WorkflowPart 2 – S1000D Content Workflow

Part 3 – S1000D Applicability

Part 4 - S1000D Interactive Electronic Register and View ALL the Recorded

Technical Publications (IETP)

Part 5 - S1000D and Multimedia

ALL the Recorded Events!

http://www.sdl.com/en/xml/resources/resources-by-topic/topic-s1000d.asp

SDL S1000D Specification Education Series

Introduction to S1000D S1000D – An In-Depth Explorationp pAuthoring and Editing for S1000DChange Management (Editing/QA Cycle/Workflow)Front Matter – An Exploration of the PossibilitiesApplicability – An In-Depth Exploration of its Inner WorkingsWorkingsCommon Source Data Base (CSDB) – What It Is, What It Can Do, What You Need to KnowProject Startup for S1000D

SDL’s Ask an S1000D Expert™ Tour

Dallas, TX – September 2011 US Navy, PMS401 – Acoustic Submarine Program

• “A TeamSub S1000D Strategy”

Warner Robins, GA – October 2011 TBD/Tentative: ADL – The case for integrating Tech Data and Training TBD/Tentative: ADL The case for integrating Tech Data and Training

Washington, DC - November 2011 Lockheed Martin – “S1000D, a tactical advantage.”

A b t ti h t i t ti t h d t d t ti l t• A best practices approach to integrating tech data and tactical systems.

http://www.sdl.com/en/xml/events/

Industry Conferences, Groups

Industry Conferences S1000D User Forum S1000D User Forum

• http://www.ataebiz.org/forum

AIA Techpubs Conference, Clearwater, FL – each May

S d U GSpecs and User Groups Download the S1000D Spec – for a little light reading!

• http://public s1000d org/Downloads/Pages/S1000DDownloads aspxhttp://public.s1000d.org/Downloads/Pages/S1000DDownloads.aspx

S1000DPC™ User's Group • http://www.s1000dpc.com/

LinkedIn “S1000D Users” Group LinkedIn – S1000D Users Group

S1000D Workshop

Objectives Gain a high level

understanding of the S1000Dunderstanding of the S1000D specification

Experience the project planning process

Create S1000D content Manage content in a CSDB Publish an interactive

electronic technical manual (IETM)

Lay foundation for business case

Prerequisites Team has XML authoring skillsg Executive sponsor identified,

and available for opening and close of workshop

Wrap Up

Evaluation FormLiteratureLiteratureSurvival ToolBuddiesBuddies

Contact Us!

[email protected]

Documents

AskAnS1000DExpert Tour - San Diego CA - June 2011 - Draft 1downloadcenter.sdl.com/tridion/S1000D/AskAnS1000DExpertTour_Sa… · document production and data exchange. Mike is a ppg