MCFMIS Draft PWS April 2026 V4.docx

PERFORMANCE WORK STATEMENT (PWS)

MARINE CORPS INSTALLATIONS COMMAND (MCICOM)

FOOD SERVICE AND SUBSISTENCE SECTION (G-4)

SERVICES BRANCH (LFS)

FACILITIES AND SERVICES DIVISION (LF)

INSTALLATIONS AND LOGISTICS DEPARTMENT (L)

MARINE CORPS FOOD INFORMATION SYSTEMS SUPPORT

1. SCOPE.

The purpose of this Performance Work Statement is to outline requirements needed to support a Class I information Management System (Marine Corps Food Management Information System (MCFMIS)). This system will provide the Marine Corps Food Service Program with a tool to determine subsistence requirements; conduct inventory; generate and modify recipes menus, and production lists, analyze nutritional content, figure cost, and capture point of sale information.

The software will be installed at all Marine Corps commands within the Continental United Sates (CONUS) and Outside the Continental United States (OCONUS).

The Marine Corps will require a perpetual corporate license with unlimited users for use of software. The perpetual license will cover all enhancements/modifications to the Commercial of the Shelf (COTS) resulting from engineering changes and required interfaces.

2. Background.

In 1997, the United States Marine Corps implemented a DOS based COTS software package to manage their entire garrison feeding operations. Over the next ten plus years, the COTS product adopted the name Marine Corps Food Management System (MCFMIS) and was continually enhanced to meet the Marine Corps needs. While many of the higher-level modules were implemented for the software providers civilian customer base as a whole, several were done at the request of the Marine Corps’ MCFMIS system.

In 2006 the Marine Corps upgraded to a re-engineered and re-designed web-enabled, Windows based platform, designed to take advantage of the cutting-edge of technology for the Food Service industry. While the originally upgraded package was 100% COTS, the Marine Corps eventually identified and purchased some of the specific functionality contained in the original legacy system.

In 2018, the Marine Corps transitioned MCFMIS to support both garrison food operations and field food service operations. This change incorporated the term Field Marine Corps Food Management Information System or FMCFMIS. This enhancement allows for auditability and management of requests and inventory for field rations as well as money allocated to field contract feeding.

With the introduction of new financial policy and software programs in the Marine Corps, evolving cybersecurity requirements, and Defense Logistics Agency (DLA) subsistence supply chain Modernization efforts, the need to continue software enhancements is evident.

The Marine Corps contract with its current software provider ends, 31 March 2027.

The Marine Corps’ goal is to provide its users with a internet and cloud-based system that allows designated users to work from any location on any computer. The software shall support food management operations in an “unconnected” mode so that users can still access all capabilities of the system if the Internet is unavailable for a given time. The software shall incorporate DOD Single Sign On (SSO) technology to achieve DOD Public Key Infrastructure (PKI) and Public Key (PK) Enabling IAW Department of Defense (DoD) Information Technology (IT) Enterprise Strategy and Roadmap, to eliminate the need for username and passwords to connect. The software shall provide the basic core functions of: meal planning, food ordering, inventory control, forecasting, headcount recording, recipe management, budget and financial management and reporting, as well as enhanced use by personnel involved in menu development, menu evaluation, nutrition education, nutrition research, food research and development, and patron verification/accountability. The processes should be the same in peacetime, contingency and war, in CONUS as well as OCONUS.

The Marine Corps collects and manages vast amounts of data within MCFMIS. Turning that data into information and using that information to intelligently manage government operations is a huge challenge. In some cases, it may take days or weeks to pull together data from different sources and reports, to obtain historical, current, and predictive information required for effect business operations. The Marine Corps is looking for a way to access timely, detailed, and trustworthy data to drive timely decision making. The Government believes the use of Artificial Intelligence (AI), Business Intelligence (BI) and Data Warehousing will enable more effective strategic, tactical, and operational insights and decision making.

The Software Provider shall implement a solution that incorporates a software module to help the Government achieve a solution that integrates the use of Artificial Intelligence (AI), Business Intelligence and Data Warehousing.

MCFMIS must be able to function consistently in peacetime, contingency, and war. MCFMIS shall be accessible from authorized computers that have access to the worldwide web. The Food Management system must allow for operations even when the web is not accessible at a site. Data and transactions should be capable of being submitted in real time via the Internet and be capable of being “batched” at such times when the web is not accessible and transmitted when web access is again available. The MCFMIS system must also be able to automatically re-synchronize data and operations when connection to the web is re-established.

