Skip to Content

IT service management

FootPrints' IT Service Management template provides a great deal of ITIL 3 compatibility, integrating the Change and Release Management, Configuration Management, and Service Catalog workspaces with a Service Desk workspace. The IT Service Management workspace template actually creates four separate workspaces: Service Desk; Problem Management; Change/Release Management; and Service Portfolio when it is created.

Service Desk

  • Fields - Custom fields can be created to track the different requests and problems reported to the corporate Service Desk. These fields will help with quick data entry, and help sort and report on different areas and problem types.
    • Built-in Fields:
      • Title – Is used as a brief summary or description of request. If desired, this can be a drop-down list of acceptable request types.
      • Description – Is used for complete description of request or problem, updates, and resolution. Each addition to the description automatically contains a time, date and user stamp.
      • Assignees – The Assignee field automatically lists all agents. Refer to the section below on “Assignment” for more information.

      • Statuses – Request, Open, Closed, Need More Info, Await Approval, Pending, Internal FAQ

        Warning

        Note

        Request” status is a built-in status, but only appears when an employee customer submits a Request, prior to it being assigned to an Agent. Open and Closed statuses are also built-in, so only the other 4 need to be created.

    • Priorities
      • Maximum - Set to 5
      •  Default - Set to 5
      • Words defined - Critical, High, Medium, Low, Planning
    • Workspace Fields – Up to 100 custom Workspace Fields can be created (no limit in SQL/Access versions) to record information about the incident. Contact information is tracked in the Address Book (see below). Here are some suggested fields.
      • Type of Incident (drop-down)  – Failure, Service Request
      • Main Category (drop-down) – Hardware, Software, Printer, Network
      • Hardware
        • Sub-category (drop-down) - CD-ROM, Hard Drive, Floppy Drive, Keyboard, Memory, Modem, Monitor, Mouse
      • Software
        • Sub-category (drop-down) - Acrobat, Excel, Internet Explore, Outlook, PowerPoint, PhotoShop, Word
      • Printer
        • Sub-category (drop-down) - Various printer models
      • Network
        • Sub-category (drop-down) - Change Authority, Can't Connect to Network, Can't Connect to Internet
      • Closure Code (drop-down) - Completed successfully, Training required, Documentation needed, No fault found, Monitoring required, Advice given, RFC needed
      • Resolution - Multi-line text entry field for describing the resolution.
    • Service Level
      • Impact (drop-down) - High, Medium, Low
      • Urgency (drop-down) - High, Medium Low
      • SLA Response Time (date/time)
      • SLA Due Date(date/time)
    • CI Links - For FootPrints Configuration Manager, an add-on module.
    • Time Tracking - FootPrints can track the time spent by Agents working on Issues. This data can be used to create time tracking reports, which can be used for billing, or to track any time-related information, such as how long one or more users spend on certain kinds of Issues. 
      • Recommended configuration – Enabled, Mandatory, Automatic.
        With this configuration, FootPrints automatically tracks the time spent by Agents as they fill out and edit an Issue, for example, as the Agent is speaking on the phone with the user. In addition, the initial Agent (or second/third level Agent) can fill in their time spent on troubleshooting/fixing manually. An hourly billing rate should be specified for each Agent (see Users). In this way, time tracking data can be used for charge-backs to other departments, or to justify increased resources.
    • Address Book – The Address Book is a sub-database that contains all of the contact information for your user base. Each record in the Address Book is called a “Contact”. Users who are reporting problems are referred to as “Contacts” or  “Employee Customers” in FootPrints. The Address Book can contain up to 100 fields (SQL/Access versions are unlimited) for employee data, including Name, Department, Phone number, Email address, etc.
      • Suggested Address Book Fields:
        • Department (drop-down) – Customer Service, R&D, Executive, Finance, Human Resources, IT, Marketing, Sales
        • Last Name (character field)
        • First Name (character field)
        • User ID (character field)
        • Email address (Email address)
        • Phone (character field)
        • Location (drop-down) – 1st Floor, 2nd Floor, 3rd Floor, 4th Floor, Downtown Office, Remote

        • Service Level (drop-down) – Platinum, Gold, Silver, Bronze.

          Warning

          Note

          The preceding field should be specified as “Internal”.

      • Address Book Data – Address Book data can be entered manually for each Contact, imported from a text file, or taken dynamically from and LDAP-compliant contact database. Please refer to the section on Address Book Administration for more information.
    • Assignment – Assignment can be handled manually, or the Auto Assign Feature can be used to assign one or more users to a new Issue based on, for example, the “Request Type” field.
    • Escalation – Escalation should be enabled and various rules defined to meet service levels, handle high-priority issues, and set up follow-up reminders. Some rules to consider:
      • One “Instant” escalation rule can be made for each Service Level. The actions can include changing the priority, to an appropriate priority for that level, assignment, etc. See the example in the topic on “Escalation”.
      • Escalation rules can be defined for certain high priority issues, such as network outages, etc. 
      • Rules can be made to handle Issues that have been open for a certain amount of time to send a reminder to the assignees that the Issue must be resolved, and/or to reassign them to someone else. 
      • A rule should be set to send an email to the assigned Agent based on the “Follow Up Date” field.  The criteria should include:
        • Name:  Per-Issue Reminders
        • Escalation On/Off: Select “On”
        • Actions:  “Send mail to the Assignees” checked, select one or more email types
        • Time Unedited: 5 minutes
        • Criteria:
        • Status=Highlight ”Request”, “Open”, and any custom statuses to get reminders on active Issues, or “Closed” to get reminders on Closed Issues (OR highlight all statuses except for “Solution” to get reminders on any Status Issue)
        • For “Follow Up Date”, choose “equal to” and check the box for “Current Date” (do not fill in any dates).
  • Email – Outgoing email notification rules should be set to send mail to assignees and customers for all changes, or, if you would prefer, only for certain statuses. One or more Agents should also be defined to receive an email each time a new Request is submitted by a Customer. Incoming email can be configured to handle both incoming email submissions and email updates to existing Issues.
    • CCs – Other agents, developers, or other users can be copied on an Issue without actually being assigned. These people will receive email notification, and can optionally respond to the email with comments or suggestions, which will automatically be threaded to the Description of the Issue with a time, date and user stamp. 
  • Queues – Create 1 Saved Search for each “Request Type” (Hardware, Software, Network, etc). For example, the Criteria for the Hardware Queue would include “Status”=Request, Open, and all other active statuses, “Request Type”=Hardware, Sorting “Date Submitted Ascending” (oldest at the top), Name “Hardware Queue”, Type “Shared”.  
  • Reports – The built-in Metric reports can be used by the Service Desk Manager to get important metrics like Open vs. Closed rates, number of Open Issues by assignee, etc. Custom report templates can be made to show details and stats for things like: All active Issues by assignee, All active Issues by Request Type, All active Issues by Department, Priority, etc. The Auto-run Reports feature can be used to automatically email one or more reports to the Managers every Monday morning, etc.
    • Cross-workspace Reports – The Administrator can create cross-workspace reports to return data from multiple workspaces, such as Service Desk, Development, and Issue Management. All built-in fields, as well as any common custom fields found in the workspaces, can be included in the report. So, if the Address Book is shared between the aforementioned workspaces, a report can be generated on a particular contact that includes all activity for that user across all departments.
  • Asset Management – The BMC FootPrints Asset Core Add-on Module is highly recommended. All hardware, software, and network information for each PC will be automatically tracked. Other network devices, like servers, routers and printers can also be tracked. Asset information can be included as part of the history of an Issue.
  • Knowledge Base – The FootPrints Knowledge Base feature is very useful for the Internal Service Desk. Frequently Asked Questions, Solutions to common problems, and patches can be made into Solutions.  When a Customer Issue is resolved, it can also be made into a Solution. FAQ categories can be defined to group solutions by problem type, platform, software version, etc. Both Agents and Customers can have access to Solutions and FAQ categories. Agents can use the Knowledge Base to solve current Issues, searching the FootPrints Knowledge Base by keyword, by FAQ category, and even searching popular online knowledge bases like Microsoft TechNet. 
  • Customer Self Service – The Customer Self Service option allows employee customers to submit and track their Service Desk requests, as well as search the Knowledge Base. Users can log into FootPrints using a common shared ID and password, their email address, or a unique ID and password. Unique Customer IDs and passwords can be linked to their network IDs and passwords (using NT, UNIX or LDAP password authentication and the Auto-Add Customer feature). Customer contact information can be dynamically populated via the Dynamic Address Book Link feature. Customers can also submit Requests, receive notification, and respond to notification via email.
  • Users – Agent users can set their personal preferences to view a list of their own assignments on the FootPrints home page, as well as set their home page columns to display important information about those Issues on the home page, like “Request Type”, “Department”, “Platform”, etc.
    • Agents can use their network ID and password to log into FootPrints if NT, UNIX or LDAP password authentication is enabled.
    • See more information on Customer users under “Customer Self Service”.

  • File attachments – File attachments are useful for employee customers to provide screenshots of the problem they have having, and for Agents to provide patches, Word documents with step-by-step instructions, etc. Solutions in the Knowledge Base can contain file attachments, allowing easy distribution of patches, procedures, and other files. Incoming email submissions from customers that contain attachments will automatically include those attachments with the Issue that is created in FootPrints

    Warning

    Note

    File Attachments in FootPrints are kept in the C:\FootPrints\html\tmp\Attachments directory on the FootPrints server. Anti-virus software can be pointed to that directory to ensure that attachments do not contain viruses.

  • Surveys—The Customer Survey feature can be used to gather information about the quality of service employee customers receive from the Service Desk and other IT departments. The survey, created by the Workspace Administrator, is sent automatically to the employee customer each time his or her Request is closed.
  • FootPrints Instant Talk—The Instant Talk feature can be used by the Internal Service Desk to allow customers to chat with available agents, quickening resolution of Issues. Instant Talk can also be used by agents to chat with each other when they are in different parts of the building, different sites, or on the telephone.
  • Remote Control—The Remote Control feature can be used by agents to take control of a user’s desktop to aid in solving a PC-related issue. The VNC Remote Control software can be optionally installed on all PC’s, or can be installed on an as-needed basis.
  • Copy/Move Issue feature—This feature can be used to assign Issues to users in other workspaces. For example, a Service Desk agent could assign an Issue in the Service Desk workspace to the development workspace.
  • Splash screen—The splash screen option can be used to communicate important information and alerts to agents and customers. Different screens can be defined for agents and customers. Splash screens can include text, HTML, links to other sites or pages, graphics, etc. They can be updated at any time by the Workspace Administrator.

