First of all I would like to thank all of those who have guided me along the way. This is the best site I have ever had the privilege of being a member of. My learning curve is still on the upward!
I would, once again, be grateful for some advice.
I am at the planning stage of designing a database (Access 2003) to service a particular workflow, for the tracking and eventual invoice of jobs carried out by tree surgeons, who cut vegetation from around a power grid. I would be grateful, once again, if someone could have a quick look at my initial design. Attached is a jpeg I have produced using Visio.
The power grid is split into 'Spans', essentially a line of poles connected to a substation. Each span is designated with a ‘Circuit Name’. Each circuit is contained within a Managed Unit (MU), which tells you the area/location of the underlying circuits and spans.
Sample Data would be:
Phase: 1 (relates to the phase of planned maintenance)
MU: 1299
Circuit Name: Camborne to Redruth
Span From: ZBU20
Span To: ZBU21
A surveyor is sent out to judge what needs to be done, ahead of any cutting. The surveying of each span attracts a fixed charge, and an invoice is generated according to the number of spans surveyed.
One particular work order may contain many spans. One particular work order would eventually result in a cutting invoice containing many spans at variable cost, separate to the survey invoice, but still of course relating to that work order.
I need to list each separate span from/to under one work order, to produce the survey invoice, and then to list each cutting job, to produce the cutting invoice. I am slightly confused at how to separate the tables for Surveying & Cutting, or even if I need to.
Each Individual work order will attract a single invoice for the sum of surveying and one single invoice for the sum of cutting.
In some instances, a single work order will be ‘Part-Cut’, but we would still invoice those spans that have been cut, leaving further invoicing to be carried out as and when the cutting progresses and is eventually ‘Completed’.
I would, once again, be grateful for some advice.
I am at the planning stage of designing a database (Access 2003) to service a particular workflow, for the tracking and eventual invoice of jobs carried out by tree surgeons, who cut vegetation from around a power grid. I would be grateful, once again, if someone could have a quick look at my initial design. Attached is a jpeg I have produced using Visio.
The power grid is split into 'Spans', essentially a line of poles connected to a substation. Each span is designated with a ‘Circuit Name’. Each circuit is contained within a Managed Unit (MU), which tells you the area/location of the underlying circuits and spans.
Sample Data would be:
Phase: 1 (relates to the phase of planned maintenance)
MU: 1299
Circuit Name: Camborne to Redruth
Span From: ZBU20
Span To: ZBU21
A surveyor is sent out to judge what needs to be done, ahead of any cutting. The surveying of each span attracts a fixed charge, and an invoice is generated according to the number of spans surveyed.
One particular work order may contain many spans. One particular work order would eventually result in a cutting invoice containing many spans at variable cost, separate to the survey invoice, but still of course relating to that work order.
I need to list each separate span from/to under one work order, to produce the survey invoice, and then to list each cutting job, to produce the cutting invoice. I am slightly confused at how to separate the tables for Surveying & Cutting, or even if I need to.
Each Individual work order will attract a single invoice for the sum of surveying and one single invoice for the sum of cutting.
In some instances, a single work order will be ‘Part-Cut’, but we would still invoice those spans that have been cut, leaving further invoicing to be carried out as and when the cutting progresses and is eventually ‘Completed’.
