Documente Academic
Documente Profesional
Documente Cultură
Executive Summary
1. Introduction
1
2. Objective of Business Cases and Scenarios Implementation
2
a log report for the Business Cases completed for the day. The log report
captured the implementation process and highlighted any issues arising
and weather the Business Case/s implemented for the day was completed
successfully or otherwise. These reports were shared with all and the
National Orchestrators and team in ASEC to record the issues and resolve
any outstanding issues immediately or after consultation with the relevant
stakeholders. An outcome of this daily reporting is the Jira (software to
track issues, and bugs related to software) report created to capture
issues that needed to be addressed by ACTS Implementation team.
4. Outcome
All the Business Cases (BC) and Business Scenarios (BS) were
implemented as planned. However due some technical challenges some
BCs were no completed and this has been recorded in the Jira report.
These BCs will be completed at a later stage with the installation of a new
version that will take into consideration the issues raised in the current Jira
report.
Main Outcomes
Log Report on the Implementation of Business Cases;
Validation of the processes and procedures;
Identification of bugs in the system;
Identification of process related issues at national level;
Identification of capacity needs at the national level;
Identification of possible network communication issues;
Addressing administrative issues including registration of traders
and redesigning of related documents;
Provided an avenue for participating AMS to familiarize their CA
team on the actual exchange of electronic messages in the ACTS at
the relevant points;
Provided a platform for the participating AMS to test their hardware
installed with the ACTS.
5. Conclusion
3
ACTS. As such, the Business Case and Scenarios implementation is the
first exercise that provided all parties concerned an avenue to test out the
ACTS under their area of responsibility. The outcome and results of the
exercise will be the basis for immediate issue resolution, improvements
and future long term enhancements to the ACTS. These exercises will be
continued if there is a necessity to further validate the system before the
parallel run and the proposed live rollout at a later stage. With the
completion of the Business Case and Scenarios implementation, Phase A
of the Pilot Stage has been successfully completed. The completion of
this stage has also given the confidence to participating AMS to move
forward with the next stage of the pilot.
Full Report
1. Purpose of Document
2. Introduction/Background
4
documentation concurrently and Phase C Live Run of a number of trucks
across borders. All three phases have been designed to validate the
electronic exchange of messages and the agreed processes and
procedures that have been put in place by AMS. Phase A of the pilot will
also be used as a proof of concept to move forward with the other phases
of the pilot stage in the participating ASEAN Member States.
5
3. Description of Phase A Implementation (Approach)
To kick off the Phase A of the Pilot Stage ARISE produced the following
documents to assist the participating AMS to prepare themselves for the
implementation: -
These documents were produced by the ARISE team and was aimed to
provide the information and guidance to operationalise Phase A of the
Pilot Stage. However, these documents remained fluid and were revised
as and when needed based on the situation on the ground during
implementation of the Business Cases/Scenario (BC/S).
6
There was considerable planning and training carried out at ASEC level on
how the BC/S should be implemented efficiently and effectively. This
included training and brainstorming, among ASEC personnel involved, by
the ACTS Implementation team to familiarise with the ACTS modules and
how they interlinked. Training also included familiarisation with the Trader
Portal and the different forms/screens and information that is needed to
complete the trader declarations including the registration of the
Guarantee. The period was also used to review the trader registration
forms based on the requirements of the Trader Registration System. As a
result, the Trader Application Form, Employee/ Declarant Details and
Authorisation Form and Authorisation Letter templates for Authorising
Customs Brokers were revised. Revised documents embedded as follows: -
For the implementation of the BC/S, 21 scenarios were developed with inputs
from participating AMS, covering registration of traders, declaration at point of
departure, procedures at entry and exit office of transit and office of destination.
These scenarios included normal declarations, Authorised Transit Trader (ATT)
declarations, declarations involving control by Customs Authorities, deviations
and claim recovery procedures. These scenarios were combined to form
Business Cases with varying complexities to validate the processes, procedures
and the electronic exchange of messages within the ACTS. The execution of the
BC/S also allowed the team to monitor the exchange of the required messages
and assess whether all the required messages were exchanged. Each Business
Case was run over four sessions giving each participating AMS an opportunity to
be the country of departure, transit and destination. A point to note is that
although for the Live Roll Out phase of the pilot, Malaysia (MY) would only be a
country of transit, however the sessions also provided MY, an avenue to be the
country of Departure, Transit and Departure as such all the relevant messages
were also exchanged between the NTAs. Attached is the table of Business Cases
and Business Scenarios.
7
ACTSPilotBusinessS
cenarios_v0 30with implementation dates as at 5th December.xlsx
From Day 3, the Business cases were implemented as per stated in the attached
schedule. The implementation of a typical BC starts with the submission of a
declaration from ASEC to the Departure AMS to get the ASEAN Reference
Number (ARN). With the ARN a set of guide lines are sent to all the AMS to start
processing the declaration at all points as required by the BC. This is repeated
for each session taking into consideration the variations that occur. A sample of
the guideline for the implementation of BCs is attached for reference.
BC 7 Implementing
Instructions 22nd November 2016 SG Dep.docx
Following this, the ACTS Implementation team keeps track of the movements and
monitors the messages and actions via the NTAs. Based on the flow of the
transit movements, emails are also sent to the relevant AMS prompting them to
continue with the next course of action. The outcome of each BC is recorded by
AMS in the log report shared daily with ASEC and participating AMS. The arising
issues are then recorded in Excel format as attached.
8
ASEAN
BusinessScenarios Draft Final Report Business Cases Implementation clean_SM2.xlsx
System-related Issues that must be rectified are then recorded in a Jira report to
be addressed by the ACTS Implementation team. The ACTS Implementation
team has reported that a new version of the software will be released taking into
consideration the critical issues raised before the parallel run phase. Out of the
21 BCs, the BCs 16,19,20,21 could not be completed as network communication
issues between MY NTA and the NTAs of other participating AMS, prevented the
final discharge of the transit declaration. As at 15 th December the final day of
the BC implementation, the network communication issue was still not resolved.
The BCs that were not completed will be implemented at a later date if time
permits, possibly before the parallel run commences.
9
4. Consolidated Results Business Cases and Scenario Implementation as Per Log Report
5.
C
a
s
e
18. 19.B 20.Successfully 21.Successfully 22.Successfully 23. 24.
1 S completed completed completed
1
25. 26.B 27.Successfully 28.Successfully 29.Successfully 30. 31.
1 S completed completed completed
10
32. 33.B 34.Successfully 35.Successfully 36.Successfully 37.Guarant 40.Jira
ee
1 S completed completed completed register
Registr
ation. ed to
Please
3 address
refer to
comme issues
nt 4
identifie
and 5
of Copy d.
of
Issues
Arising
from
BCs
implem
entatio
n.
38.
39.
41.
11
C
a
s
e
s
(
B
C
)
59. 60.B 61.Suc 62.Sus 63.Suc 64.Succes 65. 66.
3 S ces pen ces sful
sful ded sful
4
67. 68.B 69.Suc 70.Suc 71.Suc 72.Succes 73.TH had issues with re-fixing 74.Issue
4 S ces ces ces sful seals at the transit office. was
sful sful sful resolved
5
75. 76.B 77.Suc 78.Suc 79.Suc 80.Succes 81. 82.
5 C ces ces ces sful
sful sful sful
6
83. 84.B 85.Suc 86.Suc 87.Suc 88.Succes 89. 90.
6 C ces ces ces sful
12
sful sful sful
7
91. 92.B 93.Suc 94.Suc 95.Suc 96.Succes 97. 98.
7 C ces ces ces sful
sful sful sful
8
99. 100. 101. 102. 103. 104. S 105. 106.
8 BC Succes Succes Succes uccessf
9 sful sful sful ul
107. 108. 109. 110. 111. 112. S 113. 114.
8 BC Succes Succes Succes uccessf
1 sful sful sful ul
0
115. 116. 117. 118. 119. 120. S 121. 122.
9 BC Succes Succes Succes uccessf
1 sful sful sful ul
1
123. 124. 125. 126. 127. 128. S 129. SG reported that the 131.
movement final status did not
1 BC Succes Succes Succes uccessf
reflect as Goods Released
1 sful sful sful ul but instead showed Arrived.
2 Even after SG performed a
Status Request, IE018 was
not received
130.
132. 133. 134. 135. 136. 137. S 138. SG requested to 139.
1 BC Succes Succes Succes uccessf release the declaration
13
1 sful sful sful ul automatically if there is no
3 control, after the expiry of the
automatic release time.
140. 141. 142. 143. 144. 145. S 146. 147.
1 BC Succes Succes Succes uccessf
1 sful sful sful ul
4
148. 149. 150. 151. 152. 153. S 154. 155.
1 BC Succes Succes Succes uccessf
1 sful sful sful ul
5
156. 157. 158. 159. 160. 161. U 162. The Declaration 163.
1 BC Unsuc Unsucc Unsuc nsucce Amendment Timer was set to
1 ces essf ces ssful a low period, and it was not
6 sful ul sful possible for ASEC to submit
the amendment of the
declaration in time. Hence as
a result the status of the
movement were set to "Not
Released for Transit".
164. 165. 166. 167. 168. 169. S 170. This MY-SG session was 171. T
1 BC Succes Succes Succes uccessf delayed due to network he ACTS
1 sful sful sful ul connection down. Impleme
7 ntation
Team is
14
working
with
Malaysia
to
resolve
the
Network
issues.
172. 173. 174. 175. 176. 177. U 178. Sessions involving MY 179.
The
1 BC Succes Succes Unsuc nsucce could not be completed as
ACTS
1 sful sful ces ssful their Network Impleme
8 sful communications was not ntation
Team is
working. working
with
Malaysia
to
resolve
the
Network
issues
180. 181. 182. 183. 184. 185. U 186. This business case was 187.
The
1 BC Unsuc Unsucc Unsuc nsucce not completed as the was no
ACTS
1 ces essf ces ssful communication between MYs Impleme
9 sful ul sful and the rest of the ntation
Team is
participating AMS. working
with
15
Malaysia
to
resolve
the
Network
issues
188. 189. 190. 191. 192. 193. U 194. This business case was 195.
Unsuc Unsucc Unsuc nsucce The
1 BC not completed as the was no
ces essf ces ssful ACTS
2 sful ul sful communication between MYs Impleme
0 and the rest of the ntation
Team is
participating AMS. working
with
Malaysia
to
resolve
the
Network
issues
196. 197. 198. 199. 200. 201. U 202. This business case was 203.
Unsuc Unsucc Unsuc nsucce The
1 BC not completed as the was no
ces essf ces ssful ACTS
2 sful ul sful communication between MYs Impleme
1 and the rest of the ntation
Team is
participating AMS. working
with
Malaysia
to
resolve
the
Network
16
issues
204.
17
205. Outcome of Business Cases Implementation
18
o However, implementation of Phase B (Parallel Run) and Phase
C (Live Run of Trucks) of the pilot stage would provide the real
platform for testing the procedures and processes on the
ground.
209.
Identification of capacity needs at the national level
o Implementing phase A of pilot also provided AMS the avenue
to assess the actual need of personnel and the training and
capacity need in implementing future phases.
Identification of possible network communication issues
o Issues related to network and communications problems
amongst NTAs were exposed.
o The ACTS Implementation team is monitoring the situation
and working closely with participating AMS to resolve arising
issues before the next phase of the pilot.
Addressing administrative issues including registration of traders
and redesigning of related documents
o An outcome of Phase A of the pilot was also to look at some of
the administrative forms related to the implementation of
ACTS.
o For the BSs and Scenario implementation the ASEC team has
improved the Trader registration forms to accommodate the
system needs, this is an ongoing process to improve the
delivery of the ACTS.
Provided an avenue for participating AMS to familiarize their CA
team on the actual exchange of electronic messages in the ACTS at
the relevant points
o The connecting of the NTAs and the implementation of BSs
provided the hands on training to manage transit movement
and documentation related to the ACTS.
Provided a platform for the participating AMS to test their hardware
installed with the ACTS
o AMS have invested considerable amount of resources on the
acquisition of hardware and non-ACTS software to run the
ACTS, thus phase A provided the opportunity to ensure that
the hardware and software were well integrated and
19
performed the required functions both at national level and
regional.
210.
20
247. Assistant Director of Customs, Corporate Division, RMCD Head
Quarters.
248.
249. Puteri Farizadatul Norain Zainol
250. Supt. of Customs, uCustoms Project, RMCD Head Quarters.
251.
252. Abid Uzair B. Mohamd Yusof
253. Supt. of Customs, Import Division,
254. Bukit Kayu Hitam Station.
255.
256.
i. Singapore
257.
258. Mr. TEH Thiam Siong (National Orchestrator)
259. Head International Relations
260.
275.
276. Conclusions
277. With the ending of Phase A, it can be concluded that a major part of
the ACTS pilot stage has been completed. This includes the development
and agreement on of the procedures and processes to be used in the
transit movement, development of the software and acquisition of the
required hardware by the AMS. These accomplishments have been
supported by the development of the various procedural manuals for
21
Customs Authority, Transport Authority and the Private Sector including
numerous training and capacity building programmes for all the stake
holders.
278. The outcome of the BCs and Scenario implementation has provided
the necessary foundation to the implementation of Phase B and Phase C of
the ACTS pilot stage. The identified issues will be addressed to improve
the system for the implementation of Phase B and Phase C. Phase B
will kick off with the workshop for the selected stakeholders who will be
participating in the parallel run. This will be followed up with the actual
parallel run with some selected partners, who will use the ACTS along with
their current mode of moving goods across borders. The implementation
of phase C will depend on the signing of the MOU amongst participating
AMS which is still being finalised.
22