S1000D History In the early 1980s, the concept of S1000D specification originated in the aerospace field within Aerospace and Defence Industries Association of Europe (ASD). Earlier in Europe various national specifications were used in technical documentation, this made data exchange between countries more difficult. During this same period, civil aviation was successfully using ATA S100 specification to deliver and exchange information internationally. The Aerospace and Defence Industries Association of Europe (ASD) had developed the S1000D specification, originated from the Air Transport Association (ATA) S100. From then on it emerged as a widely adopted standard in Europe by military projects. S1000D also known as ASD S1000D is an international specification for the procurement and production of technical publications based on XML (extensible Mark-up Language), utilizing a Common Source Database. This specification offers a structured procedure regarding organization, processes, and management in the process of technical documentation and their publishing’s. It has become widely utilized and highly regarded across various sectors, and a good choice for documenting complex equipment with long life cycles such as defence, civil aviation, space, shipping, nuclear, automotive, rail and manufacturing. Finely tuned structures in this specification can also support sophisticated military and civil project life cycles. The S1000D specification is now supported by the successor to AECMA, the Aerospace and Defence Industries of Europe (ASD), the Aerospace Industries Association of America (AIA) and the Air Transport Association (ATA). The specification is controlled by an international body, the S1000D Steering Committee (SC), which is responsible for maintaining it and includes members from both government agencies and industry. To address the rapid development of information technology, the SC is supported by a group of specialists known as the Electronic Publications Working Group (EPWG). S1000D covers the planning, management, production, exchange, distribution and use of technical documentation that support the life cycle of any civil or military projects that include air, land and sea vehicles. Business Rules Business rules are major because they determine the implementation and processes to ensure consistent and complete content. These are decisions created by a project or an organization on how to implement S1000D. S1000D business rules are documented based on project and/or organizational requirements, and these determine and constrain all elements of a technical publication or the project. S1000D also specifically defines Business Rules Decision Points (BRDPs). Business Rules Decision Points help us to create instructions and guidelines that affect authoring, presentation and distribution of publication for a project. Business rules written in computer language are stored in the BREX document. That BREX data module is then referenced inside each data module, hence the software and applications can validate that data module’s content to the referenced BREX. S1000D now contains business rules categories. Combining your business rules into these business rules categories helps you with scope and normalization. The 11 business rules categories of S1000D are listed below: 1. General Business Rules General rules cover overall decisions made by a project or an organization that are not covered by any of specific business rule categories. They serve as overall decisions for the implementation of S1000D. These include 2. Product Definition Business Rules Product definition business rules covers the data module coding strategy as to how the product is broken down either physical or functional. Including the model identification codes down subsystem level, supplier subsystems, applicability and identifications also need to be considered. 3. Maintenance Philosophy and Concepts of Operation Business Rules These rules cover 4. Security Business Rules Following are the business rules are included 5. Business Process Business Rules Business process business rules cover the interaction with other disciplines into Technical Publications in an organisation, project level of organisation or project as a whole, agreed workflow procedures between manufacturer, subcontractor and customer and reuse of content across systems including training environment. Rules to be considered in preparing a strategy for data module coding are 6. Data Creation Business Rules Data creation business rules give information about the creation of text, illustrations and multimedia objects. The data creation business rules include: (a). Data Creation Business Rules – Text Text creation business rules consist of rules and guidelines (including terminology rules such as language and dictionaries, and the order of preference) for maximizing the amount of reuse that can be achieved within technical publications, and between technical publications and supporting training content. Text creation business rules provide rules and guidance how the technical and learning content is to be developed. They also specify eg the use of dictionaries, how numbers must be expressed, how the author must refer to technical terms, how multimedia, maintenance, operational and learning content is to support IETP and training, and the establishment and use of a terminology database. Markup business rules provide information about which markup elements and attributes must be used and populated. These rules are often project or organization specific. 6(b). Data Creation Business Rules – Illustrations and Multimedia Illustration and multimedia creation business rules cover the creation of illustrations and multimedia objects. They are divided into style, detail and data format. Data style rules for illustrations and multimedia objects govern characteristics such as illustration sizes, use of color, line weights, fonts, projection methods (isometric or trimetric), etc. The rules for illustrations cover for example the use of hotspots. Data format rules cover the formats in which the information must be stored. For a CGM illustration, this will cover the elements that are permitted (eg coordinate types, polylines, restricted text). For raster images it can include the resolution and orientation. It is often difficult to separate style from format. 7. Data Exchange Business Rules This data exchange business rules includes rules for usage of Data Dispatch Note (DDN), Data Module Requirements List (DMRL), Data Module List (DML), CSDB status lists, File based transfer protocol, Data exchange frequency. Rules for data module issue numbers and agreed criteria for acceptance and rejection between partners and customers. Acceptance and rejection are based on agreed criteria. 8. Data Integrity and Management Business Rules These business rules enforce the referential integrity within