Customs Tariff_ Section VI_ English version by wuyunyi

VIEWS: 25 PAGES: 101

									                                  149




 SECTION VI. TECHNICAL REQUIREMENTS
(INCLUDING IMPLEMENTATION SCHEDULE)
150                                                                                            Section VI. Technical Requirements




                                      TABLE OF CONTENTS


A. BACKGROUND........................................................................................ 155
      A.1     THE PURCHASER ............................................................................... 155
              A.1.1 AGENCY’S LEGAL BASIS, ORGANIZATIONAL ROLE, CORE
                    OBJECTIVES ............................................................................................... 155
      A.2     BUSINESS OBJECTIVES OF THE PURCHASER .................................... 156
              A.2.1 OVERVIEW OF THE CURRENT BUSINESS OBJECTIVES, PROCEDURES,
                    AND PROCESSES ........................................................................................ 156
              A.2.2 OVERVIEW OF THE CHANGES IN OBJECTIVES, PROCEDURES, AND
                    PROCESSES AND EXPECTED BENEFITS OF THE SYSTEM .............................. 156
      A.3     ACRONYMS USED IN THESE TECHNICAL REQUIREMENTS ............... 157
      A.4     CORE OBJECTIVES AND BUSINESS FRAMEWORK ............................ 158
      A.5     CURRENT STATUS.............................................................................. 159
      A.6     SCOPE OF WORK OF SUPPLIER ....................................................... 160
              A.6.1 SUPPLIER’S DUTIES ...................................................................................160
              A.6.2 WHAT IS NOT THE SUPPLIER’S DUTY .............................................160
              A.6.3 PURCHASER’S DUTIES ................................................................................160


B. FUNCTIONAL PERFORMANCE REQUIREMENTS OF THE
   SYSTEM..................................................................................................... 162
      B.1     GENERAL FUNCTIONAL REQUIREMENTS OF THE ACT .................... 162
              B.1.1     MULTILINGUAL .......................................................................................... 162
              B.1.2     GRAPHICAL USER INTERFACE....................................................................162
              B.1.3     SEARCHING, SELECTING AND FILTERING ...................................................163
              B.1.4     SEARCH/REPLACE CAPABILITY .................................................................163
              B.1.5     CT ATTRIBUTES ........................................................................................163
              B.1.6     SAVING AND EXPORT OF DATA...................................................................164
              B.1.7     DATA PRINTING .........................................................................................164
              B.1.8     ACCESS TO THE ACT AND DATA................................................................ 164
      B.2     USER VIEWS OF THE ACT .............................................................. 164
      B.3     USER GROUPS OF THE ACT .......................................................... 164
              B.3.1 PASSING THE CUSTOMS TARIFF ..................................................................166
                        B.3.1.1     Analysis and simulations ................................................................................ 166
                        B.3.1.2     Exporting data for GZAOP ............................................................................ 167
              B.3.2 USING THE CUSTOMS TARIFF .....................................................................167
                        B.3.2.1     Findings and Opinions on classification of goods within the CT ................... 167
                        B.3.2.2     Elements of Risk Analysis .............................................................................. 168
Section VI. Technical Requirements                                                                                                               151




                       B.3.2.3      List of Goods.................................................................................................. 168
                       B.3.2.4      The Tariff Calculator ..................................................................................... 168
             B.3.3 UPDATING THE CUSTOMS TARIFF .............................................................. 169
             B.3.4 PUBLISHING ON THE INTERNET .................................................................. 169


C. TECHNICAL SPECIFICATIONS ......................................................... 170
    C.1      GENERAL TECHNICAL REQUIREMENTS........................................... 170
             C.1.1     GENERAL TECHNICAL REQUIREMENTS OF THE ACT .................................. 170
             C.1.2     GENERAL TECHNICAL REQUIREMENTS FOR WEB PUBLISHING................... 170
             C.1.3     LANGUAGE SUPPORT ................................................................................ 170
             C.1.4     DATES ....................................................................................................... 171
    C.2      NETWORK AND COMMUNICATIONS SPECIFICATIONS ..................... 171
             C.2.1 LOGICAL AND PHYSICAL ORGANIZATION OF THE CDRC
                   COMMUNICATIONS NETWORK .................................................................... 171
             C.2.2 LOGICAL CONNECTION SCHEME OF THE CDRC COMMUNICATIONS
                   NETWORK .................................................................................................. 172
                       C.2.2.1      Municipal Institute for Automatic Data Processing - GZAOP ....................... 173
                       C.2.2.2      Central location (CL) ..................................................................................... 173
                       C.2.2.3      Type1 locations .............................................................................................. 174
                       C.2.2.4      Type2 locations .............................................................................................. 174
                       C.2.2.5      Type3 locations .............................................................................................. 174
                       C.2.2.6      Type4 locations .............................................................................................. 175
             C.2.3 FUNCTIONAL STRUCTURE OF THE NETWORK............................................. 175
                       C.2.3.1      Network Topology ......................................................................................... 175
                       C.2.3.2      Internet Access ............................................................................................... 175
                       C.2.3.3      The CDRC Business Application ................................................................... 175

    C.3      COMPUTING HARDWARE SPECIFICATIONS ...................................... 175

    C.4      SOFTWARE SPECIFICATIONS ............................................................ 176
             C.4.1 GENERAL REQUIREMENTS ......................................................................... 176
             C.4.2 GENERAL-PURPOSE SOFTWARE ................................................................ 176
             C.4.3 DATABASE SOFTWARE AND SOFTWARE DEVELOPMENT TOOLS ................ 176
    C.5      SERVICE SPECIFICATIONS ................................................................ 176
             C.5.1 PREPARATION OF THE INITIAL STATUS ...................................................... 176
             C.5.2 SYSTEM INTEGRATION .............................................................................. 177
             C.5.3 INSTALLATION AND CONFIGURATION OF APPLICATIONS AND
                   DATABASES .............................................................................................. 178
             C.5.4 INSTALLATION AND IMPLEMENTATION OF THE ACT .................................. 178
             C.5.5 TRAINING AND TRAINING MATERIALS ...................................................... 178
                       C.5.5.1      User Training ................................................................................................. 178

    C.6      SERVICES TO BE PROVIDED UNDER A SEPARATE, TO-BE-AGREED
             “CUSTOMER SERVICES CONTRACT” ............................................... 179
             C.6.1 SUPPORT ................................................................................................... 179
                       C.6.1.1      Technical Support .......................................................................................... 180
152                                                                                                  Section VI. Technical Requirements




                         C.6.1.2     Warranty Service ............................................................................................ 180
                         C.6.1.3     User support/Hot-line ..................................................................................... 181
                         C.6.1.4     Technical Assistance ...................................................................................... 181
               C.6.2     SYSTEM INTEGRATION ......................................................................181
               C.6.3     USER TRAINING .........................................................................................181
               C.6.4     UPGRADING AND UPDATING......................................................................181
               C.6.5     CHANGE ORDER PROCEDURE ....................................................................181
               C.6.6     TECHNICAL CONSULTATION ......................................................................182
               C.6.7     TROUBLESHOOTING AND MAINTENANCE...................................................182
      C.7      DOCUMENTATION -- GENERAL REQUIREMENTS ............................. 182
               C.7.1 REPORTS ...................................................................................................182
               C.7.2 PERIODIC SUBMITTALS/DELIVERABLES .....................................................183
      C.8      DOCUMENTATION - SOFTWARE VERIFICATION AND VALIDATION
               PLAN (SVVP) .................................................................................... 184
      C.9      DOCUMENTATION - SOFTWARE CONFIGURATION MANAGEMENT
               PLAN (SCMP) ................................................................................... 185
      C.10 DOCUMENTATION - SOFTWARE REQUIREMENTS SPECIFICATION
           (SRS) ................................................................................................. 189
      C.11 DOCUMENTATION - SOFTWARE DESIGN DESCRIPTION (SDD) ....... 192
      C.12 DOCUMENTATION - USER DOCUMENTATION................................... 193
               C.12.1 USER DOCUMENTATION GENERAL REQUIREMENTS...................................193
                         C.12.1.1    Content ........................................................................................................... 193
                         C.12.1.2    Format ............................................................................................................ 194
                         C.12.1.3    Body of the User Document ........................................................................... 194
                         C.12.1.4    Error Messages ............................................................................................... 196


D. TESTING AND QUALITY ASSURANCE REQUIREMENTS .......... 198
      D.1      TESTING AND QUALITY ASSURANCE PROJECT TEAM ........................ 198

      D.2      ACCEPTANCE OF SOFTWARE REQUIREMENTS SPECIFICATION ...... 198
      D.3      ACCEPTANCE OF SOFTWARE DESIGN DESCRIPTION ....................... 201
      D.4      ACCEPTANCE OF PILOT SITE IMPLEMENTATION ............................ 201
      D.5      OVERALL ACCEPTENCE OF COMPLETE AND
               INTEGRATED SYSTEM .............................................................. 202

E. IMPLEMENTATION SCHEDULE ....................................................... 203
      E.1      IMPLEMENTATION SCHEDULE TABLE.............................................. 204
      E.2      SYSTEM INVENTORY TABLE (RECURRENT COST ITEMS) –
               SERVICES.......................................................................................... 206
Section VI. Technical Requirements                                                                                       153




    E.3      SITE(S) TABLE 1 ............................................................................... 207
    E.4      SITE(S) TABLE 2 ................................................................................ 208
    E.5      PURCHASER WORKING HOURS TABLE ............................................ 216
    E.6      TABLE OF HOLIDAYS AND OTHER NON-WORKING DAYS .............. 217

F. REQUIRED FORMAT OF TECHNICAL BIDS .................................. 218
    F.1      INFORMING THE BIDDER ................................................................. 218
    F.2      DESCRIPTION OF THE INFORMATION TECHNOLOGIES,
             MATERIALS, OTHER GOODS, AND SERVICES .................................. 218
    F.3      ITEM-BY-ITEM COMMENTARY ON THE TECHNICAL
             REQUIREMENTS ................................................................................ 218
    F.4      PRELIMINARY PROJECT PLAN ......................................................... 219
    F.5      PLATFORM REQUIREMENTS PLAN ................................................... 220
    F.6      COMPUTING HARDWARE SPECIFICATIONS ..................................... 220
    F.7      SOFTWARE SPECIFICATIONS ............................................................ 221
             F.7.1 SYSTEM SOFTWARE AND SYSTEM-MANAGEMENT UTILITIES
                   (SS&SMU)............................................................................................... 221
             F.7.2 COMMUNICATIONS SOFTWARE.................................................................. 221
             F.7.3 GENERAL-PURPOSE SOFTWARE ................................................................ 221
             F.7.4 DATABASE SOFTWARE AND SOFTWARE DEVELOPMENT TOOLS ................ 221
    F.8      SERVICE SPECIFICATIONS ................................................................ 221
             F.8.1     TECHNICAL SUPPORT ................................................................................ 221
             F.8.2     WARRANTY SERVICE ................................................................................ 222
             F.8.3     USER SUPPORT/HOT-LINE.......................................................................... 222
             F.8.4     TECHNICAL ASSISTANCE ........................................................................... 222
    F.9      CHANGE ORDER PROCEDURES ........................................................ 223
    F.10 OTHER NON-IT GOODS .................................................................... 223

G. TECHNICAL RESPONSIVENESS CHECKLIST ............................... 224
    G.1      THE TECHNICAL RESPONSIVENESS CHECKLIST ............................. 224
    G.2      FUNCTIONAL PERFORMANCE REQUIREMENTS OF THE SYSTEM ...... 225
             G.2.1 GENERAL FUNCTIONAL REQUIREMENTS ................................................... 225
             G.2.2 FUNCTIONAL MODULES ............................................................................ 225
    G.3      TECHNICAL REQUIREMENTS OF THE SYSTEM ............................... 225
             G.3.1 GENERAL TECHNICAL REQUIREMENTS ..................................................... 225
154                                                                                              Section VI. Technical Requirements




             G.3.2 GENERAL TECHNICAL REQUIREMENTS FOR WEB PUBLISHING ..................226
             G.3.3 COMPUTING HARDWARE SPECIFICATIONS .................................................226
             G.3.4 REQUESTS OF THE RDBMS .......................................................................226


H. ATTACHMENTS...................................................................................... 228
      H.1    ATTACHMENT 1: THE CUSTOMS LAW ............................................. 229
      H.2    ATTACHMENT 2: THE CUSTOMS TARIFF LAW ................................ 315
      H.3    ATTACHMENT 3: COMMENTS ON THE CUSTOMS TARIFF ............... 317
      H.4    ATTACHMENT 4: THE CUSTOMS ADMINISTRATION LAW ............... 319
      H.5    ATTACHMENT 5: PROCEDURES FOR PASSING AND DATA SOURCES
             FOR THE CUSTOMS TARIFF ................................................................ 359
             H.5.1 PROCEDURE FOR PASSING THE CT............................................................. 360
             H.5.2 DATA SOURCES .........................................................................................360
                      H.5.2.1     Basic data sources .......................................................................................... 360
                      H.5.2.2     Data sources which govern use of the Customs Tariff Law............................ 361
                      H.5.2.3     Data Sources which Govern Classification of Goods ..................................... 362
                      H.5.2.4     Special Data Sources ...................................................................................... 362
                      H.5.2.5     CT Attributes .................................................................................................. 362
             H.5.3 SUBJECTS OF THE CT .................................................................................363
      H.6    ATTACHMENT 6: ORGANIZATION OF THE CUSTOMS
             DIRECTORATE OF THE REPUBLIC OF CROATIA ............................... 365
             H.6.1 ORGANIZATIONAL STRUCTURE OF THE CDRC ..........................................366
      H.7    ATTACHMENT 7: FORMS AND BINDING OPINIONS CONCERNING
             CLASSIFICATION OF GOODS WITHIN THE CUSTOMS TARIFF ............ 368
Section VI. Technical Requirements                                                        155




                             A. BACKGROUND

A.1 THE PURCHASER

A.1.1 AGENCY’S LEGAL BASIS, ORGANIZATIONAL ROLE, CORE OBJECTIVES
        The Customs Directorate of the Republic of Croatia (CDRC) is a legal enforcement
        entity operating within the framework of the Ministry of Finance. Its mandate is
        defined by law, and includes the enforcement of the legal provisions concerning the
        movement of goods and people in and out of the country, with regards to duty and tax
        payments, tariffs, quotas, preferential rates, currency control, etc.
        The Headquarters are located in Zagreb, and it administers the 10 Regional Customs
        Houses which are located across the entire territory of the country. Likewise, each
        Customs House manages the 158 individual Customs Offices, located within their
        jurisdiction (See Figure 1. Site Locations of CDRC).
        The regulation of the Customs System in the Republic of Croatia is achieved through
        the implementation of the following legislative acts: The Customs Law (see section
        H.1 Attachment 1: The Customs Law), The Customs Tariff Law (see sections
        H.2 Attachment 2: The Customs Tariff Law and H.3 Attachment 3: Comments on The
        Customs Tariff) and The Customs Administration Law (see section H.4 Attachment 4:
        The Customs Administration Law).
        The Customs Directorate’s main functions and tasks are:
                 To protect society by enforcing constraints and prohibition on imports,
                  exports and transit;
                 Continuously to provide support to economic development by maintaining an
                  optimal balance between trade and an efficient application of domestic
                  regulations;
                 To collect customs duties and other revenues under the law;
                 To combat all types of customs fraud (smuggling, etc.);
                 To collect and analyze statistics on international trade;
                 To propose to the Government initiatives and measures within its remit;
                 To carry out its tasks in a rational and effective manner.
156                                                             Section VI. Technical Requirements




A.2 BUSINESS OBJECTIVES OF THE PURCHASER

