Construction and Energy

Case Study

Faster Project Risk Assessment and Access to Information for Daily Operations

Industry Vertical and Application Type:

Construction and energy, professional services project management

Workflow Steps Accelerated:

Project risk assessment, access to information for day-to-day project operations

Challenge: Project managers at a large engineering firm needed to look at specific parameters to assess the risks of potential large-scale, engineering projects in order to decide whether they were worth taking on. In complex construction projects, project managers need to be able to silo data between unionized and non-union labor through internal controls, and adhere to compliance and visibility policies. For example, although the project managers had access to how much unionized and non-unionized labor was being paid and the hours they were logging, the two groups were not allowed to see each other’s data. This challenge was tricky, as the systems are complex and interconnected, especially within the energy sector.

Solution: The engineering firm chose KonaSearch because its robust security checks the users’ permissions on each system, ensuring they only access the data they are permitted to view. Because KonaSearch presents results from multiple data silos in a single relevancy-ranked list, users can review all the relevant data without making multiple searches on multiple systems.

Impact: Project managers spend more time managing and less time being an information switchboard between different parties on a project. Project managers also need less time to evaluate the risks and benefits of potential new projects.

How KonaSearch Applies Permissioning Across Different Data Sources

When a user is searching through KonaSearch, the user’s identity (the system they are logged into) is included with the query sent to the KonaSearch server, so that KonaSearch can determine which results the user is allowed to see from ALL content in its index. KonaSearch connects the different identities for the user either: within its index; calling out to the client’s identity manager (such as Ping Identity, Active Directory, or Salesforce Identity); or through a piece of logic, such as a common email address.
KonaSearch resolves which results the user is allowed to see either by comparing the identity against source results that use Access Control Lists (ACLs), or logically, because KonaSearch has indexed the permissioning model rather than use ACLs.