M00264-25-R-0002 Amend 0004.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is the follow ing:

- address questions received as a result of the revised PWS paragraphs submitted w ith Amendment 0003.

- revise PWS paragraphs 4.4.2.5; 4.4.2.7; 4.4.3.4; 4.4.3.6; and 6.

All other terms and conditions remain unchanged. See Summary of Changes.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 38

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 14-May-2025

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X M0026425R0002

X 9B. DATED (SEE ITEM 11)

23-Oct-2024

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

15-May-2025

CODE

MCINCR - RCO

2010 HENDERSON RD

EGGLESTON-SCOTT, CHRISTA

QUANTICO VA 22134

M00264 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

M0026425R0002

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

Q&AS FOR AMEND 0003

Solicitation Section Comment/Question Answer 1 PWS Section 4.4.2.5 (Page 44 of

57) PWS Section 4.4.2.5 (Page 44 of 57), last bullet currently reads as ‘- Completed by end of contract base year.’ Can the Government confirm that with the changes implemented in Amendment 0003, that this last bullet should read as: Completed by the end of contract option year one?

PWS paragraph revised to read “complete by end of contract option year one”.

2 PWS Section 4.4.2.7, last bullet (appearing on Page 46 of 57)

PWS Section 4.4.2.7, last bullet (appearing on Page 46 of 57), currently reads as ‘- Completed within the first eight (8) months of the contract base year.’ Can the Government confirm that with the changes implemented in Amendment 0003, that this last bullet should read as: Completed within the first eight

(8) months of contract option year one?

PWS paragraph revised to read “complete by end of contract option year one”.

3 PWS Section 4.4.3.4 (Page 47 of 57)

PWS Section 4.4.3.4 (Page 47 of 57), last bullet current reads as ‘- Completed by end of contract option year one.’ Can the Government confirm that with the changes implemented in Amendment 0003, that this last bullet should read as:

Completed by end of contract option year two?

PWS paragraph revised to read “complete by end of contract option year two”.

4 PWS Section 4.4.3.6 (Page 48 of 57)

PWS Section 4.4.3.6 (Page 48 of 57), last bullet current reads as ‘- Completed by end of contract option year one.’ Can the Government confirm that with the changes implemented in Amendment 0003, that this last bullet should read as:

Completed by end of contract option year two?

PWS paragraph revised to read “complete by end of contract option year two”.

5 Volume 3 – Factor 3 – Past Performance

Volume 3 – Factor 3 – Past Performance. Can the Government confirm that as long as previously submitted Past Performance citations remain within the relevancy period of five (5) years of the revised due date

The Government confirms that as long as previously submitted Past Performance citations remain within the relevancy period of five (5) years of the revised due date for submission under Amendment 0003 for submission under Amendment 0003 (28 May 2025), that offerors do not need to resubmit Volume 3 and associated documentation [such as Past Performance Questionnaire (PPQ) (Attachment 2) or Assessor Past Performance Questionnaire (APPQ)] as a result of Amendment 0003? Rationale: This reduces the burden on Government personnel who have already completed this documentation where the citations being referenced are the same and would be duplicative in nature without any changes.

(28 May 2025), that offerors do not need to resubmit Past Performance.

6 PWS para 4.4.2.5 This SOW paragraph was moved to OY1, but the paragraph still says the task must be completed by end of Base Year. Could the Government please confirm that it should say that the task will be completed by end of

OY1?

PWS paragraph revised to read “complete by end of contract option year one”.

7 PWS para 4.4.2.7 This SOW paragraph was moved to OY1, but the paragraph still says the task must be completed by end of Base Year. Could the Government please confirm that it should say that the task will be completed by end of

OY1?

PWS paragraph revised to read “complete by end of contract option year one”.

8 PWS para 4.4.3.4 This SOW paragraph was moved to OY2, but the paragraph still says the task must be completed by end of OY1. Could the Government please confirm that it should say that the task will be completed by end of

OY2?

PWS paragraph revised to read “complete by end of contract option year two”.

9 PWS para 4.4.3.6 This SOW paragraph was moved to OY2, but the paragraph still says the task must be completed by end of OY1. Could the Government please confirm that it should say that the task will be completed by end of

OY2?

PWS paragraph revised to read “complete by end of contract option year two”.

10 PWS para 6 (List of Deliverables) The Deliverables list shows an "Artificial Intelligence Assistance" deliverable for SOW 4.4.2.7 and 4.4.3.6, both both of those paragraphs are called "Flight Schedule Assistant" in the SOW. Could the Government please confirm that these deliverables should be the Flight Schedule Assistant?

The Government confirms the deliverables should be Flight Schedule Assistant.

SECTION SF 1449 - CONTINUATION SHEET

The following have been modified:

PWS

PERFORMANCE WORK STATEMENT (PWS)

TRAINING AND EDUCATION COMMAND (TECOM), AVIATION STANDARDS BRANCH (ASB):

MARINE SIERRA HOTEL AVIATION READINESS PROGRAM (M-SHARP)

REVISED IN ACCORDANCE WITH (IAW) RFP AMENDMENT 0003