A.2.1 OVERVIEW OF THE CURRENT BUSINESS OBJECTIVES, PROCEDURES, AND
      PROCESSES
      Existing applications for certain functionalities concerning the Customs Tariff (CT)
      are not-unified or non-existent. For instance, when passing a new Customs Tariff,
      analyses and simulations are not performed.
      The CT is available to Customs employees through the Information System (IS), along
      with all legally binding information (permits, quotas, etc), but because of the
      inconvenient technique of presentation, employees mostly utilize it in written form.
      There is no centralized application for laboratory findings, but each of the three
      Customs’ Labs creates separate lists of findings regarding classification of goods,
      which are available only in written form, just like the opinions of the Customs Tariff
      Commission.
      Presentation of the CT and related data currently on the WEB in the CDRC
      (http://www.carina.hr) is provided through static HTML, where the user must search
      the entire contents to reach the searched data.
      For more information about procedures and processes see section A.5 Current status.
      The Customs Tariff Application (the ACT) shall, through the proposed development of
      the Supplier provide a unification of functionalities related to the Customs Tariff,
      within an integrated application.

A.2.2 OVERVIEW OF THE CHANGES IN OBJECTIVES, PROCEDURES, AND
      PROCESSES AND EXPECTED BENEFITS OF THE SYSTEM
      When passing, i.e. creating documents the ACT shall provide users an easy and
      standard way of data entry and updating, as well as enable accessibility and a clear
      layout of the entire document archive relating to the CT.
      The electronic form of the CT and all related data shall be accessible to all CDRC
      employees. Using the ACT shall simplify all tariffing activity for CDRC employees
      (checking of goods and matching with tariff labels), thereby enabling easier flow of
      goods and services in import and export.
      The ACT implementation shall enable direct access (selection) to data concerning the
      specific user.
      Publishing, preparation for printing and preparation for printing locally shall be
      resolved within the application, so that additional activity of ACT users regarding the
      aforementioned shall not be required.
      The presentation of the CT on the Web shall be by dynamic HTML, which shall enable
      participants in the customs proceedings, as well as other users, easier and more precise
      search of the CT and other related data.
      In the organizational aspect, the ACT shall group users of the CT within the CDRC
      into characteristic groups of users, depending on the type of job performed. In this way
      all CT users within the CDRC shall be enabled to use the ACT improving job
      performance related to the CT.
Section VI. Technical Requirements                                                                157




A.3 ACRONYMS USED IN THESE TECHNICAL
    REQUIREMENTS
                Term                                       Explanation

         ACT                  Customs Tariff Application
         CL                   Central location
         CT                   Customs Tariff
         CZ                   Customs Law
         D                    Delete
         DB                   Data Base
         DBA                  Data Base Administrator
         EU                   European Union
                              Gradski zavod za automatsku obradu podataka - Municipal Institute
         GZAOP
                              for Automatic Data Processing
         HS                   Harmonized system
         HQ                   Headquarter
         HT                   Croatian Telecom
         HW                   Hardware
         IS                   IT system
         KN                   Combined nomenclature
         MFN                  Moust Favored Nation
         MU                   Management utility
         NN                   Narodne novine- National Gazette of the Republic of Croatia
         QoS                  Quality of Service
         R                    Read
         RDBMS                Relational Database Management System
         RH                   Republika Hrvatska- Republic of Croatia
         SAD                  Single Administration Document
         SQL                  Structured Query Language
         SW                   Software
         W                    Write
         WCO                  World Custom Organization
         WTO                  World Trade Organization
         ZCS                  The Customs Administration Law
         ZCT                  The Customs Tariff Law
158                                                              Section VI. Technical Requirements




A.4 CORE OBJECTIVES AND BUSINESS FRAMEWORK
      The customs procedure is a special type of administrative procedure, which can be
      divided into the following basic elements: subjects of the procedure, objects of the
      procedure and their relationships. The Customs Law (CZ) is a legal document of the
      Single Administration Document (SAD), describing implementation of the customs
      procedure. The object of the customs procedure are the goods. A Customs Tariff (CT)
      is applied for the purpose of unique identification and classification of goods.
      The ZCT and the CZ are the basis for implementation of customs laws, i.e. for control
      of application of the customs laws. The Customs Tariff is an integral part of the
      Customs Tariff Law, and consists of a classification of goods (a system of
      nomenclature, numerical labeling , rules of classification of goods and calculation of
      customs duties). In the Republic of Croatia the Customs Tariff used is based on the
      International Convention on Harmonized systems and numerical marking of goods
      (HS) from 1983; currently in use is the third issue from January 1st 2002. Since
      January 1st 2002, the Republic of Croatia also utilizes, at lower levels of classification,
      the Combined Nomenclature (KN) of the EU.
      Furthermore, the CT of the Republic of Croatia (RH) is in accordance with
      recommendations of the World Customs Organization (WCO) and other international
      treaties signed by RH. The HS is in use as of January 1st 1988, based on the Brussels
      nomenclature and the Standard International Trade Classification.
      The document form of the CT is described in the ZCT in the graphical sense, and
      consists of General rules for usage of nomenclature and numerical labeling of goods,
      21 sections with notes and 97 chapters with notes (the 77. chapter is reserved for future
      use) and tables consisting of rows and columns. Some columns contain numerical
      (tariff) codes, names, unit measures, and customs rates according to Most Favored
      Nation (MFN) status, as well as customs rates according to free trade agreements
      (currently 12 columns). There is a unique link between classification level and number
      of lines within the label and the numerical label (tariff code), measuring unit and
      customs rate (see section H.2 Attachment 2: The Customs Tariff Law). Linked to the
      individual numerical (tariff) labels in the CT is data concerning quotas for preferential
      customs rates, according to free trade agreements, displayed as additional tables within
      the CT (currently 14 such tables).
      The classification is based on a hierarchical model, so that goods within one chapter
      are sorted into 4-digit tariff codes, which are further subdivided into tariff subcodes.
      The international convention on HS standardizes the numerical tariff code to 6 digits,
      and a maximum of two levels of subdivision within a tariff code (up to two lines
      preceding name). Since in the RH the KN is in use as of January 1st 2002, the further
      subdivision of tariff codes of the HS is also in use. The HS code is expanded with a
      seventh and eighth digit, allowing for eight levels of subdivision within an HS tariff
      code (up to eight lines before a name).
      Tariff subcodes at the lowest classification level have an eight digit code, and an
      additional measuring unit, a customs rate according to Most Favored Nation status,
      and a customs rate according to each free trade agreement. The RH has also
      maintained tariff codes on the “national level”, which are marked with a ninth and
      tenth digit that represent exclusion from the corresponding KN tariff subcode (for
      example because of different customs rates, tax regulations, limited or special
Section VI. Technical Requirements                                                             159




        regimens of import/export etc.). Such “national” tariff subcodes also have a
        corresponding measuring unit, customs rate according to MFN and a customs rate for
        each free trade agreement.
        The Customs rate depending on type of goods is applied in two ways:
             by value (ad valorem);
             by quantity.
        The sum of the customs rate by value and quantity is often limited by a maximum total
        amount, specified as a percentage of the customs value of the goods.
        The customs rate by value is expressed in percentage, while the customs rate by
        quantity is expressed in absolute value per measuring unit. Goods with customs rates
        by quantity are mostly seasonal so they also have dates from when and until when they
        apply.
        Furthermore, preferential customs rates based on free trade agreements are only linked
        to certain quantities of goods (customs quotas), whereas outside of these quotas the
        MFN principle applies, or a percentage of it.



A.5 CURRENT STATUS
        Since so far there was no integrated application for passing, updating and using the
        CT, each of these tasks have different procedures.
        Passing the new CT was implemented using MS Word software. Unifying the draft
        and forming a final version was performed within the CDRC. Following this the
        document of the new CT was published in the Official Gazette (NN) and in .doc
        format on the CDRC WEB pages. (http://www.carina.hr).
        For updating and use within the CDRC IS, the text was extracted in .txt format, the
        tables were converted to .xls format, and this was presented to GZAOP (see section
        C.2.2.1 Municipal Institute for Automatic Data Processing - GZAOP), which included
        them in the basic business application for the CDRC. MS Access and MS Excel were
        used for this operation.
        The CDRC IS business application is used for implementing customs regulations by
        entering and processing the SAD. It is located on the host in GZAOP, and available to
        CDRC employees through terminal access.
        The CDRC business application contains the Customs tariff subsystem. This enables
        updating, monitoring changes and overview of CT data. Updating is performed in two
        ways: incorporating data as described above, which requires programmer intervention,
        or manual input through the terminal. Updating data by terminal input is enabled only
        to certain authorized CDRC employees. The subsystem also includes some of the data
        which regulate ZCT usage (like permits, available in CDRC in written form, and input
        manually into the application). The subsystem enables overview of data in such a
        manner that searches are performed only by customs/tariff codes.
        The CDRC business application for processing the SAD deals only with the tariff
        code. Reports for users located outside of the CDRC contain only the code label,
        without the accompanying text. The CT nomenclature assigned to the tariff code often
160                                                             Section VI. Technical Requirements




      is simply:”other”, which is wrong and unusable (there should be abbreviated names of
      tariff items).
      For more information relating to the procedure for passing a new CT, and related data,
      the Bidders are referred to section H.5 Attachment 5: Procedures for passing and data
      sources for the customs tariff.
      Such a manner of passing, using, updating and publishing data related to the CT is
      inefficient and not satisfactory, so the need arose for developing a software solution for
      the Customs Tariff Application (ACT).



A.6 SCOPE OF WORK OF SUPPLIER

A.6.1 SUPPLIER’S DUTIES
              Software development of the program product ACT (a one-time job);
              Installing and implementation of the the ACT (a one-time job);
              Perform the system-integration;
              Upgrade and update service of system SW, application SW and the database
               SW;
              Preparation of the initial status (a one-time job);
              Training of Customs employees for use of the Information System, with
               possible refreshing (a one-time job);
              Maintenance of the ACT (in warranty period);
              Implementation activity that should precede operational acceptance (including
               System integration);
              To deliver technical specifications for the overall platform;
              The Supplier is responsible to specify any additional hardware, related
               technologies, and standard softwarebut not to supply them.

A.6.2 WHAT IS NOT THE SUPPLIER’S DUTY
              Collection and conversion of data in electronic form for filling the database;
              Improvements and interventions in the existing business application of the
               CDRC IS (done, maintained and developed in GZAOP) and installation and
               configuration of network equipment;
              Supply and distribution of HW and system SW and database SW;
              Education of users outside of the CDRC (except within the Ministry of
               Industry and Ministry of Agriculture and Forestry, which participate in
               passing the CT and use the ACT);
              Timely provision of network and hardware infrastructure for implementation
               of ACT in CDRC.

A.6.3 PURCHASER’S DUTIES
              Providing full support during the implementation of the ACT, including:
Section VI. Technical Requirements                                                        161




                   o Know-how in customs affairs and customs tariff;
                   o Assisting the Supplier to perform the process analysis.
                 Providing all data sources in the format requested by the Supplier;
                 Timely provision of access permits to CDRC premises, as required by the
                  ACT implementation;
                 Timely provision of required network and hardware infrastructure for
                  implementation of the ACT;
                 Providing a commission of elected Customs officers, covering functional and
                  non-functional (i.e. IT) requirements.
162                                                                Section VI. Technical Requirements




      B. FUNCTIONAL PERFORMANCE
      REQUIREMENTS OF THE SYSTEM

B.1 GENERAL FUNCTIONAL REQUIREMENTS OF THE
    ACT
        The Customs Tariff Application (ACT) is to be used for passing, updating and using,
        as well as publishing data relating to the Customs Tariff and accompanying
        documents, i.e. document sources for the CT and ACT (for more information see
        section H.5.2 Data Sources). In the realization of this mission the ACT MUST
        generally satisfy the following functional requirements.

B.1.1   MULTILINGUAL
        The ACT MUST support multilingual implementation of the CT and all
        accompanying documents (document sources). The ACT MUST be implemented in
        Croatian and English (for publication on the Internet).
        The ACT functionality for CT Internet publication MUST be implemented in such a
        way that selecting the desired language enables a user interface in the selected
        language (Croatian or English), including forms for searching, menus, warnings and
        help facilities.
        The Supplier MUST design the application in such a way that enables the IT staff of
        the CDRC to add additional documents in the database, and the offered development
        of the ACT shall enable the Purchaser simple implementation in other languages (like
        German, French, etc.)

B.1.2 GRAPHICAL USER INTERFACE
        The Graphical User Interface (GUI) of the ACT MUST be intuitive, easy to use and
        support innovative and modern user interface techniques.
        The forms for entry, updating and searching should be intuitively understandable to the
        user, easily recognizable, and implemented in a graphical and multicolored form.
        Display of a large quantity of data should be intuitive and surveyable (like
        simultaneous display of several tariff codes), keeping the hierarchical structure
        intuitive (for example displayed as a root hierarchy). Tariff codes, tariff items and
        related data should be displayed while maintaining a balance between quantity of
        displayed data on the screen and legibility.
        The ACT MUST enable simultaneous display on the screen of two subsequent
        versions of the CT. Versions in Croatian/English should be selectable freely (or other
        languages the CT may be translated into).
Section VI. Technical Requirements                                                                163




        The ACT MUST display correlations between changes in classification of goods in the
        CT, the two next CT versions, graphically and textually (in table format). Correlations
        between old data and replacing data should be shown (in the case of deletion of tariff
        items in one CT version, new tariff items should be shown where the corresponding
        goods are classified in the other CT).

B.1.3 SEARCHING, SELECTING AND FILTERING
        The ACT MUST enable searching and selecting of data on the CT by all CT elements
        and related data (attributes) on the level of the entire document, or just a part of it (like
        a part of the text). When displaying data for a tariff item all higher classification levels
        should be displayed, and an overview of the lower classification levels should be
        offered. When the searched data is found, all related data should also be displayed (or
        be available in a simple manner), or if not appropriate for onscreen display, an offered
        link should enable access to the document providing more information.
        As there is a unique connection between the CT, additional data sources for the CT
        and all other related documentation, The ACT should enable the user to search for data
        based on any initial basis (selection criteria), as well as access to all other related data
        i.e. cross-reference to other information within the ACT. For example, if the search is
        based on the commercial name of the goods there MUST be a visible link to all data
        related to the CT: the tariff code/tariff item, abbreviation of the tariff item, CT
        comment on the tariff code, as well as all other related data MUST be available
        (analysis of Customs Labs, opinions of the Customs Tariff Commission, etc.), whereby
        selection enables easy and intuitive review and access to a whole plethora of
        information related to the initial selection criteria.
        The ACT MUST be able to filter a group of data related to CT by some desired
        criteria.
        Searching, selecting and filtering of data related to each CT element should be fast and
        intuitive.
        It is also necessary that sorting, searching and filtering understands Croatian diacritic
        symbols (ć, č, dţ, Ď, š, ţ) and their sequence in the Croatian alphabet.

B.1.4 SEARCH/REPLACE CAPABILITY
        For subjects in the passing and updating of the CT, the ACT MUST support modern
        techniques of Search/Replace in the CT and accompanying data sources, only in one
        part (i.e. chapter/head/item of the Customs Tariff and Comments on the Customs
        Tariff) or in the entirety.
        Modern search techniques shall be performed by authorized persons in the CDRC,
        with appropriate user permits (see section B.1.8 Access to the ACT and data)

B.1.5 CT ATTRIBUTES
        Since the number of CT attributes (see section H.5.2.5 CT Attributes) is not final, the
        ACT cannot be limited to the current number and type of attributes, enabling for future
        addition of new attributes (as needed).
164                                                              Section VI. Technical Requirements




      Along with each attribute there MUST be information on the source of data (like for
      example the legal basis), with the contents in required form.
      The attributes of the CT MUST be kept inside a unique database, including
      information on the time of creation, beginning and end of usage.
      There are no other specific knowledges or relevant informations at this time, but the
      Supplier is expected to propose solutions to be discussed, and accepted upon
      agreement.

B.1.6 SAVING AND EXPORT OF DATA
      For subjects who are participants in the passing and update of the CT, the ACT MUST
      provide storage (archiving) of all (previous old) versions of the CT (and drafts during
      the passing phase) and accompanying documents (data sources connected to the CT).
      All data are kept in a database and MUST be available in a format which enables
      publication, with possibility of exporting to other formats (.doc, .xls, HTML, XML,
      .jpg, .bmp) i.e. in the format agreed to with the Supplier.

B.1.7 DATA PRINTING
      THE ACT MUST enable printing of CT data and all accompanying documents on a
      local printer, in original (formatted) form, in black-and-white or color. Printing of one
      part (like a chapter/head/item of the CT and Comments on the CT) or the entirety
      MUST be enabled.

B.1.8 ACCESS TO THE ACT AND DATA
      Access to the ACT should be protected by user login. Functional possibilities are
      arranged according to users’ access rights. Groups of users of the ACT are listed in
      section B.3 USER groups of THE ACT.



B.2 USER VIEWS OF THE ACT
      Depending upon the different groupes of users (see section B.3) the ACT can be
      divided in several modules (functional requirements set before the ACT) according to
      “views” that the different users will need:
              Passing the CT;
              Updating the CT;
              Using the CT:
               o Searching and selecting the CT;
              Publication of the CT on the Internet.


B.3 USER GROUPS OF THE ACT
      Users participating in passing the CT MUST be separated from all other users of the
      CT, and MUST be enabled to work on a separate server located in the central CDRC
Section VI. Technical Requirements                                                                    165




           location, which is connected by network to dislocated servers located in the Ministry
           of Industry and Ministry of Agriculture and Forestry. Data exchange between these
           servers is performed by data replication. These users MUST have read, write and
           delete rights on the data, with the possibility to have access to all earlier valid tariffs,
           and the possibility of CT update revisions.
           Users that shall use and read the CT should have read rights.
           Users that shall update the tariff MUST have the right to read and write data (adding to
           the database) because they update the CT already in use.
           Other external users (all other participants in the customs procedure and all other
           interested parties) shall have access to the CT over the Internet, i.e. to the published
           version of the CT on the CDRC WEB.
           The following table shows an overview of the ACT users, according to function and
           needs for the CT:

                                Subjects                        Passing        Using       Updating

       Customs Directorate RH:                                   RWD             R           RW
            o employees of the Service for Customs Value,
                                                                                             RW
              Customs Tariff, Analysis and Lab
            o employees of the Service for CT and Lab                                        RW
            o employees members of professional bodies,
                                                                                             RW
              related to the CT
            o employees in the professional services and
              departments of the Central Office and Customs                                  RW
              Houses
            o employees in Customs offices                                       R
       Ministry of Industry                                      RWD             R
       Ministry of Agriculture and Forestry                      RWD             R
       GZAOP                                                                  COPY

           where:
                     Passing – includes the procedure for collecting drafts, running analyses and
                      simulations, preparation for publishing the CT in NN and possible changes to
                      the CT;
                     Using – includes use of the CT and related data sources, proceedings of the
                      customs procedure while inspecting and classifying goods, by use of data over
                      the CDRC communication network;
                     Updating – includes entry/changes to accompanying data sources to the CT,
                      bringing opinions and lab findings, creating lists of goods, elements of risk
                      analysis and all other CT attributes;
                     Publication on the Internet – means availability, and usage of published CT
                      data over the Internet.



    For more details see section B.3.1.2.
166                                                             Section VI. Technical Requirements




B.3.1 PASSING THE CUSTOMS TARIFF
      Interested Ministries (see section H.5) propose parts of the Tariff, which are
      consolidated, validated and verified (in a separate database on a separate server). The
      CDRC after verification, proposes such data for passing.
      The ACT should support passing the CT according to the procedure, described in
      section H.5.1, but not limited to it. The interested Ministries shall have development
      servers installed as well as workstations for the employees working on passing the CT.
      As previously mentioned, the CT and accompanying data sources are written into a
      database, and a necessary requirement that the ACT MUST satisfy is providing the
      possibility for editing and browsing, in the form originally entered into the database.
      Requirements on the ACT regarding the functionality of passing the CT are:
              Number of digits of a tariff item expandable indefinitely;
              Insight into sequential chronology of all changes made by user who created
               them;
              Accessibility of the current and all previous CTs with all user functionality
               (updating, using and publication) of the CT (see sections B.3.2 and B.3.3);
              Simultaneous on-screen display of two versions of the CT in all available
               linguistic implementations;
              Performing of analyses and simulations (see section B.3.1.1);
              Saving and export of newly passed CT in the format required for
               incorporation in the CDRC business application (see section B.3.1.2);
              Editing for publication in NN;
              Automatic publication on the CDRC WEB site;
              Automatic replication of new data on the CDRC application server.

                                B.3.1.1 Analysis and simulations
      The CDRC shall ensure that data from the SAD on export/import of goods exists for a
      certain time period, to be agreed with the Supplier of the ACT, for the need of analysis
      and simulation during the passing of a new CT. The largest subsection of data from the
      SAD relevant for analysis and simulation shall be determined. This subsection shall be
      placed on the CDRC development server’s database, and refreshed at agreed periods
      from the CDRC IS.
      The format shall be agreed with the chosen Supplier of the ACT. This database MUST
      be accessible directly (through ISDN) by connection to the CDRC development server,
      but also locally off-line at the site of the Ministry of Agriculture and Forestry and
      Ministry of Industry.
      To present a better idea of the expected analyses and simulations, two examples are
      presented:
              Analyses and simulations of the change of income for the state budget if a
               customs rate is changed (on different classification levels) for calculating
               average, nominal and pondered obligations (existing and simulated). For
               example: If a certain quantity of imported goods according to a tariff item
               with a given customs rate, how much would the revenue intake change
Section VI. Technical Requirements                                                             167




                 (increase/decrease) if the customs rate changes (increases/decreases) for a
                 certain amount?
              Analysis and simulation of calculating the effective customs rate based on
                 input-output analysis.
        The analysis and simulation know-how shall be supplied by the CDRC to the Supplier,
        and the implementation and technical solution shall be developed in accordance with
        the Purchaser during the process of software development and piloting.

                                     B.3.1.2 Exporting data for GZAOP
        For incorporation in the CDRC business application, the selected Supplier of the ACT
        shall agree on the data export format with the Purchaser.

B.3.2 USING THE CUSTOMS TARIFF
        The ACT is primarily used in the CDRC. Given the specific user requests for the CT
        there are two basic user groups of the ACT within the CDRC:
                Users that will update (enter changes and amendments to the accompanying
                 data sources of the CT, edit them, update elements of risk analysis and other
                 CT related data);
              Users that will browse the CT through theACT for easier classification of
                 goods within the CT, and easier application of the Customs Procedure Law.
                 These users do not have the possibility to enter data, but only read data related
                 to the CT.
        The ACT MUST enable defining user rights for each group, regarding access and use
        of the application.

              B.3.2.1 Findings and Opinions on classification of goods within the CT
        The ACT MUST enable entry of new findings and opinions on classification of goods
        in the CT (according to analysis of customs labs and opinions of the CDRC Service for
        Customs Tariff) as well as incorporation of international and foreign sources of data
        (documents) on classification of goods (issued by the WCO and EU).
        Basically all these documents contain a common group of data. The selected Supplier
        shall find the largest common group of data (and verify it with the Purchaser) and
        based on this build a basic form, to be completed based on type of document (finding,
        opinion) being brought.
        Generally these documents have a period of validity (compulsory usage in the
        procedure for classification of goods), after which they are used only as archive data. If
        the period of validity of the finding, or opinion, has not expired and the CT
        nomenclature changes, the change should also be incorporated in the document of the
        finding, i.e. opinion.
        Specifically, some binding opinions on the classification of goods by the CDRC
        Service for Customs Tariff are a state secret, and as such should be accessible only to
        some users of the ACT. The ACT MUST enable selective accessibility to this data.
        The Purchaser shall develop the security mechanisms for this data in cooperation with
168                                                              Section VI. Technical Requirements




      the selected Supplier, and the list of authorized personnel shall be presented to the
      Supplier.
      The form “Binding Opinion on the Classification of Goods within the Customs Tariff”
      (see section H.7 Attachment 7: Forms and binding opinions concerning classification
      of goods within the customs tariff) is regulated by the Instruction on implementing the
      Customs Law. Forms for other findings and opinions are not defined, so the Purchaser
      and Supplier shall agree on the final form during software development and piloting of
      the ACT.

                                B.3.2.2 Elements of Risk Analysis
      Elements of risk analysis MUST be linked as attributes to the CT. In the use of the CT
      their function (by reading them) is to help Customs employees with inspection of
      goods. Following are some examples of elements of risk analysis:
            Risk of erroneous classification of goods;
            Risk of high customs or tax burden;
            Risk of country of origin of the goods;
            Risk of importing country of the goods;
            Risk of large value variations of the goods.
      The ACT will follow and update elements of risk analysis and MUST enable creation
      of relationships in the database between "risky" tariff items, and their attributes.
      Because of the secrecy of such data, it shall be available only to authorized Customs
      employees.
      The Supplier should suggest the algorithm of risk analysis.
      The ACT should enable a qualified DB administrator to assign new relations between
      data without jeopardizing the integrity of existing data.

                                       B.3.2.3 List of Goods
      In order to enable easy searching, the ACT needs three lists (registers):
           List (alphabetical) of goods;
           List of standard commercial names of goods;
           Abbreviated names of CT tariff items.
      These lists are formed in such a way that items are uniquely linked to a tariff code,
      with reference to all other interdependent data in the ACT.
      The ACT MUST enable searching by keywords, or multiple words.

                                  B.3.2.4 The Tariff Calculator
      The Tariff calculator performs fast calculation of duties in the customs procedure for
      specific goods, based on value and quantity. It is to be used primarily by Customs
      officers for calculation of all duties (customs, special taxes and VAT).
      This function should be available to all interested users outside of the CDRC, through
      the CT published on the Internet through an option which would be offered as part of
Section VI. Technical Requirements                                                               169




        the web page. Activating the opition would display the tariff calculator on the
        computer screen, and the result should be printable on the local printer of the tariff
        calculator user.
        The calculation is as follows: selecting determines the tariff item for the desired goods,
        the quantity and value of goods is input, as well as country of origin. The result MUST
        be the calculation of all costs for the given parameters.
        The algorithm of the tariff calculator shall be proposed by the Supplier (and accorded
        with CDRC experts) and data concerning the tariff shall be available in the ACT
        database.
        For this functionality of the ACT there are no requirements concerning user access
        rights, or archiving of data.

B.3.3 UPDATING THE CUSTOMS TARIFF
        The ACT MUST support this special form of using the CT by specially authorized
        CDRC employees (for more details see section B.3). They will be enabled to
        add/delete/change data in the CT and other related data sources.

B.3.4 PUBLISHING ON THE INTERNET
        The CT MUST be published on the Internet in order to be available to all interested
        users in the country and abroad, and the Internet version of the CT must therefore
        satisfy a minimal set of functional requirements:
                 Support for an unspecified number of languages (minimally Croatian and
                  English);
                 Automatic generation of contents from the ACT database (without operator
                  intervention);
                 Visually identical to the CT published in NN;
                 Search functionality according to section B.1.3.
170                                                          Section VI. Technical Requirements




      C. TECHNICAL SPECIFICATIONS

C.1 GENERAL TECHNICAL REQUIREMENTS

C.1.1 GENERAL TECHNICAL REQUIREMENTS OF THE ACT
             Distributed business application;
             Three tiered architecture;
             Minimum 32 bit application;
             Uses a relational database (RDBMS);
             Compatible with Windows 2000 Professional operating system or newer
              (both client and server side);
             Optimized for low-bandwidth network;
             Optimized for users in the CDRC network, with a fixed or dial-up connection;
             Standalone version (for CDRC mobile users);
             Optimized for 800x600 resolution with minimally 16 bit color;
             Access to the application protected by password system;
             Intuitive "user-friendly" Windows oriented GUI;
             Written in Croatian (with possibility to incorporate other languages);
             On-line, context sensitive and tool tip help in Croatian;
             Possibility of printing to different printers (laser, ink-jet, etc.);
             Possibility of import (export) of data in standard format for processing in
              standard office applications.

C.1.2 GENERAL TECHNICAL REQUIREMENTS FOR WEB PUBLISHING
             Automatic generation of contents from the database, without DB
              administrator intervention;
             Optimized for minimally fourth generation Web Browsers (MS Internet
              Explorer 4.x and Netscape Communicator 4.x);
             User friendly graphical design;
             Optimized for 800x600 resolution in minimally 16 bit color;
             Support for unspecified number of languages;
             Possibility for searching tariff data and related data.

C.1.3 LANGUAGE SUPPORT
      All information technologies MUST provide support for Croatian. Specifically, all
      display technologies and software MUST support sorting of data in Croatian, and
      satisfy standards for technical requirements.
Section VI. Technical Requirements                                                           171




        The code page used in the Republic of Croatia is CP-1250 used in Windows
        applications, and for the Internet the ISO 8859-2 standard character set is used.

C.1.4 DATES
        All information technologies MUST properly display, calculate, and transmit date
        data, including, but not restricted to 21st Century dates.
        In the ACT the date MUST be in the format ”dd:mm:yyyy”.



C.2 NETWORK AND COMMUNICATIONS
    SPECIFICATIONS
        The ACT MUST be developed in such a way that the existing CDRC communication
        network, with its topology and transmission speed completely satisfies all needs for
        normal and unobstructed functioning.
        The CDRC communication network is based on modern multiservice devices which
        support a wide specter of transmission technologies and integration of multimedia
        services. The network is based on the IP protocol, which results in simplified control
        functions, lesser network cluttering and faster introduction of QoS, enabling a robust,
        developed and high bandwidth network.

C.2.1 LOGICAL AND PHYSICAL ORGANIZATION OF THE CDRC
        COMMUNICATIONS NETWORK
        The ACT shall be installed at the central location of the Customs Directorate and is
        independent on any other application, except that data from it shall be exported to
        GZAOP, in the format agreed with the Supplier (see section B.3.1.2 Exporting data for
        GZAOP).
        The logical organization of the CDRC communication network follows the CDRC
        business organization, on several levels. Diverse network resource needs at different
        locations prompted a system of categorization of all IT locations in several groups, as
        follows:
              GZAOP – site of the central application;
              CL – Central location of the CDRC communication network;
              Type1 – Customs houses;
              Type2 – larger Customs offices/departments;
              Type3 – medium Customs offices/departments;
              Type4 – smaller Customs offices/departments.
        The CDRC communications network central location (CL) is located in the premises
        of the Zagreb Customs house.
172                                                                                                                                                                                                       Section VI. Technical Requirements



                                                                                                                                            Mur.Središće
                                                                                                                                                                   Goričan

                                                                                                                                       Trnovec                               Kotoriba
                                                                                                                          Otok Virje                Čakovec
                                                                                                              Dubrava Kriţovljanska                                Ţeljezničkapostaja
                                                                                                                                             Varaţdin                                   Koprivnica
                                                                                                                 Macelj                                    Ludbreg
                                                                                                           Lupinjak                Ivanec
                                                                                                                                                  Pošta
                                                                                                      Hum na Sutli
                                                                                                                                  Krapina                                  Koprivnica
                                                                                                               Razvor                                                                                                                                      Duboševica
                                                                                                                              Jankomir - Intereuropa         Bjelovar                                                                 Beli Manastir
                                                                                                                                                                                                                             Bar.Petrovo selo                              Batina
                                                                                                                                Jankomir
                                                                                                             Harmica
                                                                                                          Bregana
                                                                                                                                             Glavni kolodvor                       Virovitica                       Donji Miholjac
                                                                                                Bregana naselje                     Pošta           Ţitnjak                                                                                                Luka Drava
                                                                                                                                                                                                                       Ţeljeznički kolodvor Osijek
                                                                                                           Zapadni Kolodvor       Zagreb                                                                                                  Osijek
                                                                                                                                                                                                                                                                                Erdut Ţ.kol.
                                                                                                                                                                                                                                                                                  Erdut
                                                                         Prezid                                    R. kolodvor                                                                                                                                  ZL Osijek
                                                                                           Jurovski brod                              Zračna Luka                                Kutina                                                            Pošta
                                                                                                                                                                                                                                                                             Vukovar
                                                                                                                                         Zagreb            Sisak
                         Plovanija      Kaštel Poţane            Rupa    Ţ. kol. Šapjane    Brod na                                                                                                       Poţega                                               Vinkovci
                                                                                                                                                                                                                                                                                          Ilok
                                                                                             Kupi     Pribanjci
                       Umag                                             Pošta
 Umag (pomorski granični prijelaz)                     Pasjak                                                     Karlovac                                                                                                                                                                     Ilok (Sot)
                                                                 Luka             Ţ. kolodvor
                                        Buje
                                                 Buzet                            Luka Rijka (skladište)              Maljevac
                                                                                                                                                                                                                         Sl.Brod          Svilaj           Ţupanja                   Tovarnik Ţ.kol
                                     Ţelj. kol. Lupoglav (2x)
                                                                                     Luka Rijka (Brajdica)                                                                   Hrv.Dubica
                          Poreč                                 Rijeka               Luka Rijka (Odjel za kontrolu)                                                                        Stara Gradiška                     Sl.Brod -
                                                                                                                                                                                                                                                                                    Tovarnik
                                                       Pazin                                                                                                                                                                                                                         Bajakovo
                                                                                       Bakar                                                                                                                                    Most                           Ţupanja -
                             Rovinj                             Labin   ZL Rijeka                                                                                                                                                                                Most        Ţeljeznički kolodvor Gunja

                     Pula (kolodvorska)
                                                Pula
                                                                                                                                                                                                                                                                        Gunja
                                                            Raša -                             Senj
                                        Luka
                                                            Bršica
                                        ZL Pula
                               ZL Pula (Carinski gat)                                                                    Ličko
                                                            M.Lošinj                              Gospić                Petrovo
                             M.Lošinj (Pomorski granični prijelaz)                                                       Selo




                                                                                                                                                  Strmica
                                                                                                                                   Knin

                                                                                           Zadar

                                                                                                                   Gaţenica



                                                                                                                                     Industrijska zona Raţine
                                                                                                               Šibenik                                                            Kamensko


                                                     Node Type                                                                                                 Zračna Luka Split
                                                                                                                                                Pošta
                                                            1                                                                     Sjeverna Luka Split                Luka Split - gat                Vinjani Gornji
                                                                                                                                                                   Luka Split
                                                            2                                                                                 Split                                Imotski
                                                                                                                                                                                                       Vinjani Donji
                                                            3                                                                                                                                   Vrgorac
                                                            4                                                                                                                                          Mali Prolog

                                                                                                                                                                                              Ploče             Metković
                                                                                                                                                                                                                      Ţ. kolodvor i Luka Metković
                                                                                                                                                                                                                       Klek
                                                                                                                                                                              Korčula
                                                                                                                                                          Blato - Vela Luka                            Zaton Doli



                                                                                                                                                                                                                                                     Gornji Brgat
                                                                                                                                                                                                                        Pošta Dubrovnik
                                                                                                                                                                                                                                                           ZL Dubrovnik
                                                                                                                                                                                                                                                               Karasovići
                                                                                                                                                                                                                              Dubrovnik


                                                                                                  Figure 1. Site Locations of CDRC

C.2.2 LOGICAL CONNECTION SCHEME OF THE CDRC COMMUNICATIONS
                  NETWORK
                  Figure 2. shows the logical connection scheme of the network infrastructure. It also
                  shows the entire equipment, which is installed within the GZAOP and CL locations,
                  except for Type1 - Type4 locations where it shows only the router with their associated
                  permanent connections.
Section VI. Technical Requirements                                                                                                                                                                                                                                                                                                                                    173



                                   GZAOP
                           OSA                                     OSA                                                                                                         Central location
                           OSA                                     OSA
                           OSA                                     OSA                                                                                                                                                                                                                                Internet
                                                                                                                                                                                                                                                                PC

                                    Host 1
                                               Host 2
                                                         Host 3


                                                                                                                          GateKeeper                                                                                                  Switch                                                                                            Router

                                                                                            Already exist on
                                                                                              GZAOP site
                                             TN3270 Server                                                                GateKeeper
                                             Load Balancing
                                                                                                                                                                                                                                                                                                                                    Switch

                                                                                                                                                                                            L3 SLB
                                                                                                                                                                                            Switch
                                                                                                                                                                                                                                                                                                                                        Firewall
                                                                                                                                                                                                                                     Server
                                                                                                                                                            Server                                                                    farm




                                                                                                                                      3
                                                                                                                                        x
                                                                                                                                                             farm




                                                                                                                                           IS
                                                                                                                                             D
                                                                                                                                             N
                                                                                                                                                 PR
                                                                                                                                                  A
                                                                                                                                                                                                                                                                                                                                                        Switch

                 Firewall                                                   Firewall
                                                                                                                                  PBX                                                                                                     4 x IS
                                                                                                                                                                                                Router                                          DN PR
                                                                                                                                                                                                                                                        A

                                                                                   PR   A        FR/ATM
                                                                              ISDN
                                                                                                                                                                                                                                                                                                                                            DMZ
                        Router                                                      FR/ATM

                                                                                                       ATM
             ISDN PRA                                                                                                                                                                                FR/ATM


                                                                                                              FR/ATM         ATM                                     FR/ATM                                   FR/ATM                               ATM          FR/ATM                          ATM                          ATM



     Type I                                     FR/ATM                                                                            FR/ATM                                                                                                 FR/ATM                                   FR/ATM                                                      ATM
                                                                                                                                                                         FR/ATM
     (PRA, PBX,                                                                                                                                                                                     FR/ATM     FR/ATM

       Phones)                                                                                                                                                                            HQ Site



                        FR/ATM        FR/ATM                           FR                           FR/ATM      FR/ATM   FR/ATM                            FR                                                                                  FR/ATM       FR/ATM FR/ATM                  FR                  FR/ATM   FR/ATM FR/ATM                  FR/ATM     FR/ATM




  Type II                                                                                                                                                       FR/ATM

  (BRA, PBX,                                                                                                                                                                                         FR/ATM
                                                                                                                                                                              FR/ATM                                   FR/ATM
    Phones)                                                       FR
                          FR/ATM        FR/ATM                                                                                              FR                                         FR/ATM                                   FR        FR/ATM            FR/ATM       FR/ATM             FR        FR/ATM             FR/ATM                              FR/ATM
                                                                                                                         FR/ATM
                                                                                                                                                      FR                                                                                                          FR/ATM                                   FR/ATM              FR/ATM               FR/ATM        FR/ATM
                                   FR/ATM                                                         FR/ATM
                                                                                        FR/ATM
                                                                                                           FR/ATM




  Type III
     (BRA)




  Type IV
    (BRA)




                                                                                                                            Figure 2. Logical Connection Scheme

                                                 C.2.2.1 Municipal Institute for Automatic Data Processing - GZAOP
                   GZAOP is a company owned by the City of Zagreb. Its basic activities are renting
                   computer resources and offering data processing services to larger business systems.
                   CDRC is one of such larger users of GZAOP services.
                   The central computer (Mainframe) is situated at the location of GZAOP, which runs
                   the central Customs application.

                                                                                                                                             C.2.2.2 Central location (CL)
                   The CL is the central location of the network. Its functioning is of vital importance for
                   the correct functioning of the entire network. The biggest part of the network services
                   and functions is implemented here and some of them, which are the most important,
                   are:
                                                         Aggregate site of the entire network;
                                                         The only existing link to GZAOP;
                                                         Central acceptance site for network backup calls;
                                                         central site for connecting mobile users;
                                                         central site for connecting to Internet;
                                                         Server farm;
                                                         Connecting to the local PBX;
                                                         Network Management;
                                                         Videoconferencing Server.
174                                                              Section VI. Technical Requirements




      Because of the significance of all services mentioned above, the CL location was
      projected and created in High Availability technique, i.e. there are two separated
      devices or links of each. Each of these central routers accepts traffic with 5 Customs
      Houses and traffic from one accessible router coming from the GZAOP location. Each
      of them has also 4 ISDN BRA links and they accept backup calls from locations of
      Customs Houses and other Customs Offices, as well as from the calls of mobile users.
      Connection to the Internet was also realized in the High Availability technique because
      of its importance when communicating with other participants in customs traffic.
      Access links and devices are doubled; the linking speed towards ISP amounts to
      2 x 512 kbps.
      The Central control system is able to monitor all devices of the active network
      equipment and to discover stifled links or their malfunctioning.

                                      C.2.2.3 Type1 locations
      Type1 locations include all Customs Houses of the CDRC – a total of 10 (see section
      E.4 Site(s) Table 2). Between 30 and 80 customs officers and employees work in each
      of these Customs Houses. Approximately half of them have computers at their
      disposal. Type1 locations aggregate lines with Type2 and Type3 locations, which are
      administratively assigned to that Customs House. They also accept ISDN BRA calls
      from Type4 locations and ISDN BRA backup calls from Type2 and Type3 locations,
      that are permanently linked to them. The connecting speeds for Type2 and Type3
      locations are between 128 and 384 kbps. Connecting speed towards the CL location is
      higher and varies between 384 and 786 kbps. In case of network overload, a backup
      call may be engaged automatically if needed, which will help to decrease the load for
      the permanent link. VoIP service is implemented at the Type1 locations by connecting
      analog links from the local telephone company to the router.

                                      C.2.2.4 Type2 locations
      Type2 locations (see section E.4 Site(s) Table 2) comprise bigger Customs Offices and
      Departments, which generate heavier traffic. In order to obtain high availability, each
      router is equipped with one additional ISDN BRI link. When the permanent link with
      the superior location is interrupted, this additional link will be the connection to it. In
      case that all links at the Type1 location are occupied, the local router will make the
      connection to the CL location through an ISDN call. These locations have among
      20 and 40 Customs officers and employees.

                                      C.2.2.5 Type3 locations
      Type3 locations (see section E.4 Site(s) Table 2) administratively are subordinated to
      Type2 locations, i.e. they are also administratively subordinated to Type1 locations,
      but they generate less traffic and usually have a lower number of customs officers and
      employees. Therefore, the VoIP service is not implemented here. Routers on Type3
      locations are connected to the superior Type1 locations with the link speed of 128
      kbps. As a backup, they use ISDN BRI module for the realization of backup calls
      towards Type1 or the CL location.
Section VI. Technical Requirements                                                             175




                                        C.2.2.6 Type4 locations
        Small Customs offices and small Customs Departments, which have no need for the
        permanent link towards superior locations, are sorted into group Type4 (see section
        E.4 Site(s) Table 2). When needed, they can be occasionally connected to Type1 or CL
        location by using the ISDN BRA call. At Type4 locations usually there is a maximum
        of 4 computers.

C.2.3 FUNCTIONAL STRUCTURE OF THE NETWORK

                                      C.2.3.1 Network Topology
        Network topology accompanies the organizational structure of the CDRC, whereby it
        is based on HT networks. At the physical level, optical and copper cables are used,
        combined with ATM, FR and ISDN transfer. Connecting to the ISDN network enables
        the realization of backup calls with high performance in order to obtain higher
        availability of the system.

                                        C.2.3.2 Internet Access
        The access to Internet is realized by central connecting from the CL location. A high
        degree of availability is obtained by using two separate firewalls and two links towards
        the ISP. The DMZ network is ready to accept all servers and services, which are
        necessary for business activities nowadays. Accepting IPSec connections from Internet
        is also enabled. This enables secure connections between participants in the customs
        traffic, as well as working from remote computers.

                                C.2.3.3 The CDRC Business Application
        The business application of the CDRC can be accessed from the terminal within the
        CDRC network by IP protocol (through TN3270 clients) using the TN3270 server.
        From this point, SNA traffic goes further through ESCON channels to the mainframe.
        Access routers at the GZAOP location are connected through two physically separated
        permanent lines with central routers at the CL location with a speed of 2 x 2 Mbps.
        Backup connections are realized through the ISDN BRI module. All traffic between
        access routers at the GZAOP location and other locations of the CDRC is encrypted
        (IPSec 3DES).



C.3 COMPUTING HARDWARE SPECIFICATIONS
        Minimum requirements are that at the CDRC location there are physically separate
        servers (for passing the tariff) from the application server(s) (for updating and using),
        and separate server(s) for publication on the Internet.
176                                                             Section VI. Technical Requirements




C.4 SOFTWARE SPECIFICATIONS

C.4.1 GENERAL REQUIREMENTS
      All program solutions MUST work on Microsoft NT technology, and the installed
      operating system shall be Windows 2000 professional or newer.

C.4.2 GENERAL-PURPOSE SOFTWARE
      For general-purpose SW, MS Office 2000 Professional is planned, containing standard
      generic applications, Internet Explorer for Internet access and MS Outlook (or MS
      Outlook Express) for e-mail.

C.4.3 DATABASE SOFTWARE AND SOFTWARE DEVELOPMENT TOOLS
      The RDBMS MUST satisfy the following criteria:
                Assigned rights on data and procedures in the database:
                o Select;
                o Insert;
                o Update;
                o Delete;
                o Execute;
              Possibility of use on diverse computer platforms and network environments
               (in particular compatibility with the desired Windows NT platform);
              Management of distributed relational databases;
              Insuring of reference integrity;
              Support for 3-tier client-server architecture;
              Possibility of transaction processing;
              Compatibility with the SQL standard;
              Cascade data deletion;
              Possibility of sorting in Croatian language (see section C.1.3 Language
               Support);
              Data encryption;
              Acceptance of 4GL tools specifications;
              Support of security, protection and integrity functions;
              Have the capacity to trap and present error messages in Croatian.


C.5 SERVICE SPECIFICATIONS

C.5.1 PREPARATION OF THE INITIAL STATUS
      In order to be able to use the offered Customs Tariff Application (ACT) a conversion
      of all available data sources connected to the CT (in electronic form) is necessary, and
Section VI. Technical Requirements                                                             177




        to be done by CDRC employees (IT services). Such prepared data shall represent input
        data for the ACT.
        The CT Supplier shall receive from the CDRC the prepared initial status (texts,
        pictures, tables) in electronic format.The Supplier shall fill the database with such
        data. All documents that the Supplier receives from the CDRC shall be in Croatian,
        and only documents to be published on the Internet shall be translated and furbished to
        the Supplier in English.
        The formats in which the data sources will be furbished to the Supplier shall be agreed
        between the CDRC and Supplier.

C.5.2 SYSTEM INTEGRATION
        The Supplier MUST perform system integration of the existing informational
        resources with the new information system (implemented in CDRC) to enable simpler
        transition to work in the new network environment.
        The Supplier MUST ensure system integration services and a project for system
        integration, as well as ensure functionality of all installed program solutions.
        The Supplier MUST perform the following tasks, after procurement of the equipment:
                   System configuration:
                   o List users by organizational units;
                   o Organize user domains;
                   o Define user groups;
                   o Organize users by groups;
                   o Install support for using and sharing system resources in each user
                       domain (printers, disks, maps, etc.);
                   o Assign users access rights to system resources;
                   o Create “electronic mailboxes”;
                   o Other configurations of the system environment;
                 Installation and configuration of applications of other manufacturers (see
                  section C.5.2);
                 Configuration and installation of databases;
                 Configuration and installation of proprietary program solutions;
                 Ensure support to users of the information system;
                 System control and fine tuning during the Warranty period.
        The Supplier MUST perform installation of system software, which supports all parts
        of the described and offered information system. The installation MUST be performed
        according to the system implementation plan, which the Supplier MUST provide and
        agree with the Purchaser.
        After installation the Supplier MUST configure all servers and workstations, and then
        proceed with installation of the new information system applications and database
        system.
178                                                             Section VI. Technical Requirements




      The Supplier MUST provide updated support documentation on the installed system
      software for each workplace/computer (with version control) and changes to the initial
      status. The Supplier shall maintain the documentation updated and available to the
      Purchaser.

C.5.3 INSTALLATION AND CONFIGURATION OF APPLICATIONS AND DATABASES
      The Supplier MUST install subsystems of the new information system. Before
      installation the Supplier MUST, in accordance with the Purchaser, test not only the
      newly developed functionality, but all other connected parts of the information system.
      The Purchaser shall control correctness and quality of the implemented functionality,
      before deciding on approving the continued installation in the field. The Supplier
      MUST, under Purchaser control, test the installation procedure before distribution.

C.5.4 INSTALLATION AND IMPLEMENTATION OF THE ACT
      In view of the size and complexity of the requested ACT development, and in order to
      lower risk, the Supplier MUST develop and implement the ACT in several phases, as
      follows:
          1.    Design of documentation for developing the ACT, which ends with
                acceptance of the documentation;
          2.    Developing the ACT, which ends with preliminary acceptance tests;
          3.    Pilot-implementation and adaptation of the subsystem at agreed locations,
                which ends with a final acceptance test (see section D.4);
          4.    Implementation of the CT for all users;
          5.    Training;
          6.    Support.
      The Supplier is expected to, according to requests, totally develop the concept of his IT
      solution, with description of the technological implementation and required
      infrastructure. The Supplier MUST describe all activities associated with each phase
      in the Project plan.
      The Supplier MUST, during installation and implementation of the ACT, ensure
      seamless functioning of the exiting IS, in such a manner that if problems in arise they
      are resolved, and the possible off-time for users is minimized.
      The Supplier MUST present to the Purchaser a plan of the project for safe data
      archival of the ACT, as well as documentation and the program basis for this part of
      the IS, and undertake all necessary measures to make this data readily and simply
      available.

C.5.5 TRAINING AND TRAINING MATERIALS

                                      C.5.5.1 User Training
      The Supplier MUST offer a training program and education courses for all users
      (users, technical and management staff) of the installed program solutions. Education
Section VI. Technical Requirements                                                             179




        should encompass all fields and disciplines connected to work on the installed
        application program solutions.
        The Supplier MUST submit a proposed plan of education, for the following fields:
               Methodology of computer use in a network environment, with emphasis on
                transfer, distribution and data circulation within the CURH IS;
             Installed system and application programming solutions;
             Applied program solutions, with accent on locations of data registration,
                movement of data and their connections.
        The proposed plan of education MUST contain:
                 Locations where the education is held;
                 Timing (limitations) and duration of education;
                 Number, qualifications and experience of instructors providing education;
                 Detailed contents;
                 Necessary pre-requisites for education (number of students per instructor,
                  required SW, HW and other) at the educational locations;
                 Use of user manuals during education.


C.6 SERVICES TO BE PROVIDED UNDER A SEPARATE,
    TO-BE-AGREED “CUSTOMER SERVICES CONTRACT”
        Based on the corresponding proposals in Preliminary Project Plan of the Supplier’s bid
        and the subsequent Agreed and Finalized Project Plan, the Supplier MUST offer a
        “Customer Service Contract” that fulfills the requirements below.
        The Customer Service Contract MUST coincide with the Warranty Service Period
        specified in the SCC for GCC 29.4. It MUST also be annually renewable at the
        Purchaser's sole discretion.

C.6.1 SUPPORT
        The Support service starts from the day of Operational Acceptance of the Entire
        System and should be performed during one (1) year.
        The Support service MUST be available during work hours (see section E.5, Purchaser
        Working Hours Table) for users of the IS located at the locations listed in section E.4,
        Site(s) Table 2, for work days specified in the section E.6, Table of Holidays and Other
        Non-Working Days.
        The support tasks which the Supplier MUST perform are:
        1) Support to users of the information system;
                 Advice – advice to users, for more efficient use of the information system.
                 Corrective help – permanent help by means of a help desk to users, when the
                  system is not functioning according to specification (whether the source of
                  error is in the system, HW or user’s incorrect operation) – enabling to finish
                  started jobs, without data loss or with minimal data loss.
180                                                            Section VI. Technical Requirements




      2) Support to the CDRC IS
      Relates to the Supplier’s support to the information personnel of the Purchaser. This
      includes help to IT employees in solving problems related to the Information System,
      and related to customizing system software, databases or problems in their work.
      The Supplier is not obliged to perform HW repairs or repairs of network equipment
      (active and passive) for which the sole responsibility is with the equipment Supplier.
      The Supplier MUST perform regular inspections (by means of montly controls of IS,
      and hand over a written report to the CDRC at latest on the 5th day of the month for the
      previous month) of the system functionality. The goal of these preventive tasks is to
      monitor the system status, i.e. checking correctness of the local network, databases,
      system and application software.
      The Supplier ensures support to the user and Information System functionality. This
      support consists of the following groups of activities:
           Technical support;
           Warranty Service;
           User support/Hot User line;
           Technical Assistance.
      The Supplier MUST perform the following modes of support:
           Telephone interventions;
           Network interventions;
           On-site interventions with the user;
           Work performed at the Supplier’s location.
      The Supplier MUST perform regular inspections of the functionality of the system.
      The goal of this preventive work is to monitor the system status, i.e. check the
      functioning of the local network, database, system and application software.
      The period for which these services are required is ONE (1) YEAR from the day of
      acceptance.

                                   C.6.1.1 Technical Support
      Refers to the Supplier’s capability to provide support to the Purchaser’s personnel in
      the warranty and outside of the warranty period. This includes help to the IT personnel
      in resolving problems connected to the functionality of the Supplier’s applications, and
      in connection with customizing the system software, as well as problems related to
      performance of the software and application software of other manufacturers. The
      technical support also refers to the Supplier’s capability to remove all non-
      functionality of the system which can arise in using the installed program solutions.

                                    C.6.1.2 Warranty Service
      Relates to the Supplier’s capability to remove all functionality problems which could
      arise in the period of usage of the installed ACT program solution, and in connection
      with removing problems in CT functionality.
