ARAS INNOVATOR ONLY
PageX: Role-Based Pages for Aras Innovator
Each role opens a part and gets one page with what it needs to decide — BOM, CAD, documents, quality events — on live Aras data, with the Aras core untouched.
- One Page per Role
- Upgrade-Safe by Design
THE PROBLEM
Seven Screens for One Decision
The answer is usually already in Aras. It sits across the part and the objects around it, and the user carries the context from screen to screen, many times a day. More training does not fix that. Fewer screens do.
Daily work where it costs the most
- Reviewing a change
- Finding the right revision
- Hopping across related items
- Exporting to Excel to compare
IN THE PRODUCT
One Page per Role, on the Same Aras Data
Five PageX pages. The first three are the same part, opened by design, quality and manufacturing. The other two are the pages a change analyst and a programme manager work from.
- BOM lines
- 8
- Total qty
- 13
- Distinct parts
- 8
- Classifications
- 2
Make vs buy
Share of BOM lines
- Make (6)
- Buy (2)
By state
Lines per lifecycle state
EBOM8
| Part number | Rev | Name | State |
|---|---|---|---|
| ASM-2026-0002073 | A | Differential Case Assembly | Released |
| ASM-2026-0002025 | A | Spider Gear Set | Released |
| PRT-0000063 | B | Taper Roller Bearing | Released |
| ASM-2026-0002076 | A | Seal Kit Assembly | Preliminary |
CAD3
| Document | Rev | Type | State |
|---|---|---|---|
| CAD-00000065 | C | Mechanical / Assembly | Released |
| MP2580 | C | Mechanical / Part | Released |
| CAD-00000065D | C | Mechanical / Drawing | Released |
Documents
LoadingMaterials
LoadingSpecial Process
LoadingCharacteristics
LoadingCAPA2
| CAP number | Problem | Severity | Status |
|---|---|---|---|
| CAP004 | Bearing seat roughness above limit | 4 | New |
| CAP001 | Thermal hazard at the housing | 3 | In Work |
Quality event PR-100032
- Title
- Non-compliance: CH-00077
- Severity
- Status
- Submitted
- Affected item
- PRT-0000061 Differential Assembly
- Problem
- Bearing seat finish is specified at Ra 1.6 µm; REQ-000000057 limits it to Ra ≤ 0.8 µm.
- Verification
Characteristic CH-00077
- Feature
- Bearing seat roughness
- Target
- Ra 1.6 µm ± 0.4
- Limit
- Ra ≤ 0.8 µm
Requirements2
| Document | Title |
|---|---|
| REQ-000000057 | Bearing surface finish |
| STD-0000002 | Machining standard |
Characteristics
Loading- Operations
- 5
- Special processes
- 3
- Material
- 1
- Open change
- 1
Process plan5
| Op | Operation | Work center | Special process |
|---|---|---|---|
| 10 | Casting | Foundry | — |
| 20 | Shot blasting | Finishing | SP-0000011 |
| 30 | Heat treatment | Furnace 1 | SP-0000005 |
| 40 | Machining, bearing seats | CNC-4 | — |
| 50 | Phosphate coating | Finishing | SP-0000014 |
Material MAT-0000009
- Grade
- Grey cast iron FG 260
- Form
- Sand casting
- State
- Released
Open change ECN-0001482
- Change
- Bearing seat finish
- Affects
- Op 40, machining
- Your review
- Waiting
Special Process
LoadingWork Instructions
Loading- Affected items
- 3
- Where used
- 2
- Documents
- 4
- Approvals
- 1 of 3
Affected items3
| Item | Name | Revision | Action |
|---|---|---|---|
| Differential Assembly | E → F | Revise | |
| PRT-0000063 | Taper Roller Bearing | B → C | Revise |
| DOC-0000258 | Bearing seat specification | A → B | Revise |
Where used2
| Assembly | Rev |
|---|---|
| ASM-2026-0003101 Rear Axle | B |
| ASM-2026-0003118 Drive Unit | A |
Approvals
- Design reviewApproved
- Quality reviewPending
- ManufacturingWaiting
Documents
Loading- Parts released
- 18 / 24
- Open changes
- 4
- Open CAPA
- 2
- Next gate
- DR3
Deliverables by state
Open changes by stage
Open changes4
| Change | Title | Status |
|---|---|---|
| Bearing seat finish change | In Review | |
| ECN-0001477 | Housing wall thickness | In Review |
| ECN-0001469 | Fastener kit second source | Approved |
| ECN-0001490 | Lubrication port relocation | Draft |
CAPA
LoadingMilestones
LoadingEVERY ARAS TEAM HAS FOUR OPTIONS
PageX, or One of the Alternatives
Aras gives you capable tools to configure forms, and an integrator can build almost anything. What decides it is the page your users need every day, who changes it next month, and what happens to it at the next upgrade.
Four ways to give Aras users better screens. Each is the right answer somewhere — the last row says where.
- Built for it
- Partly
- Not what it is for
| Configure standard Aras formsYour admin, with Aras tools | Integrator codes custom pagesBuilt to your specification | Dashboards outside ArasA BI tool next to PLM | PageXRole pages inside Aras | |
|---|---|---|---|---|
| One page for a role’s daily decision | Forms and grids, one ItemType at a time | Whatever was specified and paid for | Charts and reports to read | A part or change with its related items, per role |
| Acting on what you see | In Aras, item by item | In Aras, where it was built | Back in Aras, on another screen | In place, on the same page |
| Changing a page next month | An admin, with Methods for anything conditional | A change request to the integrator | A BI developer | Your team in PageX Builder, or us |
| At the next Aras upgrade | Copied core forms to re-check | Custom code to re-test | The data connection to re-check | Aras core untouched; upgrade support included |
| Choose it when | A simple form on one ItemType is enough | The requirement is genuinely unusual | The audience is management, across systems | People decide across related items, many times a day |
| PageXRole pages inside Aras | Configure standard Aras formsYour admin, with Aras tools |
|---|---|
| One page for a role’s daily decision | |
| A part or change with its related items, per role | Forms and grids, one ItemType at a time |
| Acting on what you see | |
| In place, on the same page | In Aras, item by item |
| Changing a page next month | |
| Your team in PageX Builder, or us | An admin, with Methods for anything conditional |
| At the next Aras upgrade | |
| Aras core untouched; upgrade support included | Copied core forms to re-check |
| Choose it when | |
| People decide across related items, many times a day | A simple form on one ItemType is enough |
HOW PAGES ARE BUILT
Configuration, Not Code
Pages are assembled in PageX Builder from a small set of parts, on the ItemTypes and relationships you already have. Sections load on demand, as the user opens them.
What a page is made of
- Page layoutThe skeleton every page starts from
- Data sectionsTable, form, card, tree grid view or structure
- HTML componentsA custom block where no standard section fits
- HTML fields and columnsA field or column inside a custom block
- Related-item columnsData from related items, in the same table
- Buttons and actionsRun a business action from the page
TWO WAYS TO START
Build the Pages Yourself, or Have Us Build Them
Both cover every Aras user and your production, development and test environments, with product updates and upgrade support from SteepGraph, an Aras partner since 2010. The difference is who builds the pages.
Your team builds
Framework licence
- Build and change pages in PageX Builder
- Training videos, release notes and feature videos
- Online and developer support
- Roadmap sessions twice a year
SteepGraph builds
Value pack
- Fixed price for the pages agreed at the start
- 1 to 4 months to system testing (SIT)
- Built by SteepGraph with AI-assisted development
- 10 hours of onboarding training over two weeks
Not part of PageX: new data model work, integrations and data migration.
GET STARTED
Bring Us the Screen Your Users Work Around
Name the Aras task people repeat all day. We will show it to you as one PageX page, on a model like yours.
FAQ
Questions About PageX
No. PageX is built for Aras Innovator and runs inside it. It is part of Rabbit User Adoption Studio, not one of our Frameworks — for work beyond Aras, see the Data Migration and Integration Frameworks.
Aras configuration works per ItemType or globally, and conditional behaviour needs Methods. A PageX page is built around a role and a decision: it brings the part and its related items onto one page, and your team changes it in PageX Builder without writing Methods.
ProAppDesigner is Aras’s tool for designing new applications: forms, workflows, dashboards and portals. PageX does one job. It gives each role one page for its daily work, with a part or a change and everything related to it on one screen. Users can act on that page directly. SteepGraph can build your pages for you, at a fixed price, in 1 to 4 months. Building a new application? ProAppDesigner is a good choice. Your data is already in Aras and your users need it in one place? Start with PageX. Both run on Aras Innovator.
No. Pages are configuration on the ItemTypes, properties and relationships you already have. The data model, workflows, permissions and vault stay untouched, which keeps PageX upgrade-safe, and product updates and upgrade support are part of every subscription. New data model work is a separate piece of work.
Every Aras user in your organisation. The licence covers your production, development and test environments.
Yes. With the framework licence your team builds pages in PageX Builder, with training videos and developer support from us. With the Value pack, SteepGraph builds the agreed pages at a fixed price and your team gets 10 hours of onboarding training.
With the Value pack, 1 to 4 months to system testing (SIT), depending on the pages agreed. UAT and go-live dates are set with you. It assumes access to your environments and a stable Aras baseline from the start.