T
TimLeonard
I don't really think so, Sounds like I just clouded up ouHmmm. What you write leads me to believe I have been laboring under
fundamental incorrect assumption.
understanding...Perhaps I just need to change or explain m
approach/logic better
This is fact true...I have been assuming that, since you wrote that
PanelData was derived from data "exported from a field panel and onl
contains what is programmed in the panel",
We are generating CompareData from PanelData
Only what has been programmed in the panel OR Deleted from the pane
will be in the PanelData and thus on the CompareData
We are generating Summary from CompareData
"Summary sheet in theory, should have all the programmed rows/cell
populated the same as the CompareData"
that we could regenerate Summary at any time, retaining changes that ha
been made manually. (after reviewing for errors and so forth). So
would intend to generate a fresh Summary sheet (retaining th
appropriate additions) whenever a new PanelData sheet was downloade
(and a new CompareData sheet generated).
In other words, I assumed it should never be the case, with a freshl
generated Summary sheet, that there could be rows on CompareData/Pane
Data which are "waiting" to be placed on the Summary sheet until th
"as-built drawings".
The methodology also assumes that we will generate a fresh Summary shee
whenever PanelData is updated. That being the case, the concept of dat
on CompareData that is not on Summary representing deletions shoul
hold.
Please clarify.
Let me try to explain it this way...Perhaps we could liken the summar
sheet as a forever ongoing updating living spreadsheet. I say thi
because the engineer could have several jobs that their working on an
it could take several months before one of the jobs gets installed, a
times some jobs get installed in phases that require devices to b
demo'd/deleted and then re-installed during the remodel/buildout.
Here is a good example...The job could be a full floor in an offic
building that gets completely demo'd at the same time the engineer i
designing the remodel. So the engineer has taken the floor plan an
determined which devices need to be deleted from the summary sheet. H
now merges the new floorplan on the drawing and begins placing th
required devices on the drawing. These new devices have differen
devicelabels and maybe extendedlabels. Now during the field inspectio
the technician is required to install another device...under my curren
process, this device would then be on the compareData sheet and not o
the Summary sheet since it did not start with the engineer...
I think the fix is rather than waiting to asbuilt the device, I think i
needs to to have a process change that will avoid ever having a devic
on the compareData that is not on the Summary Sheet...Perhaps having th
technician call the engineer to get the device number and thu
populating the summary sheet with the added device, this would preven
the comparedata sheet from having a device that the summary doesn't.
So if we are creating the summarysheet each time the comparedata shee
is created and it keeps the manually entered data then I think we ar
accomplishing the need end result as long as I make the process chang
stated above...
However what will happen when comparing the comparedata and summar
sheets and the labels don't match. The comparedata labels should tak
precedence since it is what is programmed in the field. will there b
an option to update or will it automatically do the update when i
recreates the summary sheet?
+-------------------------------------------------------------------
+-------------------------------------------------------------------