Section VI. Technical Requirements                                                               181




                                     C.6.1.3 User support/Hot-line
        Refers to the Supplier's capability to provide support to the Purchaser's personnel in
        the warranty and post-warranty period. This includes help to IT personnel in solving
        problems which can arise in working with the Supplier's applications, and are
        connected to customizing system software or problems related to its work with
        applications of other manufacturers.

                                     C.6.1.4 Technical Assistance
        Refers to the Supplier's capability to provide support to the Purchaser's IT personnel
        and all other users in the warranty and post-warranty period.

C.6.2 SYSTEM INTEGRATION
        After the Operational Acceptance of the Entire System, the Supplier MUST ensure
        system integration services described in section C.5.2, as well as ensure functionality
        of all installed program solutions as they are to be performed under the main Supply
        and Installation Contract, during the warranty period.

C.6.3 USER TRAINING
        After the Operational Acceptance of the Entire System, the Supplier MUST perform a
        training program and education courses for all users (users, technical and management
        staff) of the installed program solutions described in section C.5.5.1 as they are to be
        performed under the main Supply and Installation Contract, during the Warranty
        period.

C.6.4 UPGRADING AND UPDATING
        After the Operational Acceptance of the Entire System, the Supplier MUST promptly
        inform the Purchaser of any upgrades/updates of system software and applications of
        other manufacturers that become available. The Supplier MUST also inform the
        Purchaser of any possible benefits and downsides of implementing the
        upgrades/updates.
        The Purchaser shall inform the Supplier in writing of any upgrades or updates it wishes
        the Supplier to implement. Unless mutually agreed to by the Purchaser and the
        Supplier, the Purchaser’s request for upgrades and updates shall not be more frequent
        than once a contract year. The “Customer Service Contract” MUST address the change
        order process, implementation, testing, and the financial obligations of the Purchaser.

