Ask an S1000D Expert Tour Dallas, TX

Transcription

1 Ask an S1000D Expert Tour Dallas, TX 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: Ask An S1000D Expert Tour 12:00 12:30 Conference Registration, Networking and Lunch 12:30 13:30 Introductions and S1000D Specification Overview 13:30 14:30 Keynote Presentation. Jim Ensminger, PEO Submarine, Submarine Acoustics Systems ILS Manager, Transitioning i a Large Modernization Program to an S1000D Environment 14:30 14:45 Break, Snack, Network 14:45 15:30 S1000D in Action 15:30 16:30 Interactive Q&A/Roundtable

3 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 S1000D Explore a Real-World Business Case and Implementation Strategy for S1000D S1000D in Action SDL LiveContent and SDL Contenta S1000D Roundtable: Ask, Share, Learn Ensure you walk away with the answers to your questions

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.

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.

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.

7 Introductions Jim Ensminger, PEO Subs, PMS401LM Submarine Acoustics Systems ILS Manager PMS401 - Develops and implements the Warfare System Modernization Plan that defines future upgrades, systems standards and interface definitions for development of submarine warfare systems. Works with other Navy organizations and provides direction to coordinate development tasking at Navy Laboratories. Jim Ensminger has over 30 years of experience with Acquisition Logistics and In-service Support Policy and Program management. Jim holds an MBA in Business Management and is currently the Submarine Acoustics Logistics Manager for PMS 401, Submarine Acoustics ILS, U.S. Navy.

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

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 NAVSEA Viewer 1.0

13 Saab Aerotech Gripen 39 IETP

14 S1000D Overview Mike Cook, S1000D Business Analyst

15 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

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

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

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

19 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

20 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

21 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>

22 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

23 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

24 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

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

26 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

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

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

29 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

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

31 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

32 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 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 operation

33 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

34 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

35 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

36 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

37 Jim Ensminger, Transitioning a Large Modernization Program To an S1000D Environment Jim Ensminger, PMS401LM Submarine Acoustics Systems ILS Manager

38 Transitioning a Large Modernization Program To an S1000D Environment 20 September 2011 Jim Ensminger paul.ensminger@navy.mil Distribution A: Approved for Public Release; Distribution is Unlimited. The views expressed herein are solely those of the author and not those of the U.S. Government, its employees, trustees, or assigns.

39 Program Description US Navy Submarine Acoustics program is a large Commercial off the Shelf (COTS) based modernization program: Acoustic-Rapid COTS Insertion (A-RCI) System is nomenclatured as AN/BQQ-10(V) Sonar Set Uses COTS hardware components and custom software to provide new technology and functionality to the submarine fleet Common logistics processes and products are the key elements of the program sustainment success reduced cost and development time by following the premise of develop once, use many times Integrated Product Team (IPT) environment utilizes multidisciplinary teams to optimize the design, system engineering, production, and sustainment processes. Prime Contractor is responsible for developing, delivering, and life-cycle sustainment for the AN/BQQ-10(V) Sonar hardware, software and logistic products. Utilizes Prime contractor, subcontractors, and 3 rd party suppliers, as data developers Distribution A: Approved for Public Release; Distribution is Unlimited. The views expressed herein are solely those of the author and not those of the U.S. Government, its employees, trustees, or assigns.

40 S1000D Initiated December Department of the Navy policy on the use of XML. Mandates use of XML for acquisition, development, and maintenance of all Navy technical data Attempt to achieve enterprise interoperability between DoN, DoD, and industry October DoN Policy on Digital Product/Technical Data. Establishes XML as the markup language of choice for technical publications Requires digital data be life cycle maintained in XML for all new acquisitions February NAVSEA guidance on the use of S1000D specification for technical manual development and management. S1000D is a widely adopted commercial and international specification for the production of XML technical publications. Chosen by consortium of Navy and contractors as the XML schema of choice for the Submarine Acoustics IETMs Is a DoN approved product, supported by NAVSEA IT infrastructure (SNIPP) Distribution A: Approved for Public Release; Distribution is Unlimited. The views expressed herein are solely those of the author and not those of the U.S. Government, its employees, trustees, or assigns.

41 S1000D Decision Develop all data in S1000D format to maintain the make once, use many times program premise. Development / integration of SCORM conformant training products. Use a phased approach to obtain data out of HTML formatted (proprietary) toolset to an S1000D XML format to meet DoN Policy. PHASE ANALYSIS TOOLS DEVELOPMENT PROTOTYPE IMPLEMENTATION TASK Identify requirements and other unique project specific considerations to develop a strategy Evaluate and select S1000D CSDB and development toolset Demonstrate and evaluate prototype capability, cost considerations, and implementation recommendations Convert and export data from existing authoring system database as valid S1000D Data Modules (DMs) and Publication Modules (PMs), load all A RCI data into CSDB, and continue to author, store, manage, and deliver S1000D IETM content using the selected COTS CSDB & Authoring Tools Distribution A: Approved for Public Release; Distribution is Unlimited. The views expressed herein are solely those of the author and not those of the U.S. Government, its employees, trustees, or assigns.

