SSN_ADCFAS_Enclosure_1_PWS_DRAFT_10Sep26.pdf

PERFORMANCE WORK STATEMENT

FOR

FINANCIAL AND ADMINISTRATIVE SUPPORT SERVICES

HEADQUARTERS UNITED STATES MARINE CORPS

ASSISTANT DEPUTY COMMANDANT FOR PROGRAMS AND RESOURCES (ADC P&R)

Dated 10 September 2026

CHANGE LOG

This record shall be maintained throughout the life of the document. Each published update shall be recorded. Revisions shall be incorporated via a bilateral contract Modification.

CHANGE / REVISION RECORD

Date Page/Paragraph Description of Change Made By:

10-Sep-26 N/A Initial Publication TM

1.0 BACKGROUND

The Assistant Deputy Commandant for Program and Resources (ADC P&R) has cognizance over numerous subordinate ADCs including the Resources Fiscal (RF), Resources Budget (RB), and Programs (RP). Each of these ADCs has cognizance over various offices/divisions and/or subordinate branches.

The ADC RF specifically has cognizance over the Fiscal Division (RFD) which oversees the Accounting and Financial Systems Branch (RFA); Finance Branch (RFF); Managers Internal Controls (RMIC); and Marine Corps Non-Appropriated Fund Audit Services (MCNAFAS) as well as the Systems and Data Integration Division (SDI) which oversees the Integration Branch (RSI); Systems Sustainment Branch (RSS); Data Governance, Automation, and Reporting (RSD); and Execution Operations Branch (RSX).

SDI was stood up on 16 Sept 2024 as part of a phased P&R reorganization which consolidated existing financial systems and data functions into a dedicated division to oversee USMC DAI Program Management, provide data and automation services, and ensure the Marine Corps maintains its unmodified audit opinion.

The RFD Branches are further detailed as follows:

(a) Accounting and Financial Systems Branch (RFA)- The RFA Branch’s mission is to “support warfighting excellence through a strong business enterprise that is powered by accurate, timely, and relevant financial information and drives validated and defendable financial statements; oversee all matters pertaining to General Fund accounting policy, financial accounting, analysis, and reporting, and accounting information systems to support Marine Corps activities and operations worldwide; and provide technical advice and assistance to the Fiscal Director of the Marine Corps, the Deputy Commandant for Programs and Resources, and the Commandant of the Marine Corps (CMC), to enable informed financial decisions.”

(b) Finance Branch (RFF)- The RFF Branch serves as the primary advocate for Marine Corps disbursing operations ensuring the community is resourced with clear guidance, training, manpower, and enterprise system solutions in order to support deployed and garrison mission requirements while achieving sustainable clean audit opinions.

(c) Managers Internal Controls (RMIC) Branch – The RMIC Branch manages policy development, training, education and reporting requirements for the Managers Internal Control Program (MICP), Enterprise Risk Management (ERM) and Integrated Risk Management (IRM), Financial Management Evaluations and Assessments (FMEA), in order to ensure effective and efficient internal controls and risk mitigation processes are in place.

(d) Marine Corps Non-Appropriated Fund Audit Service (MCNAFAS) Branch – The MCNAFAS Branch provides the CMC, commanders, and managers with independent and objective value-adding audits of Marine Corps Non-Appropriated Fund Instrumentalities and other entities, as directed by CMC.

The SDI Branches are further detailed as follows:

(a) Integration Branch (RSI) - The Systems Integration Branch develops and manages the Marine Corps’ financial and accounting business and data architectures and coordinates with relevant stakeholders to integrate with feeder system processes and data.

(b) Systems Sustainment Branch (RSS) - The System Sustainment Branch oversees all DAI interfaces impacting USMC operations, provides Tier 1 Helpdesk services, manages account provisioning and terminations to ensure that updates to the DAI system meet operational needs without unintended consequences.

(c) Data Governance, Automation, and Reporting (RSD) - The Data Governance, Automation, and Reporting (RSD) Branch is to enforce robust governance and financial compliance through rigorous access monitoring, dashboard tracking, and audit-readiness frameworks. We actively leverage AI and automation to modernize processes, optimize resource management, and drive operational efficiency. By delivering standardized, data-driven reporting and fostering professional development, we empower leadership with actionable insights for strategic decision-making.

(d) Execution Operations Branch (RSX) – The Execution Operations branch facilitates enterprise level analysis of abnormal accounting conditions to inform focused budgetary decision-making, administers and oversees dormant financial transaction reviews and reporting, conducts post-review analysis to inform senior leader engagements with commanders, develops error resolution policy and fiscal year closeout and open up guidance, and provides training to field commands. The Budget Analysis branch serves as the Budget and Execution division director's holistic analytical capability to identify trends which transcend appropriation boundaries.

ADC P&R, RF Division Director, RFA Branch, and SDI have a requirement for contractor support services as set forth within this PWS.

1.1 RFA BRANCH COMPOSITION

The RFA Branch is made up of the following four sections:

(a) General Ledger and Trading Partner Reporting (GL): This section:

(1) Support monthly financial closeout.

(2) Perform quarterly trading partner reconciliations and eliminations;

(3) Review monthly and quarterly DFAS prepared journal vouchers.

(4) Conduct quarterly financial statement variance analysis and develop narratives to support material variances; and

(5) Assess lessons learned to inform property reporting process improvement initiatives.

(b) Data Integrity (DI): This section:

(1) Prepares standardized and ad hoc accounting reports to support scheduled and unscheduled accounting analysis, research, and reporting; and

