Dear All, below is the key questions of Configuration and Asset Management: 1) How is the relationship between Configuration

and Asset Management? Relationship between configuration and asset management , we called Service Asset and Configuration Management (SACM) . IT executives are clamoring for more control over the physical and service assets they manage. They are particularly interested in the owners, users, locations, and relationships between hardware, software,application, and media assets. Effective asset control and efficient delivery of information generates fewer incidents, faster mean-time-to-repair, and better data for root cause analysis.These actions alsoreduce impact of change, and improve financial management. Within the ITIL framework, this lifecycle process is called Service Asset and Configuration Management (SACM).

2) Why we need to involve Vendor (Hardware and Software) to do Configuration management? Involve of the vendors' in Configuration Management processes to ensure the vendor will provide appropriate updates to the product and notices when the product changes or is discontinued (Hardware & Software supplier vendor ). This continued support most likely will require an on-call service contract and a warranty period. On the other end, where the development is a large multi-regional system with multiple stakeholders, and a mix of custom hardware/software and COTS products owned by the system's owner and stakeholders, the Configuration Management process will be more involved for vendor. 3) What kind of table matrix that we need to document in configuration management? what is the best approach to conduct it? -Table Matrix for Configuration management is RACI Matrix . A Responsible, Accountable, Consulted, and Informed (RACI) diagram or RACI matrix is used to describe the roles and responsibilities of various teams or people in delivering a project or operating a process. It is especially useful in clarifying roles and responsibilities in cross-functional/departmental projects and processes

A traceability matrix is a document, usually in the form of a table, that correlates any two baselined documents that require a many-to-many relationship to determine the completeness of the relationship. It is often used with high-level requirements (these often consist of marketing requirements) and detailed requirements of the product to the matching parts of high-level design, detailed design, test plan, and test cases

The best approach is traceability matrix cause

Define analysis scenarios, such as automated code reviews and link them back to the original requirements Instigate test runs and record test run results with the associated code coverage measurements Automate the generation of defects logs and generate non-conformance documentation Interrogate requirements for requirements coverage and test status

And related to some of your request to do conference call to cover previous chapter, I am proposing we conduct it either Wednesday or Thursday , 5.30pm-7.30pm, starting on 13/14 Nov 2013. So i need all of you to vote, either want to conduct by Wednesday or Thursday, by also replying in this thread. I Vote Thusday , Pak Tan for CC Thank you Anwar fattah 1322402090