A contracted service must be described, not narrated.
Descriptive Standardization of Services (PDS) means applying to the service catalog, within MDM (Master Data Management), the same discipline that PDM applies to materials: taxonomy by family, attribute templates, rule-generated descriptions, deduplication and tax classification. Without it, "preventive maintenance" turns into thirty different records, each with its own price and its own terms.
160 clients trust us
A poorly described service means the wrong NBS, lost credit and a rejected invoice
Pain
"Maintenance", "prev. maintenance" and "maintenance service" are the same contract. And the system doesn't know it.
Services enter the ERP as free text. Each buyer describes it their own way, each area creates its own code, and the same scope shows up with ten different prices. When it is time to negotiate, no one can add up the spend. When it is time to invoice, tax classification becomes guesswork.
Free text instead of scope, with no attribute to compare proposals
Spend fragmented across dozens of codes for the same service
NBS and service code defined by habit, not by rule
Measurement without a basis: without standardized scope, there is no SLA or supplier comparison
How we solve it
Taxonomy, template and rule: the service is described the same way, every time.
The same PDM engine applied to the service catalog, with the attributes that define scope, unit of measurement and frequency.
Maintenance, construction, IT, facilities, logistics, consulting and professional services organized in a single tree.
Each family gets the attributes that define it: scope, specialty, unit of measurement, frequency, location and SLA.
The taxonomy is built with your teams and becomes the standard for the entire company.
A template per family ensures short name, long description and scope in the same format, at any plant or branch.
The requester selects attributes instead of writing free text, and the record is comparable from the start.
Recurring services get identical descriptions, which makes it possible to measure price per unit of scope.
AI compares description, attributes and contracting history to find equivalent services.
Every merge goes through a specialist, with history recorded for audit.
With spend consolidated by service, negotiation regains scale and the reference price emerges.
A standardized description is what makes classification possible: a well-described item is a well-classified item.
Under the Tax Reform, NBS and the service classification define the IBS and CBS treatment and the credit taken.
Native integration with SAP, TOTVS, Oracle and the main ERPs, on the same connection that already serves materials and suppliers.
The standardized catalog becomes the basis for quotation, umbrella contract and measurement of services performed.
The approved supplier and the service it provides now live in the same source of truth.
Clear scope in master data means contracts without noise in execution.
Artificial intelligence
ADAM standardizes services — and sustains governance afterward
ADAM is 4MDG's artificial intelligence. It interprets the free-text description of the requested service, identifies the nature of the activity, proposes a standardized description with the right verb and object, suggests the tax classification and shows the equivalent service already registered.
Cleansing
Service catalog in order
In the initial load, ADAM rewrites and classifies the catalog all at once, groups what is the same service written in ten different ways and returns the standardized base.
New record
Standardized from the start
On every request, the suggestion arrives ready: standardized description, service class, tax code and the contract's unit of measurement.
Governance
A standard that does not degrade
The model keeps running on the production base, flagging standard deviations, duplicate services and missing information for the steward to handle.
The final decision is always human: ADAM suggests and your team approves, with an audit trail of who accepted or rejected each suggestion.
Results
A clean service catalog pays for itself.
Visible spend per service
With the same scope under a single code, consolidated spend becomes visible and negotiation gains a solid basis.
Faster contracting
Attribute-based requisition, with no free text, reduces back-and-forth between requester, procurement and legal.
Measurement and SLA made possible
Standardized scope and unit make it possible to measure delivered service and compare supplier performance.
Consistent tax classification
Consistent NBS and service codes reduce credit disallowance, assessments and rework in tax calculation.
AI-ready foundation
A structured catalog is what enables analysis, spend forecasting and automatic scope recommendation.
Comparable suppliers
The same service quoted with the same scope across approved suppliers, with no proposal window-dressing.
Step by step
How to standardize a service catalog in five steps.
01
Diagnosis
We measure duplication, insufficient descriptions and price dispersion in your current catalog.
02
Taxonomy
Families, subfamilies and attributes defined with the teams that contract the service.
03
Standardization
Description generated from a template, with scope, unit of measurement and frequency.
04
Deduplication
Equivalent services merged, with specialist curation and an audit trail.
05
Governance
Workflow and rules so every new service is created standardized and classified.
What was contracted, what was executed and what was measured finally speak the same language.
Contact
Request a free diagnostic of your service catalog.
We show duplicates, insufficient descriptions and price dispersion for the same scope. No commitment.
Av. Queiroz Filho, 1700, Torre E, Conjuntos 715 a 718
Vila Leopoldina, São Paulo, SP, 05319-000
It applies to the service catalog the same discipline as PDM: taxonomy by family, attribute template, rule-generated description, deduplication and tax classification, so that the same scope is always described in the same way.
PDM deals with materials, which have physical attributes. PDS deals with services, whose attributes are scope, specialty, unit of measurement, frequency, location and service level. The engine, the taxonomy and the governance flow are the same.
Standardizing is not rigidity. The template describes the scope in attributes, and what varies between contracts, such as volume, deadline or location, enters as a variable attribute. What repeats becomes comparable.
A well-described service is a well-classified service. NBS and the service code depend on the description, and in the new IBS and CBS model this classification defines tax treatment and credit.
Yes. AI proposes family, attributes and classification based on the existing description and contracting history, at scale. The specialist validates critical cases, and every decision is recorded.
Yes, natively. SAP, TOTVS, Oracle, Senior, Mega and the main ERPs. The same integration already serves materials, suppliers and customers.