Int. no
| Department
| Manning Level
| ERP Adoption
| Task
| Tools
| Is Project Server Applicable?
| Interview – 1
| Finance Board of Corporate Finance Operational Controlling
| Upper manning level (80<ml<500)
| low adoption of ERP,high relevance for project
| decision making
| Excel, mail, phone
| Minimal but relevant
| Interview – 2
| Health insurance Board of Insurance service and products of Mathematics Actuary
| Upper manning level (80<ml<500)
| regular use of ERP,average relevancefrequent use of ERP,
| * answering to principal questions regarding product development * calculating regarding product development * financial reporting * statistics
| CD, phone, fax,
| Yes
| Interview – 3
| Board of Directors
| Nil
| nil
| * organization of a in-house conference
| Paper, personally, mail, phone
| yes
| Interview – 4
| Health insurance Board of Insurance service and products of Mathematics Actuary
| Upper manning level (80<ml<500)
| regular use of ERP,average relevancefrequent use of ERP,
| * calculation regarding the development / maintenance of products (high-level calculation, detail calculation, follow-up-calculation) * financial reporting with the objective, being able to decide concerning Rückstellungen - e.g. Asset Liability Management *) * statistics in the context of product inquiries - e.g. statistics of insuring-cases per member - e.g. statistics for supporting the sale-department * answering of question basilar - extremely huge projects (e.g. integration acquired new insurance-companies, merging of insurance-products, subject depending for technical integrations (incl. IT)) - overall views of competitor-products - comments concerning legal changes
| Phone, mail, word
|
| Interview – 5
| Health insurance Board of Insurance service and products of Project Management
| Upper manning level (80<ml<500)
| frequent use of ERP, low relevance per employee
| * realization of a new assurance product
| Paper, mail, orally,
| Yes
| Interview – 6
| Healthiness Management
| Low manning level (ml<80)
| frequent use of ERP,low relevance per employee
| * periodic screening for economization * e.g. visiting invalids
| word
| Minimal
| Interview – 7
| Company Organization
| Low manning level (ml<80)
| low adoption of ERP,high relevance for project
| * project leadership * e.g. forwarding information to the works council
| mail, phone, personally
| Yes
| Interview – 8
| Concern Revision
| Upper manning level (80<ml<500)
| low adoption of ERP,high relevance for project
| * e.g. scheduling an auditing plan for the next quarterly period * e.g. executing an audit
| Excel, word
| minimal
| Interview – 9
| “I’m representing the works council. There is no explicit representationin the organization chart.”
|
|
| * representing the interests of the employees (p.es. labor council or data protection officer)
|
|
| Interview – 10
| Company Organization
| Low manning level (ml<80)
| low adoption of ERP,high relevance for project
| * managing a project / collaboration in a project
| Mail, phone
| Yes
| Interview – 11
| Property management
| Upper manning level (80<ml<500)
| regular use of ERP,
| * Property Management (janitor) * Computer Aided Facility Management
|
| minimal
| Interview – 12
| Agencies within the Indoors offices (support) of Distribution
| Very high manning level (500<ml)
| frequent use of ERP,low relevance per employee
| * ~ 70 % : support of the field services * ~ 60% thereof forwarding of information/assignments to field agents * ~ 40% thereof processing on incoming acquisition * ~ 30 % : customer care (if the customer come with a question to an agency) (But the objective is, to pass this task to the centralized customer care center)
| Mail, fax)
| Minimal
| Interview – 13
| Board of Director
|
|
| * supporting the corporate governance * periodically meeting F1 (one layer below the board of...
Continue Reading
Please join StudyMode to read the full document