Ask an S1000D Expert Tour Seattle, WA

Size: px

Start display at page:

Download "Ask an S1000D Expert Tour Seattle, WA"

Elizabeth Lloyd
6 years ago
Views:

1 Ask an S1000D Expert Tour Seattle, WA Lou Iuppa VP Strategic Business Development and SDL S1000D Business Owner Michael Cook S1000D Business Analyst Michael Davis Principal i Business Consultant t

2 Agenda: S1000D Technology Conference 12:00 13:00 Conference Registration, Networking and Lunch 13:00 Introductions, Objectives, Market Trends 13:10 S1000D Overview S1000D The Basics 13:30 Boeing AWACS - Site Case Study 14:00 Brief Break 14:05 S1000D in Action An IETM/IETP Interactive Electronic Technical Manual / Publication ACSDB - Common Source Database 15:00 - Brief Break 15:05 - Roundtable 15:45 - Final Q&A and Wrap Up

3 Objectives of this Conference Explore S1000D Market Trends Understand what you need to know about S1000D Overview of the basics The importance of a CSDB (Common Source Data Base) and the publishing process to S1000D Learn from The Real World Site Case Study: The Boeing Company s U.S. Airborne Warning and Control System (AWACS) program Boeing Representative: Ed Hougardy, Programmer/Analyst, AWACSTechnical Publications and Training S1000D in Action 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 Development SDL, Structured Content Technologies Lou Iuppa is the

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

business within the aerospace, defense and commercial technical publication industries.

4 Introductions Lou Iuppa, VP, Business Development SDL, Structured Content Technologies Lou Iuppa is the VP of Business Development for SDL, Structured Content Technologies. In January 2011, Lou took on the responsibility as SDL s S1000D Business 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 the perspective of vendor, end user, and consultant.

Introductions Mike Cook, S1000D Business Analyst SDL, Structured Content Technologies Mike has a 30 year history within the aerospace and defense community and has been working with real world S1000D

5 Introductions Mike Cook, S1000D Business Analyst SDL, Structured Content Technologies Mike has a 30 year history within the aerospace and 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 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 SDL s S1000D Specification Education Series and created SDL s BREX Builder application.

Introductions Mike Davis, Principal Business Analyst and S1000D Specialist SDL, Structured Content Technologies Mike has 20 years of experience

He s worked with XML since it s inception focused on XML used within document production and data exchange.

6 Introductions Mike Davis, Principal Business Analyst and S1000D Specialist SDL, Structured Content Technologies Mike has 20 years of experience with complex computing environments, specializing in databases and XML. 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 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.

Introductions Ed Hougardy, Programmer/Analyst Airborne Warning and Control System (AWACS) Technical Publications and Training Ed

Ed s efforts also focus on the identification and delivery of data authoring process improvements.

Viewer, and for the Boeing Collaborative Document Reviewer, a state-of-the-art web application used to automate the Interim

7 Introductions Ed Hougardy, Programmer/Analyst Airborne Warning and Control System (AWACS) Technical Publications and Training Ed supports AWACS data transformation strategies that meet the online and print delivery requirements for the program. Ed s efforts also focus on the identification and delivery of data authoring process improvements. Recent projects include data transformation and style development for the AWACS Interactive Electronic Technical Manual (IETM) Viewer, and for the Boeing Collaborative Document Reviewer, a state-of-the-art web application used to automate the Interim Product Review (IPR) process for product document review. Ed s expertise is valued across multiple programs and sites and he is an active participant in the Boeing S1000D Working Group.

SDL Group Recognized Leader in Global Information

revenues Over 2000 employees in 50 offices across 32

financial i stability 1000+ deployments of enterprise

8 SDL Group Recognized Leader in Global Information Management Publicly traded company with $250m+ annual revenues Over 2000 employees in 50 offices across 32 countries Award-winning and profitable with long term financial i stability deployments of enterprise technologies 80% of the global translation supply chain use SDL software

organizations who rely on SDL Technologies

9 SDL Structured t Content t 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, project 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.

10 S1000D Trends Strong desire for Vendor Neutrality Opportunity for Cost Savings Business Significant budgetary pressure to reduce sustainment costs Government Data Acquisition Drivers Strategy: S1000D deliverables more frequently mandated in contracts Technical Drivers Multi-format, multi-device delivery ready Configuration Management Interactive Electronic Technical Manuals (IETM s) Proven interoperability between vendor solutions Market Drivers Very Strong, Active Standards d Community Government Spending is Down! Technical data management services becoming more competitive Tools are readily available to achieve the benefits of S1000D