(2) Assess lessons learned to inform property reporting process improvement initiatives.

(c) Property Reporting (PR): This section:

(1) Coordinates with external stakeholders to obtain offline quarterly property and facilities data to inform financial statement reporting;

(2) Supports full financial statement audit requirements; and

(3) Assess lessons learned to inform property reporting process improvement initiatives.

(d) Reporting and Compliance R&C): This section:

(1) Compile the annual agency financial report;

(2) Compile quarter three and four OMB Checklists;

(3) Update the annual entity profile;

(4) Supports environmental and contingent legal liability assessments and reports financial impacts;

and

(5) Assess lessons learned to inform property reporting process improvement initiatives.

1.2 RFA BRANCH MISSION

To accomplish its mission, the core RFA functions include:

(a) Developing and publishing financial management and accounting policies, processes, and procedures to include Marine Corps Orders and Bulletins, policy memos, standard operating procedures, desktop guides, and system user manuals to effectively communication reporting requirements to the Marine Corps enterprise;

(b) Developing and publishing quarterly and annual financial statements to document the Marine Corps’ financial status at designated points in time as directed by federal laws and regulations and to report to the American taxpayer an accurate representation of executed funds supporting the Commandant of the Marine Corps Title X responsibilities;

(c) Supporting annual full financial statement audits through timely and accurate data retrieval from the core accounting system Defense Agency Initiative (DAI), Marine Corps-centric processes, systems interface training/instruction to the auditors, documentation management, Provided-by-Client (PBC) response development and review, and audit liaison support.

1.3 SDI MISSION

The mission of the SDI Division is to ensure the Marine Corps maintains its unmodified audit opinion, consolidates financial systems and data functions, and integrates data/systems across various business processes. The SDI Division gives a dedicated home for the USMC Defense Agencies Initiative Program Management, distinct from budget or fiscal responsibilities. It will offer data and automation services and ensure the effective implementation of DAI Complementary User Entity Controls (CUECs).

2.0 SCOPE/OBJECTIVES

The Contractor is required to provide a variety of support for the ADC P&R, RF Division Director, RFA branch, and SDI in the following areas, as applicable:

(1) Contract/Project Management Support;

(2) Financial Systems Support;

(3) Administrative Assistance for Senior Leaders, the RFA and SDI Branches;

(4) RESERVED; and

(5) Financial Audit Assistance.

See Section 5.0 for specific tasks.

3.0 GOVERNMENT FURNISHED RESOURCES

The USMC will not issue Government-furnished property for this effort. However, the USMC will make available the following resources to the Contractor in performance of the contract:

(1) Access to systems referenced in PWS 5.0. Access will be required via the Marine Corps Enterprise Network (MCEN-N), which requires a Common Access Card. The Contractor shall coordinate with MCICOM to obtain a CAC.

(2) Access to documents required to support execution of this PWS.

(3) In the performance of this effort, the contractor will be provided documents, data, computer source code, and software for program upgrades, but not to include hardware components (i.e. monitors, CPU, key boards, etc.), as may be necessary to provide the support specified herein.

(4) When work is to be performed in USMC office spaces, the government will provide temporary/rotational workstations with phone and networked printer/scanner availability.

4.0 CONTRACTROR FURNISHED RESOURCES

The Contractor is responsible for furnishing all other resources not listed.

5.0 TASKS

The work tasks for this PWS are described in this section. The Contractor shall provide all necessary program management, quality assurance, and materials to execute each task. In executing the tasks in this section, the Contractor will be required to submit an Enterprise-wide Contractor Manpower Reporting Application (ECMRA) Annual Report, an Annual Work Plan, and a Weekly, Quarterly, and Annual Summary Report. The level of effort for these work activities must be respectively allocated with each task in this section in the Contractor’s proposal.

5.1 TASK 1: FINANCIAL SYSTEMS SUPPORT

5.1.1 RESEARCH, REPORTING, ANALYSIS, AND SYSTEM SUPPORT

Contractor will provide financial systems support to enable RFA and SDI to meet mission critical objectives in the areas of financial analysis, mixed-use systems and applications, performance measures and analysis reports advising and development, supporting system and application training, and maintenance, execution, and analysis of existing databases, reports, performance measures, tools, and documentation.

5.1.1.1 WRITTEN RECOMMENDATIONS AND ANALYSIS FOR SPECIFIC ISSUES (WRASI)

When requested, the Contractor shall provide subject matter analysis in a written format (and verbal format if requested by COR) on one or more of the following:

(1) Accurate data interfacing, accrual, and reporting in financial and business feeder systems.

(2) Accurate recordation of financial transactions to appropriate United Stated Standard General Ledger (USSGL) accounts.

(3) Provide advisory services to DC, P&R directed working groups to support internal and external data analytical efforts and data management initiatives.

(4) Regarding dashboard metrics, provide advice on best practices and methods to derive accurate and visually relevant presentations.

5.1.1.2 FINANCIAL SYSTEM DASHBOARD AND REPORTING SUPPORT

Develop (based on COR request), amend (based on COR request), and maintain (a) financial dashboard metrics and (b) existing standardized and ad hoc financial reports from accounting and supporting business intelligence systems to include, but not limited to Beginning Balances, Universe of Transactions, General Ledge Reconciliations and Variance Analysis, Systems Reconciliations, Abnormal/Overaged Accounting Performance Metrics, DAR-Q, and Quarterly and Year-End Certifications, and coordinate the archiving of historical files.

5.1.1.3 RESERVED

5.1.2 RESERVED

