The Document package collects the elements needed to support records that are one or more electronic "bit streams". Each bit stream is represented by a Document. The DispositionInstruction is used as an "action template" to form DispositionPlan's with one or more RecordSet's in which to accumulate and manage the ManagedRecords. DispositionInstruction's can change for a RecordCategory. The history is kept by the previous/next association. The current one is the latest entered that has an expired effectiveDate. (It is possible to change a DispositionInstruction effective on so-and-so date, in which case it would be entered here with a future effectiveDate.) Changing the effectiveDate requires a new DispositionInstruction. The date/time that the DispositionInstruction was approved by the dispositionAuthority. The RecordCategory associated with the DispositionInstruction. The date/time that the DispositionInstruction was created. The creator of the DispositionInstruction Text description of the DispositionInstruction The Authority that approved the DispositionInstruction. The effective date/time of the DispositionInstruction. Unique Identifier A next DispositionInstructioin The DispositionPlan for the RecordSet(s) based on the DispositionInstruction. A previous DispositionInstruction. A RecordCategory must have a valid DispositionInstruction however in some situations ManagedRecords are being set-aside and there is no approved record schedule. In this circumstance the DispositionInstruction is DispositionTBD which is an "actionless" instruction. This allows a DispositionPlan to be created to collect the ManagedRecords into RecordSet's to "wait" for an approved DispositionInstruction with a DispositionActionSequence. Under these circumstances there will not be any DispositionAction's accumulated under a DispositionPlan. The specification of a sequence of actions to be used as a template for DispositionPlan's. An DispositionActionSequence has at least three ActionSpecification's beginning with a Cutoff followed by a Retain. Optionally there can be any number of pairs of Move/Retain actions. The final action in a sequence is either a Transfer or Destroy action. The DispositionInstruction that aggregates the ActionSpecifications that constitute its definition. An event conformant with an ActionEventSpecification that triggers a DispositionAction in a DispositionPlan. Text description of the ActionEvent. The date/time that an ActionEvent occurred. The event specification. The DispositionActions triggered by the ActionEvent. ActionSpecification's are the only possible actions that can be performed on a RecordSet. Each is triggered by an event specified by an ActionEventSpecification. A DispositionAction based on the ActionSpecification The ActionEventSpecifications (triggers) that can actuate this DispositionActions based on this ActionSpecification Cutoff is like a start node in a process specification for actions on a RecordSet. It is most often triggered by a PeriodicEvent, but no matter what triggers it, the action goes immediately to whatever the next step in the process is, i.e., there is no "duration" to the action. (It is in a real sense an "event" in it's own right). An action that the RecordSet is to be retained as is for the specified Retain.duration. The work Hold is often used as synonymous with Retain. The duration for which a RecordSet is to be retained before further action. A move is not a record transfer. It is the change of control to another location without transfer of legal custody. All the metadata stays with RECORDS MANAGEMENT ENVIRONMENT of the legal custodian. Location of the record has been changed but the legal custody of the record emains the same. If a record is in a Move action it's still part of the disposition. Location concepts in RMS are not to be thought of as managing a record's physical location in a server farm, for example. Location is a logical concept, not a physical one. The logical destination (Organization) of the Move action. The expected duration of the Move action for the RecordSet. This is used for projection of workload & may be updated from time to time to improve the estimate. Legal custody of Record moves from the current organization of provenance to another. At the end of the operation the ManagedRecord would normally be removed from the Records Management Environment. (A transfer certificate might be kept, but that would be another ManagedRecord) Location concepts in RMS are not to be thought of as specifying a record's physical location in a server farm, for example. Location is a logical concept, not a physical one and refers to an Organization. The destination Organization of the Transfer action. The expected duration of the Transfer action for the RecordSet. This is used for projection of workload & may be updated from time to time to improve the estimate. This ActionSpecification is one of the "final actions" to be taken against the ManagedRecords in a RecordSet. The ManagedRecords (and their Documents and associated metadata not shared with other ManagedRecords) are destroyed. The expected duration of the Destroy action. This is used for projection of workload & may be updated from time to time to improve the estimate. Used to build DispositionInstruction's which consist of ActionSpecification's whose triggering events must be specified. This is the specification of the events that can be or are used in an ActionSpecification. The ActionSpecification for which an ActionEventSpecifications (trigger specifications) is associated. A text description of the ActionEventSpecification The specified event. Unique identifier. The name of the ActionEventSpecification A periodic event, e.g., year-end, school-year-end, month-end. The instances of this can be numerous and often dependent on the organization (e.g., school-year-end, fiscal-year-end), therefore no attempt to enumerate the possibilities is made. The PeriodicEvent.period must be a string that is interpretable to a system in order to make the DispositionAction.estimatedStartDate's for Cutoff, etc. A string representing the event period (e.g., calendar-year-end, fiscal-year-end, month-end, etc.) An event that is defined in terms of a specific date/time. The date/time at which the event is occurs and triggers whatever appropriate DispositionAction's. An event that is specific to the Records Management Environment deployment, but is not generated (or even necessarily anticipated) by the Environment itself. The event of completion of a specific DispositionAction. The DispositionAction that has ended. The DispositionPlan is an "instantiation" of the DispositionInstruction applied to a particular RecordSet as defined by a Cutoff action. It aggregates DispositionAction's that are similarly derived from ActionSpecification's. The creation date/time of the DispositionPlan. In many cases this is the same as the cutoffDate of the "previous" RecordSet, however DispositionPlan's may be established ahead of time in anticipation of the Cutoff event. A RecordSet subject to the DispositionPlan The DispositionInstruction that served as the specification for the DispositionPlan The DispositionPlan of which the DispositionAction is a part of. RecordSet's are the fundamental unit of Disposition. DispositionPlan's are applied against RecordSet's. As ManagedRecords are set-aside and assigned RecordCategory's, they are placed in RecordSet's until a Cutoff event (which may be immediate, but more usually associated with a periodicity such as monthly or quarterly). The Cutoff event is the first event in RecordSet's DispositionPlan which dictates its life-cycle. The ManagedRecords governed by a DispositionPlan are often in one RecordSet; however, they may be partitioned into multiple RecordSet's for any business purpose. A mandatory partitioning into RecordSet's occurs for suspended records (see the DispositionSuspend Package). Records governed by a particular DispositionPlan but suspended by some Authority are segregated into one or more RecordSet's assigned to the suspension. The creation date/time of the RecordSet. Often corresponds to the cutoffDate of the previous RecordSet subject to the DispositionInstruction. However, the RecordSet (along with its DispositionPlan) may be created in anticipation of the Cutoff. The status of final disposition for the RecordSet. The DispositionPlan governing the disposition of the RecordSet. The ManagedRecord's assigned RecordKeeper The RecordSet against which a DispositionSuspend has been levied. The ID(s) of the ManagedRecord(s) included in this RecordSet. The possible values of dispositionStatus for a ManagedRecord No final disposition has been triggered for the ManagedRecord A final disposition has been triggered for this RecordSet. It is in process of Transfer, or Destruction. It should be treated as no longer part of the Records Management Environment. However, it is possible that a suspension can be placed on a RecordSet that has dispositionStatus of "inProcess". Even if the RecordSet has been partially destroyed or transferred, the action is suspended. Final disposition has been completed. This is used for transfers and marks the completion of transferring the RecordSet to its destination organization. The RecordSet is now eligible for removal (deletion) from the system. As always, until the RecordSet has actually been deleted, it is subject to DispositionSuspend. DispositionAction is an "instantiation" based on the template ActionSpecification, used to populate a DispositionPlan based on its template, DispositionInstruction. Any notation concerning the execution of the DispositionAction. The actual completion date/time of the action. Based on the estimatedStartDate together with the expectedDuration of the ActionSpecification. If there is no duration attribute, it is assumed to be immediate, i.e., zero duration, e.g., Cutoff. The estimated start date/time for the action. This is based on calculations of estimated dates and durations of preceding DispositionAction's and will require update from time to time as more information is know. This is used to help project work loads based on particular actions scheduled for RecordSet's. The event of the DispositionAction ending. The next DispositionAction to be performed or to be performed. The previous DispositionAction to be performed or to be performed. The ActionSpecification that served as the template for the DispositionAction. The actual start date/time of the action. The ActionEvent that triggered the DispositionAction A SuspendEvent can be the action of a court, in which case it is a suspend order or it may be the result of an action by a record manager or some other authorized party. The SuspendEvent is associated with the DispositionSuspend's that it is responsible for. The DispositionSuspend's apply to RecordSet's. Under discovery the SuspendEvent can expand the ManagedRecords affected by adding them to a RecordSet (when subject to the same DispositionPlan), or by creating new RecordSet's under previously unaffected DispositionPlan's. The Authority declaring the SuspendEvent. The date/time that the SuspendEvent occurred. Text Description of the SuspendEvent (e.g., the court order or some other action that causes One of the DispositionSuspends that resulted from a SuspendEvent. Unique Identifier Name of the SuspendEvent The type of the SuspendEvent. These values are locally defined. One or more DispositionSuspend can be placed agains a RecordSet. If the RecordSet has records that are not to be suspended then the RecordSet is repartitioned so that the DispositionSuspend applies to a RecordSet in its entirety. No interim or final disposition can be executed on a ManagedRecord in a RecordSet.that has a DispositionSuspend unless that DispositionSuspend has a SuspensionRevocation associated with it. The date/time of the creation of the DispositionSuspend. A textual description of the DispositionSuspend. Unique identifier The ID of the SuspensionRevokation that shows the Authority authorizing the revokation. The SuspendEvent that resulted in the DispositionSuspend. A SuspensionRevocation releases a RecordSet from a particular DispositionSuspend. Note that a RecordSet can be under multiple DispositionSuspend's. Only when all DispositionSuspend's have been revoked through the creation of a SuspensionRevocation authorized by a suitable Party can final disposition proceed. The date/time that the SuspensionRevocation is authorized. A textual description of the SuspensionRevocation Unique identifier The ID of the Authority authorizing the revocation of a DispositionSuspend. The ID of the DispositionSuspend revoked by the Authority.