42 Considerations and Benefits Programmatic factors drove the move to S1000D. Rapidly changing and compressed development schedules to meet a Submarine Modernization strategy Desire to continue improving IETM and training products Projected fiscal constraints t on program budget Two distinct major projects initially fielded: AN/BQQ-10 A-RCI Sonar IETM Submarine Warfare Federated d Tactical System (SWFTS) System of Systems (SoS)Technology IETM Coordinated projects intended to support and benefit NAVSEA S1000D initiative. iti Distribution A: Approved for Public Release; Distribution is Unlimited. The views expressed herein are solely those of the author and not those of the U.S. Government, its employees, trustees, or assigns.

43 Process Impacts S1000D required process changes to: Development Integrating data from multiple providers Review andvalidation/verification Deployment and distribution Initial IETM deliveries IETM updates and revisions Lifecycle Management of Data Changes implemented: Customer support tools at the Prime contractor facility [Submarine Integrated Logistics Capability (SILC)] Feedback (comment) gathering g tools IETM installation procedures and scripts Graphical and multimedia asset management control Impacts on how collaborative development is accomplished in new tools Distribution A: Approved for Public Release; Distribution is Unlimited. The views expressed herein are solely those of the author and not those of the U.S. Government, its employees, trustees, or assigns.

44 Product Impacts Identify program-specific requirements Editors, CSDB (Contenta ), Viewers (LiveContent ) Defined requirements in S1000D IPT and Task Teams Migration, conversion from legacy tools Developed S1000D export for legacy data from Prime contractor HighTIDE database Converted existing Flash-based viewers for Physical/Parts, Troubleshooting Flowcharts, and Learn/Practice enhancement to support S1000D-based content Supplemental applications and tools needed to fill gaps in software and help development productivity Integration with existing support tools Developed export of initial Illustrated Parts Diagram from SILC Integrated LiveContent with existing IETM comment application tool SILC Integrating with Tactical System and other ILS products Developed Java script that communicates with LiveContent, Tactical System, and other ILS products Distribution A: Approved for Public Release; Distribution is Unlimited. The views expressed herein are solely those of the author and not those of the U.S. Government, its employees, trustees, or assigns.

45 People Impacts Learning curve for IETM developers and users. Migrating authors knowledge and skills Develop out of comfort zone Thinking out of the box Revised processes Lessons learned Distribution A: Approved for Public Release; Distribution is Unlimited. The views expressed herein are solely those of the author and not those of the U.S. Government, its employees, trustees, or assigns.

46 Benefits of S1000D/XML Non-Proprietary Neutral data (management and ddelivery) Modular approach ideal for web delivery Maximizes availability of tools, resources, and potential vendor support Maximizes interoperability Tailored specification more open than other schemas More projects being done to facilitate interoperability with other standards (such as SCORM) Ease of integrating with training data Best schema for medium to large systems Commercially supported Authoring Storage Display/delivery Large Community of Practice and growing (wider adoption within NAVSEA) Distribution A: Approved for Public Release; Distribution is Unlimited. The views expressed herein are solely those of the author and not those of the U.S. Government, its employees, trustees, or assigns.

47 Lessons Learned Leverage work done by others Incremental steps needed for a large project migrating from a legacy development and delivery prospective Collaborative decision making IPT and Task Teams to work specific issues Harmonization with Higher level Business Rules (BR) and processes The Specification (inconsistencies within the specification/schemas) Customers and teammates (different interpretations of the specifications or BRs) Established legacy processes and expectations of end users/support activities Tailoring Tagging concerns Identification of schemes, Data Module (DM) coding schemes Project configurable attributes and optional elements Defining rules and guidelines to drive consistency DM templates DM authoring guide BR development never ends identify any Communities of Practice rules Use any existing rules Seek to collaborate with others to adopt common rules as much as possible Distribution A: Approved for Public Release; Distribution is Unlimited. The views expressed herein are solely those of the author and not those of the U.S. Government, its employees, trustees, or assigns.

48 Contact Info Submarine Acoustics Systems ILS Manager Jim Ensminger (PMS401LM) Washington Navy Yard, DC (202) Distribution A: Approved for Public Release; Distribution is Unlimited. The views expressed herein are solely those of the author and not those of the U.S. Government, its employees, trustees, or assigns.

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

50 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

51 Roundtable Moderator: Lou Iuppa Panelists: Mike Cook, Mike Davis, Curtis Blais, and YOU!

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

53 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 Webinar Series: S1000D Applicability Boot Camp Part 2: The PCT Data Module October 11 Part 3: The CCT Data Module November 9 On-Site S1000D Workshop AskAnS1000DExpert@sdl.com

54 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

55 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

56 Industry Conferences, Groups Industry Conferences S1000D User Forum 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

57 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

58 Wrap Up Evaluation Form Literature Survival Tool Buddies

59 Contact Us!