UDFS Phase II Issues Log -- Abbreviations: A/R-Billing Team = ARBT; Asset Management Team = AMT; Grants Team = GT; Facilities/Projects Team = FPT; Technical Team = TT; Communications Team = CT; Reporting Team = RT; Crestone Consultants = CC; Information Technology Steering Committee = ITSC; Executive Steering Committee = EST; Executive Committee = EC; Not Applicable = N/A
Team Name                       or other identifier:			Asset Management
#	DATE (Submitted)	MODULE (Abbreviate)	ISSUE                                                                                   (If abbreviations are used add definition above)	OWNER (Name(s) of who will resolve)	PRIORITY (High, Medium, Low)	COMMENTS                                      (If abbreviations are used add definition above)	DATE                  (Issue Resolved)	ISSUE RESOLUTION                                                                                                                                           (If abbreviations are used add definition above)
1	w/e 11/26/03	AMT	A/P Staff assigning profile IDs (comparable to item number in current PPR system) to equipment as it is expensed.			Change in business process	00/00/00
2	w/e 11/26/03	AMT	Use of auto numbering for profile IDs.  Karen Brown currently does not use item number to look up equipment; she uses item description.  Item description field is in Psoft AM.			Advantage--will not have to manage a numbering system.  Psoft has a "class" field which groups like-assets together.  For ex, Automobiles is a class and the profiles grouped within would be van, police cruiser, etc.
3	w/e 11/26/03	AMT	Consider use of Parent/Child functionality of the Psoft AM either at implementation or at a later time.
4	w/e 11/26/03	AMT	Need to review current business practice concerning add-on values (FASB rules concerning additional life expectancy or assign a new tag #).  This is a frequent occurrence.			Would the Parent/Child functionality be useful in these instances?
5	w/e 11/26/03	AMT	No field in Asset Acquisition Detail for ownership codes (ie, federal, state, university, etc.) from central table 20070.			Could be a bolt-on.
6	w/e 11/26/03	AMT	No field in Asset Acquisition Detail for primary agency codes (source of funds in current PPR system from central table 03010).			Could be imported from 'source' chartfield in Psoft G/L if deemed that the value list is sufficient.
7	w/e 11/26/03	AMT	The location code table will consist of every building/room combination.  Auto numbering of location id is recommended.			Advantage--will not have to manage a numbering system.  There is a building id field of 10 characters.  It could contain the old building identifier of 2 alpha characters and then a numerical value.  Joan Watson has exhausted available numbers as the current system has only 4 characters.  Historical records could be maintained without having to reuse their numbers.
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25