DI-TMSS-81784A

Army S1000D Project Business Rules

Documents project-specific business rules for the preparation of technical publications in conformance with S1000D, per MIL-STD-3031, for the acquisition of military technical data.

Approval DateApril 19, 2011

AMSC Number9189

Preparing Activity—

Project Number—

OPRTM

DTIC ApplicableNo

GIDEP ApplicableNo

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatdd_form_1664

963C CompliantNo

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

This Data Item Description (DID) and MIL-STD-3031 shall be used to document project-specific business rules for the preparation of technical publications in conformance with S1000D. This DID and Appendix C of MIL-STD-3031 contain the format, content, and intended use information for the data product resulting from the work task described, and is applicable to the acquisition of military technical data.

Preparation Instructions

1Reference documentsThe applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as cited in accordance with the Acquisition Streamlining and Standardization Information System (ASSIST) database (at http://assist.daps.dla.mil/) at the time of the solicitation; or, for unlisted documents, as stated herein.

2FormatThe Army S1000D Project Business Rules shall be in the contractor's format of choice, with the exception of Appendix A which shall be consistent with the table provided in Appendix C of MIL-STD-3031.

3ContentThe Army S1000D Project Business Rules shall include:

3.1CoverA front cover sheet shall include the contract's name and address, the contract number, the nomenclature of the system or program, the date of the project business rules document, the security classification, and the name of the issuing Government activity.

3.2IntroductionThe introduction shall be a brief description of the program that includes estimated milestone dates related to technical data, high-level technical data functionality (paper or Interactive Electronic Technical Publication (IETP), the use of the process data module, etc.), and any other significant information helpful in describing the product and its technical data and use.

3.3Paragraphs 1 through 7 shall include additional narrativeParagraphs 1 through 7 shall include additional narrative descriptions for the project decisions provided below. These project decisions require narrative descriptions that are typically not suitable for Appendix A.

3.3.1Definitions of information setsThe project shall decide which information sets are to be used and the definition of their content (from S1000D Chapter 3.3 - Information generation - Information sets). This shall include a list of those information sets from Appendix A of MIL-STD-3031, the completed functionality matrix, and the corresponding completed content selection matrices that have been selected for development by the project.

3.3.2Project-specific information setsThe project shall define all project-specific information sets (from S1000D Chapter 3.3 - Information generation - Information sets). All project-unique information sets not described in Appendix A of MIL-STD-3031 shall be described here.

3.3.3General identification of access pointsThe project shall determine the identification system for those access points that do not have identifiers (from S1000D Chapter 3.4 - Information generation - Zoning and access). This shall include a description of how zoning and access is defined for the product, including any exceptions resulting from peculiarities of the product. The description shall refer to drawings that specifically map out zones and access points.

3.3.4Checklist categoriesThe project shall decide if business rules need to be created for which Extensible Markup Language (XML) elements to use and how to markup checklists for each category type (from S1000D Chapter 3.9.5.2.14 - Maintenance Checklists and Inspections). This shall list the project-unique checklists and the necessary business rules that define how to produce those checklists.

3.3.5ApplicabilityThis shall include whether and how data module and content applicability will be used, definitions of filtering criteria, and methods for determining correct filtered data to display. This scope of this paragraph shall include but not be limited by the following project decisions:

3.3.5.1Applicability (general)The project shall determine the use of applicability and describe that desired approach in the business rules (from S1000D Chapter 3.9.5.3 - Data modules - Applicability).

3.3.5.2Applicability (Quality Assurance)The project shall decide if it is permitted to differentiate quality assurance information depending on product configuration (from S1000D Chapter 3.7 - Information generation - Quality assurance).

3.3.5.3Applicability (Identification and status section)The project shall decide on how applicability is to be used. The project shall decide on the population of the elements and attributes of applicability and shall then enforce its consistency (from S1000D Chapter 3.9.5.1 - Data modules - Identification and status section).

3.3.5.4Applicability (Descriptive information)The project shall decide how to use the element <applic> in the content section of the description (from S1000D Chapter 3.9.5.2.2 - Content section - Descriptive information).

3.3.6Documentation of Standard Numbering System (SNS)This shall include complete documentation defining the project SNS. If the S1000D-maintained SNS is used, list each required table (e.g., System L - Electronic system - General). The scope of this paragraph shall include but not be limited to the following project decisions:

3.3.6.1The SNS shall be documented in theThe SNS shall be documented in the project business rules and included in the Business Rules Exchange (BREX) data module to the extent possible (from S1000D Chapter 4.3.3 - Data module code - Standard numbering system).

3.3.6.2Documentation of SNS and technical namesThe project shall compile a list which defines the SNS and all technical names (from S1000D Chapter 4.3.3 - Data module code - Standard numbering system).

3.3.6.3Sub-subsystem SNS allocationsThe project shall determine the sub-subsystem SNS allocations (from S1000D Chapter 4.3.3 - Data module code - Standard numbering system).

3.3.7Process data moduleThe project shall determine the use of the process data module and describe that desired approach in the business rules (from S1000D Chapter 4.11 - Information management - Process data module). It shall describe whether and how the process data module will be used, including interactive strategy and all necessary rules governing the production, display, and use of interactive data.

3.4Paragraphs 8 through XAdditional project business rules requiring narrative description. These shall include, in S1000D-chapter order, all narrative descriptions related to the project business rules not included in paragraphs 1 through 7 above.

3.5Appendix AThe project decision matrix. The matrix shall include project-specific business rules for all project decision points identified in Appendix C of MIL-STD-3031.

3.6The Army S1000D Project Business Rules shall notThe Army S1000D Project Business Rules shall not include guidance, tutorials, training, or repetition of business rules that are provided in S1000D or MIL-STD-3031.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer