A discovery framework where the evidence stops

The SYSPRO evidence base names projects only as a capability inside the Manufacturing pillar, so this module supplies a discovery framework and the target concepts you will need, rather than a mapping it cannot support.

What you will be able to do

Introduction

This module is different from the others in the SYSPRO path, and the difference should be stated plainly at the start.

What the evidence does and does not support

SYSPRO's Manufacturing pillar includes a projects capability; That capability sits alongside bills of materials, work in progress, manufacturing operations management, planning, engineering change control and the configurator;

Three different requirements that all sound like "projects"

The first discovery task is to establish which of three quite different requirements the business actually has, because they lead to three different target answers.

The dimension-versus-project decision

Because the first two rows of that table are so much cheaper than the last, the decision deserves a proper test rather than a preference.

The D365 target concepts, briefly

If discovery scopes the module in, these are the constructs the design conversation will use.

The project discovery pack

Is the SYSPRO projects capability licensed, and is it in use? If it is in use, how many active records exist, and how many were created in the last twelve months? Who maintains it, and who consumes its output?

Sequencing, if the module is in scope

Should discovery scope projects in, the sequencing constraints are worth stating.

Knowledge check

Summary

This module is a framework, not a mapping, and that is a deliberate and defensible position given the evidence.