1. Background:

In an effort to improve training management systems for U.S. Marine Corps aviation ground and flying squadrons, the Aviation Standards Branch of Training and Education Command implemented a Web-based program designed for the needs of the operation and headquarters units. The Marine Sierra Hotel Aviation Readiness Program, or M- SHARP, uses the Marine Aviation Training and Readiness (T&R) Program as its foundation to develop, approve and publish training plans, as well as to record and report scheduled T&R completion. More importantly, M- SHARP enables unit operations departments to track an entire unit’s progress through the training syllabus. The T&R Program sets the training stage and provides the necessary guidance for attainment and maintenance of individual, crew and unit combat skills. M-SHARP is an automated, government-owned data software program that provides real time forecasting, scheduling, execution, and reporting of accurate data and information.

The rationale behind the M-SHARP application is to integrate T&R Program guidance into a rules-based objective system that checks a unit’s training schedule based on the T&R standards in order to validate adherence to published guidelines. This functionality offers a very effective risk identification and management tool for commanders. While M-SHARP’s current functionality provides much needed assistance to squadron operations departments, other capabilities include training execution modules in the Help module.

M-SHARP enables aviation personnel to log pertinent pre- and post-flight data, T&R data for calculation of squadron readiness levels, management of crew qualifications and designations, ordnance and range use, snivels, Temporary Assigned Duty (TAD), and leave. The M-SHARP application provides the operational units a standardized means for scheduling and planning flight training and combat mission and allows the fleet to compare their present and expected training readiness to establish standards. With this information, aviation squadrons are able to intelligently plan and schedule training events to include flights, simulators, and ground events. In addition, M-SHARP provides a robust reporting interface that allows squadron personnel to create predefined and custom reports.

2. Scope of work:

M-SHARP is moving forward into its -seventeenth year of implementation across the Aviation and Aviation Ground Fleet Marine Corps Forces and Reserves (hereafter referred to as ‘Units’) wherein training and readiness is guided by the Aviation Training and Readiness Program Manual, Navy and Marine Corps Directive (NAVMC) 3500.14.

The objective of this requirement is to continue execution of efforts to deploy and support M-SHARP, implement new and enhanced functionality to fully support Marine Aviation, allow more simulator and ground utilization, and increase security. M-SHARP application increased functionality and sustainment will allow for ground and other units to use and build on current capabilities. Sustained development and support of a user friendly, web-based and stand-alone application are paramount to ensure M-SHARP remains a viable and authoritative resource for US Marine Corps Aviation flight hour and sortie-based training data.

The scope of this effort entails technical, analytical, and programmatic support to implement and sustain mission capabilities. Specifically: (1) develop and maintain significant experience and knowledge of Marine Aviation and the Aviation Program Manual; (2) continue the development of M-SHARP through sustainment of current capabilities and development of additional needed functionalities; (3) continue building, fielding, and supporting an integrated web-based application for the Units; and (4) provide the Higher Headquarters (HHQ) elements with reporting services necessary for the collection of data required to justify budgetary decisions.

3. General Requirements:

3.1. Work Location:

Work locations may include Government or Contractor provided spaces. See PWS Sections 4.1.3. and 9.1. for details.

3.2. Security:

3.2.1. Clearance:

The Contractor will require direct access to secure data systems and materials in support of this contract.

The information provided to the Contractor will be unclassified and/or Controlled Unclassified Information

(CUI).

The Contractor is required and expected to have a Facility Clearance and Contractor personnel supporting this effort are required to possess Personnel Clearance Levels.

Contractor personnel requiring access to U.S. Government sensitive unclassified information shall possess a completed background investigation (minimum of a National Agency Check with Inquiries (NACI)) for this Public Trust Position.

The requirement is for two (2) individuals at a minimum to have secret clearances in order to access required spaces for technical support, T&R revisions, and training.

Ten (10) support reps at a minimum require U.S. Government facility clearances in order to conduct support and to gain access to operational units.

Ten (10) software developers at a minimum require U.S. Government facility clearances in order to test develop and implement software in the operational units. A DD254, Department of Defense Contract Security Classification Specification will be provided to the Contractor.

3.2.2. Common Access Cards (CACs):

The Contractor shall be required to obtain Common Access Cards. The COR, or ASB designated government employee, will establish and maintain sponsorship in DEERS (as a Trusted Agent) within the DoD Contractor Verification System in order to provide the following for those Contractors directly affiliated with the development and support of the M-SHARP application:

Initiate and approve applications for Common Access Card (CAC) issuance.

Establish the need for logical or physical access to either DOD network or facilities.

Establish the affiliation with the service or agency.

CAC will only be issued to those Contractors supporting that have been authorized by the Contracting Officer’s Representative (COR). The COR will only authorize CACs for those Contractors that meet current Homeland Security Presidential Directive – 12 (HSPD-12) criteria and have a definitive requirement. CACs are not issued for convenience. A Government CAC is required for the performance of this requirement.

3.3. Travel:

