size=3>Reading List
style="mso-bidi-font-style: normal">
face="Times New Roman">Architectural Graphics 4th Ed, Francis D. K.
Ching
style="mso-bidi-font-style: normal">
face="Times New Roman">Professional Practice of Architectural Detailing, Wakita
& Linde
style="mso-bidi-font-style: normal">
size=3>Professional Practice of Architectural Working Drawings, Wakita &
Linde
size=3>CAD Managers Handbook, Grabowski
size=3>Managing Autocad in the Design Firm, Vagts
size=3>The Digital Architect, Sanders
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Gordon Price" <gordon(thorn)@albedoconsulting.com> wrote in
message
href="news:4843127@discussion.autodesk.com">news:4843127@discussion.autodesk.com...
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
size=3>My old office has hired a new IT Manager
with the intent that he also become the CAD Manager. He comes with strong IT
skills, very basic AutoCAD R14 skills, and little or no knowledge of
Architecture as a profession. I am putting together a list of topics that seem
important, and I am wondering if anyone sees something important that I
missed. To the extent that it makes a difference, the office is small (30
total, 25 architecture staff, 20 of them using CAD), VERY design oriented
(libraries, museums, campus buildings), currently using a moderately
customized AutoCAD 2005 and considering ADT or Revit. Anyway, here is my list
as it stands, italics indicate topics more related to architecture than
cad:
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
style="mso-bidi-font-style: normal">
face="Times New Roman">Architectural drawing types: Plan, Section,
Elevation, relationships.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
style="mso-bidi-font-style: normal">
face="Times New Roman">Line weight, pouche, graphic
hierarchy.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
style="mso-bidi-font-style: normal">
size=3>Design and documentation process: PD, SD, DD, CD & CA phases,
relationships to each other and CAD processes, intended audience for
graphics, reuse of work in later phases and building lifecycle.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Output control: CTBs/STBs, PlotStyles,
pltters, color, and relationships to line weight, screen, etc.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Base files and Sheet files: what is drawn
where and why.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>ModelSpace and PaperSpace: : what is drawn
where and why, relationship to scale.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Scale: annotation scale, unit conversion
scale, plot scale, view port scale.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Units: architectural, metric, unitless
AutoCAD.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Blocks: what should be made into blocks, what
should be included in blocks, how blocks are built (layer 0 issues, block
orientation, etc.)
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Xrefs: relationship to blocks, relationship to
layers, reuse of drawn information (in house reuse as well as consultant
reuse, implications of forced properties)
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Dimension & text styles: relationship to
scale, child DimStyles.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Office standards: implications for
productivity, staff sharing, new hire training. Enforcement
philosophy.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Customization:
implications for productivity, relationship to standards enforcement,
implications and opportunities for user customization, customization
location and relationship to sharing, upgrades, etc.
size=3>Reading List
style="mso-bidi-font-style: normal">
face="Times New Roman">Architectural Graphics 4th Ed, Francis D. K.
Ching
style="mso-bidi-font-style: normal">
face="Times New Roman">Professional Practice of Architectural Detailing,
Wakita & Linde
style="mso-bidi-font-style: normal">
size=3>Professional Practice of Architectural Working Drawings, Wakita &
Linde
size=3>CAD Managers Handbook, Grabowski
size=3>Managing Autocad in the Design Firm, Vagts
size=3>The Digital Architect, Sanders
Thanks for any input,
Gordon
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Ric Hammond" <
href="mailto:rhammond@caruana.com">rhammond@caruana.com> wrote in
message
href="news:4843153@discussion.autodesk.com">news:4843153@discussion.autodesk.com...
Training, Training, Training.
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Gordon Price" <gordon(thorn)@albedoconsulting.com> wrote in
message
href="news:4843127@discussion.autodesk.com">news:4843127@discussion.autodesk.com...
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
size=3>My old office has hired a new IT Manager
with the intent that he also become the CAD Manager. He comes with strong IT
skills, very basic AutoCAD R14 skills, and little or no knowledge of
Architecture as a profession. I am putting together a list of topics that
seem important, and I am wondering if anyone sees something important that I
missed. To the extent that it makes a difference, the office is small (30
total, 25 architecture staff, 20 of them using CAD), VERY design oriented
(libraries, museums, campus buildings), currently using a moderately
customized AutoCAD 2005 and considering ADT or Revit. Anyway, here is my
list as it stands, italics indicate topics more related to architecture than
cad:
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
style="mso-bidi-font-style: normal">
face="Times New Roman">Architectural drawing types: Plan, Section,
Elevation, relationships.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
style="mso-bidi-font-style: normal">
face="Times New Roman">Line weight, pouche, graphic
hierarchy.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
style="mso-bidi-font-style: normal">
size=3>Design and documentation process: PD, SD, DD, CD & CA phases,
relationships to each other and CAD processes, intended audience for
graphics, reuse of work in later phases and building lifecycle.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Output control: CTBs/STBs, PlotStyles,
pltters, color, and relationships to line weight, screen, etc.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Base files and Sheet files: what is drawn
where and why.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>ModelSpace and PaperSpace: : what is drawn
where and why, relationship to scale.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Scale: annotation scale, unit conversion
scale, plot scale, view port scale.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Units: architectural, metric, unitless
AutoCAD.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Blocks: what should be made into blocks,
what should be included in blocks, how blocks are built (layer 0 issues,
block orientation, etc.)
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Xrefs: relationship to blocks, relationship
to layers, reuse of drawn information (in house reuse as well as
consultant reuse, implications of forced properties)
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Dimension & text styles: relationship to
scale, child DimStyles.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Office standards: implications for
productivity, staff sharing, new hire training. Enforcement
philosophy.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Customization:
implications for productivity, relationship to standards enforcement,
implications and opportunities for user customization, customization
location and relationship to sharing, upgrades, etc.
size=3>Reading List
style="mso-bidi-font-style: normal">
face="Times New Roman">Architectural Graphics 4th Ed, Francis D.
K. Ching
style="mso-bidi-font-style: normal">
face="Times New Roman">Professional Practice of Architectural Detailing,
Wakita & Linde
style="mso-bidi-font-style: normal">
size=3>Professional Practice of Architectural Working Drawings, Wakita &
Linde
size=3>CAD Managers Handbook, Grabowski
size=3>Managing Autocad in the Design Firm, Vagts
size=3>The Digital Architect, Sanders
Thanks for any input,
Gordon
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Gordon Price" <gordon(thorn)@albedoconsulting.com> wrote in
message
href="news:4843127@discussion.autodesk.com">news:4843127@discussion.autodesk.com...
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
size=3>My old office has hired a new IT Manager
with the intent that he also become the CAD Manager. He comes with strong IT
skills, very basic AutoCAD R14 skills, and little or no knowledge of
Architecture as a profession. I am putting together a list of topics that seem
important, and I am wondering if anyone sees something important that I
missed. To the extent that it makes a difference, the office is small (30
total, 25 architecture staff, 20 of them using CAD), VERY design oriented
(libraries, museums, campus buildings), currently using a moderately
customized AutoCAD 2005 and considering ADT or Revit. Anyway, here is my list
as it stands, italics indicate topics more related to architecture than
cad:
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
style="mso-bidi-font-style: normal">
face="Times New Roman">Architectural drawing types: Plan, Section,
Elevation, relationships.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
style="mso-bidi-font-style: normal">
face="Times New Roman">Line weight, pouche, graphic
hierarchy.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
style="mso-bidi-font-style: normal">
size=3>Design and documentation process: PD, SD, DD, CD & CA phases,
relationships to each other and CAD processes, intended audience for
graphics, reuse of work in later phases and building lifecycle.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Output control: CTBs/STBs, PlotStyles,
pltters, color, and relationships to line weight, screen, etc.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Base files and Sheet files: what is drawn
where and why.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>ModelSpace and PaperSpace: : what is drawn
where and why, relationship to scale.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Scale: annotation scale, unit conversion
scale, plot scale, view port scale.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Units: architectural, metric, unitless
AutoCAD.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Blocks: what should be made into blocks, what
should be included in blocks, how blocks are built (layer 0 issues, block
orientation, etc.)
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Xrefs: relationship to blocks, relationship to
layers, reuse of drawn information (in house reuse as well as consultant
reuse, implications of forced properties)
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Dimension & text styles: relationship to
scale, child DimStyles.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
face="Times New Roman" size=3>Office standards: implications for
productivity, staff sharing, new hire training. Enforcement
philosophy.
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Customization:
implications for productivity, relationship to standards enforcement,
implications and opportunities for user customization, customization
location and relationship to sharing, upgrades, etc.
size=3>Reading List
style="mso-bidi-font-style: normal">
face="Times New Roman">Architectural Graphics 4th Ed, Francis D. K.
Ching
style="mso-bidi-font-style: normal">
face="Times New Roman">Professional Practice of Architectural Detailing,
Wakita & Linde
style="mso-bidi-font-style: normal">
size=3>Professional Practice of Architectural Working Drawings, Wakita &
Linde
size=3>CAD Managers Handbook, Grabowski
size=3>Managing Autocad in the Design Firm, Vagts
size=3>The Digital Architect, Sanders
Thanks for any input,
Gordon
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Paul Caruthers" <
href="mailto:pcaruthers@lamontagnebuilders.com">pcaruthers@lamontagnebuilders.com>
wrote in message
href="news:4843177@discussion.autodesk.com">news:4843177@discussion.autodesk.com...
My only input would his/her exp. Rel 14 is
a long time ago in the software world not to mention the lack of experience in
the Architectural world, he/she would need some training also just to be on
the same page as your entry level people. I know a lot of IT people wear
several hats, ours has 3 I think. I would be very concerned at this
lack of knowledge and experience.
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Gordon Price" <gordon(thorn)@albedoconsulting.com> wrote in
message
href="news:4843270@discussion.autodesk.com">news:4843270@discussion.autodesk.com...
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Paul Caruthers" <
href="mailto:pcaruthers@lamontagnebuilders.com">pcaruthers@lamontagnebuilders.com>
wrote in message
href="news:4843177@discussion.autodesk.com">news:4843177@discussion.autodesk.com...
My only input would his/her exp. Rel 14
is a long time ago in the software world not to mention the lack of
experience in the Architectural world, he/she would need some training also
just to be on the same page as your entry level people. I know a lot
of IT people wear several hats, ours has 3 I think. I would be
very concerned at this lack of knowledge and
experience.
Paul, good point but beyond my scope. The
person is hired and I am trying to help him get up to speed, and the office to
understand what is reasonable to expect. Should be fun 😉
Best,
size=2>Gordon
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Gordon Price" <gordon(thorn)@albedoconsulting.com> wrote in
message
href="news:4843296@discussion.autodesk.com">news:4843296@discussion.autodesk.com...
Part of my premise in putting together the list
is to help him realize just how much understanding of the actual architectural
process is required, as well as help him plan a process to learn it. We'll
see.
Best,
size=2>Gordon
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Gordon Price" <gordon(thorn)@albedoconsulting.com> wrote in
message
href="news:4843296@discussion.autodesk.com">news:4843296@discussion.autodesk.com...
Part of my premise in putting together the list
is to help him realize just how much understanding of the actual architectural
process is required, as well as help him plan a process to learn it. We'll
see.
Best,
size=2>Gordon
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"Gordon Price" <gordon(thorn)@albedoconsulting.com> wrote in
message
href="news:4843751@discussion.autodesk.com">news:4843751@discussion.autodesk.com...
Lest anyone think otherwise, the guy is bright,
he was a good personality fit with an office that needs a good personality
fit, and I am looking to make his transition as painless and quick as
possible. Certainly the office knows it will take time, as does he.
Maybe my question could have been better
posed, "What knowledge would one need to be an Architectural CAD Manager".
Anyway, I think with the addition of some training comments, my list is pretty
complete, if by no means deep. Should be enough to get him
started.
best all,
size=2>Gordon