English

Granite Construction Switches to ALLOut: Streamlined, and at a Fraction of the Cost

Granite Construction Switches to ALLOut: Streamlined, and at a Fraction of the Cost

Home Case Studies – Articles – Webinars – White Papers

Granite Construction Switches to ALLOut: Streamlined, and at a Fraction of the Cost

Chris Noack, Patrick Merrill, and Lynne Levassar from Granite Construction share how their switch to ALLOut Security transformed Segregation of Duties (SoD) management, control, audit readiness, and operational simplicity.

Download Case Study

Client in Focus

Granite Construction Switches to ALLOut: Streamlined, and at a Fraction of the Cost by Dr. Frosoulla Kofterou

Founded in 1922, Granite Construction is one of the U.S.’s leading infrastructure contractors, delivering large-scale projects across transportation, water, and renewable energy. Guided by values of safety, and sustainability, Granite continues to build America’s infrastructure with a focus on innovation and culture.

Challenge

Granite’s previous third-party solution led to inefficiencies across Finance, Audit and IT, requiring complex data transfers, manual reconciliation, and extended audit cycles. Reporting via fragmented workflows took months to complete, with more than 80 hours of reconciliation effort per audit.

Solution

By switching to ALLOut Security, Granite eliminated external data transfers, gained instant access to real-time, native JDE reporting, and reduced costs by approximately 75%. The familiar JDE interface and comprehensive training accelerated adoption across teams.

Results

Granite now runs self-service, audit-ready SoD reports quarterly, without manual reconciliation or fragmented workflows. The move has strengthened compliance, created IT efficiency, and positioned the company for long-term GRC success within JD Edwards.

Products Used

CombiRoles

ProfilePlus

Risk Management

Risk Reporting

SecurityPlus

SoDMaster

Download the full case study and learn how Granite Construction Switches to ALLOut: Streamlined, and at a Fraction of the Cost

Download Case Study

Events

10 Sep 2026, 1:30 pmALLOut & Version 1 JD Edwards Customer Day10 Sep 2026, 1:30 pmJoin ALLOut & Version 1 for an exclusive Oracle JD Edwards customer event focused on AI, automation, analytics, cloud integration, and enterprise…Read more

Upcoming Live Webinars

21 Jul 2026The Future of JDE Security Starts Now21 Jul 2026As JD Edwards environments are becoming more connected, security must be a priority now, not later. Operating without a well-managed security model…Register now

Empower your security team

Save time, enhance risk visibility and be audit-ready with ALLOut Security for JD Edwards.

Request a Demo

These cookies allow us to recognise and count the number of visitors and see how visitors navigate our website. This helps us to improve the way our website works.

Cookie name	Default expiration time	Description
_ga	2 years	Used to distinguish users.
_gid	24 hours	Used to distinguish users.
_ga_<container-id>	2 years	Used to persist session state.
_gac_gb_<container-id>	90 days	Contains campaign related information. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.

These cookies allow us to recognise and count the number of visitors and see how visitors navigate our website. This helps us to improve the way our website works.

Cookie name	Default expiration time	Description
_ga	2 years	Used to distinguish users.
_gid	24 hours	Used to distinguish users.
_ga_<container-id>	2 years	Used to persist session state.
_gac_gb_<container-id>	90 days	Contains campaign related information. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.

visitor_id<accountid>	The visitor cookie includes a unique visitor ID and the unique identifier for your account. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, makes sure that the visitor is tracked on the correct Pardot account. The visitor value is the visitor_id in your Pardot account. This cookie is set for visitors by the Pardot tracking code.
pi_opt_in<accountid>	If Tracking Opt-in preferences is enabled, the pi_opt_in cookie is set with a `true` or `false` value when the visitor opts in or out of tracking. If a visitor opts in, the value is set to `true`, and the visitor is cookied and tracked. If the visitor opts out or ignores the opt-in banner, the opt-in cookie value is set to `false`. The visitor cookie is disabled, and the visitor is not tracked.
visitor_id<accountid>-hash	The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. This cookie is a security measure to make sure that a malicious user can’t fake a visitor from Pardot and access corresponding prospect information.
lpv<accountid>	This LPV cookie is set to keep Pardot from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view.
pardot	A session cookie named pardot is set in your browser while you’re logged in to Pardot as a user or when a visitor accesses a form, landing page, or page with Pardot tracking code. The cookie denotes an active session and isn’t used for tracking.

visitor_id<accountid>	The visitor cookie includes a unique visitor ID and the unique identifier for your account. For example, the cookie name visitor_id12345 stores the visitor ID 1010101010. The account identifier, 12345, makes sure that the visitor is tracked on the correct Pardot account. The visitor value is the visitor_id in your Pardot account. This cookie is set for visitors by the Pardot tracking code.
pi_opt_in<accountid>	If Tracking Opt-in preferences is enabled, the pi_opt_in cookie is set with a `true` or `false` value when the visitor opts in or out of tracking. If a visitor opts in, the value is set to `true`, and the visitor is cookied and tracked. If the visitor opts out or ignores the opt-in banner, the opt-in cookie value is set to `false`. The visitor cookie is disabled, and the visitor is not tracked.
visitor_id<accountid>-hash	The visitor hash cookie contains the account ID and stores a unique hash. For example, the cookie name visitor_id12345-hash stores the hash “855c3697d9979e78ac404c4ba2c66533”, and the account ID is 12345. This cookie is a security measure to make sure that a malicious user can’t fake a visitor from Pardot and access corresponding prospect information.
lpv<accountid>	This LPV cookie is set to keep Pardot from tracking multiple page views on a single asset over a 30-minute session. For example, if a visitor reloads a landing page several times over a 30-minute period, this cookie keeps each reload from being tracked as a page view.
pardot	A session cookie named pardot is set in your browser while you’re logged in to Pardot as a user or when a visitor accesses a form, landing page, or page with Pardot tracking code. The cookie denotes an active session and isn’t used for tracking.