C.6.5 CHANGE ORDER PROCEDURE
        The Change order procedure is also part of the separate, to-be-Agreed “Customer
        Services Contract”, and they refer minimally to:
                 Format of export data;
                 Functional and nonfunctional requirements;
                 Other technical features.
182                                                            Section VI. Technical Requirements




      Procedures for changes should minimally contain:
                 The activities needed to be performed in order to implement changes:
                  o Description of the change order procedure;
                  o The way in which a change order for code changes is accepted or denied;
                  o Implementation
                  o Testing
                 Phases in implementing change order procedures;
                 Staffing;
                 Ways of setting deadlines for implementing changes;
                 Metrics for determining prices for implementing changes;
                 Quality Assurance;
                 Reporting procedures.

C.6.6 TECHNICAL CONSULTATION
      The Supplier MUST maintain adequate technical expertise and resources so that, upon
      a written request from the Purchaser, the Supplier MUST within three weeks provide a
      written proposal for the modifications to the equipment, software and/or network
      topology in accordance with changes in Purchaser's business requirements. Any
      subsequent change in the System would be governed through the Change Order
      procedures of the Contract. Alternatively, such changes may addressed through other
      contractual arrangements, as agreed upon between the Purchaser and the Supplier
      (including the possibility of the Purchaser contracting the work with another supplier –
      with due consideration of the implications for the Supplier's warranty service
      obligations).

C.6.7 TROUBLESHOOTING AND MAINTENANCE
      The Supplier MUST maintain sufficient technical resources to provide troubleshooting
      and maintenance for the System in accordance with the requirements below.
      These troubleshooting and maintenance services shall address technical problems that
      are not covered under the Supplier’s defect free warranty obligations under the Contact
      (as specified in GCC 29).
      The “Customer Service Contract” MUST provide for the response time and mode of
      troubleshooting and maintenance services as they are specified above in C.6.1.2 for the
      Warranty Services.



C.7 DOCUMENTATION -- GENERAL REQUIREMENTS

C.7.1 REPORTS
      All reports produced by the Supplier should satisfy the following requirements.
      1)       Be entirely in Croatian.
      2)       Be easily readable with dark print.
Section VI. Technical Requirements                                                        183




        3)    Have every page numbered.
        4)    Have an outline similar to the following:
                 a)    Preface
                 b)    Introduction
                        Purpose
                                Scope
                                Definitions, acronyms, and abbreviations
                                References
                                Overview of rest of the document
                  c)     Body of Document
                  d)     Appendixes
                  e)     [Index]
        5)    Have a title page which contains the following items:
                  a)     Project Title: Name of the project for which the report was prepared.
                  b)     Document Title: Name of the report.
                  c)     Abstract: A summary of what the report is all about.
                  d)     Document Version: Version of the report.
                  e)     Date: Date of the last revision of the report.
                  f)     Status: Status of the report. For example, DRAFT or APPROVED.
        6)    Have a preface which includes tables for each of the following:
                  a)     People Involved in the Preparation of the Document: List of people
                         who contributed to the development of the report.
                  b)     Review List: List of people who reviewed and approved the document.
                  c)     Change History: A chronological record of details (Version, Date and
                         Revision Description) about the updates that have been made to the
                         report.
        7)    Have a Table of Contents
        8)    Have a Table of Figures (where applicable)
        9)    Have a Table of Tables (where applicable)
        10)   Last page of each document shall be blank.

C.7.2 PERIODIC SUBMITTALS/DELIVERABLES
        The minimum requirements for periodic documents prepared by the Supplier is as
        follows.
        1)    Be entirely in Croatian.
        2)    Contain a distribution list
        3)    Be easily readable
        4)    Contain date
184                                                            Section VI. Technical Requirements




C.8 DOCUMENTATION - SOFTWARE VERIFICATION AND
    VALIDATION PLAN (SVVP)
      The SVVP specifies goals and approaches to the Verification and Validation (V&V)
      activities. The plan also specifies the V&V processes, identifies techniques and tools
      to be used, and specific plans for performing the V&V activities. The SVVP should
      follow the outline below.
      1)    Introduction
                o Purpose
                o Definitions, acronyms, and abbreviations
                o References
      2)    Verification and Validation Overview
                o Organization
                o Master Schedule
                o Resource Summary
                o Responsibilities
                o Tools, Techniques and Methodology
      3)    Life cycle Verification & Validation The Activities
                o Conceptual Phase
                o Requirements Definition and Analysis Phase
                       1.    Software Requirements Specification (SRS) Review
                      2.    System Test Plan
                      3.    Acceptance Test Plan
               o Design Phase
                   1.    Software Design Review (Preliminary and Critical)
                      2.    Unit Test Plan
                      3.    Integration Test Plan
                      4.    Unit Test Design
                      5.    Integration Test Design
                      6.    System Test Design
                      7.    Acceptance Test Design
               o Implementation Phase
                   1.   Unit Test Case/Script generation
                      2.    Unit Test Case/Script execution
                      3.    Code review
                      4.    Integration Test Case/Script generation
                      5.    System Test Case/Script generation
                      6.    Acceptance Test Case generation
Section VI. Technical Requirements                                                    185




                   o Testing Phase
                       1.     Integration test execution
                          2.     System test execution
                          3.     Acceptance test script generation
                   o Installation Phase
                        1.     Audit (functional and document)
                          2.     Acceptance test execution
                   o Operations and Maintenance Phase
                       1.    Software modification evaluation
                          2.     Software change control, reporting
        4)    Software Verification and Validation Reporting
                 o Task Reporting
                 o Summary Report Verification and Validation Phase
                       1.    Description of V&V tasks performed
                          2.     Summary of task results
                          3.     Summary of anomalies and resolution
                          4.     Assessment of software quality
                          5.     Recommendations
                   o Anomaly Report
                       1.   Description and location
                          2.     Impact
                          3.     Cause
                          4.     Criticality
                          5.     Recommendations
                   o Verification and Validation Final Report
                       1.     Summary of all life-cycle V&V tasks
                          2.     Summary of task results
                          3.     Summary of anomalies and resolutions
                          4.     Assessment of overall software quality
                          5.     Recommendations



C.9 DOCUMENTATION - SOFTWARE CONFIGURATION
    MANAGEMENT PLAN (SCMP)
        The Software Configuration Management Plan should follow the outline below.
        (a)   Introduction
                  o Purpose
186                                                           Section VI. Technical Requirements




              o Scope
              o Definitions and acronyms
              o References
              o Overview of the document
      (b)   Management
              o Organization. This subsection shall describe the organizational structure
                 that influences the configuration management of the software during the
                 development and the operation and maintenance phases. This shall:
                    1.     Describe each major element of the organization together with
                           the delegated responsibilities. Organizational dependence or
                           independence of the elements responsible for SCM from those
                           responsible for software development and use shall be clearly
                           described or depicted.
                      2.   Describe the interface between the developing organization and
                           the using organization, if any, with particular emphasis on the
                           transfer of SCM functions in the operation and maintenance
                           phase.
               o SCM Responsibilities shall describe:
                   1.  The responsibilities of the users and developer/maintenance The
                       Activity in the review, audit, and approval process during each
                       phase of the life cycle.
                      2.   Any SCM responsibilities of the representatives from each
                           organization participating in the product development.
                      3.   The overall responsibility of the Configuration Control Board.
                      4.   Description of additional responsibility the Supplier standardly
                           uses in developing SW products (possible additional permits).
               o A description of the methodology and means of ensuring functionality of
                 the SW product:
                    1.   Description of interactions between finished program
                         documentation and the finished SW product
                      2.   Description of monitoring changes in the program
                           documentation and implementation of said changes in the SW
                           product development (version description)
                      3.   Description of the HW development environment on which the
                           SW product shall be installed
               o SCMP Implementation shall establish the major milestones for
                 implementation of the SCMP, such as the establishment of:
                   1.   The configuration control board
                      2.   Each configuration baseline
                      3.   Schedules and procedures for SCM reviews and audits
                      4.   Configuration management of related software development,
                           test, and support tools
Section VI. Technical Requirements                                                                     187




                   o Applicable policies, directives and procedures, shall:
                       1.    Identify all applicable SCM policies, directives, and procedures
                             which are to be implemented as part of this plan. The degree of
                             implementation of each shall be stated
                          2.     Describe any SCM policies, and procedures that are to be
                                 written and implemented for this project,
                                     such as:
                                        Identification of levels of software in a hierarchical tree
                                        Program and module naming conventions
                                        Version level designations
                                        Software product identification methods
                                        Identification of specifications, test plans and procedures,
                                         programming manuals, and other documents
                                        Media identification and file management identification
                                        Document release process
                                        Turnover or release of software products to a library
                                         function
                                        Processing of problem reports, change requests, and
                                         change orders
                                        Structure and operation of configuration control boards
                                        Release, and acceptance of software products
                                        Operation of software library systems to include methods
                                         of preparing, storing, and updating modules
                                        Auditing of SCM The Activities
                                        Problem report, change request or change order
                                         documentation requirements describing purpose and
                                         impact of a configuration change, or both
                                        Level of testing required prior to entry of software into
                                         configuration management
        (c)   SCM The Activities
                o Configuration Identification shall
                      1.    Identify the software project baselines (that is, the initial
                            approved configuration identifications) and correlate them to the
                            specific life-cycle phases
                          2.     Delineate the project titling, labeling, numbering, and cataloging
                                 procedures for all software code and documentation.
                   o Configuration Control shall:
                       1.    Describe the level of authority for change approval to be used in
                             each of the life cycle phases.
