CA Service Management

 View Only
  • 1.  Challenges in switching from Spine to CA ITAM

    Posted Jun 02, 2014 03:58 PM

    Hi All,

    I have got a cusotmer using Spine as Asset Management Tool and wants to swtich to CA ITAM Completely, however I am facing challenges in helping customer for this:

    Spine is currently managing Assets by creating multiple entries for updating any Field etc.

    For ex: If any component is upgraded, then Spine issues a new Asset code to asset and create a duplicate entry of Asset with a new Asset Code and provide the new Date of Purchase and update the Asset cost and depriciated cost etc.

    However CA ITAM works on single entry of asset and multiple cost entries etc
    is made for managing Assets. I am not able to do this as there are multiple
    Fields which are required to be updated.

    Please find below mentioned list of Fields whcih is currently being managed by Spine:

    Spine Fields
    Assets Code
    Assets Name
    Group Name
    Location
    CostCenter
    Custodian
    Category
    Remarks
    Serial No.
    Date of Purchase
    Book Date of Use
    Quantity
    Invoice No.
    Voucher No.
    Voucher Date
    PO No.
    PO Date
    Authorize
    Vendor
    Cost as at 01/04/2013
    Addition
    Deletion
    Cost as on 20/01/2014
    Depreciation as on 01/04/2013
    Depreciation for Period
    Dep.Deletion
    Dep. as on 20-01-2014
    WDV as on 01/04/2013
    WDV as on 20-01-2014
     AMC Status as on 30.06.2013 
     AMC Period 
    Warranty starts from Delivery, Instal, Acceptance (D,I,A)
    Date of Delivery/ Instl/ Acceptance
    FREE Warranty Yrs
    WARRANTY DUE DATE
    AMC YRS
    AMC Start Date
    Due in     2009-10
     Due in    2010-11 
     Due in     2011-12 
     Due in      2012-13 
     Due in      2013-14  
     Due in      2014-15  
     Due in      2015-16 and beyond 
     Amt Due in 2010-11 
     Amt Due in 2011-12 
     Amt Due in 2012-13 
     Amt Due in 013-14 
    STATUS AS ON 31.3.2013
     Amt Due in 014-15 
     Amt Due in 015-16 

    Above mentioned fields have multiple entries for Single Asset to manage update in Field value.

    I need to manage these fields in such a way in CA ITAM so that there would be no duplicate entry of Assets. For ex: Linking with Cost etc.



  • 2.  Re: Challenges in switching from Spine to CA ITAM

    Posted Oct 08, 2014 01:56 PM

    I would like to share the solution which I had deployed for this. We had used concept of Parent and Child Assets. We imported the data from Spine Output sheet by formatting it is as per requirement of CA ITAM. We added one more field named Asset Code Alias which was created to manage child assets (Duplicate Entries of assets to manage newly updated fileds). Primary Look was used on Asset Code Alias. In addition to it, many extended Fields were created in CA APM as per requirement of Data.