M2.5: Weeding Out a Solution
Aaron L. Stone
ASCI 530 Unmanned Aerospace Systems
Embry-Riddle Aeronautical University
4/1/2017
As the systems engineer it is
imperative to remain impartial and unbiased when working with design teams when
solving difficult issues. One of the primary concerns for all systems engineers
is to be representative as a voice for the customer. This action is carried
throughout all development phases until completion of the project.
During a recent verification audit, it was found that two
separate subsystems have violated allotted weight restrictions. As the systems
engineer in charge of this project I have first identified the issue at hand. I
have reviewed the customer’s requirements and have a full understanding of what
the system must do, and what the company has agreed to produce.
Looking to the safety engineers and asking their team to
adjust the fuel margin is not a necessary step that needs to be taken
presently. The sole purpose of this UAS project has been based upon the size
and mass of intended payloads used for crop management. It is this weight
requirement that is often the premier determinant of the layout, size, and
all-up-mass (AUM) of the aircraft (Austin, 2010) . After having
analyzed the requirements, changes in the physical configuration must be made
to clear the weight restrictions.
By maintaining traceability during the entire project, it
provides the systems engineer the ability to track and identify changes in
every step of the design process. In each situation both subsystem teams
attempted to reduce project costs by purchasing off-the-shelf hardware, instead
of manufacturing a custom design. Each team has developed a technically sound
product, if not for the obvious weight violation that was neglected. One aspect
involving systems analysis and control is to effectively evaluate alternative
approaches in satisfying technical requirements and program objectives (MIT OCW,
2001) .
As systems engineer, I must have each subsystem team that
busted weight restrictions restart with the design synthesis process. This will
provide an alternative solution to using off-the-shelf hardware and busting
weight restrictions. Each team will redesign and draft new proposals on their
specific subsystems while adhering to all project outline requirements. Once
proposals are completed a cost comparison can be done. A comparison is needed
between each team to see which method is going to be cost effective for the
company while still meeting all the customer’s requirements.
References
Austin, R. (2010). Unmanned aircraft systems:
UAVs design, development, and deployment. Chichester: Wiley.
MIT OCW. (2001, January). Retrieved from Massachusetts
Institute of Technology OpenCourseWare:
https://ocw.mit.edu/courses/aeronautics-and-astronautics/16-885j-aircraft-systems-engineering-fall-2005/readings/sefguide_01_01.pdf
Comments
Post a Comment