The Marine Corps anticipates that extensions to the selected COTS Food Service Management software, as well as changes to business practices will be needed to provide a complete automated solution that satisfies our military as well as our civilian food service contractor’s requirements for subsistence production and logistics.

2.1 Food Service Organization Background

The Marine Corps must feed its personnel in various environments and under diverse conditions during peacetime and war. These different scenarios represent the basis upon which requirements must be developed for our food management system.

Garrison feeding is characterized by the requirement to feed personnel either temporarily or permanently attached to a garrison mess hall. Garrison feeding must support cafeteria and campus style, advanced meal pickup and “meals to go.” This scenario assumes that an established communications infrastructure is available to support system connectivity.

There are currently two types of garrison mess hall operations within the Marine Corps.

a. CONUS operations, which consist of contractor-managed mess halls.

b. OCONUS operations, which are military managed mess hall operations.

Each CONUS installation is comprised of one Contractor run Food Service Office (FSO), an additional Government run FSO and at least one mess hall. OCONUS installations are comprised of one Government run FSO and at least one mess hall.

An installation with only one mess hall is referred to as an “Individual Food Service Organization” and all other organizations are known as “Consolidated Food Service Organizations”. Separate systems should be utilized to operate the FSO and Mess Hall systems. The ability to separate Government (OCONUS mess halls) and Contractor FSO functionality (CONUS mess halls) is also required due to different software structure and reporting requirements.

Each mess hall operates independently of the FSO and of other Mess Halls at an installation. All functions related to mess hall operations (meal production, requisitioning, inventory, and headcount recording) are done at the mess hall. The responsibility of the FSO is to consolidate and oversee the operations of the individual mess halls and to perform functions that are generic to the entire base, such as menu development and order consolidation for all FSO sites.

Field feeding is characterized by the requirement to perform food management functions for a unit that is away from its home base. Inventory management must include the ability to assign a Date of Pack, Lot Number and Date Product Expires to an operational ration inventory item upon receipt, issue, adjustment, transfer, or sale. A core assumption for this type of feeding is that connectivity is not available or not reliable, so feeding must be supported by a system that can operate locally. Examples of field feeding are deployments and mobilizations. Field feeding can be supported by the use of operational rations, contracted feeding, Host nation support and DLA managed prime Software Provider contracts.

The current hierarchy consists of the following organizational levels and the number of allocations required at each level. The sites may be used to create the hierarchy within the system but may require changes as sites adjust due to manpower changes within the Marine Corps.

(3) Headquarters level (Garrison, Field Active and Marine Forces Reserves (MARFORRES))

(1) Civilian contractor hub which supports (48) Contractor managed mess halls CONUS

(7) Military managed mess halls OCONUS

(14) Bases in approximately 12 states CONUS and 3 countries OCONUS

(4) Marine Expeditionary Forces (MEF) level (I, II, III MEF and Marine Forces Reserves (MARFORRES))

(16) Active-Duty Major subordinate commands (MSC)

(15) Reserve Major subordinate commands (MSC)

(11) Independent organizations (IO)

If Marine Corps hierarchy structures change (adding, subtracting, or changing levels, sites, or units), Software Provider will provide a cost estimate to accomplish the task, if structure changes cannot be handled with current software deployment.

3. REQUIREMENT.

The software provider will deploy the Food Management System to all Marine Corps Mess Halls worldwide providing dining services. Prior to full deployment, the Software Provider will install a prototype at selected sites to reveal any problems or areas for improvement. Deployment will include pre-installation planning (e.g., ensuring that the correct communications and power connections are in place, that personnel will be available for training etc.) and installation of software on-site, and training site personnel in system operations and re-engineered processes.

The Software Provider will provide integration for the selected software to existing military systems, such as Subsistence Total Order Receipt Electronic System (STORES Web), Defense Agencies Initiative (DAI) financial accounting system, The Marine Corps Total Force System (MCTFS), Naval Identity Services (NIS), Defense Automatic Addressing System (DAAS), Joint Staff J4, OSD Advanced Analytics (ADVANA), and any Point-Of-Sale systems (POS) already in use. The POS system will be used by Marine Corps locations to capture customer information from the Common Access Card (CAC) as well as support nutrition education and post meal consumption. These locations include garrison mess halls and field operations at various locations around the world. The POS will use a card reader or scanning device to capture and store meal information of the customers’ status, customer category and payment method and required data from military service members’ identification cards.

