AGC AeroComposites began working with the U.S. Army on the MLASS product in 2012. The initial customer for the system is the Army’s 160th Special Operations Aviation Regiment (SOAR). This was a follow-on project to the successful LASS (Lightweight Armament Support Structure) which was fielded in 2011. The MLASS supports dual weapon pylons as opposed to LASS pylons, which support only a single weapons station.
MLASS is designed to provide two critical benefits. The first benefit is enhanced firepower enabled by the multi-station weapon configuration. The other benefit is weight savings when compared to Sikorsky’s metallic External Stores Support System (ESSS).
The MLASS fits existing Sikorsky’s UH-60M interfaces and uses the same attachment points as the ESSS. Each structure can support a variety of weapon systems including the M230 Chain Gun, M261 Rocket Launcher and M299 Missile Launcher. Each pylon can support up to four (4) Hellfire missiles.
- Full carbon structure with aluminum fittings
- Single strut design
- Design incorporates a dropped and moderately swept wing
- Easy-connect electrical stores chassis
- Meets all U.S. Army service load requirements, including stress and environmental testing
- 35% weight reduction compared to fully configured ESSS shipset*
- Composite structure offers superior corrosion resistance, damage tolerance, and fatigue life over the all metal ESSS
- Wing design (lower and swept) enables better crew visibility
- Design maintains a neutral lift and reduces drag compared to ESSS
- Single strut design along with integrated wiring access covers provide ease of maintenance and installation … less than 2 hours to convert a “slick” aircraft to a weaponized configuration
- The first two MLASS products have been delivered to the Army, and are currently undergoing testing. Airworthiness Release (AWR) is scheduled to be completed the first half of 2016.
- AGC AeroComposites is currently on contract to produce eight (8) more shipsets, with delivery expected to be completed summer of 2016.
CTTS CASE STUDY - Milestone 3: Solution Page: 3-1 MILESTONE 3 – MODELING SYSTEM REQUIREMENTS Activity 1 – Use-Case Glossary he following use cases and their descriptions and actors can be determined from the interview. Some students may identify other use cases based on standard maintenance functions. These are not incorrect, but have been left out of the glossary for the sake of simplicity. We have chosen to focus only on the use cases that will be most used. T A few notes on the use cases included in the glossary: M ANUALLY R ESOLVE S ERVICE R EQUEST was made a separate use case from A UTOMATICALLY R ESOLVE S ERVICE R EQUEST because the steps that each follow are very different. An abstract use case called R ESOLVE S ERVICE R EQUEST was added to encapsulate the logic that actually marks a service request as resolved. This will be used by M ANUALLY R ESOLVE S ERVICE R EQUEST and A UTOMATICALLY R ESOLVE S ERVICE R EQUEST . From the interview we could easily add another abstract use case for logon. But since every other use case would use logon, this was left out solely to keep the use case diagram that follows from becoming messy. An Employee role was added for two use cases that could be accessed by any employee.