Core vocabulary related to single windows and similar platforms
other Linktoparent
Submitted date | Last Update Date | Version | Project Proposal Status | Project Page | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
| Core vocabulary related to single windows and similar platforms |
Project Purpose
Text Area | ||||
---|---|---|---|---|
| ||||
Since the work on Recommendation 33 which set the basis for establishing a single window, multiple computer systems have used the term ‘single window’ to describe their system. However, this brings confusion to the business community when multiple systems in a country claim to be a ‘single window’ resulting in multiple single windows. This is further confused by private sector solutions describing their systems as ‘single windows’ without having received a mandate from the appropriate authorities. A more consistent use of the term ‘single window’ is necessary, and precise definitions of other types of systems should be provided in order to clearly distinguish different types of systems. This project proposes to provide such brief definitions in the form of a white paper which will read as an annex to Recommendation 33 and which could eventually be integrated into a revision of Recommendation 33 when and if this is eventually decided. |
Project Scope
Text Area | ||||
---|---|---|---|---|
| ||||
This project will propose a more precise definition of ‘single window,’ in strict compliance with what has been developed in the UNECE suite of recommendations on single windows (Rec33, 34, 35 and the ongoing work for the future Rec36). This project will propose terms related to Single Window development and working definitions of other types of platforms in order to provide to the government and business community clear, precise definitions. |
Project Deliverables
Text Area | ||||
---|---|---|---|---|
| ||||
The project deliverables are as follows: a) A White Paper on core vocabulary related to single windows and similar platforms |
Exit Criteria
Text Area | ||||
---|---|---|---|---|
| ||||
The exit criteria that will indicate the deliverable has been completed, are specified as below. a) White Paper on core vocabulary related to single windows and similar platforms • Internal and external review logs showing how comments have been addressed. • Final draft of text ready for publication. |
Project Team Membership and Required Functional Expertise
Text Area | ||||
---|---|---|---|---|
| ||||
Membership is open to experts with broad knowledge in the area of trade facilitation and single window systems and their implementation. In addition, Heads of Delegations may invite technical experts from their constituency to participate in the work. Experts are expected to contribute to the work based solely on their expertise and to comply with the UN/CEFACT Code of Conduct and Ethics and the policy on Intellectual Property Rights. |
Head of Delegation Support
Text Area | ||||
---|---|---|---|---|
| ||||
US, FR, IN |
Geographical Focus
Text Area | ||||
---|---|---|---|---|
| ||||
The geographical focus of the project is global. |
Initial Contributions
Text Area | ||||
---|---|---|---|---|
| ||||
Initial contributions include the UNECE Recommendations 33, 34 and 35 as well as the ongoing work on Single Window Interoperability (Proposed Recommendation 36 project). |
Resource Requirements
Text Area | ||||
---|---|---|---|---|
| ||||
Participants in the project shall provide resources for their own participation. The existence and functioning of the project shall not require any additional resources from the UNECE secretariat. The project will be prepared in between Forums, in face-to-face meetings, as feasible, and using conference call facilities (provided by the UNECE secretariat). |
Project Leadership
Text Area | ||||
---|---|---|---|---|
| ||||
Project Leader: Abdoulaye BASSE Lead Editor: Jari SALO Editor: Aleksei BONDARENKO Editor: Lance THOMPSON |
Milestones
DELIVERABLE NAME | Project Inception | Expected Completion Date | Requirements Gathering | Expected Completion Date | Draft Development | Expected Completion Date | Public Review | Expected Completion Date | Project Exit | Expected Completion Date | Publication | Expected Completion Date | Maintenance | Expected Completion Date | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Project Proposal Files
Attachments | ||
---|---|---|
|