The Software Provider also may need to develop and integrate software extensions to COTS software in order to provide required functionality not available “out of the box.” The Software Provider will establish and verify interfaces among all systems. The Software Provider will provide a standard communication interface that satisfies the requirements of garrison and deployed sites and can be used in conflict as well as peace. The Software Provider will be responsible for supporting any tool or software integrated with COTS. Support will include maintaining current browser software, operating system software, and technology.

Because the Food Management system will be based on COTS software, the processes employed in developing and implementing system will be in compliance with the DoD Directive 5000.1, the Defense Acquisition System, DoD Instruction 5000.2, and Operation of the Defense Acquisition System, the Defense Acquisition Guidebook, and the Enterprise Integration Toolkit. The Government and Software Provider will work as a team to accomplish the tasks directed in the referenced documents.

The Software Provider shall define and document the architecture that will support the Marine Corps Food Management Information System solution (MCFMIS). This shall include the hardware, software, communication networks, interfaces and connections to existing DoD infrastructure that are required to deliver MCFMIS functionality.

The Software Provider will define the platform for MCFMIS Local and MCFMIS Enterprise; the Government will purchase the hardware. The Software Provider will identify and install the platform for all MCFMIS Local sites. The Software Provider will identify and, if necessary, assist with installing the hardware specific to each location for MCFMIS Enterprise. The Software Provider is responsible for installing MCFMIS Enterprise and ensuring connectivity via the Internet to the enterprise from user workstations. The Software Provider will be responsible for ensuring that the MCFMIS site and Enterprise implementations (including COTS products, extensions, interfaces, third party hardware and software) work and interoperate in the DOD/THE MARINE CORPS infrastructure.

The Software Provider will be required to perform testing on the system to verify that it functions as required prior to deployment and support the required user acceptance and independent verification testing, and also to provide the system architecture and hardware configurations required for various customers (e.g., multiple dining facilities linked on a single base, stand-alone facilities, etc.). The Software Provider will ensure that the system architecture for MCFMIS is compatible with The Marine Corps’ system architecture. MCFMIS and its associated processes must be designed to incorporate all of Class 1 logistics support into The Marines Corps’ strategic vision.

The Software Provider also will be responsible for re-engineering the business processes used in the Marine Corps mess halls so that they work in concert with the MCFMIS automated system to provide uninterrupted, efficient Class 1 logistics support. The Software Provider shall also be responsible for Change Management activities to facilitate acceptance of MCFMIS by the Marine Corps leadership and the end users. The Software Provider will provide on-site training in the automation system and the business processes to the various personnel supporting food service at the military sites.

The Software Provider will provide help desk support as the system is deployed.

The software Provider shall provide, configure, and utilize a specialized, enterprise-grade Software Data Migration Tool (the "Migration Tool") to facilitate the extraction, transformation, validation, and loading (ETL) of legacy data from the legacy environment to the target modernized environment.

The Migration Tool must support automated data mapping, schema conversion, data validation, and automated error logging. The scope includes tool acquisition/licensing, installation, configuration, testing, production execution, training, and subsequent handoff or de-provisioning of the tool.

All artifacts and documentation produced in support of this program will be the property of the Government

3.1 Business Strategy

The Software provider will be responsible to the Marine Corps for deploying the software. Specific responsibilities include (but are not limited to):

· Performing all aspects of development, integration, and deployment of the system.

· Performing process re-engineering for existing business practices to best leverage commercial best practices and the advantages of the COTS systems.

· Ensuring and validating the system satisfies all identified requirements.

· Ensuring compliance with applicable information assurance and financial management requirements.

· Performing support of the production system, including help desk, technical support, training, and transition support.

· Performing all required data conversions and system migration to deploy each Marine Corps site.

· Providing support for all Food Management software through full operational deployment.

The Marine Corps will be responsible for ensuring the Software provider has access to the information and expertise necessary to understand the system requirements. The Marine Corps will also provide oversight of the program execution, including periodic reviews of life cycle artifacts.

Because the software will be based on COTS food management software, the processes employed in developing and implementing the entire system will be in compliance with the DoD Directive 5000.1, the Defense Acquisition System, DoD Instruction 5000.2, Operation of the Defense Acquisition System, and the Defense Acquisition Guidebook.

The Software provider shall define and document the architecture that will support the entire food management software solution. This shall include software, communication networks, interfaces and connections to existing Marine Corps infrastructure that are required to deliver the functionality.

