About me
sorry, image blocked by browser. First nameEman
Last nameFatih
Residence PermitC (Permanent)/ Switzerland
ProfessionTechnical Documentation Specialist Since 1990
AddressRosentalstr.11, CH-4058 Basel, Switzerland
Telephoneshome: 0041.61.6 838 838 / Mobile: 0041.79.6 585 909
Emaileman.tek@gmail.com
Web pagehttp://eman.click-foto.net
Skype Skype Me™!

Technical Communicator

Expertise

Professional Experience

  • Technical Documentation Authoring
  • Technical Documentation Management
  • Technical Translation
  • Translation Management
  • Workflow Optimization
  • Review Process Design
  • Review Process Management
  • Collaboration Concept

PC Hardware

As I regularly upgrade my IT knowledge, I also upgrade my PC equipment:

My hardware experience includes:

  • Choosing/buying PC components and configuring my PC.
  • Assembling components and configuring Hard Drive.
  • Installing all necessary software.
  • Regular upgrade and maintenance as needed.
  • Helping friends with PC problems.

Main tools I used

  • Microsoft Office (W, EX, PPt, OL, VI)
  • Adobe Page Maker, Frame Maker, Acrobat, Photoshop
  • Documentum eRooms
  • Web Works
  • Microsoft SharePoint and SharePoint Designer

Other tools

  • MS Front Page
  • Solid Works
  • Wave Pad Sound Editor
  • Wiki, HTML, CSS, PHP
  • FTP
Expertise

Language

Level of knowledge

Comments

English Fluent written and spoken. This is the language I commonly use at work and daily practice
French Fluent written and spoken. Alliance Française diploma 1984, and practiced regularly.
Italian Very good written and spoken. Less practice than French and English
German Good / Conversational. Good knowledge, but less practice. Can easily be improved if necessary
Arabic Mother tongue 1. Born in Baghdad and almost mastered this language in practice.
Kurdish Mother tongue 2. Much less practice but read and understand a good deal.
Russian Simple knowledge I know the alphabet and a number of words. Familiarity without practice.
Worked for
F. Hoffmann La Roche

Solution Lifecycle Manager

July 2010 - on-going
Phonak / Sonova

Documentation Manager

June 2009 - May 2010
Roche Diagnostics
  • Technical Documentation
  • Online Help
  • Translation
May 2007 - May 2009
Credit Suisse

Creation of Documentation Maintenance Concept using SharePoint.

May-October 2005
UBS (CTB and RTB)
  • Software lifecycle document
  • Documentation Repository Concept
May 2002 - December 2003
Roche Pharma

Software Documentation

January 1998 - July 2001

Among others.

SharePoint

SharePoint is now one of the market standard content management and collaboration platforms.

My first experience with it was five years ago for a department in Creadit Suisse / Zurich designing a Document Maintenance Concept. The task involved complete analysis of the status quo. I then successfully designed a comprehensive solution using SharePoint, that facilitates collaboration and document management and assures appropriate workflow.

Four years later, I provided several solutions at Phonak_Systems Engineering Department in Staefa-Zurich, using SharePoint Server 2007 technologies.

What I can provide now for and with SharePoint:

  • Introduction to SharePoint. What is it about, what is it good for and what you can do with it.
  • Introductory training to new users. How to use SharePoint. Things to pay attention to. Tips and tricks.
  • Provide support to existing users in case of difficulties or questions.
  • Analyse business and technical requirements, then design a workflow solution.
  • Design and put in practice adequate and practical review process management.
  • Design and put in practice a Documentation Management Concept.
  • Migrate documents from an old platform into SharePoint.
  • Set adequate access rights, collaboration techniques and management layout.
  • Design ad-hoc solutions, depending on the requirements and within practical restrictions.
References
Phonak / Sonova

Dr Villa: moses.villa@hotmail.com

Dr Zbinden: paul.zbinden@hsr.ch

Roche Diagnostics andre.odermatt@roche.com
Credit Suisse

raphael.backaus@credit-suisse.ch

andreas.lugenbuehl@credit-suisse.ch

UBS (CTB and RTB)

Dr Konrad Weigl: konrad.weigl@ubs.com

sanjay.bhasin@ubs.com

Roche Pharma

Dr Neumann: norbert.neumann@roche.com

baerbel.fotteler@roche.com

stephan.laage-witt@roche.com

Temporary Assignments

In temporary assignments, a package offer may sometimes be an interesting and more efficient alternative for the employer.

Package Offer

A package offer essentially means:
Based on careful analysis of the requirements, setting a lower price for the entire assignment to be paid altogether in advance, rather than a monthly or hourly rate. You expect the work to be done optimally and leave the worry about the details to the expert.

Advantages of a package offer:

  • For you:
    • The overall cost will be reduced (e.g. by CHF 10000.- or more)
    • A possibility to get the work accomplished earlier.
    • Time management becomes the contractor's worry, not the employer's. The employer worry less about hours spent each day and concentrates on work accomplished.
  • For me: After the first month including analysis, I get the entire payment of the rest in advance by the end of the second month.