5.1.3 DATA MANAGEMENT AND DATA ARCHITECTURE PROGRAM PLANNING

The Contractor shall be responsible for assisting with strategic planning, oversight, and development of necessary policies, directives and technology reporting solutions required to institute and sustain the RFA and SDI data management and enterprise architecture programs. Success in these functions is derived from: 1) a comprehensive understanding of data management concepts that enable the Contractor to provide advice and guidance to senior staff; 2) skills in the use of data management systems with the ability to implement or sustain RFA and SDI policies, directives, and principles governing data management and enterprise architecture to ensure complementary conformance with Marine Corps accounting/auditing and financial management review requirements, guidelines, and objectives; 3) skill in understanding, using, and managing databases and other automated information systems in support of RFA and SDI data management and enterprise architecture needs; 4) knowledge of the concepts, principles, and practices of data management and the technology required to extract data and/or support accounting and mixed-use financial management system implementation or enhancement; and, 5) skill in interpreting data management and enterprise architecture requirements to determine their effects on Marine Corps programs, accounting, and financial management practices.

5.1.3.1 WRITTEN RECOMMENDATIONS AND ANALYSIS FOR SPECIFIC ISSUES (WRASI)

When requested, the Contractor shall provide subject matter analysis in a written format (and verbal format if requested by COR) on one or more of the following:

(1) Provide expert representation to fiscal code working groups and assist with the development of data architecture crosswalks and alignments and support the development of authoritative fiscal code documents.

(2) Provide expertise in complimentary business processes and business systems to validate proposed code change impacts to lateral processes. Participate in associated working groups as needed.

(3) Perform reconciliations of DAI data to complimentary/supporting feeder systems data to ensure recorded transactions interface properly and code alignments correlate as intended.

(4) Recommend policies, directives, and guidelines to ensure enterprise architecture implementation and the uniform application of data management principles, methods, and practices in support of RFA and SDI goals and objectives.

(5) Assist Marine Corps system users in interpreting data management requirements and in applying Marine Corps accounting and financial management policies and guidelines.

(6) Assist external stakeholders such as OSD, DoN, DLA, GSA, GAO, and Independent Public Accounting firms appointed to audit the Marine Corps to interpreting data management requirements and in applying Marine Corps accounting and financial management policies and guidelines as applicable to higher level financial initiatives.

5.2 TASK 2: ADMINISTRATIVE ASSISTANCE SUPPORT

Assignment for contractor support for this task will be assigned by the Contractor’s Program Manager.

Request for all tasks under this task must be provided by the COR or their designee to the Contractor’s Program Manager.

This task contains a variety of administrative support. However, most of the support is support provided to the following Senior Leaders:

(1) The Assistant Deputy Commandant for Programming (ADC P),

(2) The Assistant Deputy Commandant for Resources (ADC R),

(3) The RFA Branch Head (Accounting Officer for USMC); and

(4) The RFA Deputy Branch Head (Deputy Accounting Officer for USMC).

(5) The Fiscal Division Director (RF),

(6) The Deputy Fiscal Division Director (RF).

(7) The SDI Division Director

(8) The SDI Deputy Branch Division Director.

Outside of direct support for the individuals, support is also provided for the RF Directorate, SDI Division and RFA branch.

5.2.1 CALENDAR COORDINATION (ADC P, ADC R, RF AND SDI DIVISION

DIRECTORATE, AND RFA)

Schedule meetings and briefs for ADC P, ADC R, RF Division Directorate, SDI Division Directorate, RFA Branch Head, and the RFA Deputy Branch Head with internal staff members and external stakeholders. In completion of this task, USMC will provide the meetings and briefs that require scheduling to the Program Manager or by completion of a physical or electronic form or other agreeable form of communication, for which the PM must provide oversight. The coordinator will provide a daily binder of events and read-ahead materials to each office supported.

5.2.2 PUBLIC COMMUNICATIONS COORDINATOR (ADC P, ADC R, RF AND SDI

DIVISION DIRECTORATE, AND RFA)

The Contractor must operate an intake call desk service. It must intake ADC, P, ADC, R, RF Division Directorate, SDI Division Directorate, and RFA Branch phone calls. Once the phone calls are answered, the Contractor’s objective is to route each call to the appropriate USMC ADC P, ADC R, SDI and RFA staff member based on the subject matter of the call. Additionally, for calls requesting basic, non-sensitive organizational information, the Contractor must reply with the accurate information.

5.2.3 OFFICIAL TASK COORDINATOR (ADC P, ADC R, RF AND SDI DIVISION

DIRECTORATE,, AND RFA)

The objective of this support is to coordinate the receipt, review, response, and end-to-end tracking of official tasks from the DC P&R and external tasking authorities received via DoN TRACKER, email, MS Teams, or other mediums. This support is directed at ADC P, ADC R, RF Division Directorate, SDI Division Directorate, and the RFA Branch. This is a coordination task and therefore the requirement is for the Contractor to achieve the objective of providing sufficient coordination. Tasks will be received and delegated via electronic routing systems and the contractor PM shall monitor and direct such tasks as appropriate to meet the requirement.

5.2.4 DOCUMENT ROUTING COORDINATOR (ADC P AND ADC R, RF AND SDI DIVISION

DIRECTORATE, AND RFA)

Intake and route to the designated reviewing official information papers, decision memorandums, trip reports, and other correspondence packages routed to (a) ADC P and ADC R and by (b) RF Division Directorate, and (c) RFA branch personnel to division directors, (d) SDI Division Directorate, lateral branches and divisions, and the deputy commandant and assistant deputy commandants. Requests will be provided by the Government by to a task inbox controlled by the Contractor, and for which the PM must provide oversight.