The Software provider will define the platform for the Local and Enterprise solution; the Marine Corps will provide the hardware. The Software provider will identify and install the platform for all Marine Corps Local sites. The Software provider is responsible for installing the Enterprise and ensuring connectivity via the Internet to the enterprise from user workstations. The Software provider will be responsible for ensuring that the Marine Corps sites and Enterprise implementations (including COTS products, extensions, interfaces, third party hardware and software) work and interoperate in the DOD/USMC/MCEN infrastructure.

The Software provider will be required to perform testing on the system to verify that it functions as required prior to deployment and to provide the system architecture and hardware configurations required for the Marine Corps (e.g., multiple mess halls linked to a single base, stand-alone facilities, etc.). The Software provider will ensure that the system architecture for MCFMIS is of the Government.

3.2 Core Food Management Functions

The Marine Corps has identified core functions that must be available in a system to support food management operations. The following table provides a brief description of each function/process.

Core Food Management Processes

a. Green: Less than or equal to 30% of calories from total fat AND less than or equal to 10% of calories from saturated fat.

b. Yellow: 31-49% of calories from total fat OR 11-15% of calories from saturated fat.

c. Red: Greater than or equal to 50% of calories from total fat OR greater than or equal to 16% of calories from saturated fat.

The software shall manage recipes. The current edition of MCO 10110.42B Armed Forces Recipe Service (AFRS) contains approximately 1,500 standardized recipes to be used for the requisitioning and preparation of food for the mess hall menus. The AFRS also provides general information, conversion charts, and equipment guidelines to assist with food preparation. In addition to AFRS recipes, local recipes may be used in menu development. The software must provide for storage and use of recipes in menu development. The Government will be responsible for the addition, deletion, or modification of all recipes within MCFMIS.

The software shall determine the amount of subsistence to be requisitioned and create orders which interface with Defense Logistics Agency (DLA) Subsistence Total Order and Receipt Electronic System (STORES). The process to calculate orders should be based on headcounts associated with menu items within a user-specified date range, against the amount of subsistence on-hand and the amount to be used in production between the time of requisition and its delivery to the mess hall. The calculated order amounts are then held for review and modification. Once orders are validated, they should be locked and sent electronically from the mess hall to the food service office. The software shall validate receipts. True billing documents and receipts posted by mess hall must be reconciled between the food service office and the mess hall. Previous plus current quarter’s documents related to this reconciliation must be retained.

The software should create a report that provides a list of all recipes and various portion sizes required for production of selected menus, meals, and dates. The report will be printed by production area, and for each meal period. Exceptions will be non-rotational salad bar items (i.e., raw vegetable relishes), beverage bar, and condiment/bread bars. These reports can be printed. Reports should be capable of reflecting current recipe changes. Once the products and quantities have been prepared and served, information on leftovers will be entered for meal history and use in future forecasting.

The software shall provide a report to show break out requirements for all items necessary to produce the selected menu and meal. The software shall be able to provide a separate breakout list for each production area and one consolidated breakout list. Mess halls will print a separate report for each production area.

The software shall provide a report showing an advance listing of items and quantities required for advance preparation for specific dates and meals. The report will be used daily, not only for the produce requirements, but for the meat breakouts as well. The report should be able to assign a sub-group to each individual food item and capable of separating all individual requirements by product and meal.

Under the Prime Software Provider concept, subsistence items are delivered directly to the mess hall or field site. All subsistence items and receipts found to be incorrect must be identified to the food service office or rations warehouse via the software for development or modification.

Inventory history of subsistence items shall be tracked by the software. The software must be able to conduct a physical inventory and print a report that calculates the extended dollar value of all items in stock and create an inventory list to be used for inventory purposes. When the list is filled out, the amounts on-hand are entered into the system, and an inventory cost report can be printed out. Inventory list should include all storage locations, Software Providers, active and inactive items. The inventory must be capable of being adjusted to correct discrepancies.

The software shall provide a Daily Cost Analysis (DCA) report. The DCA report must be generated for each day the mess hall functions and for any date inventory is received, issued, or transferred. All transactions posted to inventory related functions are recorded in the history file and are effective for the date in which the user posted each transaction. The Software Provider shall provide a complete, daily review of the data contained in the DCA in order to reconcile and reflect the dollar value of items available. Full review of the data contained in this document is required and will assist in identifying the value of items presently in actual/potential problem areas.

The software shall provide a Headcount Report. The headcount data will be sent to the food service office electronically daily.

The software shall provide for the Subsistence Operational Analysis Report (SOAR). The use of the SOAR is mandatory. Full SOAR requirements are listed in MCO 10110.14N.

