How to write the specifications?

In the development of China Telecom, various norms and standards have been formed. Some of these norms have a history of history and some have become a joke. There are no specific rules in the compiling process of the specifications. You may wish to discuss them if you have many experiences, lessons, and gains when writing the specifications. I personally have some experience and experience on how operators organize and formulate standards. I will first throw a brick for your criticism.

Standardized Positioning

Some netizens on the Internet vote and ask which operator has the best standards. Someone will immediately ask what is a good standard. The benevolent sees benevolence and the wise sees wisdom. I understand it literally as follows: the rule is a rule, and the model is a model. The so-called good norms are based on operability and forward-looking standards.

The fundamental purpose of a standard is to unify the implementation standards. Therefore, I think the primary criterion for evaluating a standard is its implementation. If the final construction result of the system is very different from that of a standard, it does not serve the purpose specified. On the surface, this problem is about the relationship between planning and execution. But in fact, it is very important to fully consider the feasibility during the compilation of specifications. In fact, there are indeed many reasons why the regulations are not well executed, that is, there is no way to implement them, rather than not wanting to implement them. Therefore, the quality of the evaluation criterion should first be determined by the degree of consistency between the criterion and the final system. If no one can implement the criterion, then the value can be imagined. Specifications and planning are different. The plan is made out, which gives the speaker a lot of space to play. The same set of PPT is told by different people. Although the general direction is not wrong, differences in comprehension, content, and other aspects will lead to a very large difference in results. But the specifications are different. The understanding of the specifications must be unified. What is not defined in the specification is the space for readers and implementers to play, but if defined, there must be no ambiguity.

If the system construction can be consistent with the specifications, and the purpose of the provision is achieved, the quality of the evaluation standards depends on the "fan", or whether the "fan" evaluation can be implemented. The forward-looking nature of a specification is the core value of a standard in addition to unified thinking. It should be said that the compilation of each specification is a result of the painstaking efforts of many experts and industry insiders, and is the crystallization of technological progress and ideological development. If there is a lack of foresight, it cannot set targets and directions for development and play a guiding role. Therefore, this specification can only be referred to as standards, but cannot be a model for future construction.

During the planning, design, and construction of telecommunication networks, many standards are "translations", which are based on foreign standards and suggestions. After translation, after discussion, gradually develop national and enterprise standards. Due to the special nature of the business support network, it is difficult to find similar standards and blueprints overseas. Especially for Chinese operators, the construction of business support systems is more difficult. Therefore, in many cases, we can only develop business support systems "independently and independently.

Writing standards is also completing a project. Therefore, we should organize the compilation of standards in the way of project management. At the initial stage of standardization establishment, it is necessary to clarify the purpose of standardization and the scope of its application. The purpose of standardized formulation is to clarify the time progress and milestones of standardized formulation, and to determine the problems required by standardized formulation, so as to ensure that, within the established time, all resources should be concentrated on solving the most important problems, avoiding the problems of various people, scattered themes, nonsense, and lack of center in the standardized formulation process. It is further necessary to clarify the standardized application scope and the planned application time period. The construction and upgrade of the system is a process in which the system is continuously improved and never stopped. Therefore, the standard life cycle is clearly defined, enable the enterprise plan and finance department to work with the IT department to develop an important basis for investment planning and fund Preparation Planning, so as to strengthen inter-department communication and reduce departmental friction, avoid embarrassment. This is actually an important step for the IT department to establish authority in the minds of other strong departments of the enterprise. It is also necessary to narrow down the differences, clarify the subject, and obtain operable results as soon as possible.

The positioning of norms is sometimes made clear before the Organization norms are compiled, or before the resources are put in place. Such standards are often less difficult to be compiled. There are also many standards, it is not clear before the compiler is in place. This requires the organizer and creator of the specification to discuss the positioning of the Specification. Especially in the latter case, it is often the most difficult question for everyone to solve during the compilation of large-scale norms: leaders only raise large frameworks and strategic objectives, but what is the target? How can we understand the positioning of standards? At this time, if the standardized organizer does not fulfill its obligations and does not unify the goals of the team and the expectations of the leaders, then it is easy to see unclear normative positioning and inconsistent ideas, or locate the problem that has changed, and the fate of the rule is at stake.

