Difference between revisions of "DS-T"

From NavykI
Jump to: navigation, search
Line 1: Line 1:
''Design Systems and Technologie'' is a French based firm offering software products and expertise for the marine industry. They distribute, among others, [[AutoCad]], [[ShipConstructor]] and [[Rhinoceros]].
+
''Design Systems and Technologie'' is a French based firm offering software products and expertise for the marine industry. They are Navyk supplier for [[AutoCad]], [[ShipConstructor]], [[Rhinoceros]] and [[RhinoMarine]].
  
  

Revision as of 14:20, 19 February 2009

Design Systems and Technologie is a French based firm offering software products and expertise for the marine industry. They are Navyk supplier for AutoCad, ShipConstructor, Rhinoceros and RhinoMarine.


Communication

For an effective communication DS-T has certain requirements to the EMAIL HEADERS, they should always include:

  • name of the product(s) you are writing about (ex. GHS, ShipConstructor, ShipWeight, etc.)
  • core subject of the email (ex. quote request, tech-support, shipping update, etc.)
  • company name
  • if possible, a 3-4 word description (ex. heeling moments . . . , nest report . . . , hull weight prediction method, possible bug in . . . , etc.)


Here are some header examples:

  • GHS tech-support @ ABC: damstab2
  • ShipConstructor quote request by ABC
  • NavisWorks @ ABC: evaluation serial number request
  • etc.


The above will help their antispam system KEEP our email and address it to the appropriate channel.


When logging a TECH-SUPPORT QUERY, please always include the following at the beginning of your email:

  • product version (ex. GHS v11.02b, ShipConstructor 2008 v2.0, etc.)
  • operating system particulars (ex. WinXP pro sp2 - 32bit, Vista, Win2003 Server, etc.)
  • operating system language (ex. EN, FR, IT, etc.)
  • if applicable, version and language of host system (ex. Autocad 2008 EN, Rhinoceros v4 FR, etc.)


The above will help DS-T answer constructively, and focus their investigation when looking at potential malfunctions. Moreover:

  • be as descriptive as possible, while of course remaining as concise as possible (but rather write too much than not enough)
  • describe the desired goal of your action, and describe where and how you think "it goes wrong"
  • state your question(s) explicitly (ex. Question 1: . . ., Question 2: . . . )
  • very important: always include (or make available from the internet) the files you are working with (ex. GHS run & geometry files, SCon files, etc.)


Finally, do not hesitate to send hand notes, sketches, examples, etc. by telefax (+33 4 9291 1338). Sometimes a sketch tells more than a thousand words!


External links

Design Systems and Technologie corporate website