Travel is anticipated in support of this requirement. Travel authorized in direct support of the requirements identified within this contract shall be conducted in accordance with the Federal Acquisition Regulation (FAR), including FAR Part 31, and consistent with the limits in the Joint Travel Regulations (JTR). The Contractor shall be reimbursed for all non-local travel in accordance with the Joint Travel Regulations (JTR). Non-local travel is defined as travel outside a 50-mile radius of the Government’s site. Travel authorization requires approval of the COR, in writing, prior to incurring costs. Travel shall be reconciled monthly and reported to the COR prior to invoicing. Costs incurred without authorization will not be reimbursed.

The contractor shall be required to register/utilize the Synchronized Pre-Deployment Operational Tracker (SPOT) for all outside of the continental U.S. (OCONUS) travel.

3.4. Execution Management:

The Contractor shall establish protocols and infrastructure to facilitate communications between leadership and stakeholders involved in this requirement. This includes establishing lines of authority, administrative processes, and internal protocols to ensure the efficiency and effectiveness of the program efforts. The Contractor shall establish a program support model that enables coordination with TECOM ASB leadership and ensures the integrity of the support process and promotes consistent quality outputs, as well as ensuring alignment with government objectives/priorities. The Contractor shall identify and retain a Program Manager to coordinate contract activities with Government principals. The name of this person must be designated in writing to the Contracting Officer and the COR, within ten (10) business days from date of award and within three days in the event a change occurs. The Program Manager shall have full authority to act for the Contractor on all contract matters relating to this contract. The selection of teaming partners, subcontractors, facilities, and other business considerations is discretionary on the part of the Contractor, so long as they conform to the labor categories, pricing, performance, terms and conditions that bind the Contractor. At all times, the Contractor shall be responsible for the actions of its teaming partners and subcontractors.

3.4.1. Operational Risk Management:

The Contractor shall ensure pre-execution hazard identification through objective enforcement of policy from a variety of sources to include the NAVMC 3500.14, Marine Corps Order (MCO) 3125.1, Commander of Naval Air Force (CNAF) 3710.7; as well as the ability to automate local rules and regulations through creation of decision trees.

3.4.2. Technical Performance Quality:

The Contractor shall be responsible for establishing a staff complement capable of handling the responsibilities of task execution and coordination of team resources. The Contractor shall be responsible for staffing, competency training, guidance, and supervision of qualified personnel performing PWS tasks.

The Contractor shall develop, implement, and maintain a management capability that facilitates effective performance in consonance with the criteria established in the Quality Assurance Surveillance Plan (QASP). Technical cognizance over performance remains with the prime Contractor at all times. The prime Contractor is responsible for all assigned resources, performance quality (e.g., QASP compliance), and deliverables.

The Contractor shall develop a Quality Management Plan (QMP) as a means for gauging overall effectiveness of performance. The contractor shall provide their QMP to the COR within thirty (30) calendar days after award for review and comment. The QMP shall address the Contractor’s plan to meet quality and performance standards outlined in the QASP and the Performance Requirements Summary (PRS) and shall include, at a minimum, the following components:

• Quality objectives

• Key project deliverables and processes to be reviewed for satisfactory quality level

• Quality standards

• Quality control and assurance activities

• Quality roles and responsibilities

• Quality tools

• Plan for reporting quality control and assurance problems

3.5. Government Responsibilities and Interface:

The COR, assisted by Government subject matter experts (SMEs), will execute responsibilities related to performance oversight, deliverables acceptance, invoice certification, and coordination of work effort. The Regional Contracting Office (RCO) Procuring Contracting Officer (PCO) will interface with the prime Contractor’s representative for payment and administration issues.

Only the Contracting Officer has the authority to authorize deviations from the terms and conditions of this contract, including deviations from specifications and requirements. In the event the Contractor does deviate, without written approval of the Contracting Officer, such deviations shall be at the risk of, and any cost related thereto shall be borne by, the contractor. Any matter concerning a change to the scope, prices, terms, or conditions of this contract shall be referred to the Contracting Officer.

3.6. Applicable References:

The contractor shall use the current version of the below references as a guide to the extent necessary to accomplish the tasks as stated in this PWS. If during the execution of the contract the government uncovers the need for additional references or changes to cited references, the government will provide these to the contractor.

• CNAF 3710.7(Series); Naval Air Training and Operations Procedures Standardization (NATOPS) Program General Flight and Operating Instructions.

• NAVMC 3500.14(Series); Aviation Training and Readiness (T&R) Program Manual.

• NAVMC 3500.XX; Type/Model/Series (T/M/S) and Military Occupational Specialties (MOS) specific Aviation Training and Readiness (T&R) Manuals.

• MCO 3125.1(Series); Marine Corps Flying Hour Program (FHP) Management.

• DoD Directive (DoDD) 7730.65 ; Defense Readiness Reporting System (DRRS) guidance.

• MCO 3000.13 (Series); Marine Corps Readiness Reporting Standard Operating Procedures.

• DoD Instruction (DoDI) 8550.01 dated September 11, 2012; DoD Internet Services and Internet- Based Capabilities.

• DoDI 8140.03-M dated February 15, 2023; Cyberspace Workforce Qualification and Management Program.

