Field Supply and Maintenance Analysis Office East. GCSS-MC Brief. FSMAO East POC. OIC: LtCol LaPratt SNCOIC: MGySgt Lynch AOIC/OPSO : Maj Griffith COPS: Maj Murray FOPS: CWO-4 Brewer, MGySgt Allegretto
A system that supports logistics elements of command and control, joint logistics
interoperability, and secure access to and visibility of logistics data.
GCSS-MC LCM Block 1 Increment 1.1
Provides initial capabilities for GCSS-MC/Logistics Chain Management (LCM).
GCSS-MC LCM Block 1 Increment 1.2
This is the second increment of GCSS-MC/LCM. It provides deployed and
additional capabilities for GCSS-MC/LCM. It will have its own Statement Of Work
and timelines within the current acquisition program.
Staffed during cutover to serve as the PMO’s onsite deployment team. Manages the day to day operations of GCSS-MC implementation during the deployment of GCSS-MC within a specific AOR. Collects and reports metrics and coordinates any facility issues.
GCSS-MC MEF Liaison Officer - assists each MEF and S-GOC with coordinating local deployment, implementation and cutover activities and enhance communications with the GCSS-MC PMO. II MEF LNO is LtCol Spaar. MFR LNO is Maj O’Grady.
Training Coordinator – serves as the primary scheduler and liaison between the instructor team and the unit coordinators.
MEF Training FacilitiesCoordinator- ensures that the training facilities are scheduled and prepared for instruction. This includes making sure training materials are delivered and the appropriate audio visual equipment is provided.
Future Ops – “Advance party” for the Cutover Teams. Identifies facilities and develops local schedules prior to the formal establishment of the S-GOC and arrival of the cutover teams and the training coordinator.
Key Implementation Events
The purpose of the SCAT database is to assist units in correcting legacy SASSY data in order to facilitate the conversion to GCSS-MC. The database generates a report in the form of an Excel spreadsheet for each unit, to include a report on the conversion accuracy
SASSY Files Cutting-over to GCSS
Legacy data rules are applied to a unit’s SASSY data to ensure it complies with current Legacy requirements.
These rules apply to all SASSY Records, below are data rule examples:
(The number of serial numbers on the CMR exceed the qty on the MAL)
E-Business Suite (EBS) rules are Oracle based criteria required for the correct conversion of Legacy data into GCSS-MC.
(NSN on the MAL must be resident in the MHIF in GCSS)
Error tabs and Error Code tabs – Each error tab has a corresponding Error Code tab which explains each code and gives recommended corrective action for every error.
Rejected Records - LUAF Passes, Retail Inventory Passes, Retail Loc Serf Passes, explains what information will NOT convert into GCSS.
Error tab’s and Error Codetab’s
Tab 1 - DASF Errors
Tab 2 - DASF Error Codes (recommended corrective action)
Tab 3 - LUAF Errors
Tab 4 - LUAF Error Codes (recommended corrective action)
Tab 5 - LUBF Errors
Tab 6 - LUBF Error Codes (recommended corrective action)
Tab 7 - Retail Inventory Errors
Tab 8 - RINV Error Codes (recommended corrective action)
Tab 9 - Retail Local Serf Errors
Tab 10 - RTLS Error Codes (recommended corrective action)
Tab 11 - LUAF Passes
Tab 12 - Retail Inventory Passes
Tab 13 - Retail Loc Serf Passes
Error codes with an alpha character represent a violation of a Legacy data rule or EBS data rule.
Error codes with a numeric value represent an extension of the Legacy Data rules.
LUAF Passes, Retail Inventory Passes, Retail Loc Serf Passes, are tabs intended to tell you what information will NOT convert into GCSS, if the item is not flagged/cataloged as Install Base tracked, serial tracked, etc.
*This also captures items that were rejected due to a Legacy data rules, EBS rules (errors not corrected by a unit).
Unit Training Coordinator
ID hardware & facilities
JAVA Settings and Pop-Up blocker