About Implementation Periods

Several properties define implementation periods based on the document type and the organization.

When defining an implementation period for a controlled document, you can define a default for each organization, and a default for each document type for each organization. The default implementation period is used in cases where a specific property for the combination of document type and your organization is not defined, or if someone created a new document type (or subtype), but did not add an equivalent property to the emxDocumentChangeControl.properties page object.

The format for these properties is: 

CONTROLLED_DOCUMENTS.<ResponsibleOrganizationName>.ImplementationPeriod = n
<DocumentType>.<ResponsibleOrganizationName>.ImplementationPeriod = n

where:

  • <ResponsibleOrganizationName> is an organization name.
  • <DocumentType> is the name of a document type and must be a valid administration type that is a child of CONTROLLED_DOCUMENTS.
  • n is an integer number of days.

In the schema, CONTROLLED_DOCUMENTS is an abstract type. You cannot create an object of type CONTROLLED_DOCUMENTS, but you can create an object based on one of its subtypes. The implementation period for the parent (CONTROLLED_DOCUMENTS) is inherited by its child types unless the child type has a specific property defined for it.

For example, if you have these organizations defined:

  • BusinessUnit1
  • BusinessUnit2
  • BusinessUnit3

and you have these types of CONTROLLED_DOCUMENTS in use:

  • Quality System Document
  • Process Document
  • Quality System Manual

then you could define these properties:

CONTROLLED_DOCUMENTS.BusinessUnit1.ImplementationPeriod = 20
Quality_System_Document.BusinessUnit1.ImplementationPeriod = 10
Process_Document.BusinessUnit1.ImplementationPeriod = 15
Quality_System_Manual.BusinessUnit1.ImplementationPeriod = 15

CONTROLLED_DOCUMENTS.BusinessUnit2.ImplementationPeriod = 15
Quality_System_Document.BusinessUnit2.ImplementationPeriod = 10
Process_Document.BusinessUnit2.ImplementationPeriod = 10
Quality_System_Manual.BusinessUnit2.ImplementationPeriod = 10

CONTROLLED_DOCUMENTS.BusinessUnit3.ImplementationPeriod = 15

If someone from BusinessUnit2 creates a process document, then the implementation period for that document is 10 days. BusinessUnit3 does not have any specific document types defined, so all document types have an implementation period of 15 days.

When effectivity is defined for a change order, the Change Order Configurator can override these properties by specifying a different implementation period or by defining a specific implementation date.