After a long time, he summarized the importance of standardized positioning. From a macro perspective, operability and foresight are the basic points of standardization. From a micro perspective, defining the purpose and scope of standardization is the foundation for project success or failure.

Formulation of specifications

1. Learning

The first stage of standardized compilation is the learning process. The organizer should first clarify the positioning and overall work arrangements of this standard, and then organize everyone to invest in standardized compilation. Everyone makes full use of the conditions. Of course, the organizer is also obligated to create conditions for the comrades involved in the compilation of regulations to learn and improve their technical and business capabilities. There are usually two ways to learn: one is to share documents, that is, to provide a sharing server, requiring you to put relevant information and documents for your learning; the other is organizational communication. Whether the speaker is an original manufacturer, integrator, or operator, everyone aims to present their experiences and research results to the project team, and then deepen their understanding through communication. This kind of learning opportunity is very rare. Although there are many people involved in the front and back of every standard writing, it is often the most beneficial to the project team.

2. Discussion

The next stage is the discussion, which is also the most exciting part in the process of standardized writing. Many classic ideas, ideas, and ideas are emerging, formed, and mature in the collision of this stage. However, this stage is also the most difficult to control. How difficult is it? Just like our posts on this forum, the topic often refers to one meaning, but it becomes another topic. At this time, the operator, the project team lead, and other core members should play a role. There are two things to be done: one is to control the scope of the discussion and keep the focus of the discussion focused on the most valuable goals; the second is the determination. When appropriate, the system makes a judgment when listening to a large number of opinions and ends the discussion.

This stage is the most difficult, and it is also the best time to reflect the dominant capabilities of operators. China Mobile is able to take the initiative in system planning and development because it can control the situation at this stage. Whether it is the choice of core technologies or the definition and interpretation of business problems, we need to quickly make judgments based on the discussion, the basis for making judgments is often the grasp of the system, understanding of the technology, and self-confidence. On the other hand, in fact, many questions do not necessarily have absolute right or wrong, but after we make judgments, we can stop endless discussions.

3. enrich content

At the end of the discussion stage, content enrichment is just physical activity. As long as the writers pass through the level of text, they basically do not need to exercise a great deal of attention. But at this time, be careful with the unification of text styles. A more effective solution to this problem is the cross-check and General Compilation responsibility system, which is necessary for text checks.

The most difficult chapter to write about norms is the general principles. Many people only read this chapter when reading the norms. Therefore, the quality and logical thinking of this chapter must be ensured. When I presided over the compilation of specifications, this chapter basically needs to be discussed by the leaders and written by the best people.

As other chapters, the quality can be lower, but good standards must be consistent with the style of each chapter. This often requires the team lead to grasp and reflects the overall strength of the project team.

4. Publicity

The last point is publicity. In fact, the best propagandist is a partner who participated in the compilation of regulations. During communication between provincial companies, the core ideas and the understanding and suggestions of their own companies will be provided to customers; another company will do the same. If your partners participate in the compilation of specifications, the unified part of their handouts is your specifications. In this way, the provincial company often receives more people, has a deeper understanding, and has a more comprehensive perspective, which is much better than the publicity Effect of Headquarters organizations. Therefore, for operators, the partner is both a standard participant and a propagandist, which is of great help to improve execution.

Therefore, for standardized organizers, the main task is in the early stage. After clarifying the positioning, selecting the core team, setting up the outline, and finalizing the general rules, the rest is to make a decision. For the team members involved in the standardized compilation, they must first keep their ideas consistent with the standardized organizer, and then release their energy and knowledge according to the division of labor and their positioning, and is upgraded during the release process.

Standardized skills

1. Communication

The biggest difficulty in standardized writing is to maintain communication between people. Because the writers come from different organizations such as the group headquarters, provincial companies, integrators, product manufacturers, and design institutes, they represent different interests. To some extent, they are only the spokespersons of the company, because there are still many people behind them, and this kind of coordination work is very complicated. In addition, many times, there have been conflicts between organizations from which the standard writers come from. It is critical to keep everyone's discussion right. If the writers cannot unite, the results can be imagined. Therefore, maintaining team unity is an important guarantee for the successful completion of the regulations. If the writing work lasts for a long time, this problem can be well solved. When it is closed, it gets along with each other. Generally, the relationship is easy to solve. However, if it takes a short time, you have to drink to solve this problem, the next day, my family was like a family.