• DoDI 8500.01 dated March 14, 2014; Cybersecurity.

• DoD 8570.01-M dated November 10, 2015; Information Assurance Workforce Improvement Program.

• Enterprise Cyber Security Manual (ECSM) 018; Marine Corps Assessment and Authorization Process (MCAAP)

• Committee on National Security Systems Instruction (CNSSI) 1253; Security Categorization and Control Selection for National Security Systems.

• Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs)

• Federal Information Processing Standard (FIPS) Publication 140-2; Security Requirements for Cryptographic Modules

• FIPS Publication 199; Standards for Security Categorization of Federal Information and Information Systems.

• FIPS Publication 200; Minimum Security Requirements for Federal Information and Information Systems.

• Federal Information Security Management Act (FISMA) of 2002

• National Institute of Standards and Technology (NIST) Special Publication 800-18, Rev 1; Guide for Developing Security Plans for Federal Information Systems.

• NIST Special Publication 800-30, Rev 1; Guide for Conducting Risk Assessments.

• NIST Special Publication 800-37; Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach.

• NIST Special Publication 800-53 Rev 4; Security and Privacy Controls for Federal Information Systems and Organizations.

• NIST Special Publication 800-53A Rev 4; Assessing Security and Privacy Controls in Federal Information Systems and Organizations: Building Effective Assessment Plans.

• NIST Special Publication 800-60 v1 Rev 1; Guide for Mapping Types of Information and Information Systems to Security Categories.

• NIST Special Publication 800-60 v2 Rev 1; Guide for Mapping Types of Information and Information Systems to Security Categories: Appendices.

4. Specific Requirements:

The Contactor shall support M-SHARP current capabilities, and the development and/or enhancement of new functionality as required and in accordance with established specifications and standards. In support of these requirements, the Contractor shall:

• Develop a Master Project Schedule that defines how the contractual tasks will be managed and controlled, consistent with program objectives, and which provides for the earliest delivery schedule while at the same time satisfying all requirements in a cost-effective manner. The Master Project Schedule shall be provided in electronic form using MS Office applications to the COR within thirty (30) calendar days after contract award and reviewed quarterly. If modified, the contractor shall notify the Government and Program Manager within thirty (30) days. The Master Project Schedule is to include all performance and programmatic milestones, a monthly progress review, and an estimated timeline of task effort through to completion.

• Develop an Upgrades and Enhancements Schedule that categorizes, prioritizes, and schedules when upgrades and enhancements are tentatively scheduled. This schedule will be managed by the contractor but built through collaboration between the contractor and the COR. As the contents of this schedule will likely change regularly, changes to this document will not require the COR’s signature, however, it must be saved in a location available to the COR or sent to the COR after each revision is made.

• Develop a Program Planning Milestone Chart depicting major tasks and events from start to completion of the contract. The Program Planning Milestone Chart shall be provided in electronic form using MS Office applications to the COR within ten (10) calendar days of contract award, reviewed quarterly, and updated as required. The Contractor shall notify the Government in writing within twenty-four (24) hours of any anticipated or projected work stoppages or delays that will impact schedules.

• Develop, maintain, and update, as required, a mission essential services plan to ensure continuation of services in crisis situations, per DFARS 252.237-7023 and 252.237-7024. The Mission Essential Services Plan shall be provided to the COR NLT sixty (60) days after contract award with updates as they occur.

• Ensure that any End User License Agreement (EULA), Terms of Service (TOS), lease, license, or similar legal instrument or agreement (collectively referred to as a “EULA” in this bullet) related to any supply or service furnished under this contract (including but not limited to any software or other intellectual property the Contractor obtains from or through a third party entity and then furnishes to the Government as, or as part of, a deliverable, supply, or service) is consistent with Federal law. Contractor is responsible for obtaining Contracting Officer approval of any such EULA, and Contractor agrees that any such EULA is inapplicable to this contract and is not binding on the Government unless the Contracting Officer agrees to the EULA in writing. For any EULA pertaining to software, intellectual property, a supply, or a service the Contractor obtains from or through a third party entity concerning Contractor’s performance under this contract, the Contractor shall ensure the terms of such EULA are consistent with Federal law and for obtaining Contracting Officer approval of such EULA before delivery of the supply or service to which such EULA relates.

• Ensure all personal that require privileged access to MSHAPR meet DoDM 8140.03 Cyberspace Workforce Qualification at the Intermediate level at a minimum. Privileged users may not start work on the contract until Cyber Workforce Qualification certifications are reviewed and approved by the COR and TECOM Cyber Workforce Program Manager.

4.1. System Maintenance and Sustainment:

4.1.1. Current Capability:

The contractor shall update and maintain the current M-SHARP construct in accordance with established specifications and standards, and emerging technology, in order to sustain and enhance the capabilities of Unit and HHQ Training and Readiness management and maintain system relevancy in compliance with required technological upgrades. M-SHARP capabilities and functionalities include, but are not limited to, Flight/Sim Logger and Scheduler, Unmanned Aerial Systems (UAS) Scheduling/Logger Functionality, Forward Air Controller Airborne (FAC-A) Logger; ATS, T&R Builder, , M-SHARP’s web based help desk known as M-SHARP Solution Center (MSC), Electronic Aviation Training Form (EATF) functionality, Sortie Based Training Program (SBTP).

