What Nexus PLM does

Nexus PLM is made of focused apps that share one data model, one permission system and one audit trail. Below is what each one is for. The platform is in active development — some of this is solid, some is still moving, and we will tell you which is which on a call.

Work management

Home — a configurable dashboard of tiles. Pin the boards, folders and objects you touch daily so they are one click away.

Projects — group work into projects with owners, members and shared folders. Objects link back to the project that produced them.

Programs — a level above projects, for when a body of work spans several of them.

Schedule — tasks, milestones and dependencies on a Gantt view, tied to the change and project records rather than kept in a separate plan.

Folders — the working filing system: nested folders, configurable columns, rollups and aggregates, CSV export and bulk import, check-in and check-out.

My Tasks — everything waiting on you in one inbox: approvals, review requests, assignments and acknowledgements.

Favorites and Quick Access — shortcuts to the records you return to most.

Change management

Problems — raise a problem report against a part, document or assembly, with the evidence attached.

Issues — a lighter-weight tracker for defects and follow-ups that do not warrant the full change process.

Changes — engineering change requests: what is proposed, why, what it affects, and who needs to agree.

Orders — approved change orders, carrying the affected items and the approval trail that authorised them.

Notices — change notices announcing what was released, to whom, and from when.

Kanban and Boards — board views over any of the above, with lanes you define and drag-and-drop between states.

Product data

Structure and BOM — assembly structure built by hand or pulled from CAD. Every object shows what it is made of and where it is used, so a proposed change surfaces every assembly it touches.

Requirements — capture requirements, link them to the parts and documents that satisfy them, and trace coverage both ways.

Classification — classify parts against a hierarchy so equivalent items are findable instead of being re-created.

Industry Standards — reference standards held as first-class records with their own revisions and datasets.

Costing — cost fields, rollups up the BOM, baselines and target allocation, so a structure change shows its cost consequence.

Tables — structured tabular data edited in place and embedded live into documents.

Contacts — people and organisations, grouped, with avatars and extended attributes.

Search and AI

Search — full-text indexing across object attributes and document contents, including PDFs and Office files. Results respect permissions, so you only see what you are allowed to see.

Advanced search — attribute-level queries with per-type fields and configurable result columns.

Nova — a built-in assistant that answers from your data and your own help library rather than from generic training, and links to the records it used.

Administration

Data Model — define your own object types, their attributes, lifecycle states and inheritance, plus actions and reactions that fire when something changes.

Numbering and ID rules — part numbering schemas and identifier rules, enforced centrally so numbers stay unique.

Workflow Designer — build approval flows visually: states, transitions, gates, notifications and rework loops.

Users and permissions — users, groups and per-type visibility rules, so records are shared deliberately rather than by default.

Integrations — outbound email, Slack and Teams notification channels.

Monitor and Indexing — service health and search-index status.

Reports — saved queries and exports over the object model.

Discussions — threaded comments attached to records, so context lives with the object.

Help — a built-in documentation library your team writes and Nova reads.