| Requirement | Minimum | Recommended |
|---|---|---|
| OS | Windows 10, macOS, or Linux, 64-bit | Windows 11, macOS, or Linux, 64-bit |
| RAM | 8 GB | 16 GB or more |
| Disk | 500 MB for the application | 20 GB, to hold extracts and results |
No administrator rights, no runtime to install, and no network access required beyond the licence check.
What drives memory use
MTC Skopos holds the loaded dataset in memory, which is what makes analysis on millions of authorization rows fast. Memory use therefore tracks the size of your extracts, not the size of the application.
The dominant factor is AGR_1251, the role authorization table, which on a large productive system commonly runs to millions of rows. Two rules of thumb:
- One large productive SAP system is comfortable in 16 GB
- Several large systems loaded simultaneously, which cross-system analysis needs, is where 32 GB starts to pay for itself
If an analysis is slow or the application is under memory pressure, unload the data sources you are not analyzing. See Managing Data Sources.
What drives disk use
The application itself is small. The space goes to:
- Your extracts.
CDPOS, needed for Did-Do analysis, can exceed 50 GB on its own - The CDPOS index, built beside the file, roughly 24 bytes per distinct change document
- Analysis results. A detailed report on a large landscape reaches several gigabytes, because it holds one row per contributing authorization
The 20 GB recommendation assumes ordinary extracts. Budget separately if you intend to work with change documents on a large productive system.
Scaling behaviour
Analysis is parallelized across cores, so more cores shorten a run. Nothing requires a GPU. An SSD helps materially when working with change documents, because indexing and filtered reads are I/O-bound.