Specifically, the contractor shall: Provide automation of the complex business rules for the management and reporting of the execution of training; facilitate authorized information access across systems via web services; support integration within service level domains; and provide input regarding budgetary effects of Training and Readiness to HHQ.

In order to remain responsive to the needs of the fleet, the contractor shall be capable of releasing critical updates within a week of identification and maintain a standard development iteration of two weeks.

4.1.2. Routine Updates:

4.1.2.1. Training and Readiness Manual Updates:

T&R Manuals are rewritten or updated on approximately a 3 year cycle, with daily system utilization.

During the T&R revision process, the contractor shall be available to assist TECOM ASB with the M- SHARP T&R Builder tool and Rule Book Manager. This includes but is not limited to updating drop down options, tables, and/or data fields unavailable to the user (e.g., TECOM ASB, syllabus sponsor, Unit Operations Officers).

4.1.2.2. Readiness, Planning, and Reporting:

The Contractor shall compute Core Skill Proficiency (CSP) and Mission Skill Proficiency (MSP) with real-time unit Training and Readiness reporting (CUI) via SBTP and Core Model Training Reports (CMTR); integration of the Core Competency Resource Model (CCRM); and support for Naval Aviation Enterprise (NAE) Current DRRS initiatives, to include the integration and data feed from M- SHARP to DRRS.

The Contractor shall provide the HHQ elements at the Pentagon or Quantico with reporting services necessary for the collection of data required to justify budgetary decisions. The Contractor shall provide Fleet Unit Commanding Officers and Operations departments with reporting services for their individual units to analyze personnel and operation training and readiness requirements. The Contractor shall provide reporting and documentation as are requisite to the task activities of the contract. As historical data begins to accumulate to a point of full utility, HHQ elements require the need to produce timely and accurate reports of information which can be utilized by commanders to make decisions via operations oversight modules, warehousing, and business intelligence tools.

4.1.2.3. Data connections:

The Contractor shall maintain and sustain all existing data connections and/or APIs with associated systems. Additionally, the contractor shall implement, when requested by the COR, up to two new standard data connections per contract year that use existing data exchange capabilities. In unique cases when an entirely new data connection is required, that will be handled as an upgrade (see paragraph 4.2.3).

4.1.3. User Support & Training:

4.1.3.1. On-Site Support:

The contractor shall provide M-SHARP proficient personnel for on-site support to all using Units at the locations identified below. On-site support is defined as, “The physical presence of an M-SHARP knowledgeable professional who provides troubleshooting, technical, and/or functional assistance to using Unit.” On-site support includes initial training, recurring training, and troubleshooting of the M- SHARP application to the extent required by the using units.

Contractor personnel shall execute the M-SHARP “Protocol” function in the event of a USMC aircraft or aircraft-related Mishap. Initial notification of a USMC aircraft or aircraft-related mishap may come from any USMC source (ASB, local squadrons, MAGs, Wings) or even open-source media reporting (i.e., newscasts or internet reporting). Contractor personnel are expected to initiate the protocol within 1 hour of initial notification of the event, or during the first hour of the next business day if initial notification occurs outside normal hours of operation. Contractor personnel may support Aircraft Mishap Board requests for M-SHARP data with the approval of the COR.

Hours of Operation:

On-site technical support shall be available between the hours of 0800-1700 Local Time, Monday through Friday, except Federal Holidays. Local Time is the time zone associated with each of the locations identified below.

Locations:

The contractor shall provide M-SHARP proficient personnel for on-site technical support at TECOM ASB and/or Headquarters Marine Corps, Deputy Commandant (DC) for Aviation; and spread evenly among each of the following major Marine Corps Air Stations (MCAS): MCAS Cherry Point, North Carolina (NC); MCAS New River, NC; MCAS Beaufort, South Carolina (SC); MCAS Yuma, Arizona (AZ); MCAS Camp Pendleton, California (CA); MCAS Miramar, CA; MCAS Kaneohe Bay, Hawaii (HI); 4th Marine Aircraft Wing Headquarters, New Orleans, LA;MCAS Futenma, Okinawa, Japan.

Future Contractor on-site support may be required at sites such as MCAS Iwakuni, Japan, and Guam.

If this additional support becomes a reality, a bilateral modification to the contract will be executed to include these new locations with negotiated pricing.

The Contractor is responsible for ensuring an alternate point of contact is identified on the M-SHARP web site for non-availability or emergency situations. The contractor may be required to travel to support alternate sites to assist other Units. Travel will be coordinated with the COR and the Unit to be supported. If a using Unit is satisfied with the virtual presence (phone, email, web help, etc.) then the intent for on-site technical support has been satisfied. If the using unit requests a physical presence for any reason, then a physical presence is required and mutually agreeable arrangements (between on-site contractor and using unit) shall be made with coordination and approval by the COR.

