PERFORMANCE WORK STATEMENT (PWS)

MARINE DEPOT MAINTENANCE COMMAND (MDMC)

DIGITAL DEPOT

Section 1

General Information

1.0 General. This is a performance based non-personal services contract to provide

Information Technology support services sustaining to Marine Depot Maintenance Command

(MDMC) Digital Depot. The Government will not directly instruct nor control the Contractor outside of the scope of this PWS performing the services herein. Subcontractor employees shall be accountable solely to the Contractor who, in turn, is responsible to the Government.

1.1 Mission. To provide the Fleet Marine Force (FMF) with worldwide organic field level and depot-level maintenance support for rebuild, repairs, engineering solutions, modifications, calibrations, manufacturing and technical services to maximize the operational readiness, lethality, and sustainability of ground combat and combat support weapon systems and equipment.

1.2 Background. MDMC, Digital Integration Division (DID), located at Marine Corps

Logistics Base Albany, GA, requires subject matter and technical expertise to assist MDMC with pursuit of transforming into a Digital Depot. Digital Depot is being pursued to:

• Integrate data from Internet of Things (IoT) and Operational Technology

• Centralize MDMC data into a unified namespace

• Reduce Authorization to Operate (ATO) footprint

• Go Paperless

• Enable forward deployed advanced manufacturing.

• Modernize processes

1.3 Scope. Contractor shall work with Information Systems Security Manager (ISSM) and

MDMC points of contact in accordance with this contract. Contractor shall provide general project oversight and shall provide all aspects of support in accordance with contract requirements. Support services in this effort include the following tasks:

MDMC IT systems include:

1. Depot Modernization Planning System (DMPS)

2. Integrated Global UID Enterprise Solution (I-GUIDES)

3. Maintenance Center Productivity and Labor Management System (MCPALMS)

4. Maintenance Center Production Application System (MCPAS)

5. Maintenance Repair and Overhaul System (MRO) – Removing by 5/31/2026.

6. Test Measurement and Diagnostic Equipment Website (TMDE Website)

7. MDMC Power Platform (MDMCPP)

Support services include:

• Project Management

• Microsoft Power BI, Power Apps, and Power Automate (M365) configuration

• Microsoft Dynamics 365 configuration

• Manufacturing Execution System integration

• Maintenance and enhancement of legacy systems and applications

• Operation Technology Integration

• Database administration and maintenance support

• Network Engineering/Administration support

• Systems Engineering/Administration support

• Cybersecurity support (Information System Security Officer and Validator)

• AI support (includes Machine Learning, Deep Learning, and Robotics)

• Data warehousing support

• Data Analytics support

• Cloud Migration

• Cloud Architect

1.3.1 Contractor shall comply with all contract requirements regarding safety, security, quality of work, access, Government owned property, material and information, host facility rules and regulations, policies, processes, procedures, and directions received from authorized Government personnel when attending requested meetings, briefings or performing any efforts aboard any Government installation. Contractor shall match personnel skills to the work or task to maximize resource utilization. Contractor shall provide the necessary resources and infrastructure to manage, perform, and administer the contract as defined in this PWS and supporting attachments.

1.3.2 During contract performance, the Government may implement process improvements or adjust production schedules and workload that may result in a modification to the contract resulting in a reduction of the Contractor’s staffing, adjustment to Contractor employee work schedules, staggered work schedules, or overtime. The Contractor’s

Program Manager shall participate with the Contracting Officer (KO), the Contracting

Officer’s Representative (COR), DID Staff in planning meetings and assist in determining the best approach to executing any contract changes with minimal disruption to the

Contractor’s performance. Status and staffing reports must be provided monthly to the

COR. See Section 5 for additional information (e.g., due date, method of submittal, medium and format).

1.3.3 Contractor shall coordinate and conduct a virtual post-award kick-off meeting one (1) business day after contract award. Contractor shall schedule and conduct this meeting in coordination with the KO, COR, DID Director. The Government will provide a Microsoft

Teams link, dial in number, and pin for this meeting. The purpose of the post-award meeting is to:

1. Meet and greet.

2. Q&A session.

3. Review of the Transition-In Plan.

4. Establish a common understanding of quality, schedule, and management expectations.

5. Review procedures (ex: SECNAV 5512 Base Access, training certificates, DD2875

SAAR for MCEN access, etc.).

1.3.4 Mission Support (MS). MS is the ability to continue to achieve MDMC’s goals and objectives despite potential outside factors that could affect the MDMC’s mission. MS is to support deployments, contingency operations, hostilities, war, national emergencies, critical mission systems and other unusual, critical operations and support potential outside factors that could affect MDMC’s mission. MS tasks shall include, but are not limited to surge, overtime, quality control, audits, MDMC IT system software, building moves, issues applicable to safety and security, after hour operations, and other tasks identified in this PWS. Contractor shall ensure operations are not degraded during increased operational periods such as surge.