The Marine Corps owns and operates a Cook Chill Production Center (CCPC) located in Okinawa, Japan, which will be set up as an internal Software Provider within Okinawa’s consolidated food service system. The MCFMIS software must account for the CCPC production and interaction with OCONUS facilities.

The software shall produce product labels for each container (bag) of food. The product label will indicate the product name, date of packaging, and expiration date of each product. More information can be manually added to the label in a provided field on the label, such as proper storage temperatures, instructions for re-therming, or left over handling procedures. The software system shall have the capability to upload the standard local and production recipes for each product produced at the CCPC into MCFMIS, to be available for both the mess halls and the CCPC.

For the purposes of financial reporting, the CCPC will be incorporated into Part I of the Consolidated Food Service System SOAR. The CCPC will utilize the software to establish and maintain completed product selling prices. Within the software, each completed product should have a selling price. Food Service and Subsistence Branch has established a standard formula. This formula is based on the actual food cost of the raw ingredients used to prepare each item.

The software shall support a Point of Sales (POS) system. POS is designed to replace the manual signature headcount and cash collection procedures (NAVMC 10789 and NAVMC 10298). The POS was implemented as a joint enterprise level solution which will interface with the Marine Corps Total Force System (MCTFS) and provide the tools necessary for a paperless and cashless environment. The system will incorporate card scanners and readers to read the DoD RAPID's Common Access Card (CAC) for patron identification and entitlement verification and credit card devices, to process credit card transactions. POS terminals will also be used to record cash and credit card collections by authorized paying personnel.

The software shall support required administrative personnel and payroll systems processes; establishing a means for payment data to be exchanged between the software and MCTFS. The POS will also include the ability to track the required patron headcount and meal service data to support the Commandant's Fueled to Fight™ initiative. Actual headcount data will be retained in the system for later use in determining acceptability factors, for generating ration credits, and in forecasting the number of personnel that will subsist in the mess hall. All Marine Corps personnel with a DoD CAC (bar-coded on front) will be required to scan their cards via the barcode scanner at the POS station, regardless of the meal entitlement. The scanning of the CAC will capture a headcount for reporting and budgeting purposes.

This process also facilitates in identifying the patron's meal entitlement. When the CAC barcode is read by the POS software, it will determine whether the patron should pay for the meal (BAS) or is authorized to subsist at Government's expense (SIK-Meal Card). The system will generate the patron’s meal entitlement based on the information provided by MCTFS, downloaded and distributed to each Marine Corps’ POS terminal. The system generated meal entitlement may be overridden by the mess hall Meal Verification Supervisor/Cashier on an individual meal basis if the CAC holder shows proof that a different meal entitlement is authorized.

Cashiers can look up a patrons Electronic Data Interchange Personal Identifier (EDIPI) for those patrons with an unserviceable/unreadable CAC barcode by manually keying in for validation. Patrons that cannot be validated against the POS application will be required to pay unless proof that a different meal entitlement is provided. Patrons from other services will be required to provide proof of meal entitlement via their respective services' provided Meal Card, DD Form 714 or any other authorized proof of meal entitlement.

The NAVMC 10789, Meal Verification Record will be replaced with the software Report. This will be the basic record for accounting for personnel authorized to subsist at Government expense and documenting those personnel that are in a cross service or payroll deduction status. Upon deployment of the POS, the NAVMC 10789 will be obsolete in garrison mess halls, and should only be utilized if software is not operational.

The configuration, location and number of stations are determined by the number of personnel served, food delivery methodology, and the type of command and building design. These factors should all be considered prior to the determination of the POS configuration. The POS is designed to operate in two different configurations. Commands will utilize the below criteria when determining the appropriate configuration for their facilities.

