M00264-18-R-0001.pdf

SEE ADDENDUM

(No Collect Calls)

M0026418R0001 08-Jan-2018

b. TELEPHONE NUMBER

703-784-2808

8. OFFER DUE DATE/LOCAL TIME

12:00 PM 09 Feb 2018

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA X ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

M002649. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

JUDITH M. CAMPBELL

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.X

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED ORX

SMALL BUSINESS

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

MCINCR - RCO

2010 HENDERSON RD

JUDITH M. CAMPBELL

QUANTICO VA 22134

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE M95430 16. ADMINISTERED BY

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

M95430

TRNG ED COMMAND

2079 BARNETT AVE

QUANTICO VA 22134

LINDA GISOLO

TEL: 703-784-2192 FAX:

FAX:

TEL: SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$27,500,000

NAICS:

541511

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF90

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

M0026418R0001

Section SF 1449 - CONTINUATION SHEET

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 12 Months System Maintenance and Sustainment

FFP

System Maintenance and Sustainment IAW PWS 4.1.

FOB: Destination

NET AMT

0002 12 Months Product Upgrade and Enhancements

FFP

Product Upgrade and Enhancements IAW PWS 4.2.

0003 4 Each T&R Builder

FFP

T&R Builder IAW PWS 4.3.1.1. Status provided at quarterly scheduled IPR's.

0004 4 Each Electronic Aviation Training Form (EATF)

FFP

Electronic Aviation Training Form (EATF) Advanced Analytical and Reporting functionality IAW PWS 4.3.1.2.

0005 4 Each Core Competency Resource Model (CCRM)

FFP

Core Competency Resource Model (CCRM) - Phase 1 IAW PWS 4.3.1.3. Status provided at quarterly scheduled IPR's.

0006 4 Each Outlook Mail Functionality

FFP

Outlook Mail Connectivity Functionality IAW PWS 4.3.1.4.

Travel

COST

Travel IAW PWS 3.3.

Government directed travel in accordance with the attached PWS. The

Government estimate for this line item is $86,250.00. This is a NTE cost reimbursable, non-fee bearing line item. Travel shall be in direct support of tasks within the attached PWS and will be reimbursed only in accordance with FAR

Part 31 and only up to the NTE amount identified in this order or as modified by the Government. As stated in FAR 31.2, per diem costs that exceed the rates in the Joint Travel Regulations (JTR) will be found unreasonable. Non-local travel is defined as travel outside a 50-mile radius of the Government's site.

ESTIMATED COST

1001 12 Months OPTION System Maintenance and Sustainment

FFP

1002 12 Months OPTION Product Upgrade and Enhancements

FFP

1003 4 Each OPTION Core Competency Resource Model - Phase 2

FFP

Core Competency Resource Model - Phase 2 IAW PWS 4.3.2.1

1004 4 Each OPTION Self Service Business Intelligence

FFP

Self Service Business Intelligence IAW PWS 4.3.2.2.

1005 4 Each OPTION Operations Duty Officer (ODO) Module

FFP

Operations Duty Officer (ODO) Module IAW PWS 4.3.2.3.

1006 4 Each OPTION Read and Initial Functionality

FFP

Read and Initial Functionality IAW PWS 4.3.2.4.

1007 4 Each OPTION Core Model Training Report Functionality

FFP

Core Model Training Report Functionality IAW PWS 4.3.2.5.

1008 4 Each OPTION ORM Status Report Functionality

FFP

ORM Status Report Functionality IAW PWS 4.3.2.6.

1009 4 Each OPTION Interface with (ALIS)/TMS)

FFP

Interface with (ALIS)/TMS) IAW PWS 4.3.2.7.

1010 4 Each OPTION Interface with SHARP

FFP

Interface with SHARP IAW PWS 4.3.2.8

1011 4 Each OPTION Interface with integrated Training Solut

FFP

Interface with integrated Training Solutions IAW PWS 4.3.2.9.

OPTION Travel reimbursable, non-fee bearing line item. Travel shall be in direct support of tasks within the attached PWS and will be reimbursed only in accordance with FAR