Another issue worth attention is the construction of core teams, especially the selection of team leaders. The leader plays a decisive role in the standardized compilation process. They have strong technical and organizational skills, good job, strict quality control, and a high level of passing through the standard model. The selection of the team lead is usually an excellent part of the discussion, but in general, the best combination is the partner's team lead, and the deputy team lead is the representative of the operator, in this way, if the partner does not say anything about the table, the effect will be better for the operator. In addition, it is best for the team leader to select those who have experience in standardized writing and have more exchanges at ordinary times to improve the communication efficiency. At ordinary times, the team leader takes the independent work of the team members and holds a meeting at night to discuss major issues. This work mode is very effective, which not only improves the efficiency, but also ensures the overall standardization.

2. Logistics Support

The formulation of regulations requires adequate logistical support, including selection of appropriate personnel, locations conducive to closed discussions, funding, and support for office equipment and conference rooms. The Holy Land set up by China Mobile is located in China Mobile's training center. It mainly focuses on the closed environment and several meeting rooms with different specifications, which facilitates communication in various ways, or intense or elegant, you can choose different environments based on the communication needs.

Of course, I believe that regular comrades have been compiled at the Xiaotangshan training center and should keep good memories of an affordable and unique diet, everyone once worried about the problem of "Let's continue with the development of weight", not to mention the wild hot pot in the nearby "lecture village.

We have considered establishing a more complete environment for standardized compilation, and even preparing specialized computers, so that we can achieve better confidentiality. It seems that China Telecom has done this first.

3. Incentive Measures

To encourage and unite the persons involved in the formulation of the specifications, a small nameplate can be issued to them after the formulation is completed. This small nameplate can be a proud and powerful tool for finding better job opportunities, from which excellent dispatching engineers actively participate in the formulation of specifications. We usually send a thank-you letter to the organization that participates in the compilation of the specifications. Both partners and provincial companies will be proud to be able to get standards and praise from group companies.

Normative feedback and revision

No specification can be made seamless, and no specification can take all the situations into account. Therefore, from the first day of its birth, we must consider its constant updates and improvements, by the end of its lifecycle, corresponding technical means and organizational forms are required. There may be two methods for revision. One is review and minor revision of the specification according to the comment of the review team; the other is to issue a draft for soliciting opinions, then, revise and adjust the specifications based on relevant feedback, and issue a formal version.

We have not properly resolved the problem of Business Support Network specification revision. There are many reasons. For example, the specification requires system construction for verification, but the system construction period is long and it is difficult to carry out testing and verification. However, I think there are two subjective reasons: First, after the compilation of the specifications, everyone is busy with their work. It is because the integrator's personnel have already invested in the fight for making orders, so they have no time to take care of them, the operator has either invested in the compilation of new specifications, but has to focus on publicizing the specifications. It is rare that the operator will spend time and energy on the revision of the specifications; another reason is that the standardized life cycle management awareness is relatively weak and there is no closed-loop management. It is often because the standard has been released to complete the task and relevant work has ended. Unless there is a major problem and it needs to be revised in a supplemental document, the subsequent version will be the "decree" and will not be changed. Therefore, if we want to take the standard compilation process to a new level, the issue of feedback, revision, and upgrade deserves your attention.

Lin is always talking about things, because many things are some of our experiences during our work, and may lack organization and logic. In other words, there is no rule for the compilation of specifications. Many experiences are self-developed and not necessarily correct. As the business support network is moving towards standardization, I believe that the compilation of norms will gradually mature and form a relatively fixed model. By then, we may only need to enter information in a fixed mode, the specification is automatically generated. However, because there is no framework constraint, everyone's creativity has been maximized. Although there are some shortcomings in every compilation of specifications, the good memories of that time will always be with us. I would like to take this opportunity to sincerely thank the comrades who have worked with me to develop specifications. China Mobile will not forget you.

This article from: http://www.cww.net.cn/article/article.asp? Id = 27091 & bid = 651