188                                                   Section VI. Technical Requirements




            2.    Define the methods to be used to process change proposals to
                  established configurations., including
                       Identify the routing of change proposals during each of the
                        software life cycle phases.
                       Describe the methods of implementing approved change
                        proposals (to include changes in source and object code,
                        and documentation).
                       Describe the procedures for software library control,
                        including:
                             Access control
                             Read and write protection for applicable baselines
                             Member protection
                             Member identification
                             Archive maintenance
                             Change history
                             Disaster discovery
                       If patches must be used to change object code, describe the
                        methods for identification and control.
            3.    For each change management body:
                       Define the role of each; for example, change review
                        authority
                       Specify their authority and responsibility
                       Identify the chairperson and the membership in the
                        organizations, if the organizations have been formed
                       State how the chairperson and the members (and
                        alternates) are to be appointed, if the organizations have
                        not yet been formed
                       State the relationships of the developers and the users to
                        the CCB(s)
      o Configuration Status Accounting shall
          1.    Delineate how information on the status of configuration items
                is to be collected, verified, stored, processed, and reported
            2.    Identify the periodic reports to be provided, and their
                  distribution
            3.    State what dynamic inquiry capabilities, if any, are to be
                  provided
            4.    Describe the means to be used to implement any special status
                  accounting requirements specified by the user
      o Audits and Reviews shall
Section VI. Technical Requirements                                                                 189




                          1.     Define the SCM role in audits and reviews to be performed at
                                 specified points in the software life cycle
                          2.     Identify the configuration items to be covered at each of these
                                 audits and reviews
                          3.     State the procedures to be used for the identification and
                                 resolution of problems occurring during these audits and reviews
        (d)   Tools, techniques and methodologies shall identify, state the purposes, and
              describe (within the developers' scope of proprietary rights) the use of the
              specific software tools, techniques, and methodologies to be employed to support
              SCM on the specific project. This shall include the tools, techniques, and
              methodologies used to
                  o Identify software media and media documentation
                  o Bring documentation and media under SCM control and formally release
                      it to a user
        (e)   Supplier Control shall state the provisions for assuring that contractor –
              developed software meet established SCM requirements. As a part of this, this
              section shall
                  o Indicate the proposed methods for control of contractor insofar as it
                      impacts on the execution of this SCMP
                  o Explain the methods to be used:
                          1.    To determine the SCM capability of contractor
                          2.     To monitor their adherence to the requirements of this SCMP
        (f)   Records Collection and Retention shall:
                 o Identify the SCM documentation to be retained
                 o State the methods and facilities to be used to assemble, and maintain this
                    documentation. As part of this, identify any off-site backup facilities to
                    be use
                 o Designate the retention period


C.10 DOCUMENTATION - SOFTWARE REQUIREMENTS
     SPECIFICATION (SRS)
        The Software Requirements Specification should include:
        a)    Analysis of the current system to determine the extent to which it satisfies the
              Purchaser’s needs.
        b)    Definition of current system related problem that will be eliminate from the
              environment.
        c)    Logical Modeling of the required System.
        d)    Identification of hardware, software and networking requirements
        e)    Identification of measures of security, audibility and integrity.
190                                                            Section VI. Technical Requirements




      f)   All the diagrams (e.g. Data Flow diagrams, Structural model of data, Entity
           Relationship diagrams) that are produced as a result of system analysis phase as
           well as data dictionaries should be appended to the SRS.
      The Software Requirements Specification should omit:
      a)   Project Requirements (e.g. staffing, schedules, costs, milestones, The Activities,
           phases, reporting procedures)
      b)   Designs and design issues, such as
               o Partitioning the software into modules
               o Allocating functions to modules
               o Describing flow of information or control between modules
               o Choosing data structures
      c)   Product assurance plans (e.g. configuration management plans, verification and
           validation plans, test plans, quality assurance plans)
      The Software Requirements Specification should be:
      a)   Correct: The SRS is correct if and only if every requirement stated therein
           represents something required of the system to be built.
      b)   Unambiguous: The SRS is unambiguous if and only if every requirement stated
           therein has only one representation.
      c)   Complete: The SRS is complete if it possesses the following qualities:
               o Everything that the software is supposed to do is included in the SRS.
               o Definitions of the responses of the software to all realizable classes of
                   input data in all realizable classes of situations is described.
               o All pages are numbered; all figures and tables are numbered, named and
                   referenced
               o No sections are defined as To be determined (TBD)
      d)   Verifiable: The SRS is unverifiable if it contains requirements which either:
               o Could be implemented with varying degrees of efficiency, accuracy or
                   validity.
               o Cannot be checked.
      e)   Consistent: The SRS is consistent if and only if no subset of individual
           requirements stated therein conflict.
      f)   Understandable: The SRS should be readable and understandable by
           non-computer specialists.
      g)   Modifiable: The SRS is modifiable if its structure and style are such that any
           necessary changes to the requirements can be made easily.
      h)   Traceable: The SRS is traceable if the origin of each of its requirements is clear
           and if it facilitates the referencing of each requirement in future development.
      The Software Requirements Specification should follow the outline below.
      a)   Introduction
               o Purpose
               o Scope of product
               o Definitions, acronyms, and abbreviations
Section VI. Technical Requirements                          191




                 o References
                 o Overview of rest of the SRS
        b)    Overview of Current System
                 o Organizational Structure
                 o Data Model
                 o Functional Model
                 o Problems
        c)    Logical Model of the Required System
                 o Data Model
                 o Data Dictionary
                 o Functional Model
        d)    General Description
                 o Product Perspective
                 o Product Functions
                 o User Characteristics
                 o General Constraints
                 o Assumptions and dependencies
        e)    Specific Requirements
                 o Functional Requirements
                 o Functional requirement 1
                        1.    Introduction
                          2.     Inputs
                          3.     Processing
                          4.     Outputs
                   o Functional requirement 2
                       1.    Introduction
                          2.     Inputs
                                 …
                   o Functional requirement 3
                             …
                   o External Interfaces
                       1.     User Interfaces
                          2.     Hardware Interfaces
                          3.     Software Interfaces
                          4.     Communication Interfaces
                   o Performance & Capacity Requirements
                   o Design Constraints
                        1.   Standards Compliance
192                                                            Section VI. Technical Requirements




                      2.    Hardware Limitations
               o Attributes
                    1.    Ease of Use
                      2.    Availability
                      4.    Transferability/Conversion
                      5.    Reliability
               o Other Requirements
                   1.    Database
                      2.    Security
                      3.    Protection of privacy of subjects of information
                      4.    Recovery
                      5.    Operational Support
                      6.    Site Adaptation
                      7.    Packaging
                      8.    Installation
      f)   Documentation
      g)   Training
      h)   Appendices
      i)   [Index]


C.11 DOCUMENTATION - SOFTWARE DESIGN
     DESCRIPTION (SDD)
      The SDD shows how the software system is going to be structured to satisfy the
      requirements identified in the SRS. The SDD is a translation of the requirements into a
      description of the software structure, software components, interfaces, and data
      necessary for the implementation phase. The SDD is a detailed blueprint for the
      implementation activity. In a complete SDD, each requirement must be traceable to
      one or more design entities.
      The SVVP should follow the outline below:
      1)   Introduction
               o Purpose
               o Definitions, acronyms, and abbreviations
               o References
               o Overview of rest of the SDD
      2)   Decomposition Description
               o Module Decomposition
                     1.   Module 1 Description
                      2.    Module 2 Description...
Section VI. Technical Requirements                                                           193




                   o Data Decomposition
                       1.    Data Entity 1 Description
                          2.     Data Entity 2 Description...
        3)    Dependency Description
                  o Inter-module Dependencies
                  o Data Dependencies
        4)    Interface Description
                  o Module Interface
                  o Module 1 Description
                  o Module 2 Description …
        5)    Detailed Design
                  o Module Detailed Design
                        1.   Module 1 Detail
                          2.     Module 2 Detail …
                   o Data Detailed Design
                       1.    Data Entity 1 Detail
                          2.     Data Entity 2 Detail …
        6)    Packaging
                 o Special Program Overlay Provisions
                 o Software Release
        7)    Special Notes
        8)    Appendices
        9)    [Index]


C.12 DOCUMENTATION - USER DOCUMENTATION

C.12.1        USER DOCUMENTATION GENERAL REQUIREMENTS

                                             C.12.1.1 Content
        Users of software need documents both to learn about the software (instructional
        mode) and to refresh their memory about it (reference mode). Therefore, the user
        documentation should be composed of the following sections.
        (a)   User instructions which contain an introduction, a description of the user's
              interaction with the system, and a description of any required training for using
              the system.
        (b)   A system narrative purpose and description
        (c)   Input/Output specifications
        (d)   Samples of original source documents and examples of all input formats (forms
              or displays)
194                                                              Section VI. Technical Requirements




      (e)   Samples of all outputs (forms, reports or displays)
      (f)   Data entry instructions
      (g)   References to all documents or manuals intended for use by the users
      (h)   A description of the system limitations
      (i)   A description of all error situations which can occur and how to react

                                          C.12.1.2 Format
      The basic components of a user document are the following:
      (a)   Title Page
      (b)   Table of contents
      (c)   List of illustrations
      (d)   Introduction
      (e)   Body of document
      (f)   Error messages
      (g)   Appendixes
      (h)   Bibliography
      (i)   Glossary
      (j)   [Index]

                                C.12.1.3 Body of the User Document
      (a)   Body of Instructional Mode Documents
               o Information-oriented instructional documents give the reader background
                  information or theory needed to understand the software. Describe the
                  scope of the documents before giving the information forming the major
                  portion of the document. Use topics to organize an information-oriented
                  instructional document; for example, organize the document by:
                      1.    Theory
                       2.    Software features
                       3.    Software architecture
                o Task-oriented instructional documents give the reader the necessary
                  information to carry out a specific task or attain a specific goal. Use task
                  relations to organize a task-oriented document or section; for example,
                  organize by:
                     1.    Task groups
                       2.    Task sequence
                       Include the information on the following:
                       1.    The scope of the material to be discussed.
                       2.    Any materials the user will need to complete the task (for
                             example, input manuals, passwords, computers, peripherals,
                             cabling, software, drivers, interfaces and protocols). Optionally,
Section VI. Technical Requirements                                                            195




                                 describe separately materials common to all or many functions
                                 and refer to that description.
                          3.     Any actions, technical or administrative, that must be done
                                 before starting the task (for example, obtain system passwords,
                                 access authorization, disk space). Optionally, describe in a
                                 separate section preparations common to all or many functions
                                 and refer to that section.
                          4.     General cautions and warnings that apply to the task. Place
                                 specific cautions and warnings on the same page and
                                 immediately before the action that requires caution or warning.
                          5.     Method for each task, including
                                     What the user must do.
                                     What function, if any is invoked (including how to invoke
                                      the function and how to recognize normal termination).
                                     Possible errors, how to avoid them and how to resolve
                                      them.
                                     What results to expect.
                          6.     Related Information, such as:
                                     Tasks frequently performed together and their relationship.
                                     Other tasks customarily performed by users of this
                                      document that could be supported by the methods
                                      described in this section. Describe this support.
                                     Notes, limitations, or constraints
        (b)   Body of Reference Mode Documents. A user reference document should be
              organized the way a user accesses a software function., such as:
                 o By command
                 o By menu
                 o By system calls
                  Within this organization, arrange the functions for easy access and random
                  user access (for example, alphabetical order or a menu-tree hierarchy). For
                  each function, the body of a reference mode document should include
                  following.
                   o The purpose of the function
                   o Materials needed to use the function or command (for example, input
                     manuals, passwords, computers, peripherals, cabling, software drivers,
                     interfaces and protocols). Optionally, describe separately materials
                     common to all or many functions and refer to that description.
                   o Any actions, technical or administrative, that must be completed before
                     using the function or command (for example, obtain system passwords,
                     access authorization, disk space). Optionally, describe separately
                     preparations common to all or many functions and refer to that
                     description.
196                                                            Section VI. Technical Requirements




               o The identity and description of all data required for the correct processing
                 of each function. Use one of the following methods.
                    1.    Describe inputs used only by a single function in the section
                          devoted to that function.
                      2.    Describe in a single section or in an appendix inputs used by
                            multiple functions. Refer to that section or appendix when
                            describing these functions.
               o General cautions and warnings that apply to each function. Place specific
                 cautions and warnings on the same page and immediately before the
                 action that requires a caution or warning.
               o All information needed to use and control the function. Describe all
                 parameters. Include
                    1.    Required parameters
                      2.    Optional parameters
                      3.    Default options
                      4.    Order and syntax
               o How to interrupt the function during execution and how to restart it.
               o How to recognize function terminations, including abnormal
                 terminations.
               o The results of executing the function, such as
                    1.    Screen display
                      2.    Effect on files or data:
                      3.    Completion status values or output parameters
                      4.    Outputs that trigger other actions (such as mechanical actions in
                            process control applications)
               o Common error conditions that could occur as a result of executing the
                 function, and describe how to detect that the error has occurred. For
                 example, list any error messages that the system displays.
               o Other useful information about the function that does not readily fit under
                 any of the sections previously described, such as:
                    1.    Limitations and constraints
                      2.    Notes
                      3.    Related functions
               o Other useful information about the function that does not readily fit under
                 any of the sections previously described.

                                     C.12.1.4 Error Messages
      Error messages in an easily accessed location (for example, in a separate section,
      chapter, appendix, or a separate document). For each error message, describe in detail
      the error that caused it, the procedures needed to recover from it, and the action(s)
Section VI. Technical Requirements                                                        197




        required to clear it. Describe known software problems here or in a separate document
        and provide alternative methods or recovery procedures.
198                                                             Section VI. Technical Requirements




          D. TESTING AND QUALITY
         ASSURANCE REQUIREMENTS

D.1 TESTING AND QUALITY ASSURANCE PROJECT
    TEAM
      The Purchaser shall form a mixed commission of it’s own Customs and IT experts,
      and their counterparts from the Supplier. The CDRC officials elected to this
      commission shall have all necessary business and technical know-how for fulfilling the
      Purchaser’s obligations. The Customs professionals shall provide functional know-
      how, and the IT experts non-functional and technological know-how.



D.2 ACCEPTANCE OF SOFTWARE REQUIREMENTS
    SPECIFICATION
      The SRS shall be reviewed by the Purchaser at several stages of its development. In
      particular, the Supplier should present the following sections of the SRS as they
      become ready for review:
            Analysis of current system;
            Logical Modeling of the new system;
            Identification of hardware, software and network requirements;
            Security, Audibility, Integrity and Recovery measures.
      The results of the review shall be documented in an SRR Report that identifies all
      deficiencies identified in the review and provides an agreed-to plan and schedule for
      corrective action. After the SRS is updated to correct any deficiencies, the SRS should
      be placed under configuration control to establish the baseline to be used for software
      design effort.
             The review shall include, but not be restricted to, the topics identified in the
              following Checklist:
                (a) Where does the solution fit in the Purchaser organization's overall
                     strategy?
                (b) How does the solution support the Purchaser's business architecture,
                     information architecture, and systems architecture?
                (c) Is the description of and approach to human-machine interface
                     adequate?
                (d) Is the use of symbols and specification of interfaces consistent?
                (e) Is the verification and acceptance requirements complete?
                (f) What are the key performance requirements?
                (g) What are the key compatibility requirements?
Section VI. Technical Requirements                                                           199




                   (h) What are the architectural growth requirements?
                   (i) What are the non-goals?
                   (j) What requirements will be delayed until a later time?
                   (k) What is the environment the solution will address or in which it will
                       operate?
                   (l) What are the requirements for releasing the solution into the
                       Purchaser's business environment?
                   (m) How can the target populations for the solution be characterized?
                        Organizations
                                Skill levels of workforce
                                Work flow patterns
                   (n)    What hardware and software is currently in use?
                   (o)    What documentation and other publications are required to support
                          any proposed information system?
                   (p)    What levels of support training will be needed?
                   (q)    What are the desired performance characteristics of the hardware and
                          the software under normal and extreme operating conditions?
                   (r)    What characteristics of the information system will affect the user's
                          ability to accomplish the task in a dependable, predictable way?
                   (s)    What criteria will be used for making trade-offs and assigning
                          priorities?
                   (t)    What are the key solution features? Rank the requirements and
                          features according to relative priority such as
                           Desirable
                                Important
                                Essential
                   (u)  Are there any special reliability or up-time requirements?
                   (v)  What are the maintenance requirements?
                   (x)  Does the system specification describe what but not how?
                   (y)  Are system constraints defined properly?
                   (z)  Does SRS specify interfaces to external entities clearly?
                   (aa) Is SRS testable?
                   (ab) Is SRS complete?
                   (ac) Does SRS cover the System requirements?
                   (ad) Do stated goals and objectives for the System remain consistent with
                        system goals and objectives?
                   (ae) Have important interfaces to all system elements been described?
                   (af) Is information flow, content and structure adequately defined for the
                        problem domain?
                   (ag) Are diagrams clear, can each stand alone without supplementary text?
200                                                      Section VI. Technical Requirements




            (ah) Do major functions remain within scope and has each been adequately
                  described?
            (ai) What is the technological risk of the development?
            (aj) Have alternative software requirements been considered?
            (ak) Have validation criteria been stated in detail? Are they adequate to
                  describe a successful system?
            (al) Do inconsistencies, omissions, or redundancy exist?
            (am) Is the user contact complete?
            (an) Has the user reviewed the user’s guide manual or prototype?
            (ao) How are the Software Project Plan estimates affected?
         The review of the Data Flow Diagrams (DFD) shall include, but not be
          restricted to, the topics identified in the following Checklist:
            (a) Is the diagram correct?
            (b) Are all names meaningful?
            (c) Are data flow names unique?
            (d) Is the DFD Clear? Are there too many repetitions or too many data
                  flow cross-over?
            (e) Are any parts of the diagram with few or no data flows passing
                  between them?
         The review of the Entity-Relationship (ER) diagrams shall include, but not be
          restricted to, the topics identified in the following Checklist:
            (a) Is the ER diagram complete, including all entities and relationships?
            (b) Does each entity type have a name, label, and description?
            (c) Does each relationship have a name and description?
            (d) Is the cardinality and optionality of relationships identified?
         Notwithstanding the need to reach an acceptable point in the review of the
          SRS that allows the Supplier to move on to the Design and other subsequent
          phases of the System development (i.e., “Operational” Acceptance of the
          SRS), the SRS will need to evolve during the development life cycle. Among
          other reasons for such changes include:
            (a) At the time the SRS is prepared it may not be possible to specify some
                  details. When that information is provided, the SRS is updated.
            (b) Additional changes may occur as inaccuracies, shortcomings or
                  deficiencies in the SRS are discovered.
                  Accordingly,
            (a) The requirements should be specified as complete and accurate as
                  possible even if the revisions can be foreseen.
            (b) The formal change process should be initiated to identify, control,
                  track and report any changes as soon as they are identified.
            (c) The approved changes should be incorporated in the SRS by providing
                  an audit trail of changes.
Section VI. Technical Requirements                                                             201




D.3 ACCEPTANCE OF SOFTWARE DESIGN DESCRIPTION
                 The SDD shall be reviewed by the Purchaser at several stages of its
                  development. In particular, the Supplier should present the following sections
                  of the SRS as they become ready for review:
                 The review shall include, but not be restricted to, the topics identified in the
                  following Checklist:
                         (a)   Is the SDD complete?
                         (b)     Does the SDD cover the System requirements?
                         (c)     Do stated goals and objectives for the System remain consistent
                                 with system goals and objectives?
                         (d)     Have important interfaces to all system elements been
                                 described?
                         (e)     Are diagrams clear, can each stand alone without supplementary
                                 text?
                         (f)     Have validation criteria been stated in detail? Are they adequate
                                 to describe a successful system?
                         (g)     Do inconsistencies, omissions, or redundancy exist?
                         (h)     Has the user reviewed the user’s guide manual or prototype?
                         (i)     How are the Project Plan estimates affected?