5.2.5 OFFICIAL GUEST PLANNER (ADC P, ADC R, RF AND SDI DIVISION DIRECTORATE,

AND RFA)

Coordinate the arrival of official guests for meetings with ADC,P and ADC,R, RF Division Directorate, SDI Division Directorate, and the RFA Branch. Maintain a visitor log to ensure accountability of guests at all times. The Government will identify the visitors that require the guest planning services. At all times, the contractor must identify himself or herself as contractor support to arriving guests, as well as in any telephone calls or electronic communications. The contractor will maintain a guest log for all visitors to be reviewed weekly by the PM and available to the government as needed.

5.2.6 OFFICE SUPPLY INVENTORY MANAGER (ADC P, ADC R, RF AND SDI DIVISION

DIRECTORATE, AND RFA)

Assist with researching the procurement of office supplies and track the inventory of office supplies and equipment, as authorized by ADC P, ADC R, RF Division Directorate, SDI Division Directorate, and the RFA Branch. Maintain an accountability log for ADC and RFA/SDI information technology assets and other high dollar assets and conduct monthly accountability inspections to include identifying unauthorized equipment such as wireless computer keyboards and mice. These task are performed for not only the executive, but also at the RFA/SDI branch level.

5.2.7 CALENDAR COORDINATOR (RF AND SDI DIVISION DIRECTORATE, RFA)

For the RF and SDI Division Directorate and RFA branch, ensure the shared calendars for phone line and meeting space reservations and employee accountability are properly functioning and complete scheduling of collaborative meetings on an ad hoc basis. The Contractor must review the shared calendars on a weekly basis and report significant issues in the weekly summary report.

5.2.8 PERSONNEL ONBOARDING AND TERMINATION COORDINATOR (RF AND SDI

DIVISION DIRECTORATE, RFA)

For the RF and SDI Division Directorate and RFA branch, provide onboarding and departure support of RFA/SDI personnel to include military, civilian, and contractor support. Assist with Welcome Aboard package distribution and arrival planning. Coordinate common access card (CAC) issuance and collection, access and termination to building and office spaces (DD 2249), computer network and system request processing (DD 2875), building orientation, and other related tasks which enable new employees to be productive and properly complete activities for outgoing employees. The type of support will be defined by the Government for each event in a form of communication sent to the Contractor Program Manager, which must be followed for each reoccurrence of the task unless updated by the Government.

At all times, the contractor should identify himself/herself as contractor support to all employees in person, on the phone, and in electronic communications.

5.2.9 FACILITIES MAINTENANCE PERSONNEL ACCESS FACILITATOR (RFA/SDI)

For the RFA/SDI branch, facilitate office inspections by the Fire Marshall, Cyber Security, and other facilities maintenance personnel by ensuring they have the access they need and can reach out to the appropriate P&R personnel for questions. The Government will direct the inspectors to the Contractor for this task.

5.2.10 FIRE EXTINGUISHER MAINTENANCE (RFA/SDI)

For the RFA/SDI branch, conduct monthly inspections of fire extinguishers and annotate completion of the corresponding inspection tags.

5.3 RESERVED

5.4 TASK 4: PROVIDE FINANCIAL AUDIT ASSISTANCE

5.4.1 WRASI - Provide guidance on an ad hoc basis that ensures RFA’s/SDI’s compliance with Treasury Financial Regs, OMB Circulars A-11, OSD Guidance, DoD Financial Management Regulations (FMR), DFAS Guidance, MFMIP/FSIO, DON Financial Guidance, Marine Corps Order 7300-21, FISCAM, and OUSD(C) Directives.

5.4.2 Assist RFA/SDI with coordinating and facilitating “Provided by Client (PBC)” requests and follow-up questions from the auditors, Inspector General, and the Defense Finance and Accounting Service.

5.4.3 WRASI - Assist with identifying and implementing process improvements within the RFA/SDI based on audit findings to strengthen the Marine Corps’ financial statements.

6.0 DELIVERABLES

The Contractor shall provide the deliverables listed in the deliverable table. The Contractor is free to suggest additional deliverables. All deliverables, unless they are events, shall be provided in electronic form only and shall be delivered to the COR by the dates specified below. Additional recipients for deliverables shall be added at the discretion of the Contracting Officer’s Representative or the Contracting Officer.

6.1 DELIVERABLE FORMATTING REQUIREMENTS

Unless otherwise specified by the COR, the Contractor shall deliver one (1) electronic copy with read/write capability of all deliverables. Original source files for any artwork and textual/tabular items must be provided to USMC. Electronic copies shall be delivered via email attachment or other mutually agreed upon electronic medium. The electronic copy shall be compatible with USMC computer workstations, requiring, at a minimum, Microsoft Office 2010 format or a format mutually agreed to by the Contactor and COR. The Contractor shall successfully complete and submit products in accordance with the requirements of each task. Deliverables shall be organized and written clearly. Information shall be accurate and relevant. The USMC will maintain full data rights to all products and deliverables.. The Marine Corps shall have unrestricted access and use of all deliverables upon delivery. The Contractor shall provide all deliverables in a version or media format used/useable and modifiable by the Marine Corps.

6.2 DELIVERABLES REVIEW TIMELINES

The Contractor may submit draft deliverables for review, but only one draft review shall be built into the schedule or work plan. The Government will have seven business days from the date of receipt or the date of the walkthrough, whichever is later, to accept or reject deliverables. If rejected, USMC will provide formal comments, and the Contractor will have five business days to correct and re-submit its deliverable for acceptance.

