Model Agnostic Scheduling System APS

Model Agnostic Scheduling System (APS)

Article Type: Concept / Starter Package / Platform Capability Overview Audience: Solution Architects, Application Designers, Developers, Operations Managers Module: Scheduling / APS Engine Applies to Versions: 2025.3.0+

1. Overview

The Scheduling Configuration Package is a starter template and reference implementation that demonstrates the powerful, model-agnostic Advanced Planning and Scheduling (APS) capabilities native to the Fuuz platform. Unlike traditional scheduling systems that are locked to specific data structures, Fuuz's APS engine can schedule any data model you define—making it applicable to virtually any operational domain: manufacturing execution (MES), warehouse management (WMS), maintenance management (CMMS), quality management, field service, project management, and more.

This package provides working examples of:

• Event-Resource-Assignment scheduling patterns with configurable mappings
• Primary and secondary resource allocation (workcenters, operators, tooling)
• Dependency management with lag time support
• Constraint-based scheduling with calendar/availability integration
• Alternate resource routing for flexibility and load balancing

Note: The real power of this package is not the specific data models it includes (Distribution, Workcenter, Operator, Tooling)—it's the SchedulingConfiguration pattern that shows how to map any of your data models to the scheduling engine. Your production orders, work orders, maintenance tasks, warehouse picks, quality inspections, or service appointments can all be scheduled using the same powerful engine.

Note: The original article includes the package file attachment SchedulingConfigurationPackage003.fuuz. Download it from the original KB article; the package file must be re-attached/linked in this repository.

2. Package Components

Component Summary

Component Type	Count	Description
Data Models	11	Event, resource, assignment, and constraint models
Data Flows	1	Scheduler Engine Test flow (31 nodes)
Screens	4	Configuration, resource management, and test screens
Seed Data	6 types	Sample configuration, workcenters, operators, schedules

Data Models

Model	Category	Fields	Purpose
Distribution	Event	22	The schedulable work item (task, order, job)
Workcenter	Primary Resource	7	Main resource where work is performed
Operator	Secondary Resource	7	Personnel assigned to work
Tooling	Secondary Resource	6	Equipment/tools required for work
AlternateWorkcenterComplex	Routing	5	Alternative resource options for flexibility
DistributionDependency	Constraint	7	Predecessor/successor relationships with lag
AllowedOperators	Constraint	5	Which operators are qualified for work
AllowedTooling	Constraint	5	Which tools are compatible with work
DistributionOperator	Assignment	5	Actual operator assigned to distribution
DistributionTooling	Assignment	5	Actual tooling assigned to distribution
DistributionAssignment	Assignment	1	Generic assignment placeholder

Seed Data

The package includes sample data to demonstrate the configuration:

• SchedulingConfiguration: "Complex Distribution" — fully configured mapping example
• Workcenters: 4 test workcenters with calendar associations
• Operators: 2 sample operators (Bob, Ted)
• ScheduleGroups: 2 groups (Group A, Group B) for calendar/availability
• Schedules: 2 schedules linked to groups
• ScheduleEvents: 2 sample calendar events

3. Understanding the Scheduling Configuration

The heart of Fuuz's APS flexibility is the SchedulingConfiguration model. This configuration tells the scheduling engine how to interpret your data models as schedulable events, resources, dependencies, and assignments.

Configuration Structure

Mapping Type	Purpose	Key Fields Mapped
eventMapping	Maps your data model to schedulable events	id, name, startDate, endDate, duration, resourceId, constraintDate, constraintType, percentDone
resourceMapping	Maps your data models to resources (primary/secondary)	id, name, calendar, imageUrl, resourceType
dependencyMapping	Maps predecessor/successor relationships	from, to, lag, lagUnit
assignmentMapping	Maps resource assignments to events	eventId, resourceId

Example Event Mapping

The included configuration maps the Distribution model as the schedulable event:

{
  "dataModel": "Distribution",
  "mapping": {
    "id": "id",
    "name": "name",
    "startDate": "startDate",
    "endDate": "endDate",
    "duration": "duration",
    "primaryResourceId": "primaryWorkcenterId",
    "alternateResourceIds": "alternateWorkcenterComplexes.edges.node.workcenterId",
    "constraintDate": "constraintDate",
    "constraintType": "schedulingConstraintTypeId",
    "resourceId": "workcenterId",
    "secondaryAllowedResourceIds": [
      "allowedOperators.edges.node.operatorId",
      "allowedToolings.edges.node.toolingId"
    ],
    "percentDone": "percentDone"
  },
  "transforms": {
    "tooltipTransform": "$join([\"Name: \", name, \"</br>\",\"Workcenter: \", additionalFields.workcenter.name], \"\")",
    "eventHtmlTransform": "name",
    "eventColorTransform": "$contains($.name,\"Process: 1\") ? \"blue\" : \"red\""
  }
}

Resource Types

The configuration supports multiple resource types with different behaviors:

