Register Your Vehicle

 

1. After waiting for our vehicle for many months, we want it to be registered as soon as possible. We will not blame the vehicle dealer for the months of waiting, but will blame JPJ even for one day delay in registering our vehicle. Therefore, JPJ has to come out with a complete environment of various online systems to make vehicle registration smoother and faster, while protecting the data integrity.
    
   
   
   

2. These various online systems are just to deal with a vehicle’s early life part. There are many more online systems that a vehicle has to deal with in its whole life cycle. Take the current best selling car (Perodua Axia) as an example of vehicle registration using these online systems:
   
   

1. NIK (Nombor Identifikasi Kenderaan – Vehicle Identification Number)
• Perodua as the car manufacturer will send NIK to JPJ to ensure that the Axia when going to be registered later is a genuine Axia manufactured by Perodua.
• Hence, buyer can rest assured that the Axia they bought is not a clone made by some Tom, Dick or Harry at their backyard.
• Note: For imported vehicles, the system is known as NIKi (Nombor Identifikasi Kenderaan Import).
  
  
2. eEksais

• Royal Malaysian Customs Department will send excise duty payment data to ensure that the Axia has already settled its tax.
• Hence, the Government will not be duped by fake customs’ forms anymore and losing millions in tax collection.
• Note: For imported vehicles, Ministry of International Trade and Industry (MITI) will also send approved permit data using eAP system.
  
  

3. eDaftar
• After a buyer confirmed to buy an Axia, Perodua sales dealer will send all car and owner data to JPJ through Perodua’s eDaftar system.
• Therefore, the use of paper form are eliminated and JPJ staffs will not have to key in back all those particulars contained in paper forms anymore.
  
  
4. eInsurans
• Insurance agent or insurance company will send the Axia’s insurance data with open date to JPJ to ensure that the Axia is covered by genuine insurance policy.
• There are three gateways which link all insurance companies to JPJ.
• Therefore, the use of physical insurance cover note is eliminated and JPJ staff will not have to key in back all those particulars contained in the cover note or verify dubious cover note with insurance companies anymore.
• Car owner will not be cheated by paying for fraudulent insurance which is not from insurance companies.
  
  
5. eHakmilik
• After the loan for the Axia has been approved, the bank will send ownership claim data to JPJ.
• There are two gateways which link all banks and financial institutions with JPJ.
• Therefore, JPJ will not have to key in and keep the physical ownership claim letter anymore. Furthermore later, ownership claim can be cancelled at any JPJ branch.
• Banks and financial institutions will not be cheated on ownership cancellation by faking the claim letter. 
  
  
6. ePuspakom

• If the Axia is going to be registered using an interchange registration number, Puspakom will send the other vehicle’s inspection data to JPJ.
• Hence, JPJ will not be duped by fake inspection certificate (usually of non-existent vehicle) and Puspakom will reduce the risk of losing fee collected.
• This system is also used for all types of inspection such as imported vehicles and transfer ownership inspections.
  
  

7. MySikap Registration System
• All above data will be matched automatically upon registration. JPJ will print registration card (grant) and vehicle licence (road tax) immediately.
  
  

3. Therefore, blame vehicle manufacturer/importer and its dealer if you receive your car late :)
   
   

   

Core Problem in Developing MySikap

1. MySikap is JPJ new computer system replacing Sikap. It is the backbone of JPJ Transformation Programme. Now it can be considered as a successful computer system. However, developing MySikap was not a smooth sail.
   
   
2. Normally in developing a computer system, developers will apply systems development life cycle (SDLC) which comprises of five phases which are planning, analysis, design, implementation, and support and security (Vermaat, Sebok, Freund, Campbell, & Frydenberg, 2015).
   
   
    

3. MySikap project was tendered out in 2006 (actually it was named MySikap only in 2012), but only in 2010 the developer was selected. There were many technological and requirement changes during the 4 years gap, even the old Sikap has undergone many changes from 2006 to 2010 to cater for the latest needs. Therefore, JPJ has to redo the analysis phase aka user requirement specification. This phase was largely an exciting phase.
   
   
4. But problems started with the transition from analysis to design phase. Normally for other computer system projects, the business analysts for the two phases are the same people to ensure continuity. However in MySikap project, the business analysts who work in the design phase were not involved in the analysis phase.
   
   
    

5. Looking at the real example above, can you at least design the interface? You just cannot as you were not involved in the analysis phase. 
   
   

According to Vermaat et. al. (2015), “In theory, the five system development phases often appear SEQUENTIALLY”. “In reality, activities within adjacent phases often INTERACT with one another, making system development a dynamic, iterative process”. (Emphasis are mine).

The too sequentially process that did not interact made the business analysts’ knowledge lost in between the analysis and design phase.

6. The business analysts from design phase can always refer to business analysts from analysis phase, but might as well the same business analysts do them. It was only over a year after user requirement specification document was completed that JPJ can first see the interface design, after many interventions.
   
   
7. This is where the problems started that MySikap was not able to meet its various deadlines. Many serious problems later occurred due to rushed implementations.
   
   
    
   (Source: Google Images)
   
   (Source: Google Images)
   
   
   
   (Source: Google Images)
   
   
   
   (Source: Google Images)
8. Meanwhile, Axiata also faced its own problems in its computer transformation programme.
   
   

https://www.digitalnewsasia.com/mobility/axiata-reveals-lessons-learnt-from-bumpy-it-transformation-programme

9. Hopefully with these sharings, nobody either government or private sector will repeat those same mistakes.