File information: | |
File name: | M376 Planning an Information Center; Struense.pdf [preview M376 Planning an Information Center; Struense] |
Size: | 674 kB |
Extension: | |
Mfg: | IBM |
Model: | M376 Planning an Information Center; Struense 🔎 |
Original: | M376 Planning an Information Center; Struense 🔎 |
Descr: | IBM share SHARE_61_Proceedings_Volume_1_Summer_1983 M376 Planning an Information Center; Struense.pdf |
Group: | Electronics > Other |
Uploaded: | 05-11-2021 |
User: | Anonymous |
Multipart: | No multipart |
Information about the files in archive: | ||
Decompress result: | OK | |
Extracted files: | 1 | |
File name M376 Planning an Information Center; Struense.pdf :SSHARE~ SHARE SESSION REPORT I. INTRODUCTION 61 M376 Information Center - Plans & Controls 161 SHARE NO. SESSION NO. SESSION TITLE ATTENDANCE The time is now for the Information Center concept. We have a solution to 0 ffer to the user. Information Center Barbara S. Witzig FRK PROJECT SESSION CHAIRMAN INS!. CODE As with all solutions, they must be planned for and administered with care, caution and yet expectation. Take care to plan in detail to Federal Reserve Board, 20th & Const Ave., N.W., Washington, D.C. 20051 insure success. Take caution against political battles to be waged. Stop 166 (202) 452-2806 And maintain expectation for the useful benefits that can come from SESSION CHAIRMAN'S COMPANY, ADDRESS, AND PHONE NUMBER this function. II. KNOW YOUR BUSINESS Even if you already have an Information Center functioning, this will PLANNING AN INFORMATION CENTER be useful. It may cause you to think. Treat the Information Center as a business not a technical function, WHY? 1. It, will force new thinking by traditional data processing technical people. R:lch Struense 2. Your end users will be non-technical people for the most part (non-technical D. P. that is ). Federal Express Corporation 3. Your competition ( and it will come, if not already there) is Box 727 another ousiness and'you must be able to meet them on their Memp |
Date | User | Rating | Comment |