Repository navigation
Interface 01 Calendar
中文 · Learning guide · Semantic guide
Build a two-day planning coordinate with one eight-hour production window per day. The stamping machine has two hours of maintenance on day one; assembly runs normally. You should be able to calculate each resource's daily availability directly from the records.
Confirm the planning origin, dates, shifts, and time zone. The two units represent production windows on consecutive days, not necessarily calendar instants eight hours apart. Keep the date mapping with the source-data mapping.
| id | offset | scale (seconds) | status | Business mapping |
|---|---|---|---|---|
| 1 | 0 | 28800 | 1 | Day-one production window |
| 2 | 1 | 28800 | 1 | Day-two production window |
id is referenced by demand, capacity, kitting, and results. offset orders periods; scale supplies duration. A day-one due date becomes delivery_time=1, rather than a calendar string or offset=0.
Work center 11 is stamping and 12 is assembly. Each combination below becomes one capacity row:
| id | time_unit | workcenter | used | Available minutes |
|---|---|---|---|---|
| 1 | 1 | 11 | 0.25 | 360 |
| 2 | 1 | 12 | 0 | 480 |
| 3 | 2 | 11 | 0 | 480 |
| 4 | 2 | 12 | 0 | 480 |
Day-one stamping availability is 28800 × (1−0.25) / 60 = 360 minutes. Maintenance has not been deducted elsewhere. Resources share the global calendar but can have different local occupancy.
To represent exact operating hours within a 24-hour day, use hourly units with scale=3600. Globally closed hours use status=0. A two-shift factory can make both shifts globally available, while a single-shift machine uses used=1 during the second shift. Continuous production needs a global calendar covering the whole day and local maintenance records.
status=-1 expresses optional time. Confirm how the selected model adopts it. If a resolved calendar is required, create an approved-overtime or no-overtime input view and record the decision. Do not substitute -1 into the normal-period availability formula.
- Two hours out of eight is 0.25, not 2, 120, or 25.
- Deduct maintenance once. Merge overlapping unavailable intervals before converting to a fraction.
- A 360-minute aggregate does not establish that those minutes are continuous. Represent finer periods when an uninterrupted operation must avoid an internal maintenance window.
- Compare before and after records; only the relevant resource and period should change.
Extend day-one maintenance to three hours. Change capacity.id=1 to used=3/8=0.375. Availability becomes 300 minutes, a reduction of 60. A 200-minute task still fits in aggregate, but material availability, precedence, and maintenance timing also need review.
Product Home | DecisioWorks v1.4.0 | English / 中文
- What Is DecisioWorks / DecisioWorks 是什么
- Scenarios and Pain Points / 适用场景与痛点
- Quick Start / 快速开始
- Documentation Map / 文档地图
- Research and Commercial Editions / 研究版与商业版
- Whitepapers / 白皮书
-
Learning Center / 学习中心: 8 topics / 8 个专题
- Design Principles and Differentiation / 设计原则与差异化
- Architecture Overview / 总体架构
- Component Responsibilities / 组件职责
- Standard Actions and Orchestration / 标准动作与能力编排
- Objectives and Rule Control / 目标与规则控制
- Controlled Solving and Engine Adapters / 受控求解与模型适配
- Results, Evidence, and Feedback / 结果、证据与反馈
- Developer Guide Index / 开发手册索引
- Data Objects and Fields / 数据对象与字段
- Actions, Recipes, and Execution / 动作、配方与执行
- Runtime Status, Errors, and Limits / 运行状态、错误与限制