11 Next Generation Content Delivery Platform LiveContent

12 S1000D Overview Mike Cook, S1000D Business Analyst

13 S1000D Overview Slides S1000D basics History Terminology Important activities Support files Marketplace overview How do you get there? Crossing the road to adoption The Larger context Challenges of adoption Best of Breed S1000D Implementations The myth of the end-to-end solution The best of breed solution The CSDB matters Why publishing matters

14 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) Air Transport Association (ATA) The S1000D specification is available from: An outgrowth of the ATA 100 and ATA ispec 2200 Anyone 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 p support others. It can support any product requiring publications for maintenance, operation, and configuration of parts and supplies.

15 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 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.

16 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, and viewing technologies no single standard supports all these needs 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 standards Interoperability and data exchange is problematic between the services and partners no common method Data re-use is inconsistent or impossible between publications (no prescribed recycle paradigm)

17 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 g using a formal supported format

18 S1000D Terminology Abbreviations DMC Data Module Code PMC Publication Module Code ICN Information Control Number DMRL Data Module Requirements List CSL CSDB Status List DDN Data Dispatch Note SNS Standard Numbering System DC Disassembly Code IC Information Code (aka infocode) CSDB Common Source Data Base BREX DM Business Rules Exchange Data Module LOAP List Of Applicable Publications LOEDM List Of Effective Data Modules IETP Integrated Electronic Technical Publication

19 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 as the framework for an information set. The various core schemas are: Procedural proced.xsd Descriptive - descript.xsd d Process process.xsd Crew crew.xsd Fault Isolation fault.xsd 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 Learning learning.xsd Checklist checklist.xsd Business Rules BREX brex.xsd Publication Module pm.xsd Applicability Cross-reference reference Table - appliccrossreftable.xsd Product Cross-reference Table prdcrossreftable.xsd Conditions Cross-reference Table condcrossreftable.xsd SCORM Content Package scormcontentpackage.xsd Data module file <dmodule> Metadata about the data module s content <identandstatussection> Content procedure, process, how to, etc - all based on the information code and schema of the data module <content>

20 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) Create a Data Module Requirements List (DMRL) (optional) Implement a Content Management System - referred to as a 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 customers

21 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. DMRL file CSDB Empty Data Modules DMRL can produce

22 S1000D Support file Publication Module Publication Module Aircraft Maintenance Manual (AMM) CSDB - Project Data Modules Publication Module System Description Section (SDS) Crew door latch Description of function = DMC-PROD1-A A-042A-A = System Description Section PMC-PROD1-AAAAA

23 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)

24 S1000D Marketplace Overview S1000D adoption is growing much faster than expected in the Military and Civil Aviation industry The U.S. Air Force has standardized all new projects to use S1000D Spec Aerial refueling tanker is a case in point. U.S. Air Force is undergoing S1000D trials to replace and electronically manage publications and Technical Work Orders Mil-STD 3031 U.S. Army has created standardized business rules for new projects to use S1000D Issue Joint Chiefs have also issued a draft memo from the Undersecretary of Defense for Acquisition, i i Technology and Logistics, recommending S1000D as the standard of choice for documentation associated with all new weapon systems

25 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 specification A Data Module Requirements List (DMRL) allows data modules to be defined d 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.

26 S1000D: How Do You Get There? e Crossing the road to adoption

27 S1000D: Challenges of Adoption What is Needed Details Impediments to success Deep knowledge of the specification Defining the business rules so as to manage changes to the authoring environment Technical know-how Technology infrastructure Knowledge of terminology, understanding of S000D concepts and coding rules Learning to write to the data module paradigm New workflow methods to support authoring, review, editing, and publishing cycle Knowing how to work with XML, publishing basics, and IETP experience Experience with a CMS Authoring Tools CSDB Publishing Engine APIs to Integrate with Other systems (LSAR/Parts/Wiring) Learning curve Psychology of change, new methods, identifying what needs to change in an existing environment Human resources, access to existing information on the spec, etc Flexibility, support, programming/macro language capabilities, compliance to spec File/data exchange Subcontractors, OEMs, and Seamless data exchange between partners between organizations Service organizations must all adopt S1000D