Part 31 and only up to the NTE amount identified in this order or as modified by the Government. As stated in FAR 31.2, per diem costs that exceed the rates in the Joint Travel Regulations (JTR) will be found unreasonable. The Government will not reimburse local travel. Non-local travel is defined as travel outside a 50-mile radius of the Government's site.

2001 12 Months OPTION System Maintenance and Sustainment

FFP

2002 12 Months OPTION Product Upgrade and Enhancements

FFP

2003 4 Each OPTION Publication Library

FFP

Publication Library IAW PWS 4.4.3.1.

2004 4 Each OPTION Scheduling/Logger Enhanced Functionality

FFP

Scheduling/Logger Enhanced Functionality IAW PWS 4.4.3.2.

2005 4 Each OPTION Interface with MCTIMS

FFP

Interface with MCTIMS IAW PWS 4.4.3.3.

2006 4 Each OPTION Interface with DRRS-MC

FFP

Interface with DRRS-MC 4.4.3.4.

OPTION Travel reimbursable, non-fee bearing line item. Travel shall be in direct support of tasks within the attached PWS and will be reimbursed only in accordance with FAR

Part 31 and only up to the NTE amount identified in this order or as modified by the Government. As stated in FAR 31.2, per diem costs that exceed the rates in the Joint Travel Regulations (JTR) will be found unreasonable. Non-local travel is defined as travel outside a 50-mile radius of the Government's site.

PWS

PERFORMANCE WORK STATEMENT (PWS)

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

MARINE SIERRA HOTEL AVIATION READINESS PROGRAM (M-SHARP)

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 twelfth 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 and implement new and enhanced functionality of the application by July 2020 and beyond to fully support the Fleet

Marine Forces, Headquarters Marine Corps (HQMC) and Aviation Training System (ATS) needs of Marine aviation, allow more simulator and ground utilization, increase functionality on multiplatform based systems, and increased security and current functionality. 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 and 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) continue the development of M-SHARP through sustainment of current capabilities and development of additional needed functionalities; (2) continue building, fielding, and supporting an integrated web-based and stand-alone (deployable) application for the Units; and (3) 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 10 and 11 for details.

3.2. Security

Security clearances up to the level of “Secret” will be required for facility access at designated locations. A

Department of Defense (DoD) Contract Security Classification Specification (DD 254) will be executed to support security measures in place and applicable to performance of tasks. Privacy and Security Non-Disclosure Statements shall be required for all employees working on this contract. Personnel shall adhere to the Privacy Act, Title 5 of the

U.S. Code, Section 552a and applicable agency rules and regulations. The Contractor’s employees shall be required to follow installation access procedures.

Common Access Cards (CACs)

The Contractor shall be required to obtain Common Access Cards. The Contracting Officer’s Representative

(COR), or ASB designated government employee, will establish and maintain sponsorship in Defense Enrollment

Eligibility Reporting System (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 CAC issuance.

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

Establish the affiliation with the service or agency.

CACs will only be issued to those Contractors supporting that have been authorized by the 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 8510.01 dated March 12, 2014; Risk Management Framework (RMF) for DoD Information

Technology (IT).

DoDI 8500.01 dated March 14, 2014; CyberSecurity.

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, reviewed quarterly, and modified only through bilateral agreement between the Government and the Program Manager, at which time both parties will sign the updated Master Project Schedule. 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 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.

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 Enhanced Functionality, Forward Air

Controller Airborne (FAC-A) Logger; ATS, T&R Builder, Marine Aviation Data Warehouse (M-ADW) and associated Reporting Capability Enhancements, Electronic Aviation Training Form (EATF) functionality, Sortie

Based Training Program (SBTP) and Operational Forecasting, M-SHARP Deployable functionality and updates, and system updates/upgrades.

The contractor shall continue to maintain and support the M-SHARP 1.0 Stand-Alone Deployable solution until a viable 2.0 solution is created.

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.

4.1.2. Routine Updates

4.1.2.1. Training and Readiness Manual Updates:

Updates shall be made in accordance with the NAVMC 3500.14, M-SHARP Help Desk, and TECOM Leadership

(COR, Government Program Manager (GPM), etc.) to Type/Model/Series (T/M/S) and MOS specific Aviation

T&R Manuals (approximately 40 manuals in the M-SHARP data base, averaging out to 15 per year). The contractor shall coordinate the release timeframe with the COR for the necessary changes. The contractor shall make recommendation of the best possible vehicle in which to notify the affected Units (usually via phone communication by TECOM ASB and appropriate syllabus sponsor). Per the most current NAVMC 3500.14, Units using a deployable instance during the timeframe of any changes will not be expected to operate under the updated manual guidance until returning to their garrison assignment. T&R Manuals are rewritten or updated on approximately a 3 year cycle, with daily system utilization.

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 (unclassified) 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-MC initiatives, to include the eventual integration and data feed from M-SHARP to DRRS-MC.

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.

The Contractor shall provide Operational Forecasting ability to predict deficiencies in training and readiness and provide units with the potential of planning various activities into the future.

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.

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); MCAS Futenma, Okinawa, Japan.

