1.0 Title: Combined Work Order Log
2.0 Purpose:
3.0 Recommended Usage:
4.0 Frequency:
5.0 Reference Documents:
6.0 Responsibility:
7.0 Ownership:
8.0 Level of Effort (costs)
9.0 Risks
10.0 CONTENTS:
This cdid consists of an OpenOffice data file located on the resource person's primary working computer which replicates to the resource person's perosnal webspace on the hri webspace. <to be continued>
10.1 work order <cdid:pm4 dd:pm kc:wo> [1]
This is the work order number being charged by the resource for the duration of the logging period.
10.2 task <cdid:pm45 dd:pm kc:task>
The concatenated PERT style in and out node numbers for a task within a work order. These numbers are separated by a dash.
10.3 file <cdid:pm45 dd:km kc:filename>
The hri07e format filename and URI for the file.
10.4a timestamp in <cdid:pm45 dd:pm kc:in>
This local timestamp for the file being opened for review or editing.
note: this is the time when charges have started accruing to the work order for this resource. It stands to reason that only one work order should be charged at a time and that any significant interruption should result in the the file being closed for logging purposes and the accrual of charges to that wrok order should cease.
10.4b timestamp out <cdid:pm45 dd:pm kc:out>
This local timestamp for the file being closed for review or editing.
10.5 follow-up <cdid:pm45 dd:pm kc:fup>
10.6 follow-up date <cdid:pm45 dd:pm kc:fupdate>
10.7 action <cdid:pm45 dd:pm kc:action>
10.8 location <cdid:pm45 dd:pm kc:loc>This is the location of the resource at the time of the logging. If the activity involves travel then this is the starting point. The next log entry should indicate the arrival point if a signficant activity begins at that location - otherwise the location should be assumed to be the resource's home working location for that period. (i.e. either the resource's permenent or visiting office.)
10.8 notes <cdid:pm45 dd:pm kc:notes>
Any "tweet" size comments or notes. More complex comments should be posted in the resource's work order note file.
11.0 Metadata (Data Typing)
12.0 File Handling Policy
Because almost all files will be in electronic format the CDID itself must state how documents of this type must be handled by the information system.
12.1 Backup
Backup policies must be stated for time of retention
12.2 Privacy
PIPEDA (Canada), Sorbanes Oxley (USA) and equivalent privacy handling methods must be specified.
12.2 Security
The security level of the document must be indentified and options noted.