Is there an ARC project that covers X?

 

Overview

ARC projects are packaged consulting/customization/reporting solutions designed to address common needs without starting from scratch. This guide shows how to determine if a prebuilt ARC project exists for your requirement (X), and how to request one if it doesn’t.

How to find an existing ARC project

1. Search the ARC Project Catalog

• Use your customer portal or catalog site
• Keywords: your module (e.g., Inventory, Scheduling), outcome (e.g., dashboard, automation), and “ARC”

2. Check knowledge base and release notes

• Search for “ARC” + your topic (e.g., “ARC shipping labels,” “ARC overhead report”)
• Look for case studies that mention prebuilt deliverables

3. Ask Support/Account Team

• Provide a one-paragraph description of X and your objective
• Include screenshots (if available) and any compliance constraints

Evaluate fit

• Scope match: Does the project address 80–100% of your requirement?
• Time-to-value: Is it faster than a net-new build?
• Constraints: Data availability, permissions, and infrastructure

Request an ARC project (template)

• Subject: ARC project request — <Your Topic X>
• Background: 2–4 sentences on process and business impact
• Objective: What success looks like (e.g., “single-click shipping docs,” “automated overhead re-cost”)
• Data points: Tables/fields, filters, KPIs, frequency
• Users: Roles and count, security considerations
• Target date: Desired timeline, any go-live dependencies
• Attachments: Samples, layouts, mockups

Delivery and change control

• Typical deliverables: Functional spec, config, test plan, deployment
• Change requests: Document as deltas to initial scope; confirm any cost/time impact
• Signoff: UAT acceptance documented before production move

FAQs

• Can ARC projects be modified?
  • Yes—treat as a baseline. Minor changes are typical; major changes may require a custom scope.
• How long do ARC projects take?
  • Simple report/dashboard: days. Integrations/automation: weeks, depending on complexity.

---

“When I’m scheduling a job, I get this error” — scheduling error troubleshooting

Overview

Scheduling errors usually stem from missing data, capacity/calendar issues, or material constraints. This checklist helps you identify the cause and get the job on the schedule.

Common error themes

• No available capacity on workcenter/shift/calendar
• Routing/operation time missing (setup/run/queue/transfer zero or blank)
• Predecessor/successor logic invalid (sequence gaps or loops)
• Material constraint: required component not available by start date
• Workcenter or job is locked/frozen
• Finite scheduling set but capacity model/data incomplete
• Holiday/non-working day blocking the operation

Immediate triage

1. Capture the exact error text and job number
2. Note scheduling direction: Forward vs Backward
3. Identify the failing operation (sequence) and workcenter

Fix by likely cause

• Capacity/Calendar
  • Open Resource Calendar; confirm shifts, hours, exceptions, and holidays
  • Remove workcenter “Out of Service” flags; update effective dates
  • If finite scheduling, ensure capacity exists on/after the planned start
• Missing times
  • Open Routing; enter realistic Setup and Run times (and run basis)
  • If batch size impacts time, ensure the lot size is set
• Predecessor logic
  • Ensure operation sequences are strictly increasing (10, 20, 30…)
  • Remove circular dependencies; validate overlap/transfer settings
• Material constraints
  • Check component availability and lead times
  • If shortage, expedite purchase/WO, substitute component, or allow late allocation if policy permits
• Locks and statuses
  • Ensure job is Released (not Engineering Hold)
  • Remove workcenter locks or job freezes before rescheduling
• Mode mismatch
  • If finite mode blocks scheduling, temporarily use infinite mode to validate routing data, then revert

Re-run scheduling

1. Correct the underlying data in Routing/Calendar/Materials
2. Choose scheduling direction:

• Forward: from earliest feasible start
• Backward: from required due date

3. Execute scheduling; confirm no errors at each operation

Prevent recurrence

• Maintain standard routing templates with realistic times
• Review calendars quarterly; load holidays well in advance
• Monitor a “Jobs Not Scheduled” dashboard for daily exceptions