PWS_MSHARP_draft.pdf

PERFORMANCE WORK STATEMENT (PWS)

For

TRAINING AND EDUCATION COMMAND (TECOM), AVIATION STANDARDS BRANCH

(ASB):

MARINE SIERRA HOTEL AVIATION READINESS PROGRAM (M-SHARP)

1. Background

1.1. The Marine Corps acquired the Squadron Assistance / Risk Assessment (SARA) program, as a stand-alone application installed on client systems utilizing Microsoft Access to provide the tools necessary to conduct training and readiness management within operations departments of United States

Marine Corps (USMC) squadrons. Data was updated by two (2) primary means: either manually, whereby the user configures the database, baselines information, and enters individual training events for all assigned personnel or via external media transfer from Naval Aviation Logistics Command

Management Information System (NALCOMIS) data exports of executed flight events. It provided customizable interfaces and ad-hoc querying and reporting. Performance was based upon the configuration and quality of the client system on which the application was loaded and the number of users requiring access to it. Software updates/upgrades to the application were executed via installation executables and patches. Database updates were manually configured by the users based on formal policy releases. SARA was proprietary property and subject to software licensing and distribution solely by the contractor including help desk support and training.

1.2. Technological advances and dependencies warranted real-time forecasting, scheduling, execution, and reporting of accurate data and information. SARA had become an archaic tool dependent on aged non-accessible applications that require intense training and administration to maintain accuracy. Marine

Corps Sierra Hotel Aviation Readiness Program (M-SHARP) was based on the concept that a Marine

Corps Aviation automated training management system was required to be a web-based application in order to automate the training management processes of all Marine Aviation and Aviation Ground (i.e.

non-flying) units. Specific functions include the capture and maintenance of daily training data, scheduling and validation of flight and ground training schedules against established rules and regulations, maintenance of Training and Readiness manuals, monthly export of database information to a data warehouse, maintenance of standardized reports, and a report interface enabling users to create, build, filter, and sort their own reports to summarize virtually any aspect of their training management data. Furthermore, it should be noted that the M-SHARP system including the website, application and other M-SHARP items, materials and information are government owned.

1.3. The M-SHARP application continues to provide a standardized means for scheduling and planning training and allows the fleet to compare their present and expected training readiness to establish standards. M-SHARP application increased functionality and sustainment will allow for ground and other units to use and build on current capabilities and use.

2. Scope

2.1. The objective of this requirement is to continue execution of the efforts to deploy and support M-

SHARP and implementation of enhanced functionality of the application by July 2017 and beyond to fully support the operational and Aviation Training System needs of Marine aviation, allow more simulator and ground utilization, increase functionality on multiplatform based systems, and increased security and current functionality.

2.2. M-SHARP is moving forward into its eighth 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 focus of this effort is to finalize the development of M-

SHARP through sustainment and development of additional needed functionalities and embed the application into the Units, as well as providing the Higher Headquarters (HHQ) elements with reporting services necessary for the collection of data required to justify budgetary decisions. Sustained development and support of a user friendly, web-based and stand-alone application with the characteristics described below 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 requirement is for Training, Operational Risk, Readiness, and Document Management and Stand-Alone

(Deployable) Operability.

3. General Requirement:

3.1. The Contractor shall develop, update, integrate, and maintain M-SHARP in accordance with established specifications and standards in order to sustain and enhance the capabilities of Unit training and readiness management. 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, integration within service level domains, and provide insight into the budgetary effect of Training and Readiness.

3.2. As historical data begins to accumulate to a point of full utility, higher headquarter 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.

3.3. The contractor shall continue building, fielding, and supporting an integrated web-based and stand-alone application with the characteristics described herein for the Units. This effort will be accomplished over the contract’s period of performance. The contractor shall provide recommendations of activities to define and enhance functionality. These recommendations shall be provided to the

Contracting Officer’s Representative (COR) in the 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. The Program, Product, Test, Development Leads, and Aviation Data Warehouse Manager are considered Key Personnel for this requirement.

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