In the development of China Telecom, various norms and standards have been formed. Some of these norms have a history of history and some have become a joke. There are no specific rules in the compiling process of the specifications. You may wish to discuss them if you have many experiences, lessons, and gains when writing the specifications. I personally have some experience and experience on how operators organize and formulate standards. I will first throw a brick for your criticism.

Standardized Positioning

Some netizens on the Internet vote and ask which operator has the best standards. Someone will immediately ask what is a good standard. The benevolent sees benevolence and the wise sees wisdom. I understand it literally as follows: the rule is a rule, and the model is a model. The so-called good norms are based on operability and forward-looking standards.

The fundamental purpose of a standard is to unify the implementation standards. Therefore, I think the primary criterion for evaluating a standard is its implementation. If the final construction result of the system is very different from that of a standard, it does not serve the purpose specified. On the surface, this problem is about the relationship between planning and execution. But in fact, it is very important to fully consider the feasibility during the compilation of specifications. In fact, there are indeed many reasons why the regulations are not well executed, that is, there is no way to implement them, rather than not wanting to implement them. Therefore, the quality of the evaluation criterion should first be determined by the degree of consistency between the criterion and the final system. If no one can implement the criterion, then the value can be imagined. Specifications and planning are different. The plan is made out, which gives the speaker a lot of space to play. The same set of PPT is told by different people. Although the general direction is not wrong, differences in comprehension, content, and other aspects will lead to a very large difference in results. But the specifications are different. The understanding of the specifications must be unified. What is not defined in the specification is the space for readers and implementers to play, but if defined, there must be no ambiguity.

If the system construction can be consistent with the specifications, and the purpose of the provision is achieved, the quality of the evaluation standards depends on the "fan", or whether the "fan" evaluation can be implemented. The forward-looking nature of a specification is the core value of a standard in addition to unified thinking. It should be said that the compilation of each specification is a result of the painstaking efforts of many experts and industry insiders, and is the crystallization of technological progress and ideological development. If there is a lack of foresight, it cannot set targets and directions for development and play a guiding role. Therefore, this specification can only be referred to as standards, but cannot be a model for future construction.

During the planning, design, and construction of telecommunication networks, many standards are "translations", which are based on foreign standards and suggestions. After translation, after discussion, gradually develop national and enterprise standards. Due to the special nature of the business support network, it is difficult to find similar standards and blueprints overseas. Especially for Chinese operators, the construction of business support systems is more difficult. Therefore, in many cases, we can only develop business support systems "independently and independently.

Writing standards is also completing a project. Therefore, we should organize the compilation of standards in the way of project management. At the initial stage of standardization establishment, it is necessary to clarify the purpose of standardization and the scope of its application. The purpose of standardized formulation is to clarify the time progress and milestones of standardized formulation, and to determine the problems required by standardized formulation, so as to ensure that, within the established time, all resources should be concentrated on solving the most important problems, avoiding the problems of various people, scattered themes, nonsense, and lack of center in the standardized formulation process. It is further necessary to clarify the standardized application scope and the planned application time period. The construction and upgrade of the system is a process in which the system is continuously improved and never stopped. Therefore, the standard life cycle is clearly defined, enable the enterprise plan and finance department to work with the IT department to develop an important basis for investment planning and fund Preparation Planning, so as to strengthen inter-department communication and reduce departmental friction, avoid embarrassment. This is actually an important step for the IT department to establish authority in the minds of other strong departments of the enterprise. It is also necessary to narrow down the differences, clarify the subject, and obtain operable results as soon as possible.

The positioning of norms is sometimes made clear before the Organization norms are compiled, or before the resources are put in place. Such standards are often less difficult to be compiled. There are also many standards, it is not clear before the compiler is in place. This requires the organizer and creator of the specification to discuss the positioning of the Specification. Especially in the latter case, it is often the most difficult question for everyone to solve during the compilation of large-scale norms: leaders only raise large frameworks and strategic objectives, but what is the target? How can we understand the positioning of standards? At this time, if the standardized organizer does not fulfill its obligations and does not unify the goals of the team and the expectations of the leaders, then it is easy to see unclear normative positioning and inconsistent ideas, or locate the problem that has changed, and the fate of the rule is at stake.

