Much of your businses and support processes are defined in documents. Unlike Intranets, file shares and Microsoft SharePoint
SamanthaTM links documents to their related or underlying configuration items. Why is this important?
When documents are linked to their underlying configuration items, you can easily see all of your relevant support information
per device in one place. You have a better chance at keeping your documentation up-to-date when they are attached to systems you
update. Also, change prediction software can identify the documents that might need to be changed when they are linked to their
underlying systems.
Documents in SamanthaTM are organized in categories and can be:
- Saved in the repository, ensuring the link to the document is valid
- Links to your Intranet, SharePoint or file share, thus keeping only one copy of the document on-line
- Links to URLs on the Internet
There are several examples where keeping documents in a CMDB makes sense:
- Organizing all your purchase orders, with supporting justification documents, tied to the assets that were purchased
- Keeping an on-line repository of maintenance agreemetns, liked to the devices that are covered
- To tie application development requirements documents and release plans to applications
- Using your CMDB to be a knoweldge base on your systems and applications
- To aid disaster recovery, using your CMDB as an recovery data repository
|
