Skip to content
RYAN BRENTS / SERVICES / DOCUMENTATION
●LIVE · ATL
SERVICE 03 / 12
← 02 /ross-erp04 /integrations →

Documentation

Most legacy ERPs were never really documented — the people who knew them retired, and the manual is a rumor. I rebuild the map: the schema, the screens, the programs, the data flows — until the system is legible again, to your team and to your AI tools.

THE WORK — /DOCUMENTATION
01System reconstructionReverse-engineer an undocumented schema into a searchable data dictionary — every table, column, key, relationship, and valid-value list, with field-level lineage. The manual you were supposed to get on day one.
02Knowledge graphs & schema mapsTurn thousands of tables into something you can actually navigate: a force-directed graph, path-finding between objects, and module grouping — so 'how does this connect to that' takes a click, not a career.
03Process & integration docsDocument EMF interfaces, alerts, and integrations end-to-end from their real configuration — the node graph, the wiring, the failure modes — instead of from whoever still remembers building them.
04Web services & API surfaceMap every integration entry point: SOAP/Connect web services with typed parameters, field mappings, and the tables behind each one. The surface your integrators keep asking about — 233 of them on rossdata.dev alone — finally written down.
05Machine-readable outputNot a 400-page PDF nobody opens. A REST/JSON API and an MCP server, so your systems, your dashboards, and your AI tools can all query the documentation directly.
THE PROOF — IN PUBLIC

I documented all of vanilla Ross 8.0. Then I put it online.

1,840 tables, 36,230 columns, 233 web services — a public data dictionary, knowledge graph, REST API, and MCP server for a system its own vendor barely documents.

SEE THE WORK →
Documentation — signal-routing art
PROOF IN PUBLIC — LIVErossdata.dev

The Ross ERP 8.0 schema, made legible.

I documented all of standard, vanilla Ross — every table, column, key, screen, and web service — and put it online. A searchable data dictionary, an interactive knowledge graph, 233 documented SOAP/Connect web services, a public REST API, and an MCP server your AI tools can query directly. No login, no vendor, no NDA. It is the most honest proof I can offer that I know this system down to the column — which, it turns out, is a strange thing to be able to say out loud.

OPEN ROSSDATA.DEV →
233
WEB SERVICES
1,840
TABLES
36,230
COLUMNS
2,327
SCREENS
THE WRITING — RELATED
2026-07How to think about modernizing Ross ERP in 2026→2026-07RAG for manufacturing documentation→
SEE ALSO
/ross-erp/analytics/ai

sitting on a system nobody documented — one email starts it

hello@ryanbrents.comCOPIED ✓
NO CALENDAR LINKS · NO FUNNEL · JUST MAIL

rossdata.dev documents standard, vanilla Ross only — never a customer's system. Point the same toolchain at your own instance and it stays private, yours, and behind your login.