After a long time, he summarized the importance of standardized positioning. From a macro perspective, operability and foresight are the basic points of standardization. From a micro perspective, defining the purpose and scope of standardization is the foundation for project success or failure.

Formulation of specifications

1. Learning

The first stage of standardized compilation is the learning process. The organizer should first clarify the positioning and overall work arrangements of this standard, and then organize everyone to invest in standardized compilation. Everyone makes full use of the conditions. Of course, the organizer is also obligated to create conditions for the comrades involved in the compilation of regulations to learn and improve their technical and business capabilities. There are usually two ways to learn: one is to share documents, that is, to provide a sharing server, requiring you to put relevant information and documents for your learning; the other is organizational communication. Whether the speaker is an original manufacturer, integrator, or operator, everyone aims to present their experiences and research results to the project team, and then deepen their understanding through communication. This kind of learning opportunity is very rare. Although there are many people involved in the front and back of every standard writing, it is often the most beneficial to the project team.

2. Discussion

The next stage is the discussion, which is also the most exciting part in the process of standardized writing. Many classic ideas, ideas, and ideas are emerging, formed, and mature in the collision of this stage. However, this stage is also the most difficult to control. How difficult is it? Just like our posts on this forum, the topic often refers to one meaning, but it becomes another topic. At this time, the operator, the project team lead, and other core members should play a role. There are two things to be done: one is to control the scope of the discussion and keep the focus of the discussion focused on the most valuable goals; the second is the determination. When appropriate, the system makes a judgment when listening to a large number of opinions and ends the discussion.

This stage is the most difficult, and it is also the best time to reflect the dominant capabilities of operators. China Mobile is able to take the initiative in system planning and development because it can control the situation at this stage. Whether it is the choice of core technologies or the definition and interpretation of business problems, we need to quickly make judgments based on the discussion, the basis for making judgments is often the grasp of the system, understanding of the technology, and self-confidence. On the other hand, in fact, many questions do not necessarily have absolute right or wrong, but after we make judgments, we can stop endless discussions.

3. enrich content

At the end of the discussion stage, content enrichment is just physical activity. As long as the writers pass through the level of text, they basically do not need to exercise a great deal of attention. But at this time, be careful with the unification of text styles. A more effective solution to this problem is the cross-check and General Compilation responsibility system, which is necessary for text checks.

The most difficult chapter to write about norms is the general principles. Many people only read this chapter when reading the norms. Therefore, the quality and logical thinking of this chapter must be ensured. When I presided over the compilation of specifications, this chapter basically needs to be discussed by the leaders and written by the best people.

As other chapters, the quality can be lower, but good standards must be consistent with the style of each chapter. This often requires the team lead to grasp and reflects the overall strength of the project team.

4. Publicity

The last point is publicity. In fact, the best propagandist is a partner who participated in the compilation of regulations. During communication between provincial companies, the core ideas and the understanding and suggestions of their own companies will be provided to customers; another company will do the same. If your partners participate in the compilation of specifications, the unified part of their handouts is your specifications. In this way, the provincial company often receives more people, has a deeper understanding, and has a more comprehensive perspective, which is much better than the publicity Effect of Headquarters organizations. Therefore, for operators, the partner is both a standard participant and a propagandist, which is of great help to improve execution.

Therefore, for standardized organizers, the main task is in the early stage. After clarifying the positioning, selecting the core team, setting up the outline, and finalizing the general rules, the rest is to make a decision. For the team members involved in the standardized compilation, they must first keep their ideas consistent with the standardized organizer, and then release their energy and knowledge according to the division of labor and their positioning, and is upgraded during the release process.

Standardized skills

1. Communication

The biggest difficulty in standardized writing is to maintain communication between people. Because the writers come from different organizations such as the group headquarters, provincial companies, integrators, product manufacturers, and design institutes, they represent different interests. To some extent, they are only the spokespersons of the company, because there are still many people behind them, and this kind of coordination work is very complicated. In addition, many times, there have been conflicts between organizations from which the standard writers come from. It is critical to keep everyone's discussion right. If the writers cannot unite, the results can be imagined. Therefore, maintaining team unity is an important guarantee for the successful completion of the regulations. If the writing work lasts for a long time, this problem can be well solved. When it is closed, it gets along with each other. Generally, the relationship is easy to solve. However, if it takes a short time, you have to drink to solve this problem, the next day, my family was like a family.

