<In the case of "home grown" code, this is usually the property of the
corporation, and is not owned by IT per se.>

That's true of all the records, data, applications, and infrastructure.
Determining "ownership" for retention purposes is a means of determining
responsibility for the information - either managing it or
entering/creating valid data.  For instance, IT would be responsible for
application software, configuration, access rights, programming (where
needed), code (where IT has written it) and licenses.  The business
"owner" would be responsible for the accuracy of the data entered and
the validity of the transaction data history - i.e. the transaction
"record."

Ginny Jones
(Virginia A. Jones, CRM, FAI)
Records Manager
Information Technology Division
Newport News Dept. of Public Utilities
Newport News, VA
[log in to unmask]

-----Original Message-----
From: Records Management Program [mailto:[log in to unmask]] On
Behalf Of Gerard J. Nicol
Sent: Wednesday, December 28, 2005 12:16 AM
To: [log in to unmask]
Subject: Re: IT Records

Rick,

It is difficult to class executable code as data given that you may or
may
not have the source.

Executable code never strictly belongs to IT, in the case of operating
system code it is used under license from the owner who is usually a
software company.

In the case of "home grown" code, this is usually the property of the
corporation, and is not owned by IT per se.

This would also be the case for any wrapper applications such as JCL or
shell scripts.

IT will manage the items it either owns or manages via Change Control
tools
such as CA-Endevor and Change Management tools such as Solve.

Gerard

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance