field supply and maintenance analysis office east
Skip this Video
Download Presentation
Field Supply and Maintenance Analysis Office East

Loading in 2 Seconds...

play fullscreen
1 / 31

Field Supply and Maintenance Analysis Office East - PowerPoint PPT Presentation

  • Uploaded on

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

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Field Supply and Maintenance Analysis Office East' - merlin

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
fsmao east poc
  • OIC: LtCol LaPratt
  • SNCOIC: MGySgt Lynch
  • AOIC/OPSO: Maj Griffith
  • COPS: Maj Murray
  • FOPS: CWO-4 Brewer, MGySgt Allegretto
  • Data: Mr. Rob Rangel/Mr. Vic Tompkins
  • Training Coordinator:MSgt Edwards
  • CPI/OPS: Mr. Dave Ratte/MGySgt Cartwright
  • Scheduler: MSgt Meece
program description
Program Description
  • GCSS-MC is the primary technology enabler for the Marine Corps Logistics Modernization strategy. It will replace a portfolio of legacy logistics systems that provide the backbone for all logistics information required by the Marine Air Ground Task Force (MAGTF). The core is modern, commercial-off-the-shelf enterprise resource planning software (Oracle 11i e-Business Suite). GCSS-MCs design is focused on enabling the warfighter to operate while deployed with reachback from the battlefield.
  • GCSS-MC is being implemented in three blocks:
  • Block 1 replaces 30-year old legacy supply and maintenance information technology systems. The focus of future blocks will be enhancing capabilities in the areas of warehousing, distribution, logistics planning, decision support, depot maintenance, and integration with emerging technologies to improve asset visibility.
program overview
Program Overview


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).

  • Real time view of equipment readiness
  • Replaces SASSY, MIMMS, & ATLASS

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.

  • Over-The-Horizon Objective
fsmao east


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.

  • Cutover Cells –A specialized team (normally 1 supply, 1 maintenance) assigned to each BN sized unit facilitating parallel cutovers throughout each geographic region.
    • Team Leader coordinates with Unit Coordinator. First line of help desk during rollout.
    • Oracle specialist (1 per 3 cells) helps establish initial unit accounts. The team also checks and verifies network issues.
  • Intermediate Level Cutover Team (ILCT) – The ILCT focuses on the cutover of intermediate level organizations (SMU, ISA, IMA and RIPs). It is expected that an ILCT will remain with an intermediate level organization throughout the duration of the cutover.
  • Instructor Team – Execute critical mass, roles based training. Consists of 1 CTR and 1 MEF Marine team.
  • GOC/Help Desk - Monitors Enterprise Systems Operation; located near GCSS-MC PM Office in Quantico and Albany GA.

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.







gcss mc cutover phases
GCSS-MC Cutover Phases
  • Phase 1 – Shaping/Preparatory Actions (C-11 thru C-6)
      • Objective: Unit is prepared to begin cutover activities at C-5
        • Commander’s In Brief: The unit must understand what is required for cutover
        • Cutover Team must understand the needs and mission of the unit.
        • BR-100 and Data Templates, BICs, Inventories, SCAT
  • Phase 2 – Cutover Activities (C-5 thru C-0)
      • Objective: Unit is prepared for a successful cutover at C-0
        • Unit set-ups entered into GCSS-MC (BR-100)
        • User account registration/activation
        • MOCK Conversion, SCAT
        • Compliance Analysis (TBD)
  • Phase 3 – Train Users (C-5 thru C-1)
      • Objective: Successful training of the unit’s critical mass of users
        • Identify Users and their Roles – Match users to Training
        • Assign Users to Training Sites and Schedules
  • Phase 4 – Cut Over
      • Objective: Unit successfully operating on GCSS-MC
        • Convert Data and upload Data Templates
        • Post-cutover Reconciliation Tool
        • Begin Transacting
        • Verify Activities
