- Subscribe Today
- Training & Events
- Buyer's Guide
When planning and executing manufacturing projects, difficulties can often arise when trying to track two important metrics: estimate to complete by hours (the forecasted number of hours and dollars to complete the project) and estimate at completion by hours (the forecasted cost of the project at completion).
Project cost allocation is critical in many situations, such as when profitability, capacity and customer service are linked; where manufacturers are involved in government supply chains; and in program-based manufacturing agreements.
The most common situation is where both profitability and either firm commitments to the customer or customer experience are important. If you spend more than anticipated on labor or materials in certain phases of the project and do not realize it until much later, you could run out of budget or internal capacity — including manhours and equipment — to complete the work.
Defense manufacturers dealing with government entities require cost reimbursement and cost-plus contracts, which demand rigorous tracking of project or system costs so a standard markup can be applied up to a set limit. Other contract forms include earned value management, time and materials, and even performance-based logistics, where the entire product life cycle must be managed profitably as a project.
Manufacturers in the automotive industry or commercial aviation space may find themselves involved in program-based manufacturing, which requires them to dovetail their engineer-to-order and manufacturing activities with their customer’s new product development cycle.
Unfortunately, traditional enterprise resource planning (ERP) software and its predecessor, materials requirements planning (MRP), were designed originally to match resources and demand in a repetitive manufacturing environment. However, the disciplines required for project-driven manufacturing, program-centric manufacturing and engineer-to-order involve dealing with many unknown variables.
Software used in these environments must be designed specifically to manage project risk and to allocate resources and costs across multiple projects all competing for the same productive capacity. Too often, manufacturers rely on project management or project portfolio management software. While tools such as Microsoft Project or Primavera are capable standalone project management tools, the problem is exactly that – they stand alone.
By tracking load against resources outside of ERP, manufacturers are not truly managing the project from a financial and cost standpoint. They are merely using what is essentially an operations or scheduling tool, which at most encompasses manufacturing time and attendance or work centers for engineers.
Some manufacturers, as they attack the problem of cost allocation in complex project environments, will talk about tracking their resources in terms of how many hours or people they have and begin to allocate them appropriately. This may be done on a project-by-project basis. But in order to optimize this, planners should know what jobs they have not only today but into next year. They then can start with an understanding of what resources are allocated to existing work during specific periods of time and which are not.
The need to manage project resources to meet the needs of original equipment manufacturers (OEMs) has become more common. It was not as prevalent before, which suggests that OEMs are pushing down more of the project accounting requirements on their vendors, where much of the value is delivered anyway.
Planners need to know not only what other jobs they have now but also the ones they will have in the future. They can then start with an understanding of what resources are allocated to existing work. This means if they take on a new job, they can allocate resources not only in light of a specific project requirement, but with an understanding of their existing or even anticipated resource load.
This more powerful functionality helps planners answer not only project-oriented but also enterprise-level questions and enables them to accurately quote lead times and cost. They can do this as they will know even before the project starts where and when they may need more employees or even contractors to take on some of the work.
ERP solutions should be designed for the modern project environment and be able to forecast throughout the life of a project. During that project life cycle, things change. You may have anticipated needing 10 people for 10 weeks, but maybe the customer has changed the scope. If fewer people are required, can you reallocate them to other projects?
If more resources are required, do you have existing people who can be placed onto the project or do you need to hire, outsource, approve overtime or take other measures? Perhaps a long lead time item is delayed due to a commodity shortage or vendor bottleneck. That impacts the rest of the schedule. ERP designed for the project manufacturer must enable the reallocation of hours and costs.
The optimal software tool for this task will dig deeper into several more layers of granularity. For example, which manufacturing disciplines and capacities can you commit to the project, which engineers with which skill sets, how many project managers and how much inventory is available?
The software should overlay this more granular view of capacity in the quoting process to estimate the number of hours and compare it to the current capacity usage. This enables you to move from quoted plans into actual plans for resources once you win the work. Manufacturers are then able to take the forecast and turn it into an actual resource plan that has accurate productive capacity behind it.
The plan becomes not just hours and graphics on a Gantt chart but dollars. Your software tool must deal with hours and dollars in concert. In a fully integrated project ERP, you can generate more tasks and activities linked to work orders or shop orders to generate a flexible, fine-grained schedule and cost story.
Manufacturing is not standing still. Processes have changed. At any given time, planners will need to look at an individual project or a changing portfolio of projects and identify what each has cost to date and what they will cost on completion. This must happen in the context of data from throughout the enterprise, including information on total resource loading across all projects.
In order to nail down reliable estimate to complete (ETC) and estimate at completion (EAC) figures, it is essential that project functionality is part and parcel of the ERP system rather than two separate applications that are united in a point-to-point integration.
Any demand in a project that requires you to generate a shop/work order or to put a resource in the field must accrue against resources available at that time and affect the total cost of the project. That means the project functionality must be embedded in the system of record, the ERP system.
Carrie Ghai is a senior business solutions consultant at IFS.