28 Best of Breed S1000D Implementation Product Lifecycle Management Technical Content Development Logistics Management Publishing Client Applications Product information Part data PLM digital content CSDB LSAR IETP Each of these applications represent complex processes and specific expertise. No single vendor has the expertise to do all of it well.

29 The Myth of the End-to-End Solution Single Vendor, In Theory One vendor can provide all components of the solution All components are made by the same vendor and will integrate out of the box with each other You get all the functionality you need Single Vendor, In Reality 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 industrialstrength solution Software components are developed and maintained by different business units with different development centers Integration is rarely one-size-fits-all ; so out-of-the-box of the 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 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 vendor, you do not have the flexibility to choose the solutions that best meet your specific needs

30 The Best of Breed Solution Specialization breeds focus and expertise You get to work with top of the line applications in each segment You get to keep the parts of your infrastructure that are already working You can more nimbly 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 operation

31 Authoring is not Content Management Some vendors try to simplify the requirements around S1000D by focusing on authoring tools Authoring is important, but does not address the major requirements associated with S1000D: DMRL creation DMC and ICN creation and management Publication module creation and management Data interchange using a DDN Multi-channel publishing outputs (PDF, IETP) These tasks are performed by the IT department and generally require intensive i interaction ti with the CSDB Find a good XML Editor for authoring and a good CSDB for the management of S1000D content focus on built-in functionality to handle the major requirements listed above

32 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: Ability to work in the S1000D formats you choose Workflow management (editing cycle) 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

33 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 s use your content t S1000D 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, to and text-to-graphic to linking capabilities Customizable skins and styles; open architecture Support for Process Data Modules and links to external applications Revision i highlights hli ht and incremental update functionality Annotations and built-in problem reporting Audit trails and forms capabilities

34 S1000D Best Practices for Deployment Primary Responsibility Months SDL SDL Workshop Implementation ti (out-of-the-box) Workshop System configuration and deployment Style sheets finalized Customer Learn S1000D Adoption, content reuse, and change management Business Rule decisions (document and apply to BREX DM) Client sign off Live Release! IT / Admin Setup and Configure Server Install Configured SDL Server SDL or Consultant S1000D Author Training Content Creation and Conversion IETM Styles

35 AWACS Case Study Ed Hougardy Programmer/Analyst

36 AWACS and S1000D An Overview

37 Who is Ed Hougardy I m a programmer/analyst with The Boeing Company, in the Defense, Space & Security business unit. Specifically, I work for the Airborne Warning and Control System (AWACS) technical publications group in Kent, WA: Currently, sixty six 707 AWACS aircraft, designated the E-3, are in service worldwide within the United States, NATO, Saudi Arabia, France, and United Kingdom Japan uses four 767 AWACS My primary role involves the management of and transformation of technical maintenance data.

38 AWACS and S1000D the Prequel

39 Background In the mid 1990s NATO planned a major upgrade to the NATO Mission Systems NAPMA decided to look into possibility for Interactive Electronic Technical Manuals (IETM) No knowledge available No concept available Working group established in 1995 Research feasibility for IETM for NATO AWACS major Modernization Programme (NATO Midterm) Define basic concept

40 Leaping Ahead ~ Pilot Project Data Conversion and Viewer development contracts awarded to ESG GmbH, Germany in 1996 AECMA (ASD) 1000D version 1.6 Data in SGML Close cooperation between contractor and NATO working group Lessons learned

41 Moving Forward Advantages found Quick and easy access to data, easy to use Distribution Functionalities Only limited user training required New Technical Maintenance Data Moved to 1000D version 1.7 TOC 1000d version 1.9 Tools developed for QA Check compliance with Data Interchange Specification Identifies location of errors Must pass prior to delivery

42 U.S AWACS and S1000D

43 U.S. AWACS Upgrade ~ The Big Picture The largest upgrade in the history of the U.S. AWACS fleet is underway: With new mission computing hardware and software, upgraded radar equipment, navigation and communications systems. These systems are designed to increase the AWACS capability, reliability and lower its life cycle costs Upgrades will be installed on the entire U.S. fleet of 32 AWACS by 2016 New Opportunities for the Technical Publications Group: Creating data (information) right the first time Improved In-Process Reviews (IPRs) Giving the customer what they want Transition paper to electronic media

