Additional Windchill Capabilities > Service Information Management > About > S1000D Object Initialization Rules (OIR) Administration > Content Holder (Part)- and S1000D Content (EPM Document)-based OIRs
  
Content Holder (Part)- and S1000D Content (EPM Document)-based OIRs
The includes two types of content object:
Content Holders, which are used to maintain a place in the structures
Content Holders are soft types of Part
Content objects, which manage XML content and associated images
Content objects are soft types of Dynamic Document
This is consistent with Windchill Service Information Manager.
Windchill and Windchill Service Information Manager both provide OIRs. It is essential to understand OIR inheritance, influenced both by class hierarchy and container context hierarchy, to anticipate the impacts on the of OIRs targeting these parent types.
For more information, see How Object Initialization Rules Work.
The Content Holder OIRs are all used to manage the XML content and images associated with an S1000D product. Limited customization is supported.
Load files:
\loadFiles\sisaad\S1000D\oirs\datamodule.xml
\loadFiles\sisaad\S1000D\oirs\ddn.xml
\loadFiles\sisaad\S1000D\oirs\dml.xml
\loadFiles\sisaad\S1000D\oirs\informationControlNumberCageBased.xml
\loadFiles\sisaad\S1000D\oirs\informationControlNumberModelBased.xml
\loadFiles\sisaad\S1000D\oirs\pm.xml
\loadFiles\sisaad\S1000D\oirs\brdoc.xml
\loadFiles\sisaad\S1000D\oirs\icnMetadata.xml
Attributes:
Attribute
Description
Can be customized?
Notes
folder.id
Defines the folder path for the object
Yes
This value can be changed to any desired folder.
* 
PTC recommends that the content’s object type (for example sis.s1000D.datamoduleType and the content holder’s object type (for example sis.s1000D.4.1.datamodule) use the same folder path.
MBA|versionInfo
Sets the versioning scheme
The version scheme for S1000D is wt.series.HarvardSeries.S1000D
Yes, with caution
This can be customized to a customer-specific scheme. Care must be taken when setting up custom versioning scheme.
For information on how to set up a versioning scheme, see Object Versioning.
name
Specifies the name of the object
Yes
The naming is flexible, with the option to apply suffixes and prefixes to the data module’s name
* 
It is important that the content’s object type (for example sis.s1000D.datamoduleType and the content holder’s object type (for example sis.s1000D.4.1.datamodule) use the same naming convention and that the names of the content holder and the content are identical.
number
Provides a number that is unique throughout the system, and is used to enforce uniqueness throughout all S1000D products
Yes, with caution
number uses a highly customized algorithm that creates a unique key for each data module in a product.
* 
Take care when making changes to the attribute, with consideration for retaining uniqueness both in the S1000D context and across the entire system.
responsiblePartnerCompany
originator
Provides the default value used when either Arbortext Editor’s burst operation or Windchill’s Insert New Document wizard operation fails to supply a value for these required attributes.
Yes
The value must match a manufacturer, at a locked state, in the look up library structure within the S1000D product
securityClassification
Provides the default security classification identified for the content holder or content. Typically, this will be populated by Windchill’s Insert New Document wizard
Yes
You may wish to elevate this to a higher security in projects where templates need to be identified as more secure by default.
techName
By default, techName is set to General – General, and is populated by Windchill’s Insert New Document wizard.
Yes
It could be helpful to change this value to assist users creating templates from scratch
infoCodeName
By default, infoCodeName is set to General data, and is populated by Windchill’s Insert New Document wizard.
Yes
It could be helpful to change this value to assist users creating templates from scratch.
lifeCycle.id
Specifies the life cycle template to be used
Yes, with caution
The introduces an advanced life cycle, with multiple workflows.
* 
PTC strongly advises against the introduction of a customized life cycle.
Consider introducing a customized workflow instead of an entirely new life cycle. If a new life cycle must be introduced (for example to introduce a new life cycle state), the changes must be made in both the content holder and content life cycles.
issueYear
issueMonth
issueDay
The Issue date algorithm is well established and uses an algorithm to retrieve the date and time on which a data module was created.
Issue date is updated when the data module is Issued in the data module workflow.
No
issueType
The issue type is initialized to new when the object is created. This is then inserted into the XML contet of a data module when the data module is created.
No
docType
This is initialized as PUB_COMPOUNDTEXT.
No
authoringApplication
Specifies the application to be used to author content. This is initialized as ARBORTEXT.
No
Not available for customization unless a part of a larger UWGM customization.
state.state
The life cycle defines the valid set of states and, for S1000D, there are different states that may be valid when the object is created or imported:
Initializes to Released if the data module is a template
Initializes to Imported when the document is imported from a compressed file
Initializes to WIP if the data module is not a template and has an In Work value greater than 0
Initializes to Issued if the data module is not a template and has an In Work value of 0
Yes, with caution
Caution should be taken if customizing this attribute. You could remove the Imported state, but this may cause the import to become quite slow.
State customization is commonly part of a larger life cycle customization. PTC strongly warns against introduction of a customized life cycle or state customizations. You should consider introducing a customized workflow instead of an entirely new life cycle or, possibly, tailoring the name displayed for an existing state.
seqNumberVar
Queries for all previous Data Dispatch Note (DDN) documents, finds the next available sequence, and resets it to 00000 if the DDN is the first DDN to be created in that year
No
The S1000D standard mandates the sequence rule.
uniqueIdentifier
Generates a unique identifier sequence within the product
The algorithm can be manipulated by the end user in the product’s Edit Attributes wizard — they can change various attributes to control the algorithms output.
No
Although the algorithm is highly customizable, PTC strongly advises against customization. The current algorithm adheres to the S1000D standard.
issueNumber
Sets the Issue Number for an ICN
Initializes to 001 if a ICN is created without any predecessors
If creating a new issue of the ICN, this value will be populated by the ICN’s Raise Issue operation. It will be an incremented value from its predecessor.
Yes
responsiblePartnerCompanyCode
This value is initialized from a Product container default
Yes
A user is also free to change this default value in the Product’s Edit Attribute wizard.
These attributes algorithm are not supported for customization under any circumstances:
modelIdentCode
systemDiffCode
systemCode
subSystemCode
subSubSystemCode
assyCode
disassyCode
disassyCodeVariant
itemLocationCode
infoCodeVariant
brexModelIdentCode
brexSystemDiffCode
brexSystemCode
brexSubSystemCode
brexSubSubSystemCode
brexAssyCode
brexDisassyCode
brexDisassyCodeVariant
brexInfoCode
brexInfoCodeVariant
brexItemLocationCode
brexDatamodule
This creates a value used when a Business Rule Exchange (BREX) data module refers to itself (in a circular fashion). This ensures an empty value is not specified and helps the code processing the BREX to determine the circular nature of the BREX being loaded.
Custom instance- based attributes can also be added.