Intake shaped by OPERA Controls
Start from a single-sheet controls checklist rather than a blank workbook. What the property activates decides what you are asked for, so you only answer the questions that apply.
SCS Tech / ApplicationsA better workbook.
01 / Prepare your configuration
A better workbook.
A stronger start.
Property intake, a recommended-codes library, automatic transaction-code and tax generation, and readiness checks in one working space. Build the configuration your property actually needs, instead of starting every Accelerator workbook from an empty sheet.
ARK Workbook Studio
From property inputs to reviewed data
Property intake (OPERA Controls)Captured
Recommended codesSelected
Transaction codes + generatesBuilt
Readiness findingsCleared
Accelerator exportReady
Illustrative preparation workflow. Draft rows are reviewed before delivery.
Built inOman tax chain, with a generic engine for other markets
Entry methodDropdown-driven for referenced values
ExportAccelerator-style Excel, per configuration item
What it brings to your team
Less spreadsheet effort.
More room for good decisions.
A library instead of a blank sheet
Pick from a maintained library of recommended codes and adapt them to the property. The library keeps growing, so each new property needs less hand-entry than the last.
Transaction codes built from your outlets
Name your revenue centres and the serving periods each one runs, and the matching transaction-code set is generated for you. Banquet all day, a bar on dinner and supper, in-room dining across every period.
Tax generates calculated, not retyped
Define each charge by its percentage, what it calculates on, and which subtotal it feeds. Oman’s standard chain is built in; the engine stays generic, so another market only needs its own rules supplied.
Dropdowns where values must match
Fields that reference already-configured items are dropdowns, not free text. Codes cannot be invented mid-workbook, so what you export still lines up on import.
Bulk edits three ways
Work in the grid, round-trip an Excel working file, or describe the change in plain English. Natural-language edits are previewed before anything is applied.
Readiness checks before handover
Findings point at incomplete, invalid, or orphaned rows and link straight to the item that needs attention. Fix data while it is still cheap to fix.
Work that survives the week
A configuration build runs over days. Projects persist across refreshes, closed browsers, and restarts, so nobody rebuilds a morning’s work.
Workbook Studio prepares and reviews data. It does not write to your live OPERA Cloud environment. Natural-language bulk editing requires its AI service to be configured. Supported configuration items and export formats are confirmed during scoping.
The workflow
From requirements to a reviewed workbook.
Capture
Run the controls checklist and property intake to establish what this property actually uses.
Generate
Pull in recommended codes, build transaction codes from your outlets, and calculate generates.
Review
Bulk-edit in the grid, Excel, or plain English, then clear the readiness findings.
Deliver
Export Accelerator-style workbooks per configuration item, or hand the data straight to Configurator.
Start with a clear scope
Onboard within 7 days.
Build from there.
We’ll agree supported configuration, prepare access, and help your team get started. Required data and access must be in place; delivery follows the agreed project plan.
Your next configuration starts here
Less configuration effort.
More room to move.
Opening a property, moving to OPERA Cloud, or improving your existing setup? Tell us what you are working with and we will tell you honestly whether we can help.
Email ark@scstech.me · WhatsApp +968 9390 0840