The Siemens Community Catalyst program was co-created with our community to acknowledge technology leaders who consistently contribute to the Siemens Community. Nominations are accepted on a rolling basis.
The following books were published in July 2026 in ebook and paperback formats:
All these books are described in detail and can be purchased using the following links:
https://community.altair.com/discussion/66872/three-new-books-on-altair-slc-now-available?utm_source=community-share
Altair SLC 2026 series: Introduction to posts Twenty-four ready-to-post items promoting the three Altair SLC books, eight for each. No topic appears twice. Where a subject is covered by more than one book it has been assigned to the book that treats it most fully, so the three sets could be scheduled in any order without repeating any information. The three books at a glance Book Pages Audience to aim the posts at Book A — Advanced Altair SLC: Comparing Altair SLC with SAS Software 210 Experienced SAS programmers. Technical detail earns the engagement here; lead with the specific. Book B — Altair SLC for Business Users 207 Programmers and analysts doing the daily work. Practical, problem-and-answer posts. Book C — Altair SLC for Companies 142 Managers, architects and procurement. Cost, risk and migration; keep these the shortest.
All three are by Philip R Holland and Pablo Orosco Joerger, 2026 edition, first printing, July 2026. https://hollandnumerics.org.uk/book-table https://www.lulu.com/spotlight/hollandnumerics Each post will include the purchasing links above, but also a link back to this post to explain the target audiences.
Run the analysis once. Publish it five ways.
ODS DOCUMENT captures the output of a procedure. PROC DOCUMENT replays it later to a different destination, in a different style, without running the analysis again.
It is one of the most useful things in the Output Delivery System, and one of the least used. Altair SLC supports it, and Book A works through a complete example.
The same chapter sets out where the ODS implementation in Altair SLC matches SAS software, and where it does not.
Advanced Altair SLC, chapter 2.
Book B: Altair SLC for Business Users
Altair SLC is a runtime, not an interface.
That distinction matters, because there are several ways to reach it: Analytics Workbench, the command line, Visual Studio Code, a remote server, or another application driving it.
Book B lays the routes out plainly, so that a new user knows which one they are actually using, and why the same program can behave differently depending on how it was started.
Altair SLC for Business Users, sections 2.1 to 2.2.
Why are organisations moving to Altair SLC?
Four reasons, and Book C gives the detail behind each. Cost, from a subscription model with a lower upfront commitment. Flexibility, from multi-language support for Python, R and SQL and an open architecture that fits an existing pipeline. A modern approach, with current machine learning and automation. And a comprehensive feature set under a single licence, rather than assembled from separately priced modules.
Written for the people who have to sign it off, not for the people who will use it.
Altair SLC for Companies, sections 3.1 to 3.2.
