CH & Co, a large UK-based contract catering company, successfully upgraded from Oneworld Xe to JD Edwards EnterpriseOne 9.1 using the ALLOut Security tool-set. The tools facilitated the efficient management of complex roles, tasks, and security setups, saving significant time and resources. The upgrade improved administrative processes and enhanced system security and compliance.
CH&Co Group is a prominent catering and hospitality company featuring a diverse range of specialized businesses. They offer services spanning from consumer and fully commercial catering to fixed-cost catering for some of the UK’s top brands and organizations. Their expertise extends across various sectors including business and industry, charity, leisure, education, and healthcare.
CH & Co faced a significant challenge during their upgrade from Oneworld Xe to JD Edwards EnterpriseOne 9.1. The company, a large contract caterer with over 200 establishments and 2,500 staff, needed to integrate complex roles, versions, security, and task views into their new system. The rapid expansion of their business required adding over 30 new units to the EnterpriseOne system within days, a task further complicated by the limited IT expertise of their staff. The scale of the upgrade involved designing and implementing 1,000 tasks and 5,000 task relationships within a tight timeframe, making traditional methods unfeasible.
To address these challenges, CH & Co implemented the ALLOut Security tool-set, which offered a streamlined approach to managing their system upgrade. This tool allowed them to design roles, tasks, and security structures using spreadsheets, which were then uploaded into the system within minutes, drastically reducing setup time. By standardizing menus, folders, tasks, task views, and process-based roles, and introducing role-based security and structured audit routines, they ensured a smooth transition to the new system. This approach not only facilitated the project within the required timescales but also simplified ongoing administrative maintenance.
The use of the ALLOut Security tool-set yielded significant benefits for CH & Co. The automated import and validation of menu, security, and role setup spreadsheets saved approximately 20 man days of setup and testing time. The simplified template approach enabled the accounts team to manage security and menu maintenance, eliminating the need for a specialized JDE IT security admin role. Furthermore, the compliance procedures supported by ALLOut’s Risk Reporting enhanced system access and usage oversight, addressing auditor concerns and ensuring robust security and efficiency in their upgraded EnterpriseOne environment.
We use cookies to give you the best online experience. By agreeing you accept the use of cookies in accordance with our cookie policy. You can always revoke your consent by clicking on the icon at the bottom left of the screen.
When you visit any web site, it may store or retrieve information on your browser, mostly in the form of cookies. Control your personal Cookie Services here.
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. |
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. |