including the dependency structure and task constraints the assembly of the project plan as shown in fig6 into a task list can be visualized in the table below the project plan is created by a project manager 602 who needs to have control of the various tasks 604 606 that must be accomplished in order to coordinate and successfully complete the project however the project plan 608 does not include any of the technical information that is needed in order to complete any specific task this u201c project data u201d is typically generated by many different groups within the provider 39 s delivery process the technical data may be in many different forms and may be created and input at many different times the cdm module utilizes status information generated in the workflow management system to determine when to initiate a dependent task tasks that do not have all the required entered data defined in the wfms will not be allowed to complete successfully for example a task may specify that a router needs to be ordered for a particular site and that a po purchase order number must be assigned in order for the task to be u201c complete u201d the data that describes the technical details of the router part number bandwidth etc may be stored in a spreadsheet which can be imported into the wfms platform to populate the required data items the procurement group may then access the data input screen to enter the po number to complete the task the individual tasks that are imported from the project plan will have associated data schemas which need to be satisfied before the task can be considered complete cdm allows the list of tasks to be bound to the flows to.