Although specific MS requirements are not known prior to award of the initial contract, the scope of each specific MS requirement will be known prior to authorization of each MS requirement during contract performance. Specific MS requirements will be authorized through the Government Request for Goods and Services (RGS) process, Attachment 0004. When the contractor identifies that a specific MS requirement is needed, the contractor shall submit to the

COR a RGS form with supporting documentation to allow the Government to determine whether the identified scope is required and that the corresponding price for that scope is fair and reasonable. Regardless of the dollar value, the Contractor’s supporting documentation shall consist of three competitively obtained quotes from different Contractors or a statement of the reason competitive quotes were not obtained and how the quoted price is determined to be fair and reasonable IAW Federal Acquisition Regulation (FAR) 15.404-1(b).12.203(a)(3) and FAR

12.203(c)(2). The KO is the approval authority for all RGS.

All expenses require supporting documentation for Wide Area Workflow (WAWF) invoicing

(e.g., receipts, approved RGS, email documentation, manifests). Invoices without the required approved RGS may be treated as an unauthorized commitment and processed IAW

Government regulations. All mission support shall be itemized and reported monthly to the

COR for data collection. See Section 5 for additional information (i.e., due date, method of submittal, medium and format).

1.3.5 Surge support is defined as increased mission requirements, including but not limited to, emergencies, natural disasters, terrorist threats or events, elevation of threat levels or unscheduled/short notice exercises, unit activations, contingency operations, DoW policy changes, or deployments. Surge support may require additional Contractor support.

Notification of surge support requirements may include locations, specific services required, suggested number of personnel, and any other unique information. The Government will make every effort to give the Contractor advance notice of requirements, but the services for which this contract will be used could address an emergent requirement with little or no advance notice. Contractor shall provide the Government with a proposal for surge support within 48 hours from the time of notification. Contractor shall ensure the proposed solution does not delay the execution of mission or cause mission failure. Surge pricing will be evaluated for fair and reasonableness prior to increasing support. Surge support will only become effective after a

KO approved RGS or fully executed modification to the contract.

1.3.6 Overtime hours are defined as that time exceeding the normal hours of operation. Only the KO is authorized to approve overtime through the Government RGS process; all overtime requires pre-approval from the KO.

1.3.7 MDMC IT equipment support includes the price of all parts purchased in support of

MDMC’s Digital Depot. For all material purchased for the Government by the Contractor, the following statement will be annotated on all service/repair request documentation. "All items, equipment, and material reimbursed by the Government, not operationally consumed during the performance of this contract, is/are the property of the Government.” Only the KO is authorized to approve MDMC IT system software through the Government RGS process; all

MDMC IT system software procurement requires pre-approval from the KO.

1.4 Period of Performance. The period of performance is one (1) year in length 5/1/2026 –

4/30/2027. The period of performance is one (1) 12-month base period with a possible 6-month option period. The total period of performance with option extended shall not exceed

18 months.

1.5 General Information. Contractor shall provide the necessary products and services required as outlined in this PWS. This PWS outlines requirements to support in Section 5 –

Deliverables below.

1.5.1 General Compliance. Contractor shall comply with all contract requirements regarding personnel, safety, security, quality of work, access, Government-owned property, material and information, host facility rules and regulations, policies, processes, procedures, and directions received from authorized Government personnel when attending requested meetings, briefings or performing any efforts aboard any Government installation. This does not preclude the

Contractor from complying with the requirements of this contract as specified.

1.5.2 Hours of Operation. The Government’s core hours are 0730 to 1630 ET Monday through Friday, except for all Federal holidays or when the Government facility is closed.

Scheduled maintenance windows are 1631 – 2000 ET Monday through Friday and 0730-1630

Saturday. Federal Holidays are published at https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/. The Government facility may be closed due to weather conditions, power outages, water outage, or due to a local or national emergency. Support may be required outside normal duty hours for any mission critical event(s) determined by DID Director or

COR that requires immediate attention.

1.5.2.1 Holidays. The policy of this activity is to schedule periods of reduced operations or shutdown during holiday periods. Deliveries will not be accepted on Saturdays, Sundays, or Holidays except as specifically requested by the COR/KO. All goods or services attempted to be delivered on a Saturday, Sunday, or Holiday without specific instructions from the KO or his/her duly appointed representative will be returned to the Contractor at the

Contractor’s expense with no cost or liability to the U.S. Government.

https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/ https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/

The federal Government observes public Holidays that have been established under 5 U.S.C.

6103. The actual date of observance for each of the holidays, for a specific calendar year, may be obtained from the United States Office of Personnel Management (OPM) website at

OPM.GOV or by using the following direct link: https://www.opm.gov/policy-data-oversight/pay-leave/federal-holidays/.

1.5.2.2 Delayed Opening, Early Dismissal and Closure of Government Facilities.

When a government facility has a delayed opening, is closed or federal employees are dismissed early (due to severe weather, security threat, security exercise, or a facility related problem) that prevents Contractor personnel from working onsite, Contractor personnel regularly assigned to work at that facility shall follow their company’s direction as Contractor personnel are not Government employees. Contractor shall not direct charge to the contract for such time off but shall follow parent company policies regarding taking leave

