Summary:
Section titled “Summary:”The software CI must currently be manually populated. This article defines how and when to populate a software CI.
Assumptions, Risks, or Dependencies:
Section titled “Assumptions, Risks, or Dependencies:”Assumptions:
Section titled “Assumptions:”The person creating a software CI has the necessary knowledge to properly and completely fill out the details required for the software CI.
Risks:
Section titled “Risks:”Improperly documented software CI can lead to system misconfiguration.
Dependencies:
Section titled “Dependencies:”None
Requirements:
Section titled “Requirements:”The scope of this standard includes all software configuration items (CIs) that are used within a client’s business. This includes Primary business applications, databases applications, software used by any client employee for their job or applications installed by default on client systems, and any other software components used by the organization to conduct business.
Standard:
Section titled “Standard:”- All software used by a client to conduct business or facilitate the daily operation of the business should be included as a CI. Examples of software needing a CI entry include Google Chrome, Microsoft Word/Excel/PowerPoint/etc, QuickBooks, etc.
- All software CI names must match the name used to identify the software in the windows add and remove programs application or the default start menu naming schema classified by the install process.
- Anyone who believes a software CI is missing is empowered to create a software CI, if that person does not believe they have sufficient knowledge to properly fill out the CI that person must create a problem ticket with appropriate information for the client vITM to review and complete the CI.
- Attached is a default list of basic applications that can be edited and uploaded into Halo. Please trim it down to the software the client uses and add any missing PBAs prior to uploading.
External References:
Section titled “External References:”- None
Definitions:
Section titled “Definitions:”-
Application Type:
-
On Premise: This is a server based application with a database or application system hosted on client servers, either in the cIT cloud or clients own servers
-
Cloud: this is a cloud based application that is hosted on a third party cloud, such as AWS.
-
SAAS: This is a Software as a Service application, such as QuickBooks online
-
Client Application: This is for software that does not have a backend server system and is generally installed locally on a users
-
Version Number: This will be the approved version used within a client, if the software has several versions in use and the use of any version is acceptable, leave this blank. Match this version to the version seen in add/remove programs or defined by the manufacturer in the application.