On-Site Training:

The Contractor, in coordination with the COR and the Government site leads, shall schedule and set up the M-SHARP system training for squadrons (including detachments), Marine Air Groups (MAG), Marine Air Wings, Marine Forces (MARFOR), aviation ground units and detachments, Marine Aviation Weapons and Tactics Squadron One (MAWTS-1), TECOM ASB, and HQMC. Setup shall include Contractor provided training required for using units and may be either group or individual training. Users at the MAG, Wing, Installations, MARFOR, Headquarters, TECOM ASB, and applicable aviation schoolhouse must be trained to use the M-SHARP application to a level commensurate with their designated permissions level. Periodic refresher training shall be included at least monthly and can be targeted by the Contractor on-site technical support based upon using unit requests and/or observed areas of interest or concern. Measures of successful training include the ability of organic users to generate system validated and squadron-approved training schedules and accurate report generation. While maintaining accurate and complete individual training and readiness data is ultimately the responsibility of the user, the Contractor is responsible for training the user how to retrieve data (usually from logbooks) and enter it into the system. Users must also be trained in proper data maintenance techniques, including procedures for validating unit/personnel data and correcting errors. The Contractor shall maintain a record of user and refresher training conducted over the contract period and provide training documentation to the COR for review upon request.

On Site Support Travel Requirements:

Table 1: Travel anticipated in support of this requirement.

Destination Purpose Estimated

# of annual trips

Personnel Required (FTE per trip)

Estimated Length of trip (excluding travel)

1st MAW units:

MCAS Iwakuni Guam

Conduct training and on-site support.

4 1 3 days per trip

2d MAW Units:

MCAS Cherry Point, NC MCAS New River, NC MCAS Beaufort, SC

Provide SME Support to USMC Aviation Conferences (e.g. T&R, OpsO)

3 2 4 days per trip

3d MAW Units:

MCAS Camp Pendleton, CA

MCAS Miramar, CA MCAS Yuma, AZ

Provide SME Support to USMC Aviation Conferences (e.g. T&R, OpsO)

5 2 4 days per trip

4th Marine Air Wing

(MAW) HQ, LA

Provide SME Support to USMC Aviation Conferences (e.g. T&R, OpsO)

1 1-2 3 days per trip

MACG-48, Naval Station Great Lakes, IL

Conduct training and on-site support.

1 1 3 days per trip

MAG-41, MACS-24, JRB

Naval Air Station Ft Wort, TX

Conduct training and on-site support

2 1 3 days per trip

MAG-49, Joint Base McGuire/Dix/Lakehurst, NJ

Conduct training and on-site support

1 1 3 days per trip

Naval Air Station Meridian

Conduct training and provide on-site support for Aviation Operations (MOS 7041) Course

2 1 2 days per trip

Naval Air Station Pensacola

Conduct training and on-site support to USMC aviation schools.

Provide SME Support to USMC Aviation T&R Conferences

2 1 3 days per trip

MCB Quantico (Stafford, VA)

Conduct M-SHARP Increment Planning and quality control training

2 5 3 days per trip

MCB Quantico (Stafford, VA)

Conduct annual FSR currency and quality control training

1 9 3 days per trip

MCAS Futenma MCB Hawaii MCAS Yuma MCAS Miramar MCAS Camp Pendleton 4th MAW HQ, New Orleans, Conduct support analysis/ training; observe /elicit input on FSR services from on-site units by M-SHARP Managers

4 (one trip to each

MAW

AOR)

1-2 3 days per trip

MCAS Beaufort MCAS New River MCAS Cherry Point

4.1.4. Online Support:

User System Access to M-SHARP (or Related Sites):

The contractor shall make the web site accessible to the using units (squadrons (including detachments)), MAGs, MAWs, MARFOR, aviation ground units and detachments, MAWTS-1, TECOM ASB, and HQMC upon approval by the COR. The contractor shall ensure all government or non-government web sites to interface with M-SHARP are in compliance with the applicable security protocols for M-SHARP access.

Software User Manual:

The contractor shall update the Software User’s Manual (SUM), a detailed manual to use the M-SHARP program, made available electronically to users in order to ensure the Marine Forces user information matches the software version fielded. The SUM will be located on the M-SHARP user support page.

Help Desk Support:

The Contractor shall maintain (updated concurrently with the released version) electronic web-based help files accessible within the M-SHARP application. Via the M-SHARP Solution Center (MSC), the Contractor shall provide telephone/email points of contact for all On-Site Technical Support contractors and access to a web-based Customer Support Request form (ticketing system) to recommend software enhancements, report anomalies, request accounts, and request on-site training. These recommendations shall be provided to the COR and upon COR approval, implemented into M-SHARP based on necessity and relevance of each request.

The Contractor’s M-SHARP support personnel shall be available to respond to questions and problems via telephone during the normal working hours of 0800 – 1700, Monday through Friday, except Federal Holidays (local time). Support outside of normal working hours will be through the support site ticketing system (historically occurs less than 10%). Support personnel first response from a missed phone call is expected to be within the hour, first response from a trouble ticket is expected to be by or before the next working day.

