Autodesk Technology Managers Forum
Share your knowledge, ask questions, and engage with fellow CAD/BIM Managers.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Topics for an Architectural CAD Manager

11 REPLIES 11
Reply
Message 1 of 12
Anonymous
209 Views, 11 Replies

Topics for an Architectural CAD Manager



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>
 



  1. 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.



  2. 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.



  3. style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in">
    style="mso-bidi-font-style: normal">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.


  4. 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.


  5. 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.


  6. 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.


  7. 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.


  8. 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.


  9. 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.)


  10. 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)


  11. 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.


  12. 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.


  13. 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 Manager’s Handbook, Grabowski



size=3>Managing Autocad in the Design Firm, Vagts



size=3>The Digital Architect, Sanders


 

 

Thanks for any input,

Gordon
11 REPLIES 11
Message 2 of 12
Anonymous
in reply to: Anonymous


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>
 



  1. 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.



  2. 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.



  3. 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.


  4. 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.


  5. 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.


  6. 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.


  7. 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.


  8. 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.


  9. 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.)


  10. 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)


  11. 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.


  12. 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.


  13. 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 Manager’s Handbook, Grabowski



size=3>Managing Autocad in the Design Firm, Vagts



size=3>The Digital Architect, Sanders


 

 

Thanks for any input,

Gordon
Message 3 of 12
Anonymous
in reply to: Anonymous


I guess I am looking at knowledge the CAD Manager
must have, and assuming that passing on that knowledge to users is a part of the
picture. However, specifically mentioning training, the pitfalls of not or doing
it poorly, etc should be there.

 

best,

Gordon


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">


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>
 



  1. 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.



  2. 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.



  3. 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.



  4. 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.


  5. 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.


  6. 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.


  7. 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.


  8. 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.


  9. 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.)


  10. 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)


  11. 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.


  12. 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.


  13. 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 Manager’s Handbook, Grabowski



size=3>Managing Autocad in the Design Firm, Vagts



size=3>The Digital Architect, Sanders


 

 

Thanks for any input,

Gordon
Message 4 of 12
Anonymous
in reply to: Anonymous


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 Caruthers


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>
 



  1. 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.



  2. 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.



  3. 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.


  4. 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.


  5. 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.


  6. 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.


  7. 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.


  8. 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.


  9. 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.)


  10. 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)


  11. 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.


  12. 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.


  13. 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 Manager’s Handbook, Grabowski



size=3>Managing Autocad in the Design Firm, Vagts



size=3>The Digital Architect, Sanders


 

 

Thanks for any input,

Gordon
Message 5 of 12
Anonymous
in reply to: Anonymous


 


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">


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,

Gordon
Message 6 of 12
Anonymous
in reply to: Anonymous


Well, cross your fingers, hopefully this person
knows how far behind they are, and is willing to seekout and get some
training.  Best of luck.

 

Paul Caruthers


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">


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
Message 7 of 12
Anonymous
in reply to: Anonymous


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,

Gordon
Message 8 of 12
Anonymous
in reply to: Anonymous


Watch yourself, you may just be training him 40
hours a week for 3 weeks straight as a favor and not getting any of your own
work done.

 

How can someone Hire a person with NO knowledge of
Architecture to be an integrual part of the architecture process?


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
Message 9 of 12
Anonymous
in reply to: Anonymous


Gordon,

 

Without the knowledge and experience, it's going to
be hard for him to gain respect and credibility, not to mention actually do
something really useful in CAD management.

I thought somebody had to have knowledge and
experience in order to be hired to do something.

 

Alfredo Medina


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
Message 10 of 12
Anonymous
in reply to: Anonymous


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,

Gordon
Message 11 of 12
Anonymous
in reply to: Anonymous

Here's a CAD Manager Job Description I wrote a couple years ago.

Ciao!
~Terry
------------------------------------------------------------------------

Responsibilities:
<>$ Oversee all aspects of Primary CAD Software Packages and CAD
Software additions
<>$ Develop, Implement and Maintain CAD Company Graphic Standards
<>$ Provide User Training– Hands-On, Seminars and Support including
Documentation and Intranet
<>$ Coordinate and Facilitate Projects CAD Documentation Set-ups with
Project Managers / Project Team
<>$ Coordinate and Facilitate CAD Drawings Collaboration between
Offices, Owners and Consultants
<>$ Develop, Implement and Maintain Company and Manufacturer Symbol
Libraries
<>$ Coordinate Hardware usage and maintenance; Coordinate with Strategic
Technology Plan
<>$ Maintain Training and Knowledge of CAD Technologies and Industry
Practices

<> Goals: <>
$ Optimize the effective and efficient usage of the CAD throughout the
company
$ Insure CAD Drawing Standards are consistent and quality control for
CAD Drawings
$ Increase accuracy and productivity and profitability throughout a
project and the company
$ Increase Knowledge and Abilities with CAD Software and CAD Technologies

------------------------------------------------------------------------

Gordon Price wrote:

> 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:
>
>
> 1. Architectural drawing types: Plan, Section, Elevation,
> relationships.
> 2. Line weight, pouche, graphic hierarchy.
> 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.
> 4. Output control: CTBs/STBs, PlotStyles, pltters, color, and
> relationships to line weight, screen, etc.
> 5. Base files and Sheet files: what is drawn where and why.
> 6. ModelSpace and PaperSpace: : what is drawn where and why,
> relationship to scale.
> 7. Scale: annotation scale, unit conversion scale, plot scale, view
> port scale.
> 8. Units: architectural, metric, unitless AutoCAD.
> 9. Blocks: what should be made into blocks, what should be included
> in blocks, how blocks are built (layer 0 issues, block
> orientation, etc.)
> 10. Xrefs: relationship to blocks, relationship to layers, reuse of
> drawn information (in house reuse as well as consultant reuse,
> implications of forced properties)
> 11. Dimension & text styles: relationship to scale, child DimStyles.
> 12. Office standards: implications for productivity, staff sharing,
> new hire training. Enforcement philosophy.
> 13. Customization: implications for productivity, relationship to
> standards enforcement, implications and opportunities for user
> customization, customization location and relationship to
> sharing, upgrades, etc.
>
> Reading List
>
> Architectural Graphics 4th Ed, Francis D. K. Ching
>
> Professional Practice of Architectural Detailing, Wakita & Linde
>
> Professional Practice of Architectural Working Drawings, Wakita & Linde
>
> CAD Manager’s Handbook, Grabowski
>
> Managing Autocad in the Design Firm, Vagts
>
> The Digital Architect, Sanders
>
>
>
> Thanks for any input,
> Gordon
Message 12 of 12
Anonymous
in reply to: Anonymous


Gordon,

 

I don't doubt that the guys is bright. I might be
bright, too, but I can't repair my car myself. I need a mechanic to do it. A CAD
Manager is supposed to know more than the guys to whom he is going to give
guidelines and tools for doing CAD work. You can't give him this in some
training sessions.

 

Alfredo


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

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Administrator Productivity


Autodesk Design & Make Report