(administrative or other). Non-essential Contractor personnel, who are not required to remain at or report to the facility, shall follow their company’s policy regarding whether they should go/stay home or report to another company facility. Subsequent to an early dismissal, delayed opening, or during periods of inclement weather, on-site Contractors should monitor the OPM website as well as radio and television announcements but shall follow the Contractor’s policy before departing for work.

1.5.3 Place of Performance. The work to be performed under this contract will be performed for the commands at the designated government facilities below.

Marine Depot Maintenance Command

814 Radford Blvd, Maintenance Center Bldg 2200

Albany, GA 31704-1128

1.5.3.1 Telecommuting. Teleworking will be considered on a case-by-case basis.

1.5.4 Type of Contract. The Government will award a combined contract that includes Firm

Fixed Price (FFP) CLINs for direct labor and mission support, and Cost Reimbursement (CR)

CLINs for travel and mission support.

1.5.5 Security Requirements. Contractor shall manage and ensure that all personnel are properly cleared to access designated base(s)/worksite(s). The Contractor’s management of required security clearances and Common Access Card (CAC) shall be at no expense to the

Government. Contractor shall comply with installation and other applicable security requirements. This includes entering, leaving, and being present within the installation boundaries.

1.5.5.1 Common Access Card (CAC). The work performed under this contract shall require Contractor employees to have a CAC to gain access to the Marine Corps Enterprise

Network. At a minimum, these employees will be required to have a favorable background check prior to obtaining a Government Identification Card and a dot mil account. The

Contractor is responsible for the correct and timely submission of all documents necessary for

CAC and dot mil attainment. Due to the variation in base access processing, it is important for the Contractor to ensure personnel are on site as specified in PWS paragraph 2 to start the documentation (e.g., DD Form 2875, System Authorization Access Request (SAAR)).

Contractor’s management of their employees’ CAC process shall be at no expense to the

Government. Processes for individual CACs may differ slightly from one military installation to another. However, general guidance for obtaining the Contractors CAC is provided by the

KO/COR. Approximately thirty (30) days should be factored into personnel timelines when acquiring a CAC for personnel that are NOT already approved in the base access/security system. For personnel that are already in the base access/security system as approved personnel, this process may take less than five (5) business days (depending on base ID appointment requirements).

1.5.6 Contracting Officer Representative (COR). The COR will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the

Contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; maintain written and oral communications with the

Contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including Government drawings, designs, specifications; monitor

Contractor's performance, and notifies the KO and Contractor of any deficiencies; coordinate availability of Government provided equipment, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially regarding changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.5.7 Staffing and Key Personnel. Contractor shall achieve 50 percent staffing for all key personnel within (15) calendar days and 100 percent staffing for all key personnel within (30) calendar days of contract award. Contractor shall achieve 100 percent staffing of non-key personnel listed in proposal within (30) calendar days of contract award. Below are key personnel.

Billet Labor Category Minimum Qualifications Required

Project Manager Computer and

Information Systems

Manager

• Bachelor’s degree.

• 10+ years supervisor experience.

• Mastery in briefing and communicating with senior leadership.

• 2+ years experience with IT System projects of similar size and complexity.

Cybersecurity Information Security

Analyst

• Bachelor’s degree in computer science, or other relevant degree with

6+ years USMC Risk Management

Framework experience or no degree with 8+ years USMC Risk

Management Framework experience.

• Certified Information Systems

Security Professional (CISSP) or equivalent DoW 8570 certification.

• Certified as a validator by USMC

Information, Command, Control, Communications, and Computers

(IC4).

• SECRET clearance.

1.5.7.1 Replacement of Key Personnel. Contractor shall not replace Key Personnel identified in their proposal during the first one hundred eighty (180) calendar days of the task performance period (inclusive of Phase-In period) unless the replacements are unavoidable

(e.g., sudden illness, death, withdrawal/leave of employment); in any case, the Contractor shall notify the COR in writing within two business days of their need to replace Key

Personnel and who the Contractor has appointed as the “acting” replacement. All requests for replacements hereunder must be in writing and provide a detailed explanation of the circumstances necessitating the proposed replacement(s). Request must contain a complete resume for the proposed replacement, who shall have at least the minimum qualification requirements, and any other information requested by the KO to evaluate the proposed replacement. The KO and COR will evaluate such requests and promptly notify the contactor of their assessment thereof, in writing, within two (2) business days. Key personnel replacement(s) shall be hired and on-site within thirty (30) calendar days from the date of vacancy. After the initial one hundred eighty (180) calendar days, the Contractor shall submit to the COR in writing all proposed replacements of key personnel at least thirty (30) calendar days in advance unless the replacements are unavoidable which requires the Contractor to notify the COR in writing within two (2) business days. The Contractor shall not allow diminished capability in any given work section due to personnel vacancies and absences.

Also, vacant positions for other than key personnel shall be filled within thirty (30) calendar days from the date of vacancy.

