Which BPM solution to use, when Organization Structure and a Document Management System should co exist also?

I am looking for a product that can solve a problem for me开发者_StackOverflow社区, and I hope you can help me with this ASAP.

I have a client which needs software modules to be integrated together, the following are the modules with what I think is the software that fulfills its goals next to it:

1. Document Management System (DMS): Sharepoint Portal.
2. Company Organization Structure (needed for workflows and used in DMS also): Probably custom development integrated with Active Directory and sharepoint portal.
3. Workflow Managment System (or BPM): Nintex Workflow.

The questions are:

1. Are the points above logical, or is there something missing.
2. Will it take too much time for development to integrate the Company organization structure with the workflow management and sharepoint, or is there a simpler solution, such as a built in Organization Structure in sharepoint or in Nintex Workflow?

I am still reviewing software solutions, I am not familiar with sharepoint, a combination of software solutions which lead to this product/solution I can use as a product later on for future clients is what I am looking for also.

For example, let's say we have a Leave request workflow process, the process is as follows:

Start -> Fill Leave Form -> Approve Form by CURRENT active manager -> save leave form data by HR team (on file or on separate HRMS) -> Close process

The organization structure is defined, and then the "CURRENT active manager" is defined for a group of people, the process will be built by a "workflow management system"/BPM software, the "Leave Form" can be a webform, or a template stored on a document management system.

I'm not familiar with Nintex Workflow however if your active directory information is up to date, in terms of the organisation structure and user details & groups, the organisation structure is probably supported out of the box by SharePoint.

Thus all that might remain is the workflow component which again could probably be created using standard SharePoint functionality, with minor customization with SharePoint Designer.

Having said that, configuring and installing SharePoint is not simple, and needs some thought.

From my experience with Nintex Workflows, it integrates really well into SharePoint and would work in a hierarchical company organization structure. If Active Directory is correctly set to indicate "bosses", "subordinates", etc, this information can be used within the workflow. For instance, "Send this workflow to my boss", followed by "send it to his boss", would be simple to program, since that information would be available from Active Directory.

Depending on what is needed, standard OOB SharePoint and Nintex can be used together to produce amazing workflows. One of the major advantages of using Nintex Workflows is that it can be used without programming. However, if programmers are available, additional logic can be added to augment a workflow (such as event-level programming).