• Primary Resources (Workcenter): The main location where work occurs. Events are scheduled to primary resources first.
• Secondary Resources (Operator, Tooling): Additional resources required for work. Can be configured with allowOverlap: true for shared resources like tools.
• Alternate Resources: Alternative primary resources that can be used if the preferred resource is unavailable.

4. Cross-Industry Use Cases

Because the Fuuz APS engine is model-agnostic, the same scheduling capabilities can be applied to virtually any operational domain. Below are detailed scenarios showing how to adapt this package for different solutions.

MES — Manufacturing Execution

Scenario: Schedule production orders across manufacturing work cells with operator and machine tool constraints.

Scheduling Concept	MES Data Model	Example
Event	ProductionOrder, WorkOrder, Operation	PO-2025-001: Produce 500 units of Widget A
Primary Resource	Workcenter, Machine, ProductionLine	CNC Mill #3, Assembly Line A
Secondary Resource	Operator, Fixture, Die, Mold	John Smith (Certified CNC Operator), Die #42
Dependencies	OperationSequence, RoutingStep	Cut → Weld → Paint (with 30 min cure time lag)
Constraints	OperatorCertification, ToolingCompatibility	Only certified operators can run hazardous operations

Additional MES scenarios:

• Multi-stage production with setup time between product changeovers
• Batch processing with minimum/maximum batch sizes
• Parallel processing on multiple machines with load balancing
• Rework routing with priority scheduling

WMS — Warehouse Management

Scenario: Schedule pick waves, replenishment tasks, and shipping dock assignments across warehouse zones with forklift and picker constraints.

Scheduling Concept	WMS Data Model	Example
Event	PickTask, PutawayTask, ReplenishmentTask, ShipmentTask	Pick Wave #45: 150 orders, Ship by 2PM
Primary Resource	Zone, Aisle, Dock, StagingArea	Zone A (Refrigerated), Dock 7
Secondary Resource	Picker, Forklift, PickCart, Scanner	Maria (High-Bay Certified), Forklift #12
Dependencies	TaskSequence	Pick → Pack → Stage → Load
Constraints	ZoneAccess, EquipmentCertification, CarrierCutoff	FedEx pickup at 3PM, hazmat requires certified handlers

Additional WMS scenarios:

• Wave planning with carrier cutoff optimization
• Cross-docking with tight timing windows
• Cycle counting during low-activity periods
• Yard management and trailer scheduling

CMMS — Maintenance Management

Scenario: Schedule preventive maintenance, corrective work orders, and calibration tasks with technician skills and parts availability constraints.

Scheduling Concept	CMMS Data Model	Example
Event	WorkOrder, PMTask, CalibrationTask, InspectionTask	WO-5521: HVAC filter replacement, PM due 1/30
Primary Resource	Asset, Equipment, Location, System	Compressor #7, Building A HVAC System
Secondary Resource	Technician, Tool, SparePart, Contractor	Mike (Electrical License), Multimeter, Belt Part #P-4422
Dependencies	TaskSequence, LockoutTagout	Isolate → Lockout → Repair → Test → Restore
Constraints	TechnicianSkill, PartsAvailability, ProductionWindow	Schedule during 3rd shift when line is down

Additional CMMS scenarios:

• Predictive maintenance scheduling based on sensor alerts
• Shutdown/turnaround project scheduling with critical path
• Multi-trade coordination (electrical, mechanical, HVAC)
• Contractor and vendor coordination

QMS — Quality Management

Scenario: Schedule inspections, audits, calibrations, and CAPA activities with inspector qualifications and equipment availability.

Scheduling Concept	QMS Data Model	Example
Event	Inspection, Audit, CalibrationDue, CAPATask, NCRReview	First Article Inspection for Part #12345
Primary Resource	InspectionStation, QALab, AuditArea	CMM Room, Incoming Inspection Station
Secondary Resource	Inspector, Auditor, MeasurementEquipment, Gauge	Sarah (ASQ CQI), CMM Machine, Caliper Set #7
Dependencies	InspectionSequence, ApprovalChain	Visual → Dimensional → Functional → Sign-off
Constraints	InspectorCertification, EquipmentCalibration, RegulatoryDeadline	ISO audit must complete by Feb 15

Additional QMS scenarios:

• Statistical sampling inspection scheduling
• Supplier audit scheduling with travel constraints
• Document review and approval workflows
• Training and certification renewal tracking

Additional Scenarios

Domain	Events	Resources	Example Use Case
Field Service	ServiceCall, Installation, Repair	Technician, Vehicle, Territory	Route optimization for HVAC service calls
Project Management	Task, Milestone, Deliverable	TeamMember, Equipment, Room	Engineering project resource leveling
Lab Management	Test, Experiment, Analysis	Instrument, Scientist, Bench	R&D lab instrument time booking
Healthcare	Appointment, Procedure, Treatment	Clinician, Room, Equipment	Operating room and surgeon scheduling
Transportation	Trip, Route, Delivery	Driver, Vehicle, Trailer	Fleet dispatch with HOS compliance
Training	Course, Session, Certification	Instructor, Room, Equipment	Employee training room and instructor booking