Contractor personnel supporting the above listed MCASs shall share the task of servicing, on an as needed basis, Marine Forces Reserve units and all active reserve units not physically located at a major MCAS.

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 school house 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-

Travel is anticipated in support of this requirement.

Destination Purpose Estimated

# of trips

Personnel

Required (FTE per trip)

Estimated Length of trip (excluding travel)

4th Marine Air Wing

(MAW) Units:

Conduct training and on-site support to 4th MAW units

- McGuire AFB, NJ

- Norfolk, VA

- Fort Worth, TX

- New Orleans, LA

- Stewart AFB, NY

6 total trips in support of

4th MAW units.

1 3 days per trip

I MAW units:

Iwakuni, Japan

Conduct training and on-site support to I MAW units

4 1 3 days per trip

2MAW Units, Conduct support analysis/ training; observe /elicit input on

FSR services to 2nd MAW units

- MCAS Beaufort, SC

- MCAS Cherry Point, NC

- MCAS New River, NC

2 1 5 days per trip

San Diego, CA Quarterly Project Management briefs

4 1 4 days per trip

San Diego, CA Quarterly Requirements Review 4 2 4 days per trip

Naval Air Station

(NAS) Meridian

Operations Administrator

Course Computer

1 1 2 days per trip

Marine

Expeditionary Units

(MEU) Various

Ships

Deploying Group Systems

Integration Testing (DGSIT)

Support;

installation and testing of software aboard ship

4 1 5 days per trip

MCAS Miramar, CA and/or

MCAS Yuma, AZ

Provide SME Support for T&R review and development as required

4 2 4 days per trip

MCAS Cherry

Point, NC

MCAS Miramar, CA

MCAS Yuma, AZ

Provide SME Support toward

USMC Aviation conferences/ briefs as required

2 1

4 days per trip

4.1.3.2 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 Support page, incorporated in the main M-

SHARP site, 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 %).

4.1.4. 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.5 Technical Requirements

4.1.5.1 Accreditation and Information Assurance (IA).

The Contractor shall adhere to all updated policies and requirements per TECOM G-6. Management of IA testing related activities shall be consistent with program acquisition category (ACAT) levels, milestone schedules, and overarching policy requirements

4.1.5.2.1 Certification and Accreditation (C&A) Analysis

4.1.5.2.1 Marine Corps Certification and Accreditation Support Tool (MCCAST) and Federal Risk

Management Framework (RMF)

The Contractor shall use MCCAST to complete the RMF for all TECOM, Training Command (TRNGCMD) and

Education Command (EDCOM) Information Systems (ISs), Enclaves and applications under the purview of the

TECOM Information System Security Manager (ISSM), Chief Information Officer (CIO) and G-6 per DoDI

8510.01.

4.1.5.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 Enterprise Information

Technology Services, MCEITS; 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 C&A documentation and 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.5.2.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 C&A and provide recommendations to the ISSM of MCEITS that integrate with established Marine Corps cybersecurity directives.

4.1.5.2.4 C&A Packages:

The Contractor shall develop and maintain C&A packages, and perform weekly quality assurance reviews with the

ISSM, in accordance with the RMF and Marine Corps C&A processes. A C&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, etc.

