RECMGMT-L Archives

Records Management

RECMGMT-L@LISTSERV.IGGURU.US
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version:
1.0 (1.0)
Content-Type:
text/plain; charset=utf-8
Date:
Tue, 17 May 2016 08:59:51 -0700
Reply-To:
Records Management Program <[log in to unmask]>
Subject:
Re: Business Processes
From:
RIMMAN <[log in to unmask]>
In-Reply-To:
<[log in to unmask]>
Content-Transfer-Encoding:
8bit
Sender:
Records Management Program <[log in to unmask]>
Parts/Attachments:
text/plain (31 lines) 
The primary example that comes to mind is purchase of high value, or sophisticated, "engineered equipment".  Things build to design specifications that may have long term (15 year or longer) warranties.

In these cases, you have specs and drawings that have a retention period, which may accompany bid and procurement, along with shipping and receiving documentation, that all have their (typically) shorter retention periods.  And the equipment may have warranty documents that arrive with it, or independent of it.

It's not common that all of these documents get 'married' together and are retained as a set for the longest required retention period... The end of the warranty, or possibly, the resale of the equipment before it reaches end of useful life.

The shortest retention is generally shipping and receiving papers, followed by procurement documents, then specs and drawings.  

And yes, I'm speaking "real world" examples here... Like utilities who design and deploy compressor stations and ancillary equipment, pipelines, etc.  not naming any names, but I think one that's STILL in the news may come to mind.

Larry Medina
[log in to unmask]

Sent from MY iPhoneSeís

> On May 16, 2016, at 12:37 PM, Gary Link <[log in to unmask]> wrote:
> 
> I am looking for examples of business processes that you have observed in 
> your professional travels wherein the business process did not support the 
> retention policy for the records it created. An easy example of what I 
> mean would be a business process which generated records having an 
> event-driven retention, however, the process did not provide for the 
> triggering event to be communicated back to the group or system that 
> managed the records. The result is of course that the retention could not 
> be executed.

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]

ATOM RSS1 RSS2