1.5.7.2 Absence of Key Personnel. Contractor must notify the COR of any scheduled absence of key personnel at least five business days prior to the first day of the absence. The absence must not compromise nor hinder the contract’s performance in any way. If the absence is greater than two (2) business days, the Contractor must provide a detailed plan with the absence notification to the COR. The detailed plan shall cover the PWS requirements of the absentee and who will perform these requirements during the absence. For unscheduled absence (e.g., emergency leave, sick), the detailed plan shall be provided NLT two (2) business days after notification of absence to the COR.

1.5.8 Training. Contractor is responsible for verification of all staffing and Key Personnel certifications as required by PWS. Contractor is responsible for the training of Contractor personnel in performance of this contract, except for that explicitly defined as training at

Government expense. Any replacement of Key Personnel, who received Government expense training, will require the Contractor to pay for training the replacement Key Personnel.

Contractor shall ensure its personnel are trained and qualified to perform the requirements under this contract safely and efficiently. Training is not considered a single occurrence, but an ongoing program in all aspects for all supported customers. IAW FAR 52.203-13, the

Contractor Code of Business Ethics and Conduct, the Contractor shall be required to conduct an effective training program on business ethics awareness and compliance.

The Government is responsible for providing access to Government web-based training modules. There are also several government-provided training courses required for DoW

Contractors who operate on or have access to computers connected to the military (dot mil) internet system. This includes but is not limited to:

1. Cyber training https://securityawareness.dcsa.mil/cybersecurity/index.htm

2. PII training https://securityawareness.dcsa.mil/piiv2/index.htm

3. CUI training https://securityawareness.dcsa.mil/cui/index.htm

In addition, each user of Government-Owned, Contractor-Operated Information-Technology

(GOCO-IT) systems shall take all required government-provided training courses, in accordance with their roles and responsibilities. The Government will provide access to computer-based training for the operation of GOCO-IT systems, as well as periodic on-site training. The Government will not accept any untrained or unqualified personnel performing under this contract. The Government may direct training based on updates to policy or changes in equipment necessary for the performance of the PWS requirements.

For Contractors that are hired as systems’ administrators and/or, software developers that require privileged access to systems/DBs, the contractor will complete the required training for access and token for privileged access. They will also complete the annual training and certification required to maintain this access.

Required items for privileged access:

1. Privileged User Cybersecurity Responsibilities https://jkodirect.jten.mil/html/COI.xhtml?course_prefix=SOU&course_number=-JIA-01-

2. Cyber Security training (CompTIA Security+)

3. IT Level 2 security designation (usually minimum T3 investigation)

At the Government’s discretion, the Government may provide Contractor training as necessary to support changes in Government requirements, doctrine, policy, procedures, regulations, or as needed to benefit the Government. Additionally, the Government will provide a tactical training/licensing examiner to issue tactical licenses to Contractors, as needed.

1.5.9 Dress Code. To ensure employee safety, the Contractor shall comply with Marine Depot

Maintenance Command Order 12000.1. Clearly identifiable company shirt/pants with company emblem/logo may be worn at the discretion of the Primary Contractor. Only the Primary

Contractor emblem/logo shirts/pants are permitted. No Subcontractor clothing shall be https://securityawareness.dcsa.mil/cybersecurity/index.htm https://usg01.safelinks.protection.office365.us/?url=https%3A%2F%2Fsecurityawareness.dcsa.mil%2Fpiiv2%2Findex.htm&data=05%7C02%7Cbrandon.connelly%40usmc.mil%7C5d6b44cf80cf4676647b08ddd4ecd695%7Cf4c44cda18c646b080f2e290072444fd%7C0%7C0%7C638900836006194024%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=BnSVU5r5IkUaxChWm%2BOFWMvDz3JzExESkZJRYjh4reg%3D&reserved=0 https://securityawareness.dcsa.mil/cui/index.htm https://jkodirect.jten.mil/html/COI.xhtml?course_prefix=SOU&course_number=-JIA-01-0006 https://jkodirect.jten.mil/html/COI.xhtml?course_prefix=SOU&course_number=-JIA-01-0006 permitted at any site. No headgear may be worn except for PPE such as hardhats, or as necessary in adverse weather conditions. Clothing, shoes, and PPE are not reimbursable by the

Government. Contractor shall be responsible for the enforcement of these standards.

1.5.10 Contractor Travel. If the Government determines that travel is required to support this effort, all requests for travel will be in accordance with the travel CLIN and preauthorized by the COR and KO using an RGS. Travel reimbursements will be in accordance with the regulatory implementation of Public Law 99-234 and FAR 31.2. If travel is required and performed, the Contractor shall submit a trip report that provides the reason for travel, topic discussions, outcomes, action items and any follow-on requirements. Trip report must be provided within seven (7) calendar days after trip completion. Contractor shall attach actual invoices when submitting a cost voucher within WAWF as supporting documentation. See Section 7 for additional information (e.g., due date, method of submittal, medium and format).