5. Implementation Approach

Prerequisites

• Fuuz platform version 2025.3.0 or higher
• App Admin or Developer access type
• Understanding of your schedulable entities and resource types
• Existing or planned data models for events, resources, and constraints

Phase 1: Install the Starter Package

1. Open the Fuuz Package Manager.
2. Upload the Scheduling Configuration Package (.fuuz file).
3. Complete the installation process.
4. Verify screens appear at /system/testing/ routes.

Phase 2: Explore the Reference Implementation

1. Review the included SchedulingConfiguration "Complex Distribution".
2. Examine the data model relationships (Distribution → Workcenter, Operator, Tooling).
3. Create sample Distribution records and test the scheduling flow.
4. Observe how mappings translate your data to the scheduling engine.

Phase 3: Design Your Scheduling Model

1. Identify your Event model: What gets scheduled? (Orders, Tasks, Appointments)
2. Identify your Primary Resource model: Where does work happen? (Machines, Locations, Rooms)
3. Identify Secondary Resource models: What else is required? (People, Tools, Materials)
4. Define Dependencies: What sequencing rules exist? (Predecessor/Successor)
5. Define Constraints: What qualification/compatibility rules apply?

Phase 4: Create Your Scheduling Configuration

1. Create a new SchedulingConfiguration record.
2. Define eventMapping for your event data model.
3. Define resourceMapping for each resource type (primary and secondary).
4. Define dependencyMapping if you have sequencing requirements.
5. Define assignmentMapping for secondary resource assignments.
6. Configure transforms for tooltips, colors, and display formatting.

Phase 5: Build Scheduling Screens

1. Use the Fuuz Screen Designer to create Gantt chart views.
2. Configure the scheduling component to reference your SchedulingConfiguration.
3. Add filters for date ranges, resource groups, and event types.
4. Implement drag-and-drop rescheduling actions.

Tip: Start with a minimal configuration mapping only the required fields (id, name, startDate, endDate, resourceId). Add complexity incrementally as you validate each layer works correctly.

6. Platform APS Capabilities

This starter package introduces core concepts, but the Fuuz APS engine provides many additional capabilities for advanced planning scenarios:

Scheduling Features

Feature	Description
Constraint Types	Start No Earlier Than, Finish No Later Than, Must Start On, As Soon As Possible
Calendar Integration	ScheduleGroup, Schedule, and ScheduleEvent models for availability windows
Dependency Types	Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish with lag
Effort-Driven Scheduling	Duration adjusts based on assigned resources
Resource Leveling	Automatic conflict resolution and load balancing
Progress Tracking	percentDone field for partial completion visualization
Visual Customization	JSONata transforms for colors, tooltips, and HTML rendering
Overlap Control	allowOverlap setting for shared resources like tooling

Integration Points

• ERP Integration: Import orders, routings, and BOMs; export scheduled dates
• IoT/Gateway: Real-time machine status updates affecting availability
• Notification Channels: Alert operators of schedule changes
• Data Flows: Automated rescheduling triggers on constraint violations
• Document Designer: Generate printed schedules and work orders

7. Troubleshooting

Issue	Possible Cause	Resolution
Events not appearing	eventMapping field names don't match data model	Verify mapping field names match exactly (case-sensitive)
Resources not loading	resourceMapping dataModel name incorrect	Check dataModel matches your model's exact name
Dependencies not respected	Dependency records missing or mapping incorrect	Verify dependency records exist and from/to fields are mapped
Calendar not applied	scheduleGroupId not linked to resource	Ensure resources have scheduleGroupId populated
Transforms not rendering	JSONata syntax error in transform	Test transform in JSONata playground with sample data
Secondary resources not assigned	assignmentMapping missing or incorrect	Verify assignment model and eventId/resourceId mapping

8. Resources

• Fuuz Industrial Operations Platform — Main product site
• SchedulingConfiguration Reference — Complete mapping specification
• Screen Designer: Scheduling Components — Gantt chart and calendar widgets
• Data Model Designer Guide — Creating custom event and resource models
• Schedule and Calendar Management — ScheduleGroup, Schedule, ScheduleEvent models
• JSONata Transform Reference — Custom Fuuz bindings for transforms

9. Revision History

Version	Date	Editor	Description
1.0	2025-01-25	Fuuz Documentation Team	Initial release documenting Scheduling Configuration Package v0.0.3 with cross-industry use cases and platform APS capability overview

See Also

• Flow-Schedules
• Fuuz-Standard-Packages
• Data-Model-Schema-Design-Standards
• Jsonata-Tutorial
• Custom-Fuuz-Only-JSONata-Library
• Application-Designer-Guide

---

Source: support.fuuz.com