Share
Report
199I'm looking for some best practices in building a system that manages a schedule at the task level. We are a manufacturer of custom products, and we operate like a "job shop". Every job has products within it. Each product or "scope" operates on a separate schedule.
In Dataverse, we have the following tables to help manage this information:
- Jobs
- Scope
- Scope Tasks
There is a lookup field in Scope to point to the particular job and there is a lookup field in Scope Tasks to point to the particular piece of scope. Each piece of scope goes through a set of tasks. Some of these tasks are not required for every piece of scope, but here is the list of tasks.
- Drafting
- Engineering
- Listing
- Field Measuring
- Purchasing
- Production
- Ready for Delivery
- Delivery
- Installation
Each one of these tasks also has an Estimated Start Date, Actual Start Date, Estimated Completion Date, Actual Completion Date and an Estimated Required Hours quantity. We're wondering about the best way to keep this information. Should we create individual fields within the Scope Tasks table, which would look like this (showing only those associated with the Drafting task):
- Drafting_Estimated Start Date
- Drafting_Actual Start Date
- Drafting_Estimated Completion Date
- Drafting_Actual Completion Date
- Drafting_Estimated Required Hours
Is there a better way to think about this and to organize this data?
All responses (
Answers (
