Module: Configure Production Prerequisites

Section: Resources, Routes, and Calendars

Lesson: Resources and Resource Groups

Introduction: The Foundation of Production Planning

In any manufacturing or production environment, the ability to accurately track, schedule, and manage your capacity is the difference between a profitable operation and a chaotic one. Whether you are building complex machinery or assembling consumer goods, you need to know exactly what equipment, labor, and facilities are available at any given moment. This is where the concept of Resources and Resource Groups becomes the backbone of your entire production system.

Resources represent the individual entities that perform work. This could be a specialized CNC machine, a manual assembly station, or a specific technician. Resource Groups, on the other hand, are the logical containers that bundle these individual resources together based on shared characteristics, such as location, skill set, or machine type. By organizing your production floor into these hierarchical structures, you gain the ability to perform high-level capacity planning while maintaining the granular control necessary for daily execution.

Understanding how to configure these entities is not just a technical requirement for your ERP or production management software; it is a strategic necessity. If your resource model is too rigid, you will struggle to adjust to machine breakdowns or staff shortages. If it is too loose, your scheduling engine will produce unrealistic plans that lead to missed deadlines and excess inventory. This lesson will guide you through the structural design, configuration, and maintenance of these critical production building blocks.

Defining Resources: The Individual Units of Capacity

A resource is any entity that has a finite capacity and is required to complete a production task. When we define a resource, we are essentially digitizing a physical asset or a human role so that the system can account for its availability. Without a properly defined resource, the system cannot calculate the time required for an operation, nor can it track the actual cost of production.

Types of Resources

To build a functional model, you must first categorize your resources. Most modern production systems distinguish between several primary types:

• Machine Resources: These are your physical capital assets. They often have specific maintenance requirements, power limitations, and operating speeds. Tracking these allows you to monitor machine utilization and schedule preventive maintenance effectively.
• Labor/Human Resources: These represent the people working on the floor. While sometimes treated as a "cost" rather than a "machine," they are essential for operations that cannot be automated. You must account for their shift patterns, breaks, and holidays.
• Tooling Resources: Sometimes, a production step requires a specific jig, mold, or specialized tool that is not tied to a single machine but must be "checked out" for a period. Managing these separately ensures you don't schedule a job that requires a mold which is currently in use elsewhere.
• Vendor/Subcontractor Resources: If you outsource parts of your production, you must still represent these as resources to track lead times and costs, even if the work is performed outside your four walls.

Attributes of a Resource

When you create a resource in your system, you are not just giving it a name. You are defining its behavior through several key attributes. These attributes determine how the system interacts with the resource during the scheduling process.

1. Capacity: This defines the maximum output potential per unit of time. For a machine, this might be the number of units it can produce per hour. For a person, it might be the total hours they are scheduled to work in a week.
2. Efficiency: Not every resource operates at 100% capacity. You must account for real-world factors like setup time, warm-up periods, and minor inefficiencies. A resource with an efficiency of 0.85 means that for every hour of scheduled time, the system assumes only 51 minutes of productive output.
3. Calendars: A resource is only useful when it is available to work. Linking a resource to a specific calendar (e.g., "Standard Day Shift" or "24/7 Continuous") ensures that the system doesn't try to schedule a job at 3:00 AM if the facility is closed or the staff is off-duty.

Callout: Resources vs. Work Centers In many systems, you will encounter the term "Work Center." It is important to distinguish this from a "Resource." A Work Center is often a broader organizational entity, while a Resource is the specific unit of work. Think of a Work Center as a "Department" or "Area" and a Resource as the individual machine or person within that area. A Resource belongs to a Resource Group (or Work Center), but the Resource is what actually consumes time on the schedule.

Configuring Resource Groups: The Logic of Aggregation

Resource Groups serve as the bridge between high-level planning and low-level execution. By grouping resources, you allow the production scheduler to look at "available capacity" for a type of work rather than hunting for a specific machine. This provides a buffer of flexibility that is essential for real-world operations.

Why Use Resource Groups?

Imagine you have five identical lathes in your shop. If a job comes in that requires a lathe, you don't necessarily care which of the five performs the work, as long as one is available. By placing all five lathes into a "Lathe Resource Group," you enable the system to automatically assign the job to the first available unit.

• Load Balancing: Resource groups allow you to view the total load on a specific capability. If the "Assembly Group" is overloaded, you can easily shift tasks between the resources within that group to balance the load.
• Simplified Routing: Instead of defining a route that says "Use Machine A," you can define a route that says "Use any machine in the Assembly Group." This makes your product routings much easier to maintain as your equipment inventory changes.
• Reporting: Resource groups provide a natural layer for performance analysis. You can compare the efficiency of the "Welding Group" versus the "Painting Group" to see which department is underperforming.

Designing Your Hierarchy

The design of your resource groups should mirror the physical layout of your shop floor or the logical flow of your production processes. A common mistake is to create groups that are too large or too small.

• Too Broad: If you create a group called "Production Floor," you lose the ability to schedule effectively because the system treats a sewing machine and a drill press as interchangeable.
• Too Narrow: If you create a group for every single piece of equipment, you lose the benefits of load balancing, and your scheduling engine will struggle to find alternatives when a machine breaks down.