6.3 DELIVERABLE TABLE

The recipient for all deliverables in the below table is the COR.

Deliverable Description Format Due Date Acceptance Criteria Draft Annual Work Plan (PWS 5.0)

This is the Contractor’s plan for accomplishing all work activities for the current contract year.

MS Word Draft within 2 weeks of the contract and each option’s start date.

The plan must describe the Contractor’s plan for accomplishing all work activities for the current contract year. It must be complete and cover all tasks in PWS 5.0-5.4.

Annual Work Plan (PWS 5.0)

This is the Contractor’s plan for accomplishing all work activities for the current contract year.

The COR will provide comments for the Draft Annual Work Plan deliverable. The Contractor must address these comments and re-submit the deliverable.

MS Word Due within two weeks following receipt of COR comments on Draft Annual Work Plan.

The plan must describe the Contractor’s plan for accomplishing all work activities for the current contract year. It must be complete and cover all tasks in PWS 5.0-5.4. It must address all of the COR’s comments on the Draft Annual Work Plan.

Summary Report

(PWS 5.0)

This report provides the Government with the Contractor’s updates on current, completed, and planned work activities on various intervals depending on the reporting period. Briefings are required for selected iterations of this report.

Microsoft Excel unless otherwise agreed to by the COR.

Narratives for quarterly updates shall be provided in MS Word.

Within one business day of the conclusion of the work week.

The Contractor shall provide HQMC P&R RFA with a weekly report summarizing all work performed, completed, or in progress under this Performance Work Statement.

The report shall address (a) Reporting Week, (b) Work Status, Planned or Unplanned, (c) Date Completed. Additional or alternative data fields may be included with prior COR approval.

For the report on the first week of each March, June, September, December, this report shall also include written narratives that summarizes (a) all work performed and completed over the prior 3-month period and work planned for the next 3-months; (b) all Contractor’s accomplishments for the prior 3-month period; and (c) Problem areas and recommended solutions to include personnel turnover, utilization of sub-contractors, and future staffing projections.

For the report on the 2nd week of January, this report shall also include written narratives that summarizes

(a) all work performed and completed over the prior 12-month period; and (b) major problem areas and/or challenges encountered; (c) and all of the Contractor’s accomplishments for the prior 12-month period.

A briefing describing the report shall be provided by phone or in-person for the following reports: 1st week of March, June, September, December; and 2nd week of January.

Written recommendations

When requested this deliverable shall be

MS Word or Excel based

5-10 business days after request, COR will

The deliverable must (a) address the objectives and and analysis for specific issues

(WRASI) –

(5.1.1.1, 5.1.3.1, 5.4.1, and 5.4.3) provided and the requestor will provide objectives that must be addressed and formatting and content requirements that must be met for each requested written recommendation and/or analysis.

on COR’s request.

determine the deadline between 5-10 days.

formatting requirement provided in the Government’s request and meet the PWS reference requirements (if applicable);

(b) be timely; and (c) recommendations must be supported by detailed, analytical findings and/or industry/military citations (when applicable); and (d) non-compliance with (a) and

(c) are corrected in a revised work product within 7 business days.

Financial and Administrative Support Event Tasks (PWS 5.1.1.2-3, 5.1.2, 5.2.1- 5.2.10)

See PWS 5.1.1.2-3, 5.1.2, 5.2.1-5.2.10.

N/A: event based deliverable.

Support is provided as follows:

- 5.1.1.2: Provide estimated timeline for completion within 2 days;

- 5.1.1.3: Provide the required support on the day the meetings are scheduled provided a 1 business day notice is provided, and support provided outside of meetings must be provided within 5 days of request;

- 5.1.2: Initially assess ticket requirements and route for follow on action as required within 1 day of request;

- 5.2: Within 1 day for all tasks except 5.2.10, which is every 30 days.

All support must meet the requirements identified in

PWS 5.1.1.2-3, 5.1.2, 5.2.1-

5.2.10. Tasks are initiated by

a request from the Government and must be completed timely. PWS

5.2.10 is regular maintenance that must be completed monthly. Tasks for 5.1.2 must fully address each help desk ticket’s concerns or document elevation to the appropriate entity for follow on action as required by

PWS 5.1.2.

Marine Corps Orders and Bulletins (PWS

5.3 (1))

When requested this deliverable shall be provided and the requestor will provide the document objectives that must be addressed.

MS Word 10 business days after request

The deliverable must (a) address the objectives and formatting requirement provided in the Government’s request; (b) be timely; (c) meet the requirements outlined in iSECNAV M-5210.2 (Department of the Navy (DoN) Standard Subject Identification Code), SECNAV M-5215 (DoN Directives Management Manual), MCO 5215 (Marine Corps Directives Management Program), and MCO 5216.20 (Marine

Corps Supplement to DoN Correspondence Manual);

and; and (d) non-compliance with (a) and (c) are corrected in a revised work product within 7 business days.

Miscellaneous

RESERVED

RESERVED RESERVED RESERVED RESERVED

Audit Support

(PWS 5.4.2)

When requested, coordinate answers to PBC requests with necessary stakeholders. This is a one-time annual request for each type of auditor (annual Financial Statement Auditor, I.G., and the Defense Finance and Account Service reviews/audits).

Coordination by e-mail

When requested, conduct the required coordination within 30 days and submit the required answers to the COR for review.

The deliverable must fully address the PBC request and contain correct answers regarding USMC’s financial information.

ECMRA – All of the PWS Tasks