D.4 ACCEPTANCE OF PILOT SITE IMPLEMENTATION
        With the goal of lowering risk, the Supplier shall develop and implement the ACT in
        several phases (see section C.5.4), of which one is the implementation phase.
        The pilot-implementation and adaptation of the subsystem should be performed at the
        following network locations:
             Headquarters;
             Ministry of Industry;
             Customs House Zagreb (CL);
             one of Customs Offices;
             Implementing the ACT for Internet publication.
        The pilot implementation ends with a final acceptance test which includes:
                 Technical documentation;
                 Performancerequirements:
                  o To be performed by measuring access speed to the database which cannot
                      be less than 16 Kb/sec,
                  o Response time of the system under load cannot be more than 300 ms.
                 Functional testing to be performed by:
                  o Qualified users (CDRC employees that use the customs tariff every day).
202                                                             Section VI. Technical Requirements




              Stress testing to be performed by:
                o Unqualified users (who do not work with the customs tariff, and use the
                    ACT for the first time).
      Stress testing shall be performed under load from all locations planned for pilot site
      implementation.
      Review of the source code and/or data structure to ensure their fidelity to the accepted
      technical documents.
      The ACT is considered to completely functionally satisfy the Purchaser after signature
      on the final memorandum on acceptance of the ACT implementation for all test
      locations of the CDRC.



D.5 OVERALL ACCEPTENCE OF COMPLETE AND
    INTEGRATED SYSTEM
      Overall acceptenence of complete and integrated system shall be reviewed by the
      testing and quality assurance project team.
      Overall acceptenence of complete and integrated system shall include, but not be
      restricted to the topics identified as follows:
              Has the project plan been met completely?
              Is the SW documentation complete and updated?
              Does the complete and integrated system cover the System requirements?
              Are all functional requirements of the ACT satisfied, for various groups of
               users, including:
                o Passing the CT;
                o Updating the CT;
                o Using the CT:
                        Searching and selecting the CT;
               o Publication of the CT on the Internet?
              Are all nonfunctional requirements of the ACT satisfied?
              Does the whole integrated system function correctly for the intended purpose?
Section VI. Technical Requirements   203




      E. IMPLEMENTATION SCHEDULE
204                                                                                                                                Section VI. Technical Requirements




E.1 IMPLEMENTATION SCHEDULE TABLE
                                                              “entire System procurement”

                                                                                                    Delivery
 Line                                                                                              (Bidder to      Installation      Acceptance       Liquidated
                                                          Configuration Table
 Item                       Subsystem/Item                                      Site/Site Code   specify in the    (weeks from       (weeks from       Damages
                                                                 No.
  No.                                                                                             Preliminary     Effectiveness)    Effectiveness)    Milestone
                                                                                                 Project Plan)

      0.   Project Plan                                           --                  --              --               --                W__               no
           Documentation - Software Verification and
      1.                                                   Tech. Requir. C.8          --              --               --                W__               no
           Validation Plan
           Documentation - Software Configuration
      2.                                                   Tech. Requir. C.9          --              --               --                W__               no
           Management Plan
           Documentation - Software Requirement
  3.1                                                      Tech. Requir. C.10         --              --               --                W12              yes
           Specification
  4.1      Documentation – Software Design Description     Tech. Requir. C.11         --              --               --                W16              yes
      5.   Development of Customs Tariff application              --                  --              --               --                W__               no
           Timely provision of network and hardware
           infrastructure for Pilot site Implementation                           HQ, CL,
      6.                                                          --                                  --               --                W__               no
                                                                                 1xR2, 1xR5
           (This is a Purchaser’s duty.)
                                                                                  HQ, CL,
  7.1      Pilot Site Implementation                      Tech. Requir. C.5.4                         --              W__                W38              yes
                                                                                 1xR2, 1xR5
      8.   User and Technical Documentation                Tech. Requir. C.12         --              --               --                W__               no
           Timely provision of network and hardware
      9.   infrastructure                                         --               All sites          --               --                W__               no
           (This is a Purchaser’s duty)
  10.0     System Installation and Integration            Tech. Requir. C.5.1      All sites          --              W__                W__               no
Section VI. Technical Requirements                                                                                                                                            205



                                                                                                                Delivery
  Line                                                                                                         (Bidder to      Installation      Acceptance        Liquidated
                                                                    Configuration Table
  Item                     Subsystem/Item                                                   Site/Site Code   specify in the    (weeks from       (weeks from        Damages
                                                                           No.
   No.                                                                                                        Preliminary     Effectiveness)    Effectiveness)     Milestone
                                                                                                             Project Plan)

                  Installation and configuration of the
                   System Software and
  10.1                                                               Tech. Requir. F.7.1       All sites          --               W__               W__                no
                   System-Management Utilities (SS&SMU)
                   on servers and workstations
                  Installation and configuration of the
  10.2                                                               Tech. Requir. F.7.2       All sites          --               W__               W__                no
                   Communications Software
                  Installation and configuration of the
  10.3                                                               Tech. Requir. C.4.2       All sites          --               W__               W__                no
                   General-Purpose Software
                  Installation and configuration of the
  10.4             Database Software and Development                 Tech. Requir. C.4.3       All sites          --               W__               W__                no
                   Tools
                  Installation and configuration of the
  10.5             Application of the Customs Tariff (The            Tech. Requir. C.5.3       All sites          --               W__               W__                no
                   ACT) and databases
   11.    User Training                                             Tech. Requir. C.5.5.1      All sites          --                --               W__                no
          Operational Acceptance of Complete and
   12.                                                                        --               All sites         W52               W52               W52               yes
          Integrated System

Note:    Refer to the System Inventory Table(s) below for the specific items and components that constitute the Subsystems or item. Refer to the Site Table(s) below for details
         regarding the site and the site code.
          - - indicates not applicable. “ indicates repetition of table entry above.
206                                                                                                                                         Section VI. Technical Requirements



E.2 SYSTEM INVENTORY TABLE (RECURRENT COST ITEMS) – SERVICES
                                                                                                                         Warranty Period
                            Component                                                            Relevant Technical   Quantities / Requirements
                                                             Component Name
                               No.                                                                  Requirement
                                                                                                                                   Y1
                                 1.          Support                                                     C.6.1            All items / All sites
                                 2.          System integration                                          C.6.2                  All sites
                                 3.          User training                                               C.6.3                     HQ
                                 4.          Upgrading and Updating                                      C.6.4                  All sites
                                 5.          Change Order procedure                                      C.6.5                     HQ
                                 6.          Technical Consultation                                      C.6.6                     HQ
                                 7.          Troubleshooting and Maintenance                             C.6.7                  All sites

Note:   The above items shall be covered by a separate Customer Service Contract, as per Technical Requirements sub-section C.6.
        Any other Service obligations, which is not listed in this table fall under the main Contract.
Section VI. Technical Requirements                                                                                                         207



E.3 SITE(S) TABLE 1
                                                                    “entire System procurement”

                        Site Code                       Site Type                     City/Town/Region         Primary Street Address

                           HQ        Headquarters                                          Zagreb            Alexandera von Humboldta 4a
                           CL        Central location                                      Zagreb                Avenija Dubrovnik 11
                           R1        Customs House                                                  See Site(s) Table 2
                           R2        Border/Clearing                                                See Site(s) Table 2
                           R3        Border                                                         See Site(s) Table 2
                           R4        Clearing                                                       See Site(s) Table 2
                           R5        GZAOP                                                          See Site(s) Table 2
                           R6        Other ministries                                               See Site(s) Table 2
208                                                                                                                                  Section VI. Technical Requirements



E.4 SITE(S) TABLE 2
                                                                     “entire System procurement”

            Customs           Site Code
  Site ID                                                          Site Name                                               Address
             House       [See Site(S) Table 1]
  CL001      Zagreb               R1             CACA Zagreb                             Avenija Dubrovnik 11, Zagreb
  DU002     Dubrovnik             R1             CACA Dubrovnik                          Dr. Ante Starčevića 53, 20000 Dubrovnik
  DU003     Dubrovnik             R2             CI Zračna Luka Dubrovnik                Zračna Luka Dubrovnik, 20217 Čilipi
  DU004     Dubrovnik             R3             CI Luka Gruţ - putnički                 Gruška obala1., 20 000 Dubrovnik
  DU005     Dubrovnik             R2             CI Gornji Brgat                         Brgat, 20207 Mlini
  DU006     Dubrovnik             R3             CI Karasovići                           Karasovići, 202515 Gruda
  DU007     Dubrovnik             R2             CI Korčula                              Obala Vinka Palatina, 20260 Korčula
  DU008     Dubrovnik             R4             CI Pošta Dubrovnik                      Put Republike 32, 20000 Dubrovnik
  DU009     Dubrovnik             R3             CI Zaton Doli                           Most Bistrina, 20231 Doli
  DU010     Dubrovnik             R3             CO Blato-Vela Luka                      Obala 1, 20270 Vela Luka
  KC011     Koprivnica            R1             CACA Koprivnica                         Kolodvorska b. b. , 48000 Koprivnica
  KC012     Koprivnica            R2             CI Goričan                              Komparija b. b. , 40332 Goričan
  KC013     Koprivnica            R4             CI Varaţdin                             V. Novaka 48c, 42000 Varaţdin
  KC014     Koprivnica            R2             CI Čakovec                              Carinski odvojak b. b. , 40000 Čakovec
  KC015     Koprivnica            R3             CI Dubrava Kriţovljanska                Ci Dubrava Kriţovljanska, 42208 Cestica
  KC016     Koprivnica            R2             CI Koprivnica                           Ivana Česmičkog b. b. , 48000 Koprivnica
  KC017     Koprivnica            R3             CI Banfi                                Banfi, 40 312 Štrigova
  KC018     Koprivnica            R3             CI Gola                                 Dravska b.b., 48 331 Gola
  KC019     Koprivnica            R3             CI Terezino polje                       Terezino Polje, 33 407 Gornje Bazje
Section VI. Technical Requirements                                                                                                                209



             Customs            Site Code
   Site ID                                                          Site Name                                                   Address
              House        [See Site(S) Table 1]
  KC020      Koprivnica              R3            CO II Bukovje                             Bukovje, 40313 Sv. Martin na Muri
  KC021      Koprivnica              R2            CI Kotoriba                               Kolodvorska b. b. , 40329 Kotoriba
  KC022      Koprivnica              R3            CI Mursko Središće                        Trg Josipa Bana Jelačića bb, 40315 Mursko Središće
  KC023      Koprivnica              R3            CI Trnovec                                CI Trnovec, 40306 Macinec
  KC024      Koprivnica              R4            CI Virovitica                             Stjepana Radića 110, 33000 Virovitica
  KC025      Koprivnica              R4            CO Bjelovar                               Vukovarska b. b. , 43000 Bjelovar
  KC026      Koprivnica              R3            CO Ludbreg                                Koprivnička b. b. , Ludbreg
  KC027      Koprivnica              R4            CO Pošta Varaţdin                         Miškinina bb, 42000 Varaţdin
  KC028      Koprivnica              R3            CO Ivanec                                 Lipovac 32246
  KC029      Koprivnica              R3            CO Otok Virje                             CO Otok Virje, Varaţdinska bb, 42208 Cestica
  KC030      Koprivnica              R3            CO Ţeljeznička postaja Čakovec            Kolodvorska 2, 40000 Čakovec
  OS031        Osijek                R1            CACA Osijek                               Cara Hadrijana 11, 31000 Osijek
  OS032        Osijek                R3            CI Bajakovo                               Lipovac 32246
  OS033        Osijek                R2            CI Donji Miholjac                         Granični prijelaz CI D. Miholjac
  OS034        Osijek                R2            CI Luka DravaOsijek                       Donjodravska Obala 6, 31000 Osijek
  OS035        Osijek                R4            CI Donji Miholjac - robna                 31 540 Donji Miholjac, Granica
  OS036        Osijek                R3            CI Slavonski Šamac                        35 220 Slavonski Šamac
  OS037        Osijek                R3            CI Ţeljeznički kolodvor Slavonski Šamac   35 220 Slavonski Šamac
  OS038        Osijek                R3            CO Ilok I (Ljuba)                         32236 Ilok
  OS039        Osijek                R3            CO Ilok III (Neštin)                      32236 Ilok
  OS040        Osijek                R3            CO Bapska                                 32236 Ilok
  OS041        Osijek                R3            CI Slavonski Šamac - skela (Dubočica)     35 220 Slavonski Šamac, Skela
210                                                                                                                           Section VI. Technical Requirements



            Customs        Site Code
  Site ID                                                        Site Name                                          Address
             House    [See Site(S) Table 1]
  OS042      Osijek            R2             CI Beli Manastir                   Trg Slobode 24, Beli Manastir
  OS043      Osijek            R3             CI Duboševica                      GP Duboševica
  OS044      Osijek            R4             CI Ilok                            Most na Dunavu Ilok-Bačka-Palanka
  OS045      Osijek            R4             CI Luka Drava Osijek               Istočno predgraĎe bb, 31000 Osijek
  OS046      Osijek            R4             CI Pošta Osijek                    Franje Markovića 2, 31000 Osijek
  OS047      Osijek            R4             CI Poţega                          Osiječka ulica 19, 34000 Poţega
                                                                                 Relkovićeva 11, Nova Gradiška (glavni ulaz DI"Stjepan Sekulić" d. d. Nova
  OS048      Osijek            R4             CI Stara Gradiška
                                                                                 Gradiška)
  OS049      Osijek            R3             CI Tovarnik                        Ul J. B. Jelačića b. b. , 32249 Tovarnik
  OS050      Osijek            R4             CI Vinkovci                        Eugena Kvaternika 76, 32100 Vinkovci
  OS051      Osijek            R4             CI Vukovar                         Dunavski prilaz bb, Vukovar
  OS052      Osijek            R4             CI Ţeljeznički kolodvor Osijek     Bartula Kašića b. b. , 31000 Osijek
  OS053      Osijek            R2             CI Ţeljeznički Kolodvor Tovarnik   Ţeljeznički kolodvor Tovarnik, Tovarnik
  OS054      Osijek            R4             CI Ţupanja                         B. Radića bb, Ţupanja
  OS055      Osijek            R3             CO Slavonski Brod                  Naselje "Slavonija I", Sl. Brod i "Đuro Đaković"
  OS056      Osijek            R3             CO Slavonski Brod Most             Šetalište braće Radić, Slavonski Brod
  OS057      Osijek            R3             CO Ţupanja most                    Ţupanja-most
  OS058      Osijek            R3             CI Baranjsko Petrovo Selo          Baranjsko Petrovo Selo
  OS059      Osijek            R3             CI Batina                          Franje Markovića 2, 31000 Osijek
  OS060      Osijek            R3             CI Erdut                           N. Š. Zrinskog b. b. , Erdut
  OS061      Osijek            R3             CI Gunja                           Miroslava Krleţe b. b. , 32260 Gunja
  OS062      Osijek            R3             CI Stara Gradiška                  35435 Stara Gradiška (Most)
Section VI. Technical Requirements                                                                                                             211



             Customs            Site Code
   Site ID                                                            Site Name                                                 Address
              House        [See Site(S) Table 1]
  OS063        Osijek                R2            CI Zračna luka Osijek                     Sv. Leopolda Bogdana Mandića b. b, 31000 Osijek
  OS064        Osijek                R2            CI Ţeljeznički kolodvor Erdut             Kolodvorska b. b. , Erdut
  OS065        Osijek                R3            CI Ţeljeznički kolodvor Gunja             Stari Drenovci 1, 32257 Drenovci
  OS066        Osijek                R3            CO Ilok II (Sot)                          prometnica Ilok-Sot, Šid
  OS067        Osijek                R3            CO Svilaj                                 Svilaj b. b.
  PL068        Ploče                 R1            CACA Ploče                                Trg Kralja Tomislava 26, Ploče
  PL069        Ploče                 R2            CO Ţeljeznički kolodvor i Luka Metković   Obala Neretvanske Kneţevine 1, Metković
  PL070        Ploče                 R3            CI Klek                                   Orah, Vrgorac
  PL071        Ploče                 R3            CI Mali Prolog                            Mali Prolog
  PL072        Ploče                 R3            CI Metković                               Metković
  PL073        Ploče                 R3            CI Vrgorac                                Orah, Vrgorac
  PL074        Ploče                 R3            CO II Gabela I                            Gabela Polje, Ploče
  PU075         Pula                 R1            CACA Pula                                 Riva 10
  PU076         Pula                 R4            CI Labin                                  Kature bb
  PU077         Pula                 R1            CACA Pula                                 Kolodvorska 4
  PU078         Pula                 R4            CI Buje                                   Digitronska 33
  PU079         Pula                 R2            CI Buzet                                  Trg fontana 4
  PU080         Pula                 R3            CI Kaštel                                 GP Kaštel
  PU081         Pula                 R2            CI Luka Pula                              Labinska 38
  PU082         Pula                 R4            CI Pazin                                  Kurelovićeva 20
  PU083         Pula                 R3            CI Plovanija                              GP plovanija
  PU084         Pula                 R2            CI Poreč                                  matije Vlašića 49
212                                                                                                                           Section VI. Technical Requirements



            Customs        Site Code
  Site ID                                                       Site Name                                           Address
             House    [See Site(S) Table 1]
  PU085      Pula              R3             CI Poţane                          CI Poţane, 52420 Buzet, Poţane p. p. 9
  PU086      Pula              R2             CI Rovinj                          Pećine 9
  PU087      Pula              R2             CI Umag                            Vrh b.b.
  PU088      Pula              R4             CO II Slobodna zona Pula           Sv. Polikarpa 8, 52 000 Pula
  PU089      Pula              R2             CI Umag                            Obala Josipa Broza Tita bb
  PU090      Pula              R2             CI Zračna luka Pula                Valtursko polje bb
  PU091      Pula              R2             CI Zračna luka Pula                Riva bb
  PU092      Pula              R2             CO Bršica                          GP Bršica
  PU093      Pula              R4             CO Ţeljeznički kolodvor Lupoglav   CO Ţelj. Kol. Lupoglav, 52426 Lupoglav b. b.
                                                                                 CO Ţelj. Kol. Lupoglav, Putnički promet Buzet- 52420 Buzet-Ţeljeznička
  PU094      Pula              R4             CO Ţeljeznički kolodvor Lupoglav
                                                                                 postaja Buzet
  RI095      Rijeka            R1             CACA Rijeka                        Rijeka, Riva Boduli 9
  RI096      Rijeka            R4             CI Bakar-Škrljevo                  Kukuljanovo b. b. (skladište s6)
  RI097      Rijeka            R2             CI Luka Rijeka                     Rijeka, Senjsko pristanište bb
  RI098      Rijeka            R4             CI Ţeljeznički kolodvor Rijeka     Miroslava Krleţe 4, Srdoči-kamionski terminal
  RI099      Rijeka            R4             CI Gospić                          Gospić, Bilajska b. b.
  RI100      Rijeka            R3             CI Pasjak                          GP Pasjak
  RI101      Rijeka            R2             CI Pošta Rijeka                    Privremena-Antuna Barca 3 c, Rijeka
  RI102      Rijeka            R2             CI Prezid                          Prezid
  RI103      Rijeka            R3             CI Rupa                            GP Rupa
  RI104      Rijeka            R2             CI Zračna Luka Rijeka              Hamec 1, Omišalj
  RI105      Rijeka            R3             CO I Šapjane                       Šapjane b.b., 51 000 Rijeka
