Table 8.1
General criteria for required national single window functions (continued)
Requirement
General criteria
Design constraints—client application languages
No constraints other than compatibility with technical infrastructure.
Design constraints—system engineering
•
• Design constraints—system management configuration, version control
•
•
•
The implemented products for the national single window must be underpinned by a published architecture encompassing requirements specification, high level design specification, detailed design specification, technical infrastructure specifications, and implementation specification including message schema, database schema, service schema, source code, and presentation layer definitions. A widely used, commercially available and supported system engineering tool must be the repository for the published architecture. The implemented products for the national single window will be administered through a widely used, commercially available, and supported system management toolset for the configuration tables and reference tables of the software application at various versions, plus the configuration and installation definitions for technical infrastructure components, also at various versions. The system management approach and toolsets will support at least environments for live service at dual redundant sites, a transition-to-live environment for pre-live acceptance testing, system test environment, development environment, and training environment. The architecture will be based on message dissemination and distributed workflows, with the scheduling of any system changes to be negotiated with affected users.
Design constraints—escrow
All system engineering definitions and all system management definitions for all products placed in any environment other than development will also be placed in escrow.
Service requirements—training
• • • •
Training of traders and government agencies will be necessary. Training would be performed as an initial burst and then periodically. Seminar style and small group hands on training would be provided on dedicated training configurations. Web based tutorials would be provided.
Service requirements—support
•
Short term on site support for government agencies is required for initial implementation of any distributed workflow systems. On call support is required for government agencies when any new versions of the services are planned—possibly including changes for type 1 or type 3 distributed workflows, as shown in the technical architecture or assistance, with any necessary changes in type 2 workflows where the government agency has a connected in house system.
•
Service requirements—data conversion
• •
An initial conversion of registered traders and other control information will be required. A switchover plan from the current operational system or systems to the national single window is required (so that no declarations or requests for permits are lost). Conversion is a computerized process for extracting records from an electronic database, manipulating that data as required, and loading it into the national single window data structures.
Service requirements—data take-on
The solution may require data take-on for proper service operation. Take-on is a computerized process for capturing data from various sources, manipulating the data as required, and loading the data into national single window data structures.
Service requirements—warranty, support, and maintenance
•
Help desk, customer service, fix on fail and preventative maintenance for application software and technical infrastructure, and technical advisory services for all users are required.
8
Source: Indonesia National Single Window Preparatory Team. Developing a national single window: implementation issues and considerations
Notes
1. Th is discussion draws on presentations by the author and Gerard McLinden in 2007. 2. The content of this chapter draws from technical assistance work for the Indonesia National Single Window.
B O R D E R M A N A G E M E N T M O D E R N I Z AT I O N
141