RESTRICTED
WORLD TRADE G/MA/IDB/W/2
27February 1997
ORGANIZATION(97-0844)
Committee onMarket Access
SUMMARY REPORT ONTHE STUDY FOR
THE DOWNSIZING OFTHE INTEGRATED DATA BASE
1. BACKGROUND
1. Atthemeeting oftheCommittee onMarket Access of31October 1995, itwasagreed that
theSecretariat undertake astudy onthe"downsizing" oftheIntegrated DataBase(IDB) andthatthe
IDBbemade operational withbasic information ontariffs andimports before broadening itsscope
byincluding non-tariff measures andother types ofrestrictions. Thestudy wastobecarried outby
aconsultant. Subsequently, theSecretariat prepared theterms ofreference andfiveoffers were
evaluated. TheNatsoft-Cambridge Technology Partners company wasselected toundertake thestudy,
which wascarried outduring theperiod of26August 1996 -30January 1997.
2. OBJECTIVES OFTHE STUDY
2. Theterms ofreference identified anumber ofobjectives forthenewIDBthatthestudy should
address. Insummary, these are:
- Simplification oftheIDBin:database design, datapreparation anddissemination formats,
processing, useofandaccess totheinformation andapplications software.
- Improved efficiency andflexibility in:processing submissions, distribution oftheinformation,
software development andadding newtypes ofinformation andprocesses.
- Incorporation ofrecent developments intheinformation technology (IT)industry anduseof
standard third-party software tools where appropriate.
- Management andparticipation ofSecretariat staffinthesoftware development ofthenewIDB
tobeabletoundertake future maintenance anddevelopment; useofexternal resources for
software development where applicable andcost-effective.
- Costreductions resulting fromelimination ofmainframe computer usage forIDBprocessing;
possible useoftheInternational Computing Centre (ICC) services1forthenewplatform if
cost-effective.
1TheICCprovides facilities management andother services forPCandUNIX based systems.G/MA/IDB/W/2
Page2
3. CONTENTS OFTHE STUDY
3. Thestudy wascarried outaccording tothree benchmarks covering thefollowing areas:
Systems Analysis
- Identification ofinformation toberecorded inthenewIDB.
- Analysis ofsubmission preparation, conversion, update anddissemination requirements and
processing forthenewsystem andrecommendations forahigh-level design approach.
Database Design
- Redesign ofthedatabase andinput formats.
Client-server2Platform, Costs andDevelopment Strategies
- Identification andrecommendations for:theclient-server platform fortheproject including
hardware, software development tools, database management system (DBMS); software for
thereplacement offunctionality provided bygeneral-purpose mainframe software inthenew
environment; requirements forandimpact oftheproject ontheexisting hardware andsoftware
infrastructure, theLocal AreaNetwork (LAN), thetelecommunications infrastructure; security
andbackup requirements.
- Staffing andtraining requirements forproject development andmaintenance.
- Provision ofacost/benefit analysis including boththeclient-server infrastructure andstaffing
requirements forproject development andmaintenance.
- Recommendationsforstandardstobeadoptedandestimatesoftimerequiredforimplementation.
- Strategies forproject development, implementation, cutover fromthemainframe andfallback
position.
4. Thestudy comprises around 220pages plusannexes andwillbeavailable shortly onarequest
basis. Thisdocument provides asummary ofthemain conclusions andrecommendations reached in
thestudy.
4. ANALYSIS OFREQUIREMENTS
5. Thestudy concluded thattoserve theobjectives oftheIDB(support ofnegotiations, data
exchange among Members, servicing requests fromMembers andDivisions oftheSecretariat), most
functions provided bythecurrent application systems were required. Broadly defined, these are:
submission preparation, restructuring ofsubmissions, analysis ofsubmissions, validation, correction
ofinvalid data,conversion ofnational codes andnational currency import values, adapting theimport
statistics nomenclature tothetariffnomenclature ofadifferent year, loading thedataintothedatabase,
updating thedatabase anddissemination ofthedataviafilecopies, reports andtheIDBCD-ROM.
2Client-server isacomputational architecture thatinvolves client processes requesting services from server processes.
Typically, theserver processes runonpowerful hardware toincrease performance. Client processes canrunonlesspowerful
machines.G/MA/IDB/W/2
Page3
6. Anumber ofproblems withthecurrent implementation oftheIDBwereidentified. Toagreat
extent, these problems resulted from theinfrastructure ofthecurrent implementation, bothinterms
oftheapplication systems designs andrestrictions imposed bytheuseofthemainframe andthecurrent
DBMS. Theothermajor problem wasthatthevalidation rulesinplaceweredrawn upontheassumption
thatcomplete submissions ofdataintegrated atthetariff linelevelwould bereceived fromMembers.
However, fewMembers provide full,integrated submissions.
7. Recommendations wereprovided toremedy these problems andaredescribed intherelevant
sections below.
5. DATA ELEMENTS TOBERECORDED INTHE NEW IDB
8. Onerequirement ofthestudy wastheidentification ofinformation toberecorded inthenew
IDBbased onthecurrent IDBcontent andnewrequirements resulting fromthecreation oftheWTO.
Thisresulted intherevision ofthecurrent formats ofsome dataelements andtheintroduction ofnew
dataelements inorder toreduce thecomplexity ofprogram logic. These aredescribed intheAnnex.
9. Furthermore, theAnnex identifies theminimum datarequired forthenewIDB. Italsodescribes
thepurpose ofthenon-essential dataelements andthepotential drawbacks ofeliminating them from
thenewIDB. Theelimination ofnon-essential elements would reduce thecomplexity ofbothpreparing
submissions innational capitals anddeveloping thenewIDBapplication systems. However, Members
would needtodetermine whether theirrequirements could besatisfied byonlyrecording theessential
dataelements inthenewIDB.
6. OVERVIEW OFTHE DATABASE DESIGN
10. Itwasoriginally intended thatthemainframe IDBcontain twophysical databases. The"work"
database would serve thepurpose ofupdating. The"user" database would serve thepurpose of
dissemination. Ultimately, theuserdatabase wasnotimplemented owing totimeconstraints during
theUruguay Round oftrade negotiations. Instead, asystem wasdevised whereby IDBinformation
wasmadeavailablebyunloadingandre-formattingfilesfromtheworkdatabase,aftertheywereupdated,
verified and,where necessary, permission wasobtained fortheirrelease. Dissemination requirements
wereserved bygeneral-purpose report andfile-formatting programs, adhocprograms toserve non-
standard requirements andtheIDBCD-ROM.
11. Thestudy recommended thatinthesetting upofthenewIDB, thework anduserdatabases
should befullyimplemented, theprincipal reasons being:
- Security forwork database dataandconsistency fordisseminated datawould beprovided.
Theworkdatabase would beprotected byrestricting access totheSecretariat staffwhoperform
thenecessary updates. Theuserdatabase would beupdated periodically fromtheworkdatabase
andthedatacontained therein would notbesubject toconstant change. Theuserdatabase
datawould bethusmore consistent andprovide astable platform forthedissemination ofdata.
- Adhocdissemination requirements could beaccomplished byusing third-party (standard) query
andreport tools. Thiscould reduce theprogramming effort andwould allow end-users to
perform theirownanalyses. However, situations would presumably arisewhen thequery and
report toolscould notserve certain requirements. Therefore, application programming and
theextraction andmanipulation ofdatawould needtobeavailable ascomplementary tools.G/MA/IDB/W/2
Page4
- Theuserdatabase would beacentral repository fordissemination thatwould include besides
theIDBinformation, packaged application programs andpre-defined query andreport modules.
12. Ideally, tofullyminimize thedatabase complexity, thework anduserdatabase designs would
bethesame. Thiswould bethecaseiftherequirements forupdating anddissemination could be
effectively achieved using thesame structure. While theuserdatabase design isaderivative ofthe
work database design, some information needed tobeadjusted, inorder tomake useofthird-party
tools andtoreduce thecomplexity ofreporting logic. Thiswasmainly duetocomplications inthe
methodology usedforcompiling IDBreports, suchas:
- Defaulting ofcustoms duties
- Theneedtocompute certain values before compiling reports
- Selection ofdatabyshare andrankoftrade
- Complications arising from theuseofthetariff treatment code
- Compiling reports using different trade aggregates
- Simulation reporting during negotiations.G/MA/IDB/W/2
Page5
13. Thestudy identified themaintypes ofdatabase structures andtheircorresponding dataelement
content thatwould existinthenewIDB:
Type ofData Description
Nomenclature Standard (Harmonized System, standard category definitions, etc.)
andreporting country level(customs tariff lines) nomenclature data.
Thedatawould consist ofspecifications ofallnomenclatures inuse,
theirfullycoded content andtherelated multilingual product
descriptions. Additional datasuchasstages ofprocessing, products
ofspecial interest todeveloping countries, would alsobestored at
theappropriate levelforcertain types ofnomenclature (example:
HSnomenclature). Thenomenclature structure would alsoinclude
thefacility toconcord onenomenclature toanother.
Countries andCountry
GroupsStandard (WTO) definitions ofcountries andcountry groups
referenced within theIDBandtheirrelated data(example: WTO
Member indicator).
Quantity Units Standard definitions ofquantity units.
Reporter Reporting countries andinformation relating toindividual
submissions (example: national currency exchange rate,system of
trade).
Reporter 'sTrading
PartnersNational definitions ofcountries andcountry groups andrelated
datausedinreporting countries submissions (example: national
country code, relation afforded byreporting country topartner).
Reporter 'sQuantity
Codes
National definitions ofquantity units usedinreporting countries
submissions andtheircorresponding standard WTO codes.
Tariffs Thenational customs tariffs ofreporting countries.
Imports Theimport statistics ofreporting countries.
Negotiation Duties
 Reporting countries trade negotiation datarelating tobaseand
