DDOM COMPLIANT SOFTWARE APPLICATIONS
Important Points About DDI Software Compliance:
-
DDI Compliance means that the application itself has demonstrated the capability to conform to the required specifications. It does not mean that the software provider has demonstrated the ability to practically apply or help others practically apply the method.
-
DDI Compliance assumes that organizational personnel will be formally educated on the methodology to use a compliant system properly and effectively. There is no substitute for proper education. More on DDI educational offerings.
-
The DDI evaluation process is FREE OF CHARGE to software entities.
-
The DDOM compliance criteria were written in such a way that ensures compliance to the method but allows open space for competitive differences, creativity and innovation.
-
Software that is deemed to be compliant will be allowed to use the DDOMP compliance logo.
-
Systems or applications that have not successfully completed the process are non-compliant.
DDOM COMPLIANCE CRITERIA
Component 1: Additional DDOM Modeling
-
The software must be able to declare identified resources control points or drums.
-
The software must be able to place time buffers at defined points in routings and/or in advance of resource activity.
Component 2: Demand Driven Scheduling
-
The software must offer finite capacity scheduling for control point resources or sets of resources.
-
The software must be able to tie the finite scheduling of control point resources to order due dates and/or net flow priorities of stock buffers.
-
The software must synchronize material release dates, times and quantities in relation to the control point schedules including allowances for time buffers.
Component 3: Demand Driven Execution Requirements
-
The software must track order progression against time buffer penetration and control point schedules.
-
The software must allow for reason code collection at buffers for outlier events.
-
The software must display detailed capacity loading for all resources.
-
The software must display or connect the stock buffer status that an order is progressing toward.
DDOM COMPLIANT SYSTEMS
The following software applications have successfully completed the DDI DDOM Software Compliance Process. While they are not ERP systems most of these add-on applications have interfaces designed specifically for a particular ERP system or multiple ERP systems. If your ERP system is not DDOM compliant contact these providers to see if they might be the right fit for you.
Intuiflow
Developer: Demand Driven Technologies
Languages: English, Chinese, Dutch, Finnish, French, German, Hungarian, Korean, Polish, Portuguese, Russian, Spanish, Spanish (LATM), Turkish
Deployment: Cloud and On-Premises
Website: https://demanddriventech.com
​
CAMELOT LEAN Suite
Developer: Camelot ITLab
Languages: All common languages
Deployment: Cloud & On-Premises
Website: http://www.camelotleansuite.com/
ForgeFlow®
Developer: ForgeFlow S.L.
Languages: English and Spanish: Other languages by request
Deployment: Cloud and On-Premises
Website: https://www.forgeflow.com/demand-driven
Contact: Jordi Ballester
DDMRP for Dynamics
Developer: SHEA Global (in partnership with B2Wise)
Language: English, French, Italian, Spanish and other languages by request
Deployment: Cloud & On-Premises
OpenValue DDMRP
Developer: OpenValue Consulting
Language: English and Italian
Deployment: Cloud and On-Premises
Website: openvalue.cloud
Contact: info@openvalue.cloud
Flowsoft & Flowpro
Developer: Flowing Consultoria
Languages: Spanish (LATAM)
Deployment: Cloud & On-Premises
Website: http://www.flowingconsultoria.com
Contact: dapoveda@flowingconsultoria.com
Simio RPS
Developer: Simio
Language: English
Deployment: On-Premises
Website: https://www.simio.com
Contact: ​Dan Vasalani, Vice President Global Sales, dvasalani@simio.com
Note: Simio is granted an exemption to the reason code collection requirement in Component 3. Simio is a forward-looking simulation-based Process Digital Twin, whereas reason code collection for outlier events is standard for a 'transaction based system recording past events.
C&DS
Developer: Bureau Leonard
Language: English
Deployment: Cloud and On-Premises
Website: https://www.leonard.eu.com/cds-eng/
Contact: ​Patrick@leonard.be