1.5.11 Data Rights. All Items generated by the Contractor, including, but not limited to, software and database data/information/products, instructional/help guide products, SOPs, schematics, diagrams, and general or analytical reports, all related updates, and all associated intellectual property, in whatever form, created, generated, or produced under this requirement will become the property of the U.S. Government/Marine Corps and not the

Contractor, subcontractor, or individual author or researcher. Therefore, the U.S.

Government/Marine Corps will have the irrevocable, royalty-free, worldwide right to use, modify, reproduce, perform, display, release, or disclose such Items, in whole or in part, in any manner, and for any purpose whatsoever, and to have or authorize others to do so. The contract will include all applicable DFARS clauses (including, but not limited to, DFARS

252.227-7013, 252.227-7014, 252.227-7015, and 252.227-7020).

No data, materials, information, or other items (hereinafter singularly or collectively "Items") created or provided expressly for this PWS will 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 KO.

1.5.12 Organizational Conflict of Interest (OCI). Contractor and Subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications, or work statement, etc.) or perform evaluation services which may create a current or subsequent OCI as define in FAR

Subpart 9.5. Contractor shall notify the KO immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the KO to avoid or mitigate any such OCI. The Contractors mitigation plan will be determined to be acceptable solely at the discretion of the KO and in the event the KO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the

KO may affect other remedies as he or she deems necessary, including prohibiting the

Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.5.13 Safety. Marine Corps Logistics Command (MARCORLOGCOM) is in the process of pursuing OSHA Voluntary Protection Programs (VPP) recognition or has already received VPP recognition from OSHA. VPP affects all applicable Contractor’s operating on site. It is the Contractor's responsibility to ensure its employees and managers are in full compliance with OSHA requirements and have a general understanding of VPP. All

Contractors, whether regularly involved in routine site operations or engaged in temporary projects such as construction or repair, must follow the safety and health rules of MCLC.

Apply established safety regulations and practices to minimize minor violations and to avoid major violations due to employee error or negligence. Ensure the holding area is well organized and maintained within good housekeeping standards. Detailed information on VPP is available on the OSHA website at http://www.osha.gov/dcsp/vpp/index.html. Contractor shall comply with commercial safety standards as identified by the Occupational Safety and

Health Administration. Contractor shall comply with all Federal, State, Department of War

(DoW), Department of the Navy (DON), United States Marine Corps (USMC), and local rules and regulations to include but not limited to OSHA Standards, National Fire Protection

Association (NFPA) Standards, Navy Marine Corps Directive (NAVMC DIR) 5100.8, Marine

Corps Order (MCO) 5100.8. The Contractor must have a written Safety Plan and submit it to the COR for review and approval by the KO within ten (10) calendar days after contract. In addition to the requirements listed above, the Contractor’s written Safety Plan shall, as a minimum, address the following:

1. Mishap reporting procedures

2. Monthly safety meetings

3. Employee training requirements

4. Monthly safety inspections

5. Requirements for Subcontractors to comply with the safety provisions of this contract

1.5.13.1 Additional Safety Requirements. See below:

1.5.13.1.1 Applicable Contractors. These requirements apply to Contractors, Subcontractors, and their employees or agents.

1.5.13.1.2 Days Away, Restricted, and/or Transfer Case Incident Rate (DART).

Number of recordable injuries and illness cases per one hundred (100) full-time employees resulting in days away from work, restricted work activity, and job transfer that a site has experienced in a given period.

1.5.13.1.3 Total Case Incident Rate (TCIR). Total number of recordable injuries and illness cases per one hundred (100) full-time employees that a site has experienced in a given period.

1.5.13.1.4 Mishap Incident Report. Contractor shall report any mishaps or incidents within one (1) hour of any mishap or incident resulting in personal injury (OSHA recordable) or significant property damage while performing work authorized by this contract, the Contractor shall notify the installation safety office, DID Director, KO/COR.

Mishap notifications shall contain, as a minimum, the following information:

1. Contract Number, Name of Company, and Name and Title of Person(s) Reporting

2. Date, Time, and exact location of accident/incident

3. Brief narrative of accident/incident (Events leading to accident/incident)

4. Cause of accident/incident (if known)

5. Estimated cost of accident/incident (material and labor to repair/replace)

6. Nomenclature of equipment and personnel involved in accident/incident

7. Corrective actions (taken or proposed)

Mishaps/Incidents report must be provided within twenty-four (24) hours, one (1) calendar day of the incident. See Section 6 for additional information (e.g., due date, method of submittal, medium and format).

1.5.13.1.5 Contractor shall fully cooperate with MDMC safety personnel during safety inspections of the workplace and inspections of required documentation.

1.5.13.1.6 Safety requirements listed in this package that do not relate to the

Contractor’s operations or services may be waived by the KO. Objections made by the Contractor must be reported to the KO within ten (10) business days of contract award. Objections will be considered on a case-by-case basis.

1.5.13.1.7 Smoking and the use of tobacco products is allowed in designated areas only.