Enterprise-wide Contractor Manpower Reporting Application (ECMRA) Annual Report Submission - The contractor must report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Planning, Programming, Budgeting Execution, and Auditing Support via a secure data collection site.

Contracted services excluded from reporting are based on Product Service Codes (PSCs).

The excluded PSCs are:

W, Lease/Rental of Equipment;

X, Lease/Rental of Facilities;

Website Submission

Annually but no later than October 31st of each year.

Report must be submitted by the deadline and be 100% correct and compliant with the following instructions:

(1) The contractor must report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site.

Contracted services excluded from reporting are based on Product Service Codes (PSCs).

(2) The contractor is required to completely fill in all required data fields using the following web address:

sam.gov.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30.

While inputs may be reported any time during the FY, all data must be reported no later than October 31 of each calendar year.

https://www.ecmra.mil/

Y, Construction of Structures and Facilities;

D, Automatic Data Processing and Telecommunications, IT and Telecom- Telecommunications Transmission (D304) and Internet (D322)

ONLY;

S, Utilities ONLY;

V, Freight and Shipping ONLY.

Contractors may direct questions to the help desk, linked at sam.gov.

6.4 PERFORMANCE REQUIREMENTS SUMMARY (PRS)

Service PWS Reference

Performance Standard

Acceptable Quality Level

Method of Surveillance

Incentive / Penalty

Timeliness of Deliverables required by the Contract

PWS 5.0 Deliverables shall be submitted in accordance with the delivery requirements required by the PWS.*

95% of the deliverables / reports are submitted on time.

COR Tracking

-CPARS ratings -Contract Deficiency Report

(CDR)

Accuracy of Deliverables required by the Contract

PWS 5.0 Reports and Other Deliverables are complete and correct when submitted.

No more than 3 Errors in content per Deliverable.

COR Review for completion and accuracy

-CPARS ratings -Contract Deficiency Report

(CDR)

Financial System Reporting Maintenance

PWS

5.1.1.2

Financial reports are developed or amended within 10 days of the COR’s request and do not have downtime.

2 reports are permitted to be late up to 5 days per year. Downtime must not exceed 5 business days.

COR Review for completion and accuracy

-CPARS ratings -Contract Deficiency Report

(CDR)

Fire Extinguisher Maintenance

PWS

5.2.10

Fire extinguisher logs show monthly inspections were completed.

100% accuracy Random COR Review for completion and accuracy

-CPARS ratings

-Contract Deficiency Report

(CDR)

Document Routing

PWS 5.2.4 Documents routed reach the required signature authority and/or reviewer within 1 business day.

Reminders are provided

No more than 2 errors per month.

Random COR Review for completion and accuracy

CPARS ratings -Contract Deficiency Report

(CDR)

*Note: Deliverables are not counted as late when, on a case by case basis, the COR approves later deliverable submission. The COR’s approval of a late deliverable submission or failure to strictly enforce delivery requirements will not be deemed a waiver of the applicable delivery requirements for future deliverables.

7.0 PLACE OF PERFORMANCE

7.1 Unless noted below, the majority of the work may be performed remotely. All staff are offsite except staff assigned for work performed for (a) PWS 5.2 for ADC P, ADC R work activities onsite performance is required with telework allowed on limited circumstances and (b) PWS 5.2 for RFA and SDI work activities, onsite performance is required with telework allowed for up to 3 business days per week.

Assigned personnel will be asked to attend meetings and working groups from time to time at the Programs and Resources offices located in the Pentagon or at designated off-site locations as the work effort dictates.

7.1.1 Working on a Government Installation. On occasion, work must be performed on government installations. Contractor personnel supporting administrative coordination roles such as administrative assistants will be required to work on site daily at the designated Pentagon or NCR location.

7.1.1.1 The Contractor shall provide each employee with an identification badge identifying, by photograph, the individual as an employee of the Contractor. These badges shall be worn at all times and presented for examination upon request from the Contracting Officer, COR, Quality Assurance Personnel, Military Police, or any other Government official with a need to see the badge.

7.1.1.2 The Contractor and its employees shall be subject to all traffic, security, and registration regulations for personnel and vehicles, to include Marine Corps Base Order 4200.3 “Contractor Screening Policy”. Copies of current regulations may be obtained from the Contracting Officer.

7.1.1.3 All Contractor personnel attending meetings, answering government telephones, working on site, where their Contractor status is not known to third parties, must identify themselves as Contractors, to include wearing identification badges, identifying them as such. Contractor personnel shall also ensure that when logged into Government equipment that their profile shows them as Contractor personnel.

Unless otherwise directed by the Contracting Officer or the COR, all documents produced or revised by Contractors or developed through Contractor participation must be marked as “Contractor Generated Documents” or otherwise identified in a manner that discloses the Contractor’s participation.

7.2 Travel. Travel is unauthorized.

8.0 PERIOD OF PERFORMANCE

8.1 The period of performance (PoP) for this contract / Task Order shall be in accordance with the Contract Line Item Numbers (CLINs) established within the solicitation / award document.

The following federal holidays are observed:

after 5 days if the reviewer has not completed their required action.

1 January New Year’s Day 3rd Monday of January Martin Luther King’s Birthday 3rd Monday of February Presidents Day Last Monday of May Memorial Day 19 June Juneteenth Day 4 July Independence Day 1st Monday of September Labor Day 2nd Monday of October Columbus Day 11 November Veterans Day 4th Thursday of November Thanksgiving Day 25 December Christmas Day