4.1.5.2.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.5.2.6 Marine Corps Enterprise Network (MCEN) Compliance

On a monthly 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.5.2.6 Information Systems Security Analysis

4.1.5.3.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.5.3.2 Cyber Threat Analysis:

On a daily basis, the Contractor shall review Marine Corps Information Assurance Vulnerability Alerts (IAVA), Information Assurance Vulnerability Bulletin (IAVB), Information Assurance Technical Advisories (IAVT) notices, Communication Tasking Orders (CTOs), and Marine Collection Database (MCD) and provide recommended action and Cyber Threat Analysis in the POA&M (stored in the accreditation package, housed in

MCEITS and reviewed weekly by MCEITS) to address operational impacts to TECOM hardware, software and network requirements. The Contractor shall provide MCEITS a weekly summary of the Information Assurance

Vulnerability Management (IAVM) and Marine Corps Directive (MCD) actions taken to MCEITS ISSM.

4.1.5.3.3 Incident Response:

The Contractor shall assist, as required by requesting government agency, with investigating events related to threats to confidentiality, integrity, and availability of Marine Corps hardware, software, and networks and provide analysis of log files and reporting.

4.1.5.3.4 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.

4.1.5.3.5 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.6. 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.6.1. Server and Database Replication

The Contractor shall maintain server architecture to ensure replication of data between at least two (2) server clusters located at two (2) or more separate geographical locations within the contiguous United States as determined by mutual agreement between the Contractor and COR. Each cluster will contain real-time mirrored copies of all M-SHARP databases.

4.1.6.2.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 complete 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 Authorization Agreement (SSAA)

4.1.6.3.Software Updates and Patches

The Contractor shall provide software updates and patches as required to sustain and maintain system functionality.

Routine software updates and patches will be approved by the COR for contractor development, implementation, and distribution to the fleet. Once approved by the COR, the contractor shall develop and implement the approved software changes, updates or patches and notify users of the updated software releases. Documentation of approved software changes, updates, patches and notification of software releases shall be provided by the

Contractor to the COR at the end of each update iteration.

The Contractor shall provide notifications of M-SHARP software releases via the M-SHARP website and the M-

SHARP Support web site. Software releases shall be automated and executed in a manner that informs the user

(upon logon) of the release. Under rare circumstance, Units using a deployable instance may be updated manually via Compact Disc (CD). Optimally deployed units will continue to operate with the M-SHARP Deployable instance issued upon their departure.

For emergency fixes or bugs requiring immediate release, the Contractor shall develop a fix or patch and, with

COR approval, release the fix as soon as possible.

4.1.6.4. NALCOMIS Data Transfer

The Contractor shall support M-SHARP continuous, daily data feeds to Naval Aviation Logistics Command

Management Information System (NALCOMIS). Methods used for data transfer to NALCOMIS shall be electronic; either copying of files to a network location or having files automatically extracted and placed on a network location for NALCOMIS consumption. Use of multimedia disks to move data via “sneaker-net” is not permitted except where shipboard or austere conditions prevent connectivity among M-SHARP and NALCOMIS.

The determination of whether such an exception applies shall be at the discretion of the Government personnel appointed as IT systems manager of the ship or unit. TECOM ASB will identify and communicate this requirement to NALCOMIS Program Managers. This shall be the standard operating procedure until M-SHARP and

NALCOMIS achieve interoperability.

4.2. Product Upgrade and Enhancements

4.2.1 System Enhancements

The contractor shall review/refine software requirements with designated Government SMEs, describe Marine functional necessity which mirrors training and readiness management requirements as documented in governing publications, and describe functional characteristics which are required to satisfy Marine Aviation training and readiness management reality. The contractor shall provide recommendations for enhanced functionality to all current functional capability. These recommendations shall be provided to the COR and GPM and upon COR approval, updated in the Master Project Schedule.

4.2.2 Routine Upgrades

The Contractor, in conjunction with designated ASB government experts, shall coordinate with other units or agencies as necessary to communicate and refine software requirements with appropriate SMEs to aid in design and development of the system, describe Marine functional necessity which mirrors training and readiness management requirements as documented in governing publications, and describe functional characteristics which are required to satisfy Marine Aviation training and readiness management reality.

