|
|
|
In IT lifecycle, company confronts several problems in each stage of IT lifecycle.
We seek and propose the solution for these problems.
Almost all IT companies have one's field of expertise.IT companies would force customer to buy their software because of their sales.
We are not software vendor but consulting company, so we can propose the best solution in every stage of IT lifecycle.

"Planning" is the first of IT lifecycle.It is started before system planning.
We also join to planning with deep understanding for customer's shape of future.

IT investment to obtain company's goal is infinite variety.
As for us, what should be chosen from experience which is talking with a customer directly.
Just forming the plan which suited each customer is called for in a plan.
The environment of the labor force which a customer holds, a fund, and others is original with a customer.
In a plan, we have to take many factors into consideration.
In a template or methodology, it will become the pie in the sky in many cases.
Although we also have methodology, it does not carry out without agreement.
Our system implementation is completed for a short period of time compared with the former.
For example, in ERP package implementation, we choose the optimal system that suited the requirements for a customer. And we do base customization, and are striving to get a customer to use it immediately.
We realize short-term implementation. The cost which a customer pays can be reduced and skill level can be raised over long time.

without the strong request from a customer, we do no development which accompanies the package.
I think a package must be added several options is insufficient as a package.
It is the purpose to strengthen and grow up business.The "completeness" which an introductory vendor investigates has plentifully a case where it ends with minimum.
We understand that it is called for that the route to which a customer utilizes a system, and strengthens and grows up business is shown.
An ERP package may become unnecessary from a planning phase.
Depending on a customer's scale or a request, implementation of only an accounting system may be sufficient.
Almost all, "operations support" is needed after system [ both of systems completed over one year, and systems introduced in three months ] implementation.
With customer's system person's in charge situation, a user's skill level, etc., we examine how much support is required, and propose.
However, since the customer itself uses a system, it is striving to be able to solve a problem by customer itself fundamentally.

In order to be able to master, it must continue using. But advanced usage is difficult from the inside of the beginning which does not get used.
After fundamental usage is become skilled and got used, we advise use an advanced and convenient function.
A fundamental manual is used at first. However, if a customer grows familiar with a system, he will use him in a user friendly manner.
If it uses continuing a system, the portion which does not suit the business model or scale of a company will occur.
In the case of many companies, if it was implemented and years pass, the portion to which maintenance of a system is not careful will occur.
Moreover, business may become complicated and dissatisfaction may come also out of an employee.
It is necessary to check all the business in connection with a system, and an employee's situation before a plan. We do from the check proposal of a system, to the proposal of an improvement.
|
〒105-0001 4-3-20, Toranomon, Minato-ku, Tokyo The 14th floor of the Kamiya town MT building RECS co.,ltd. Tel:+81-03-5450-3581
|
Copyright(C) 2012 RECS Technologies ALL RIGHTS RESERVED.
|
|