Check-in: (Intended to be used at MCRD's and/or TECOM environments). The mess hall cashier(s) will be located near the mess hall line entrances, with a conspicuous sign displayed near this position to inform personnel not entitled to eat at government expense to pay for all meals consumed. This sign will list the current meal rates for each meal.

Check-out: (Intended for most Garrison Base and Station Mess hall Operations). The mess hall cashier(s) will be located at the end of the serving line, with a conspicuous sign displayed near this position to inform personnel not entitled to eat at Government expense to pay for all meals consumed. This sign will list the current meal rates for each meal.

When personnel are in a status that requires mass feeding within a specific time frame, such as recruit feeding and Officer Candidate School (OCS), meals will be accounted for using group feeding (block signature) procedures. Users will be able to export data to software and the food service office schema and export transaction details to a CAC schema for eventual exporting to MCTFS. Software will have the ability to automatically transfer data on a daily basis at a regular time.

The Software shall include a custom report to support operations at United States Marine Corps Logistics Base Albany, GA. The functionality will allow USMC to generate a report that will be used to pay the food service contractor at Albany for feeding Subsistence in Kind (SIK) Marines. Below is a list of the requirements for this report:

· Report shall be structured like as an invoice report and shall be for meal entitlements only.

· Contract price that the USMC will pay per Marine shall be entered in the report setup and shall not be stored historically in the database.

· Users shall be able to enter the contract price for the following meals: Breakfast, Lunch, Dinner, Breakfast Brunch, and Dinner Brunch in the report setup.

· Contract price shall be retained from the previous time the report was generated.

· Report shall have the capability to be run for a specific date/meal range.

The software shall include an enhanced bulk meal process designed to make the bulk meal process easy for all applicable users. The bulk meal process involves the creation of bulk rosters in the back office that will be available for cashiers at the POS register. Changes in the Bulk Meal Process should be limited to maintain integrity of audit but flexible enough to make last-minute changes such as increase or decrease to number of personnel on the roster. The new ROM/SIQ process should include a way for commands to account for SIQ/ROM meals that are requested after hours may not be pre-approved. The process should include additional functionality that allows the cashier to enter or change the following at the register:

· Total number of meals picked up

· Select any existing Armed Services Branch and Components

· Payment type (default to SIK and must be changed for cash payment)

· Choose Traditional, Box Meal, or Field Chow Support type

· Enter Group Leader/POC contact information (email address or Phone Number)

The process should include the ability to be turned on or off in the back office by security within a terminal group and when on, allow the transaction to be initiated at the register. All resulting SIQ/ROM register transactions should be identified in the POS back office with an Attention Status. The process should include a way to allow a POS back-office user to backfill patron EDIPI in the SuitePoint!Point-of-Sale POS back office program, for all unplanned/last minute SIQ/ROM bulk meal request. The process should include a way for a designated POS back-office user to view group leader POC contact information entered at the POS register.

Additional reporting requirements are needed to identify the total number of ROM/SIQ meals processed. The report should have the ability to sort by Mess Hall and by Base. A separate report or category to identify the number of SIK/cash payments, by installation, by mess hall is required. This information will be used to assist the Marine Corps with identifying the total number of SIK meals served compared to the total number of SIK entitlement holders available in a given location/installation to include MCTFS MEAL_CARD_ENTITLEMENT as an ETL. This should give the report a reference point between the number of reported SIK from the POS compared to the number of available MEAL_CARD_ENTITLEMENT flagged as Y in the MCTFS file. All unplanned/last minute SIQ/ROM bulk meal request shall be reported on the existing applicable MCFMIS Headcount, Cash Reimbursement and Other Than Cash Reimbursement report. All unplanned/last minute SIQ/ROM bulk meal request shall be reported on the existing applicable POS back-office Meal Activity report.

· A Meal Activity Report that contains vital headcount information without sensitive information such as EDIPI: The new report will contain similar information as the current meal activity report but will be in a section of the BackOffice that is accessible by the Contractor.

· Modification of permissions to Transaction console to verify headcounts but limit access to sensitive information such as EDIPI: The console will be in a section of the back office that is accessible by the Contractor who has a CAC. This will allow contractor personnel to safely view headcount information without having access to sensitive information.

· Specified POS register administrators need to approve or deny certain transactions conducted at the register: POS register administrators must be able to approve some register processes. New permissions may be required when looking for a Marine, selecting reimbursable collection, and processing refunds.

· Process to improve and streamline sending headcounts and reviewing and printing meal activity reports: Transaction console and meal activity report should include the ability to send headcounts for multiple days.

The software shall provide the Marine Corps specific Class I data which will show what Class I items are on-hand; by items, location, lot number, initial test date and quantity. Data will be transmitted via interface to allow for real-time information to Joint Staff (J4) software program once developed. The interface will be developed based on an agreed upon interface method between Software Provider and Government.

The software shall provide a module to automate exercise closures, allow for MEF to MEF transfers, present budget forecasting data into useful information from a BI standpoint, track unbudgeted exercises, and allow for changes in the special meal request (SMR) submissions. Additionally, the following shall be delivered in the Accounting Pro Module:

· Enhancing MEF to MEF transfers to include MSC to MSC and rations turn in (returns) between exercises and Ration warehouses

· Separations of duties (separate Order approval for funds check and STORES)

· Ability to search for Purchase Order numbers(PO)

· Ability to see the PAX and Enhancement Budget info of exercises

· Add Exercise ID to search parameters in the Field MCFMIS dialog software.

· Add a DAI dashboard to view and meet DOD CUEC 10 order and receipt data transmission statuses between MCFMIS, Field MCFMIS, Reserve MCFMIS and DAI).