cutover timeline weeks
Cutover Timeline (Weeks)
  • C-11: Cutover team conducts Initial In-Brief
  • C-6: Begin user training, Mock Conversion, Collect BR.100 data
  • C-5: Cutover team submits BR.100 to program office, work Mock Conversion discrepancies
  • C-4: All priority 13 requisitions stopped
  • C-3: Verify BR.100 data in GCSS-MC, DASF and DPR records match, SABRS and SASSY records match, final 06 priority requisitions
  • C-2: BIC pull for GCSS-MC, upload HR data, final 02 requisitions
  • C-1: Self-registration/activation/setup of user accounts, DASF, RO, ROP allowances are correct, final reconciliation with legacy systems for tracking purposes
  • C-0: Account conversion to GCSS-MC
  • C+1: Data Validation and conduct live transactions
  • Unit Expectations
  • FSMAO training team will arrive at C-05
    • Receive training information in three phases
      • 1) In-brief at C-11
      • 2) Preparation and Education
        • Schedule for actual dates SGOC training team will provide instruction to be provided during unit in-brief
      • 3) Classroom instruction from C-05 to C-01
  • Unit to provide a Unit Training Coordinator (UTC) name at In-brief
    • Recommend the S-3 Chief
    • Requires MCTMS access (local school entries required)
  • Be prepared to provide a current Alpha roster of all unit personnel at In-brief
    • On-hand strength by T/O Billet
    • Used to identify roles and required training
      • Name  Billet  Role  Training
  • Provide classroom (if available)
  • Training Process
  • The FSMAO training team will:
    • Provide general guidance and responsibilities of UTC position to include:
      • Completing and submitting a Unit Training Docket
        • Name  Billet  Role  Training
      • Student enrollment process – “Registering”
      • Individual readiness requirements
      • Unit readiness requirements (based on current O/H personnel)
      • SGOC reporting procedures and performance metrics used
      • SGOC training database usage (pending completion)
    • Identify initial estimate of critical mass users requiring training
    • Provide the unit a copy of training schedule NLT C-6
  • Units should expect to have all identified GCSS-MC users fully trained no later than 1 week prior to planned cutover date
  • Additional Notes:
  • Course completion certificates
  • Entry of course completion in MCTMS  MOL
  • Training is open to all potential users regardless of cutover date or unit
    • Cutover units have priority during cutover period
  • *** Training recommendation: All users receiving training prior to their scheduled cutover activities beginning (C-06) to receive re-evaluation/ testing.
  • Online pre-requisite course have been replaced with Instructor Lead Training (ILT)
    • Introduction to GCSS-MC
    • Highly recommended that all students attend prior to any other ILT
  • Commander’s Course – CO, XO, AO, RO and key staff members
    • 2 hour course
data quality
Data Quality
  • Data Quality: The reliability and effectiveness of data. Data quality is not linear and has many dimensions like Accuracy, Completeness, Consistency, Timeliness and Auditability.
  • Data Cleansing:Data cleansing is the act of detecting, correcting, or removing corrupt or inaccurate records from a record set, table, or database.
  • Data Quality is paramount:
    • MHIF/Item Master
    • Data stream bomb out
      • Can’t just key punch the data into the new system because there multiple touchpoints, if one wrong…..
    • Labor Intensive
    • Skill level must grown
      • Initial skill set will not be optimal
      • Totally new …..
SCAT Purpose

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


Data Rules


Error Codes

Rejected Records

SASSY Files Cutting-over to GCSS

  • LUAF (PC “C” – MAL)
  • LUBF/GABF (PC “A”, “F”, “G”)
data rules
Data Rules

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:

  • LUAF (MAL)
    • RTLS Ser # count does not match LUAF OH

(The number of serial numbers on the CMR exceed the qty on the MAL)

  • RTLS file (Serial Numbers on the CMR’s)
    • Duplicate serial #’s in more than one AAC

E-Business Suite (EBS) rules are Oracle based criteria required for the correct conversion of Legacy data into GCSS-MC.