Another issue worth attention is the construction of core teams, especially the selection of team leaders. The leader plays a decisive role in the standardized compilation process. They have strong technical and organizational skills, good job, strict quality control, and a high level of passing through the standard model. The selection of the team lead is usually an excellent part of the discussion, but in general, the best combination is the partner's team lead, and the deputy team lead is the representative of the operator, in this way, if the partner does not say anything about the table, the effect will be better for the operator. In addition, it is best for the team leader to select those who have experience in standardized writing and have more exchanges at ordinary times to improve the communication efficiency. At ordinary times, the team leader takes the independent work of the team members and holds a meeting at night to discuss major issues. This work mode is very effective, which not only improves the efficiency, but also ensures the overall standardization.

2. Logistics Support

The formulation of regulations requires adequate logistical support, including selection of appropriate personnel, locations conducive to closed discussions, funding, and support for office equipment and conference rooms. The Holy Land set up by China Mobile is located in China Mobile's training center. It mainly focuses on the closed environment and several meeting rooms with different specifications, which facilitates communication in various ways, or intense or elegant, you can choose different environments based on the communication needs.

Of course, I believe that regular comrades have been compiled at the Xiaotangshan training center and should keep good memories of an affordable and unique diet, everyone once worried about the problem of "Let's continue with the development of weight", not to mention the wild hot pot in the nearby "lecture village.

We have considered establishing a more complete environment for standardized compilation, and even preparing specialized computers, so that we can achieve better confidentiality. It seems that China Telecom has done this first.

3. Incentive Measures

To encourage and unite the persons involved in the formulation of the specifications, a small nameplate can be issued to them after the formulation is completed. This small nameplate can be a proud and powerful tool for finding better job opportunities, from which excellent dispatching engineers actively participate in the formulation of specifications. We usually send a thank-you letter to the organization that participates in the compilation of the specifications. Both partners and provincial companies will be proud to be able to get standards and praise from group companies.

Normative feedback and revision

No specification can be made seamless, and no specification can take all the situations into account. Therefore, from the first day of its birth, we must consider its constant updates and improvements, by the end of its lifecycle, corresponding technical means and organizational forms are required. There may be two methods for revision. One is review and minor revision of the specification according to the comment of the review team; the other is to issue a draft for soliciting opinions, then, revise and adjust the specifications based on relevant feedback, and issue a formal version.

We have not properly resolved the problem of Business Support Network specification revision. There are many reasons. For example, the specification requires system construction for verification, but the system construction period is long and it is difficult to carry out testing and verification. However, I think there are two subjective reasons: First, after the compilation of the specifications, everyone is busy with their work. It is because the integrator's personnel have already invested in the fight for making orders, so they have no time to take care of them, the operator has either invested in the compilation of new specifications, but has to focus on publicizing the specifications. It is rare that the operator will spend time and energy on the revision of the specifications; another reason is that the standardized life cycle management awareness is relatively weak and there is no closed-loop management. It is often because the standard has been released to complete the task and relevant work has ended. Unless there is a major problem and it needs to be revised in a supplemental document, the subsequent version will be the "decree" and will not be changed. Therefore, if we want to take the standard compilation process to a new level, the issue of feedback, revision, and upgrade deserves your attention.

Lin is always talking about things, because many things are some of our experiences during our work, and may lack organization and logic. In other words, there is no rule for the compilation of specifications. Many experiences are self-developed and not necessarily correct. As the business support network is moving towards standardization, I believe that the compilation of norms will gradually mature and form a relatively fixed model. By then, we may only need to enter information in a fixed mode, the specification is automatically generated. However, because there is no framework constraint, everyone's creativity has been maximized. Although there are some shortcomings in every compilation of specifications, the good memories of that time will always be with us. I would like to take this opportunity to sincerely thank the comrades who have worked with me to develop specifications. China Mobile will not forget you.

This article from: http://www.cww.net.cn/article/article.asp? Id = 27091 & bid = 651