· The ability to track both unbudgeted and cancelled exercises

· A streamlined process for cancelling exercises (i.e. automatically remove required rations and budgeted amount and track the original approved budget requirements)

· Ability to upload and link STORES Sent Order and Sent Receipt reports as Supporting documentation for MCFMIS and FMCFMIS Purchase Orders (include hyperlink to PO’s

The software shall include a module that will take information in the data warehouse and allow for creation of reports to support BI and dashboards at multiple levels of the organization (HQ, MEF, and MSC). Information and reports should be capable of being extracted in Extract, transform, load (ETL) format.

The software shall include a module that will allow barcode creation to streamline inventory processes and ensure inventory accuracy. Bar codes shall be used to receive, issue, account for signature, track lot numbers, initial test date, date of pack, and national stock number. Information shall be capable of being scanned and used with handheld hardware devices such as a tablet.

Additional Software engineering support shall be required to strategically implement enhanced capability to support a more streamlined, user friendly and intuitive design; as well as establishing a new Business Intelligence (BI) and dashboard-related reporting system. Enhanced reporting will consist of utilizing existing reports and creating new ADHOC reports that are restricted to data specific to certain organizational entities (e.g., HQ, Bases, Mess Halls, MEF, MSC, Exercises, etc.), as requested by the Government. The dashboard will incorporate a graphical interface which provides at-a-glance views of key performance indicators, identified by the Government, and may change based on current mission requirements, as well as relevant stock levels. Data shall be analyzed via analytical software. Dashboards will include inventory on-hand levels, cost of inventory, inbound inventory, outbound inventory, headcount, and be capable of adding additional reporting criteria such as inventory close to expiration.

3.3 System Interface Requirements

The proposed solution will address all system interfaces required to support the MCFMIS requirements. These include but are not limited to:

· Defense Agency Initiative (DAI) an automated financial system operated by the Marine Corps

· Defense Enrollment Eligibility Reporting System (DEERS) or

· The Marine Corps Total Force System (MCTFS)

· Subsistence Total Order and Receipt Electronic System (STORES) an automated ordering system operated by DLA

· Defense Automatic Addressing System (DAAS)

· Naval Identity Service (NIS) Identity Credentialing and Access Management (ICAM)

A key objective for the Food Management system will be to limit the number of physical interfaces required (e.g., utilizing a central hub or component of the system to accomplish most interfaces) to facilitate system maintenance. The Software provider should allow for up to two additional bi-directional interfaces and one additional one-way interface for MCFMIS. Those interfaces should be priced separately.

3.4 Security Requirements

The Software provider will outline an approach to gaining security accreditation. The Software provider will be responsible for working with the Marine Corps to ensure that the Food Management system will be a certified and accredited system complying with all security and information assurance requirements The Software provider shall work with the Marine Corps to ensure the system is certified and accredited as defined in the Risk Management Framework (RMF) standards, guidelines and policies, prior to being deployed The current MCFMIS has been classified as a Mission Assurance Category (MAC) III system in terms of availability and integrity, with a confidentiality of Sensitive but Unclassified. The Software provider shall provide input for an applicable Continuity of Operations Plan (COOP).

The Software provider shall support the government in reviewing the potential threats and vulnerabilities to proposed system architecture and implementation and assist the government in executing a robust and comprehensive system Security Testing and Evaluation (ST&E) process to ensure system design and implementation meet the established security requirements.

The Software provider shall provide recommendations for threat and vulnerability mitigation, to bring the level of risk to the Marine Corps Enterprise Network (MCEN) to an acceptable level to the AO. This analysis shall be conducted by means of architecture review, documentation review, security scanning and scanning results review, and configuration verification.

The Software provider shall provide risk analysis documentation in accordance with DoD policy that shall form the basis of an accreditation recommendation to the government.

The Software provider shall ensure that the system complies with the Security Technical Implementation Guides (STIGs). The Non-Secure Internet Protocol Router Network(NIPRNet) URL for the Information Assurance Support Environment (IASE) site is http://iase.disa.mil/.

3.5 Federal Financial Management Requirements

The Food Management System shall also comply with the Financial Improvement and Audit Readiness (FIAR) of 2017, meeting the standards set forth in the DFAS 7900.4-G Guide to Federal Requirements for Financial Systems. The Food Management System shall not be a financial management system, but must comply with the standards for a financial feeder system. The MCFMIS acquisition must comply with OMB Circular 127, which requires that software purchased be tested and certified in accordance with the FIAR. OMB Circular No. A-127 specifically prescribes policies and standards for executive departments and agencies to follow in developing, operating, evaluating, and reporting on financial management systems. The FIAR requirements specifically state that Agency financial management systems shall conform to existing applicable functional requirements for the design, development, operation, and maintenance of financial management systems.

Functional requirements are defined in a series of publications entitled Federal Financial Management Systems Requirements. Access to the Business Management Modernization Program, which oversees the FIAR requirements, can be accessed from a .mil or .gov address at http://www.dod.mil/comptroller/bmmp/pages/.

The Contractor shall work with the Marine Corps to ensure that MCFMIS is FIAR-compliant prior to deployment. The Contractor shall be responsible for delivering to the Government documentation supporting FIAR compliance.

3.6 Software Requirements

The food service management COTS, proposed for use in support of MCFMIS, will be selected from the Federal Supply Schedule. The software provider must specify the number of copies and/or licenses required for deployment at each site. The Government will purchase the selected software using the Federal Supply Schedule. The Software provider will be responsible for ensuring that the COTS software and any needed extension development will satisfy the requirements for MCFMIS.

The Software provider will be required to provide the data rights for all interface applications, as well as any external applications such as a deployable support extension that may be developed for the Food Management System. The Software provider is responsible for maintaining any interfaces and software extensions throughout the life of the program and ensuring they are incorporated and continue to function with new releases of the COTS software.

Field units also will be supported. The need to support food management operations in an unconnected mode is an important requirement for MCFMIS. The Software provider will be responsible for exploring flexibility in licensing to allow for successful integration of Field or deployable units with their land-based parent units. The Software provider will describe a licensing solution that reflects the operational constraints associated with connected and unconnected units to allow for additional instances or licenses. The Software provider will provide pricing in the technical proposal for the purchase and maintenance of licenses required to support the system architecture.

The software purchased to support the Food Management system has to be able to operate on a system that meets the information assurance standards. Information regarding information assurance requirements can be found in Defense Logistics Agency’s Information Technology Solutions dated December 2003 and in DoD Instruction 8500.1, Information Assurance, dated November 21, 2003. MCFMIS will be installed on the Windows operating system and must be capable of interfacing with systems via web browser.

3.7 Hardware Requirements

Government will be responsible for providing the hardware to the customer sites.

3.8 Deployment Plan

The Software provider will develop a plan, showing resources and schedule, for installing and implementing MCFMIS. The plan will be a deliverable and will be required at least 60 days prior to the beginning of deployment. The Software provider will identify training, Operational Test and Evaluation (OT&E), and support needed to ensure each site is integrated successfully. The Software provider will also need to provide input to a MCFMIS Program Integrated Support Plan.

3.9 Training and Knowledge Transfer

The Software provider will be responsible for all aspects of training and will be required to develop training materials for installing, maintaining, and using the system. This will require close coordination with the Marine Corps.

The Marine Corps anticipates six scenarios for training: training users at a typical CONUS dining facility; training users at an OCONUS dining facility; training for users operating in a field environment; training materials for users at the Train the Trainer course; training users during Sustainment training, and training materials to be used in military schoolhouses. The Marine Corps require that training on the Food Management System be provided at the Marine Corps Food Service schoolhouse operated at Fort lee, Virginia, Train the Trainer course, and Sustainment training onsite and via web-based platform. The software provider will prepare an instruction curriculum, demonstration software, and hands-on training environment along with an instruction guide, to be used during these trainings. This training package will be provided to the Food Service schoolhouse and the Marine Corps Food Management Information System Contracting Officer Representative after the demonstration period, after the Marine Corps has determined that Food Service Management System is ready for implementation. This curriculum will be updated as needed to remain current with the systems and procedures in operation in the dining facilities and field locations.

The Marine Corps will provide the number of sites requiring training and the number and type of participants who require training as the sites are identified for deployment.

The Software provider will provide training and user manuals for MCFMIS and will update them as required to support new releases/enhancements to the software.