Software Issues: 1. System development - Do you have any standard for software development regarding computer language, GUI tools, real-time functions, etc? - Is there any organization to approve the software development, which is proposed for observatory/telescope/instrument. 2. Source Code Control - How do you control your Source Code? - Do you use some source code control system like SCCS? - Who manage the source code control, a single person or group of people? - When new software start to be developed, are Source Code Control forced to be applied to? 3. User feedback to the software - How do you reflect user's opinions to your software system. - How often do you apply or modify the system? - Do you apply quick bug fix when some serious bug is reported? 4. Quality Control - Which place is QC carried on, Garching or Chile? - How does QC evaluation affect observation sequence? 5. Remote Observation - When remote observation is carried, does some person(s) monitor the remote obervation in Chile? If so, can monitoring person(s) execute any commands to control Telescope/Instrument? 6. Scheduling tool - In Phase II Proposal Preparion (P2PP) system, are any scheduling tools ( like SPIKE ) running? - Is automatic scheduling of observation sequence applied for your telescope? 7. Data archives - Where is Data Archival systems running? - What is data flow from observatory site to Data Archival site? - Where do you hand observation data to observers? 8. Manual/Document - How often do you revise manuals/documents for software; immediate revision just after software revised ? - Do you have dedicated person(s) for manuals/documents? 9. Man power - How many persons are working for computer hardware/software; development, operation, and maintenance? - How do you communicate on software development/maintenance between observatroies in Chile and Headquarter in Garching? - What is a role of astronomers in software and computer hardware? Operation issues ( based on Noumaru-san' mail): 1. Entire organization of the telescope operation 2. Titles of operation staff (day crew, night crew, support scientist, night assistant, facility engineer, instrument technician, etc. anyone who involves in the operation of the telescope) 3. Task of each staff 4. Communication between day staff and night staff 5. If there are managers, what are their tasks and responsibilities? 6. The work flow of the troubleshooting, reporting and revising the manuals. 7. Work schedule and observation schedule management (person, database tools, managers work shift) 8. Human resources (special benefit for night work, high altitude work, policy on vacation leaves, etc.) 9. How to cope with the sudden schedule change (Communication with the relevant staff, time compensation to observers due to TOO observation or system problem and assignment change of the day/night crews) 10. Facility(like simulator), course and materials for the operation training. 11. How to promote the operation staff to the higher position. How to keep them interested in the job, if you intended to do so. 12. How to produce the professional operation staff with strong academic background (i.e. having Ph.D. in astronomy) 13. Any management/operation effort to make the telescope use more effective.