The applications and information systems are subject to a process of continuous change (new markets, new competitors, business needs, and legal requirements) and this action forces a continuous adaptation of applications and information systems, and this evolution maintains the business of our customers.
From the IT Manager's point of view, that change implies the alignment of some factors which must be controlled, and the success of said control will determine to a great extent the quality of service rendered regarding the needs of the business he supports.
Therefore, we can say that the control of these factors, as well as their alignment, constitutes a strategic factor of competitiveness, since they adjust as soon as possible the applications and the information systems to the business needs. The idea of SWF consists on working over specifications and designs already defined by the customer himself who knows better than anyone his business and from which, by taking advantage of our technological capacities, we carry out only the construction and test stages.
History has proven that when companies undertake internally this type of projects, in many occasions they deal with problems, such as:
• |
Budget appropriation and control to comply with these requirements |
• |
Control of input/output of requests and queries |
• |
Large number of changes and/or cases to be managed or solved (Management of the Claim) |
• |
Attention received or management of internal user’s or customer’s satisfaction |
• |
Collection and elaboration of information for the decision-making process |
• |
Evaluation and follow-up of suppliers |
• |
Commitments made with the user (Estimations/projections, SLAs) |
• |
Compliance with the commitments acquired |
• |
Planning of works |
• |
Personalization of technological support knowledge of the applications |
The SWF immediately allows our customers to develop the project faster reusing to the fullest the existing components and technologies. With SWF it can specifically be obtained:
• |
Software depersonalization |
• |
Scale economies (Cost Reduction) |
• |
Higher level of commitment (Management) |
• |
Removal of collateral circuits of requests |
• |
Checking of request validity |
• |
Unification of requests with similar characteristics |
• |
Removal of concurrent requests |
• |
Classification of requests (Urgency/Sensitivity) |
• |
Identification of area(s) affected |
• |
Establishment of commitments between parties |
• |
Follow-up (process and commitment) |
• |
Communication of closure |
• |
INFORMATION: Who? When? Why? What for? How? How much/many? |
In short, it is intended to improve the current service quality to the users, releasing resources for new developments, depersonalizing the maintenance activity.
|