1.5.13.1.8 All vehicle operators and passengers of Contractor and privately owned vehicles are required to wear seatbelts while their vehicle is in operation on the installation and performing work under this contract. The use of seatbelts is also required on all mobile construction equipment operating on the installation and performing work under this contract.

1.5.13.1.9 All vehicle operators and passengers are prohibited from using a cell phone, personal digital assistant (PDA), unless the vehicle is safely parked, or the operator is using a hands-free device. The use of portable headphones, earphones, or other listening devices (except for hand-free cell phones) while operating a motor vehicle is also prohibited.

1.5.13.1.10 Should an accident occur and in the event the US Government investigates the mishap, the Contractor and Subcontractors shall cooperate fully and assist government personnel during the investigation period. Instructions pertaining to the assistance required from the Contractor in support of an investigation and the point of contact of the MDMC safety personnel involved in an investigation will be provided by the COR or the KO.

1.5.13.1.11 Contractors operating on installations will be responsible for briefing and ensuring the employees adhere to the safety and traffic rules and regulations. The foreman, job supervisor and other personnel providing workman leadership will ensure the workers comply with these rules and regulations. Speed limits on installations are posted. Individuals are to obey all entry procedures. If instructions are given by the military police/law enforcement personnel on the entry points gates, they will be always complied with.

1.5.14 Identification of Contractor Produced Documents. All contract personnel shall ensure that all documents or reports produced by Contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed. Additionally, all

Contractors with Government issued dot mil shall incorporate the following legal disclaimer into their email correspondence.

1.5.15 Per DFARS 211.106, Contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with

Government personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in formal and informal written correspondence.

DISCLAIMER:

I am a contract employee of (Company name). The information in this email is for official use only and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient or believe that you have received this in error, do not copy, disseminate or otherwise use the information and immediately contact the owner/creator.

1.5.16 Contractor Personnel Identity and Responsibilities

A. The Pass and ID Offices are responsible for issuing badges and CACs to all

Contractor and Subcontractor employees in need of access or performing work on the installation. The information required to be submitted by the Contractor will be determined by the governing regulations and policies at the time of the Contractor’s request.

B. There will be instances in which Contractor employees will only be issued the CAC.

When this occurs and in addition to the CAC, the Contractor shall ensure that all contractor employees display a contractor badge with their name and their company name on their person while on board the installation or on official duty elsewhere.

C. When communicating (telephone, email, meetings, etc.) with government personnel, Contractor employees must first identify themselves as contractor employees.

D. When conducting any form of communication with government personnel, contractor employees must immediately excuse themselves if source selection or similar information inappropriately enters the interaction in their presence.

1.5.16 Other Direct Costs (ODC)

A. Contractor may incur incidental and additional costs supporting the performance of required services within the scope of this PWS where the exact requirement is not known prior to award. Examples of some items that fall into the ODC category include but are not limited to network services, software licenses, and software license support.

B. Contractor shall obtain Government approval for any ODC requirements prior to procuring. All ODCs require KO approval. If the Government determines an ODC is necessary, the Government will submit approved ODC requirement with a quote to the Contractor. The Contractor shall obtain the ODC requirement, provide to the

Government within seven (7) calendar days, and invoice the Government for the same cost in the quote (no G&A added) within sixty (60) days.

1.5.17 Mission Essential Contractor Services. The Government has identified Section 4:

4.2, 4.3, and 4.4 as mission essential. The Contactor will adhere to paragraph (b) of

DFARS 252.237-7023, Continuation of Essential Contractor Services and DFARS

252.237-7024, Notice of Continuation of Essential Contractor Services. Its plan may mirror its proposal for incorporation into the contract.

Section 2

Government Furnished Items and Services

2.0 Services. The Government will provide telephones, email services, and Marine Corps

Enterprise Network (MCEN) access as needed for the function of official business use only.

2.1 Facilities. The Government will provide proper facilities for completion of requirements.

2.2 Utilities. The Government will provide all utilities in the facility for the Contractor’s use in performance of tasks outlined in this PWS.

2.3 Equipment. The Government will provide equipment (desk, chairs, etc.) necessary for completion of requirements within the operating spaces. Contractor shall be liable for loss or damage to Government provided equipment beyond fair wear and tear.

If the KO determines it necessary to temporarily issue equipment to a Contractor due to unforeseen or urgent requirements, the Contractor shall follow the guidelines delineated by

FAR clause 52.245-1 and DFARS clause 252.211-7007.

2.3.1 Information Technology (IT). The Government will provide MCEN-N laptops; 1 per key and non-key personnel. Contractor shall be liable for loss or damage to Government-furnished IT systems due to negligence beyond fair wear and tear.

2.3.2 Removal of Government-Furnished Equipment (GFE). In no case, without prior approval of the COR, will any GFE be removed from any government facility or installation. The Government reserves the right to request an inventory of GFE items at any time.

2.4 Government-Furnished Information (GFI). The Government shall furnish the requirements of the PWS such as Standard Operational Procedures, applicable regulations, publications, bulletins, manuals, and other materials associated with the project and the hardware/software noted throughout this PWS.