Example

You have a project for which you have estimated and planned six months with a budget of CHF 72000.-/6 = 12000.- per month.

My proposal

Within the first month, I perform careful analysis of the requirements and define together with you, the employer, the targets to achieve. First month is paid 12000 as initially agreed. Then I give you a package proposal of 50000.- for the five remaining months, instead of your planned 60000.- [72000 (original) - 12000(1st month) - 10000(reduction)=50000]

You can accept or reject this proposal, of course, but if you accept, you agree to pay the entire proposed package in advance by the end of the second month. Remember, this agreement takes place within the first month (which is paid normal), to give ample chance for both sides to cover the requirements. Also included in the agreement whether finishing the necessary tasks may be achieved sooner than planned. Concretely, if all the requirements are satisfied after four months, for instance, the contractor is allowed to terminate his service and leave. But on the other hand, if so agreed, if more time appears to be needed within the same predefined requirements, no extra payment is added.

This kind of offer is particularly interesting for mission critical assignments with tight budget and time. The project ends up costing less than predicted and probably even finished earlier. This gives an additional possibility to make improvements or adjustments as necessary.

Any further improvements or adjustments may then either be discussed separately, if significant work is required, or just carried out within the given time limit in case of minor impact.

Why Package Offer?

Experience shows that a lot of stress is caused both to the employer and the contractor in following hourly rates. This is particularly true when some days require more hours than usual.

  • For the employer, because more hours mean more pressure on the budget.
  • For the contractor, because this pressure causes extra stress that reduces efficiency.

Therefore, agreeing on a package means more peace of mind for both sides.

The agreement is written and signed by both, within the first month. In case of any unexpected changes to the requirements during the following months (some requirements abandoned, or some new added), the two sides meet and agree on how much this change impact the agreement, and if necessary, make an adjustment to it.


Files

Past professional experience: Avionics Technician.

Testing, Diagnosing, Repairing and Servicing Electronic Control Systems and various Aircraft Equipment and Devices of Boeing Aircrafts.

  • Auto-Brake and Skid Control System
  • Windshield Temperature Control System
  • Pressure Control System
  • Engine Control System
  • Miscellaneous

Documents to download:

ISO/DIS 6433 Technical product d
ISO/DIS 6433
Technical product documentation -- Part references
ISO 7200:2004
Technical product documentation -- Data fields in title blocks and document headers
ISO 7573:2008
Technical product documentation -- Parts lists
ISO/DIS 10209
Technical product documentation -- Vocabulary -- Terms relating to technical drawings, product definition and related products
ISO 10209-4:1999
Technical product documentation -- Vocabulary -- Part 4: Terms relating to construction documentation
ISO 11005:2010
Technical product documentation -- Use of main documents
ISO 11442:2006
Technical product documentation -- Document management
ISO 13567-1:1998
Technical product documentation -- Organization and naming of layers for CAD -- Part 1: Overview and principles
ISO 13567-2:1998
Technical product documentation -- Organization and naming of layers for CAD -- Part 2: Concepts, format and codes used in construction documentation
ISO/TR 13567-3:1999
Technical product documentation -- Organization and naming of layers for CAD -- Part 3: Application of ISO 13567-1 and ISO 13567-2
ISO 15226:1999
Technical product documentation -- Life cycle model and allocation of documents
ISO 15519-1:2010
Specification for diagrams for process industry -- Part 1: General rules
ISO/WD 15519-2
Specifications for diagrams for process industry -- Part 2: Measurement and control
ISO 16016:2000
Technical product documentation -- Protection notices for restricting the use of documents and products
ISO 16792:2006
Technical product documentation -- Digital product definition data practices
ISO/WD 16792
Technical product documentation -- Digital product definition data practices
ISO/TS 16952-1:2006
Technical product documentation -- Reference designation system -- Part 1: General application rules
ISO/TS 16952-10:2008
Technical product documentation -- Reference designation system -- Part 10: Power plants
ISO/TR 19033:2000
Technical product documentation -- Metadata for construction documentation
ISO/FDIS 29845
Technical product documentation -- Document types
ISO 81714-1:2010
Design of graphical symbols for use in the technical documentation of products -- Part 1: Basic rules
IEC 81714-2:2006
Design of graphical symbols for use in the technical documentation of products -- Part 2: Specification for graphical symbols in a computer sensible form, including graphical symbols for a reference library, and requirements for their interchange
IEC 81714-3:2004
Design of graphical symbols for use in the technical documentation of products -- Part 3: Classification of connect nodes, networks and their encoding
IEC 82045-1:2001
Document management -- Part 1: Principles and methods
IEC 82045-2:2004
Document management -- Part 2: Metadata elements and information reference model
ISO 82045-5:2005
Document management -- Part 5: Application of metadata for the construction and facility management sector
IEC/CD 82079-1
Preparation of instructions for use -- Structuring, content and presentation -- Part 1: General principles and detailed requirements