Siemens Rulestream Documentation Suite

The Product

Rulestream ETO is Siemens' engineer-to-order platform — enterprise software that integrates with CAD, ERP, and other PLM (Product Lifecycle Management) systems. It enables manufacturing companies to automate engineering design and configuration for custom-built products.

This is highly technical, domain-specific software where documentation directly affects whether customers can configure integrations, understand system requirements, and adopt new features.

The Problem

I was Rulestream's first and only dedicated technical writer. When I started:

Legacy documentation hadn't been updated in nearly a decade
Customers were often unaware of features that had been rolled out — the only discovery mechanism was contacting support
No structured release communication existed — no release notes, no What's New content
The full product documentation suite needed to be rebuilt from the ground up

What I Built

I managed the complete documentation suite across all document types:

System requirements documentation — hardware, software, and environment specs for deployment
Install guides — step-by-step installation procedures for the platform and its integrations
Release notes & compendium — structured release communication covering new features, enhancements, and fixes across versions
Product integration guides — documentation for CAD, ERP, and PLM system integrations
UI/UX guides and user manuals — task-based documentation for end users
Reference documentation — technical reference for configuration and customization

I used Oxygen XML Editor and CCMS (Component Content Management System) to manage modular, reusable documentation at scale — each document type shared common components while maintaining its own structure and audience focus.

Impact

Customers could discover product releases immediately, helping marketing teams convert and upgrade users without relying on support.

Reduced support ticket volume by giving users self-service access to current install procedures, system requirements, and integration guides.

Updated the entire product documentation suite within 6 months — from a decade-old baseline to current, accurate, structured content.

Why This Matters

This project gave me experience owning documentation end-to-end at an enterprise scale — managing multiple document types, working with cross-functional teams (developers, testers, product management), and using structured authoring tools (XML, CCMS) to maintain complex, modular content. It's the foundation for the documentation ownership I've carried into every role since.