44 Boeing U.S. AWACS History Pre-upgrade state of the AWACS publications: Develop system/equipment specific maintenance and operation manuals using United States Defense Standards for Technical Orders (MIL-SPEC/MIL-STD) Manuals created/maintained with various programs, such as BroadVision Interleaf, Adobe FrameMaker, and SGML data authored with Arbortext Editor and formatted with SDL s XPP Several MIL-SPECS are employed such as, MIL-STD for General Maintenance Manuals; MIL-PRF-7700G for Basic Flight Manuals; MIL- PRF-5096F for Work Cards

45 Moving Forward New state of the AWACS publications: Develop system/equipment specific maintenance and operation data products using S1000D S1000D is an international specification for technical publications, utilizing a common source database (CSDB). 1000s of XML data modules authored with Arbortext Editor and maintained in SDL s Contenta Cost savings associated with reuse of information Subject matter expert authoring Web 2.0 Based IPR support tool Supports review of S1000D data Content Management System employed Adds revision/history control to data Adds meta-data for information control systems

46 How We Got There Established Boeing / Customer (Air Force) S1000D Business Rules Team Business Rules can make or break a project Business Rules define how the project is going to create, manage, and deliver technical content. The S1000D specification (Issue 4.0.1) has nearly 700 paragraphs that contain Business Rules Decisions information. The S1000D specification (Issue 4.0.1) has identified ten categories for all major business rules decisions: General business rules Data creation business rules Product definition business rules Data exchange business rules Maintenance philosophy & concepts of operation Data integrity and management Security business rules Legacy data conversion & management Business process business rules Data output business rules

47 How We Got There continued Business Rules Team Team was made up of representatives from several disciplines / groups The customer Authoring staff Illustration staff Information Technology Staff S1000D Subject Matter Expert Programmers Arbortext Developer Stylesheet t / FOSI Developer Schema / DTD Subject Matter Expert Team Lead (Managers / Focal) Team Scribe Document the decisions 3rd party vendors / subcontractors when appropriate

48 How We Got There continued Team decisions Determine which version of S1000D to be used Identify content to be managed Content (scope) of the Data Modules Line Replacement Module (LRM) / Line Replaceable Unit (LRU) Logistics Databases Data Module output Electronic Printed Both Functionality Matrix from the S1000D specification Types of Data Modules Media types (output)

49 How We Got There continued Team Empowerment Have invested one hour week meeting time for four years Established that Business Rules are a living document revisiting is OK Accepted that change is inevitable (paradigm shift)

50 Business Rules Summary Started the project with Issue 2.0 of the specification, migrated to Issue 3.0 and now brought the data forward to Issue At the start of the project developed with our customer a set of fbusiness Rules. These rules primary focused on: Authoring guidelines for content creators Element and Attribute usage Information Code usage As the data migrated to newer versions of the specification: Business Rules were updated to take advantage of new elements and functionality and element/attribute name changes Core Business Rules focus did not change

51 Challenges Faced by The Technical Publications Group Challenges caused by this changing situation: New standard for authoring Authoring permissions and workflow control Complex workflow Reviewing data within Boeing and our military customer Potential for complex delivery requirements

52 Authoring Workflow Strategies to meet authoring challenges of the new specification Provide training Develop custom application plug-ins to assist authors with repetitive tasks Use Business Rules Provide QA and Business Rules checking application CMS / CSDB Authoring Revision Change management

53 The In-Process Review Problem Extremely complex workflow between Boeing and the Air Force: Produce, print, and ship copies of data products to the various customers required to perform review Hand mark review copies for correction/change Transfer markups to Air Force form 158 to formally record comments Gather all reviewers interested t to review data products Find repetitive comments Perform a line by line review of documents and all comments made Compile all comments and incorporate into data product

54 Boeing Collaborative Document Reviewer The In-Process Review solution BCDR: Web based / Server Hosted Tool Documents are uploaded to web server (XHTML, XML, PDF) Documents Support S1000D and IETM look and feel Just-In-Time Processing Workflow support Band Width Efficient Graphics don t load until needed XHTML page does not require reload when adding/updating comments Collaborative Asynchronous, group reviewing Sticky-note like comments Real time - Server updates every 15 seconds Comments embedded within document at original location Everyone comments, everyone sees everyone else s comments