Aim for a middle ground where the resources within a group are truly interchangeable for the purposes of your production routing. If a machine requires a unique skill set or specific tooling that others don't have, it should likely reside in its own dedicated group.

Practical Implementation: Step-by-Step Configuration

To configure these in a typical production system, you will generally follow a logical flow from the calendar level up to the resource group level.

Step 1: Define Your Calendars

Before you create a single resource, you must define the time parameters. Create calendars for your various shifts.

• Example: Create a "Day Shift" calendar (8:00 AM - 4:00 PM, Monday-Friday) and a "Night Shift" calendar (4:00 PM - 12:00 AM, Monday-Friday).
• Tip: Ensure you include non-working days like holidays or scheduled maintenance shutdowns in these calendars.

Step 2: Create Resources

Create your individual machines or labor pools. Assign them to a specific site or location to ensure you aren't trying to schedule a resource in New York for a job that is physically located in London.

• Essential fields: Resource ID, Name, Type (Machine/Labor), and the associated Calendar.

Step 3: Define Resource Groups

Create your groups and associate them with your site and department.

• Linking: Add your previously created resources to these groups. A resource can generally only belong to one group at a time, though some advanced systems allow for secondary associations.

Step 4: Map Resources to Routes

This is where the magic happens. In your production routing (the sequence of steps required to build a product), you will assign a "Requirement" to each step. Instead of selecting a specific resource, select the "Resource Group."

Note: The Importance of Throughput When setting up resources, always consider the "Bottleneck." If your "Painting" resource group has a total capacity of 50 units per day, it does not matter if your "Assembly" group can do 200 units. Your total output is constrained by the bottleneck. Ensure your resource groups accurately reflect the capacity of these constraints.

Code Example: Defining Resource Logic

While many ERP systems provide a GUI for this, understanding the data structure is vital for integration. Below is a simplified JSON representation of how a Resource and Resource Group relationship is typically stored in a database.

{
  "resourceGroup": {
    "groupId": "ASSEMBLY_01",
    "name": "Manual Assembly Line",
    "site": "PLANT_A",
    "resources": [
      {
        "resourceId": "ASM_STA_01",
        "name": "Assembly Station 1",
        "type": "Labor",
        "calendarId": "DAY_SHIFT",
        "efficiencyFactor": 0.95
      },
      {
        "resourceId": "ASM_STA_02",
        "name": "Assembly Station 2",
        "type": "Labor",
        "calendarId": "DAY_SHIFT",
        "efficiencyFactor": 0.90
      }
    ]
  }
}

Explanation of the code structure:

• groupId: The unique identifier for the container.
• resources: An array that holds the individual units.
• efficiencyFactor: Note that we assigned different factors to each station. This allows the system to be precise. If Station 2 is slightly slower due to its location, the system can automatically adjust the expected completion time based on which station is chosen.

Best Practices for Maintaining Your Resource Model

The configuration of resources is not a "set it and forget it" task. As your business grows, your equipment changes, and your labor force fluctuates, your resource model must evolve.

1. Conduct Regular Audits

Every quarter, review your actual production output against your configured capacity. If you consistently find that your "Welding" group is finishing jobs faster than the system predicts, your efficiency factors are likely set too low. Conversely, if you are constantly behind schedule, your capacity settings may be too optimistic.

2. Standardize Naming Conventions

Use a clear, descriptive naming convention for all resources and groups. A resource named MCH_001 is meaningless to a new employee. A resource named CNC_LATHE_01 tells everyone exactly what the machine is and where it belongs.

3. Use Effective Dates

Most systems allow you to set "Effective Dates" for resource configurations. If you know you are adding a new high-speed machine to your "Assembly" group next month, you can configure it today and set the start date for the future. This prevents you from having to rush the configuration on the day the machine arrives.

4. Separate Maintenance from Production

Never use a production resource for maintenance tasks without accounting for it in the system. If a machine is down for a week of repairs, its calendar or capacity should be updated to reflect zero availability. Failing to do this will result in the system scheduling jobs for a machine that cannot possibly complete them.

Common Pitfalls and How to Avoid Them

Even with the best intentions, it is easy to fall into traps that can derail your production planning. Here are the most common mistakes and how to navigate them.

Pitfall 1: Over-Engineering the Hierarchy

Some managers try to create a complex, multi-level hierarchy for their resources. They create "Sub-groups" and "Super-groups," which often makes the system impossible to navigate.

• The Fix: Keep it simple. A two-level hierarchy (Resource -> Resource Group) is sufficient for 95% of manufacturing environments. Only add layers if your reporting needs absolutely demand it.

Pitfall 2: Ignoring Setup Time

When defining a resource, it is tempting to only think about "Run Time" (the time it takes to make the part). However, setup time (the time to change the mold, load the material, or calibrate the machine) is often where the most time is lost.

• The Fix: Always include a "Setup Resource" or a "Setup Time" component in your routing. If a machine requires a specific technician for setup, ensure that technician is also defined as a resource.