Problem Management

  • Fields - Custom fields can be created to track the different requests and problems. These fields will help with quick data entry, and help sort and report on different areas and problem types.
    • Built-in Fields:
      • Title – Is used as a brief summary or description of request.  If desired, this can be a drop-down list of acceptable request types.
      • Description – Is used for complete description of request or problem, updates, and resolution. Each addition to the description automatically contains a time, date and user stamp.
      • Assignees – The Assignee field automatically lists all agents.  Refer to the section below on “Assignment” for more information.

      • Statuses – Request, Open, Closed, Need More Info, Await Approval, Pending, Internal FAQ

        Warning

        Note

        Request” status is a built-in status, but only appears when an employee customer submits a Request, prior to it being assigned to an Agent. Open and Closed statuses are also built-in, so only the other 4 need to be created.


    • Priorities
      • Maximum - Set to 5
      •  Default - Set to 5
      • Words defined - Critical, High, Medium, Low, Planning
    • Workspace Fields – Up to 100 custom Workspace Fields can be created (no limit in SQL/Access versions) to record information about the problem. Contact information is tracked in the Address Book (see below).  Here are some suggested fields. 
      • Type (drop-down)  – Problem, Known Error
      • Impact (drop-down) - High, Medium, Low
      • Urgency (drop-down) - High, Medium, Low

    • Incident Information
      • Type of Incident (drop-down) - Failure, Service Request
      • SLA Due Date (date/time)
  • CI Links - CI Links section for FootPrints Configuration Manager, an add-on module.
    • Time Tracking - FootPrints can track the time spent by Agents working on Issues. This data can be used to create time tracking reports, which can be used for billing, or to track any time-related information, such as how long one or more users spend on certain kinds of Issues. 
      • Recommended configuration – Enabled, Mandatory, Automatic.