Section VI. Technical Requirements                                                                                                 213



             Customs            Site Code
   Site ID                                                           Site Name                                           Address
              House        [See Site(S) Table 1]
  RI106        Rijeka                R4            CI Bakar                          Senjska ulica 165., 51 000 Rijeka
  RI107        Rijeka                R3            CI Brod na Kupi                   Fankopanska b. b. , 51301 Brod na Kupi
  RI108        Rijeka                R2            CI Luka Rijeka                    Luka Rijeka-Ţabica 1
  RI109        Rijeka                R2            CI Luka Rijeka                    Luka Rijeka-Ţabica 2
  RI110        Rijeka                R2            CI Luka Rijeka                    Luka Rijeka-Ţabica 3
  RI111        Rijeka                R2            CI Mali Lošinj                    V. Gortana 7, Mali Lošinj
  RI112        Rijeka                R2            CI Mali Lošinj                    Privlaka b. b. , Mali Lošinj
  RI113        Rijeka                R3            CO Senj                           Obala Kralja Zvonimira 6, Senj
  RI114        Rijeka                R3            CO Ţeljeznički kolodvor Šapjane   Šapjane b. b.
  ST115         Split                R1            CACA Split                        Zrinsko Frankopanska br. 60, Split
  ST116         Split                R4            CI Sjeverna Luka Split            Put Sj. luke b. b. , Split
  ST117         Split                R2            CI Zračna Luka Split              Zr. Luka Kaštela; putnička zgrada
  ST118         Split                R3            CO Kamensko                       21246 Arţano-Kamensko
  ST119         Split                R3            CO Vinjani Donji                  Vinjani Donji
  ST120         Split                R3            CO Vinjani Gornji                 Vinjani Gornji
  ST121         Split                R4            CI Imotski                        Imotski, Glavina
  ST122         Split                R2            CI Luka Split                     gat Sv. Duje, Split
  ST123         Split                R4            CI Pošta Split                    Vinjani Donji
  ST124         Split                R3            CO II Arţano                      21246 Arţano
  ST125         Split                R2            CI Luka Split                     Gat sv. Duje Split
  ŠI126       Šibenik                R1            CACA Šibenik                      obala Hrv. Mornarice 2, Šibenik
  ŠI127       Šibenik                R4            CI Industrijska zona Raţine       ul. Narodnog preporoda 12, Raţine Šibenik
214                                                                                                                               Section VI. Technical Requirements



            Customs           Site Code
  Site ID                                                           Site Name                                           Address
             House       [See Site(S) Table 1]
  ŠI128     Šibenik               R2             CI Knin                             K. Zvonimira 1, Knin
  ŠI129     Šibenik               R3             CO Strmica                          Strmica-granični prijelaz
  ŠI130     Šibenik               R3             CO I Ličko Dugo Polje               Ličko Dugo Polje, 22 000 Šibenik
  ZD131      Zadar                R1             CACA Zadar                          Ivana Brčića 2, Zadar
  ZD132      Zadar                R3             CI Ličko Petrovo Selo               Ličko Petrovo Selo
  ZD133      Zadar                R4             CI Gaţenica                         Gaţenica b. b. , Zadar
  ZD134      Zadar                R2             CO I Zračna Luka Zadar              Zemunik b.b., 23 000 Zadar
  ZG135 Središnji Ured           HQ              Carinska Uprava RH Središnji Ured   Alexandera von Humboldta bb
  ZG136     Zagreb                R4             CI Jankomir                         Jankomir 25
  ZG137     Zagreb                R4             CI Ţitnjak                          Slavonska Avenija b. b. , Zagreb
  ZG138     Zagreb                R3             CI Bregana                          10432 Bregana
  ZG139     Zagreb                R2             CI Glavni Kolodvor Zagreb           Zagreb, Gl. Kolodvor V. peron, ul. Grgura Ninskog
  ZG140     Zagreb                R3             CI Jurovski Brod                    Jurovski Brod b. b.
  ZG141     Zagreb                R4             CI Velesajam                        Zagreb, AV Dubrovnik 11 (ZV Paviljon 9)
  ZG142     Zagreb                R4             CI Zapadni Kolodvor Zagreb          Vodovodna 20a, Zagreb
  ZG143     Zagreb                R2             CI Zračna Luka Zagreb               Pleso b. b. , 10150 Zagreb
  ZG144     Zagreb                R3             CO II Volinja                       Volinja 4a, 44 435 Divoša
  ZG145     Zagreb                R2             CI Zračna Luka Zagreb               Pleso b. b. , 10150 Zagreb
  ZG146     Zagreb                R3             CO Harmica                          Ivana Perkovca 40, Šenkovec
  ZG147     Zagreb                R3             CI Hrvatska Kostajnica              Hrvatska Kostajnica, Most
  ZG148     Zagreb                R3             CO II Dvor na Uni                   Ulica Matice hrvatske b.b., 44 440 Dvor
  ZG149     Zagreb                R3             CI Hrvatska Dubica                  ul. Oluje 95. b. b. Hrvatska Dubica
Section VI. Technical Requirements                                                                                                     215



             Customs            Site Code
   Site ID                                                           Site Name                                               Address
              House        [See Site(S) Table 1]
  ZG150       Zagreb                 R4            CI Jankomir                            Josipa Lončara 8
  ZG151       Zagreb                 R4            CI Karlovac                            Ilovac b. b. , 47000 Karlovac
  ZG152       Zagreb                 R4            CI Krapina                             Ţutnica b. b. , Krapina
  ZG153       Zagreb                 R4            CI Kutina                              Metanska 9, Kutina
  ZG154       Zagreb                 R3            CI Macelj                              Gornji Macelj, pošta Đurmanec
  ZG155       Zagreb                 R2            CI Pošta Zagreb                        Maljevac b. b. , 47222 Cetingrad
  ZG156       Zagreb                 R2            CI Ranţirni KolodvorZagreb             Branimirova 4, Zagreb
  ZG157       Zagreb                 R2            CI Sisak                               Jakuševac 2, Zagreb
  ZG158       Zagreb                 R3            CO Bregana Naselje                     Bregana Naselje
  ZG159       Zagreb                 R2            CO Hum na Sutli                        Hum na Sutli
  ZG160       Zagreb                 R3            CO Lupinjak                            Lupinjak
  ZG161       Zagreb                 R3            CO Razvor                              Razvor bb, 49295 Kumrovec
  ZG162       Zagreb                 R3            CI Maljevac                            Maljevac b. b. , 47222 Cetingrad
  ZG163       Zagreb                 R3            CO Pribanci                            Pribanjci b. b.
  GZ164          -                   R5            GZAOP                                  Paljetkova 18, 10001 Zagreb
  Min165         -                   R6            Ministry of Industry                   Ulica grada Vukovara 78, 10000 Zagreb
  Min166         -                   R6            Ministry of Agriculture and Forestry   Ulica grada Vukovara 78, 10000 Zagreb
216                                                       Section VI. Technical Requirements



E.5 PURCHASER WORKING HOURS TABLE
                         Site Code    Working Hours
                           HQ        Mon-Fri 7:30-15:30
                            R1       Mon-Fri 7:30-15:30
                            R2       Mon-Sun 0:00-24:00
                            R3       Mon-Sun 0:00-24:00
                            R4       Mon-Fri 7:30-15:30
                            R5       Mon-Fri 0:00-24:00
                            R6       Mon-Fri 8:30-16:30
Section VI. Technical Requirements                                        217



E.6 TABLE OF HOLIDAYS AND OTHER NON-WORKING DAYS
                                               Date      Description
                                     January 1            New Year
                                     January 6            Epiphany
                                     April             Easter Monday
                                     May 1               Labour Day
                                     May 30            National Holiday
                                     June 22           National Holiday
                                     August 5          National Holiday
                                     August 15           Assumption
                                     November 1           All Saints
                                     December 25, 26    Christmas Day
218                                                            Section VI. Technical Requirements




              F. REQUIRED FORMAT OF
                  TECHNICAL BIDS

F.1 INFORMING THE BIDDER
      F.1.1 The Bidder shall, before submitting his bid, be informed of the nature and
            scope of the product and services to be submitted. It is expected that the Bidder
            shall:
             Study the Bidding documentation;
             Study all risks and work conditions of the offered IS which can affect the bid,
              available on demand from the Purchaser;
             Furnish a precise and complete bid, so that the offered price covers all costs
              incurred in satisfying conditions from the bidding documentation, as well as
              all else needed to successfully install the system as described in the bidding
              documentation;
             Request additional explanations which will enable submitting a unique and
              complete bid.


F.2 DESCRIPTION OF THE INFORMATION
    TECHNOLOGIES, MATERIALS, OTHER GOODS, AND
    SERVICES
      F.2.1 The Bidder MUST provide detailed descriptions of the essential technical,
            performance, or other relevant characteristics of all key Information
            Technologies, Materials, other Goods, and Services offered in the bid (e.g.,
            version, release). Without providing sufficiently clear details, Bidders run the
            risk of their bids being declared non responsive.
      F.2.2 To assist in the bid evaluation, the detailed descriptions should be organized
            and cross referenced in the same manner as the Bidder’s item-by-item
            commentary on the Technical Requirements described in Section F.3 below.
            All information provided by cross reference MUST, at a minimum, include
            clear titles and page numbers.



F.3 ITEM-BY-ITEM COMMENTARY ON THE TECHNICAL
    REQUIREMENTS
      F.3.1 The Bidder MUST provide an item-by-item commentary on the Purchaser’s
            Technical Requirements, demonstrating the substantial responsiveness of the
            overall design of the System and the individual Information Technologies,
            Services offered to those Requirements.
Section VI. Technical Requirements                                                            219




        F.3.2 In demonstrating the responsiveness of its bid, the Bidders are strongly urged
              to use the Technical Responsiveness Checklist provided in Section G of the
              Technical Requirements. Failure to do so, increases significantly the risk that
              the Bidder’s Technical Bid will be declared technically non responsive. Among
              other things, the checklist should contain explicit cross references to the
              relevant pages in the Bidder’s Technical Bid.



F.4 PRELIMINARY PROJECT PLAN
        F.4.1 The Bidder MUST prepare a Preliminary Project Plan describing, among other
              things, the methods and human and material resources that the Bidder proposes
              to employ in the design, management, coordination, and execution of all its
              responsibilities, if awarded the Contract, as well as the estimated duration and
              completion date for each major activity. The Preliminary Project Plan MUST
              also address the topics and points of emphasis specified in GCC Clause 19 and
              in the Bid Data for ITB Clause 14.2 (c). The Preliminary Project Plan should
              also state the Bidder’s assessment of the major responsibilities of the Purchaser
              and any other involved third parties in System supply and installation, as well
              as the Bidder’s proposed means for coordinating activities by each of the
              involved parties to avoid delays or interference.
        F.4.2 In addition to the topics and points of emphasis, the Preliminary Project Plan
              MUST address:
                       1.    Project Organization and Management Plan;
                       2.    Plan of development of the IT subsystem (ACT);
                       3.    Plan of system integration;
                       4.    Pilot-implementation and adjustment of the subsystem at agreed
                             locations;
                       5.    Pre-commissioning and Operational Acceptance Testing Plan;
                       6.    Delivery and Installation Plan;
                       7.    Training Plan;
                       8.    Task, Time, and Resource Schedules;
                       9.    Support plan.
        F.4.3 The Bidder shall in his bid also suggest all technological solutions relating to:
              File formats and data exchange format with GZAOP;
              Algorithm for implementing analysis and simulations in the ACT;
              Algorithm for implementing solutions for the Tariff calculator in the ACT;
              Solutions for CT publication on the Internet;
              Specification of all needed resources (human and technological to be engaged
               by the CDRC) in order to implement the offered solution.
        F.4.4 The Bidder MUST provide with it’s bid system integration projects for similar
              projects performed in the past. The submitted system integration project
              MUST be in English or Croatian.
220                                                          Section VI. Technical Requirements




F.5 PLATFORM REQUIREMENTS PLAN
      F.5.1 The Bidder MUST in his bid elaborate a Platform Requirements Plan which
            MUST describe on which platform the offered solution (ACT) shall work, with
            special emphasis on required HW, system software, database and required
            network resources(with minimal technical requirements) needed in order that
            the offered ACT development meets all functional and non-functional
            requirements.
      F.5.2 The Bidder MUST describe his proposed solution for (minimal technical
            requirements) implementation of the ACT:
           Needed HW resources;
           Operating system;
           Database;
           Required network resources especially transmission speed;
           Physical and logical topology of the server;
           Data security;
           Data protection;
           Fail safe;
           Maximum system down time.
      F.5.3 The minimal required condition is that in the Customs Directorate physically
            separate development server(s) (for passing the Tariff) from the application
            server(s) (for updating and using), and server(s) for Internet publication.



F.6 COMPUTING HARDWARE SPECIFICATIONS
      The Bidder MUST specify and describe (according to section C.3) the server and
      workstation topology (with minimal technical requirements) needed for the proposed
      development of the ACT to satisfy two groups of users:
           ACT users linked to the CDRC Intranet;
           Mobile users, using the standalone version of ACT.
      The Bidder MUST describe his solution for:
             Physical topology of servers;
             Logical topology of servers;
             Data security;
             Data protection;
             Fail safe;
             Maximum down time.
Section VI. Technical Requirements                                                          221




F.7 SOFTWARE SPECIFICATIONS

F.7.1 SYSTEM SOFTWARE AND SYSTEM-MANAGEMENT UTILITIES (SS&SMU)
        The Bidder MUST specify all additional SS&SMU (which will ensure higher security
        and quality of the offered ACT development) such as:
                 System administration SW;
                 Anti-virus SW;
                 SW for data backup;
                 Maintenance and troubleshooting tools etc;
                 Utility SW;
                 System Management Utilities.

F.7.2 COMMUNICATIONS SOFTWARE
        The Bidder MUST specify if the listed network resources satisfy the communications
        requirements for unhindered work of the offered ACT program solution, and answer
        the following questions:
                 Which minimal bandwidth is needed to satisfy the communications
                  requirements for unhindered work of the offered ACT program solution?
                 What kind of connection is planned for mobile users in Customs?
                 What kind of connection is planned for external users?
                 What kind of protection system shall be used against unauthorized usage of
                  data?

F.7.3 GENERAL-PURPOSE SOFTWARE
        The Bidder MUST specify (but not supply) in his bid all additional SW according to
        section C.4.2 which will ensure higher security and quality of the offered ACT
        development, such as:
                 Programming tools and libraries.

F.7.4 DATABASE SOFTWARE AND SOFTWARE DEVELOPMENT TOOLS
        The Bidder MUST specify and explicitly list (according to section C.4.3) in his bid all
        required modules (including licensing policy) for installation and support of the
        database.



F.8 SERVICE SPECIFICATIONS

F.8.1 TECHNICAL SUPPORT
        The Bidder MUST ensure and quote in his bid the following:
                 Coverage period;
222                                                         Section VI. Technical Requirements




             Response time and problem-resolution performance standards;
             Modes of technical support, such as on-site, on-call, return to warehouse;
             Time of (from-to) providing technical support to the Purchaser on location;
             Locations from which service shall be provided;
             Planned number of employees which will ensure maintenance in the warranty
              period;
             Planned number of telephone lines for providing technical service;
             Response time for problem solution;
             Number, qualifications and experience of support personnel and their time
              availability on location;
             Communication and computer equipment for remote technical support.

F.8.2 WARRANTY SERVICE
      The Bidder MUST provide and state in the bid the following:
             Coverage period;
             Response time and problem-resolution performance standards;
             Modes of warranty service, such as on-site, on-call, return to warehouse;
             Locations from which maintenance shall be provided within the warranty
              period;
             Planned number of employees providing maintenance in the warranty period;
             Number, qualifications and experience of maintenance personnel and their
              time availability on location during the warranty period;
             Time of (from-to) providing technical support in the warranty period;
             Communication and computer equipment for remote maintenance in the
              warranty period.

F.8.3 USER SUPPORT/HOT-LINE
      The Bidder MUST provide and state in the bid the following:
             Coverage period;
             Response time and problem-resolution performance standards;
             Locations from which maintenance shall be provided within the warranty and
              post-warranty period;
             Planned number of employees providing user support;
             Number, qualifications and experience of personnel providing user support
              and their availability;
             Time of (from-to) providing technical support in the warranty and post-
              warranty period.

F.8.4 TECHNICAL ASSISTANCE
      The Bidder MUST provide and state in the bid the following:
Section VI. Technical Requirements                                                             223




                 Coverage period;
                 Response time and problem-resolution performance standards;
                 Anticipated tasks and objectives;
                 Locations from which technical assistance shall be provided within the
                  warranty and post-warranty period;
                 Planned number of employees providing technical assistance;
                 Number, qualifications and experience of personnel providing user support
                  and their availability;
                 Time of (from-to) providing technical assistance in the warranty and post-
                  warranty period;
                 Communication and computer equipment for remote technical support.


F.9 CHANGE ORDER PROCEDURES
        The Bidder MUST describe (according to chapter C.6.5) the metrics and method of
        implementing change order procedure for accepting the Purchaser’s requests for
        changes.



F.10 OTHER NON-IT GOODS
        The Bidder MUST specify (this is a part of the bid ) all non-IT goods needed for
        successful development, installation and implementation of the SW product the ACT
        (if any).
224                                                                Section VI. Technical Requirements




      G. TECHNICAL RESPONSIVENESS
               CHECKLIST

G.1 THE TECHNICAL RESPONSIVENESS CHECKLIST
      Note to Bidders: The following Checklist is provided to help the Bidder organize and
      consistently present its Technical Bid. For each of the following Technical
      Requirements, the Bidder MUST describe how its Technical Bid responds to each
      Requirement. In addition, the Bidder MUST provide cross references to the relevant
      supporting information, if any, included in the bid. The cross reference should identify
      the relevant document(s), page number(s), and paragraph(s). The Technical
      Responsiveness Checklist does not supersede the rest of the Technical Requirements
      (or any other part of the Bidding Documents). If a requirement is not mentioned in the
      Checklist, that does not relieve the Bidder from the responsibility of including
      supporting evidence of compliance with that other requirement in its Technical Bid.
      One- or two-word responses (e.g. “Yes,” “No,” “Will comply,” etc.) are normally not
      sufficient to confirm technical responsiveness with Technical Requirements.


      Require. No. [insert   Requirement:                              [specify:
      number]                                                          Mandatory or
                             [insert: abbreviated description of
                                                                       Preferred]
                             Requirement]
      Bidder’s reasons supporting compliance:


      Bidder’s cross references to supporting information in Technical Bid:




      Table explanations:
              In the column “Requirement” requirements of the system are listed;
              In the column “Related Section” referenced chapters in Section VI are listed;
              In the column “M/P” Mandatory (M) or Preferred (P) requirements of the
               system are listed.
Section VI. Technical Requirements                                                 225




G.2 FUNCTIONAL PERFORMANCE REQUIREMENTS OF
    THE SYSTEM

G.2.1 GENERAL FUNCTIONAL REQUIREMENTS
                             Requirement                        Related Section   M/P
 Multilingual implementation of ACT                                  B.1.1        M
 Intuitive and effective GUI                                         B.1.2        M
 Searching, selecting and filtering                                  B.1.3        M
 “Search/Replace” capabilities                                       B.1.4        M
 Attributes of the CT                                                B.1.5        M
 Saving and export of data                                           B.1.6        M
 Printing data                                                       B.1.7        M
 Access to the ACT and data                                          B.1.8        M


G.2.2 FUNCTIONAL MODULES
                             Requirement                        Related Section   M/P
 Functional modules of the ACT:                                      B.2          M
      1.   Passing the CT                                            B.3.1        M
            Analysis and simulations                               B.3.1.1       M
            Exporting data for GZAOP                               B.3.1.2       M
      2.   Updating the CT                                           B.3.3        M
      3.   Using the CT                                              B.3.2        M
            Findings and Opinions on classification of goods
                                                                    B.3.2.1       M
             within the CT
            Elements of Risk Analysis                              B.3.2.2       M
            List of Goods                                          B.3.2.3       M
            The Tariff Calculator                                  B.3.2.4       M
      4.   CT publication on the Internet                            B.3.4        M



G.3 TECHNICAL REQUIREMENTS OF THE SYSTEM

G.3.1 GENERAL TECHNICAL REQUIREMENTS
                             Requirement                        Related Section   M/P
 Distributed business application                                    C.1.1        M
 Three tiered architecture                                           C.1.1        M
 Minimum 32 bit application                                          C.1.1        M
 Uses an RDBMS                                                       C.1.1        M