Note: If a federally observed holiday should fall on a Saturday, it will be observed on the preceding Friday; if it falls on a Sunday, it will be observed on the following Monday. When this occurs, Government employees will typically be exempt from work for that day and the Contractor may follow company policy for performing work on these days.

8.2 RFA and SDI’s core hours are 0800 to 1500, Monday through Friday. The Contractor will be available, at a minimum, during these times, but flexibility is required to accommodate essential meetings occurring outside of these times and business process events such as fiscal year closeout which may occur later in the day or on weekends. Additionally, accountability of personnel regardless of start time, is required by 0730 each week day to meet DC, P&R muster reporting timelines.

9.0 ACCEPTABLE NIPR LAPTOP

In the performance of their duties all contractor personnel will require connectivity and access to the MCEN for accessing sensitive information and sending and/or receiving e-mails that contain sensitive information. In doing so, the contractor shall comply with MCENMSG-Unification 003-14 ENABLING CONTRACTOR ASSET CONNECTIVITY TO THE MCEN. Compliant laptops/computers will be imaged by the Marine Corps. The Contractor is responsible for providing these laptops/computers; the Government will not furnish laptops/computers for this PWS. No more than one laptop/computer will be imaged per Contractor employee. The current list of computers eligible for imaging are as follows:

MCEDS Supported Models Version 1.0.13.0 (25H2)

6/8/2026

PLEASE SEE THE LINE 55 FOR LEGEND AND REFER TO FAQ TAB FOR MCEDS SUPPORT

INFORMATION

Manufactu rer Model BIOS Upgrades in 1.0.13.0

Drivers in

MCEN-N

SCCM

Drivers in

NIPR

ISO

version on

DML*

Dell Latitude 5330 Yes X X Dell Latitude 5420 Yes X X Dell Latitude 5430 Yes X X Dell Latitude 5440 Yes X X

Dell Latitude 7350 Detachable Yes X X Dell Latitude 7330 Rugged Extreme Yes X X Dell Optiplex 5000 Yes X X Dell Precision 3440 Yes X X Dell Precision 3450 Yes X X Dell Precision 3460 Yes X X Dell Precision 3561 Yes X X Dell Precision 3571 Yes X X Dell Precision 3581 Yes X X Dell Precision 3591 Yes X X Dell Precision 5280 Tower X-Series Yes X X Dell Precision 7770 Yes X X Dell Pro 14 PC14250 Yes X X Dell Pro Max 16 MC16250 Yes X X Dell Pro Max Tower T2 FCT2250 Yes X X

DT

Research DT311CY No X X

DT

Research DT311TY No X X Getac F110 G6 No X X Getac F110 G7 No X X Getac B360 G2 No X X Getac B360 G3 No X X Getac K120 G2 No X X Getac UX10 G3 No X X HP Elite x360 830 G11 Yes X X HP Elitebook 640 G11 Yes X X HP Elitebook 645 G9 Yes X X HP Elitebook 645 G10 Yes X X HP Elitebook 645 G11 Yes X X HP Elitebook 845 G8 Yes X X

HP

Elitebook 6 G1ah 14 Inch Notebook PC Yes X X

HP

Elitebook 6 G1a 14 Inch Notebook AI PC Yes X X

HP Elite SFF 600 G9 Yes X X

HP

EliteDesk 8 Mini G1i Desktop AI PC Yes X X

HP

EliteDesk 8 Tower G1i Desktop AI

PC

HP Elite Tower 600 G9 Yes X X HP Engage One Pro AI No X X HP ProBook 640 G8 Yes X X

HP

ProDesk 4 Tower G1i Desktop AI PC Yes X X

HP Pro Mini 400 G9 Desktop PC Yes X X HP HP Zbook Fury 16 G11 Yes X X HP Zbook Power G7 Yes X X HP Zbook Power G9 Yes X X

HP Zbook Power G10 Yes X X HP Zbook Power 16 G11 Yes X X

HP

ZBook X G1i 16 inch Mobile Workstation PC Yes X X

HP Z2 Tower G9 Yes X X Panasonic Toughbook FZ55-3 No X X

Legend EUS = End User Services, PEO Digital. Formerly Client Computing Services (CCS) & Marine Corps Common Hardware Suite (MCHS).

MCFMIS = Marine Corps Food Management Information System aka Chow Hall POS systems.

PCE = Procurement Center for Excellence, PEO Digital. Formerly Strategic Sourcing Service (SSS).

Green = Available for purchase as of date on line #3.

Yellow = Model is only supported for MCEDS 1.0.13.X. Upon release of next MCEDS this model we be removed from the supported list unless owner re-submits model to EUS for testing.

*The ISO on the DML it will support all models IF you copy of the correct drivers folder.

See the instructions on the DML.

The updated list of approved laptops authorized to be attached to the MCEN can be obtained from MCSC G6 upon request. The Contractor will transfer the contractor owned laptops to the MCSC, G-6, Information Technology Asset Management (ITAM) department to have the MCEN imaged placed on each laptop before it can be connect to the MCEN. Upon completion of the contract or at such time as the contractor reclaims the asset from the USMC effort; non-Government owned internal\external hard drives and data associated with the laptop shall become the property of the US Government and turned over to the COR upon request. For additional questions regarding current system specifications contact the COR.

The laptops purchased will not be considered Government property and will not transfer to the Government at the end of the task order (except hard drives and data listed above).

10.0 SECURITY REQUIREMENTS