With this configuration, FootPrints automatically tracks the time spent by Agents as they fill out and edit an Issue, for example, as the Agent is speaking on the phone with the user. In addition, the initial Agent (or second/third level Agent) can fill in their time spent on troubleshooting/fixing manually.  An hourly billing rate should be specified for each Agent (see Users). In this way, time tracking data can be used for charge-backs to other departments, or to justify increased resources.


    • Address Book – The Address Book is a sub-database that contains all of the contact information for your user base. Each record in the Address Book is called a “Contact”. Users who are reporting problems are referred to as “Contacts” or  “Employee Customers” in FootPrints. The Address Book can contain up to 100 fields (SQL/Access versions are unlimited) for employee data, including Name, Department, Phone number, Email address, etc.
      • Suggested Address Book Fields:
        • Department (drop-down) – Customer Service, R&D, Executive, Finance, Human Resources, IT, Marketing, Sales
        • Last Name (character field)
        • First Name (character field)
        • User ID (character field)
        • Email address (Email address)
        • Phone (character field)
        • Location (drop-down) – 1st Floor, 2nd Floor, 3rd Floor, 4th Floor, Downtown Office, Remote

        • Service Level (drop-down) – Platinum, Gold, Silver, Bronze.

          Warning

          Note

          The preceding field should be specified as “Internal”.




        • Address Book Data — Address Book data can be entered manually for each Contact, imported from a text file, or taken dynamically from and LDAP-compliant contact database. Please refer to the section on Address Book Administration for more information.
    • Assignment — Assignment can be handled manually, or the Auto Assign Feature can be used to assign one or more users to a new Issue based on, for example, the “Request Type” field.
    • Escalation — Escalation should be enabled and various rules defined to meet service levels, handle high-priority issues, and set up follow-up reminders. Some rules to consider:
      • One “Instant” escalation rule can be made for each Service Level. The actions can include changing the priority, to an appropriate priority for that level, assignment, etc. See the example in the topic on “Escalation”.
      • Escalation rules can be defined for certain high priority issues, such as network outages, etc. 
      • Rules can be made to handle Issues that have been open for a certain amount of time to send a reminder to the assignees that the Issue must be resolved, and/or to reassign them to someone else. 
      • A rule should be set to send an email to the assigned Agent based on the “Follow Up Date” field. The criteria should include:
        • Name:  Per-Issue Reminders
        • Escalation On/Off: Select “On”
        • Actions:  “Send mail to the Assignees” checked, select one or more email types
        • Time Unedited: 5 minutes
        • Criteria:
        • Status=Highlight ”Request”, “Open”, and any custom statuses to get reminders on active Issues, or “Closed” to get reminders on Closed Issues (OR highlight all statuses except for “Solution” to get reminders on any Status Issue)
        • For “Follow Up Date”, choose “equal to” and check the box for “Current Date” (do not fill in any dates).
  • Email — Outgoing email notification rules should be set to send mail to assignees and customers for all changes, or, if you would prefer, only for certain statuses. One or more Agents should also be defined to receive an email each time a new Request is submitted by a Customer. Incoming email can be configured to handle both incoming email submissions and email updates to existing Issues.
    • CCs — Other agents, developers, or other users can be copied on an Issue without actually being assigned. These people will receive email notification, and can optionally respond to the email with comments or suggestions, which will automatically be threaded to the Description of the Issue with a time, date and user stamp. 
  • Queues — Create 1 Saved Search for each “Request Type” (Hardware, Software, Network, etc). For example, the Criteria for the Hardware Queue would include “Status”=Request, Open, and all other active statuses, “Request Type”=Hardware, Sorting “Date Submitted Ascending” (oldest at the top), Name “Hardware Queue”, Type “Shared”.  
  • Reports — The built-in Metric reports can be used by the Service Desk Manager to get important metrics like Open vs. Closed rates, number of Open Issues by assignee, etc. Custom report templates can be made to show details and stats for things like: All active Issues by assignee, All active Issues by Request Type, All active Issues by Department, Priority, etc. The Auto-run Reports feature can be used to automatically email one or more reports to the Managers every Monday morning, etc.
    • Cross-workspace Reports — The Administrator can create cross-workspace reports to return data from multiple workspaces, such as Service Desk, Development, and Issue Management. All built-in fields, as well as any common custom fields found in the workspaces, can be included in the report. So, if the Address Book is shared between the aforementioned workspaces, a report can be generated on a particular contact that includes all activity for that user across all departments.
  • Asset Management — The BMC FootPrints Asset Core Add-on Module is highly recommended. All hardware, software, and network information for each PC will be automatically tracked. Other network devices, like servers, routers and printers can also be tracked.  Asset information can be included as part of the history of an Issue.
  • Knowledge Base — The FootPrints Knowledge Base feature is very useful for the Internal Service Desk. Frequently Asked Questions, Solutions to common problems, and patches can be made into Solutions.  When a Customer Issue is resolved, it can also be made into a Solution. FAQ categories can be defined to group solutions by problem type, platform, software version, etc. Both Agents and Customers can have access to Solutions and FAQ categories. Agents can use the Knowledge Base to solve current Issues, searching the FootPrints Knowledge Base by keyword, by FAQ category, and even searching popular online knowledge bases like Microsoft TechNet. 
  • Customer Self Service — The Customer Self Service option allows employee customers to submit and track their Service Desk requests, as well as search the Knowledge Base. Users can log into FootPrints using a common shared ID and password, their email address, or a unique ID and password. Unique Customer IDs and passwords can be linked to their network IDs and passwords (using NT, UNIX or LDAP password authentication and the Auto-Add Customer feature). Customer contact information can be dynamically populated via the Dynamic Address Book Link feature. Customers can also submit Requests, receive notification, and respond to notification via email.
  • Users — Agent users can set their personal preferences to view a list of their own assignments on the FootPrints Home page, as well as set their home page columns to display important information about those Issues on the home page, like “Request Type”, “Department”, “Platform”, etc.
    • Agents can use their network ID and password to log into FootPrints if NT, UNIX or LDAP password authentication is enabled.
    • See more information on Customer users under “Customer Self Service”.

  • File attachments — File attachments are useful for employee customers to provide screenshots of the problem they have having, and for Agents to provide patches, Word documents with step-by-step instructions, etc. Solutions in the Knowledge Base can contain file attachments, allowing easy distribution of patches, procedures, and other files. Incoming email submissions from customers that contain attachments will automatically include those attachments with the Issue that is created in FootPrints.

    Warning

    Note

    File Attachments in FootPrints are kept in the C:\FootPrints\html\tmp\Attachments directory on the FootPrints server. Anti-virus software can be pointed to that directory to ensure that attachments do not contain viruses.

  • Surveys—The Customer Survey feature can be used to gather information about the quality of service employee customers receive from the Service Desk and other IT departments. The survey, created by the Workspace Administrator, is sent automatically to the employee customer each time his or her Request is closed.
  • FootPrints Instant Talk—The Instant Talk feature can be used by the Internal Service Desk to allow customers to chat with available agents, quickening resolution of Issues. Instant Talk can also be used by agents to chat with each other when they are in different parts of the building, different sites, or on the telephone.
  • Remote Control—The Remote Control feature can be used by agents to take control of a user’s desktop to aid in solving a PC-related issue. The VNC Remote Control software can be optionally installed on all PC’s, or can be installed on an as-needed basis.
  • Copy/Move Issue feature—This feature can be used to assign Issues to users in other workspaces. For example, a Service Desk agent could assign an Issue in the Service Desk workspace to the development workspace.
  • Splash screen—The splash screen option can be used to communicate important information and alerts to agents and customers. Different screens can be defined for agents and customers. Splash screens can include text, HTML, links to other sites or pages, graphics, etc. They can be updated at any time by the Workspace Administrator.

