|
|
If we think of asset management as divided into day-to-day work and organization (InfoAsset Manager) and long term, CIP planning work (Info360 Asset), this idea would bring asset management full circle. It'd also provide a huge workflow benefit for InfoAsset Manager current users to begin to migrate to the cloud with the certainty in knowing that their data is still all up-to-date. The two compliment each other very well - IAM has the complexity to manipulate all data, data integrity, etc., Info360 has the simple interface, cloud, etc. - they just need to connect more seamlessly.
This would require enabling Cloud datastore/database for InfoAsset Manager desktop client. This would be the first step.
This makes sense to me. IAM does so much so elegantly both by itself and especially when InfoAsset Exchange and Ruby scripting are used to aid in importing / exporting / manipulating data. It would appear to be logical to make the IAM database structure the back bone of what is displayed in simplified fashion in Info360 Asset.
This would be tremendously beneficial. In the long tem Info360 Asset will be the all encompassing AM product, but in the near to midterm an integrated approach is required to maintain current clients and eventaully migrate them. We also need this 'integrated' approach to open new markets. In EMEA we need to address the market needs which currently Info360 Asst does not address. Capturing new clents is critical in the short to midterm with the idea to convert them to Info360 Asset when it is ready. We cannot abandon a market for 2/3 years whilst we wait for a product to mature.