S6 and SASMO relationship ?

Thank you Sir! Finding a way to make it work is my concern! The main reason for the merge is because of man power! But how do i merge them and keep both role separate ? I can’t fond a unit that successfully done so to give me a good idea on the approach

1LT (Join to see) - you can't keep it separate with regard to your span of control. You now own it. There is often a perception that SASMO doesn't do anything, so "free labor". They have to be in constant contact with supported units verifying their readiness status, if they are having issues, and talking them down from 30000 feet. One BMO complains in a material maintenance review that something doesn't work (may or may not have anything to do with you, or he had not even turned on the system) and you get thrown under the bus to check the exhaust bracket status.

SASMO has to pull info out of the supported units. Otherwise their STAMIS becomes NBC (no body cares), until they fail an inspection, reports don't happen, and critical parts are not on order. Now you have the whole supply system in GCCS-A between class VII, II, IV, and IX, which were all different things before: PBUsE, ULLS, and SAMS/SARSS.

Everyday they need to be out hustling. Customers should be sick of hearing from them.

Thank you Sir! That part i understand,but the reason for my question is that our BC rolled the SASMO section under the S6 OIC! My concern is how can i merge both section but not take away the SASMO section mission/role?

1LT (Join to see) - I have never seen that. My response as a SPO would have been over my dead body.

If that is the mandate you got, I would consider the following
- like the Sig BN and the S6 has the system stop light chart for the network nodes, you need to have a dashboard of all the SATs, including key update package status.
- making people use the SAT at home station will ensure they can make them work while on mission.
- unless you check it, the SATs will be broke at H Hour and no one will know. Getting those repaired is a painful process.
- the SASMO signaleers need to immerse themselves in the STAMIS piece, now GCCS-A with some exceptions. They may need to go to class, get some distance learning, or OJT in the SPO or the HHQ MMC (those are coming back) to,learn what the systems does so they can look for network issues.
- the SASMO 92 series need the opposite.
- both need to be fluent in trouble shooting the SAT.
- if you have a Civlian SASMO (I had one as a BCT SPO), you may have to work through the XO to have his job description altered.
- whenever there is a pushed patch or major software change/update, this will negatively impact log systems. Always does. Water is wet, sky is blue, NEC pushed changes Jack up systems. gCCS-A is no exception. It's all fun and games until people can't order deadlines parts or the CG doesn't get the cyclic report that is due. When you start talking ports and firewalls, people's eyes glaze over...stuff should just work. Change confirms and settings automatically, at random, or with undue care as to the system impact really infuriates user types.
- using the SASMO team as fillers and DA6 sacrifices will come back to haunt you, just like misusing 35Hs. They are small but they are mighty.
- Do you have a SASMO warrant?
- long story long, you need to preserve the section's mission. There is a cross train potential here, but there hasn't to be the Cadre of expertise that must be developed and preserved for that cross training to mean anything

LTC (Join to see) have you seen the SASMO under the S6 at NTC?

LTC Jason Mackay I experienced the same issue as a SPO when I was in 615th ASB. The S6 staff was small and inexperienced and the CSSAMO at the time was robust and full of professional nerds. The BC thought incorrectly that they could be his personal computer help team. So I understand the Manning issue but this is also a training issue and la k of understanding of the Task/Purpose of the SASMO and SPO External Support Function. As GM07, I can tell you that most BSB's and CSSBs are unfamiliar with setting up their network architecture and have fallen back on the garrison backbone for connectivity. The S6 needs to define roles and responsibilities first of each section then begin to identify major daily taskers that will be accompanied. I can see how a Brigade can royally screw themselves over if their LIS is not sync'd with the G8 on Cl IX req's. As a SPO that is non negotiable.