4.2.3 M-SHARP Users’ Group (MUG) (Product Steering)

The Contractor shall provide MUG (Product Steering) support. MUG will be conducted to receive fleet and user feedback to define and support future requirements for M-SHARP software. The Contractor’s Key Personnel shall participate in the MUG committee to be held as required but no more than twice a year. Contractor participation shall include:

Providing expertise to the MUG committee regarding proposed M-SHARP upgrades and updates.

Develop, capture and compile data and distribute to the COR minutes of meetings, to include the tracking of action items, and capturing Software Change Requests for incorporation into the Software

Change Configuration Board process.

Providing M-SHARP update briefs to Marine Forces and briefing assistance to the GPM on an as needed basis and as coordinated with TECOM ASB.

Provide demonstrations for the users to conduct “hands-on” evaluation of functionality and functionality changes prior to delivery.

Provide recommendation via a report no later than (NLT) 30 calendar days after the MUG to the GPM and COR for future functionality based on user inputs, emerging technology, and analysis.

4.2.4 Update Notifications

The Contractor shall provide notification of future developments (through customer support representatives to individual units, and/or via official message through TECOM ASB) per the COR’s guidance regarding proposed and scheduled product upgrades via the M-SHARP site and the M-SHARP User Support Web Site.

4.2.5 User Milestone Functionality Checks.

The Contractor shall provide a method by which the government COR and users (Marine Forces active and reserve units) can verify application functionality at stated (Master Schedule) milestones (partial capabilities demonstrating a functioning business rule or training and readiness management process). This is not intended to limit user feedback to milestone events. Interim functionality checks (in support of the Master Schedule) with the users are encouraged.

4.3 Develop New M-SHARP functionality:

4.3.1 Base Year Tasks

4.3.1.1 T&R Builder Module

The Contractor shall design, develop, and implement a program that provides the end user the ability to input data into a user friendly environment, which results in a real time fully functional and printable draft T&R manual in accordance with the Program Manual NAVMC 3500.14. This functionality shall be delivered to the Government

NLT 365 days after contract award.

T&R Builder shall include the necessary framework to create, edit, and publish draft/versioned manuals.

T&R Builder shall interface with CCRM and EATF in a draft format, in order to provide the user the ability to see the effects of draft T&R changes on a mock CCRM and EATF in real or near real time.

T&R Builder shall link connected parts of the manual IOT reduce input redundancies and errors.

T&R Builder shall allow multiple users with M-SHARP system access to edit the document simultaneously.

4.3.1.2 Electronic Aviation Training Form (EATF) Advanced Analytical and Reporting Functionality

The Contractor shall design, develop, integrate, and implement functionality that will automatically generate, populate and provide output and track completion of aviation training forms (ATFs) to support the training execution of flights, simulator, and ground events, identify trends and improving student/instructor/squadron/training system performance, and improve reporting and notification capability. This functionality shall be delivered to the Government NLT 365 days after contract award.

Develop and implement instructor grading analysis in order to provide units with data to report on performance metrics of instructors and how they relate over curriculum spectrum (to include phases, stages, and skills).

Develop and implement Grade Point Average reporting.

Develop and implement student performance analysis in order to provide Units with data on performance metrics of students and how they relate over curriculum spectrum (to include phases, stages, and skills).

Develop and implement a database of performance metrics and reason codes, which correlate with MAWTS-1 grading criteria.

Develop the ability to create and print kneeboard cards of the EATF to use during flight operations.

Create user and instructor roles depending on M-SHARP unit assignment.

Develop interface capability to pull and use analytical data from the Integrated Training Solution (ITS) system.

Develop capability to transfer all M-SHARP 1.0 EATFs.

Develop the capability to transfer Excel EATFs.

4.3.1.3 Core Competency Resource Model (CCRM) Module – Phase 1

The Contractor shall design, develop, and implement functionality to automatically create, calculate and adjust the

Core Competency Resource Model. The following functionality shall be delivered to the Government NLT 365 days after contract award

4.3.1.3.1…