226                                                                     Section VI. Technical Requirements




                              Requirement                                Related Section           M/P
 Compatibility with Windows 2000 Professional operating system
                                                                              C.1.1                 M
 or newer
 Optimized for work in low-bandwidth network                                  C.1.1                 M
 Optimized for CDRC network users with permanent dial-up link                 C.1.1                 M
 Standalone version (for CDRC mobile users)                                   C.1.1                 M
 Optimized for 800x600 resolution with minimally 16 bit color                 C.1.1                 M
 Access to the application protected with password system                     C.1.1                 M
 Intuitive "user-friendly" Windows oriented GUI                               C.1.1                 M
 Written in Croatian (with possibility to introduce other languages)          C.1.1                 M
 On-line, context sensitive and tool tip help in Croatian                     C.1.1                 M
 Possibility of printing on different printers (laser, ink-jet, etc.)         C.1.1                 M
 Data export in standard format for office applications                       C.1.1                 M


G.3.2 GENERAL TECHNICAL REQUIREMENTS FOR WEB PUBLISHING
                              Requirement                                Related Section           M/P
 Automatic content generation from the database, without
                                                                              C.1.2                 M
 intervention of DB administrator
 Optimized for minimum fourth generation Web Browsers (MS
                                                                              C.1.2                 M
 Internet Explorer 4.x and Netscape Communicator 4.x)
 User friendly GUI                                                            C.1.2                 M
 Optimized for 800x600 resolution in minimum 16 bit color                     C.1.2                 M
 Support for unspecified number of languages                                  C.1.2                 M
 Possibility of searching the CT and related data                             C.1.2                 M


G.3.3 COMPUTING HARDWARE SPECIFICATIONS
                              Requirement                                Related Section           M/P
 The existing CDRC communication network satisfies the ACT’s
                                                                               C.2                  M
 communication needs


G.3.4 REQUESTS OF THE RDBMS
                              Requirement                                Related Section           M/P
 Assignment of data a procedure rights in the database:                       C.4.3                 M
              Select                                                         C.4.3                 M
              Insert                                                         C.4.3                 M
              Update                                                         C.4.3                 M
              Delete                                                         C.4.3                 M
              Execute                                                        C.4.3                 M
Section VI. Technical Requirements                                                     227




                            Requirement                             Related Section   M/P
 Possibility of usage on different network environments and
 computer platforms (especially compatibility with target Windows        C.4.3        M
 NT platform)
 Control of distributed relational databases                             C.4.3        M
 Referential integrity                                                   C.4.3        M
 Possibility of processing transactions                                  C.4.3        M
 Compatible with SQL standard                                            C.4.3        M
 Cascade delete                                                          C.4.3        M
 Client-Server supported                                                 C.4.3        M
 Sorting in Croatian enabled                                             C.1.3        M
 Data encryption                                                         C.4.3        M
 Compatibility with 4GL development tools specifications                 C.4.3        M
 Support for security, protection and integrity                          C.4.3        M
 Error messages in Croatian                                              C.4.3        M
228                                              Section VI. Technical Requirements




                   H. ATTACHMENTS
H.1 Attachment 1: The Customs Law

H.2 Attachment 2: The Customs Tariff Law

H.3 Attachment 3: Comments on The Customs Tariff

H.4 Attachment 4: The Customs Administration Law

H.5 Attachment 5: Procedures for passing and data sources for the
    customs tariff

H.6 Attachment 6: Organization of the customs directorate of the Republic
    of Croatia

H.7 Attachment 7: Forms and binding opinions concerning classification of
    goods within the customs tariff
Section VI. Technical Requirements                                                                      229




H.1 ATTACHMENT 1: THE CUSTOMS LAW*




   Please note that the following is an unofficial English translation of the original Croatian text and as
    such should be used for purpose of reference only;
   Published in Offical Gazette, 78/99;
   Ammendments 117/99, 73/2000.
Section VI. Technical Requirements         315




H.2 ATTACHMENT 2: THE CUSTOMS TARIFF LAW
316                                                           Section VI. Technical Requirements




      The Customs Tariff Law, together with the current Customs Tariff for 2002 is
      enclosed in electronic form on the CD, at the back of the Bidding documentation.
Section VI. Technical Requirements          317




H.3 ATTACHMENT 3: COMMENTS ON THE CUSTOMS
    TARIFF
318                                                          Section VI. Technical Requirements




      Comments on the Customs Tariff are enclosed in electronic form on the CD, at the
      back of the Bidding documentation.
Section VI. Technical Requirements         319




H.4 ATTACHMENT 4: THE CUSTOMS ADMINISTRATION
    LAW
Section VI. Technical Requirements             359




H.5 ATTACHMENT 5: PROCEDURES FOR PASSING AND
    DATA SOURCES FOR THE CUSTOMS TARIFF
360                           Attachment 5: Procedures for passing and data sources for the customs tariff




H.5.1 PROCEDURE FOR PASSING THE CT
      The Customs Tariff Law, whose integral part is the CT, is passed by the Parliament of
      the RH, and changes and amendments to the CT by the Government of the RH in the
      form of Customs Tariff Regulations, at the latest in November of the current year for
      the next calendar year. The basis for developing the draft Customs Tariff are
      obligations undertaken within the WTO, and other international treaties signed by the
      RH. The draft is prepared by the interested Ministries: Ministry of Finance (i.e.
      Customs Directorate of the RH), Ministry of Industry and Ministry of Agriculture and
      Forestry, with consultations and approval of members of the Customs Tariff
      Commission, from the Ministry of Small and Medium Enterprises, Ministry of
      Shipping, Traffic and Communications, Ministry of Health, Ministry of Environmental
      Protection, State Bureau of Statistics, Croatian Chamber of Industry and Croatian
      Chamber of Commerce.
      When passing a new CT, based on amendments to the existing CT, analyses and
      simulations are performed (based on the international convention on Harmonized
      systems). The analyses and simulations are performed for scientific measurement of
      customs rates, enabling implementation of the state fiscal policy and protection of
      domestic production and market, performed by the interested Ministries, in the part of
      the CT under their jurisdiction.
      The Ministry of Agriculture and Forestry has jurisdiction over customs rates for
      chapters 1 to 24, and the Ministry of Industry for chapters 25 to 97. The Tariff codes
      and nomenclature of goods is under the jurisdiction of the Ministry of Finance, i.e.
      CDRC, for all chapters of the CT.
      After performing analyses and simulations, and consultations with all involved
      subjects, the new draft CT is presented to the CDRC. Each such agreed version (draft)
      CT, is controlled by the CDRC (formally and logically, assigned tariff codes,
      nomenclature assigned and "returned" to the interested Ministries for final approval.
      The final draft is edited by the Customs Directorate and presented to the Government
      for passing. After publication in the Official Gazette (NN) and date of validity, the CT
      is used in Customs proceedings. Only the currently valid CT can be applied, as
      published in NN (http://www.nn.hr). So a crucial element is correctness and
      truthfulness of published data in the NN, because even erroneous published data shall
      be utilized until amendments are published in NN.
      From the above it is clear the CT is passed in the interested Ministries, and unified in
      the CDRC for publishing in the NN.

H.5.2 DATA SOURCES
      Data sources are all documents related to the Customs Tariff. The most important data
      sources for the CT are hereby listed, by groups:

                                    H.5.2.1 Basic data sources
      The basic data source is the Customs Tariff of the RH, as an integral part of the
      Customs Tariff Law. A procedure is underway for including the combined EU CT,
      with the third amended HS, in use as of January 1st 2002.
Attachment 5: Procedures for passing and data sources for the customs tariff                   361




                  H.5.2.2 Data sources which govern use of the Customs Tariff Law
        Data sources governing the application of the Customs Tariff Law govern elements
        connected to goods (for example interested Ministries of the RH rule for which tariff
        numbers which kind of import permit should be procured). These sources include:
                  The Customs Law (see section H.1);
                  Bilateral free trade contracts which the RH has with the EU, EFTA, Slovenia,
                   Macedonia, B&H, Hungary, Czech, Slovakia, Bulgaria, Poland (and others in
                   the future);
                  The Law on VAT;
                  Laws on Special Taxes;
                  Other Laws concerning Customs exemptions;
                  Permits, approvals, findings, documents, confirmations accompanying goods
                   in the Customs procedure:
                    o Import and Export permits (issued by the Ministry of Industry);
                    o Permits for exporting or temporary exporting of goods (issued by the
                        Ministry of Industry);
                    o Permits for import of goods from non-WTO countries (issued by the
                        Ministry of Industry);
                    o Permits for import of military goods for the Croatian Army and Police
                        (issued by the Ministry Defense, i.e. by the Ministry of Interiors);
                    o Permits for import of military goods for further export (issued by the
                        Ministry of Industry with consent of the Ministry of Interiors);
                    o Permits for import of artifacts, collectors items and antiques (issued by
                        the Ministry of Culture);
                    o Permits for the import of transmitters, radars, radio-navigation equipment
                        and remote control radio equipment (issued by the Croatian Institute of
                        Telecommunications);
                    o Approvals for importing of live shells (issued by the Administration for
                        Veterinary and Fishing i.e. by the Ministry of Agriculture and Forestry);
                    o Permits for import of mushrooms, snails, frogs and frog legs (issued by
                        the State Administration for Environmental Protection);
                    o Permits for import of medicines and veterinary medications (issued by
                        the Ministry of Health, i.e. by the Ministry of Agriculture and Forestry);
                    o Permits for import and export of drugs according to the List of dangerous
                        drugs (issued by the Ministry Health);
                    o Permits for import of measuring instruments (issued by the State Bureau
                        for measurements);
                    o Permits for import and export of materials dangerous to the ozone layer,
                        according to the List of materials dangerous to the ozone layer (issued by
                        the Ministry of Industry with a previous opinion of the Ministry of
                        Environmental Protection);
                    o Permits for import and export of materials from the List of Materials
                        from the Convention on prohibition of development, production,
362                           Attachment 5: Procedures for passing and data sources for the customs tariff




                 proliferation and use of chemical weapons and their disposal (issued by
                 the Ministry of Industry);
               o Permits for import based on genealogical certificates (issued by the
                 Ministry of Agriculture and Forestry);
               o Approvals for import or export of waste (issued by the Ministry of
                 Environmental Protection);
               o Certificates of origin (EU).

                 H.5.2.3 Data Sources which Govern Classification of Goods
      For the scope of easier and more precise classification of goods, i.e. passing and use of
      the CT other data sources are also used.
      Sources which facilitate classification of goods (application of the CT) are:
              Translated Notes on the CT (sent by the WCO);
              WCO opinions on classification;
              WCO decisions on classification;
              EU opinions on classification;
              EU decisions on classification;
              EU court decisions on tariffs;
              Findings of the Customs Labs of the CDRC;
              Opinions of the Customs Labs of the CDRC;
              Obligatory opinions issued by professional commissions at CT departments in
               Customs Houses in Zagreb, Rijeka and Split;
              Opinions of the CT Commission (a professional body appointed by the CDRC
               Director) related to classification of goods in the Customs Tariff, for
               resolving disputes in second level administrative proceedings;
              Domestic court rulings related to classification of goods within the CT.

                                   H.5.2.4 Special Data Sources
      Special data sources are:
              Catalogues of the Motor Vehicle Center;
              Stock Exchange bulletins;
              The Internet;
              Registers and codebooks in the Information system of the CDRC;
              Data in the CDRC IS collected from processing of Customs documents.

                                       H.5.2.5 CT Attributes
      All data related to the CT is considered as attributes to the CT. According to meaning,
      these attributes might define use of a Law, elements of risk analysis or are in any other
      way relevant for the Customs proceedings (like country of origin), and are uniquely
      linked to the CT.
Attachment 5: Procedures for passing and data sources for the customs tariff                      363




H.5.3 SUBJECTS OF THE CT
           Subjects are all participants involved in the process of passing, updating, using or
           browsing the CT and all related data sources.
           Subjects that take part in passing the CT should be separated from other CT subjects,
           and they MUST have access to a separate server, located in the CDRC Headquarters,
           which will be connected by network to dislocated servers in the Ministry of Industry
           and Ministry of Agriculture and Forestry. Data between the servers is exchanged by
           data replication. The listed users MUST have read, write and delete rights, as well as
           access to all previous versions of the tariff, with possibility to review changes to the
           CT.
           The subjects who update the tariff MUST have read and write access (to the database)
           because they shall update the CT currently used.
           The subjects who are to use and browse the CT should have read rights.
           The subjects participants in the passing of the CT are hereby listed:
                    Customs Directory of the RH (Headquarters):
                     o Employees of the Service for customs value, customs tariff and analysis
                         and Lab;
                     o Employees of the Department for Customs Tariff and the Customs Lab in
                         the Customs Houses in Zagreb, Rijeka and Split;
                     o Customs employees members of professional bodies, whose work is
                         connected to the CT;
                     o Customs employees in professional services and departments of the
                         Central Office and Customs Houses;
                     o Customs employees in Customs Offices and departments;
                    Ministry of Agriculture and Forestry;
                    Ministry of Industry;
                    Ministry of Finance;
                    Ministry of Small and Medium Enterprises;
                    Ministry of Shipping, Transport and Communications;
                    Ministry of Foreign Affairs;
                    Ministry of Health;
                    Ministry of Environmental Protection;
                    Ministry of Defense;
                    Ministry of Interiors;
                    Ministry of Culture;
                    Croatian Chamber of Industry;
                    Croatian Chamber of Commerce;
                    Croatian Telecommunications Institute;
                    State Administration for Ecology;


    The organizational structure of the CDRC is presented in section H.6.1.
364                    Attachment 5: Procedures for passing and data sources for the customs tariff




         State Bureau of Measurements;
         State Bureau of Statistics;
         Municipal Institute for Automatic Data Processing (GZAOP);
         Brokers Union;
         Importers and Exporters;
         All interested parties (published data related to CT).
Section VI. Technical Requirements          365




H.6 ATTACHMENT 6: ORGANIZATION OF THE CUSTOMS
    DIRECTORATE OF THE REPUBLIC OF CROATIA
366                       Attachment 6: Organization of the customs directorate of the Republic of Croatia




H.6.1 ORGANIZATIONAL STRUCTURE OF THE CDRC
      The Customs Directorate is active in the whole territory of the Republic of Croatia. It
      is organized in such a manner that the Central Office, headed by the Director, with
      help from professional services, coordinates work of 10 regional offices (Customs
      Houses). A Customs House covers a certain geographic region through Customs
      Offices, which are internally organized by departments.
      Customs Houses are organized according to the Central Office, and are therefore
      divided into departments monitoring work of the Customs Offices. Customs
      offices/departments can be of the border or clearance type.
      Employees of the CDRC that use the ACT for entry and updating of data are all
      located in the Central Office (Service for Customs value, tariff, and origin of goods
      and the Customs Lab) and the Department for customs tariff and labs in the Customs
      Houses in Zagreb, Rijeka and Split. All other employees of the CDRC use the ACT for
      using data from the CT and related documents.
      In the Site(s) Table 2 a list of Customs entities is presented, according to Customs
      Houses, with the respective number of employees and nodes on the local network.
      The organizational structure CDRC is as follows:
              CENTRAL OFFICE:
               o Office of the Director;
               o Service for Customs system and application of Customs procedures:
                   Customs system department;
                   Department for application of Customs procedures.
               o Service for Customs value, tariff, origin of goods and Customs Lab:
                  Department for Customs value;
                  Department for Customs tariff;
                  Department for origin of goods;
                  Department of the Central Customs Lab.
               o Service for Customs administration and misdemeanors:
                  Department for Customs administration;
                  Department for Customs misdemeanors;
               o Service for Customs control and prevention of smuggling:
                  Department for prevention of smuggling and investigations;
                  Revisions department;
                  Internal Control department;
                  Reporting department.
               o Service for International Customs Cooperation:
                  Department of International Law;
                  Department of European Integration.
               o Service for Information Systems and Customs Premises:
                  Department for Information Systems;
Attachment 6: Organization of the customs directorate of the Republic of Croatia             367




                       Department for Customs Premises;
                   o Service for Legal, Human Resources and Operations:
                       Financial department;
                       Analysis department;
                       Legal department and Human Resources;
                       Department for Education and Training;
                       Operations department;
                   o Service for Special Taxes:
                       System department of Special Taxes;
                       Department for application of Special Taxes;
                       Department for application of other taxes, trade and hard-currency
                        regulations.
                  CUSTOMS HOUSE:
                   o Directors Office;
                   o Department of customs administration proceedings;
                   o Department of Customs misdemeanors;
                   o Controlling department;
                   o Department for Customs Tariff and Lab;
                   o Revision department;
                   o Department for prevention of smuggling and investigations;
                   o Financial department;
                   o Human Resources and Operations;
                   o Customs Office;
                       Customs departments.
368                            Section VI. Technical Requirements




H.7 ATTACHMENT 7: FORMS AND BINDING OPINIONS
    CONCERNING CLASSIFICATION OF GOODS WITHIN
    THE CUSTOMS TARIFF
Attachment 7: Forms and binding opinions concerning classification of goods within the customs tariff           369




 BINDING OPINION CONCERNING CLASSIFICATION OF GOODS WITHIN THE
                        CUSTOMS TARIFF
Primjerak za korisnika
 1. CARINSKA UPRAVA - STRUČNA KOMISIJA                           2. Broj mišljenja
   (Članak 5. Uredbe o provedbi Carinskog zakona)


 3. Korisnik (naziv i adresa           povjerljivo               4. Datum početka vaţenja


 Napomena                                                        5. Datum i broj zahtjeva
 Sukladno članku 12. stavak 8. Carinskog zakona, mišljenje
 vaţi jednu godinu od dana donošenja, osim u slučajevima
 navedenim u točkama a) i b) navedene odredbe. .


 Korisnik ima pravo ţalbe Carinskoj upravi - Središnjem          6. RasporeĎivanje robe u Carinsku tarifu
 uredu u roku 15 dana od dana dostave mišljenja.



 7. Opis robe




 8. Trgovački naziv i drugi                                                                       povjerljivo




 9. Pravni osnov rasporeĎivanja robe




 10. Mišljenje se izdaje na osnovi sljedećih podataka i materijala,
     koje je podnio podnositelj zahtjeva:


     Opis     •        Prospekti •           Fotografije   •          Uzorci   •     Ostalo   •


     Mjesto                                  Potpis                                  Pečat


     Datum
370            Attachment 7: Forms and binding opinions concerning classification of goods within the customs tariff




 BINDING OPINION CONCERNING CLASSIFICATION OF GOODS WITHIN THE
                        CUSTOMS TARIFF
Primjerak za Carinsku upravu

 1. CARINSKA UPRAVA - STRUČNA KOMISIJA                           2. Broj mišljenja
      (Članak 5. Uredbe o provedbi Carinskog zakona)




 3. Korisnik (naziv i adresa)             povjerljivo            4. Datum početka vaţenja




 Napomena                                                        5. Datum i broj zahtjeva
 Sukladno članku 12. stavak 8. Carinskog zakona, mišljenje
 vaţi jednu godinu od dana donošenja, osim u slučajevima
 navedenim u točkama a) i b) navedene odredbe.


 Korisnik ima pravo ţalbe Carinskoj upravi - Središnjem          6. RasporeĎivanje robe u Carinsku tarifu
 uredu u roku 15 dana od dana dostave mišljenja.




 7. Opis robe




 8. Trgovački naziv i drugi podaci                                                                povjerljivo




 9. Pravni osnov rasporeĎivanja robe




 10. Mišljenje se izdaje na osnovi sljedećih podataka i materijala,
       koje je podnio podnositelj zahtjeva:


       Opis     •       Prospekti •           Fotografije   •         Uzorci   •     Ostalo   •


       Mjesto                                 Potpis                                 Pečat


       Datum
Attachment 7: Forms and binding opinions concerning classification of goods within the customs tariff   371




 11. Dopunske obavijesti:                                12. Broj mišljenja
     Carinska uprava - Središnji ured
     Sluţba za carinsku vrijednost,
     carinsku tarifu, analize i laboratorij,
     Odjel za carinsku tarifu i laboratorijske analize
     Zagreb, Alexandera von Humboldta 4a
                                                         13. Jezik
 telefon:


 telefax:


 14. Ključne riječi:




            ________________________________                    _____________________________


            ________________________________                    _____________________________


            ________________________________                    _____________________________


            ________________________________                    _____________________________


            ________________________________                    _____________________________


            ________________________________                    _____________________________

								
To top