Change/Release Management

This template is designed to track and manage changes. The Issue page that is created with this template contains sections that are Status-dependent, meaning that the sections of the Issue expand or collapse depending on the value in the Status field.

  • Built-in Fields
    • Title—Single-line character field.
    • Priority—Drop-down field.
    • Status—Drop-down field. Values are:  New, Initiation Phase, Design Phase, Development Phase, QA Testing Phase, Implementation Phase, Rejected, Canceled, All Phases, Completed.
    • Summary of Change (Description) —Multi-line character field.  Used for complete description of the proposed change.

  • Suggested Fields

    • Status set to New—When the Status field is set to New, the following suggested fields are shown in the RFC Information section:
      • Reason for Change—Drop-down field.  Values are:  Incident/Problem Resolution, User/Customer Dissatisfaction, New Requirements, Upgrade to Infrastructure, New or Changed Legislation, Location Change, Product/Service Change from Vendor, New Account, Personnel Vacancy, Updated Information.
      • Change Type—Drop-down field.  Values are:


        • Data Content—Dependent values that are displayed in the Category field when this value is selected are Updating Information, Replacing Information, Deleting Information.
        • Data Storage Method—Dependent values that are displayed in the Category field when this value is selected are Change to Database (DDL), Change Server, Change Database.
        • Software Update—Dependent values that are displayed in the Category field when this value is selected are Upgrade to Software, Feature Request.
        • Equipment Update—Dependent values that are displayed in the Category field when this value is selected are CD-ROM/DVD, Hard Drive, Memory, Processor, Operating System.
        • New Application—Dependent values that are displayed in the Category field when this value is selected are Replacing Existing Application, For New Requirements.
        • New Equipment—Dependent values that are displayed in the Category field when this value is selected are Replacing Existing Equipment, Supplementing Existing Equipment, New Implementation.
        • Backup/Restore—Dependent values that are displayed in the Category field when this value is selected are Backup to Tape, Backup to CD/DVD, Restore from Tape, Restore from CD/DVD.
        • Policy Change—Dependent values that are displayed in the Category field when this value is selected are Data Access, Server Access, Physical Data Storage, User Account Management.
        • Access Control—Dependent values that are displayed in the Category field when this value is selected are Access to Data, Access to Server, Access to Application.

    • Category—Drop-down field for selecting the category for the change type. This is actually a dependent field, the choices for which depend on the choice of Change Type.
    • Data type— Drop-down field for selecting the type of data to be changed. Values are:  Financial Accounting, Financial Reporting, Internal Auditing, Information Security, Product Information.
    • Data Classification—Drop-down field for selecting a classification for the data to be changed. Values are:  Public, Proprietary, Confidential, Secret.
    • Business Unit Impacted—Drop-down field for defining the business unit that is affected by the change. Values are:  Finance, IT, Audit, Legal, Operations.
    • Application—Drop-down field for defining the software applications that will be affected by the change. Values are:  Acrobat, Excel, FootPrints, Internet Explorer, Netscape, Outlook, Photoshop, Powerpoint, Quick Books, Word.
    • Business Owner—Drop-down field for defining the title of the individual whose business Unit will be affected by the change. Values are: CFO, CIO, CEO, COO, Director of Accounting, Director of IT, Accounting Manager, IT Manager.
    • IT Owner/Custodian—Drop-down field for defining the title of the individual within the IT department who has responsibility for implementing the change. Values are:  CIO, IT Director, IT Manager, IT Analyst.
    • Host server—Drop-down field for setting the name of the server on which the change is to be implemented. Values are:  SERVER1, SERVER2, SERVER3, SERVER4, SERVER5, SERVER6, SERVER7, SERVER8.

    • Status set to Initiation/Evaluation Phase—When the Status field is set to Initiation/Evaluation Phase, the following suggested fields are shown in the RFC Information section:
      • Initiation Start Date—Date field for when the phase began.
      • Initiation Action—Drop-down field for selecting the status of action in this phase. Values are:  In Progress, Completed, Insufficient Data.
      • Initiation Notes—Multi-line character field for notes.
      • Estimated Scope—Drop-down field for defining the scope of the change in terms of its severity. Values are:  Minor, Significant, Major, Company-wide.
      • Cost/Impact—Drop-down field for defining the estimated financial impact of the change. Values are:  $0-$5k, $5k-$10k, $10k-$50k, $100k-$500k, $500k+.
      • Business Owner Identified—Checkbox field for defining whether the business owner for the change has been determined. This field is to be completed at the end of the phase.
      • IT Owner Identified—Checkbox field for defining whether the IT owner for the change has been determined. This field is to be completed at the end of the phase.
      • Application Identified—Checkbox field for defining whether the application affected by the change has been determined. This field is to be completed at the end of the phase.
      • Server Identified—Checkbox field for defining whether the server affected by the change has been determined. This field is to be completed at the end of the phase.
      • Initiation End Date—Date field for noting when this phase is completed. This field is to be completed at the end of the phase.
    • Status set to Design Phase—When the Status field is set to Design Phase, the following suggested fields are shown in the RFC Information section:
      • Design Start date—Date field for when the phase began.
      • Design Action—Drop-down field for selecting the status of action in this phase. Values are:  In Progress, Completed, Insufficient Data.
      • IT Lead—Drop-down field for specifying the title of the individual who will be the leading IT person for the development of the change. Values are:  CIO, IT Director, IT Manager, IT Analyst.
      • Approximate Time to Complete—Estimate of the amount of time it will take to complete the design and implementation of the change.
      • Design Notes—Multi-line character field for notes.
      • Technical Specs Attached—Checkbox field for defining whether the Technical Specifications have been attached to the Issue. If checked, it means the specifications are attached .If not checked, it means the specifications are not attached.  This field is to be completed at the end of the phase.
      • Security Review Completed—Checkbox field for defining whether the Security Review has concluded. If checked, it means the review has been completed. If not checked, it means the review has not been completed. This field is to be completed at the end of the phase.
      • Impact Review Completed—Checkbox field for defining whether the Impact Review has concluded. If checked, it means the review has been completed. If not checked, it means the review has not been completed. This field is to be completed at the end of the phase.
      • Design End date—Date field for noting when this phase is completed. This field is to be completed at the end of the phase.
    • Status set to Development Phase—When the Status field is set to Design Phase, the following suggested fields are shown in the RFC Information section:
      • Development Start Date—Date field for when the phase began.
      • Development Action—Drop-down field for selecting the status of action in this phase. Values are:  In Progress, Completed, Insufficient Data.
      • Primary Developer—Drop-down field. The title of the individual who will be the leading developer on the project. Values are IT Director, IT Manager, IT Developer, IT Analyst.
      • Development Notes—Multi-line character field for notes.
      • Code Review Completed—Checkbox field for defining whether the Code Review has concluded. If checked, it means the review has been completed. If not checked, it means the review has not been completed. This field is to be completed at the end of the phase.
      • Development End date—Date field for noting when this phase is completed. This field is to be completed at the end of the phase.
    • Status set to QA Testing Phase—When the Status field is set to Design Phase, the following suggested fields are shown in the RFC Information section:
      • QA Testing Start—Date field for when the phase began.
      • QA Action—Drop-down field for selecting the status of action in this phase. Values are:  Not Started, In Progress, Completed, Insufficient Data.
      • Primary Tester—Drop-down field. The title of the individual who will be the leading tester on the project. Values are IT Director, IT Manager, IT Developer, IT Analyst, QA Analyst, QA Manager, QA Director.
      • QA Testing Notes—Multi-line character field for notes.
      • Functionality Verified—Checkbox field for defining whether the test results are verified. If checked, it means the functionality has been verified. This field is to be completed at the end of the phase.
      • Usabillity verified—Checkbox field for defining whether the usability test results are verified. If checked, it means the usability has been verified. This field is to be completed at the end of the phase.
      • QA Testing End date—Date field for noting when this phase is completed. This field is to be completed at the end of the phase.
      • Status set to Implementation Phase—When the Status field is set to Design Phase, the following suggested fields are shown in the RFC Information section:
      • Implementation Start Date—Date field for when the phase began.
      • Implementation Action—Drop-down field for selecting the status of action in this phase. Values are: Not Started, In Progress, Completed, Insufficient Data.
      • Implementation Plan—Multi-line character field for describing the implementation plan.
      • Back-out Plan—Multi-line character field for describing the plan for backing out if there is a problem with the implementation.
      • Implementation Notes—Multi-line character field for notes.
      • Change Deployed—Checkbox field for defining whether the change has been deployed. If checked, it means the change has been deployed. This field is to be completed at the end of the phase.
      • User notified—Checkbox field for defining whether the users affected by the change have been notified of the change.  If checked, it means the users have been notified. This field is to be completed at the end of the phase.
      • Implementation End date—Date field for noting when this phase is completed. This field is to be completed at the end of the phase.
    • Status set to Rejected, Canceled, or Completed—These Statuses do not affect the display of other fields.
    • Status set to All Phases—All of the sections are expanded when the status is set to All Phases.
  • Address Book—The Address Book is a sub-database that contains all of the contact information for your organization members.  Each record in the Address Book is called a “Contact”. Organization members are referred to as “Contacts” in FootPrints. The Address Book can contain up to 100 fields (SQL/Access versions are unlimited) for employee data, including Name, Department, Phone number, Email address, etc.
    • Suggested Address Book Fields
      • Last Name (character field)
      • First Name (character field)
      • Email address (email address)
      • Department (character field)
      • Phone (character field)
      • Job Title (character field)