offered customs duties.
Loose-leaf Schedules3
Reporting countries Loose-leaf schedule ofcommitments.
Quantitative
restrictions3Details ofquantitative restrictions applied byreporting countries.
14. Thedatabase designs forboththework anduserdatabases werebased onthefulldataelement
content ascontained intheAnnex. Should Members agree onrecording onlyessential dataelements
inthenewIDB, thedesigns would beadjusted toeliminate thenon-essential elements.
3While thestudy addressed theareas oftheIDBrelating tocustoms tariffs, product descriptions andimport statistics,
provision wasmade inthedatabase design fortheincorporation ofinformation relating totheLoose-leaf Schedules of
Commi tmentsandnon-tariffmeasur es.However ,theanalysisofdataandprocessi ngrequirement sforthesetypesofinformation
wasnotwithin thescope ofthestudy.G/MA/IDB/W/2
Page6
15. Facilities andfeatures were incorporated inthedesign tofoster flexibility:
- Thedatabase hasbeendesigned interms ofclearly defined structures, allowing fortheeasy
addition ofnewtypes ofinformation, bothattheleveloffilesanddataelements.
- Dataaccess would nolonger belimited topre-programmed processes. Avariety ofreports
could beproduced using third-party query andreport tools.4
- Submission data(imports, tariffs, product descriptions) would bestored independently. For
example, animport submission would notneed tobepresent inthedatabase foratariff
submission tobepresent.
- More thanonesubmission could bestored foragiven yearandreporter. Thus, regular IDB
submissions could bestored separately from submissions relating totrade negotiations.
- Thebasenomenclature (HS1992, HS1996) could bespecified foreachsubmission.
7. APPLICATIONS FOR THE NEW IDB
16. Thedownsizing oftheIDBwould involve theprovision oftheIDBfunctionality onaPC
platform. Thisfunctionality would beimplemented, toalargeextent, bythecreation ofnewPC-based
applications. These applications would provide themeans for:thepreparation andmanipulation of
submission data, theconversion, loading andupdating ofsubmission data, thetransfer ofdatafrom
thework database totheuserdatabase andthedissemination ofdata.
PCSubmission Preparation Applications
17. Thestudy identified several problems withthecurrent IDBregarding submissions byMembers:
- lackofMember submissions,
- theformats, contents andcoverage ofsubmissions,
- incomplete and/or inaccurate submissions,
- deficiencies inthetools inplace forsubmission preparation andformatting.
18. Itwasrecommended thatthenewIDBshould better facilitate thereceipt ofdatafromMembers
byimproving theavailable IDBPCDataEntry software forthepreparation andvalidation ofMembers '
submissions. Better facilities could beprovided tohandle datalacking some agreed-upon contents.
Furthermore,thesubmissionpreparationapplicationshouldincludefeaturestoimportdatafromexternal
files, process import statistics andidentify differences innomenclature.
19. Inorder toimport datafromexternal files,itwasrecommended thatthesubmission preparation
software provide functionality tomanipulate submission datainaflexible, user-friendly manner. In
addition todataentry andupdating functions, some features provided bytheapplication would be:
- Import different types ofnative software formats,
- Import awiderange ofrecord structures,
- Specification andsaving ofinput record structures,
4Thisisachieved byStructured Query Language (SQL) compatibility. AnySQL-compatible software (e.g.MSAccess,
MSExcel, Lotus) could beusedtosubmit aSQLquery toretrieve information from thedatabase. Theretrieved information
would beinthenative format ofthesoftware used toprepare thequery.G/MA/IDB/W/2
Page7
- Import selected elements only,
- Sorting,
- Selection ofsubsets ofrecords forprocessing,
- Mass changes todataelement values foralloraselected range ofrecords,
- Mass copies ofonedataelement value toanother foralloraselected range ofrecords,
- Replication oftariff lineswhere theyarenotsystematically recorded onallrecords,
- Validation ofthedata,
- Various options forviewing andupdating thedata.
Conversion andupdate applications
20. Anumber ofproblems wereidentified withthecurrent implementation oftheIDBregarding
conversion andupdate processing:
- theamount oftimerequired toprocess submissions,
- restrictions andcomplexity imposed bythemainframe DBMS,
- complexity forusers,
- complexity infiledesigns, processing andprogram code,
- complexities owing totheuseofbatch processing,
- stringent verification processes,
- costofprocessing.
21. Thestudy recommended thatthenewIDBshould provide thefunctions ofconversion andupdate
byameans thatistimely, direct andeasytousebycreating anonline application fordatabase updating.
22. Since theapplication would beaPConline function, theproblems relating tobatch processing
andthemainframe DBMS would beresolved. Theproblems ofprocessing timeandcosts, complexity
inapplication software andfilestructures would bereduced. Theapplication would bedeveloped in
aPCprogramming language thatdoesnothavetherestrictions imposed bythatusedinthemainframe
applications.
23. Itwasrecommended thattheIDBvalidation rulesbereviewed, given thatthecurrent validation
processing wasdesigned ontheassumption thatfullintegrated submissions would bereceived from
Members eachyear. Thenewvalidation ruleswould bemore flexible inhandling missing information.
24. Theapplication would provide thefollowing features:
- Source ofData-Theapplication would allow datathataretobethesource ofanupdate to
theIDB, tobeobtained from either theIDBitself orfrom anexternal file.
- Allow SetsofRecords tobeViewed andUpdated ataTime -Theapplication would allow
users toview, compare, manipulate andupdate more thanonerecord atatime.
- DataValidation -Theuserwould havethefacility tovalidate thedatabeing updated atany
time. Arange ofvalidation options would besupplied.
- DataCorrection -Theapplication would provide adirect andvisual means bywhich thedata
could bemodified.G/MA/IDB/W/2
Page8
- Conversion ofNational Codes andImport Values -Theapplication would provide afeature
toconvert national codes toWTO codes andtocalculate import values inUSdollars from
values recorded innational currencies.
- Adapt Imports toaTariff ofaDifferent Year -Theapplication would provide features to
determine differences between thenomenclature ofanimport submission andthatofatariff
submission andtoresolve these differences.
- Database Update -Following modifications tothedata, theuserwould havethechoice to
update thedatabase ortodiscard themodifications.
- Audit Trail-Theapplication would provide anappropriate audittrailtorecord theprocessing
thathadbeenperformed during theconverting, loading andupdating ofsubmissions.
Dissemination application
25. Several problems were identified withthecurrent implementation oftheIDBregarding
dissemination:
- costofprocessing,
- complexity inreporting methodology,
- lackofacentral repository ofapplication programs andfiles,
- lackofquery andreporting tools,
- deficiencies inthemechanisms inplace fordisseminating filecopies andproducing reports.
26. Thestudy recommended thatstandard reports andflexible extraction functions should allbe
included inasingle IDBdissemination application. Thestandard extraction andreport functions would
beanenhanced version ofthatcurrently available ontheIDBCD-ROM (tariff averages, tariff and
trade profiles, etc.). Thiswould alsoinclude multi-reporter processing5andsimulation facilities.
Efficient andflexible report processing would beaddressed inthenewIDBbytheprovision ofan
accessible database withaccompanying flexible end-user query tools. During thepreparation ofthe
study,limitedtestingofthisconceptwascarriedoutusingathird-partyquerytoolandtestfilesstructured
intheformat ofthework database. Theapproach appeared tobefeasible.
External Dissemination ofIDBinformation
27. Inorder todistribute IDBinformation toexternal users (governments andinternational
organizations), itwould benecessary toprovide themwiththedataandapplication software foranalysis.
Thedatawould beextracted fromtheuserdatabase andtheapplication software would beanenhanced
version ofthatcurrently provided bytheIDBCD-ROM. Thestudy identified three options for
distributing IDBdatatoexternal users:
- Distribution ofsoftware anddataonCD-ROM
ThisoptionwouldrequirethephysicaldistributionofaCD-ROMcontainingboththeapplication
software andthedata. Thisisoneofthecurrent distribution means.
5Multi-reporter processing refers totheaggregation ofinformation forgroups ofreporting countries. Thispermits
thecalculation oftariff averages, tariff andtrade profiles, etc.bygeographical regions orbylevelofdevelopment (developed
economies, developing economies, etc).G/MA/IDB/W/2
Page9
However, from theuser'sperspective, thedatawould beupdated lessfrequently, since new
CD-ROMs would bedistributed onlyseveral times ayearandnoteachtimeanewcountry
submission wasavailable.
- Distribution ofSoftware andDatabyInternet (orother means ofremote access)
TheIDBCD-ROMcouldhaveanassociatedInternetwebsite.Authorizeduserscoulddownload
upgrades oftheIDBCD-ROM analysis software anddataasthey become available.
Furthermore, theweb-site could provide up-to-date pre-produced reports. Users would be
suppliedwithauseridentificationcodeandpasswordthatwouldallowaccesstothedownloading
facility. Asimilar function isalready available forthedistribution ofofficial documents using
theWTO 'sInternet website.
Themainadvantageofthisoptionwouldbethatupdateddatawouldbemorefrequentlyavailable
totheuser. However, thedistribution mechanism6might beslow.
- IDBInternet Application
ThisoptionwouldprovideanapplicationwithfunctionalitysimilartotheIDBCD-ROM,directly
onanInternet website. Theapplication would beaccessible bypassword. Theapplication
would bedirectly accessible -nodistribution ortransfer ofdataorsoftware would berequired.
Theuserwould prepare arequest thatwould berouted viatheInternet tothewebsitewhere
theIDBdataandinternet application waslocated. Theapplication would beexecuted onthe
webserver andtheresults oftherequest would beformatted andsentbacktotheuser.
However, theSecretariat would havetoprovide thehardware infrastructure onwhich torun
theapplication7.Furthermore,acomplexpassword-protectedwebsitewouldneedtobedesigned
toinclude end-user application features required forspecifying report criteria andviewing and
printing reports.
28. Thestudy recommended thatthedistribution ofsoftware anddatabyCD-ROM andInternet
beadopted fortheshort tomedium term. However, anIDBInternet application would needtobe
consideredforthefuture.Refertothefollowingsectionunder"InternetApplicationDevelopmentTools"
formore information.
8. SOFTWARE AND HARDWARE INFRASTRUCTURE
29. Thestudy provided recommendations fortheselection ofsoftware development platforms for
thenewIDBPCapplications. Thestudy examined standard/mainstream Windows application
development platforms, report andquery tools andthepotential forIntranet/Internet application
development. Criteria wereestablished ineachareaandtheproducts wererated fortheirsuitability.
6Using theInternet connection supplied bytheSecretariat, itcantakebetween 15and45minutes todownload a2.5
megabyte filefrom random Internet sources. Thevolume oftrade andtariff datafortheIDBismuch larger thanthis,even
when compressed. Therefore, thetimerequired todownload thedataviatheInternet might behours, possibly overnight
forstandard modem users.
7Thismight require veryapowerful processor andcommunications means (routers, lines, etc.), astheapplication would
bedata-access intensive andsimultaneous access totheapplication could cause unmanageable peaks indataaccess andmemory
usage.G/MA/IDB/W/2
Page10
Software Development Platform
30. Thestudy evaluated PowerBuilder, Visual Basic andDelphi andrecommended Powerbuilder
asthesoftware development platform. Powerbuilder wasstrong intheareas ofdatabase access,
productivity andobject-orientation. These would bekeyareas forthedevelopment ofapplications
forthedownsized IDB,astheapplications would beverymuch database-related andshould bedesigned
based onefficient re-usable components.
31. However, other options existforthedevelopment ofclient-server applications, notably client-
server application development (second-generation) CASE8tools. CASE tools were notconsidered
bytheconsulting firmcarrying outthestudy, mainly because ofeither known deficiencies intheir
functioning ortheirhighcost. However, attheendof1996, anewproduct -Texas Instrument s
(TI)Performer came onthemarket. Performer isascaled-down version ofTI'sComposer enterprise
CASE tool. Performer allows thedesign anddevelopment ofentire applications. Thedatabase and
compiled application code(C++) aregenerated directly. Performer iscompatible withSybase, Oracle,
MSSQLServer, Informix, DB2, XDB andODBC-accessible databases. Performer willshortly be
evaluated bytheSecretariat.
32. Performer might provide anefficient andconsistent means ofapplication development. Itwould
allow fullapplications tobecreated without having towrite anysource code. Application maintenance
could bemuch easier anddevelopers would nothavetolearn anewprogramming language.
33. Themain problem withPerformer isthatitisnewtothemarketplace andthecurrent release
doesnotalways work properly. Ifthese problems canbesolved intheshort-term, Performer might
beasuitable application development platform forthenewIDB.
Report andQuery Tools
34. Ofthenumerous report andquery toolscurrently available, threewereidentified asparticularly
appropriate tothedissemination needs ofthenewIDB: Business Objects, Impromptu andPowerplay,
IQObjects andIQVision.
35. Business Objects wasrecommended asitprovides alloftherequired features inasingle product,
allows component objects tobecreated andshared among users, abstracts theusers from SQL9and
provides good security andadministration tools.
36. Besides theabove-mentioned sophisticated report andquery tools, other toolswereidentified
which could fulfilsome dissemination needs ofthedownsized IDB. Microsoft Access could provide
goodquery andextraction facilities. Microsoft Excel could provide goodanalysis features, inparticular
thefacility formulti-dimensional analysis viapivot tables.
Internet Application Development Tools
37. ThestudyrecommendedthatthedevelopmentofanIDBdisseminationapplicationusingInternet
technology should notbeconsidered inthemedium term. According totheconsulting firm, themarket
8Computer-Assisted Software Engineering
9Structured Query LanguageG/MA/IDB/W/2
Page11
ischanging toorapidly andthere arecurrently noproven products forfull-scale application
development10.Furthermore, there isstillconsiderable uncertainty astothelong-term standards that
willemerge.
Database Management System
38. Moving theIDBtoaclient-server environment would require asuitable database management
system (DBMS). Inaddition tomerely operating within thenewenvironment, theDBMS should also
provide broad database accessibility fordevelopment tools andsupport awide range ofthird-party
report andquery tools.
39. Thestudy identified asetofcriteria fortheworkanduserdatabases andprovided acomparative
evaluation ofSybase SQLServer, Microsoft SQLServer, Oracle andInformix Dynamic Server. The
study recommended theuseofSybase astheDBMS forthenewIDB. While other DBMS products
werealsodeemed suitable, thedetermining factor wasthatSybase database administration experience
exists within theSecretariat.
Operating System
40. Thestudy determined thatWindows NTServer would beanappropriate operating system for
thenewIDBandwould allow applications tobedeveloped andrunina32-bit11environment. However,
applications thatareintended forexternal distribution (such asthesubmission preparation application)
would alsoneedtobeproduced in16-bit versions, tosupport external users whohavenotyetmigrated
to32-bit operating systems. Itwasrecommended thattheapplications forexternal distribution be
implemented early inthedevelopment cycle.
Hardware andother requirements
41. Thestudy evaluated theimpact ofthenewIDBontheexisting hardware andsoftware
infrastructure,theLAN,thetelecommunicationsinfrastructure.Recommendationsforhardware,security
andbackup were provided.
42. Besides these recommendations, thesubject oftheultimate location ofthenewIDBwas
evaluated. Concerning theLANandtelecommunications, theimpact ofthedownsizing operation differs
according towhether thenewIDBisphysically located attheWTO orattheICC. Options existfor
providing asimilar service whatever thelocation. Therefore, theissue wasdetermined tobecost.
TheSecretariat isexpecting anevaluation from theICCconcerning thismatter.
9. DEVELOPMENT CONSIDERATIONS
43. Theimplementation ofthenewIDBinvolves therealisation ofseveral distinct projects. The
study provided estimates ofstaffing requirements, thetimerequired tocomplete these projects and
thecosts ofdownsizing.
10Complete Internet applications canbewritten using HTML (Hyper TextMarkup Language), theJavaprogramming
language andCGI(Common Gateway Interface). CGIprograms canbewritten inC,C++, Fortran, PerlorVisual Basic.
According totheconsulting firm, creating Internet applications would becomplex, timeconsuming andcostly. Itwould
bebetter tousehigh-level toolstofacilitate theprocess. Although some suchtoolshaveemerged onthemarket, none have
fully matured.
1132-bit and16-bit concern thearchitecture oftheoperating system. Windows 95andWindows NTare32-bit operating
systems. Windows 3.1andWindows 3.11 are16-bit operating systems.G/MA/IDB/W/2
Page12
Staffing
44. Thestudy identified theroles ofthestaffrequired forthedevelopment ofthenewIDB.
StaffMember Role
Project Manager Administer theproject, provide analytical input andberesponsible for
thehigh-level product definition.
Project Leader Lead project development interms ofday-to-day co-ordination,
determine andimplement standards, co-ordinate technical design and
monitor progress. Theproject leader would alsocarry outanalysis
anddesign.
Analyst Ananalyst would berequired tofulfil theanalysis anddesign phase
ofeachproject. Thisrolewould befulfilled tovarying degrees by
theproject manager, theproject leader, users anddevelopers.
Developers Thedevelopers would perform theprogramming/coding aspects of
eachproject.
Database
AdministratorThedatabase administrator (DBA) would beresponsible forthe
implementation andadministration ofthework anduserdatabases. In
general, theDBA would beresponsible forsecurity, tuning and
support issues. TheDBA would alsoprovide technical support for
dataaccess issues andforthedesign andimplementation ofdatabase
procedures (stored procedures, triggers andrules).
External Expert Astherecommended software development platform anddesign of
large object-oriented applications arenewtomost development staff,
thedevelopment timeandlearning curve could bereduced by
contracting anexternal expert towork withtheIDBdevelopment
teamduring theinitial stages ofdevelopment, andpossibly from time
totimeduring laterstages. Theexternal expert would provide
training andwork witheachmember ofthedevelopment teaminthe
design andprogramming during thefirstproject. Themain roleof
theexternal mentor would betotransfer his/her knowledge tothe
teammembers.
Users Users would berequired towork withthesoftware development team
toprovide analysis anddesign input, design testplans andtoperform
testing.
Network
AdministratorsNetwork Administrators would needtoperform astudy todetermine
theoptimal method ofincorporating thehardware forthedownsized
IDBintothecurrent configuration. Following this,thenecessary
hardware andoperating system software required forthedownsized
IDBwould beinstalled andsupported.G/MA/IDB/W/2
Page13
Projects
45. Thefollowing tableidentifies theprojects thatwould comprise thebroad-level implementation
ofthenewIDB:
Project Description
Database setup Thiswould involve theinstallation oftheDatabase Management System
ontheserver(s), thecreation ofthework anduserdatabases, the
assignment ofsecurity rights andpreliminary tuning. Furthermore, the
performance levels ofthedownsized environment would needtobetested
asearly aspossible. IDBmainframe datawould bereformatted and
loaded intothework database. Then performance testswould becarried
outviaadhocprogramming andavailable report andquery tools (i.e.
Microsoft Access, Microsoft Excel).
Submission preparation TheIDBPCDataEntry application would bere-designed andenhanced
toinclude dataimport andformatting options, theprocessing ofimport
statistics andthematching ofnomenclatures. Thisapplication would be
essential forthereceipt ofquality datafrom Members.
IDBConversion and
UpdateThisapplication would perform conversion, loadandupdate processing
forthework database. Itwould allow fortheimport ofsubmission files,
national reference files(trading partners, country groups, quantity units,
etc.), thedefinition ofglobal codes (countries, country groups, quantity
codes, nomenclature, concordances). Thisapplication would perform all
operations toadd,modify anddelete datawithin thework database.
Database transfer Thedatabase transfer process would transfer andre-format datafrom the
work database totheuserdatabase. Itwould alsoperform validation.
Dissemination Thedissemination application would provide standard dissemination
processing from theuserdatabase. Thiswould include theproduction of
standard reports, fileextractions andreports fornegotiations. Itwould
alsocover theexternal distribution oftheIDBCD-ROM data, software
andpre-processed standard reports viatheInternet. Thedissemination
application could alsoperform simulation processing fornegotiations -
entry ofsimulation data, production ofreports andextraction ofsimulated
data. Facilities fordefinition ofconcordances andtheextraction ofdata
would alsobeprovided.
Report andQuery
ToolsThiswould involve theestablishment, administration andpackaging of
standard queries andreports, query objects, views andquery
methodologies forusers.
Loading Mainframe
IDB DataThisproject would involve thecreation ofsoftware toreformat and
transfer theexisting mainframe datatothenewIDB.
IDBInternet
ApplicationThisproject would involve thecreation ofadissemination application to
provide thefunctionality oftheIDBCD-ROM directly viatheInternet.
Theapplication would allow forthecreation ofstandard reports andthe
extraction ofdatabased onuser-defined selection criteria.G/MA/IDB/W/2
Page14
Time Estimates
46. Thestudy provided initial timeestimates inwork months, forthedownsizing oftheIDB.
Twoestimates were calculated forthecorresponding elapsed time. Thefirstestimate assumes that
noexternal resources areallocated forproject development12.Thesecond estimate assumes thatexternal
resources areprovided13.Theestimated elapsed times werecalculated based ontheanalysis anddesign
being conducted byoneanalyst inlinear sequence, followed bycoding, testing anddeployment being
equally divided among theavailable programmers.
47. TheIDBInternetapplicationwasexcludedfromthetimeestimates,sincethestudyrecommended
thatthisproject bedeferred (refer to"Internet Application Development Tools", above).
Project Analysis/
DesignCoding Testing and
DeploymentTotal
TimeElapsed
Time -
no
external
resourcesElapsed
Time -
external
resources
provided
Work Months
Database Setup 0.25 0.75 1 2 1.1 0.8
Submission
Preparation3.5 7 3 13.5 8.5 6.8
Conversion and
Update3.5 7 3 13.5 8.5 6.8
Database transfer 1.5 3.5 1.5 6.5 4 3.2
Dissemination 5 8.5 3.5 17 11 9
Report andQuery
Tools1.5 N/A 0.5 2 2 2
Loading Mainframe
IDB Data0.5 0.75 0.5 1.75 1.1 0.9
Total 15.75 27.5 13 56.25 36.2 29.5
N.B. When converting theabove timeestimates intowork years, afactor often(3.6years for36.2
months) should beusedrather thanafactor oftwelve, since theestimates donottakeintoaccount
timeforleave andofficial holidays.
12TwoIDBsystems development staffwould carry outrespectively theroles ofproject manager andanalyst. Thelatter
would alsoactasproject technical leader. Thiswould leave twoSecretariat programmers available forcoding, testing and
implementation. However, theSecretariat staffwould notbeworking full-time onthedownsizing, because ofon-going
commitments (see paragraph 49).
13These timeestimates would include anadditional programmer (external) being allocated fortwenty-six months of
project development.G/MA/IDB/W/2
Page15
48. Withrespect totheabove table, itshould benoted thattheestimated elapsed times arecalculated
onaproject byproject basis anddonottakeintoaccount project scheduling considerations, which
could theoretically reduce theimplementation time.
49. However, theabove estimates donotinclude overhead inthedevelopment process. Thiswould
include training, additional timerequired forputting intopractice thenewdevelopment platform and
object-oriented concepts, andtheadditional modifications thatwould berequired oncetheindividual
projects wereimplemented. Alsoexcluded arethesupport ofon-going IDBoperations, theservicing
ofadhocrequests during project development andunforeseen contingencies.
50. Ontheotherhand, theseestimates reflect thetimerequired toprovide allfunctionality described
inprevious sections ofthisdocument. Thiswould exceed theminimum processing thatisrequired
forthenewIDBtobecome operational. Asdescribed under "Strategies forDevelopment and
Implementation" below, thenewIDBcould becarried outinphases, allowing theinitial implementation
tobeaccomplished within ashorter timeframe.
Costs andBenefits
51. Estimates inSwiss francs forthecostsofthedownsizing wereprovided. Theestimates assumed
thatthedownsizing would begin inmid-1997.
Items14Year Total
1997 1998 1999 1999 or200015
Hardware 0 53,270 0 39,501 92,771
Software 30,950 24,082 20,291 25,435 100,758
External IT
Resources117,600 302,400 117,600 0 537,600
Training 7,500 0 0 7,500 15,000
Total 156,050 379,752 137,891 72,436 746,129
52. Taking intoconsideration theannual mainframe operational costs fortheIDB(estimated at
SwF406,000) andtheabove costs ofdownsizing (including theuseofexternal resources), thestudy
estimated thatthenewIDBwould become cost-effective twoyears afterthenewIDBbecame operational
(i.e.fiveyears afterthebeginning ofthedevelopment cycle). Ifnoexternal resources wereallocated,
thedownsizing would become cost-effective around six-months afterthenewIDBbecame operational
(i.e.fouryears afterthebeginning ofthedevelopment cycle).
14Costestimates forsoftware andhardware were based onlocal vendors 'listprices for1997. Itwasassumed that
existing WTO hardware could beusedduring theinitial project development andthatnohardware would bepurchased until
1998. CostestimatesforadditionalITresourcesincludedanexternalexpertforsix-mont hsandexternalprogrammingresources
fortwenty-six months, andwere calculated using theaverage local prevailing rateofSwF800perday.
15Theestimated costs (based on1997 prices) under thiscolumn would beforanadditional database server andsoftware
licenses thatwould berequired asthesizeofthedatabase andnumber ofusers increase. Alsoincluded aretraining costs
forInternet development.G/MA/IDB/W/2
Page16
53. Thestudy identified anumber ofbenefits which could beobtained bydownsizing. The
downsized IDBshould beconsiderably lessexpensive tomaintain thanthemainframe IDB. Preparation
ofIDBsubmissions innational capitals should beeasier withthenewdataformats, coding schemes
andimprovedsubmissionpreparationsoftware.Thenewapplicationswouldbemoreflexibleinhandling
missing information. Thetimerequired forthevarious aspects ofprocessing should beconsiderably
reduced andthenewIDBwould bemorereadily available totheuseraudience. Theflexibility provided
bythenewdesign andPCenvironment would improve theIDB'sability toservice theanalytical needs
ofMembers andtoincorporate future requirements.
Strategies forDevelopment andImplementation
54. Thestudy identified general strategies forthedevelopment andimplementation ofthedownsized
IDB. These strategies concerned theorder inwhich thevarious projects would bedeveloped and
theextent ofthefunctionality thatwould beincluded ineachapplication.
55. Itwasdetermined thatthesubmission preparation application wasanecessary requirement
andshould bedeveloped first. Thestudy recommended thattheapplications relating totheuserdatabase
(except theIDBInternet application) should bedeveloped next. Thus, thedownsized IDBcould become
operational earlier. Thelaststepwould bethedevelopment oftheconversion andupdate application
forthework database.
56. InordertohavethedownsizedIDBoperationalwithinanearliertimeframe,thestudyconcluded
thatitwould benecessary toallocate external resources forthedownsizing andtoreduce theestimated
elapsed development timeofthree years (29.5 elapsed months). Thiscould beachieved intwoways.
Theestimate ofthree years wasbased ononeexternal programmer working fortwenty-six months
ofthedevelopment cycle. Iftwoexternal programmers wereallocated forthirteen months each, the
elapsed timecould befurther reduced, since during partoftheproject development, theexternal
programmers would beworking concurrently. Thiswould notincrease theestimated costsforadditional
ITresources. Secondly, thestudy recommended thatthefunctionality included intheapplications
bereduced. Only thefunctionality required forfuture trade negotiations16would beimplemented in
thefirstphase. Thiswould include facilities to:
- Update reference files(country, national partners, etc.)andconcordances,
- Produce thereports andfileextractions required fornegotiations,
- Process simulations,
- Convert, update andtransfer totheuserdatabase theminimum datarequired fornegotiations.
Byadopting thisapproach, thestudy concluded thatitwould bepossible tocarry outthedownsizing
within twoyears. Oncethebasicsystem wasoperational, theapplications would beenhanced toinclude
additional functionality. Thiscould bedoneusing onlyinternal resources.
57. Given thatthestudy provided onlyinitial timeestimates, theactual development timecould
varyfromthose provided above. Requirements forexternal resources, ifselected asthedesired option,
would bereviewed andifnecessary, adjusted during thedevelopment cycle, inorder tomeetdeadlines.
Ifonlyinternal resources areused, theonlyflexibility toaccount forunforeseen factors would beto
extend thecompletion date. Furthermore, theproject development would needtobegin shortly and
Members would needtotakeadecision regarding thedownsizing asearly aspossible.
16Theapplications would bedesigned toincorporate thefulldatacontent andfunctionality. However theprograms
would belimited tofunctions required fornegotiations. Thiswould include processing forbaseandoffered customs duties,
possibly applied duties, import statistics, product descriptions andcorresponding reference files. Itisassumed thatthedata
content andfunctionality required forfuture negotiations would besimilar totherequirements forprevious negotiations.G/MA/IDB/W/2
Page17
ANNEX
Information toberecorded inthenewIDB
Thefollowing tables describe thedataelement content thatwould beprovided byMembers forthe
newIDB.RefertodocumentIDB/URM/3-"ReferenceManualforthePreparationofIDBSubmissions"
forfurther information onthedataelements.
1.Import Statistics
DataElement Description Essential
Tariff item National tariff itemnumber X
Country code National trading partner country code X
Import treatment Tariff treatment (MFN, GSP, etc.)under which the
product wasimported
Import national value Import value innational currency X
Import primary quantity
unitNational quantity unitusedfortheprimary quantity X
Import primary quantity Import quantity expressed inprimary quantity units X
Import secondary quantity
unitNational quantity unitusedforthesecondary
quantity
Import secondary quantity Import quantity expressed insecondary quantity
units
Remarks:
There arethree elements intheimport submission thatarenotidentified as"essential": thetariff
treatment, thesecondary quantity andthesecondary quantity unit.
Thetariff treatment isacodethatidentifies, foreachtariff line,theimports thatwereadmitted atthe
MFN tariff orwhich benefitted effectively from tariff preferences.
Thetraditional methodology usedinWTO negotiations isbased oncombined imports fromMFN and
GSPorigins (whether admitted atGSPpreferential tariffornot). Theimports fromcountries signatory
toFTAorother contractual preferential arrangements arenotconsidered. Theimport treatment code
istherefore notusedinthestandard IDBanalytical reports. Apparently, veryfewcountries collect
import statistics according tothedutypaidinthedetail ofcustoms tariff lines. Forthose reasons,
theimport treatment codeisnotconsidered asessential atthisstage.
Concerning import quantities, itwould seem thatsome countries havedifficulties inproviding import
quantities and/or quantity unitsintheirIDBsubmissions. Inmany countries, primary quantities are
expressed inagiven unit(e.g.tonsorkilograms) forallproducts andsecondary quantities areexpressed
invarious units. Ifquantity units arenotrecorded inasubmission, itisrelatively easytoaddthe
primary unit,butmuch more time-consuming toaddthesecondary units. Forthatreason, onlyprimary
quantities areconsidered asessential atthisstage.G/MA/IDB/W/2
Page18
2. Tariffs
DataElement Description Essential
Tariff Item National tariff itemnumber X
Tariff ItemSuffix Tariff suffix X
Duty treatment First-level specification oftypeofduty(MFN,
FTA, GSP, etc.)X
Duty type Second-level specification oftypeofduty(MFN
bound duty, MFN applied duty, etc.)X
Duty startdate Dateonwhich thedutycame intoeffect.
Duty enddate Dateonwhich thedutyceased tobeineffect.
Duty available Indicates ifthedutyrateisavailable X
Duty rate Advalorem dutyinpercentage X
Nature Nature ofduty-specific, advalorem, mixed, etc.
Estimation Source ofestimation oftheadvalorem equivalent
oftheduty-reporting country orWTO
AVE calculation method Method ofcalculation oftheadvalorem equivalent
-WTO imports, MFN imports, etc.
Averaging method Method ofcalculation ofthedutyrateforthe
principal itemforatariff linewithsuffixes.
Binding status Binding status ofMFN duties (fully bound, bound
atceiling, bound atdifferent levels, unbound)X
Binding coverage Indicates ifthebinding ofthedutycovers thepart
ofthetariff lineX
Limitation status Indicates iflimitations apply totheduty(e.g.
safeguard measures inagriculture)X
Duty coverage Indicates ifthedutycovers theentire tariff line
Other duty Textual description ofthedutyifitisspecific,
mixed orcompound.X
Duty notes Textual information relating totheduty.
Remarks:
Twonewdataelements havebeenintroduced fortariffs inthenewIDB-thedutytreatment andthe
dutyavailable flag.
Inthecurrent IDB, thedutytypeconsists ofathree-character code. Forexample, thedutytypecode
"01"isusedtoidentify MFN bound duties andthedutytypecode"40"isusedtoidentify GSPduties.
InthenewIDB, thedutytypehasbeenbroken down intotwodataelements. Thedutytreatment isG/MA/IDB/W/2
Page19
equivalent tothefirstcharacter ofthecurrent dutytype("0"forMFN duties, "4"forGSPduties,
etc.). ThedutytypeinthenewIDBrepresents thesecond andthirdcharacter ofthecurrent dutytype.
Since theverification rulesforMFN duties aredifferent fromthose forpreferential duties, theprogram
logic would belesscomplex withtheintroduction ofthedutytreatment.
Thedutyavailable flaghasbeenintroduced toindicate anon-available duty. Inthecurrent IDB, the
value of"999.999" isrecorded inthedutyratetoindicate anon-available duty. Theintroduction of
thisflagwould reduce program complexity.
Thedataelements ofthetariff submissions thatarenotconsidered as"essential," arethose thatare
notrecorded inmost submissions andnotusedinthestandard IDBanalytical reports.
Theperiod ofvalidity ofaduty(duty startdateanddutyenddate) isusedtorecord duties inforce
forpartoftheyearcovered inthetariffsubmission. Theexperience oftheSecretariat hasshown that
when theperiod ofvalidity ofduties isincluded intherecord key,these twoelements aredifficult
toverify andmaintain inthecomputer systems forprocessing thesubmissions, andeven more
complicated tointegrate incomputer analytical programs (calculation ofsimple and/or trade-weighted
averages, distribution intariff profiles, etc.). Itisproposed thatduties applicable onlyduring part
oftheyearberecorded under "ex-items" byusing the"tariff suffix" element.
There would appear tobeproblems inincluding thecodes "nature", "estimation", "AVE calculation
method", "averaging method" and"duty coverage" intariff submissions. Thereason might bethat
thisinformation isnotspecifically indicated inpublished customs tariffs which areoftentheonlysource
usedtoprepare submissions. Since these codes arenotusedinIDBstandard analytical reports, they
arenotconsidered asessential atthisstage.
Theelement "duty notes" isatextual element usedtogivedetails onthedutyoronitsapplication.
Thiselement wasrarely included inpastsubmissions andisnotconsidered asessential atthisstage.
Inthecurrent IDB, specific, mixed andcompound duties canberecorded inanormalized format that
could permit thecomputerized calculation ofadvalorem equivalents. However, fewcountries have
everrecorded specific duties using thenormalized format. Most countries record theirspecific duties
intextual format inthecurrent IDB. Therefore, itisproposed toeliminate thenormalized format
from thenewIDBandtorecord specific duties under thedataelement "other duty".G/MA/IDB/W/2
Page20
3. Product Descriptions
DataElement Description Essential
Tariff item Tariff itemortariff header. X
Tariff suffix Tariff suffix X
Nomenclature level Indicates ifthetariff itemrepresents atariff
heading (towhich nodutyisattached) oratariff
line.X
Language Thelanguage inwhich theproduct description is
provided.X
Product description Description oftheproduct represented bythetariff
itemandtariff suffix combinationX
Remarks:
Inthecurrent IDB, itispossible torecord three setsofproduct descriptions (English, French and
Spanish) foragiven reporter. Thisfeature causes additional complexity inthecomputer programs.
Thecomplexity could bereduced ifonlyprocessing forasingle language version (English, French
orSpanish) perreporter isprovided.G/MA/IDB/W/2
Page21
4. Negotiation Duties
Thisinformation would beusedtorecord baseandoffered duties fortrade negotiations.
DataElement Description Essential
Tariff Item National tariff itemnumber X
Tariff ItemSuffix Tariff suffix X
Basedutyavailable Indicates ifthebasedutyrateisavailable X
Basedutyrate Advalorem basedutyinpercentage X
Basenature Nature ofbaseduty-specific, advalorem, mixed,
etc.
Baseestimation Source ofestimation oftheadvalorem equivalent
ofthebaseduty-reporting country orWTO
BaseAVE calculation
methodMethod ofcalculation ofbasedutyadvalorem
equivalent -WTO imports, MFN imports, etc.
Baseaveraging method Method ofcalculation ofthebasedutyrateforthe
principal itemforatariff linewithsuffixes.
Basebinding status Basedutybinding status. X
Basebinding coverage Indicates ifthebinding ofthebasedutycovers the
entire tariff lineX
Baselimitation status Indicates iflimitations apply tothebaseduty
Basedutycoverage Indicates ifthebasedutycovers theentire tariff
lineX
Baseother duty Textual description ofthebasedutyifitisspecific,
mixed orcompound.X
Basedutynotes Textual information relating tothebaseduty
Offer dutyavailable Indicates iftheoffered dutyrateisavailable X
Offer dutyrate Advalorem offered dutyinpercentage. X
Offer nature Nature ofoffered duty-specific, advalorem,
mixed, etc.
Offer estimation Source ofestimation oftheadvalorem equivalent
oftheoffered duty-reporting country orWTO
Offer AVE calculation
methodMethod ofcalculation ofoffered dutyadvalorem
equivalent -WTO imports, MFN imports, etc.
Offer averaging method Method ofcalculation oftheoffered dutyratefor
theprincipal itemforatariff linewithsuffixes.
Offer binding status Binding status oftheoffered duty. XG/MA/IDB/W/2
Page22
DataElement Description Essential
Offer binding coverage Indicates ifthebinding oftheoffered dutycovers
theentire tariff lineX
Offer limitation status Indicates iftariff limitations apply totheoffered
duty
Offer dutycoverage Indicates iftheoffered dutycovers theentire tariff
lineX
Offer other duty Textual description oftheoffered dutyifitis
specific, mixed orcompound.X
Offer dutynotes Textual information relating totheoffered duty
Remarks:
Most remarks under "tariffs" above, would alsoapply fornegotiations duties.G/MA/IDB/W/2
Page23
5. Reference files
Thisinformation described below would needtobesupplied byreporting countries toestablish the
IDBreference files.
5.1 Reporter Information
DataElement Description Essential
Country code Thecountry supplying thesubmission X
Year Theyeartowhich thesubmission relates X
Submission type Thetypeofsubmission -standard ornegotiation X
Submission sub-type Thetypeofnegotiation submission -agriculture,
sectorial, etc.
Exchange rate Exchange ratebetween imports national currency and
USdollarX
Imports currency unit National currency units inwhich imports are
specifiedX
Currency adjustment
factorAdjustment factor between imports currency unitand
thecurrency unitusedforrecording specific duties.
Duty currency unit National currency unitusedforrecording specific
duties
Duty assessment Basis onwhich duties areassessed (gross weight, net
weight, etc.)
System oftrade System oftrade -general orspecial
Valuation basis Valuation basis ofimport values -c.i.f., f.o.b, etc.
Type ofreference year Fiscal orcalendar year
Documentation language Thelanguage inwhich information isdisseminated to
thereporter
Reporting yearstartdate Startdateofreporting year
Reporting yearenddate Enddateofthereporting year
Submission notes Textual information describing thesubmission
Basenomenclature Nomenclature onwhich thenational nomenclature is
based (e.g.HS92,HS96)
Basenomenclature level Level ofcompliance between national tariff
nomenclature andthebasenomenclature (e.g.HS
four-digit, HSsix-digit)G/MA/IDB/W/2
Page24
5.2 Import Statistics National Partner Countries
DataElement Description Essential
National partner code National codeofeachtrading partner country X
Relation Relation afforded bythereporter tothepartner X
Sub-relation Sub-classification ofrelation forGSPpartners X
Remarks:
Thecoding scheme oftherelation hasbeenrevised inthenewIDBtoinclude anewdataelement -
thesub-relation. Thiswould beusedforGSPandLDC duties. Thesub-relation would provide a
direct logical linktothedutythatwould apply, inabsence ofGSPorLDC preferences. Furthermore,
byrecording LDC duties using dutytype"50", LDC imports could bedirectly linked toLDC duties.
Current IDB relation NewIDBrelation/sub-relation
0=Most-favoured-nation (MFN),
1=Free-trade area(FTA),
2=Zone-zone (trade between preferential
areas),
3=Other preferential agreements,
4=GSP(most-favoured-nation),
5=GSP(other preferences),
6=GSP(general),
8=General,
9=Unspecified.0=Most-favoured-nation (MFN),
1=Free-trade area(FTA),
2=Zone-zone (trade between preferential
areas),
3=Other preferential agreements,
40=GSP(most-favoured-nation),
43=GSP(other preferences),
48=GSP(general),
8=General,
9=Unspecified.
Thefollowing relation codes havebeenadded:
50=LDC (most-favoured-nation),
53=LDC (other preferences),
58=LDC (general).G/MA/IDB/W/2
Page25
5.3 Import Statistics National Quantity Codes
DataElement Description Essential
National Quantity Codes Nationally quantity codes usedinimports
National Quantity Code
DescriptionDescription ofthenational quantity code
5.4 Tariff Partner Countries
Thiswould include information relating tobothindividual countries andgroups ofcountries.
DataElement Description Essential
National Partner Code National codeofeachtariff partner country X
Duty treatment Duty treatment associated withthepartner duty
typeX
Duty type Thedutytypespecific tothepartner andatariff
treatmentX
Trade agreement Textual description oftrade agreement with
partnerX
Remarks:
Fortariffs submissions, thenational partner codeisusedtorecord thecountry coverage ofpreferential
duties. Thenational partner codecould represent anindividual country oragroup ofcountries.
5.5 Tariff Country Groups
Thecountry group composition would berequired forthose tariff submissions containing preferential
duties applicable toagroup ofcountries.
DataElement Description Essential
National Country Group
CodeNational codeofeachtariff andimport partner
groupX
Country group members Thegroup membership ofeachnational partner
country groupX