Subject Matter Experts (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.

3.5. Unless otherwise directed by the COR, all services shall be accomplished in accordance with the most current version of the following references.

Office of the Chief of Naval Operations Instruction (OPNAVINST) 3710.7(Series); Naval Air

Training and Operations Procedures Standardization (NATOPS) Program General Flight and

Operating Instructions.

Navy and Marine Corps (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.

Marine Corps Order (MCO) 3125.1(Series); Marine Corps Flying Hour Program (FHP)

Management.

Department of Defense (DoD) Directive 7730.65 dated Jun 2002; Defense Readiness Reporting

System (DRRS) guidance.

Interim Defense Readiness Reporting System (DRRS) Policy and Procedures for Marine Corps

Units and Installations.

Department of Defense (DoD) Instruction 8550.01 dated Sept 2012; DoD Internet Services and

Internet-Based Capabilities.

4. Base Year Tasks

4.1. Aviation Training Systems (ATS) functionality – Phase 1. The Contractor shall:

4.1.1 Design, develop and enhance the existing simulator scheduling functionality to enable more efficient identification of networking and linked capabilities as well as all necessary resources associated with executing training events within the simulator devices. The Contractor shall include the capability to auto populate the simulator scheduling module with events created within the flight scheduler module of the application.

4.1.2 Design, develop, and incorporate interoperability between the logging of simulator events and the simulator scheduling module to identify execution and completion of training.

4.1.3 Upon completion of Tasks 4.1.1-4.1.3, identify Aviation Distributed Virtual Training

Environment (ADVTE) requirements and capabilities necessary to be performed within M-

SHARP.

4.2 T&R Builder - Phase 1. The Contractor shall:

4.2.1 Re-design, develop, and implement a modular architecture in order to provide efficiencies in creating a fully functional T&R Manual within the application in support of periodic T&R policy updates.

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

4.3. Unmanned Aerial Systems (UAS) Scheduling/Logger Functionality. The Contractor shall develop and implement functionality to:

4.3.1 Optimize unit scheduling specific to the UAS community in conjunction with requirements specified with the OPNAV 3710.7X Chapter 8 business rules.

4.3.2 Optimize unit flight logging specific to the UAS community in conjunction with requirements specified with the OPNAV 3710.7X Chapter 8 business rules.

4.4. Marine Aviation Data Warehouse (M-ADW) Enhancements 1. The Contractor shall, continue the refinement of the unclassified automated data warehouse to capture and store Unit training, flight hour, and readiness management data with a capacity to retrieve and analyze historical data. The Contractor (or

M-ADW) shall support various permission levels and custom report queries as required.

4.5. Accreditation and Information Assurance (IA). The contractor shall provide Information

Assurance support. This includes the planning, review, reporting, tracking, and management of IA documentation and the technical analysis of the M-SHARP information system IA Certification and

Accreditation (C&A) posture against DoD, US Department of Navy and Marine Corps security standards.

Key support requirements include an understanding and application of the following:

1. DoD 8510.01 DoD information Assurance Certification and Accreditation Process (DIACAP,

2. DoD 8500.2 IA control compliance requirements

3. Defense Information System Agency (DISA) Security Technical Implementation Guides (STIGs)

4. NIST IA control compliance requirements

5. Management of IA testing related activities consistent with program ACAT levels, milestone schedules, and overarching policy requirements.

4.6. System Sustainment: The Contractor shall maintain M-SHARP and M-SHARP Deployable, and

M-ADW, in accordance with the established specifications, and standards. The Contractor shall make recommendations regarding functionality enhancements which contribute to the effectiveness of training and readiness.

4.6.1. Software Updates and Patches

4.6.1.1. 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. These changes shall be identified during each iteration, usually four (4) to five (5) times a year

4.6.1.2. For emergency fixes or bugs requiring immediate release, the Contractor shall develop a fix or patch and, with COR approval, release the fix without waiting for the next iteration.

4.6.1.3. The contractor shall provide notifications of M-SHARP software releases via 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.

4.6.2 Training and Readiness Manual Updates:

4.6.2.1 Updates shall be made continuously to T/M/S and MOS specific Aviation T&R Manuals. 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

Naval Message released by TECOM (ASB)). 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.

4.6.3. On-Site Technical Support

4.6.3.1. The contractor shall provide on-site technical support to using Units. On-site technical support is defined as, “The physical or virtual presence of an M-SHARP knowledgeable contractor professional who provides troubleshooting, technical, and/or functional assistance to using Unit.” On-site technical support includes initial training, recurring training, and troubleshooting of the M-SHARP application to the extent required by the using Units. 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 Marine Corps Air Stations identified below.

4.6.3.2. On-site technical support shall consist of M-SHARP proficient contractors spread evenly throughout the Marine Corps Air Stations (MCAS), TECOM (ASB) and Headquarters Marine Corps.

These on-site contractors shall share the task of servicing Marine Forces Reserve units and all active reserve units not physically located at a major MCAS.

1. MCAS Cherry Point, NC

2. MCAS New River, NC

3. MCAS Beaufort, SC

4. MCAS Yuma, AZ

5. MCAS Camp Pendleton, CA

6. MCAS Miramar, CA

7. MCAS Kaneohe Bay, HI

8. MCAS Futenma, Okinawa, Japan

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

4.6.4. Help Desk and Tools

4.6.4.1. 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 to recommend software enhancements, report anomalies, request accounts, and request on-site training.

These recommendations will be vetted and implemented into M-SHARP based on the Program

Manager’s decision regarding necessity and relevance of each request. The Program Manager will prioritize the need of each recommendation.

4.6.4.2. 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).

4.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.8 User Group Support.

4.8.1 M-SHARP Users’ Group Membership (Product Steering). The Contractor shall participate in the

M-SHARP Users’ Group (MUG) committee to be held, at a minimum, semi-annually and no more than five (5) times per year. Contractor participation shall include:

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

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

3. Providing M-SHARP update briefs to Marine Forces and briefing assistance to the government Program Manager on an as needed basis and as coordinated with TECOM

(ASB).

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

4.8.2. Product Upgrade Status (M-SHARP User Support Web Site). The contractor shall provide notification of future developments regarding proposed and scheduled product upgrades via the M-

SHARP User Support Web Site, which is currently a “.com” site, but may migrate to a “.mil. location.

4.8.3. Updates to User Documentation. The contractor shall provide updates to electronic documentation via a Software User’s Manual (SUM) made available to users in order to ensure the

Marine Forces user information matches the software version fielded.

4.8.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; this applies to the development phases as well. The contractor shall make the web site accessible to the using units upon approval by the COR.

4.8.5 User Group Milestone Functionality Checks. The contractor shall provide a method by which the government COR and designated user groups 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 group feedback to milestone events.

Interim functionality checks with the user group are encouraged.

4.9. Tracking/Training Management

4.9.1. The Contractor shall manage all flight, ground, simulator, resource, and duty scheduling, to include automated tracking, logging, and reporting of qualifications, designations, proficiency and flight hours in accordance with the business rules identified within the NAVMC 3500.14.

4.9.2. Initial and Follow-On Training. The Contractor shall set up the M-SHARP system for squadrons

(including detachments), Marine Air Groups, Marine Air Wings, Marine Forces, aviation ground units and detachments, Marine Aviation Weapons and Tactics Squadron One (MAWTS-1), TECOM (ASB), and HQMC. Setup shall include training required for units. 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. Additionally, users at the Marine Aircraft Group (MAG), Wing, Installations, Marine Forces

(MARFOR), Headquarters, and TECOM (ASB) levels 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 on-site technical support Contractor based upon using unit requests and/or observed areas of interest or concern.

4.10. 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. 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 Military Standard 498 (MIL-STD-498); Including the:

1. Database Design Description (DBDD)

2. Operational Concept Description (OCD)

3. Software Design Description (SDD)

4. Software Development Plan (SDP)

5. Software Test Description (STD)

6. Software Test Plan (STP)

7. Software Test Report (STR)

8. Software Version Description (SVD)

9. System Security Authorization Agreement (SSAA)

4.11. Naval Aviation Logistics Command Management Information System (NALCOMIS) Data

Extracts. The Contractor shall support M-SHARP data feeds to 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.

4.12. 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. Each cluster will contain real-time mirrored copies of all M-SHARP databases.

4.13. 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, MCO

3125.1, OPNAVINST 3710.7, as well as the ability to automate local rules and regulations through creation of decision trees.

4.14. Readiness Management. The Contractor shall compute Core Skill Proficiency (CSP) and Mission

Skill Proficiency (MSP) with real-time unit Training and Readiness reporting (unclassified) via the

Sortie-Based Training Plan (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.

5. Option Year One (1) Tasks: Option Year tasks may be exercised upon award or by modification.

The option year one (1) tasks are as follows:

5.1. Aviation Training Systems (ATS) functionality Enhancements – Phase 2. The Contractor shall:

5.1.1 Enhance the existing simulator utilization report in order to provide a more thorough documentation of executed training relative to scheduled training and utilization.

5.1.2 Design, develop, and implement a simulator corrected flight schedule report based upon scheduled events vs. executed events vs. unscheduled events at each individual MATSS facility.

5.2. T&R Builder - Phase 2. The Contractor shall:

5.2.1. Re-design, develop, and implement a modular architecture in order to provide efficiencies in creating a fully functional T&R Manual within the application in support of periodic T&R policy updates.

5.2.2. T&R Builder Phase 2 enhancements shall include the necessary design, development, and implementation of input and export interfaces to be utilized by TECOM(AS) Subject Matter Experts and

MAWTS-1 T&R Model Managers in the periodic and preparatory actions of updating T&R Manuals.

5.3. Marine Aviation Data Warehouse (M-ADW) Enhancements 2. The Contractor shall, continue the refinement of the unclassified Automated Data Warehouse that shall provide the ability to capture and store Unit simulator, ranges, and ordnance training data.

5.4. Accreditation and Information Assurance (IA). The Contractor shall, continue to provide

Information Assurance support. This includes the planning, review, reporting, tracking, and management of IA documentation and the technical analysis of the M-SHARP information system IA Certification and

Accreditation (C&A) posture against DoD, US Department of Navy and Marine Corps security standards.

Key support requires an understanding and application of the following:

1. DoD 8510.01 DoD information Assurance Certification and Accreditation Process (DIACAP)

2. DoD 8500.2 IA control compliance requirements

3. Defense Information System Agency (DISA) Security Technical Implementation Guides (STIGs)

4. NIST IA control compliance requirements

5. Management of IA testing related activities consistent with program ACAT levels, milestone schedules, and overarching policy requirements

5.5. System Sustainment. IAW 4.9, the Contractor shall maintain M-SHARP and M-SHARP

Deployable, including patches and updates, in accordance with the established specifications and standards.

5.6. Operations Duty Officer (ODO) Module. The Contractor shall design, develop, and implement an interface which provides the ODO with the interactive capability to update scheduled event data as it is executed, creating efficiencies in the flight logging process.

5.7. Electronic Aviation Training Form (EATF) functionality. The Contractor shall design, develop, integrate, 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, to include reporting and notification capability.

5.8. Core Competency Resource Model (CCRM) – Flight Hours. The Contractor shall enhance functionality in order to accommodate the compensation of future year Flight Hour Program management adjustments and calculations.

5.9. Core Competency Resource Model (CCRM) – Simulators. The Contractor shall design, develop and implement functionality that will capture simulator resource requirements involved in the planning and management of individual and Unit training. This functionality will include a reporting capability.

5.10. Interface with Optimized Organizational Maintenance Activity-Naval Aviation Logistics Command

Management Information System (OOMA-NALCOMIS). The Contractor shall design, develop and implement an interface between M-SHARP and OOMA-NALCOMIS.

5.11. Interface with DRRS-MC. The Contractor shall design, develop and implement an interface between M-SHARP and DRRS-MC.

5.12. Interface with Sierra Hotel Aviation Readiness Program (SHARP). The Contractor shall design, develop and implement an interface between M-SHARP and SHARP.

6. Option Year Two (2) Tasks: Option Year two (2) tasks may be exercised upon award or by modification. The option year two (2) tasks are as follows:

6.1. T&R Builder Phase 3. The Contractor shall enhance the T&R Building functionality to provide tools which support model managers with construction, analysis, and validation of T&R manuals in preparation and conduct of T&R Manual Conferences.

6.2. Marine Aviation Data Warehouse (M-ADW) Enhancements 3. The Contractor shall continue the refinement of the unclassified Automated Data Warehouse that shall provide the ability to capture and analyze training and readiness event, syllabus, and POI data. The Contractor shall support permission levels and custom report queries as required.

6.3. System Sustainment. IAW 4.9, the contractor shall maintain M-SHARP and M-SHARP Deployable, including patches and updates, in accordance with the established specifications and standards.

6.4. Technological Advancements. The Contractor shall:

6.4.1 Research, identify, and with TECOM (ASB) guidance, develop the capability to utilize

MSHARP/M-ADW on any browser or computer platform.

6.4.2 Research, identify, and with TECOM (ASB) guidance, develop the capability to utilize M-

SHARP/M-ADW on mobile devices.

6.5. Core Competency Resource Model – Ordnance. The Contractor shall design, develop and implement functionality that will capture ordnance resource requirements involved in the planning and management of individual and Unit training. This functionality will include a reporting capability.

6.6. Core Competency Resource Model – Ranges. The Contractor shall design, develop and implement functionality that will capture range resource requirements involved in the planning and management of individual and Unit training. This functionality will include a reporting capability.

7. Contractor Qualification and Experience

7.1. The Contractor shall provide proof of Vendor CMMI Level 3 Certification.

7.2 Key personnel are understood to be those individuals for whom resumes were submitted and evaluated as part of the technical proposal submission. Key personnel are:

Project Lead – Initiates and establishes processes for the management of product requirements throughout their life-cycle from strategic definition to end-of-life planning. Plans and directs all specialized engineers working on specific projects. Manages the development, implementation, and evaluation of complex designs. Oversees product construction and testing in order to ensure completion of projections as efficiently and effectively as possible. Familiar with a variety of field’s concepts, practices, and procedures, relies on extensive experience and judgment to plan and accomplish goals. Leads and directs the work of others. A wide degree of creativity and latitude is expected. Typically reports to a head of a unit/department. Requirements:

Bachelor of Science (BS) in Computer Science (CS) or Engineering plus four (4) years’ experience OR;

BS plus seven (7) years’ experience OR;

Nine (9) years combined education and experience.

Project Manager – Responsible for the coordination and completion of information technology professional service projects. Oversees all aspects of IT projects to include: setting deadlines, assigning responsibilities, and monitoring and summarizing progress of IT project, prepares reports for upper management regarding status of IT projects, familiar with a variety of the information technology concepts, practices, and procedures, relies on extensive experience and judgment to plan and accomplish goals, performs a variety of tasks and leads and directs the work of others. A wide degree of creativity and latitude is expected. Typically reports to a manager or head of a unit/department. Requirements:

BS in CS or Engineering plus four (4) years’ experience OR;

Bachelor’s Degree plus seven (7) years’ experience OR;

Nine (9) years combined education and experience.

Software Development Manager – Manages a team of software engineers to architect, design enterprise software products / operating systems. Writes product requirement documents, implements and tracks development timelines, negotiates feature sets with the development leads and product. Requires experience with software development in .NET and strong relational database knowledge. Knowledge of customer relationship management, data warehousing, and business intelligence. Generally manages a group of software developers/engineers. Relies on experience and judgment to plan and accomplish goals. Typically reports to a senior manager. Requires at least two (2) years as a Software Development

Manager I or equivalent. Requirements:

BS in CS or Engineering plus six (6) years’ experience OR;

Bachelor’s Degree plus eight (8) years’ experience OR;

Thirteen (13) years’ experience AND CEO recommendation.

Product Support Engineer – Coordinates all information technology service projects and ensures company resources are utilized appropriately. Compiles IT project status reports, coordinates IT project schedules, manages IT project meetings, and identifies and resolves technical problems. Identifies and analyzes information technology system requirements and defines information technology project scope, requirements, and deliverables. Coordinates project activities and ensures all project phases are documented appropriately. Familiar with standard information technology concepts, practices, and procedures within a particular field. Relies on experience and judgment to plan and accomplish goals.

Performs a variety of tasks. A degree of creativity and latitude is required. Typically reports to a supervisor or manager. Requirements:

Bachelor’s degree and at least five (5) years of experience in the field or in a related area, OR;

Seven (7)+ years of direct or related experience in lieu of a bachelor’s degree.

Customer Support Manager – Acts as a Customer Support Information Technology professional services liaison. Takes lead with customer to ensure all IT project needs are/have been fulfilled. Responsible for designing and implementing IT operation policies, based on client experience. Recommends changes to

IT products or changes to or the addition of information technology services to fulfill customer IT needs as necessary. Familiar with a variety of the field’s information technology concepts, practices, and procedures. Relies on experience and judgment to plan and accomplish goals. Typically reports to senior manager. Requirements:

Bachelor’s degree in business, marketing, or related area, and at least seven (7) years of experience in the field.

8. Deliverables

8.1 The Contractor shall develop a Quality Management Plan (QMP) as a means for gauging overall effectiveness of performance. The contractor shall provide their Quality Plan to the COR within thirty

(30) days of award for review and comment. The QMP shall address the Contractor’s plan to meet quality and performance standards outlined in the Quality Assurance Surveillance Plan (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

8.2 The Contractor shall provide on a monthly basis a Monthly Status Report. This report shall provide updated status on all current projects and sustainment of the program. The report shall identify the contract number and Project Manager; Work scheduled; Work completed; Work to be completed within the next 30 days; any issues that arose and their resolution; pending issues and recommendations for resolution; and travel costs including purpose of trips, duration, and related actions. The report shall clearly delineate on-schedule, behind schedule, or ahead of schedule tasks. This report shall be provided in electronic form using MS applications. Additional hard copies shall be provided upon government request.

8.3 Table 1 below provides a notional schedule of deliverables associated with base year contract performance. Specific due dates will be accomplished at the POA&M review, following contract award.

The COR and the Contractor shall concur on any changes to the schedule and ensure that adherence to the revised timeline is followed.

Deliverable Ref: Content Due Date

Master Project

Schedule

3.3 -Performance and programmatic milestones

-Estimated timeline of task efforts through completion

Due to COR and designated ASB government leads within 14 days after award

Quality

Management Plan

See 8.1 Due to COR NLT thirty (30) days after award

Monthly Status

Reports

8.2 See para 8.2 Due to COR no later

than the 5 th day of the following month for the work accomplished from the first (1 st ) through the final calendar day of the previous month

Aviation Training

Systems (ATS)

Functionality (Phase

I)

4.1 Program functionality to

-Network and link devices

-Capability auto flight scheduling and logging

Due to COR and designated ASB government leads through the period of performance

T&R Builder

(Phase I)

4.2 T&R Builder

-Create, edit and publish draft manuals

Due to COR and designated ASB government leads

NLT 12 months after contract award

UAS Scheduler/

Logger

Functionality

4.3 -Unit scheduling enhancements

-Unit flight logging enhancements

Ongoing throughout period of performance

Marine Aviation

Data Warehouse (M-

ADW)

Enhancements 1

4.4 Enhanced functionality to Automated data warehouse:

Marine Aviation Data Warehouse (M-ADW)

Due within NLT 12 months after contract award

Accreditation and

Information

Assurance

4.5 -Ensure C&A compliance within DoD standards.

-Identify and implement IA requirements.

Ongoing throughout period of performance

System Sustainment 4.6 -System maintenance and functionality IAW Marine

Corps and Program Manager directives.

Ongoing throughout period of performance

Customer

Acceptance

Document (CAD)

4.6.1 Documentation of approved software changes, updates, patches; notification of software releases

Each update iteration

M-SHARP Users

Group Membership

(Product Steering)

Meetings (MUG)

Meeting Minutes

4.8 Compiled data including the tracking of action items

and Software Change Requests

Due to the COR within ten (10) days of scheduled meeting

User Training 4.9 See para 4.9.2 As required

Server data replication

4.12 See para 4.12 Ongoing through

period of performance

Reports, Briefs, and other PWS required items not captured in this chart

As requested As required

Table 1

8.4 Table 2 below provides a notional schedule of deliverables associated with option year one (1) contract performance. Specific due dates will be accomplished at the POA&M review, following contract award. The COR and the Contractor shall concur on any changes to the schedule and ensure that adherence to the revised timeline is followed.

Monthly Status

Reports

8.2 See para 8.2 Due to COR no later

than the 5 th day of the following month for the work accomplished from the first (1 st ) through the final calendar day of the previous month.

ATS Functionality

(Phase II)

5.1.1 -Enhance simulator utilization data capturing

-Program functionality for a corrected flight scheduler.

Due within 12 months of option exercise.

T&R Builder

(Phase II)

5.1.2 T&R Builder Enhancements

-audit and analyze syllabi.

Due within 12 months of option exercise.

Marine Aviation

Data Warehouse (M-

ADW)

Enhancements II

5.1.3 Enhanced functionality to Automated data warehouse:

Marine Aviation Data Warehouse (M-ADW)

Due within NLT 24 months after option exercise.

Accreditation and

Information

Assurance

5.1.4 -Ensure C&A compliance within DoD standards.

-Identify and implement IA requirements.

Ongoing throughout period of performance

System Sustainment 5.1.5 -System maintenance and functionality IAW Marine

Corps and Program Manager directives.

Ongoing throughout period of performance

Customer

Acceptance

Document (CAD)

4.6.1 Documentation of approved software changes, updates, patches; notification of software releases

Each update iteration

ODO Module 5.1.6 Interactive capability to update scheduling and logging. Due within 12 months option exercise

Electronic Aviation

Training Form

(EATF)

5.1.7 Program functionality to automatically generate, populate, provide output and track completion of

ATFs.

Due within 12 months of option exercise

CCRM Flight Hour

Enhancements

5.1.8 Functionality which captures Flight Hour CCRM

calculation updates.

Due within 12 months of option exercise

CCRM Simulators 5.1.9 Functionality which captures simulator device requirements.

Due within 12 months of option exercise

Interface OOMA-

NALCOMIS

5.1.10 Fully functional Web system interface with OOMA-

NALCOMIS

Due within 12 months of option exercise

Interface with

DRRS-MC

5.1.11 Fully functional Web system interface with DRRS-MC Due within 12 months of option exercise

Systems Interfaces with SHARP

5.1.12 Fully functional Web system interface with SHARP Due within 12 months of option exercise

Reports, Briefs, and other PWS required items not captured in this chart

Table 2

8.5 Table 3 below provides a notional schedule of deliverables associated with option year two (2) contract performance. Specific due dates will be accomplished at the POA&M review, following contract award. The COR and the Contractor shall concur on any changes to the schedule and ensure that adherence to the revised timeline is followed.

Monthly Status

Reports

8.2 See para 8.2 Due to COR no later

than the 5 th day of the following month for the work accomplished from the first (1 st ) through the final calendar day of the previous month

T&R Builder

(Phase III)

6.1 T&R Builder Enhancements

-Enhanced functionality.

Due within 12 months of option exercise

Marine Aviation

Data Warehouse (M-

ADW) (Phase III)

6.2 Enhance functionality to Automated data warehouse:

Marine Aviation Data Warehouse (M-ADW).

Due within 12 months of option exercise

System Sustainment 6.3 -System maintenance and functionality IAW Marine

Corps and Program Manager directives.

Ongoing throughout period of performance

Customer

Acceptance

Document (CAD)

4.6.1 Documentation of approved software changes, updates, patches; notification of software releases

Each update iteration

Technological

Advancements

6.4 -Program functionality for utilization on any computer platform and browser.

-Develop functionality for mobile devices.

Due within 12 months of option exercised

CCRM Ordnance 6.5 Functionality which captures ordnance resource requirements.

Due within 12 months of option exercised

CCRM Ranges 6.6 Functionality which captures range resource requirements.

Due within 90 days of option exercised

Reports, Briefs, and other PWS required items not captured in this chart

Table 3

9. Deliverables, Handling, and Use of Items and Intellectual Property

9.1. Deliverables are identified within the Tasks and/or are summarized within this PWS/task order. Execution of the PWS tasks will frequently yield deliverables in the form of, but not limited to, reports, papers, and presentation packages such as PowerPoint briefings, slides, computations with backup information, databases and database-related items, website and website-related items, graphics, visual aids, and meeting minutes. Reports shall contain information in sufficient detail to ensure that a professionally qualified third party can follow the logic of the report(s). Government review comments shall be incorporated into the final deliverable in the form of revisions, deletions, additions and corrections.

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

9.3. No data, materials, information or other items (hereinafter singularly or collectively “Items”) created or provided expressly for this PWS shall be used by the Contractor for any purpose other than those that are in support of, or for performance under, this PWS without the prior written permission of the

Contracting Officer. The Contractor is obligated to protect from unauthorized use or disclosure all

Government confidential or classified material and/or Government-owned proprietary, and/or Personally

Identifiable Information or Personal Privacy, Items obtained in the course of performance under the

Government contract, as long as such Items remains proprietary, confidential, sensitive or classified. Any information obtained in the course of duties, or the performance of services, under this contract including, but not limited to, information that may be made available for use that relates to the technical data, trade secrets, processes, operations, style of work, or apparatus, or to the technical data, statistical data, amount or source of any income, profits, losses, or expenditures of any person, firm, partnership, corporation, or association is included in this clause (and with “Items”). Contract personnel shall not publish, divulge, disclose, or make known Items in any manner, or to any extent not authorized by the Contracting Officer.

When the Contractor’s need for any Items ends, the Items shall be returned promptly (within ten (10) business days) to the appropriate government program personnel. However, the obligation not to discuss, disclose, release, reproduce or otherwise provide or make available such Items, or any portion thereof, shall continue, even after completion of this contract/order. Any actual or suspected unauthorized use, disclosure, release, or reproduction of any Items or violation of this agreement, of which the company or any employee is or may become aware, will be reported promptly (within one business day) to the

Contractor’s program manager, who will inform the Contracting Officer within five (5) business days of receiving such report.

9.4. All Items and or deliverables generated by the Contractor under this PWS, and all associated intellectual property, in whatever form, created, generated, or produced under this PWS shall become the property of the U.S. Government/Marine Corps and not the Contractor, subcontractor, or individual author or researcher; therefore, the U.S. Government/Marine Corps shall have the irrevocable, royalty-free, worldwide right to use, modify, reproduce, perform, display, release, or disclose such Items, in whole or in part, in any manner, and for any purpose whatsoever, and to have or authorize others to do so.

The contract will include DFARS 252.227-7020.

9.5. All Contractor developed databases and database related items, all website and website-related items, analyses, studies, applications, information, and all associated intellectual property, completed or in progress under the contract shall be solely and fully owned by the Government. During the transition period, the Contractor shall turn over such documents, information, and all associated intellectual property, to the Government if not already delivered.

9.6. Distribution, Media and Format.

9.6.1. Unless otherwise directed by the COR, see the PWS for required distribution, media and format. The Marine Corps shall have unrestricted access and use of all deliverables upon delivery. The Contractor shall provide all deliverables in a version, format, and media used/useable and modifiable by the Marine Corps.

10. Meetings.

10.1 Periodic meetings involving the government and the contractor are necessary to facilitate documentation and analytical support efforts. Date, time, and location for these meetings will be determined by mutual agreement between the Contractor and the COR.

10.2 Post Award Conference. The Contractor shall schedule and coordinate a post award conference within seven (7) days after Contract award. The purpose of this meeting is to ensure the contractor and the government understands their roles and responsibilities, validate understanding of the requirement, including external influences, and establish a schedule for updates and communications. The meeting will provide an introduction between the contractor personnel and Government personnel who will be involved with this Contract. The meeting will provide the opportunity to discuss technical, management, and security issues, and travel authorization and reporting procedures. At a minimum, the attendees shall include vital contractor personnel, relevant Government personnel, and the Contracting Officer’s

Representative (COR).

11. Transition Support. The incumbent contractor may be required to provide transitional support. This support shall include a transfer of functional roles and responsibilities and personal side-by-side assistance necessary to ensure no disruption to ASB mission support. During the transition period, the incumbent shall maintain staffing levels as needed to impart knowledge and understanding of task requirements to the new contractor. All contractor developed databases, analyses, studies, applications and information completed or in progress under this contract shall be solely and fully owned by the

Government. The contractor shall turnover such documents and information to the Government, if not already delivered, and will provide whatever assistance is needed to protect the Government’s rights to the intellectual property.

11.1 Transition-In. The Contractor shall ensure that there will be minimum service disruption to vital

Government business and no service degradation during and after transition. Prior to the end of the existing Contract period, the Contractor, in coordination with the Government and the incumbent contractor, shall provide phase-in support for up to thirty (30) days. All transition activities shall be completed 30 calendar days after the start date of the order. The Contractor shall deliver a draft

Transition-In Plan at the Project Kick-Off Meeting. The draft Transition-in Plan is subject to changes pending Government comments and recommendations after the kick-off meeting. The final Transition-In

Plan shall be approved by the COR.

The phase-in activities shall include such functions as:

* Transfer of knowledge, experience, and lessons learned to the new Contractor.

* Assist in startup to ensure no service disruption to MCNOSC and a smooth transition.

* Transfer appropriate property, documentation, or personnel, as agreed to between the parties (including but not limited to, devices, equipment, databases and systems related to this PWS).

* Attend program reviews and participate in working groups, briefings.

The Transition-In Plan shall, at minimum, address the above phase-in activities. The plan shall also include a training program for contractor personnel and a date for accepting responsibilities for each division of work described in the Transition-In Plan. Additionally, proposed staff levels during the transition in period shall be included within the Transition-In Plan.

11.2 Transition-Out

The Transition-Out Plan shall facilitate the accomplishment of a seamless transition from this Contractor to any subsequent incoming contractor and Government personnel at the expiration of this Contract. The

Contractor shall provide a Transition-Out Plan NLT 90 calendar…