Two-year summary

Preface: Working in a company for two years, no work and record and summary (old habits have not changed), must be summed up.

In the company's role:

This company is my third company (there is a company is an internship), as a research and development engineer in the role, during the development, application operations, software maintenance, system three-tier support. Later, due to the expansion of product size (on-line machine reached 5000 units) to the application of operations, software maintenance, three-tier system support mainly. The above is the company's position on me.

Operational normality of application operations:

7x24 hours, the computer does not leave the body (including after work, holidays)

Here are my job responsibilities for specific roles:

First, the application operation and maintenance

1, product launch preparation (including environment deployment, data preparation, data import)

2, Product release (the new version of the application and environment for the requirements of confirmation, testing and re-verification, determine the correct after the upgrade plan and implementation), update the final identified requirements documentation

3, responsible for testing platform, quasi-production platform and production platform consistent deployment and maintenance work;

4, after-line promotion training and maintenance, processing and follow-up

A) application system emergency, problem and service request response, location, tracking, resolution, and statistical summary analysis and management

II) Problem categories have failures, requests, inquiries, new requirements, complaints, if categorized as new requirements, feedback to the project manager, demand analyst, development team

5, responsible for application system availability and performance monitoring (including automatic monitoring and manual monitoring) to ensure the stable operation of the system to ensure that the customer's business is not affected

6, operation maintenance of Knowledge Base update

Includes version update management, requirements documentation updates, issue records and their solution documentation updates

7. Research on operation and maintenance related technologies

8, complete other tasks assigned by the leader.

Understanding of operation and maintenance:

OPS is also a service that aims to emphasize improving

Operation and maintenance process, the most like to do is fault treatment, looking at the problem of a solution, good fun O (^▽^) o

In particular, the above 4 instructions, because the failure to deal with more, it is necessary to summarize, otherwise time spent on repetitive work.

Types of events, we can be divided into: failure, request, consulting, new requirements, complaints, so that can cross-project statistics, each cycle of
The number of each event type. For example, the classification of events: we can be divided into software, hardware, network, database, interface, business.
Need to have an accurate record and positioning, so that you know where the number of problems, at the project level can provide accurate data to make improvements (which module is the most problematic), at the management level, the recorded information will tell you which kind is our operational dimension of the weak point (if the hard disk failure proportion of large, We may change the supplier, or improve the operation of the maintenance personnel in the hard disk repair capacity)

Need time resource records: This part of the data collection is the most difficult, but also the most valuable, and it interacts with the above information analysis, you can know which kind of events spend our most time resources (CMDB), you can know our fault average processing time is how much (event classification), We can also know how much time the new demand will take US resources (the type of event), in addition to the employee-based performance analysis and data statistics of operations and accounting are required based on this part of the information.

Two-year summary