Arc FAQ
Arc FAQ
Answers to the most common questions about Arc for IBM Planning Analytics (TM1).
General
What is Arc?
Arc is an integrated development environment (IDE) for IBM TM1 and Planning Analytics. It provides a centralised platform for all TM1 development, giving you access to all your on-premise and cloud environments from a single location.
Arc is built to take advantage of features in Planning Analytics (TM1 11+) such as hierarchies and Turbo Integrator debugging.
How much does it cost?
Arc comes with a three-month trial period. After the trial, a subscription is required to continue using Arc. Subscriptions are available for organisations (monthly or yearly) and individuals (monthly only). Pricing details are available on the Arc pricing page.
Configuration
What are the Arc prerequisites?
Arc is officially supported on TM1 11+ (Planning Analytics 2+). Most features work with TM1 10.2.2, but a number of important APIs are only available in TM1 11+.
The TM1 REST API must be enabled by setting
HTTPPortNumberintm1s.cfg, e.g.HTTPPortNumber=8111.To enable Turbo Integrator debugging, add
EnableTIDebugging=truetotm1s.cfg.Restart the TM1 service after making changes to
tm1s.cfg.
What security modes does Arc support?
Arc supports all IBM Planning Analytics security modes that require a password, including Native TM1 security, Windows security, CAM, OpenID, IBM ID, and IBM PA SaaS v12 security keys.
Where should I install Arc?
Arc should ideally be installed on the same server where TM1 is running. This allows Arc to access ODBC data sources and text files on the TM1 server. If Arc is installed on a separate server or desktop, it will function normally except for ODBC and Text preview features in Turbo Integrator processes.
See the Where to Install Arc for TM1 page for a full discussion of deployment options.
How do I hide or unhide the history tab in Slice?
The History tab in Slice is controlled by the Page History Maximum setting. If this value is set to 0, the history tab will not be shown.
To show the history tab, set Page History Maximum to a value greater than 0.
Can a non-admin user lock an element in Arc?
No. The lock/unlock element option in the subset editor context menu is only available to users with a global Admin or DataAdmin user type. Having ADMIN security rights on the dimension itself is not sufficient.
In Arc, the permission check is based on the user's global type, not on dimension-level security assignments. This means a regular user — even one with ADMIN access to a specific dimension — will not see the lock option in the context menu.
This differs from IBM Perspective, which may handle this permission check differently.
Workaround: If you need a non-admin user to be able to lock elements, promote them to DataAdmin or Admin at the global level.