Understanding design engineers from a system perspective

superstar_gu

Understanding design engineers from a system perspective [Copy link]

 

Thanks to the power supply learning activity organized by EEWORLD, I have learned a lot from reviewing the power supply theory learned in college with the experts. At the same time, I feel that I still have a lot to learn.

Dear students, I have been working in the power supply industry for a while. In the process of carrying out power supply projects, we will deal with the client, peers, suppliers, foundries, testers, certification agencies, markets, etc. Whenever we have a first chat, many people will ask power supply engineers the following questions:

(1) Is it a high voltage power supply or a low voltage power supply?

(2) Is it a radio frequency power supply, a high frequency power supply, or a low frequency power supply?

(3) Is it DC or AC?

(4) High power or low power

(5) Is it a current type or a voltage type?

(6) Which industry field? Power industry, inverter, etc.

(7) Ordinary power supply, special power supply

(8) etc.

It can be seen that although power supply (now mainly switching power supply) is a branch of power electronics, it has a wide extension. Precisely because of the wide dimension, power engineers often specialize in a certain field or a certain power architecture. How do power engineers view power supply? Let's officially start to talk about the theme of this time: how to view the development of the power supply industry from a system perspective. Here, let's first understand the concept of product life cycle.

The definition of product life cycle can refer to ISO/IEC 152888:2015 . The international IEEE organization divides the system life cycle into four processes:

1)agreementprogress

The participants in this process are producers and system users. One participant (the issuer/requester) assigns tasks for products and services to another participant (the acquirer/supplier). Both parties constrain each other by reaching an agreement. 2) Organizational project-enabling progress

This process provides resources to meet demand expectations. The participants in this process are generally market business departments.

3)technicalmanagementprogress

The project management process is used to develop and grow the project plan, evaluate the actual results and progress against the plan, and control the execution of the project through implementation. The participants in this process are generally project managers.

4)technicalprogress

Technical processes are used to define the need for a system and translate that need into an effective product, allow consistent replication of the product when necessary, utilize the product to provide the required services, maintain the provision of those services, and dispose of that product when it is removed from service.

Power engineers are generally involved in the technical process, which is also what we will focus on this time.

(1) Requirements definition process

The process of defining the requirements for a system that can provide services to users and other stakeholders in a defined environment. This is accomplished by developing a model, usually textual, that focuses on the system purpose and behavior, and describes it in the context of the operating environment and conditions. Requirements identify the parties that will have an interest in the system throughout its life cycle and express their needs, wishes, expectations, and the constraints imposed by them and the operating environment.

(2) Requirements Analysis Process

This process transforms a requirements-driven view of desired system services into a technical view of the desired system product that can provide those services. The resulting system requirements specify what the system needs to do from a developer's perspective to satisfy the stakeholders' needs. The goal is to build a representation of the future system product that satisfies the stakeholders' needs and avoids implementation problems as much as possible. System requirements are the basis for tests that verify that the delivered system meets the designer's intended solution.

(3) Architecture design process

This process synthesizes solutions that meet the system requirements. Architectural design involves identifying and exploring one or more implementation strategies at a level of resolution consistent with the technical and business requirements and risks of the system. From this point, the design solution is defined in terms of the requirements for a complete set of technically and commercially viable components from which the system is configured. Architectural design is also the basis for planning and designing an assembly and test strategy that will detect and diagnose failures during the integration step.

(4) Implementation process

This process implements the components required in the acquirer's system. This can be achieved by designing, manufacturing, and testing a new component, manufacturing and testing a new component based on an existing design, or adapting and testing an existing component. The implementation process continues with the design at the system/subsystem level by performing a detailed design based on the selected implementation technology. The components are manufactured and/or assembled based on the selected implementation technology. The manufactured or adapted components are tested based on criteria derived from the component characteristics specified in the system requirements and possible procurement agreements.

(5) Integration process

Assemble the validated components to create the system product specified in the system requirements.

(6) Verification process

By evaluating the system product, verification demonstrates that its behavior and characteristics conform to its specified design requirements. Verification provides the information needed to take remedial action to correct faults in the implemented system or in the processes acting on it.

(7) Transition process

The transition process installs validation systems at their operational locations according to an agreed-upon schedule, along with the use phase enabling systems (e.g., operating systems, support systems, operator training systems, user training systems) defined in the agreement to establish the capability to provide the system services required by the stakeholders.

(8) Verification process

The validation process is conducted to provide objective evidence that the services provided by the system when used meet the needs of the stakeholders and are defined in the requirements document included in the agreement to acquire the system. If discrepancies are found, these are documented and direct corrective actions. Since validation is a comparative assessment of requirements, it also confirms that the needs of stakeholders, especially users, have been correctly identified and requested; again, discrepancies lead to corrective actions.

(9) Operation and maintenance procedures

The Operation and Maintenance process enables staffing and training for operations and maintenance activities, operating the system, maintaining the system, monitoring system and operator system performance, and recording problems for analysis.

(10) Disposal process

Used to decommission a system and remove it from running service, deliver it to its final state, and restore the environment to its original state.

