Single Window Systems
In the OIC Member States
22
Elaboration
After the endorsement of the vision document, the preparatory work for is conducted. The
Single Window reflects the particular national institutional and regulatory context. A coy and
paste approach is therefore not possible and the purpose of the preparatory work is to identify
the specific domestic requirements and priorities. Strategic decisions include the technology,
organizational and funding models. The documents that are developed in this phase are a
feasibility study and a strategy document, which may carry many different names such as
Single Master Plan, Roadmap, Blueprint or Strategy.
The feasibility study presents the high level requirements, i.e. the expected changes and
benefits, and presents the different implementation options and their organizational, legal and
financial impacts.
The feasibility study leads to the adoption of a strategy, which outlines and defines the
approach taken by the government at high level. The strategy document defines the objectives,
the high level functionalities of the SW, the organizational model, and the resources required
for the implementation and operation. An action plan and financial plan is a part of the
strategy document. It is useful, but not always common, to also elaborate an IT strategy 13 to
define the possible IT architectural model and patterns of the Single Window strategic design.
Planning
A formal decision commonly kicks off the Single Window implementation project. An entity is
tasked with the implementation and resources are allocated to the project. A project
implementation plan or Master Plan is prepared to plan how strategic goals and objectives will
be achieved, by whom and when, and how.
The Master Plan is “an important management tool to plan, execute, monitor, evaluate and
adjust the project implementation”14. Such a plan identifies the different aspects of the Single
Window project; IT development, legal and institutional changes, training and capacity
building, communication and change management, and deliverables and timeframe for
delivery identified for each of them.
Further documents that are developed in this phase are a project plan, the user and functional
requirements, and technical specifications. The project plan, which can be part of the Master
Plan or a separate document, establishes the project team and defines roles and
responsibilities, budget and resources allocation and use, and risk and risk mitigation
13 The SW IT Strategy defines all possible architectural model that will cover information technology performance, stability
and security; end-user high level workflows and overall productivity; IT management organization and workflows; business
framework costs and expenses and IT management framework costs and expenses.
14 UNESCAP and UNECE, Single Window Planning and Implementation Guide (New York and Geneva: United Nations, 2012)