Section 3

Contractor Furnished Items and Responsibilities

3.0 Contractor will not be reimbursed for normal cost of doing business. This includes, but is not limited to, personnel, administrative costs, relocation costs in the Continental United

States, contractor-owned equipment, automotive cost, training, refresher training, day-to-day office supplies, and any other items determined by the KO.

3.1 Contractor shall procure and maintain all equipment and services in support of this task order (e.g., material handling equipment, maintenance vehicles, pressure washers, semi-tractors and flatbed trailers, utility carts, personnel safety equipment to include hard hats, steel toe boots, safety vests and cell phones for key personnel). Contractor shall notify the COR of any down equipment within 24 hours of the occurrence and repair or replace the down equipment within 72 hours of the notification. Status of equipment report must be provided on a weekly basis to the COR. See Section 7 for additional information (e.g., due date, method of submittal, medium and format).

3.2 Contractor shall maintain all required licenses, registration, and insurance on Contractor provided equipment. Contractor shall ensure that they observe and comply with all

Department of Transportation, DoW, and Marine Corps Installation (if applicable) regulations and policies.

3.3 Medical services for Contractor personnel are the responsibility of the Contractor. On-installation medical activities will provide emergency care to the extent that medical services are available to any person while performing duties required by this PWS when necessary; to prevent undue suffering or loss of life for job related injuries.

3.4 Contractor shall test all software updates and patches at the vendor facility prior to deployment at the operational environment at MDMC. Contractor shall also provide patch notes on all changes to the new software version or release. Additionally, the Contractor shall assist in the mitigation and resolution of any patches or software issues that occur once implemented with the operational environment.

Section 4

Requirements/Tasks

Contractor shall be obligated contractually to perform every requirement in this performance work statement. Not every performance requirement has a related standard expressed in this document. In such cases the performance standard is either inherent in the requirement or performance is to be in accordance with standard commercial practice.

4.1 Project Management

4.1.1 Provide a primary, Project Manager (PM), and alternate contractor point of contact that is responsible for the management of tasks, subtasks, and deliverables within this PWS.

4.1.2 Provide overall project management to include detailed project planning, progress planning, risk mitigation, requirements gathering, quality assurance, user training, and customer support.

4.1.3 Ensure MDMC IT systems are maintained in accordance with references in Section 7.

4.1.4 Contractor shall participate in weekly meetings with project stakeholders and brief current projects, risks and mitigations, and recommendations.

4.1.5 Contractor shall maintain Capability Maturity Model Integration (CMMI) Level 3 certification (and other superseding Levels/guidance) at no cost to the Government and ensure CMMI Level 3 practices are followed and documented.

4.1.6 Contractor shall submit a Weekly Status Report (WSR) by uploading report to a

Government provided SharePoint site. Government will provide Contractor a two-page template. See Section 5.1 for more details.

4.1.7 Contractor shall maintain Capability Maturity Model Integration Level 3 certification or greater.

4.1.8 Upon receiving KO approval on a request for reimbursable goods or services (RGS), Contractor shall obtain and provide proof of support for all Department of Navy

Applications and Database Management System (DADMS) listed in MDMC IT Systems

Department of Defense Information Technology Portfolio Repository Department of

Navy (DITPR-DoN) MAP tab to IT system PM/A-PM and COR prior to USMC last date allowed for all MDMC IT Systems and software whose procurement is required through a Government blanket purchase agreement.

4.1.9 Contractor shall limit turnover to less than 10 percent per calendar year which is applicable to the entirety of the staffing effort (key and non-key personnel).

4.2 Development, Test, & Production Environments

4.2.1 Contractor shall provide and maintain a development environment that is approved by

DoW and ISSM.

4.2.2 Contractor shall provide and maintain a test environment for that is approved by DoW and ISSM.

4.2.3 Contractor shall provide and maintain a production environment that is approved by

DoW and ISSM and sized appropriately to maintain 99.3% or greater availability.

Scheduled maintenance approved by PM/A-PM does not count against availability.

Availability is calculated within a three-month period and resets each quarter (example:

Quarter 1: Jan – Mar, Quarter 2: April – June, Quarter 3: July – Sept, Quarter 4: Oct -

Dec).

4.3 Post Deployment System Support (PDSS)

4.3.1 Contractor shall maintain all IT System code and crons in https://web.git.mil/.

Government will provide access and link upon contract award.

4.3.2 Contractor shall use Remedy for all requests for changes (RFCs). Government will provide Remedy access (Analyst Role) upon receipt of Contractor providing certificates for following MarineNet https://www.marinenet.usmc.mil/ courses:

• MCSCOVW901 USMC E-ITSM Remedy Features and Functionality Overview

• MCSCINC001 USMC E-ITSM Incident Management Process and Tool Training

• MCSCRQF901 USMC E-ITSM Request Fulfillment Process and Remedy Tool

4.3.3 Contractor shall document a level of effort (LOE) to complete each requirement captured in a unique Remedy work order prior to beginning work.

