Wednesday, November 11, 2015

GST Implementation for Malaysia

Localisation – GST Implementation for Malaysia

About Swisslog
Swisslog designs, develops and delivers best-in-class automation solutions for forward-thinking hospitals, warehouses and distribution centers. Swisslog is an inspiring global organization in more than 20 countries on four continents and customers in more than 50 countries. Headquartered in Buchs/Aarau, Switzerland, the Swisslog group is organized in two business areas, Healthcare Solutions (HCS) and Warehouse & Distribution Solutions (WDS). 

GST Malaysia:
The Goods and Services Tax (GST) is a value added tax in Malaysia. GST is levied on most transactions in the production process, but is refunded to all parties in the chain of production other than the final consumer.

GST Implementation challenges:
  • Limited knowledge on Tax codes by business
  • Short duration for GST implementation
  • Migration of master data and transaction data from legacy system (MYOB) to SAP
  • Fulfilling legal compliance
  • Generation of FORM-03
Implementation methodology:
There are 12 work packages in the implementation



  • GST Project plan: Project plan to implement GST.
  • GST Business blueprint: Blueprint covering Tax codes and business scenarios
  • GST Issue tracker: Tracks GST regulation, process and technical issues
  • RMCD inquiry register: Tracks GST inquiries
  • GST IT Blueprint: Blueprint covering the IT process landscape
  • GST OCM: GST change management
  • GST IT Landscape strategy: IT landscape covering interface to RMCD
  • GST Testing strategy: Testing strategy and test coverage
  • GST Master data management: Vendor and Material master maintenance
  • GST RICEFW: GST related forms, reports and interfaces
  • GST Training strategy: Training strategy covering all the stake holders
GST Implementation:
GST Implementation covers organization structure, master data and documents that is affected by the implementation of GST in the SAP system

Organization structure:
  • Company code: Swisslog Malaysia has one active company code in SAP system and the company is located in Kuala Lumpur. The company is not located in Duty-Free Zone or Free Trade Zone or Super Economic Corridor.
  •  Plant code: Swisslog Malaysia has one active plant code.
Master data:
  • General Ledger: The GL accounts are activated and the standard chart of accounts (COA) is being used across the groups. 
  • Customer master data: Around 250 active customer master records and ship to parties are maintained in SAP. There is no interface to/from for customer master records in SAP system. 
  • Vendor master data: Around 250 active customer master records and ship to parties are maintained in SAP. There is no interface to/from for customer master records in SAP system. 
  • Material master data: Approx. 10000 active materials are maintained in SAP. There is no interface to/from for customer master records in SAP system.
Business Process coverage:
GST on Sales and Purchases between Group companies.
  • Import of Services.
  • Bad Debt Relief
  • Credit Memo / Debit Memo processing
  • Rebate Processing
  • Asset Disposal / sales
  • Automatic Calculation of GST expected
  • Customer Down Payment Processing
  • Export Sales for Goods /Services.
  • Free of Charge Sales
  • AP & AR Down Payment
  • Sales with Foreign Currency
  • Third Party Processing.
  • Subcontracting
  • Employee benefits – Loans and Advances
  • Travel claims and reimbursements
Documents:
The below list of documents are affected by GST:
  • Purchase Order
  • Sales order
  • Billing document
  • Accounts receivable – open item
  • Accounts payable – open item
  • External vendor invoice
  • External customer invoice
Reports and Forms:
The below list of forms and reports are required for GST:
  • FORM-03
  • GST Audit File (GAF)

Monday, November 2, 2015

Requirement Insight:How to avoid software requirement chaos

Requirement challenges:

The biggest challenge in the software industry is collecting the requirements. Most of the requirements comes with one line. The customer himself might not be clear on the requirement. The delivery manager will have a lot of pressure to accept the requirement and to make sure the requirement is understood and the application is developed. The pressure percolates to the design and development team and at the end the schedule gets slipped, project cost is increased and poor quality in delivered.

Requirement collection:

Requirements has to be collected like a story writing.Based on the information provided by the  customer the story has to be developed. The story should have the sequences i.e. the business cases, should have a actors i.e. the roles played by each users, should have the screen plays i.e. for each roles the different types of events, should have a good looking i.e. the user interfaces must be very user friendly, characters should know the limitations i.e. constraints of the applications.

The collected requirements should be told as a story like how our Grandma's tell stories during our childhood days. By doing so the customer connects easily on the understanding of the requirement and confirms the understanding.

Requirement documentation:

Different tools are available to document the requirement. There should be a clear categorization of requirements and each requirements have to be documented with properly tagged along with meaningful numbers. This tagging will help to do a complete traceability so that at any given point of the time it can be traced back if it is missed in any of the phases during the project.

Last but not least requirement collection and requirement documentation is an art. The perfection will be achieved only by writing and practicing.

Saturday, September 19, 2015

Cultural challenges in ERP rollouts

Change Management Challenges in ERP rollout:

Change management is a key area when it goes for ERP roll-out especially SAP roll-outs. The business organisation will be working totally in a legacy way and all of sudden if they want to move SAP then lots of resistance will be coming from the end user or key user community. How to overcome this challenge will be interesting. Below are some of the approaches which could give some results.

Approach:

Strong leadership qualities:
General human tendency is to resist if there is any change in the current practice. User community will put of pressure back to rollout team in non accepting the processes, not cooperating with rollout team to do testing and validating etc. Spread negative vibe to other regions and make life complicated for the rollout team.

Here the situation leadership qualities are very much required. Change manager must understand the dynamics of the situations and encourage the user community to get participate in the journey. There should be many awareness programs organised to make user community in understanding of the benefits of the new process and system. Regular campaigns to be organised to strengthen to connect to the user community. Wherever required the change manager must take strong decision for the benefit of the project.

Cultural understanding:
Cultural understanding is must as the team will be comprises of different region, language, countries etc. There should be a ice break sessions or project initiation and acceleration workshops to be organised. These workshops will be break the initial hiccups and makes the way for understanding of each other. This gives avenues for the rollout team on how to come with the strategy during the rollout period.


Winning the heart of key users:
Winning the heart of key users is possible if the rollout team really mingles with the user community. The approach must be applying so more soft skill approach. There should be a fine balancing required between the technical and soft skills.  

Sunday, September 13, 2015

Challenges in Mass Transportation System

Background:

Most of the cities in India has grown in an unimaginable growth over the last 20 years. More or more peoples are migrating from rural areas to urban areas due to better job opportunity. and improved life style. Because of this there is lot of movement happening between the peoples.

Problem:

Challenge 1: Poor quality of roads
The quality of the roads are of poor quality due to which the vehicles has to move slow. An average a person has to waste 2 to 3 hrs average every day.

Challenge 2: Narrow roads
Because a sudden growth most of the arterial roads are narrow where as the vehicles are more. The ratio between the road capacity and vehicles is very high where traffic congestion is more/high.

Challenge 3: No driver discipline
There is a big cultural challenge with drivers. Lane discipline is not followed in many of the circumstances. This lead to lots of chaos in the roads.

Solutions:

The quality of the roads have to be increased. High quality standard to be set so that the contractor strictly follows the high standards. If there are any quality compromises then Govt must ensure that the standards are followed and practiced

There should be a good coordination across the different Govt. departments. This ensures loss in translation and gives better results.

Govt should implement good traffic management system to ensure smooth movements in the road. There should be a clear demarcation of medians, platforms and traffic signals for smooth movements.

Lane discipline should be followed as habit by everyone so that the accidents are avoided and human injuries or lives are saved.



Saturday, September 12, 2015

Parking Chaos and Solutions In India

Background:

After opening up new economy policies in India in 1991 more or more investments started coming up in India which lead to change in the life style of middle class. More or more middle class were moved from middle class to upper middle class in the layer. The purchasing capacity has been increased for these so called upper middle and the passenger car sales between 1991 and 2015 has been increased by more than 100%. This is good for the country's economic growth on the other hand it had also created challenges in the areas of traffic congestion and parking congestion.

Problems:

The metropolitan cities Chennai, Delhi, Kolkatta, Mumbai, Bangalore and Hyderabad has a huge challenge in controlling and monitoring the traffic congestion and parking congestion due to the fact of narrow roads and in efficient traffic management system. This lead to an average of 1.5 to 2 hrs every day during peak hours (7:30 AM to 10:30 AM and 5:00 PM and 8:00 PM) one has to spend/waste time.

Most of the cities are not equipped with good parking system in place and they park the vehicles in the side of the road where they create a traffic congestion till it is parked. This has lead to lot of stress to both drivers as well the traffic police men.

Solutions:

To overcome the situations there should be an efficient parking system by involving sensors with good data analytic. The solution is that parking bay should be equipped with sensor which is integrated to the central system. When the vehicle is parked in/out in the bay the details are captured and stored in the system. This gives information to the central system on the availability. This information can be shared to a Mobile app or can be displayed in some of the hot spots where the drivers can find where the parking space is available.