So far, we have basically established the concept of the system life cycle.

Our project will start with the following content in this context. Here we develop a battery-based bidirectional DC-DC converter according to the product cycle concept. How should our project be carried out? In combination with the life cycle concept, we divide the design of this product into the following stages:

(1) According to the preliminary research

(2) Requirements sorting

(3) Topology selection and simulation

(4) Solution design

(5) Component selection

(6) Schematic diagram

(7) Printed circuit board

(8) Welding and assembly

(9) Debugging and testing

(10) Project summary

We will start organizing requirements next week and have a preliminary discussion on topology.

Please reply to this question:

When you just got your project, what was the first step? How to ensure that each step is steady? Did you look back during the project development process?

电子微创意

The first step to a project is to clarify the requirements! Clarify the requirements! Clarify the requirements! In order to ensure that all actions in the later stage of the project are effective, it is necessary to clarify the requirements at the beginning of the project and ensure that the requirements converge so as to start the solution design.

想飞就飞

The first step is to do a good job of demand research. It is really important. Unclear requirements will lead to hardware re-modification in the later stage. After doing a good job of demand research in the early stage, there should be a detailed project schedule and project plan arrangements. If necessary, a backup plan can also be arranged.

okhxyyo

If you want to fly, just fly at 2021-4-9 16:58 The first step is to do a good job of demand research. It is really too important. Unclear requirements will lead to hardware re-modification in the later stage. After doing a good job of demand research in the early stage, there must be a...

It’s a good idea to prepare a backup plan! Indeed, we cannot guarantee that the process will go smoothly, so it is really necessary to have a plan B.

cjjh2014

There are two situations when the project is available:

1. The first is that the business receives project requirements from customers. In this case, we need to evaluate whether the customer requirements are reasonable and whether the cost is acceptable, and confirm the demand parameters based on these two points.

2. The second situation is receiving project requirements from the company's senior management, which are the demand parameters after review, so all parameter requirements must be fully accepted;

The next step for the above situation is to compare the various models currently available in the company. If they are similar, the parameters can be changed directly from the current models. If not, a new solution should be selected for development. In order to ensure that each step is stable, it is best to consult a solution provider who has mass-produced many solutions in the market. I think there is a need to go back and redevelop the project development process, but that is when the development process cannot be completed. Or when customer needs change.

一个小白5

The first thing to do is to determine whether the demand can be achieved with current technology.

我的学号

The first step is to analyze what the requirements are. After all, the entire project is driven by requirements.

Only with clear requirements, or goals, can we plan the next steps. For power products, the input power, output efficiency, loss requirements, safety standards, cost sensitivity, and application scenarios need to be determined. Mechanically, should the packaging be molded or purchased ready-made? What are the size requirements? How is the hole positioning? How long is the development cycle? How many people are involved? All these determine the future arrangements and direction of the project.

If you have enough time, you can start with simulation theory to study the feasibility of the solution; if time is tight, you can learn as much as possible, especially for products with large shipments and stability; you also need to have enough accumulation in daily life so that you can cope with emergencies. It is best to set goals in stages during the development cycle, and timely inspection and feedback are required when small goals are completed;

Unless you plan both PLANA and PLANB at the beginning, how can you go back when time is tight? All you can do in a project is to proceed steadily and steadily. Sometimes you may complain about the rules and regulations, but in fact, it is these rules and regulations that have been worked out through years of trial and error that ensure the normal completion of the project.

呜呼哀哉

The main thing is customer demand, but the demand is from the upper level, and the other is the time node. With the time node, if there is enough time, we will consider whether to consider innovation and cost saving. Otherwise, the first step is to consider the safest and most reliable on-time completion.

bqgup

Once the project is in hand, we will start to decide on the plan and choose the plan.

1nnocent

The first step is to analyze the project requirements. Before starting a project, you should brainstorm and make full preparations as much as possible. This will ensure that every step is taken steadily. Looking back, it is better to be well prepared at the beginning.

nmg

At this special time, we must first determine the solution to be used and whether there is a chip

sylar^z

When you get a project, clarify the requirements first, then determine the plan, and consider whether you need to reserve design margins for expansion.

erikaasuka

The first step is to collect requirements, including customer and internal requirements.

MianQi

Demand analysis and quantification.

ap0904433

The first step should be demand analysis

se7ens

If you are Party B, the first step is to analyze product requirements

If you are Party A, the first step is to analyze market demand

okhxyyo

sylar^z posted on 2021-4-14 12:56 First clarify the requirements of the project, then determine the plan, and consider whether it is necessary to reserve design margins for expansion

It is really necessary to keep this.

haifeng13980999

The first step is to clarify the needs. Do research. Technical difficulty, ensure the smoothness of the project, find matching items from existing models, and never look back.

ddllxxrr

Think twice before you act, and think again. The first step is of course to conceive.

hk386

When we just got the project, we first had to know what we were going to do and what functions we were going to achieve, then start looking for solutions and discussions, followed by functional implementation and hands-on debugging, and finally the finished product.