4.3.4 Contractor shall request a HP Fortify code scan prior to requesting promotion to test environment. Contractor shall remedy any issues found in HP Fortify code scan prior to promoting code to test environment.

4.3.5 Contractor shall promote changes to the test environment at a day/time approved by the

PM/A-PM.

4.3.6 Contractor shall promote changes to the production environment at a day/time approved by the PM/A-PM.

https://www.marinenet.usmc.mil/

4.3.7 Contractor shall obtain monthly Assured Compliance Assessment Solution (ACAS) scans. When a new plugin arises, Contractor shall coordinate a fix within below time frames. The time starts once the Contractor is notified of the plugin vulnerability. The timeline stops once the fix is promoted. Fix is achieved when A-PM/ISSO validate the plugin ID falls off the new ACAS scan or when the Contractor provides proof of false positive and receives PM/A-PM concurrence.

Severity Fixed in Test Fixed in Production

Critical 2 business days 4 business days

High 5 business days 7 business days

Moderate 25 business days 30 business days

Low 35 business days 40 business days

4.3.8 Contractor shall ensure the products chosen are based on the appropriate Evaluated

Assurance Level (EAL) of the network involved and used IAW latest Defense

Information Systems Agency (DISA) policy.

4.3.9 Contractor shall demonstrate compliance with policy guidance for International Common

Criteria (ICC) for Information Security Technology Evaluation Mutual Recognition

Arrangement, the National Information Assurance Partnership (NIAP) Evaluation and

Validation Program, Federal Information Processing Standard (FIPS) validation program, use of Mobile Code Technologies in DoW Information Systems, and Ports, Protocols, and

Services Manual (PPSM).

4.3.10 Contractor shall provide training upon request by DID Dir or COR.

4.3.11 Contractor shall identify Security Technical Implementation Guides (STIGs) and other implementation guidance, with input from and in coordination with the Government, as needed.

4.3.12 Contractor shall provide support with Marine Corps Directives (MCD), Marine Forces

Cyberspace Command (MFCC) direction, Cyber Protection Team (CPT) support, Assured Compliance Assessment Solution (ACAS) support and Microsoft Defender scans.

4.3.13 Contractor shall backup data daily and store at a location approved by PM/A-PM.

Contractor shall retain backups for 30 calendar days.

4.3.14 Contractor shall ensure IT systems listed in Section 1.3 are logging events documented in control plan AU-2.

4.3.15 Contractor shall ensure servers and databases are compliant with current security guidelines set forth in Security Technical Implementation Guidelines (STIGs) and vendor and/or DoW vulnerability patches and alerts.

4.3.16 Contractor shall provide support for all six stages of Software Development Life Cycle, requirement determination/validation, analysis, solution design, solution configuration, system test and implementation/sustainment. Update documents within 3 business days after change is promoted successfully to production.

4.3.17 Contractor shall develop and maintain a User Guide for each system listed in Section 1.3.

4.3.18 Contractor shall provide support to extract, transform, and load (ETL) as required by

PM/A-PM. This includes sending data to authoritative sources and receiving data from authoritative sources. Contractor shall troubleshoot and resolve all ETL errors.

4.3.19 Contractor shall provide expert technical advice in leveraging cloud native technologies to ensure effective and efficient cloud operations.

4.3.20 Contractor shall develop a tracking mechanism that tracks alarms, unplanned outages, and provide reports of any degradation or event.

4.3.21 Contractor shall conduct daily (Monday-Friday) monitoring to assess the functionality and health of each system listed in Section 1.3.

4.3.22 Contractor shall communicate network performance issues and partner with

MCCOG/DISA to resolve latency issues.

4.3.23 Contractor shall complete a backup recovery within 1 business day upon request.

4.4 Cloud Support

4.4.1 Contractor shall provide expertise in cloud technologies necessary to extract, transform, load, clean, integrate, apply business rules, and conduct analytical operations on data using approved technologies available within the Marine Corps Enterprise Network. This will support developing and maintaining of a solution that is flexible, extensible, agile, and highly scalable to accommodate rapidly changing data landscape within the Marine

Corps, supporting MDMC’s Digital Depot.

4.4.2 Contractor shall estimate, monitor, and recommend adjustments to usage of cloud compute costs, data transit costs, data storage costs and reserve instance procurement to minimize costs while meeting operational necessities.

4.4.3 Contractor shall migrate data to a Government approved Cloud environment within 30 calendar days upon request.

4.5 Cybersecurity support

4.5.1 Contractor shall provide USMC Certified Validator(s) to perform validation/auditing of

MDMC RMF authorization requirements in accordance with Enterprise Cybersecurity

Manual (ECSM) 018 Marine Corps Assessment and Authorization Process (MCAAP).

4.5.2 Contractor shall perform Common Vulnerability Scoring System (CVSS) scoring, develop the Security Assessment Report (SAR) and other Validation support requirements as required by DoW and USMC policies and guidance for the assigned system(s). Document results in a government-provided repository.

4.5.3 Contractor shall provide required system artifacts in support of…