Main conclusions recommandations
 
Conclusions and recommendations - general issues  
  1. Appropriate assessment of issues related to transition from existing system to the integrated SMOK System is necessary.
  2. An Interface control document is essential to be produced and maintained without delay.
  3. At least on the beginning, acronyms, if used, should always be accompanied by the Task Description to insure full understanding of the tasks under discussion.
  4. Use of IMGW Internet and intranet (www.imgw.pl) as the communication platform for better dissemination of information and communication about the project.
Conclusions - general issues  
  1. Optimal use of Internet information systems should be fully exploited, such as web sites, email, ftp, user groups and news groups.
  2. Pragmatic approach easing communication between different suppliers (without jeopardy to QAP) is necessary.
  3. To promote understanding of system components and interconnectivity the use of diagrams icons and cartoons to represent components and tasks is strongly recommended.
    As an example, the following figure was developed and used very successfully to represent the Hydrologic Forecast system during the USA NWS modernization. This concept proved to be so successful that it was eventually used as the starting point for all meeting discussions concerning the River Forecast system, and other components. Additional figures were developed to represent all major system components, such as the Meteorological Office Forecast System, NEXRAD Doppler RADAR etc.
Conclusions - specific issues  
  1. Integration documents
    1. Data Exchange query - to be answered by Task Leaders and to be disseminated to Contractors.
    2. Data amount - on-line availability restricted to 7-10 days
    3. O&M costs to be assessed asap
  2. Functional design of the future operational use of SMOK
    1. Data Flow charts must be prepared asap (B2.2.3)
    2. user requirements : syno, hydrology (PC based), conversion is required , a need for clear procedures
    3. Parallel data exchange (files) practice should be maintained - this is relevant to pragmatic solutions implemented at IMGW since long (“going through verified and working channels”)
    4. Information exchange between different teams is an universal problem, creation of interdisciplinary teams may help.
  3. Preparation of the next SMOK System Integration Seminar
    1. Presenters should be strongly encouraged to produce well thought out high quality slides for seminars.
    2. Copies of all slides should be available and handed out before the presentations.
    3. At System Integration Seminars, the task leaders should lead the task discussions. They should always introduce themselves to the audience in a relatively formal manner, such as:
      My name is: ________
      My Title is: _________
      I am the manager of _____Task.
      The Task Contractor is _________.
  4. IMGW Integration Team structure:
    1. A Data Administrator, Computer System Administrator, Hydrologic Forecast System Administrator should be appointed before the integration process.
    2. Issues related to the maintenance of various sub-systems must be solved at the central level (similarily to the IT and telecommunication)