EBS example

  • LUAF (MAL)
    • NIINs on the LUAF must be resident in the Item Master

(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.

  • Reports will be sent out on a weekly basis to the SFTP site. Go to the SFTP site, ATLASS folder, FSMAO Folder, FSMAO East folder, appropriate TLC folder, MSC folder, AAC folder.
error reports

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)

Rejected Records

Tab 11 - LUAF Passes

Tab 12 - Retail Inventory Passes

Tab 13 - Retail Loc Serf Passes

error codes

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.

rejected records
Rejected Records

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).

billet identification code
Billet Identification Code
  • Validate & verify employee base
    • BIC must be assigned for all Marines
    • BIC is utilized in GCSS-MC to route user request to UUAM and for user roles/responsibilities within unit
    • Current BIC percentage assignment for each unit
unit key personnel
Unit Key Personnel
  • Unit Coordinators and Using Unit Account Managers (UUAM)
    • Unit Coordinators are tasked as liaisons between cutover teams and the unit accomplishment of tasks. Requires knowledge of billet holders, functional areas, and unit SOPs. Will be required to assist in initial unit set-ups (BR.100) and coordination of training for unit Marines. Temporary billet.
    • UUAM will be required to approve users, provision accounts with groups, calendars, territories, and sub-inventories, granting shipping access, and assignment of roles. Permanent billet.
unit key personnel1
Unit Key Personnel

Unit Training Coordinator

  • From Site Survey Activities
    • Identify Users of GCSS-MC
    • Match users to system roles
    • Match users/roles to training for those roles
    • Assign users to training sites and schedules
  • Training
    • Self-Training Web based curricula (Basics of GCSS-MC)
    • Instructor led training via
      • MTS (Mobile Training suites)
      • Typically, one to six weeks of training (Role based)
      • Cutover training is generally scheduled for weeks C-6 to C-1
  • Objective: Successful training of the unit’s critical mass of users
hardware and software issues
Hardware and Software issues

ID hardware & facilities

  • NMCI hardware by commodity
  • NMCI port locations
  • Hardware availability for MFS application

JAVA Settings and Pop-Up blocker

  • Must be done for each user on a computer asset
  • Does not require NMCI approval
  • If not done it will prevent Oracle application from loading
keys to success
Keys to Success
  • Understanding GCSS-MC is not MIMMS/SASSY/ATLASS
  • Open mind – new way of business (not always fastest)
  • Patience to learn and operate under a new system
  • Stakeholder ownership
  • Proactive vice reactive
  • ASK, question, and submit issues
  • Tasks that can be performed now:
  • BIC assignment
  • Data Quality
  • Start identifying unit key personnel
  • Identify Sub inventories and stock locations
  • Begin role/responsibility planning
  • Review Maintenance related programs
  • Classroom Requirements
  • Seating for 20+ students and instructor
  • (2) 20 amp circuits
    • Supports MTS server and up to 24 laptops
  • Minimum of (5) available electrical outlets
  • Adequate lighting
  • Climate controlled
  • Access to head facilities (male and female)
  • Physical security requirements
    • Locks for doors and windows
    • Restricted access after hours
  • ** Classroom will be used by all students within the same cutover Sequencing Group
mts functional technical data
MTS Functional/Technical Data
    • The Mobile Training Suite (MTS) is the combination of equipment, documentation, and procedures used in the training of GCSS-MC/LCM personnel in locations where network connectivity to the Enterprise Training environment is not available. All the equipment required for the mobile training environment is built within portable enclosures so that it can be easily transported to any classroom or training environment.
    • GCSS-MC is comprised of a portable 20 student computer trainer system consisting of 1 HP DL360 G5 Server and 24 HP KR151AV laptops, an uninterruptable power supply (UPS), Storage Works MSA 60 Network Switch, Mitsubishi DLP Projector, HP printer, and associated peripherals.