Service Request Service Level Agreement (MSC Tickets):

Service requests are assigned severity levels (Critical, High, Medium, Low) based on the urgency of the need to support the system users as defined below:

Severity Level and Description Time to follow-up after first response Critical Functionality is required to complete daily user functions and normally impacting more than one unit; there is no available work-around; or a safety of flight issue.

4 business hours

High Functionality is required to complete daily user functions and normally impacting just one unit or small number of users; there is an available work-around.

Impacts accuracy of reporting that is not safety related.

8 business hours

Medium Functionality is not required to complete daily user functions but does impact usability.

2 business days

Low A problem that has minimal impact on the user.

5 business days

4.1.5. User Access to M-SHARP or other Related Web Sites:

The contractor shall ensure all government or non-government web sites to interface with M-SHARP are in compliance with the applicable security protocols for M-SHARP access. The contractor shall make the web site accessible to the using units upon approval by the COR.

4.1.6. Technical Requirements:

4.1.6.1. Accreditation and Information Assurance (IA).

The contractor shall provide an appropriately credentialled individual at the intermediate or advanced proficiency level per DoDM 8140.03 requirements to serve in the project’s Information System Security Officer (ISSO) role. The Contractor shall adhere to all updated policies and requirements per TECOM G-6, Marine Corps Cyberspace Operations Group (MCCOG), and Deputy Commandant for Information. Management of IA testing related activities shall be consistent with program acquisition category (ACAT) levels, milestone schedules, and overarching policy requirements.

4.1.6.2. Assessment and Authorization (A&A) Analysis:

4.1.6.2.1. Marine Corps Certification and Authorization Support Tool (MCCAST) and Federal Risk Management Framework (RMF):

The Contractor shall use MCCAST to complete the RMF for M-SHARP per DoDI 8510.01 and ECSM 018. The Contractor shall work with TECOM ISSM to migrate the MSHARP ATO accreditation package from MCCAST to EMASS during FY2026. Once ATO accreditation package is migrated to EMASS Contractor will work with TECOM ISSM to update and maintain all required ATO documentation within EMASS. Additionally, the contractor shall coordinate with the TECOM ISSM and other parties to ensure that any external interfaces or system interconnections with M-SHARP, in accordance with ECSM 018, provide applicable ATO, System Interface Agreement (SIA), or other documentation as needed to assess and ensure the security of the interface with M-SHARP and that it does not impact the M-SHARP ATO. The Contractor shall be responsible for funding of the Independent Verification and Validation.

4.1.6.2.2. Network and Application Documentation:

The Contractor shall develop and maintain, throughout the lifecycle of the system; network and application documentation, and assist TECOM and appropriate units (such as; Marine Corps Cyberspace Operations Group, MCCOG; Marine Corps Enterprise Network, MCEN and other applicable organizations and units in support of the accreditation package) with the production and maintenance of their supporting A&A documentation and artifacts and DODAF artifacts, keeping all documents synchronized and up to date with actual system configurations in MCCAST which will include conducting vulnerability assessments, uploading artifacts, running applicable reports, control assessments and validation.

4.1.6.3. Authority to Operate (ATO) Plan of Action & Milestones (POA&M):

The Contractor shall develop and maintain ATO POA&M documentation to mitigate risks identified during A&A and provide recommendations to the TECOM ISSM that integrates with established Marine Corps cybersecurity directives.

4.1.6.4. A&A Packages:

The Contractor shall develop and maintain A&A packages, and perform weekly quality assurance reviews with the ISSM, in accordance with the RMF and Marine Corps C&A processes. A A&A package consists of the entirety of the documentation for an application system. A summary of a package includes Ports and Protocols, System Security Plan, Disaster Recovery (DR) Plan, Configuration Management (CM) Plan, Risk Management Plan, or other A&A package items as directed by the COR.

4.1.6.5. Risk Management Strategies:

The Contractor shall analyze strategies in order to mitigate risks of threats and vulnerabilities, determine deviations from established configurations, and recommend appropriate mitigation countermeasures. Recommendations are part of the POA&M document.

4.1.6.6. Marine Corps Enterprise Network (MCEN) Compliance:

On a weekly basis, the Contractor shall use the Assured Compliance Assessment Solution (ACAS) tool to verify compliance with MCEN operational directives. ACAS shall be put into a report that is fed into the Online Position Description and Recruitment System (OPDRS), which is the authoritative source for compliance and vulnerability management.

4.1.6.7. Information Systems Security Analysis:

4.1.6.7.1. IA scans:

The Contractor shall conduct IA scans, using the ACAS tool, as required under existing Marine Corps Cyber Security directives, and provide recommendations in a weekly report that address the operational impact of the findings. Recommendations shall include identifying and applying the appropriate IA methodology, life cycle implementation process, and configuration guidance to meet the security requirements of the technology, system, and environment.

4.1.6.7.2. Cyber Threat Analysis:

