BMC FootPrints Reviews and Ratings

Use Cases and Deployment Scope

I use BMC FootPrints to keep the tracking of product demos and proofs of concept with the customers, we have different workspaces, one for presales, other for the projects, other for end user's comments, other for end customer's support, and the last one for internal support. This product really doesn't face any problems, the only thing that I can say is that the interface is a little bit ugly, there out is a lot of software more friendly but Footprints is really functional for us, it has so many configurations to accomplish the tasks that we need.

Likelihood to Recommend

BMC Footprints is so well suited to keep the documentation easy to read and find, as same as typification. You can find specific documentation for an audit so fast and export a report using the specific criteria that you need to comply with your boss or audit needs. As I told before, BMC footprints need to be more friendly to the end users because they get lost many times trying to track some ticket or typing documentation.

Use Cases and Deployment Scope

We use it to track our projects and what phase they are in. Tickets can be Open, in-progress, Pending, requires follow up, completed. This allows all our team members to keep track of the status of each project. We trace our Classroom maintenance requests, so we don't forget any requests, it also sends an email to the requestor once the project is completed.

Likelihood to Recommend

Tracing any maintenance requests, so you don't forget any requests, it also sends an email to the requestor once the project is completed.

Keeping status of projects in progress and the current state they are in. Allowing anyone with access to know the current state of any project. Generating a useful report is a bit more difficult then I would like.

Use Cases and Deployment Scope

We have been using it for around 5 years, and we use it in Outsourced departments. Our client helpdesk uses it for tracking trouble tickets from our clients and resident engineers, our project management dept uses it for tracking IT projects of the clients, our programmers use it for change management, and my network team uses it for tracking problem tickets and network changes. It helped us maintain compliance, as well as to grow a large history of all problems and changes in our company.

Likelihood to Recommend

FootPrints really can be well suited for any company large or small. We have millions of tickets in the system and that gives us a long history of tickets to look back on when needed.

Use Cases and Deployment Scope

In our current configuration, BMC FootPrints is being used by the IT department. FootPrints allows our end-users to submit trouble tickets for issues for their computers, phones, prints, or network issues. The IT department also uses FootPrints to document and track internal projects and tasks. Other areas in the organization are also looking to implement FootPrints in their areas for namely the same reasons of tracking and documentation.

Likelihood to Recommend

BMC FootPrints does helpdesk ticketing very well for us in our IT department. In general, any scenario that requires some way to enter in, track and report on issues for enterprise users is the best fit. We've been doing this for more than 10 years on different versions of FootPrints. Where I would not see this as a good fit is probably is for smaller deployments of less than 50 users.

Use Cases and Deployment Scope

We have been using FootPrints for around 15 years, and we use it in multiple departments. Our helpdesk uses it for tracking trouble tickets from our stores and field users, our project management dept uses it for tracking IT projects, our programmers use it for change management, and my network team uses it for tracking problem tickets and network changes. It helped us maintain Sox and PCI compliance, as well as to grow a large history of all problems and changes in our company.

Likelihood to Recommend

FootPrints really can be well suited for any company large or small. We have millions of tickets in the system and that gives us a long history of tickets to look back on when needed, so it's really helpful for tracking anything. Larger companies might find some of the more expensive ITSM products more useful, as they do offer more features, but I really think anybody could get by using FootPrints just as well for cheaper.

Use Cases and Deployment Scope

It is being used across the organization by each department. BMC FootPrints is set up by what is called 'workspaces'. These are each designed for different workflows and are each independent databases. We use it for CAPA events, as well as tracking customer products that can not be received to an error in the receiving documentation.

Likelihood to Recommend

Use Cases and Deployment Scope

FootPrints is being used by the company I am consulting. We are tracking IT support issues, projects, and tasks associated to the projects. The system is being utilized by the entire company to submit and track any IT issues that need to be addressed.

Likelihood to Recommend

[It's] Well suited for tracking IT requests.

Use Cases and Deployment Scope

St. Luke's has used BMC's FootPrints for the last 7+ years and it has served the purpose of ticket management for Incident, Service Request, Change Mgmt, Customer Portal, Knowledge Base, and Service Catalog. The product has been deployed for departments both inside of IT and outside of IT including: Marketing, Finance, Human Resources, Supply Chain, and Project Management.

Likelihood to Recommend

Very well suited for small and emerging IT departments that need to provide basic Incident/Request Management, Change Management, and a basic customer portal. It is also a good tool for organizations who do not have well defined ITIL/ITSM Processes.

Use Cases and Deployment Scope

BMC FootPrints Service Core is used as the support ticketing system for various campus departments to help users troubleshoot issues that arise.

Likelihood to Recommend

BMC FootPrints Service Core is well suited for institutions that support large volumes. Being able to better categorize tickets is something I would like to see, akin to Gmail's labels and archiving.

Use Cases and Deployment Scope

The IT department of Cellular Sales used it to manage IT tickets for all types of support. The Operations Team (Tier 1), Systems (II), and Network (III) had access to it. Sales reps would send in tickets via email and they would be sorted in BMC and addressed.

Likelihood to Recommend

Who is the end user? They will get emails back with their ticket information. Make sure its easy to read and applicable.