Pitfall 3: The "Infinite Capacity" Trap

Some systems default to "Infinite Capacity" planning, where the system assumes you have unlimited resources available. This is dangerous because it masks your true constraints.

• The Fix: Always configure your systems for "Finite Capacity" planning. This forces the system to respect the limits of your resources and provides an accurate view of what can actually be accomplished.

Quick Reference: Resource Configuration Checklist

Advanced Considerations: Interdependency and Secondary Resources

As you become more comfortable with basic resource configuration, you may need to address more complex scenarios. One such scenario is the use of Secondary Resources.

A secondary resource is a resource that is required for an operation but is not the primary driver of the process. For example, in a heat-treating operation, the primary resource is the furnace, but the secondary resource might be the specialized operator who is certified to handle the chemicals. In your system, you should configure the operation to require both the Furnace (Primary) and the Technician (Secondary).

Managing Constraints

When you have multiple resources involved in one step, your system must be able to handle "Resource Constraints." This means the system will check for the availability of both the furnace and the technician before scheduling the job. If the furnace is free but the technician is busy, the job will not be scheduled. This level of detail is what separates a basic system from a truly powerful production management suite.

Callout: The "Bottleneck" Strategy When dealing with multiple resources, identify your "Constraint Resource." This is the resource that is most frequently at capacity. Focus your optimization efforts here. If you can increase the efficiency of your bottleneck by even 2%, your overall throughput will increase significantly, whereas increasing the efficiency of a non-bottleneck resource will have zero impact on your final output.

Handling Changes and Scalability

Production environments are dynamic. You will add new equipment, retire old machines, and reorganize your shop floor. Your resource model must be flexible enough to handle these changes without requiring a total system overhaul.

Adding New Resources

When adding a new resource to an existing group, ensure you update your efficiency factors and calendar associations before it goes "live" in the system. Test the new resource in a sandbox or staging environment if possible to ensure that the scheduling engine correctly picks it up.

Retiring Resources

When a machine is retired, do not simply delete it from the system. If you delete a resource, you lose all the historical cost and performance data associated with it. Instead, mark the resource as "Inactive" or "Retired" and update the "To Date" on its effective range. This preserves your historical reporting while removing it from current scheduling.

Scaling Across Locations

If your company opens a new plant, you should replicate your resource structure. Use the same naming conventions and logic as your existing plants. This allows for "Cross-Plant Reporting," where you can compare the productivity of the "Assembly" group in Plant A against the "Assembly" group in Plant B. This is a powerful tool for identifying best practices that can be shared across the entire organization.

Common Questions and Troubleshooting

Q: Why is the system scheduling jobs on my weekends? A: Check the Calendar associated with the resource. It is likely that the calendar is set to a "24/7" or "Continuous" mode rather than a "Standard" work week. Adjust the calendar definition to exclude Saturdays and Sundays.

Q: My "Efficiency" setting is 1.0 (100%), but I am still behind schedule. Why? A: An efficiency of 1.0 assumes perfect operation. You are likely experiencing "unplanned downtime" (machine jams, material shortages, etc.) that is not accounted for in your efficiency factor. Try reducing it to 0.85 or 0.90 to account for these real-world interruptions.

Q: Can a resource belong to two different groups? A: In most systems, no. A resource should have a single "Home" group. If you need a resource to perform multiple types of work, you should consider whether your groups are defined correctly. Perhaps the groups should be based on "Capabilities" rather than "Departments."

Q: How do I handle temporary capacity? A: If you hire temporary staff for a seasonal surge, create a separate "Temporary Labor" resource. You can set an expiration date on this resource so that the system automatically stops including it in the schedule once the season is over.

Key Takeaways

As we conclude this lesson, remember that your production resources are the digital representation of your physical reality. If your digital model is inaccurate, your production plan will be, too. Keep these core principles in mind as you build and maintain your configuration:

1. Granularity Matters: Define your resources at the level of individual machines or labor roles, but bundle them into logical groups to allow for flexibility and load balancing.
2. Calendars are King: A resource is only as good as its availability. Always link resources to accurate, up-to-date calendars that reflect shifts, breaks, and holidays.
3. Efficiency is a Reality Check: Never assume 100% efficiency. Use historical data to set realistic efficiency factors that account for setup times and minor operational hiccups.
4. Avoid Complexity: Keep your hierarchical structure as flat as possible. Complexity introduces errors and makes the system harder to maintain for your team.
5. Preserve History: Never delete resources. Mark them as inactive to ensure you retain the valuable historical performance data needed for future analysis.
6. Focus on Bottlenecks: Identify the resources that constrain your total output and focus your configuration and optimization efforts on those units first.
7. Audit and Adapt: Treat your resource model as a living document. Regularly review your actual output against your planned capacity and adjust your configuration to bridge any gaps.

By following these practices, you will create a resilient, accurate, and scalable production model that serves as the foundation for high-performance manufacturing. Proper resource management is not just about keeping the lights on; it is about providing the visibility and control needed to drive continuous improvement across your entire operation.