Business Analysis


Purpose: Analyze your business to fit for your own operation.


Ensuring a smooth installation of the STEP Pro by GAP analysis, of which we have accumulated over 20 years' experience and know-how in order to implement the STEP Pro system efficiently and effectively.


  • Apply TRE default GAP settings in order to minimize time and achieve ease of use.
  • Analyze and organize your operational flow, and produce a report before system installation.
  • Listen closely to customer expectations, and decide whether or not this is achieved by the system.
  • Alternatively, review existing operation for Business Process Re-engineeting (BPR).
  • The results of the analysis, such as operational flow and your company policy, will be provided in written form as a deliverable.


1) Applying a default set pattern makes it is easier for customers to understand how the system analysis work.
2) Analyzes and tidies up your operation; helps you to find and solve existing problems.
3) You can use the results as operating rules. 
(TRE receives good commendation, because it can check operational flow on JSOX.)
4) Customer's operations can even be uniquely customized.
5) Allows us to estimate the customer's implementation workload and draw up an optimized schedule.

The Procedure and Confirmation Features of Gap Analysis

Our best practice for introducing ERP that TRE accumulated for 30 years. We will ensure reliable system operation in a short period of time.

  • Operational Flow Analysis
    Optimize variance between standard operational flow and customer's operatinal flow.
  • Input / Output / Month-end Data Checking
    Find out user-friendly input/output and month-end data.
  • Verification of System Environment
    In order to find out optimum computer running environment, such as hardware, OS or remote communication.
  • Fix Feasible Implementation Schedule
    Fix milestones such as system installatio, training and live-run schedule.

GAP discuss in points

GAP meetings take place for six weeks after signing the contract and consist of two half-day meetings per week.

1. General Information

  • Nature of business
  • Management expectations

2. Operation Flow Analysis

  • Daily, month-end, year-end
  • Operation policy and rules

3. Input Items

  • Master code design
  • numbering rules
  • Input rules

4. Output Items

  • Inquiry
  • Report format

5. Data Consistency Check

  • Confirm month-end cross-check points
  • Confirm parallel run data cross-check points

6. Running Environment

  • Hardware environment
  • OS, OA environment, language
  • Database environment

7. Implementation schedule

  • Project Management
  • Training Curriculum