1 / 4

Functional Management Office (FMO )

Learn about the responsibilities and processes of the Functional Management Office (FMO) in validating manpower business processes within Information Systems (IS). The FMO oversees documentation, configuration management, governance reviews, and more to ensure efficient operations.

hmclemore
Télécharger la présentation

Functional Management Office (FMO )

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Functional Management Office (FMO)

  2. Commanding Officer Technical Director FMO Workforce Officer: 1 Enlisted: 0 Civilian: 7 Total: 8 Code FMO Functional Management Office Executive Officer Business Operations Code 10 Classification Programs Code 20 Manpower Programs Code 30 Aviation Programs Code 40 Afloat Programs Functional Management Office (FMO) Organization Code FMO Functional Management Office Deputy DH

  3. Functional Management Office Responsibility • Goal: Validate manpower business processes in Information Systems (IS) to ensure production of proper manpower documents • Current Manpower Information Systems (IS) • Activity Manpower Management (AMM) • Total Force Manpower Management System (TFMMS) Program Of Record (POR) Deployed last October • Manpower Requirements Determination (MRD) – Fleet • Navy Manpower Requirements System (NMRS) (POR) • Navy Occupational Classification System Support (NOCSS) • No POR • Processes: Conduct assessments on Information System (IS) procedures and documents • Document, validate & manage manpower business requirement functionality for IS • Position Management - Functional Review Board (FRB) Administration • Business Requirement Documents (AMM-BURT v1.1, FMRD-BURT v1.2, NOCSS-BURT v1) • Configuration Management • Configuration Control Board (CCB) Administration • Coordinate functional testing and reviews • Information System User Accounts (SAAR) • Represent users in IS governance processes • Governance Reviews (FAM, FISMA, Budget Processes) • Coordinate governance changes to the IS with Stakeholder Organizations • Maintain data reliability in IS • Data Management Administration (Data Steward – Validate System Tables, Interfaces, Meta-data, Security Levels) • Not FMO responsibilities • Does not conduct program modifications or operate the system - SSC NOLA responsibility • Does not own the manpower data – business process owners (e.g. BSOs/N122/NAVMAC/CNRFC)

  4. Business Requirement GovernanceStakeholder Organizations MPTE Governance/Strategy CNO N1/CNP Navy IT Governance/Strategy Navy CIO MPTE IT Governance/Strategy CNO N16 MPTE Resource Sponsor CNO N10 BUPERS Requirements Office (Pers-074) Manpower Governance / Requirements Sponsor (CNO N12) Manpower Business Requirements NAVMAC Functional Manager Planning, Programming & Budget Manpower Managers (BSOs/N122/NAVMAC/CNRFC) Navy Authorizing Official (NAO) U.S. Fleet Cyber Command System Operations Resources FMB System Project Director PPBE & Congressional Plus Up Funding Central Design Activity SPAWARSYSCENLANT NOLA Budget Submitting Office (BSO) SPAWAR Sea Warrior Systems PEO-EIS PMW 240 Program Manager PEO EIS Navy Acquisition Governance ASN (RD+A)

More Related