Project Insight vs. Trimble ProjectSight

My rating would vary depending on the types of projects that need to be managed. Since I am in software, I don't think it was an excellent fit to manage software projects unless they are small projects with only a few tasks. On the other hand, if you are needing to manage a wide range of departments that are working on a single project with many moving pieces, then I would think that PI might be a better fit. Think of it as a jack of all trades, but master of none.

Incentivized

I would probably recommend Trimble ProjectSight (Prolog) over Procore, as it is an easier user interface and typically avoids any problems with the users. I would say that it does take some getting used to, but once you are used to it it is pretty easy to use. This would be good for a residential home in construction.

Incentivized

• History tracking for any changes made to data.
• Tracks all milestones and retains records for lifetime of account.
• Easy extracting for reporting purposes.

Incentivized

• Change orders: great way to send and document official communications to subs and clients.
• Drawings: always good to have drawings and info readily available.

Incentivized

• Not a good fit for all types of projects
• Very Complex

Incentivized

• speed. Some items take a bit long to bring up.
• more direct use for individual specifications

Incentivized

I found Project Insight somewhat opaque overall. I thought the training was sparse and answers to questions few and far in between. There was a lot of power there for the dedicated user/administrator. For me, who was a casual user and administrator, I found support lacking. I didn't administer Project Insight much, just some work on integrations with other tools.

Incentivized

• When I got to the company where I used Project Insight, we had our own custom tool that fit the tasks that it was designed for but wouldn't grow with the company unless resources were put onto expanding capabilities. We needed something more.
• We replaced that tool with Redmine. It worked well and was easy to use, but it looked pretty dated when we got it, and since we didn't have many resources for managing, it looked dated after a few years without receiving upgrades. It was a decent tool for small teams that were focused on similar tasks. Redmine was much more straightforward than Project Insight and felt more reliable since we never had an issue with our internal servers. On the other hand, Redmine felt dated and didn't fit as many of the tasks that were needed. Redmine's price was right if you installed it locally and was probably still cheaper if you used their SAAS version.
• Jira, on the other hand, felt like an excellent tool for software teams. Jira had a great project and task management and felt right for a software team. Jira also had useful integrations, even with Project Insight. Jira seemed pretty unreliable, worse than Project Insight. Our team would have preferred Jira, but I think it didn't work for other teams.

Incentivized

I have only used Procore otherwise, and from what I remember Procore does not have as many features in terms of keeping track of CD documents, and organizing RFI's like Trimble does. I think overall Trimble ProjectSight (Prolog) is a better product, and if it was up to me I would pick Trimble ProjectSight (Prolog) over Procore.

Incentivized

• Reduction in costs on materials (i.e. - paper documentation)
• Improved efficiency given that our field members need to report back on an hourly basis
• Web based platform allows anyone access to the same information

Incentivized

• Positive: kept jobs running smoothly, awesome tool to track and oversee projects
• Negative: not much really, good tool, just very in-depth with information that is needed to fill in documentation

Incentivized