10.1 All tasks shall be conducted in full compliance with DoD security regulations. At time of contract award, all of the Contractor’s staff assigned to this contract shall have and maintain a Secret clearance and the Contractor shall have and maintain a Secret facility clearance. USMC will sponsor reinvestigations, but will not sponsor initial Secret clearances for Contractor personnel unless this requirement is waived by the COR. Upon award, the DD 254 will be provided and incorporated into the contract.

10.2 Contractor personnel will be required to access information systems and data through portals via user accounts and Common Access Cards (CAC) that will be provided by the Government. Contractor personnel shall meet specific requirements to be granted these privileges and maintain these credentials.

Compliance with all USMC communications regulations pertaining to network activities is mandatory.

Failure to comply with security requirements will result in revocation of access privileges and personnel removal from work under this contract. The contractor shall comply with the following: On August 27, 2004, President Bush signed Homeland Security Presidential Directive 12 (HSPD-12), "Policy for a Common Identification Standard for Federal Employees and Contractors". Based upon this directive, the National Institute for Standards and Technology (NIST) developed Federal Information Processing Standards publication (FIPS) 201 including a description of the minimum requirements for a Federal Personal Identification Verification (PIV) system. HSPD-12 directs the implementation of a new standardized badging process, which is designed to enhance security, reduce identity fraud, and protect the personal privacy of those issued CAC identification.

FIPS PUB 201 is available at http://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.201-2.pdf The Office of Management and Budget (OMB) associated guidance, M-05-24 is available at http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2005/m05-24.pdf.

10.3 Contractor personnel providing support under this contract will require background checks in order to obtain user account at the IT level 3 (unclassified network access). The minimum investigation requirement is a National Agency Check with written Inquiries (NACI). Contractor personnel must meet HSPD-12 Standards and have the ability to obtain and maintain a favorable NACI is when requesting access to either or both unclassified IT systems. And/or access to Federal facilities/buildings. The Contractor is advised this process could take 6-12 weeks to complete or longer. An in-person visit with the HQMC P&R Security Officer will be required for contractor personnel to in-process. These visits occur on Tuesday of each week. To accomplish in processing:

Contractors must have:

10.3.1 Defense Information System for Security (DISS) Visit Request sent to HQMC P&R Security Management Office, HQMC P&R (SMO Code: M02215) OR *** IF UNABLE TO SEND VIA DISS

ONLY ***

Contractors must bring:

10.3.1.1 Finalized DD 254, Contract Security Classification Specification form;

10.3.1.2 Performance Work Statement (sometimes within the contract or written up as a separate document);

10.3.1.3 For newly hired contractors with no previous clearance, the incumbent must complete NACI SF85 and have available two completed and original FD-258 Fingerprint cards.

11.0 TRAVEL REIMBURSEMENT

11.1 The contract does not include travel and travel is not authorized.

12.0 OTHER

12.1 Non-Disclosure Agreements. All Contractor personnel receiving access to Government data or data from another Contractor through this contract must provide a signed non-disclosure agreement prior to commencing work. This original agreement shall be submitted to the Contracting Officer and a copy shall be submitted to the COR. A non-disclosure agreement shall be signed by all Contractor personnel involved in this effort and returned to RFA within five (5) business days after receipt of award or commencement of work. The term “business day,” as used in the context of this paragraph, means normal Government working hours between the hours of 0730 and 1630, Monday to Friday, excluding weekends and federally observed holidays.

12.2 Government Furnished Information (GFI). The Government will provide the Contractor with all reasonably available information requested concerning this PWS and the applicable documents required to perform the tasks outlines in Section 3 of this PWS.

http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2005/m05-24.pdf

12.2.1 The Contractor shall protect all GFI (technical data) provided by the Government from public disclosure in accordance with the marking contained thereon.

12.2.2 While the services performed under this contract generally involve access to and handling of material at the Unclassified level, engagements in meetings and working groups may lead to exposure to information and materials classified at the Secret level.

12.2.3 All material developed by the Contractor during this contract shall become the property of Headquarters, U.S. Marine Corps. The Contractor shall be required to abide by the disclosure standards set forth in DFARS 252.204-7000. The Contractor shall not release any information to regulators, media, or other parties. Information releases will come from USMC Government employees only.

13.0 INTELLECTUAL PROPERTY

13.1 The Contractor shall not use Contractor’s or third-party proprietary items and/or materials unless otherwise agreed upon in writing by the Contracting Officer prior to the commencement of the work.

13.2 No data, materials, information or other items (hereinafter singularly or collectively “Items”) created or provided expressly for this PWS shall be used by the Contractor for any purpose other than those that are in support of, or for performance under, this PWS without the prior written permission of the Contracting Officer. The Contractor is obligated to protect from unauthorized use or disclosure all Government confidential or classified material and/or Government-owned proprietary, and/or Personally Identifiable Information or Personal Privacy, Items obtained in the course of performance under this Government contract, as long as such Items remains proprietary, confidential, sensitive or classified. Any information obtained in the course of duties, or the performance of services, under this contract including, but not limited to, information that may be made available for use that relates to the technical data, trade secrets, processes, operations, style of work, or apparatus, or to the technical data, statistical data, amount or source of any income, profits, losses, or expenditures of any person, firm, partnership, corporation, or association is included in this clause (and with “Items”). Contract personnel shall not publish, divulge, disclose, or make known Items in any manner, or to any extent not authorized by the Contracting Officer.

When the Contractor’s need for any Items ends, the Items shall be returned promptly (within ten (10) business days) to the appropriate government program personnel. However, the obligation not to discuss, disclose, release, reproduce or otherwise provide or make available such Items, or any portion thereof, shall continue, even after completion of this contract/order.