The data module code for the given XML would be:
DMC-S1000DLIGHTING-AAA-D00-00-00-00AA-056A-A_007-00_EN-US.xml
The XML filename in which this data appears would be:
DMC-S1000DLIGHTING-AAA-D00-00-00-00AA-056A-A_007-00_EN-US.xml
Presented at DocTrain East 2007 by Joe Gollner, Stilo International -- This workshop will introduce participants to S1000D, a rapidly evolving standard that has gained growing level of adoption as a shared approach to addressing the wide range of requirements associated with planning, creating, managing, publishing and exchanging documentation for complex equipment systems. The workshop will provide guidelines for assessing the applicability of S1000D and an implementation framework for managing S1000D deployments. The following topics will receive specific attention:
* An overview of S1000D, its purpose and history
* A review of the S1000D schema framework
* A closer look at specific models
* The underlying identification and management schemes
* Recent changes and future directions
* Implementation examples
* Criteria for determining if S1000D is right for you
* Key considerations to keep in mind when implementing S1000D
* Comparing S1000D with other standards (e.g., DITA)
This document provides an overview and introduction to the information objects stored in a Common Source Database (CSDB) according to the S1000D specification. It describes the three major types of information objects as data modules, graphical objects, and publication modules. Data modules include different types like crew/operator, descriptive, fault isolation, etc. each with their own SGML document type definitions (DTDs). Other information objects include publication modules, comment modules, data dispatch notes, and data module lists, which have XML DTDs. Graphical objects like illustrations are also stored in the CSDB.
This document discusses S1000D data modules, which are reusable blocks of information that can be shared and reused across technical publications. It describes the components of a data module, including the metadata ID status section and content section. It provides examples of different types of data modules, such as those for fault isolation, maintenance planning, parts information, and wiring data. The document is presented by Absolute Data Group, a provider of S1000D and technical documentation products and services.
This whitepaper from CDG provides a high level overview of the background and benefits of the S1000D publications standard. This standard has been widely used in Europe for many years, and is now gaining momentum in the US as well.
The creation and delivery of illustrations is a significant component of an S1000D project. There are several factors that require consideration when creating and maintaining illustrations…
ADG Webinar Series - Introduction to ASD S1000D provides you with an introduction to the ASD S1000D Specification. To view other informative S1000D presentations visit http://www.absolutedata.com/free-resources/webinars
Presented at DocTrain East 2007 by Joe Gollner, Stilo International -- This workshop will introduce participants to S1000D, a rapidly evolving standard that has gained growing level of adoption as a shared approach to addressing the wide range of requirements associated with planning, creating, managing, publishing and exchanging documentation for complex equipment systems. The workshop will provide guidelines for assessing the applicability of S1000D and an implementation framework for managing S1000D deployments. The following topics will receive specific attention:
* An overview of S1000D, its purpose and history
* A review of the S1000D schema framework
* A closer look at specific models
* The underlying identification and management schemes
* Recent changes and future directions
* Implementation examples
* Criteria for determining if S1000D is right for you
* Key considerations to keep in mind when implementing S1000D
* Comparing S1000D with other standards (e.g., DITA)
This document provides an overview and introduction to the information objects stored in a Common Source Database (CSDB) according to the S1000D specification. It describes the three major types of information objects as data modules, graphical objects, and publication modules. Data modules include different types like crew/operator, descriptive, fault isolation, etc. each with their own SGML document type definitions (DTDs). Other information objects include publication modules, comment modules, data dispatch notes, and data module lists, which have XML DTDs. Graphical objects like illustrations are also stored in the CSDB.
This document discusses S1000D data modules, which are reusable blocks of information that can be shared and reused across technical publications. It describes the components of a data module, including the metadata ID status section and content section. It provides examples of different types of data modules, such as those for fault isolation, maintenance planning, parts information, and wiring data. The document is presented by Absolute Data Group, a provider of S1000D and technical documentation products and services.
This whitepaper from CDG provides a high level overview of the background and benefits of the S1000D publications standard. This standard has been widely used in Europe for many years, and is now gaining momentum in the US as well.
The creation and delivery of illustrations is a significant component of an S1000D project. There are several factors that require consideration when creating and maintaining illustrations…
ADG Webinar Series - Introduction to ASD S1000D provides you with an introduction to the ASD S1000D Specification. To view other informative S1000D presentations visit http://www.absolutedata.com/free-resources/webinars
Blisks are single engine components that combine a rotor disk and blades into one piece, either through casting, machining, or welding. Blisks replace separate disks and blades in turbomachinery. They provide advantages such as eliminating the need to attach blades to disks, decreasing the number of components, reducing drag, and increasing compression efficiency. Additionally, removing the dovetail attachment of traditional blades eliminates a common source for cracks to form.
This document is a technical manual providing repair and maintenance instructions for Deere Power Systems Group diesel engines models 3179, 4239, 6359, 4276, and 6414. It covers specifications, tools required, disassembly and assembly sequences, and procedures for servicing various engine components like the cylinder head, valves, rocker arms, push rods, cylinder block, and more. Safety precautions are emphasized throughout and mechanics are instructed to clean components, check tolerances, replace seals, and adjust clearances as specified to properly service these engines.
The document outlines Novell's documentation process for iFolder. It includes:
1. Deliverables such as admin guides, user guides, help documents, and readme files.
2. A documentation development life cycle with phases for requirements, planning, design, implementation, validation, release, and post-release.
3. Roles and responsibilities for the documentation, development, and test teams in each phase.
1997 Porsche Boxster 986 Service Repair Manualjksmmemd
This is the Highly Detailed factory service repair manual for the1997 PORSCHE BOXSTER 986, this Service Manual has detailed illustrations as well as step by step instructions,It is 100 percents complete and intact. they are specifically written for the do-it-yourself-er as well as the experienced mechanic.1997 PORSCHE BOXSTER 986 Service Repair Workshop Manual provides step-by-step instructions based on the complete dis-assembly of the machine. It is this level of detail, along with hundreds of photos and illustrations, that guide the reader through each service and repair procedure. Complete download comes in pdf format which can work under all PC based windows operating system and Mac also, All pages are printable. Using this repair manual is an inexpensive way to keep your vehicle working properly.
Service Repair Manual Covers:
986 Group 0a General
986 Group 1 Engine To 13
986 Group 1 Engine From 15
986 Group 2 Fuel-Exhaust
986 Group 3 Transmission-Automatic
986 Group 3 Transmission-Manual
986 Group 4 Running Gear
986 Group 5 Body
986 Group 6 Body Exterior
986 Group 7 Body Interior
986 Group 8-9 AC-Electrics
986 Group 9 Circuit Diagrams From 00
986 Group 9 Circuit Diagrams To 99
986 Group 0a Diagnosis To 45
986 Group 0a Diagnosis From 69
986 owners manual
File Format: PDF
Compatible: All Versions of Windows & Mac
Language: English
Requirements: Adobe PDF Reader
NO waiting, Buy from responsible seller and get INSTANT DOWNLOAD, Without wasting your hard-owned money on uncertainty or surprise! All pages are is great to have1997 PORSCHE BOXSTER 986 Service Repair Workshop Manual.
Looking for some other Service Repair Manual,please check:
https://www.aservicemanualpdf.com/
Thanks for visiting!
8
ATA Spec 100 provides industry-wide standards for aircraft maintenance documentation, including systems numbering and guidelines for technical manual content and format. It was originally released in 1999 but has since been combined with other specifications into a consolidated standard called ATA iSpec 2200, which provides guidelines for electronic aircraft information exchange. ATA Spec 100 defined a widely used numbering scheme for aircraft parts and systems and is used by airlines for maintenance.
This document provides a summary of revisions made to an aircraft characteristics manual for the Airbus A320 and A320NEO. Key changes include adding new illustrations and dimensions for the NEO version, revising existing illustrations and tables, and updating part numbers and effectivity. Over 60 figures and various sections throughout were revised to update information and improve layouts and clarity.
This document provides information on a water heater model HYDRONIC 10, including its technical description, installation instructions, and operating instructions. The water heater has options for 12V or 24V systems and uses diesel fuel. It connects to the vehicle's cooling water circuit, electrical system, and fuel system. Proper installation and bleeding of the cooling system is required. Safety instructions warn that exhaust contains toxic substances and the heater should not be operated in enclosed spaces or when refueling.
O documento fornece informações técnicas sobre eixos cardan agrícolas produzidos pela AEMCO. É apresentada a classificação dos cardans de acordo com sua capacidade de torque e potência, além de detalhes sobre os componentes, tipos, aplicações e manutenção dos eixos cardan.
Large scale topological optimisation: aircraft engine pylon caseAltair
1) The document discusses using topology optimization to design an improved engine pylon concept for an aircraft. It aims to reduce mass, part count, and assembly time compared to the current design.
2) Topology optimization was performed on the engine pylon and aft pylon fairing using Altair OptiStruct to minimize compliance. This provided optimized structural designs with up to 200kg mass savings per plane.
3) Preliminary analysis shows the optimized design could reduce the part count from over 650 parts to just 14 parts, and assembly time from over 2600 fixes to around 350 fixes.
IRJET - Helmet Violation Detection using Deep LearningIRJET Journal
This document describes a proposed system to detect motorcycle riders without helmets using deep learning techniques and report violations. The system uses support vector machines (SVM) for vehicle classification, convolutional neural networks (CNN) and SVM for helmet detection, and optical character recognition (OCR) for license plate recognition. Motorcycles are classified, helmet use is identified, and license plate numbers of riders without helmets are captured and SMS fines are sent. The goal is to reduce accidents by increasing helmet compliance through automated detection and reporting of violations.
Composite materials are increasingly being used in the aerospace industry. They provide benefits like reduced weight, high strength to weight ratio, corrosion resistance, and fatigue resistance compared to traditional metals. Common composite materials used include carbon fiber reinforced polymers (CFRP) and glass fiber reinforced polymers (GFRP). These are used in aircraft structures like wings, fuselage, empennage and engine components. While composites provide advantages, there are also challenges to address like delamination, damage tolerance, and high manufacturing costs. Analysis of composite wing structures helps optimize design for strength and stiffness.
This document provides a chart that lists common pipe tap sizes along with the corresponding drill bit sizes needed to tap each size of pipe. The chart includes both decimal inch and metric tap sizes ranging from 1/16 inch to 1-1/2 inches and 0.8mm to 36mm. For each tap size, the matching drill size is provided to ensure proper threading of the pipe.
The document provides an overview of aircraft structures and their key components. It discusses the fuselage, wings, empennage, landing gear, and powerplants. For each component, it describes the basic design and functions. It also covers important aircraft structural concepts like stressed skin construction, monocoque vs semi-monocoque design, and choices of lightweight metal materials. Overall the document serves as a high-level introduction to aircraft structures and the major structural components of airplanes.
1) O documento fornece instruções sobre a instalação e manutenção corretas de rolamentos para evitar acidentes e aumentar a vida útil.
2) A lubrificação e manutenção adequadas são essenciais para o bom funcionamento dos rolamentos.
3) A não observância das instruções pode causar falhas no equipamento e riscos de acidentes.
O documento lista códigos e descrições de itens de rolamentos Eaton, incluindo rolamentos de esferas, rolamentos de agulhas, rolamentos de roletes cilíndricos e conicos, conjuntos de capas e cones, e kits de rolamentos.
Allison 1000-2000 Series Service Manual.pdfRolandasPetkus
This document provides an overview of the Allison 1000/2000 series transmissions. It describes the key features and components including:
- Five speeds forward with overdrive fifth gear, plus reverse and neutral controlled electronically through six solenoids.
- Planetary gear sets and five clutch packs provide the gear ratios and shifting.
- Fully automatic operation controlled by the transmission control module (TCM).
- Common hydraulic system and oil pump provides pressure for clutches and lubrication.
- Variety of shift selector positions available depending on model and application.
John deere power tech 2.9 l diesel engines service repair manualfjsekkxszdmmem
This document provides an overview and summary of repair procedures for PowerTech 2.9 L diesel engines. It begins with introductory information such as engine identification, specifications, and diagrams. It then details procedures organized by major engine systems, including the cylinder head and valves (Group 05), cylinder block (Group 10), crankshaft (Group 15), and other systems. The document emphasizes safety and provides concise instructions for repairs, with references to additional information sources. It aims to equip technicians with the essential guidance for servicing these engines.
DITA and S1000D Two Paths to Structured DocumentationJoseph Storbeck
Today, the creation of usable technical documentation is accomplished through through the managed authoring of quality content. Increasingly, that content is being created using structured data, in part due to its unique inherent advantages. This presentation will compare the similarities and differences between two of the most popular XML-based structured data specifications that are being adopted by companies world-wide: DITA and S1000D.
NOTE: This presentation refers to DITA 1.2
Every business strives to get the most out of their technical data and must find opportunities to fulfill that requirement through reuse. S1000D was conceived as a model for improving reuse through topic-oriented modularization of content and enables companies to achieve this lofty goal.
Instead of creating new content or copying and pasting information which may or may not be current and authoritative, organizations must manage a repository of content assets – or S1000D Data Modules – that can be centrally managed, maintained and reused across the enterprise.
Blisks are single engine components that combine a rotor disk and blades into one piece, either through casting, machining, or welding. Blisks replace separate disks and blades in turbomachinery. They provide advantages such as eliminating the need to attach blades to disks, decreasing the number of components, reducing drag, and increasing compression efficiency. Additionally, removing the dovetail attachment of traditional blades eliminates a common source for cracks to form.
This document is a technical manual providing repair and maintenance instructions for Deere Power Systems Group diesel engines models 3179, 4239, 6359, 4276, and 6414. It covers specifications, tools required, disassembly and assembly sequences, and procedures for servicing various engine components like the cylinder head, valves, rocker arms, push rods, cylinder block, and more. Safety precautions are emphasized throughout and mechanics are instructed to clean components, check tolerances, replace seals, and adjust clearances as specified to properly service these engines.
The document outlines Novell's documentation process for iFolder. It includes:
1. Deliverables such as admin guides, user guides, help documents, and readme files.
2. A documentation development life cycle with phases for requirements, planning, design, implementation, validation, release, and post-release.
3. Roles and responsibilities for the documentation, development, and test teams in each phase.
1997 Porsche Boxster 986 Service Repair Manualjksmmemd
This is the Highly Detailed factory service repair manual for the1997 PORSCHE BOXSTER 986, this Service Manual has detailed illustrations as well as step by step instructions,It is 100 percents complete and intact. they are specifically written for the do-it-yourself-er as well as the experienced mechanic.1997 PORSCHE BOXSTER 986 Service Repair Workshop Manual provides step-by-step instructions based on the complete dis-assembly of the machine. It is this level of detail, along with hundreds of photos and illustrations, that guide the reader through each service and repair procedure. Complete download comes in pdf format which can work under all PC based windows operating system and Mac also, All pages are printable. Using this repair manual is an inexpensive way to keep your vehicle working properly.
Service Repair Manual Covers:
986 Group 0a General
986 Group 1 Engine To 13
986 Group 1 Engine From 15
986 Group 2 Fuel-Exhaust
986 Group 3 Transmission-Automatic
986 Group 3 Transmission-Manual
986 Group 4 Running Gear
986 Group 5 Body
986 Group 6 Body Exterior
986 Group 7 Body Interior
986 Group 8-9 AC-Electrics
986 Group 9 Circuit Diagrams From 00
986 Group 9 Circuit Diagrams To 99
986 Group 0a Diagnosis To 45
986 Group 0a Diagnosis From 69
986 owners manual
File Format: PDF
Compatible: All Versions of Windows & Mac
Language: English
Requirements: Adobe PDF Reader
NO waiting, Buy from responsible seller and get INSTANT DOWNLOAD, Without wasting your hard-owned money on uncertainty or surprise! All pages are is great to have1997 PORSCHE BOXSTER 986 Service Repair Workshop Manual.
Looking for some other Service Repair Manual,please check:
https://www.aservicemanualpdf.com/
Thanks for visiting!
8
ATA Spec 100 provides industry-wide standards for aircraft maintenance documentation, including systems numbering and guidelines for technical manual content and format. It was originally released in 1999 but has since been combined with other specifications into a consolidated standard called ATA iSpec 2200, which provides guidelines for electronic aircraft information exchange. ATA Spec 100 defined a widely used numbering scheme for aircraft parts and systems and is used by airlines for maintenance.
This document provides a summary of revisions made to an aircraft characteristics manual for the Airbus A320 and A320NEO. Key changes include adding new illustrations and dimensions for the NEO version, revising existing illustrations and tables, and updating part numbers and effectivity. Over 60 figures and various sections throughout were revised to update information and improve layouts and clarity.
This document provides information on a water heater model HYDRONIC 10, including its technical description, installation instructions, and operating instructions. The water heater has options for 12V or 24V systems and uses diesel fuel. It connects to the vehicle's cooling water circuit, electrical system, and fuel system. Proper installation and bleeding of the cooling system is required. Safety instructions warn that exhaust contains toxic substances and the heater should not be operated in enclosed spaces or when refueling.
O documento fornece informações técnicas sobre eixos cardan agrícolas produzidos pela AEMCO. É apresentada a classificação dos cardans de acordo com sua capacidade de torque e potência, além de detalhes sobre os componentes, tipos, aplicações e manutenção dos eixos cardan.
Large scale topological optimisation: aircraft engine pylon caseAltair
1) The document discusses using topology optimization to design an improved engine pylon concept for an aircraft. It aims to reduce mass, part count, and assembly time compared to the current design.
2) Topology optimization was performed on the engine pylon and aft pylon fairing using Altair OptiStruct to minimize compliance. This provided optimized structural designs with up to 200kg mass savings per plane.
3) Preliminary analysis shows the optimized design could reduce the part count from over 650 parts to just 14 parts, and assembly time from over 2600 fixes to around 350 fixes.
IRJET - Helmet Violation Detection using Deep LearningIRJET Journal
This document describes a proposed system to detect motorcycle riders without helmets using deep learning techniques and report violations. The system uses support vector machines (SVM) for vehicle classification, convolutional neural networks (CNN) and SVM for helmet detection, and optical character recognition (OCR) for license plate recognition. Motorcycles are classified, helmet use is identified, and license plate numbers of riders without helmets are captured and SMS fines are sent. The goal is to reduce accidents by increasing helmet compliance through automated detection and reporting of violations.
Composite materials are increasingly being used in the aerospace industry. They provide benefits like reduced weight, high strength to weight ratio, corrosion resistance, and fatigue resistance compared to traditional metals. Common composite materials used include carbon fiber reinforced polymers (CFRP) and glass fiber reinforced polymers (GFRP). These are used in aircraft structures like wings, fuselage, empennage and engine components. While composites provide advantages, there are also challenges to address like delamination, damage tolerance, and high manufacturing costs. Analysis of composite wing structures helps optimize design for strength and stiffness.
This document provides a chart that lists common pipe tap sizes along with the corresponding drill bit sizes needed to tap each size of pipe. The chart includes both decimal inch and metric tap sizes ranging from 1/16 inch to 1-1/2 inches and 0.8mm to 36mm. For each tap size, the matching drill size is provided to ensure proper threading of the pipe.
The document provides an overview of aircraft structures and their key components. It discusses the fuselage, wings, empennage, landing gear, and powerplants. For each component, it describes the basic design and functions. It also covers important aircraft structural concepts like stressed skin construction, monocoque vs semi-monocoque design, and choices of lightweight metal materials. Overall the document serves as a high-level introduction to aircraft structures and the major structural components of airplanes.
1) O documento fornece instruções sobre a instalação e manutenção corretas de rolamentos para evitar acidentes e aumentar a vida útil.
2) A lubrificação e manutenção adequadas são essenciais para o bom funcionamento dos rolamentos.
3) A não observância das instruções pode causar falhas no equipamento e riscos de acidentes.
O documento lista códigos e descrições de itens de rolamentos Eaton, incluindo rolamentos de esferas, rolamentos de agulhas, rolamentos de roletes cilíndricos e conicos, conjuntos de capas e cones, e kits de rolamentos.
Allison 1000-2000 Series Service Manual.pdfRolandasPetkus
This document provides an overview of the Allison 1000/2000 series transmissions. It describes the key features and components including:
- Five speeds forward with overdrive fifth gear, plus reverse and neutral controlled electronically through six solenoids.
- Planetary gear sets and five clutch packs provide the gear ratios and shifting.
- Fully automatic operation controlled by the transmission control module (TCM).
- Common hydraulic system and oil pump provides pressure for clutches and lubrication.
- Variety of shift selector positions available depending on model and application.
John deere power tech 2.9 l diesel engines service repair manualfjsekkxszdmmem
This document provides an overview and summary of repair procedures for PowerTech 2.9 L diesel engines. It begins with introductory information such as engine identification, specifications, and diagrams. It then details procedures organized by major engine systems, including the cylinder head and valves (Group 05), cylinder block (Group 10), crankshaft (Group 15), and other systems. The document emphasizes safety and provides concise instructions for repairs, with references to additional information sources. It aims to equip technicians with the essential guidance for servicing these engines.
DITA and S1000D Two Paths to Structured DocumentationJoseph Storbeck
Today, the creation of usable technical documentation is accomplished through through the managed authoring of quality content. Increasingly, that content is being created using structured data, in part due to its unique inherent advantages. This presentation will compare the similarities and differences between two of the most popular XML-based structured data specifications that are being adopted by companies world-wide: DITA and S1000D.
NOTE: This presentation refers to DITA 1.2
Every business strives to get the most out of their technical data and must find opportunities to fulfill that requirement through reuse. S1000D was conceived as a model for improving reuse through topic-oriented modularization of content and enables companies to achieve this lofty goal.
Instead of creating new content or copying and pasting information which may or may not be current and authoritative, organizations must manage a repository of content assets – or S1000D Data Modules – that can be centrally managed, maintained and reused across the enterprise.
SuiteHelp 4.0: Latest Features in Enterprise WebhelpSuite Solutions
SuiteHelp 4.0 is a solution for delivering HTML-based content across devices. It provides content structure, management, collaboration and distribution capabilities. The document reviews SuiteHelp's high-level architecture, native HTML5 generation capabilities, and new features including responsive design, search improvements, and video support. Upcoming releases will focus on customer feedback and improved chunking support.
ADG S1000D Series - S1000D Information Sets & PublicationsAbsolute Data Group
Join ADG's Tammy Halter and Reeta Nye, to learn about the types of information sets available, where to find the information sets and how they equate to the content that is to be presented.
Also learn the impacts of information sets on Data Module Coding, Titles and the DMRL and how the information sets drive the structure of your publications.
View ADG's education session to learn the Benefits of Using S1000D. Topics covered include: Planning and Management / Production / Exchange / Distribution / Relationship with Computer Based Training Systems (CBT).
Gone through articles and presentations on the web and got a half-baked understanding of the Darwin Information Typing Architecture (DITA)?
Refer to my DITA Quick Start presentation for the 2007 STC India Conference to learn to evaluate, plan and start implementing DITA.
In this presentation, you will learn about the following:
o Structured authoring and XML
o Key DITA concepts: topics, maps, specialization
o DITA architecture and content model
o Authoring in topics
o Organizing content using DITA maps
o Creating relationship tables
o Conditional text and reuse in DITA
o Metadata support in DITA
o DITA tools, standards and processes
o Publishing with the DITA Open Toolkit
The document describes the 8 step data mining process:
1) Defining the problem, 2) Collecting data, 3) Preparing data, 4) Pre-processing, 5) Selecting an algorithm and parameters, 6) Training and testing, 7) Iterating models, 8) Evaluating the final model. It discusses issues like defining classification vs estimation problems, selecting appropriate inputs and outputs, and determining when sufficient data has been collected for modeling.
Preparing Your Legacy Data for Automation in S1000Ddclsocialmedia
This document discusses preparing legacy data for automation in S1000D. It outlines the challenges of converting traditional linear documents into the modular structure required by S1000D. These challenges include identifying reusable content, assigning data modules and codes, and structuring information across publications. The document recommends planning thoroughly for a conversion project, including assessing source materials, analyzing content reuse, specifying the conversion, and normalizing data. It describes setting up the conversion project, performing document analysis, and developing a detailed specification to guide the conversion process.
New Aircraft - Trends & Technologies to Improve MROMichael Denis
Presentation given at the Airline MRO Network - North America conference in Seattle. This presentation by Michael Wm. Denis of Flatirons Solutions, covered new generation aircraft and the trends and technologies coming to market that improve maintenance, repair and overhaul (also known as Service Lifecycle Management (SLM)).
Additional presentations were given by Airbus, Boeing, GE Aviation, MTU, Lockheed Martin, Honeywell, Lufthansa Technik, FAA, ARSA, Pratt & Whitney, UTC, and AJW.
Minimalism Revisited — Let’s Stop Developing Content that No One Wantsdclsocialmedia
Dr. JoAnn Hackos, Comtech President and Director of the Center for Information-Development Management (CIDM), demonstrates how using a minimalist approach in developing content is more relevant today than ever before. Busy customers simply want simple help on performing a task and getting a job done. Learn what minimalism really feels like. Learn about designing minimalist information that gets your customers coming back for more.
S1000D Training for Issue 4.0
S1000D, “International specification for technical publications using a common source database”, is an international specification for the production of technical publications. Since its inception over 30 years ago, S1000D has grown to where it is now used widely around the world. Currently, its uses include:
Defense systems – including land, sea, and air products
Civil aviation products
Construction industry products
Ship industry products
The specification is publicly available and is free to download from this web site. Downloads include the specification, schemas, sample files, and much more.
S1000D is the European standard of technical publications or technical documentation being followed in Aerospace since 1980, which uses CSDB, a Common source database which is used for preparing, managing, and publishing technical information for a warship, or Aerospace, or even Civil airlines too.
S1000D is the European standard of technical publications or technical documentation being followed in Aerospace since 1980, which uses CSDB, a Common source database which is used for preparing, managing, and publishing technical information for a warship, or Aerospace, or even Civil airlines too.
The creation and delivery of illustrations is a significant component of an S1000D project. There are several factors that require consideration when creating and maintaining illustrations.
Abstract: The creation and delivery of illustrations is a significant component of an S1000D project. There are several factors that require consideration when creating and maintaining illustrations…
S1000D is the European standard of technical publications or technical documentation being followed in Aerospace since 1980, which uses CSDB, a Common source database which is used for preparing, managing, and publishing technical information for a warship, or Aerospace, or even Civil airlines too.
S1000D is a European technical documentation standard used in aerospace and defense industries since 1980. It uses a common source database (CSDB) to store and manage reusable data modules that can be compiled to generate technical manuals. The benefits of S1000D include reduced costs from reusable data, standardized naming conventions, open format, and the ability to generate customized outputs from a single data source. Major users include the military, aviation, and space industries. Code and Pixels is an experienced developer of S1000D technical documentation.
S1000D is the European standard of technical publications or technical documentation being followed in Aerospace since 1980, which uses CSDB, a Common source database which is used for preparing, managing, and publishing technical information for a warship, or Aerospace, or even Civil airlines too.
Technical manuals (e.g. maintenance, user, training, operations, etc) published in electronic format are becoming more and more popular than paper based manuals for their interactivity, convenience and ease of use.
Application framework (ofen called TAM) is Application component of TM Forum frameworx. TAM maps with Business Process framework (aka eTOM) and Information Framework (aka SID).
This presentation discusses the Defense Interest Group (DIG) Business Rules (DIGBR) for implementing technical publications using S1000D specifications. It provides an overview of the DIGBR, including the challenges faced in developing common rules across nations. Examples are given of applying the DIGBR within NATO and Swedish military projects. The presentation also outlines future targets, such as publishing the DIGBR and BREX data module. The overall aim of the DIGBR is to promote standardization and interoperability when authoring technical manuals using S1000D.
This document discusses the PA DIM (Process Automation Device Information Model) presentation. It introduces PA DIM as a standardized information model for accessing device data via OPC-UA. PA DIM is based on NAMUR requirements and reuses interfaces from the OPC UA Device Integration model. It allows mapping device information contained in packages like FDI to OPC-UA clients, providing access to signals, functions and health of devices nearly independently of the physical communication protocol. The presentation also provides an overview of common device driver types like EDD, FDT/DTM and FDI and how OPC-UA supports information modeling and both client-server and publish-subscribe communication mechanisms.
S1000DTM is an international specification for technical publications that utilizes a common source database to allow reuse of data modules across publications. CDG is committed to supporting S1000DTM through technical authoring services, representation on standards committees, and being a pioneer in applying S1000DTM to land systems. Key benefits of S1000DTM include reduced costs through reuse of data modules and facilitating information sharing between organizations.
This document provides an overview of Mercedes-Benz's product documentation system called DIALOG which is used to administer bills of materials. It describes the structure and hierarchy used to represent different parts, assemblies, and variants in DIALOG. Key aspects include the use of main modules, modules, submodules, positions, and variants to represent the parts list structure. It also discusses codes used to define technical attributes and customer options and how these are used to control applications between parts lists, models, and variants. The document provides examples of exploring and expanding the parts list structure in DIALOG to view different levels from the overall product down to individual part numbers.
NIEM and XML for Architects and DevelopersBizagi Inc
The document provides an overview of delivering data services aligned with the National Information Exchange Model (NIEM). It discusses NIEM and XML, the NIEM data model and domains, challenges with NIEM, and tooling to help with NIEM implementation including the Content Assembly Mechanism (CAM) toolkit. The presentation emphasizes that dictionaries are a key pillar for information sharing and outlines an approach to developing domain dictionaries within a semantic framework.
The existence of countless proprietary file formats and the exchange of 3D CAD data has been a significant problem since the beginning of 3D CAD modeling. CAD applications and methods using digital data are constantly changing, which predicates the need for a solution to share validated and accurately translated data, thus the birth of STEP242
Automotive Diagnostic Systems - From OBD to Open Diagnostics Exchange formatTorben Haagh
Like in other fields, in automotive fault diagnosis, humans were increasingly removed from the loop, and computers took over until we are now at the stage of on-board diagnosis (OBD). Sensors are attached to various components, such as a cooling system's thermostat, and a wire runs from that through a harness and to a terminal block, which, in turn, is plugged into a diagnostic machine outside the car.
Find out more about Automotive Diagnostic Systems here: http://bit.ly/automotive-diagnostics
This Object Management Group (OMG) RFP solicits submissions identifying and defining mechanisms to achieve integration between DDS infrastructures and TSN networks. The goal is to provide all artifacts needed to support the design, deployment and execution of DDS systems over TSN networks.
The DDS-TSN integration specification sought shall realize the following functionality:
● Define mechanisms that provide the information required for TSN-enabled networks to calculate any network schedules needed to deploy a DDS system.
OMG RFP
● Identify those parts of the set of the IEEE TSN standards that are relevant for a DDS-TSN integration and indicate how the DDS aspects are mapped onto, or related to, the associated TSN aspects. Examples include TSN- standardized information models for calculating system-wide schedules and configuring network equipment.
● Identify and specify necessary extensions to the [DDSI-RTPS] and [DDS- SECURITY] specifications, if any, to allow DDS infrastructures to use TSN- enabled networks as their transport while maintaining interoperability between different DDS implementations.
● Identify and specify necessary extensions to the DDS and DDS- XML specification, if any, to allow declaration of TSN-specific properties or quality of service attributes.
Considerations on usage of Computer on Modules for Applications inside Emerge...Toradex
This document discusses considerations for using computer modules in emergency response vehicles. It describes a project where an Italian municipality needed a rugged, scalable computing platform for its emergency vehicles. A solution was developed using Diamond Systems' Eaglet carrier board coupled with Toradex Apalis computer-on-modules. This provided a flexible, long-life system that met the client's needs within budget. The modular design allows easy processor upgrades or replacements to extend the product lifetime.
3. Overview of S1000D
The information contained in this presentation was gleaned and/or
copied from the S1000D International specification for
technical publications, Issue 4.0,1 2009-05-12.
Information was also gleaned from
The Aerospace Industries Association, A Recommendation to
the Department of Defense to Adopt the S1000D – the
International Specification for Technical Documentation,
April 25,2008
4. Overview of S1000D
Information in this training covers the following:
• A brief history and the benefits of S1000D
• Discussion of the S1000D data types and associated codes:
Data Modules
Information Control Numbers
Data Module Requirements List
Publication Modules
Data Dispatch Notes
• Applicability
• Business Rules
5. “S1000D is an international specification for producing technical
publications. It is co-owned by the European Association of Aerospace
Industries (ASD), the Aerospace Industries Association (AIA) and the Air
Transport Association (ATA).
Although its roots are in the aviation industry, the specification supports any
type of air, land or sea system or machinery that requires maintenance,
operation and configuration to parts and supplies.”
Aerospace Industries Association, A Recommendation to the Department of Defense to Adopt the S1000
What is S1000D?
Overview of S1000D
6. “Amongst many S1000D working groups, the U.S.-based U.S.
Specification Management Group (USSMG) and the international
Technical Publication Specification Maintenance Group (TPSMG) have
taken the lead in developing and maintaining the S1000D specification.”
“To assist the USSMG in defining and submitting U.S. interests toward
the specification, the U.S. Specification Implementation Group (USSIG)
was established under the USSMG to recommend detailed technical
solutions, perform feasibility reviews, submit change proposals, and
advise USSMG on a course forward.”
“AIA manages the USSMG and the USSIG.”
Aerospace Industries Association, A Recommendation to the Department of Defense to Adopt the S1000
Overview of S1000D
7. Why was S1000D developed?
In the 1980s, documentation for military projects in Europe used various
national specifications, making data interchange between nations difficult.
During this same period, civil aviation was successfully using ATA S100 to
deliver and interchange information internationally.
To ease interchange between nations, the AeroSpace and Defence
Industries Association of Europe (ASD) (formerly AECMA) developed the
S1000D specification; derived from ATA S100, it was widely adopted in
Europe by military projects.
Overview of S1000D
8. Why has S1000D continued to evolve?
Documentation for military projects in the various U.S. joint services
were written to various standards, making interchange difficult and
often requiring each service to support multiple military specifications.
Documentation for military variants of commercial aircraft had to be
converted into various mil-specs from civil aviation standards.
Overview of S1000D
9. “The most important factor in the development and oversight of S1000D is
that it is an industry specification. Industry is the primary advocate for
developing government-procured systems, and it is industry that sees the
benefit in developing documentation in S1000D”
“Hundreds of individual DoD contractors that specialize in life cycle
technical documentation have volunteered tens of thousands of hours over
seven years to shape S1000D into a specification that can support all
services and their equipment.”
Overview of S1000D
10. The Benefits of S1000D
“Most experts will agree that the single greatest benefit
offered by S1000D is the ability to re-use data.
With S1000D, specific data modules are created
(containing text and/or graphics), and then stored in the
Common Source Database (CSDB).
You can then reuse and redistribute that very same data
module in many other different projects or publications.”
So, why use S1000D and what are the benefits?
11. For instance, output is controlled by a publication module (PM)
that organizes data modules (DM) and multiple publication
modules can reference the same data module.
Content is reusable across systems, configurations, and delivery
formats.
The Benefits of S1000D
12. Why use a CSBD?
Because the spec calls for it!
It uses a Common Source Database (CSDB)
The Benefits of S1000D
14. Business Rules
Business rules are decisions that are made by a project or an organization on
how to implement S1000D.
Business rules cover all aspects of S1000D and are not limited to authoring or
illustrating.
Throughout the specification, business rule decision points have, wherever
possible, been identified. However, in many cases, they have been marked as
"None identified". Projects and organizations must decide whether certain
business rules decisions must be made in these cases.
15. Business Rules
S1000D recognizes that a number of decisions related to its implementation are
made not only on a project level but often also on an organizational level (eg
national Ministries or Departments of Defense (MoD or DoD), international
consortia such as Civil Aviation Working Group (CAWG), etc).
The structure and content of business rules between projects and various
organizations can differ considerably.
In support of the business rule categories, a layered model of business rules is
introduced.
17. Data Modules
Data Modules are defined in the S1000D issues as:
“The smallest self contained information unit within
a technical publication.”
Data modules (DMs) focus on fulfilling a single self-contained
purpose.
18. Data modules (DMs) focus on fulfilling a single self-contained
purpose.
For example, a DM may contain a:
• Procedure
• Description of Function
• Fault isolation
• Illustrated Parts Data
Data Modules
19. Data Module Types
• Descriptive
• Procedural
• Illustrated Parts Data
• Fault Isolation
• Wiring Diagram
• Maintenance Scheduling
• Crew/operator
• Technical Information Repository
• Business Rules Exchange (BREX)
• Container
New in 4.0 are:
• Checklist
• Learning
• SCORM Content Package
Data modules types identify a purpose for the data. The types are:
20. Data Module Codes
Each data module has unique data module code (DMC) that
indicates to what component it applies and the information it
contains and conveys.
“The data module code is the standardized and structured
identifier of a data module.
The data module code is used to manage data modules in the
CSDB, to retrieve them or to gain access to them in an electronic
environment.”
22. Data Module Codes
“S1000D does for technical data what inventory control mechanisms do
for parts management:
Data becomes a configuration item that must be created, tracked,
modified and distributed.
The rigor applied to data management ought to come from some type of
neutral source in much the same way Universal Product Codes (UPC)
provide standardized barcodes for tracking inventory.
S1000D is an industry specification for the life cycle maintenance of
air, land, and sea vehicles, but it can also apply to any technical system
that requires parts management, operation, and life cycle maintenance.”
25. DMC-S1000DBIKE-AAA-D00-00-00-00AA-00PA-D_004-00_EN-US.xml
Model Identification Code
The following is a sample DM xml file. The DMC is highlighted in grey.
Data Module Codes (DMCs)
System Difference Code
Standard Numbering System
The standard numbering system is
comprised of 4-5 numbers identifying the
system, subsystem, and sub-subsystem.
In the case where it is necessary to
indicate the type of SNS used, an
additional single alphanumeric character
is placed in front of the SNS. The
character is called the materiel item
category code.
In this example it is indicated by D in the
System Code.
26. DMC-S1000DBIKE-AAA-D00-00-00-00AA-00PA-D_004-00_EN-US.xml
Model Identification Code
The following is a sample DM xml file. The DMC is highlighted in grey.
Data Module Codes (DMCs)
System Difference Code
Standard Numbering System
The materiel item category code is used
to indicate different SNS coding
structures that are applicable to an
individual project at the system,
subsystem and sub-subsystem level
within the SNS.
27. DMC-S1000DBIKE-AAA-D00-00-00-00AA-00PA-D_004-00_EN-US.xml
Model Identification Code
The following is a sample DM xml file. The DMC is highlighted in grey.
Data Module Codes (DMCs)
System Difference Code
Standard Numbering System
“The unit or assembly is two or four
alphanumeric characters. It is a sequential
number starting from 01 or 0001.
The use of four characters provides
identification for units in complex systems.”
Unit or Assembly
28. DMC-S1000DBIKE-AAA-D00-00-00-00AA-00PA-D_004-00_EN-US.xml
Model Identification Code
The following is a sample DM xml file. The DMC is highlighted in grey.
Data Module Codes (DMCs)
System Difference Code
Standard Numbering System
Unit or Assembly
Disassembly Code / Disassembly Code Variant
“The disassembly code
identifies the breakdown
condition of an assembly to
which maintenance information
applies.”
(2 alphanumeric characters - 00)
“The disassembly code
variant designates alternative
items of equipment or
components differing slightly
in design, but not enough to
warrant a change of the system
difference code.”
(1-3 alphanumeric characters - AA)
29. DMC-S1000DBIKE-AAA-D00-00-00-00AA-00PA-D_004-00_EN-US.xml
Model Identification Code
Data Module Codes (DMCs)
System Difference Code
Standard Numbering System
Unit or Assembly
Disassembly Code / Disassembly Code Variant
Information Code / Information Code Variant
The following is a sample DM xml file. The DMC is highlighted in grey.
“The information code
identifies the type of
information within a data
module.”
(3 alphanumeric characters – 00P)
The information code
variant identifies any
variation in the activity
defined by the information
code
(1 alphanumeric character – A)
30. DMC-S1000DBIKE-AAA-D00-00-00-00AA-00PA-D_004-00_EN-US.xml
Model Identification Code
Data Module Codes (DMCs)
System Difference Code
Standard Numbering System
Unit or Assembly
Disassembly Code / Disassembly Code Variant
Information Code / Information Code Variant
The following is a sample DM xml file. The DMC is highlighted in grey.
Item Location Code
“The item location
code indentifies the
situation to which the
information is
applicable, eg where
the maintenance task
will be carried out in
terms of a Product.”
31. <dmIdent>
<dmCode modelIdentCode="S1000DBIKE" systemDiffCode="AAA"
systemCode="D00" subSystemCode="0" subSubSystemCode="0"
assyCode="00" disassyCode="00" disassyCodeVariant="AA"
infoCode="00P" infoCodeVariant="A" itemLocationCode="D"/>
<language countryIsoCode="US" languageIsoCode="en"/>
<issueInfo issueNumber="004" inWork="00"/>
</dmIdent>
Element Tags in the XML for the DMC
In the document, the DMC is stored within the <dmCode>
element. The data in the xml file indicating the DMC in
<dmCode> for the example above is (highlighted in grey):
DMC-S1000DBIKE-AAA-D00-00-00-00AA-00PA-D_004-00_EN-US.xml
32. Model Identification Code
System Difference Code
Standard Numbering System
Assembly Code
Information Code / Information Code Variant
Item Location Code
Disassembly Code / Disassembly Code Variant
The remainder of the codes (within dmIdent) are part of the XML filename.
Issue Number
Data Module Codes (DMCs)
For every
release of a
data module,
the issue
number must
be incremented
by one.
DMC-S1000DBIKE-AAA-D00-00-00-00AA-00PA-D_004-00_EN-US.xml
33. Model Identification Code
System Difference Code
Standard Numbering System
Assembly Code
Information Code / Information Code Variant
Item Location Code
Disassembly Code / Disassembly Code Variant
Issue Number
In Work
Data Module Codes (DMCs)
The remainder of the codes (within dmIdent) are part of the XML filename.
The inwork number is used to
track drafting of changed
information during the
information generation process.
DMC-S1000DBIKE-AAA-D00-00-00-00AA-00PA-D_004-00_EN-US.xml
34. <dmIdent>
<dmCode modelIdentCode="S1000DBIKE" systemDiffCode="AAA"
systemCode="D00" subSystemCode="0" subSubSystemCode="0"
assyCode="00" disassyCode="00" disassyCodeVariant="AA"
infoCode="00P" infoCodeVariant="A" itemLocationCode="D"/>
<language countryIsoCode="US" languageIsoCode="en"/>
<issueInfo issueNumber="004" inWork="00"/>
</dmIdent>
Element Tags in the XML for the DMC
The data in the xml file indicating the issue number and
in work codes:
DMC-S1000DBIKE-AAA-D00-00-00-00AA-00PA-D_004-00_EN-US.xml
35. Data Module Codes (DMCs)
Model Identification Code
System Difference Code
Standard Numbering System
Assembly Code
Information Code / Information Code Variant
Item Location Code
Disassembly Code / Disassembly Code Variant
Issue Number
In Work
The remainder of the codes (within dmIdent) are part of the XML filename.
DMC-S1000DBIKE-AAA-D00-00-00-00AA-00PA-D_004-00_EN-US.xml
Language and
Country codes
Language: two alpha characters from
International Standards Organisation (ISO)
specifying the language.
Country: two alpha characters from ISO to
denote the country where the language is
spoken.
36. <dmIdent>
<dmCode modelIdentCode="S1000DBIKE" systemDiffCode="AAA"
systemCode="D00" subSystemCode="0" subSubSystemCode="0"
assyCode="00" disassyCode="00" disassyCodeVariant="AA"
infoCode="00P" infoCodeVariant="A" itemLocationCode="D"/>
<language countryIsoCode="US" languageIsoCode="en"/>
<issueInfo issueNumber="004" inWork="00"/>
</dmIdent>
Element Tags in the XML for the DMC
The data in the xml file indicating the language and
country codes:
DMC-S1000DBIKE-AAA-D00-00-00-00AA-00PA-D_004-00_EN-US.xml
37. Element Tags in the XML for the DMC
The basic structure or hierarchy of
the elements in the DM is shown to
the right.
The data module code information is
contained in the Data Module
Address section. The code is
metadata, it is not data that is
displayed in the publication itself.
38. Element Tags in the XML for the DMC
<dmIdent>
<dmCode modelIdentCode="S1000DBIKE" systemDiffCode="AAA"
systemCode="D00" subSystemCode="0" subSubSystemCode="0"
assyCode="00" disassyCode="00" disassyCodeVariant="AA"
infoCode="00P" infoCodeVariant="A" itemLocationCode="D"/>
<language countryIsoCode="US" languageIsoCode="en"/>
<issueInfo issueNumber="004" inWork="00"/>
</dmIdent>
40. XML and the DMC
Specify the data module code considering the following XML:
<dmIdent>
<dmCode modelIdentCode="S1000DLIGHTING"
systemDiffCode="AAA" systemCode="D00"
subSystemCode="0" subSubSystemCode="0" assyCode="00"
disassyCode="00" disassyCodeVariant="AA" infoCode="056"
infoCodeVariant="A" itemLocationCode="A"/>
<language countryIsoCode="US" languageIsoCode="en"/>
<issueInfo issueNumber="007" inWork="00"/>
</dmIdent>
41. XML and the DMC
Specify the XML filename in which this data appears:
<dmIdent>
<dmCode modelIdentCode="S1000DLIGHTING"
systemDiffCode="AAA" systemCode="D00"
subSystemCode="0" subSubSystemCode="0" assyCode="00"
disassyCode="00" disassyCodeVariant="AA" infoCode="056"
infoCodeVariant="A" itemLocationCode="A"/>
<language countryIsoCode="US" languageIsoCode="en"/>
<issueInfo issueNumber="007" inWork="00"/>
</dmIdent>
42. The D in the systemCode indicates: ________________________
The 00 in the system and subsystem codes indicate:
_____________________________________________________
XML and the DMC
Refer to the S1000D International specification for technical
publications, Issue 4.0, 2008-08-01 and interpret the following:
systemCode="D00" subSystemCode="0" subSubSystemCode="0“
43. Defining the Data Module Codes
Below is an example for the lab that follows—assume that
you are asked to create a DMC that contains a procedure for
draining the gas tank on the Jeep Wrangle as part of routine
servicing.
In addition, note that your Business Rules specify that the
MIC is JEEP and the SDC is defined as 01 for the Wrangler,
02 for the Liberty, and 03 for the Commander and that other
codes should be obtained from the specification.
MIC SDC System Sub
system & sub-subsystem
Unit
Assembly
DC DCV IC ICV ILC
JEEP 01 12 10 00 00 00 200 0 A
44. Defining the Data Module Codes
MIC SDC System Sub
system & sub-subsystem
Unit
Assembly
DC DCV IC ICV ILC
Using the Business Rules and other information provided
previously and create a DMC for the procedure to
disassemble and remove the brakes on the Jeep Liberty.
This is to be done as part of an examination and check for
proper functioning.
46. Illustrations and Multimedia
Illustrations and multimedia are identified by a unique
Information Control Number (ICN).
Illustrations are typically
• Vector line drawings (CGM)
• Raster images (CCITT Grp/4, TIFF)
• Photos and other artwork (JPEG, GIF, PNG)
Multimedia can be of any type defined and supported by the
project’s business rules.
47. ICN-S1000DBIKE-AAA-D000000-0-U8025-00502-A-004-01.CGM
Model Identification Code
System Difference Code
Standard Numbering System
Information Control Number (ICN)
The following is a sample Model Identication Code based
ICN.
Assembly Code
Responsible Partner Company Code
Orginator Code (NCAGE)
Unique Identifier
Information Variant Code
Issue Number
Security Classification
48. Model Identification Code
System Difference Code
Standard Numbering System
Information Control Number (ICN)
Assembly Code
The ModelIC, SDC, SNS and Assembly Code is the same as that
for the Data Module.
ICN-S1000DBIKE-AAA-D000000-0-U8025-00502-A-004-01.CGM
49. ICN-S1000DBIKE-AAA-D000000-0-U8025-00502-A-004-01.CGM
Information Control Number (ICN)
The Responsible Partner Company Code is the company or
organization responsible for the illustration independent of its use in
the data module.
Format: 1 character, defined by the project.
Example: In the example of the bike data’s ICN (shown above) the
Responsible Partner Company Code is represented by 0.
50. ICN-S1000DBIKE-AAA-D000000-0-U8025-00502-A-004-01.CGM
ICN – Originator Code
The Originator Code specifies the originator of the illustration. It is used as
a status element in the identification and status section of the data module.
characters.
Format: 5 alphanumeric characters NCAGE code
Example: In the example of the bike data’s ICN shown above, the
Originator Code is represented by U8025
51. ICN – Unique Identifier
The Unique Identifier starts from 00001 for each originating
company.
• The identifier must be unique for each originator code.
• For each model identification code, the identifier must be unique
for each originating company.
Format: 5 digits
Example: In the example of the bike data’s ICN shown above, the
Information Sequential Number is represented by 00502
ICN-S1000DBIKE-AAA-D000000-0-U8025-00502-A-004-01.CGM
52. ICN-S1000DBIKE-AAA-D000000-0-U8025-00502-A-004-01.CGM
ICN – Variant Code
The Variant Code identifies the variants of a basic illustration. A variant
is a supplemental scaled, cropped, rotated, mirrored, and/or annotated
basic illustration.
Format: 1 alpha character The variant A identifies a basic illustration and
B identifies the variant.
Example: In the example of the bike data’s ICN shown above, the
Variant Code is represented by A.
53. ICN-S1000DBIKE-AAA-D000000-0-U8025-00502-A-004-01.CGM
ICN –Issue Number
The Issue Number starts from 001 for each basic illustration and is
incremented each time the illustration is updated.
Format: 3 digits
Example: In the example of the bike data’s ICN shown above, the Issue
Number is represented by 004 .
54. ICN-S1000DBIKE-AAA-D000000-0-U8025-00502-A-004-01.CGM
ICN – Security Classification
The Security Classification identifies the security classification of the
illustration. The same classes as the data modules must be used. The
illustration, multimedia object or other data has its individual security
classification independent of where it is used. If an illustration is
reclassified, it is given a new issue number.
Format: 2 numeric characters
Example: In the example of the bike data’s ICN shown above, the Security
Classification is represented by 1.
55. ICN – Unique Identifier
Note that these two graphics were supplied by
the same originator (identified by the NCAGE
code S7282) and have the same MIC, SDC,
and the SNS.
However, they can be differentiated by the Unique Identifier.
56. ICN – CAGE code based
The CAGE code based
ICN is illustrated to the
right. It is comprised of
five parts whereas the
Model Identification Code
based ICN is ten parts.
It is similar to the Model
Identification Code based
ICN except it starts with
the Originator code.
58. Defining the Information Control Number
ICN-S1000DBIKE-AAA-D000000-0-U8025-00502-A-004-1.CGM
Using the Model Identification Code based ICN above,
create the CAGE code based ICN for the same module.
60. What is Applicability?
It provides the mechanism to identify the context for
which a data module or parts of a data module is valid.
The term Applicability refers to a set of rules and
directives used to determine if a particular piece of content
is applicable to the end user.
The S1000D applicability model supports simple to very
complex implementations.
61. Applicability
Suppose a master data module contains the information for all
deliveries for all customers.
When publishing, the data module can be filtered on data tagged
for applicability so that the publication is appropriate to the
delivery, and specific for the customer.
63. The applicability mechanism is supported by:
• the applicability annotation within data modules
• three specific data module types
S1000D Applicability
64. The three specific data module types are:
• the Applicability Cross-reference Table (ACT) data
module
• the Conditions Cross-reference Table (CCT) data
module
• the Products Cross-reference Table (PCT) data module
Although not prohibited, these data modules are not intended
to be displayed to the end user.
S1000D Applicability
65. The ACT Data Module is used to declare product attributes.
These are attributes that are not likely to change during the
product life cycle. They are typically set at manufacturing time.
For example:
• Manufacturers serial number
• Aircraft registration number
• Model number
ACT Data Module
ACT Data Module
66. ACT Data Module
Reference to the ACT is in the Data
Module’s status section, for example:
<applicCrossRefTableRef>
<dmRef xlink:type="simple"
xlink:actuate="onRequest" xlink:show="replace"
xlink:href="URN:S1000D:DMC-S1000DBIKE-
AAA-D00-00-00-00AA-00WA-D">
<dmRefIdent>
<dmCode modelIdentCode="S1000DBIKE"
systemDiffCode="AAA" systemCode="D00"
subSystemCode="0" subSubSystemCode="0"
assyCode="00" disassyCode="00"
disassyCodeVariant="AA" infoCode="00W"
infoCodeVariant="A" itemLocationCode="D"/>
</dmRefIdent>
</dmRef><
/applicCrossRefTableRef>
The infoCode 00W specifies the
Attribute Cross Reference Table.
67. CCT Data Module
The CCT Data Module is used to declare conditions that
affect the applicability of the data, such as:
• Technical
• Operational
• Environmental
For example:
• Icy conditions yes or no
• Pre or post Service Bulletin SB1
• Combat situation yes or no
• Temperature
• Wind speed
CCT Data Module
68. PCT Data Module
The PCT Data Module is a repository for defining product
instances.
• More a product database
• Defines attributes and conditions for an actual instance
For example:
Car 1 Car 2
License plate PR-XG-63 License plate AL-32-22
Model: V40 Model: Daffodil
Year: 1998 Year: 1964
Manufacturer: Volvo Manfacturer: DAF
PCT Data Module
An instance is a single physical occurrence of the product.
69. ACT Data Module
Consider the following contents of an ACT data module:
ACT=application cross
reference table
70. ACT Data Module
“One of the attributes
is serialno
another attribute is
Model
another is version...”
“The following is a list of attributes...”
continued...
72. Identifies the CCT
Identifies the PCT
The infocode 00Q specifies a Conditions
Cross Reference Table
The infocode 00P specifies a Product Cross
Reference Table
ACT Data Module-con’t
73. The DM and Cross Reference Tables
So, the ACT is identified in the Data Module...
... and the CCT and PCT are defined in the ACT:
Data Module
<applicCrossRefTableRef>
<dmRef xlink:type="simple" xlink:actuate="onRequest"
xlink:show="replace" xlink:href="URN:S1000D:DMC-
S1000DBIKE-AAA-D00-00-00-00AA-00WA-D">
<dmRefIdent>
<dmCode modelIdentCode="S1000DBIKE"
systemDiffCode="AAA" systemCode="D00"
subSystemCode="0" subSubSystemCode="0"
assyCode="00" disassyCode="00"
disassyCodeVariant="AA" infoCode="00W"
infoCodeVariant="A" itemLocationCode="D"/>
</dmRefIdent>
</dmRef><
/applicCrossRefTableRef>
Attribute Cross
Reference
Table
Conditions
Cross
Reference
Table
Product
Cross
Reference
Table
74. We’ve seen that the Brook trekker and Mountain storm have
already been established as a model and Mk1 and Mk9 have
been established as versions.
S1000D Applicability within DMs
Assume that you want to test for the Mk1 Brook trekker
or the Mk9 Mountain storm.
75. <assert>
use for a single test which resolves to a boolean True or False
<evaluate>
use as a means to group a set of assertions using the operators
and or or
These elements groupings can be nested, resulting in very
complex expressions.
The test consists of the following elements:
S1000D Applicability
Test for the Mk1 Brook trekker or the Mk9 Mountain
storm.
76. <assert> contains the following components:
• The attribute applicPropertyIdent containing the identifier of
a product attribute or condition to test.
•The attribute applicPropertyValues containing the values
and ranges to test against
S1000D Applicability—assert
<assert applicPropertyIdent=“model”
applicPropertyType=“prodattr” applicPropertyValues=“Mountain
storm”/>
<assert applicPropertyIdent=“version”
applicPropertyType=“prodattr” applicPropertyValues=“Mk1”/>
77. S1000D Applicability
In this example, the test is for the model Mountain Storm
version Mk1.
<assert applicPropertyIdent=“model”
applicPropertyType=“prodattr” applicPropertyValues=“Mountain
storm”/>
<assert applicPropertyIdent=“version”
applicPropertyType=“prodattr” applicPropertyValues=“Mk1”/>
78. S1000D Applicability
<assert applicPropertyIdent=“model”
applicPropertyType=“prodattr” applicPropertyValues=“Mountain
storm”/>
<assert applicPropertyIdent=“version”
applicPropertyType=“prodattr” applicPropertyValues=“Mk1”/>
<evaluate andOr="and">
</evaluate>
Wrap the <assert> tags with <evaluate> tags to group the
assertions, and specify if both need to be true (boolean
“and”) or if only one has to be true (boolean “or”) for the
assertions to be true.
79. <applic>
<displayText><simplePara>Mountain bicycle and (Mountain storm
Mk1 or Brook trekker Mk9)</simplePara></displayText>
<evaluate andOr="and">
<assert applicPropertyIdent="type" applicPropertyType="prodattr"
applicPropertyValues="Mountain bicycle"/>
<evaluate andOr="or">
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Mountain
storm"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk1"/>
</evaluate>
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Brook
trekker"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk9"/>
</evaluate>
</evaluate>
</evaluate>
</applic>
These and operators specify
to test for model AND version
for each of the bicycles.
Starting from the inside
evaluate expressions...
S1000D Applicability within DMs
80. DMC-S1000DBIKE-AAA-D00-00-00-00AA-941A-D_006-00_EN-US.xml
The first and tests for the
model Mountain Storm and
version MK1.
The second tests for model
Brook trekker and version
Mk9.
<applic>
<displayText><simplePara>Mountain bicycle and (Mountain storm
Mk1 or Brook trekker Mk9)</simplePara></displayText>
<evaluate andOr="and">
<assert applicPropertyIdent="type" applicPropertyType="prodattr"
applicPropertyValues="Mountain bicycle"/>
<evaluate andOr="or">
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Mountain
storm"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk1"/>
</evaluate>
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Brook
trekker"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk9"/>
</evaluate>
</evaluate>
</evaluate>
</applic>
S1000D Applicability within DMs
81. DMC-S1000DBIKE-AAA-D00-00-00-00AA-941A-D_006-00_EN-US.xml
The outside “or”
denotes if either of the evaluate
annotations are 'true' then the
entire applicability results in the
Boolean value of 'true'.
This applicability annotation
tests for either a "Mountain
storm Mk1" or a "Brook trekker
Mk9”.
S1000D Applicability within DMs
<applic>
<displayText><simplePara>Mountain bicycle and (Mountain storm
Mk1 or Brook trekker Mk9)</simplePara></displayText>
<evaluate andOr="and">
<assert applicPropertyIdent="type" applicPropertyType="prodattr"
applicPropertyValues="Mountain bicycle"/>
<evaluate andOr="or">
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Mountain
storm"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk1"/>
</evaluate>
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Brook
trekker"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk9"/>
</evaluate>
</evaluate>
</evaluate>
</applic>
82. <applic>
<displayText><simplePara>Mountain bicycle and (Mountain storm
Mk1 or Brook trekker Mk9)</simplePara></displayText>
<evaluate andOr="and">
<assert applicPropertyIdent="type" applicPropertyType="prodattr"
applicPropertyValues="Mountain bicycle"/>
<evaluate andOr="or">
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Mountain
storm"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk1"/>
</evaluate>
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Brook
trekker"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk9"/>
</evaluate>
</evaluate>
</evaluate>
</applic>
Computable assert annotation
The attribute in the assert statement in the DM
(DataModule) is matched to the attribute in the
assign statement in the PCT (Products Cross-
Reference Table):
83. <applic>
<displayText><simplePara>Mountain bicycle and (Mountain storm
Mk1 or Brook trekker Mk9)</simplePara></displayText>
<evaluate andOr="and">
<assert applicPropertyIdent="type" applicPropertyType="prodattr"
applicPropertyValues="Mountain bicycle"/>
<evaluate andOr="or">
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Mountain
storm"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk1"/>
</evaluate>
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Brook
trekker"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk9"/>
</evaluate>
</evaluate>
</evaluate>
</applic>
Computable assert annotation
The attribute in the assert statement in the DM
(DataModule) is matched to the attribute in the
assign statement in the PCT (Products Cross-
Reference Table):
84. In the data module:
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Mountain storm"/>
<assert applicPropertyIdent="version“ applicPropertyType="prodattr"
applicPropertyValues="Mk1"/>
</evaluate>
Computable assert annotation
For example – where the result = true
In the PCT:
<product>
<assign applicPropertyIdent=“serialno” applicPropertyType="prodattr“
applicPropertyValue=“1B07001”//>
<assign applicPropertyIdent="model“”applicPropertyType="prodattr“ applicPropertyValue="Mountain
storm"/>
<assign applicPropertyIdent=“version” applicPropertyType="prodattr“ applicPropertyValue="Mk1"/>
<assign applicPropertyIdent=“SB-S001” applicPropertyType="prodattr“ applicPropertyValue=“Pre"/>
</product>
85. In the data module:
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Mountain storm"/>
<assert applicPropertyIdent="version“ applicPropertyType="prodattr"
applicPropertyValues="Mk9"/>
</evaluate>
Computable assert annotation
For example – where the result = false
In the PCT:
<product>
<assign applicPropertyIdent=“serialno” applicPropertyType="prodattr“
applicPropertyValue=“1B07001”//>
<assign applicPropertyIdent="model“”applicPropertyType="prodattr“ applicPropertyValue="Mountain
storm"/>
<assign applicPropertyIdent=“version” applicPropertyType="prodattr“ applicPropertyValue="Mk1"/>
<assign applicPropertyIdent=“SB-S001” applicPropertyType="prodattr“ applicPropertyValue=“Pre"/>
</product>
86. S1000D Applicability within DMs
<applic>
<displayText><simplePara>Mountain bicycle and (Mountain storm
Mk1 or Brook trekker Mk9)</simplePara></displayText>
<evaluate andOr="and">
<assert applicPropertyIdent="type" applicPropertyType="prodattr"
applicPropertyValues="Mountain bicycle"/>
<evaluate andOr="or">
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Mountain
storm"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk1"/>
</evaluate>
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Brook
trekker"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk9"/>
</evaluate>
</evaluate>
</evaluate>
</applic>
Where does the data within the
<applic> ... </applic> tags appear in
the DM?
To specify applicability for the data
module enter the markup as shown in
the identification and status section
of the data module.
88. S1000D Applicability within DMs
The applicability information has the same construct whether applied to the
whole data module or a part of the content.
To apply to the whole data module, enter it as previously described in the DM’s
status section.
However, when defined for use for part of the content, surround the <applic>
tags with <referencedApplicGroup> ... </referencedApplicGroup> tags.
This says that it will be referenced in the
content section of the DM and it is not to
be applied to the whole DM.
89. In addition, add an id attribute to the <applic> tag. The id is used in the content
section of the DM to identify and target the applicability test to use.
For example: <applic id=“appl-001”>
S1000D Applicability within DMs
Use this ID in the DM’s content section to
“target” use of this applicability test.
91. <applic>
<displayText><simplePara>Mountain bicycle and (Mountain storm
Mk1 or Brook trekker Mk9)</simplePara></displayText>
<evaluate andOr="and">
<assert applicPropertyIdent="type" applicPropertyType="prodattr"
applicPropertyValues="Mountain bicycle"/>
<evaluate andOr="or">
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Mountain
storm"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk1"/>
</evaluate>
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Brook
trekker"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk9"/>
</evaluate>
</evaluate>
</evaluate>
</applic>
<referencedApplicGroup>
<applic id=“appl-001”>
<displayText><simplePara>Mountain bicycle and (Mountain storm
Mk1 or Brook trekker Mk9)</simplePara></displayText>
<evaluate andOr="and">
<assert applicPropertyIdent="type" applicPropertyType="prodattr"
applicPropertyValues="Mountain bicycle"/>
<evaluate andOr="or">
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Mountain
storm"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk1"/>
</evaluate>
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Brook
trekker"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk9"/>
</evaluate>
</evaluate>
</evaluate>
</applic>
</referencedApplicGroup>
S1000D Applicability within DMs
This specifies that the
applicability test is only to be
applied in the content section
where and when the
applicability id is specified.
92. <referencedApplicGroup>
<applic id=“appl-001”>
<displayText><simplePara>Mountain bicycle and (Mountain storm
Mk1 or Brook trekker Mk9)</simplePara></displayText>
<evaluate andOr="and">
<assert applicPropertyIdent="type" applicPropertyType="prodattr"
applicPropertyValues="Mountain bicycle"/>
<evaluate andOr="or">
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Mountain
storm"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk1"/>
</evaluate>
<evaluate andOr="and">
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Brook
trekker"/>
<assert applicPropertyIdent="version"
applicPropertyType="prodattr" applicPropertyValues="Mk9"/>
</evaluate>
</evaluate>
</evaluate>
</applic>
</referencedApplicGroup>
S1000D Applicability within DMs
To reference the
applicability id in the
content section of the DM...
...use the applicRefId
attribute—for example,
applicRefId=“appl-001”
(refer to the example in your notes)
93. S1000D Applicability – Textual Assert
In addition to computable assert annotations as discussed, you can add textual
assert annotations.
For instance, the assert annotation in the DM reads:
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Brook trekker"/>
Note that the textual assert annotation contains no computable components.
Since it is not computable the result is a Boolean value of true.
94. S1000D Applicability – Textual Assert
In addition to computable assert annotations as discussed, you can add textual
assert annotations.
For instance, the assert annotation in the DM reads:
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Brook trekker"/>
Note that the textual assert annotation contains no computable components.
Since it is not computable the result is a Boolean value of true.
The Applicability Cross Reference Table (ACT) is referenced—if the product
attribute declaration from ACT reads:
<productAttribute id="model" valuePattern=".">
<name>Model name</name>
<displayName>Model:</displayName>
<descr>Model of the bike</descr>
<enumeration applicPropertyValues="Brook trekker|Mountain storm"/>
</productAttribute>
95. S1000D Applicability – Textual Assert
In addition to computable assert annotations as discussed, you can add textual
assert annotations.
For instance, the assert annotation in the DM reads:
<assert applicPropertyIdent="model"
applicPropertyType="prodattr" applicPropertyValues="Brook trekker"/>
The human readable format is:
"Model: Brook trekker”
The Applicability Cross Reference Table (ACT) is referenced—if the product
attribute declaration from ACT reads:
<productAttribute id="model" valuePattern=".">
<name>Model name</name>
<displayName>Model:</displayName>
<descr>Model of the bike</descr>
<enumeration applicPropertyValues="Brook trekker|Mountain storm"/>
</productAttribute>
The Applicability Cross Reference Table (ACT) is referenced—if the product
attribute declaration from ACT reads:
<productAttribute id="model" valuePattern=".">
<name>Model name</name>
<displayName>Model:</displayName>
<descr>Model of the bike</descr>
<enumeration applicPropertyValues="Brook trekker|Mountain storm"/>
</productAttribute>
97. Applicability Exercise
Consider the following and indicate the appropriate boolean
value result.
<assert> annotation in the data module:
<assert applicPropertyIdent="serialno"
applicPropertyType="prodattr"
applicPropertyValues="1B070643~1B070799"/>
<assign> annotation from PCT:
<assign applicPropertyIdent="serialno"
applicPropertyType="prodattr"
applicPropertyValue="1B070642"/>
Boolean value result: true false
98. Applicability Exercise
Consider the following and indicate the appropriate boolean
value result.
<assert> annotation in the data module:
<assert applicPropertyIdent="serialno"
applicPropertyType="prodattr"
applicPropertyValues="1B070640|1B070642~1B070720|
1B070722|1B070730~1B070799"/>
<assign> annotation from PCT:
<assign applicPropertyIdent="serialno"
applicPropertyType="prodattr"
applicPropertyValue="1B070642"/>
Boolean value result: true false
99. Textual assert annotation
Indicate the values in the data module for a result of readable text:
Road Conditions: Icy
<assert> annotation in the data module:
<assert applicPropertyIdent=“_____________"
applicPropertyType="prodattr"
applicPropertyValues=“_______________"/>
product attribute declaration from ACT:
<productAttribute id=“conditions" valuePattern=".">
<name>Road Conditions</name>
<descr>Weather/road Conditions</descr>
<enumeration applicPropertyValues=“icy|
dry"/></productAttribute>
101. Publication Module (PM)
The publication module (PM) defines the content
and the structure of a publication.
It contains one or more references to:
• the data modules
• the illustration data modules
• other publication modules
• legacy technical publications
102. Publication Modules
Publication Model Concept
Final Deliverable
Publication Module
<pmRef> - reference to a
Publication Module, Pub A
<pmRef> - reference to a
Publication Module, Pub B
<dmRef> - reference to a Data
Module
<dmRef> - reference to a Data
Module
<dmRef> - reference to a Data
Module
<dmRef> - reference to a Data
Module
<pmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
Pub A Pub B Pub C
103. Publication Model Concept
Publication Modules
Final Deliverable
Publication Module
<pmRef> - reference to a
Publication Module, Pub A
<pmRef> - reference to a
Publication Module, Pub B
<dmRef> - reference to a
Data Module
<dmRef> - reference to a
Data Module
<dmRef> - reference to a
Data Module
<dmRef> - reference to a
Data Module
<pmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef
>
<dmRef
>
<dmRef
>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
<dmRef>
Pub A Pub B Pub C
Final Deliverable
Publication Module
Legacy
Data <externalPubRef>– legacy
data
In addition to the first publication deliverable, suppose a second that shares some of
the data:
104. Publication Module Code
The Publication Module Code (PMC) is a standardized and
structured identifier of a publication module or a final
delivered publication. The PMC is part of the unique
identifier of the publication module.
105. Publication Module Code
Use <pmref> to reference the PM.
The element <pmRef> contains details of the destination
publication module that is referred from some other S1000D
context, such as a data module, another publication
module etc. (refer to the example in your notes)
106. Publication Module (PM)
The Publication Module (PM) is similar to a Data Module in
that it has:
• an identifier and status section <identAndStatusSection>
• a content section <content>
The content section contains the references to data modules,
legacy technical publications or other publication modules in the
order and the structure the publication is to be delivered.
107. The element <pm> contains a definition of the content and
structure of a publication.
Example:
<pm>
<identAndStatusSection>
<pmAddress>... </pmAddress>
<pmStatus>...</pmStatus>
</identAndStatusSection>
<content>...</content>
</pm>
Publication Module (PM)
108. There is an identAndStatusSection
Publication Module (PM)
Example:
<pm>
<identAndStatusSection>
<pmAddress>... </pmAddress>
<pmStatus>...</pmStatus>
</identAndStatusSection>
<content>...</content>
</pm>
Example:
<pm>
<identAndStatusSection>
<pmAddress>... </pmAddress>
<pmStatus>...</pmStatus>
</identAndStatusSection>
<content>...</content>
</pm>
<pmAddress>
<pmIdent>
<identExtension>
<pmCode>
<language>
<issueInfo>
</pmIdent>
<pmAddressItems>
<issueDate>
<pmTitle>
</pmAddressItems>
</pmAddress>
With a <pmAddress>
115. <content>
<pmEntry>
<externalPubRef>
<externalPubRefIdent>
<externalPubCode pubCodingScheme ... </externalPubCode>
<externalPubTitle>...</externalPubTitle>
</externalPubRefIdent>
</externalPubRef>
...
In addition to referencing a data module, <dmRef> and/or another
publication module, <pmRef>, the <content> may also include a reference a
non-S10000D publication or document, <externalPubRef>.
Publication Module (PM)
116. Pub Updates and Version Control
• Updates of publications are due to updates in the data
modules that the publication module(PM) references,
or to the PM itself.
• The S1000D specification requires that the publication
module be reissued if there are any updates to the
publication.
• Updates can be either in the form of a change or a new
issue.
117. Pub Updates and Version Control
• A consecutive three digit number is issued to indicate every issue
of a PM. The initial issue of a publication must be numbered 001.
• An optional attribute can be used to number the drafts/revisions or
changes to the PM issue or a DM that is referenced in the PM. The
attribute is a two digit sequential number.
• A value of attribute type of the issueInfo, it describes the type of
update for a new issue of the publication module. It is related only to
the issue number.
119. Defining the Publication Module Code
Create a PMC that meets the following requirements:
This is publication number 16, the second volume of a three
volume documentation set for the Jeep Cherokee. The
issuing authority is Chrysler.
120. Publication Module (PM) <dmRef>
Complete the following XML to reference the data module:
DMC-S1000DLIGHTING-AAA-D00-00-00-00AA-056A-A_007-00_EN-US.xml
<dmRef>
<dmRefIdent>
<dmCode modelIdentCode="________" systemDiffCode="_____" systemCode="____"
subSystemCode="__" subSubSystemCode="__" assyCode=" ____" disassyCode=" ____"
disassyCodeVariant=" ____" infoCode="______" infoCodeVariant="__" itemLocationCode="__" />
<issueInfo issueNumber="______" inWork="____"/>
</dmRefIdent>
<dmRefAddressItems>
<dmTitle>
<techName>____________</techName>
<infoName>________________________</infoName>
</dmTitle>
</dmRefAddressItems>
</dmRef>
122. Data Interchange
S1000D provides standard ways to transfer data modules using an
S1000D CSDB interchange (transfer) package.
The transfer package consists of one Data Dispatch Note (DDN), and
at least one of the following data categories:
• one or more data modules, associated illustrations, multimedia and other data
• one or more CSDB Status List (CSL)
• one or more Data Module Requirement List (DMRL)
• one or more COMment forms (COM) and associated attachments
• one or more Publication Modules (PM)
123. S1000D provides standard ways to transfer data modules using an
S1000D CSDB interchange (transfer) package.
The transfer package consists of one Data Dispatch Note (DDN), and
at least one of the following data categories:
• one or more data modules, associated illustrations, multimedia and other data
• one or more CSDB Status List (CSL)
• one or more Data Module Requirement List (DMRL)
• one or more COMment forms (COM) and associated attachments
• one or more Publication Modules (PM)
Data Interchange
This is the actual data you want to
send—the DM(s), ICN(s) and/or
other data
124. S1000D provides standard ways to transfer data modules using an
S1000D CSDB interchange (transfer) package.
The transfer package consists of one Data Dispatch Note (DDN), and
at least one of the following data categories:
• one or more data modules, associated illustrations, multimedia and other data
• one or more CSDB Status List (CSL)
• one or more Data Module Requirement List (DMRL)
• one or more COMment forms (COM) and associated attachments
• one or more Publication Modules (PM)
To ensure that all CSDB are
built up without divergence, it
is recommended that each
agency/company produces and
exchanges a periodic reference
listing of all data modules that
it has issued for interchange.
Data Interchange
125. S1000D provides standard ways to transfer data modules using an
S1000D CSDB interchange (transfer) package.
The transfer package consists of one Data Dispatch Note (DDN), and
at least one of the following data categories:
• one or more data modules, associated illustrations, multimedia and other data
• one or more CSDB Status List (CSL)
• one or more Data Module Requirement List (DMRL)
• one or more COMment forms (COM) and associated attachments
• one or more Publication Modules (PM)
Data Interchange
The DMRL is used to
identify the required data
modules for a project.
126. Data Interchange
S1000D provides standard ways to transfer data modules using an
S1000D CSDB interchange (transfer) package.
The transfer package consists of one Data Dispatch Note (DDN), and
at least one of the following data categories:
• one or more data modules, associated illustrations, multimedia and other data
• one or more CSDB Status List (CSL)
• one or more Data Module Requirement List (DMRL)
• one or more COMment forms (COM) and associated attachments
• one or more Publication Modules (PM)
Contains comments and reports on issues raised on data
modules or publication modules during the
verification process and the in-service phase of the Product
127. S1000D provides standard ways to transfer data modules using an
S1000D CSDB interchange (transfer) package.
The transfer package consists of one Data Dispatch Note (DDN), and
at least one of the following data categories:
• one or more data modules, associated illustrations, multimedia and other data
• one or more CSDB Status List (CSL)
• one or more Data Module Requirement List (DMRL)
• one or more COMment forms (COM) and associated attachments
• one or more Publication Modules (PM)
Data Interchange
(I hope this one is obvious)
128. Data Dispatch Note
The DDN defines the sender, receiver and content of the
dispatch.
A data delivery list (DDL) is optionally included in the
DDN. This lists all file names of the dispatched data together
with their control numbers and issue numbers as additional
options.
129. Data Dispatch Note
MI-SSSSS-RRRRR-YYYY-
NNNNN
Model Identifier
Sender NCAGE
Receiver NCAGE
Year
Sequential number
per year
The DDN defines the sender, receiver and content of the
dispatch.
The DDN is identified by a CONTROLNUMBER in the format:
130. Data Dispatch Note
For example:
MI-SSSSS-RRRRR-YYYY-
NNNNN
Model Identifier
Sender NCAGE
Receiver NCAGE
Year
DDN-S1000DBIKE-U8025-I9005-2003-00002.XML
seqNumber Contains a sequence number of the comment, related to
senderIdent and yearOfDateIssue
modelIdentCode Identifies the Product to which the data applies
senderIdent Contains the CAGE code of the sender of the comment
receiverIdent Contains the CAGE code of the receiver of the comment
yearOfDateIssue Contains the year (YYYY) when the issue was made public
Sequential number
per year
132. Data Dispatch Note
<ddnCode senderIdent="______________"
yearOfDataIssue="_____________"
modelIdentCode="___________"
receiverIdent="___________"
seqNumber="_____________" />
DDN-S1000DBIKE-U8025-I9005-2003-00002.XML
Use the sample DDN for this exercise and fill in the blanks below.
134. Business Rules
The S1000D spec outlines requirements for business rules as a
foundation for each project to maintain consistency across the
departments and individuals who are part of the project.
Business rules are decisions that are made by a project or an
organization on how to implement S1000D. Business rules
cover all aspects of S1000D and are not limited to authoring or
illustrating.
They can also address issues that are not defined in S1000D
such as rules related to how S1000D interfaces with other
standards, specifications and business processes that are
related to its implementation.
Refer to Chap 2.5 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
135. Business Rules
Throughout the specification, in particular the authoring chapters,
business rule decision points have, wherever possible, been
identified.
However, in many cases, they have been marked as "None
identified".
Projects and organizations must still decide for themselves
whether certain business rules decisions must be made in these
cases.
Refer to Chap 2.5 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
136. Ten different business rule categories have been identified.
These categories are defined to ensure that business rules
developers consider all major business rules decisions within
S1000D.
Business Rules
Refer to Chap 2.5, page 3 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
137. Business Rules
Refer to Chap 2.5, page 3 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
Ten different business rule categories have been identified.
138. Business Rules
Refer to Chap 2.5, page 3 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
Business rule category 1: General serve as overall
decisions (business rules) for the implementation of
S1000D
Ten different business rule categories have been identified.
139. Business Rules
Refer to Chap 2.5, page 4 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
Business rule category 2: Product definition covers
the data module coding strategy related to how the
Product is broken down (eg physical or functional).
Ten different business rule categories have been identified.
140. Business Rules
Refer to Chap 2.5, page 4 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
Business rule category 3: Maintenance
philosophy and concepts of operation
cover the types of information that a
project or an organization requires.
Ten different business rule categories have been identified.
141. Business Rules
Refer to Chap 2.5, page 5 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
Business rule category 4: Security
covers all security issues. They include
security classifications, copyright
markings, use or disclosure restrictions,
destruction instructions and any other
data restrictions.
Ten different business rule categories have been identified.
142. Business Rules
Refer to Chap 2.5, page 6 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
Business rule category 5: Business process
cover how technical publications development is
coordinated with other disciplines within an organization
or within the project level at that organization or the
project as a whole.
Ten different business rule categories have been identified.
143. Business Rules
Refer to Chap 2.5, page 7 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
Business rule category 6: Data creation
gives information about the creation of text, illustrations
and multimedia objects. The data creation business rules
include rules for creating textual data and rules for
creating graphics, 3D content and multimedia objects
Ten different business rule categories have been identified.
144. Business Rules
Refer to Chap 2.5, page 8 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
Business rule category 7: Data exchange
Covers the rules for how data must be exchanged
between partners and customers. This includes for
example the use of data dispatch notes and how
data module requirement lists as well as CSDB status
lists are used.
Ten different business rule categories have been identified.
145. Business Rules
Refer to Chap 2.5, page 9 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
Ten different business rule categories have been identified.
Business rule category 8: Data integrity and management
enforce the referential integrity within the CSDB.
Closely coupled with the data exchange business rules, they
cover how data is managed by both the creator and the customer
146. Business Rules
Refer to Chap 2.5, page 9 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
Ten different business rule categories have been identified.
Business rule category 9: Legacy data
conversion, management and handling
include but are not limited to:
− conversion rules (including mapping
between elements and attributes of source
and target specifications)
− rules for inclusion of legacy information in
a technical publication
147. Business Rules
Refer to Chap 2.5, page 10 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
Ten different business rule categories have been identified.
Business rule category 10: Data output
specify the output formats for S1000D data.
These formats can include page-oriented (eg
paper) formats, IETP formats, multimedia
formats and SCORM Formats.
148. Business Rules
The top level of the business
rules (S1000D BR) are those
developed and defined in the
S1000D spec.
The layers under, are in a
hierarchy whereby “the
business rules in the lower
("children") layers must adopt
or must be conformant to the
business rules of the higher
(their "parent") layer.”
Refer to Chap 2.5.1 pgs 13 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
149. Business Rules
As a minimum requirement,
the higher layers are
responsible for informing the
lower layers on their business
rules.
For example, organizations
must provide information to
projects, which organizational
business rules must be
followed and which decision
points are up to the projects.
Refer to Chap 2.5.1 pgs 12-14 in S1000D International specification for technical publications, Issue 4.0, 2008-08-01
150. Example Business Rules Conflicts
“Problems can occur in the project
layers when the same Product is
used in different projects.
Consider an engine that is used in
different airframes where one
airframe manufacturer imposes
different rules than another.
Another example is when a given
Product is used for both civil and
military use, which can mean data
rewrites.”
Engine A
Airframe A
Airframe B
Airframe C
151. Example Business Rules Conflicts
Business Rules AFM C
Use 2.3 DTD
Do not use <techstd>
Titles in uppercase
...
Business Rules AFM B
Use 1.9 DTD
<techstd> is to contain.....
Illustrate as CG4
Use OxfordEnglish
Business Rules AFM A
Use 1.8 DTD
Do not use <techstd>
Do not use step leve 4-5
Illustrate as CGM
Use Webster’s English
Engine A
Airframe
A
Airframe
B
Airframe
C
152. “Before any authoring or implementation
of S1000D begins on a project, all
stakeholders who have their own business
rules must reach consensus on the
business rules to be deployed for that
project.”
Example Business Rules Conflicts
Business Rules AFM C
Use 2.3 DTD
Do not use <techstd>
Titles in uppercase
...
Business Rules AFM B
Use 1.9 DTD
<techstd> is to
contain.....
Illustrate as CG4
Use OxfordEnglish
Business Rules AFM A
Use 1.8 DTD
Do not use <techstd>
Do not use step leve 4-5
Illustrate as CGM
Use Webster’s English
153. “When projects are presented with
conflicting business rules from multiple
customers or parent organizations,
projects must resolve these conflicts.
These conflicts must be resolved by:
• coordinating a change or waiver to the
conflicting rules with one or more of the
customers or parent organizations
• producing data modules to comply
with each set of rules.”
Example Business Rules Conflicts
Business Rules AFM C
Use 2.3 DTD
Do not use <techstd>
Titles in uppercase
...
Business Rules AFM B
Use 1.9 DTD
<techstd> is to
contain.....
Illustrate as CG4
Use OxfordEnglish
Business Rules AFM A
Use 1.8 DTD
Do not use <techstd>
Do not use step leve 4-5
Illustrate as CGM
Use Webster’s English
154. Business Rules (BREX)
Business Rules EXchange mechanism (BREX) is a means
to communicate the business rules that have been
developed and agreed upon within a project.
To facilitate unambiguous description of the business rules,
a BREX data module can be used and is stored in the
CSDB.
156. Business Rules (BREX)
snsCode for system is 05
Subsystem for:
general aircraft is 0
standard practices, airframe is 1
ground handling is 2
safety and protectice devices is 3
A copy of the Issue 4.0 spec is available at:
http://public.s1000d.org/Downloads/Pages/S1000DDownloads.aspx
Note that information contained in this training is relevant to specification 4.0.1. Differences in previous versions can be noted in the Highlights section at the beginning of the specification for each release.
A most significant difference in version 4.0 from previous versions is the change in the XML markup (element tags).
A copy of the Aerospace Industries Association recommendation (white paper) is available at:
http://ww.adlnet.org/About/JPTC/Shared%20Documents/AIA%20S1000D%20Recommendations%20White%20Paper%20-%20Final.pdf
The Data Modules themselves (each containing a specific knowledge domain) define the discrete data items (marked with XML), allowing individual items to be changed without affecting the surrounding content
System 12 indicates Servicing. (Chapter 8.2.3 pages 2-3)
Subsystem and Sub-subsystem 10 indicates instructions necessary for the replenishment or depletion of fluids. (Chapter 8.2.3 page 9 – note that for a system code of 12, the subsystem code 10 indicates replenishing and depleting.)
Unit/Assembly 00 indicates no specific unit or assembly, refer to as the whole.
DC (disassembly code) 00 and DCV (disassembly code variant) 00 indicates that this module does not pertain to assembly/disassembly; not applicable to the data.
IC (information code) 200 specifies that the data pertains to servicing. (Chapter 8.4 page 2)
ICV (information code variant) 0 indicates that there is no variation; not applicable to the data.
ILC (item location code) A indicates that this procedure pertains to items installed on the product. (Chapter 4.3.8 page 2).
These examples are from the S1000D International specification, Chap 3.9.2.1 page 17 and page 20.
From the S1000D specification: Chapter 4.4. page 3
Technical conditions are typically tied to the configuration of the Product, such as service bulletins or modifications. The state of technical conditions can change throughout the service life of a product instance.
Examples of operational and environmental conditions are location of maintenance, availability of tools, regulatory rules, temperature, wind speed and sandy conditions.
Refer to the S1000D Specification, Chapter 8.4.1, page 6 to see the infoCode.
Sample Cross Reference Table:
In the context of a data module, the markup to test for Mountain storm Mk1 or Brook trekker Mk would look like what is shown above.
This tests for a Mountain bicycle which is either Mountain storm Mk1 or Brook trekker Mk9.
Mountain bicycle is either Mountain storm Mk1 or Brook trekker Mk9
Refer to the S1000D Specification, Chapter 7.8 Section 4.2 on pages 7-10.
Note that the textual assert annotation contains no computable components. Since it is not computable the result is a Boolean value of true.
Refer to the S1000D Specification, Chapter 7.8 Section 4.2 on pages 7-10.
Note that the textual assert annotation contains no computable components. Since it is not computable the result is a Boolean value of true.
For example, assume:
Pub A contains information that is used as the introduction section of the publication. It includes DMs that may have (for example) an overview of the company, customer service contact information, how to apply register the product, etc. and can be used in multiple publications.
Pub B comprises Section 1 of this publication. It contains a reference to Chapter 1 which is contained in Pub C. It also references additional information contained in some of the other DMs.
You can have several publications referencing the same PMs (such as our sample introduction section which may be used in all publications from this manufacturer) or it may reference the same DMs that other PMs reference.
In this case, the first publication and the second publication use the same Pub A (PM) and share some of the DMs but not all of them.
The two publications share all of the DMs that are in Pub A and two of the DMs.
In addition, the second publication references some legacy data.
From the spec:
When work first starts on a data module, the issue number is set to the value &quot;000&quot;, using the attribute issno, the attribute type is set to the value &quot;new&quot; and attribute inwork is set to the value &quot;01&quot;. Then, when the data module is released, the attribute inwork is reset to the value &quot;00&quot;, and the issue number incremented to indicate approved release of that instance of the data module. From issue &quot;002&quot; onwards the attribute type must not be set to the value &quot;new&quot; but is to reflect the release status of the instance of the data module.
Refer to the S1000D Specification Chap 4.5.2 for information about the CSBD Status List.
“...the CSDB at the originating agency/company is the definitive source of data modules for which that agency/company has responsibility.”
Refer to the S1000D Specification, Chapter 4.6 for more information about the comment form.
“This form is compiled by the commenting authority and sent to the issuing authority of the data modules or publication modules. The comment form is also used to provide a response to the originator of the comment. The commenting process is explained in Chap 3.7.”
Refer to the S1000D Specification, Chapter 4.6 for more information about the comment form.
“This form is compiled by the commenting authority and sent to the issuing authority of the data modules or publication modules. The comment form is also used to provide a response to the originator of the comment. The commenting process is explained in Chap 3.7.”
Chap 4.6 pg 13
Example from the S1000D Specification, chapter 2.5.1 page 15
We have sample BREX from USAF – part of it shown in this slide. The file in on your workstation. Open the BREX (in notepad or wordpad) to read the contents and become familiar with a BREX.