Daily, the Contractor shall review Marine Corps Information Assurance Vulnerability Alerts (IAVA), Information Assurance Vulnerability Bulletin (IAVB), Information Assurance Technical Advisories (IAVT) notices, Operational Directives (OPDIRS), Communication Tasking Orders (CTOs), and Marine Collection Database (MCD) and provide recommended action and Cyber Threat Analysis in the POA&M to address operational impacts to TECOM software and network requirements. The Contractor shall provide TECOM a weekly summary of the Information Assurance Vulnerability Management (IAVM) and Marine Corps Directive (MCD) actions taken to TECOM ISSM. The Contractor shall coordinate with the TECOM ISSM to comply with any USMC, DoD, or government released alerts, directives, policies, taskers, or guidelines to ensure the cybersecurity posture of M-SHARP remains secure and compliant.

4.1.6.7.3. Incident Response:

The Contractor Shall follow Enterprise Cybersecurity Manual 001 Marine Corps Cyber Incident Response Version 3.0 dated February 20, 2025 (ECSM 001) guidance for Incident Response reporting. The Contractor will also incorporate ECSM when creating or updating Incident Response policies and procedures for MSHARP.

4.1.6.8. IT Procurements:

The Contractor shall evaluate Information Technology (IT) procurements for compliance with established Marine Corps IT Security policies and guidance and provide recommendations to the COR for approval as needs arise. Contractor is responsible in accordance with USMC and TECOM policy for working with the M-SHARP government program manager and ISC during the submission of Information Technology Procurements Requests (ITPRS) for all new hardware, software, IT services, or cloud services that will be used as part of the MSHARP system.

4.1.6.9. Information System Security Officer:

The Contractor shall support the Information System Security Officer (ISSO) duties (the ISSM will delegate duties, such as vulnerability management, to the contractor ISSO/ISSM to perform), per DoDI

8510.01 and MCO 5239.2B relative to the RMF for all TECOM ISs, Enclaves and applications under the purview of the TECOM ISSM.

4.1.7. Central Configuration Management of M-SHARP Software and Support Materials:

The Contractor shall maintain central configuration control for the M-SHARP software and support materials.

4.1.8. Document Management:

The Contractor shall create, maintain, and update all programmatic and system specific documentation, test plans, supporting documentation, and presentation material in support of M-SHARP in a location determined by the Contractor and made accessible to the COR and the GPM. The Contractor shall maintain T/M/S and MOS specific Aviation T&R Manuals (NAVMC 3500.XX) contained within the database as a single source of T&R standardization. The Contractor shall ensure all programmatic and system specific documentation, test plans, supporting documentation, and presentation material formatted in accordance with references below, including the:

• Database Design Description (DBDD)

• Operational Concept Description (OCD)

• Software Design Description (SDD)

• Software Development Plan (SDP)

• Software Test Description (STD)

• Software Test Plan (STP)

• Software Test Report (STR)

• Software Version Description (SVD)

• System Security Plan (SSP)

4.2 Cloud Maintenance and Sustainment:

4.2.1 Change Management:

The contractor shall have experience and certifications in all aspects of Infrastructure as a Service (IaaS) within the Amazon Web Services (AWS) GovCloud environment, including migration, new architecture, and sustainment in support of M-SHARP. The Contractor shall provide a cost-effective infrastructure hosted in AWS GovCloud that meets Federal and DOD IT security requirements and utilizes industry standards and best practices that meet or exceed the following requirements:

• Recommend procedures associated with Government-authorize project change requests.

• Provide impact analysis associated with proposed changes.

• Propose maintenance change schedules and change plan.

• Implement approved changes per approved change request procedures.

• Manage changes to the baseline, project plan, committed maintenance and enhancement dates.

• Respond to alerts and notify Government about changes in status within terms of the Service

Level Agreement (SLA).

• Suppress redundant alert notifications pertaining to same root cause.

• Generate tickets for selected alert types using ticketing system.

• Maintain audit trail of all detected alert conditions and their resolution lifecycle.

• The contractor shall provide support to M&RA with the sustainment and operation of the

Manpower Cloud Services (MCS) environment until M-SHARP finalizes the migration to the MCCOG Secure Cloud Computing Architecture (SCCA). Once migrated, the contractor shall provide support to MCCOG with the sustainment and operation of the MCCOG Amazon web services SCCA.

• The contractor shall provide support to M&RA, the MCCOG, and any other related entity to facilitate the migration of M&RA’s locally controlled SCCA to MCCOG’s SCCA.

• In accordance with current SLA’s, the contractor supports the M&RA cloud enterprise by maintaining one cloud engineer and one cloud architect. This requirement is dependent on the current applicable SLA and may be subject to change. At a minimum contractor must provide one cloud professional with the minimum certification level of AWS Cloud Solutions Architect Professional, with optional but beneficial certifications of AWS Certified DevOps Engineer Professional, AWS Certified Machine Learning Specialty, and/or AWS Certified Security Specialty.

• Coordinate with applicable SCCA provider for the Web Application Firewall (F5).

• Maintain a Centralized Cloud Management Account to house access to cloud resources.

• Ensure proper access control to master CSO account.

• Privileged user management and authorization artifact…