Service Portfolio

The Service Portfolio is a workspace for proposing and approving items to be included in the Service Catalog..

  • Built-in Fields
    • Brief Description—Single-line character field.
    • Priority—Drop-down field.
    • Status—Drop-down field.   Values are: New, Initiation Phase, Design Phase, Development Phase, QA Testing Phase, Implementation Phase, Rejected, Canceled, All Phases, Completed.
    • Summary of Change (Description) —Multi-line character field.  Used for complete description of the proposed change.
  • Service Proposal Details
    • Business Case—Multi-line text field.
    • Pricing Models—Multi-line text field.
    • Potential Customers—Multi-line text field.
    • Service Level Agreement—Multi-line text field.
  • CI Links - For BMC Configuration Management. BMC Configuration Management is an add-on module.
  • Owners and Notifications - The same as Assignees and Email
  • Address Book—The Address Book is a sub-database that contains all of the contact information for your organization members Each record in the Address Book is called a “Contact”. Organization members are referred to as “Contacts” in FootPrints. The Address Book can contain up to 100 fields (SQL/Access versions are unlimited) for employee data, including Name, Department, Phone number, Email address, etc.
    • Suggested Address Book Fields
      • Last Name (character field)
      • First Name (character field)
      • Email address (email address)
      • Department (character field)
      • Phone (character field)
      • Job Title (character field)

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

FootPrints Service Core Online Help 11.6