55 Success The Boeing AWACS Technical Publications Group: Has delivered to the U.S. Air Force S1000D data which has passed Verification Key to success: Key to success: Close cooperation between all parties Government, Contractors, and Vendors is must for a successful result

56 Future S1000D 4.1 Consider updates to the specification Joint USAF and NAMPA project Common approach data reuse Training data is planned to be included Flight Manual data More legacy paper based Technical Orders to be converted to S1000D

57 Conclusion When implemented correctly, a S1000D project has the potential of providing a cost effective, standards based, interactive solution for technical data presentation. Provides a generic concept for quality assurance of publications in a life-cycle perspective Provides standardized transfer format for exchange of information between any organization Promotes content reuse and repurposing

58 S1000D in Action Mike Davis, Principal Business Analyst and S1000D Specialist

59 What we re going to demonstrate Manage and Automate Author Publish Deliver Electronically CCM/CSDB Contenta S1000D ORACLE Publishing Output XML Professional Publisher LiveContent Publishing Server Type 2 Interactive Electronic Technical Manuals Live Content Check in/out XML DB Editorial Workflow Arbortext Editor Data Module(s) Type 1 Paper/PDF Technical Manuals XSL-FO

60 Roundtable Moderator: Lou Iuppa Panelists: Ed Hougardy, Mike Cook, Mike Davis, and YOU!

61 Webinars, Workshops and Wrap Up Lou Iuppa, VP Business Development

62 Where can I go from here? SDL Your Source for S1000D Information SDL S1000D Resources Page (handout) SDL s Educational S1000D Recorded Webinars Series/Archive SDL S1000D Specification i Education Series Ask an S1000D Expert Tour Upcoming Events Webinars, Conferences, Tours June 1, 2011 Should S1000D be required by the Department of Defense? July, 2011 A best practices approach to S1000D data conversion. On-Site S1000D Workshop AskAnS1000DExpert@sdl.com

63 SDL S1000D Online Webinar Recordings Register and View ALL the Recorded Events! 5 Part Series Part 1 S1000D Alphabet Soup: Introduction to S1000D Concepts Part 2 S1000D Content Workflow Part 3 S1000D Applicability Part 4 - S1000D Interactive Electronic Technical Publications (IETP) Part 5 - S1000D and Multimedia

64 SDL S1000D Specification Education Series Introduction to S1000D S1000D An In-Depth Exploration Authoring and Editing for S1000D Change Management (Editing/QA Cycle/Workflow) Front Matter An Exploration of the Possibilities Applicability An In-Depth Exploration of its Inner Workings Common Source Data Base (CSDB) What It Is, What It Can Do, What You Need to Know Project Startup for S1000D

SDL s Ask an S1000D Expert Tour San Diego, CA June 2011 Naval Postgraduate School Should S1000D be required by the Department of Defense. S1000D as an acquisition strategy.

65 SDL s Ask an S1000D Expert Tour San Diego, CA June 2011 Naval Postgraduate School Should S1000D be required by the Department of Defense. S1000D as an acquisition strategy. Fort Worth, TX September 2011 US Navy, PMS401 Acoustic Submarine Program A TeamSub S1000D Strategy Warner Robins, GA October 2011 ADL The case for integrating Tech Data and Training Washington, DC - November 2011 Lockheed Martin S1000D, a tactical advantage. A best practices approach to integrating tech data and tactical systems. / / / /

66 Industry Conferences, Groups Industry Conferences June6to8- S1000D User Forum 2011 in Montreal AIA Techpubs Conference, Clearwater, FL each May Specs and User Groups Download the S1000D Spec for a little light reading! aspx S1000DPC User's Group LinkedIn S1000D Users Group

S1000D Workshop Objectives Gain a high level

Experience the project planning process Create

an interactive electronic technical manual

Prerequisites Team has XML authoring skills g

67 S1000D Workshop Objectives Gain a high level understanding 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 skills g Executive sponsor identified, and available for opening and close of workshop

68 Wrap Up Evaluation Form Literature Survival Tool Buddies

69 Contact Us!

Ask an S1000D Expert Tour Smithsonian National Air & Space Museum, Chantilly, VA

Ask an S1000D Expert Tour Smithsonian National Air & Space Museum, Chantilly, VA Lou Iuppa VP Strategic Business Development and SDL S1000D Business Owner Michael Cook S1000D Business Analyst Michael Davis