PWS MCRTAMS.docx

PERFORMANCE WORK STATEMENT (PWS)

TECHNICAL SUPPORT

MARINE COPRS RANGE AND TRAINING AREA MANAGEMENT SYSTEMS (MCRTAMS)

1. SCOPE OF WORK.

1.1. The Range and Training Area Management Branch, TECOM requires contractor support to provide technical services to enhance and maintain the Marine Corps Ranges and Training Area Management System (MCRTAMS).

2. BACKGROUND.

The Range and Training Area Management (RTAM) Branch at TECOM Headquarters, United States Marine Corps Base Quantico, sponsors all Range-related IT systems and databases. They provide the tools, education, access, and data necessary to support the scheduling, planning, management, development, and safe operation of Marine Corps ranges and training areas. These systems are a collection of databases and applications that integrate workflow and other information to support the Marine Corps community, and they are maintained by RTAM support personnel. RTAM is currently staffed with a mix of Marine, Civilian, and Contractor personnel. To continue maintaining the requisite systems knowledge, skill, and ability to support the RTAM mission, the requirement exists to contract for technical support within five (5) core areas: Project Management, Database Administration and Application Development, Information Assurance, and Analytical Support.

2.1. The MCRTAMS provides commanders, operating units, range managers, and cross-service users with the metrics to relate range capabilities to specific training requirements utilizing established and developing software tools and data metrics. It provides a Range Managers Tool Kit for safety, range use, range planning, and range support functions. It stores and provides Geographic Information System (GIS) data for the Marine Corps ranges and training areas. The MCRTAMS also provides the Marine Corps’ integrated and readily available range inventory and training range database. This inventory is continuously updated and shared among range users, managers, and planners at all levels of command. The MCRTAMS identifies all available training resources, specific training capacities and capabilities, and those specific training constraints initiated by encroachment. The MCRTAMS matches the Marine Corps Training and Readiness (T&R) requirements with specific ranges and USMC and DoD facility category codes, identifying the ranges and facilities capable of satisfying/supporting the T&R training standards. The MCRTAMS provides Marine Corps managers and planners at all levels of command with the essential information to develop a comprehensive training range sustainment plan to sustain, upgrade, and modernize USMC ranges. Further, the GIS environment allows training planners to research range and training area resources located at other USMC installations, which can be used to visually assist in defining activities or exercises within a given training scenario.

The focus of this Program of Work will include the following efforts:

Task 1: MCRTMAS Program Management and Technical Support Services Task 2: Application Development and Support Services Task 3: Database and System Administration Support Services Task 4: Immersive Photo and Data Services Task 5: Information Assurance Support Services Task 6: RTAM Training Systems Analytical Services (Option Task-1) Task 7: RTAM Program Analytical Services (Option Task-2) Task 8: Cloud Service Provider (CSP) (Option Task-3).

3. TASK DESCRIPTION/SPECIFICATION

3.1 Task 1. – MCRTAMS Program Management and Technical Support Services. The Contractor shall provide Program Management and program services to ensure mitigation of project risks, minimal schedule variances, and adherence to budget compliance. The following table summarizes the requirements and deliverables required by Task 1:

Table 1.

· Provide overall program management to include: assisting in project planning, risk mitigation, requirements determination, quality assurance, staff services, and customer support for Ranges IT systems.

· Act as the single point of contact for management of tasks, subtasks, and deliverables.

· Develop and maintain required system Information Assurance (IA), Authority to Operate (ATO) and Authority to Connect (ATC) compliance documentation.

· Develop and implement a means to provide remote system management, administration, and support services from an off-base facility IAW USMC best practices.

· Develop a Task Order Plan (TOP) to accomplish the subtasks outlined in this task order.

· Maintain documentation to establish MCRTAMS as a Marine Corps application in the Department of the Navy Applications Management Database (DADMS) and DITPR-DON.

· Provide staff coordination with the Functional Area Manager (FAM) and the HQMC C4 staff required to establish and obtain approval of MCRTAMS software on the HQ Marine Corps Software List and in DADMS.

· Provide the staff coordination certification and deployment actions for MCRTAMS and associated applications.

· Prepare and staff documentation to obtain the DoD Information Assurance Certification and Accreditation Process (RMF) approval and the MCEN Authority to Connect via the Marine Corps Certification and Accreditation Support Tool (MCCAST) assessment engine.

· Prepare the internal supporting documentation that will be required for the MCCAST assessment engine. This includes maintaining documents like the Continuity of Operation, Concept Of Operations, Disaster recovery, configuration management, etc.

· Provide staff coordination with HQMC C4 and MCNOSC Information Assurance (IA) staff on the DIACAP accreditation and authority to connect analysis.

· Execute new daily, weekly, monthly, and yearly IA-related security reviews, scanning with multiple approved DOD toolsets (e.g. ACAS, Nessus), inventory maintenance, warranty maintenance, data verification, backup validation, compliance and reporting.

· Prepare and deliver a draft TOP to the Government 45 days from contract award.

· Prepare and deliver required documentation per the TOP.

· Prepare and deliver reports, documents, or briefs within 10 days from receipt of task or provide appropriate POA&M.

· Attend Range meetings and conferences as requested by the Government Program manager. Provide Trip report within 10 days.

· Provide Subject Matter Expertise in support of requirements.

· Review the following deliverables to assess the timeliness, quality, and accuracy IAW the contract requirements:

· Deliverables

· Monthly Performance and Cost Reports (PCRs)

· Quarterly Status Reports (QSRs)

· Conduct meetings to discuss contract performance:

· Monthly Contracting Officer’s Rep/Program Manager (COR//PM) meetings with the Contractor PM.

3.1.1 Deliverable item:

3.2. Task 2. Application Development and Support Services. The Contractor shall provide Application Development and Support services to develop, enhance, or maintain new or existing MCRTAMS Range Management or operational capabilities. The following table summarizes the requirements and deliverables required by Task 2:

Table 2.

· Identify and Document future state requirements which support new and/or enhanced MCRTAMS, Range Management, or range operations capabilities.

· Provide application development to include but not limited to: Access Request Module, Security Manage Module, Dashboard Module, Core Module, Ground Range Sustainment Module, Range Training Systems Module, Range Clearance Module, Role Player Module, etc.

· Maintain onsite resident skills in Oracle 19c, .NET (v3.5,v4.5), SQL, ESRI services to include ArcGIS Server (v10x), DevExpress (v12x), and greater versions.

· Provide configuration management, version control and bug tracking.

· Develop and maintain internal application help files.

· Provide technical coordination with vendors of MCRTAMS dependent or integrated applications, e.g., ESRI.

· Provide technical support to, and representation of, the TECOM Range and Training Area Management Branch at conferences, meetings, and outside vendors/contractors – to include other DOD services.

· Research and provide guidance on new technologies and applicable industry standards which can be used to enhance the functionality and value of the MCRTAMS system.

· Provide maintenance and support activities including application maintenance, user support and help support.

· Provide Manual code reviews and automated code reviews with HP Fortify.

· Provide management, maintenance and integration support of system interfaces, and third-party modules within MCRTAMS while meeting federal records disposition requirements using Laserfiche.

· Prepare and deliver required documentation per the TOP.

· Prepare and deliver reports, documents, or briefs within 10 days from receipt of task or provide appropriate POA&M.

· Provide configuration documentation and controls.

· Provide subject matter expertise in support of requirements.

· Routine email and telephone coordination.

· Report notebook(s) containing supporting documentation:

· Information papers

· Draft report sections

· Briefings

· GIS products

3.2.1. Deliverable items:

3.3. Task 3: Database and System Administration Support Services. The Contractor must provide Database and Systems Administrations services to design, implement, manage, and maintain MCRTAMS databases and servers. The Contractor shall provide the following Database Administration Services. The following table summarizes the requirements and deliverables required by Task 3:

Table 3.

· Perform installation and configuration of Oracle 19c (and higher version) database software.

· Provide database administration for MCRTAMS databases residing on Oracle 19c (and higher version).

· Provide database administration to support managing a GIS environment in an Oracle configuration.

· Provide database monitoring, optimization, development, data query capability and encrypt data backups as necessary. Execute ad hoc data requests as directed by RTAM staff.

· Incorporate backup and recovery plans for critical databases to include weekend and holiday availability.

· Provide account creation and maintenance, user assistance, and knowledge transfer for TECOM Range systems personnel.

· Assist and advise in the enhancement and refresh of database technologies as required to optimize system performance, maintainability, integrity, and scalability.

· Prepare and deliver required tasks and/or documentation per the TOP. Tasks, reports, documents up-dates or briefs will be submitted within 10 days from receipt of task, or appropriate POA&M.

· Provide subject matter expertise in support of requirements.

· Provide technical system and application coordination support with the SYSCOM PM for the Marine Corps Enterprise Information Technology Services (MCEITS) Data Center and with the HQMC MCEITS program coordinator. Provide meeting minutes within 10 days.

· Attend Range meetings and conferences as requested by the Government Program Manager. Provide Trip report within 10 days.

· Prepare and submit Firewall Change Requests and associated changes to the ASP/CCR as required to support MCRTAMS. (i.e., meet the customer’s requirements within 24 to 48 hours upon receiving the requirement, depending on urgency of the task.)

· Provide monthly reports.

· Provide program reviews and briefings as required by the Government Program Manager.

· Provide maintenance and administration of 4 physical Dell servers and Tintri SAN.

· Provide maintenance and administration of 2 Cisco switches.

· Incorporate backup and recovery plans for database to include weekend and holiday availability.

· Perform installation and configuration of all server operating systems, security templates, IAVA patches, SSL.

· Perform Perform installation, configuration, and tuning of multiple versions of server and desktop products to include but not limited to ARCGIS Server and Desktop, VMWare ESXi (7.03 and above), Splunk (9.1 and above), Trellux, Nessus (10.1 and above), and Juniper vSRX firewalls.

· Develop, implement, and monitor backup routines for production and pre-production environments.

· Provide performance tuning of servers to properly utilize available memory and processing resources.

· Maintain awareness of new versions of software and hardware; provide guidance to customer regarding advantages and disadvantages of software and hardware upgrades.

· Develop and test disaster recovery plan for MCRTAMS.

· Prepare and deliver required tasks and/or documentation per the TOP. Tasks, reports, documents up-dates or briefs will be submitted 10 days from receipt of task, or appropriate POA&M provided.

· Meets the customer’s requirements within 24 to 48 hours upon receiving the requirement, depending on urgency of the task.

· Report notebook(s) containing supporting documentation.

· Routine email and telephone coordination.

· Perform installation, configuration, and IT maintenance tasks as required for systems administration and to optimize system availability.

3.3.1. Deliverable items:

3.4. Task 4: Immersive Photo and Data Services. The government will provide the Kickoff meeting. Specifically, additional support is required for 360-degree images, photos, GIS Data, and Immersive Video capture for USMC Ranges as listed below:

High Level General Needs:

· Utilize commercial grade 360 degree camera (e.g., 30 megapixels or better) and lenses to capture and produce 360-degree images.

· Utilize commercial grade digital camera (e.g., 30 megapixels or better) and lenses to capture still and panoramic photos.

· Utilize survey grade standard (e.g., Archer, Trimble, etc.) GPS to record the scene coordinates of every photo taken.

· Utilize commercial grade 360 degree camera (e.g., 30 megapixels or better) and lenses to capture and produce 360-degree immersive video clips.

· Utilize survey grade USB GPS puck receiver (SX Blue or greater) to record the GPS path embedded into the immersive video clips.

· Produce a GIS layer that contains all the photo points (one layer per Military Installation)

· GIS layer shall be captured in WGS84 DATUM with units in meters and projected to the appropriate UTM zone for the locale.

· GIS layer shall include fields for the following data (at a minimum):

· Name. Name of the photo, e.g., “Firing Point 3.”

· Text field

· Size: 50

· Location. General description of the location where the photo was taken, e.g., “R7 200m Firing Line.”

· Text field

· Size: 100

· Installation Code.

· Identifier indicating at which installation the photo was taken.

· A list of valid Installation Codes will be provided by RTAM Division

· Text field

· Size: 10

· Photo Type captured.

· “360”

· “Still”

· “Panoramic”

· Photo Date captured. i.e., Date/Time field

· Latitude of the camera at time of capture e.g., 99.999999

· Longitude of the camera at time of capture e.g., -99.999999

· MGRS coordinates of the camera at the time of capture.

· 10-digit, including full zone identifier, e.g., “99S AB 1234567890”

· ITEM_ID populated by customer.

· Text field

· Size: 38

· Processing. All raw data captured shall be delivered to the COR:

· All GIS layers and data produced.

· All photos taken, regardless of resolution or quality, to include all raw 360-degree hemispheres captured and used to create the final 360 images as well as all original TIFF files.

· All Immersive Video captured, to include all raw (mp4, .mov) video files, jpg masters, and processed H.264 MP4 videos.

· Images.

· All images need to be captured and delivered at a minimum of 300-dpi horizontal and maximum of 600 dpi vertical resolution and 24-bit color depth.

· Original images shall be in TIFF format.

· Processed images shall be in zero-compression .JPG format (as appropriate)

· 360-degree images shall be processed using the latest version of PTGui, GoPro Fusion studio, or Adobe Photoshop.

· 360-degree images shall be produced using the maximum supported resolution of the PTGui, GoPro Fusion studio, or Adobe Photoshop software and shall be based on the raw, original TIFF files.

· Still and panoramic images may be processed using an industry standard tool (e.g., Adobe Photoshop, etc.).

· Video

· All immersive videos shall be captured at minimum resolution of 4k or greater.

· Original immersive video shall be in the RAW .mov format.

· Capture camera control settings such as the shutter, gain, white balance, gamma, and settings. GPS com port will be set via the programmable software before each video recording.

· All immersive video captures will be recorded using the latest release of the studio software and electronic image stabilization.

· Immersive videos shall be processed using the latest release of a studio software (e.g., Adobe Premiere Pro and GoPro fusion studio), sequentially the final video will be processed using an industry standard tool (e.g., Adobe Premier Pro or Final Cut Pro X)

· Processed data deliverables include:

· GIS Data

· Final GIS layer in WGS84 DATUM projected to the correct UTM zone.

· One GIS layer per Marine Corps Installation.

· GIS data can be delivered in either ESRI Shape file format or ESRI Geo Database format (Compliant with ESRI 10.6.1 software and ARL Pro).

· All GIS layers must contain FGDC compliant metadata.

· Images

· Still Images

· Resized and cropped appropriately for display at a maximum of 5267x2959 and a minimum of 1024x768 resolution, uncompressed JPG.

· Contain appropriate metadata to describe the image, location, and date/time of capture. This must include the Name, Location, and Installation Code that matches the associated record in the GIS layer.

· Panoramic Images

· Two versions, both showing a minimum of 180-degrees.

· Resized and cropped appropriately for display at a maximum of 5267x2959 and a minimum 1024x768 resolution, uncompressed JPG.

· Resized and cropped appropriately for display at a maximum of 5267x2959 and a minimum 1600x1200 resolution, uncompressed JPG.

· Contain appropriate metadata to describe the image, location, and date/time of capture. This must include the Name, Location, and Installation Code that matches the associated record in the GIS layer.

· 360-degree Images

· Stitched together, final photos.

· Ensure that images are stitched together in a reasonably clean manner, as to reduce (as much as possible) the visible lines between each hemisphere in the final images as well as tripod removal.

· Ensure that the images have been cleaned up and do not contain shadows from or parts of the photographic team.

· Contain the USMC TECOM RTAM Logo and Compass tripod cap in the images (logo will be provided by the USMC TECOM RTAM Division)

· Contain appropriate metadata to describe the image, location, and date/time of capture. This must include the Name, Location, and Installation Code that matches the associated record in the GIS layer.

· Finalized 360° images will be exported / saved out from the Adobe suite in .jpg format.

· Thumbnail Images

· 360° and still images resized appropriately for display at 128x128 resolution, 72dpi (or better) Panoramic images resized appropriately for display at 128x64 resolution, 72dpi (or better).

· Contain appropriate metadata to describe the Name, Location, and Installation Code that matches the associated record in the GIS layer

· Immersive Video

· Using GoPro fusion studio visually review .mov recordings, define mark-in and mark-out points for image / video processing, and define the stich and output settings such as Projection Distance, Image quality, Vignette Compensation, and Blending.

· Convert the .mov (raw) files to the stitched jpg masters using the latest release of the Adobe Premiere Pro

· Create a H.264 MP4 encoded video from the stitched jpg master file in conjunction with GoPro Fusion studio.

· Output Resolution will be Custom 1536x768.

· Output FPS will be 15.

· Output Bitrate (Mbit) will be 1.5.

· Profile will be H.264 MP4.

· Create a GIS KML Route Layer. The KML file will be renamed to include the Installation Code, Name, and Location of the video route.

· Import and enhance the H.264 MP4 video using an industry standard tool (e.g., Adobe Premier Pro, Final Cut Pro X, etc.)

· Finalized H.264 MP4 video will contain the USMC TECOM RTAM Logo to cover the Nadir void. The Nadir void is created by the camera where the camera head is mounted and comes across in post produced footage as a black hole.

· Finalized H.264 MP4 video will be 1080P at 30FPS, a bit rate of 1.5 and contain appropriate metadata to describe the video, location, and date/time of capture. The finalized video will be renamed to include the Name, Location, and Installation Code that matches the associated GIS KML layer.

· Existing photos and immersive video will be maintained on https://rtam.tecom.usmc.mil. The inventory of photos and immersive video will be updated during this effort to ensure that the final deliverables include the most recently available subject matter. Much like any newly identified locations and subjects

· Locations for 360, photo, Immersive Video, and GIS Data Capture:

· CONUS USMC Installations:

· MCB Quantico (VA)

· MCAS Cherry Point (NC), including:

· Bogue Field

· Atlantic Field

· BT-9 and BT-11

· Oak Grove

· MCB Camp Lejeune (NC), including:

· Greater Sandy Run Area

· MCAS Beaufort/Townsend (SC)

· MCRD Parris Island (SC)

· MCAS Yuma (CMAGR and BMGR) (AZ and CA)

· MCAGCC Twenty-nine Palms (CA)

· MCAS Miramar (CA)

· MCMWTC Bridgeport (CA)

· Hawthorne Ammo Depot (NV)

· MCB Camp Pendleton (CA)

· MCLB Albany (GA)

· MCLB Barstow (CA)

· MSF Yorktown, VA

· OCONUS:

· MCB Hawaii (HI), including:

· Puuloa Range Training Facility (PRTF)

· Marine Corps Training Area Bellows (MCTAB)

· MCB Camp Blaz (Guam)

· Live Fire Training Range Complex (LFTRC)

· Skaggs Urban Training Complex

· Commonwealth of Northern Mariana Islands (CNMI)

· MCB Camp Butler (Japan), including:

· Central Training Area (CTA)

· Northern Training Area (NTA)

· Ie Shima Training Facility (ISTF)

· Camp Fuji (Japan), including:

· North Fuji Maneuver Area (NFMA)

· East Fuji Maneuver Area (EFMA)

· At each installation visited, produce 360/photos/immersive video/GIS data for the Range and Training Area facilities and features identified below:

· All MOUT facilities, to include concrete/brick/wooden structures as well as CONNEX box structures.

· Road intersections within the MOUT

· Building entrances and exits

· Windows (one per each side of building at the highest safe elevation)

· Building interiors

· Rooftops (if safely accessible)

· High-ground areas above and around MOUT facilities, if applicable

· Note –MOUT facilities with dense building locations may be best suited to on-site determination by the RTAM/Installation escort of which particular buildings are captured, as the utility of images taken from closely packed structures may be limited.

· SACON Shoot Houses

· All ranges

· Center of firing line

· Left and Right firing line limits (if safely accessible)

· Firing and throwing bays

· High-ground areas above and around ranges

· Observation towers

· From the base and at the top (if safely accessible)

· Observation Points

· Additional photo points will be needed, but many will be at the discretion of the photographer or escort who has direct familiarity with USMC training exercises and how ranges may be used.

· Knowledge

· Must have demonstrated experience in utilization of USMC ranges, training activities and knowledge of safety guidelines at each location and as presented by the local Range Safety Specialist.

· The USMC TECOM RTAM Division will initiate this process with guidance to each installation about the tasks, support, and time coordination requirements.

· The photographer will coordinate directly with the installation Range Safety Specialist at Range Control and/or MOUT Mayors in order to obtain proper escort to each location on the installation and to determine the availability and suitability of the locations for imagery capture.

· Existing Range SOP information and associated guidance will be provided by the Installations for the purposes of helping to understand / identify appropriate photo and videography locations for each range and to maintain safety awareness for each range.

· Installations (with the coordination of RTAM Division) will provide a list of Ranges that need to be captured including their priorities and recent/pending construction activities that may affect scheduling and/or range accessibility.

· GIS Administration

· The Contractor shall complete an evaluation and prepare an installation-by-installation data development plan and month-by-month execution schedule, and present this as a draft task execution plan to the Government within thirty (30) working days of award of contract. The Government will review the task execution plan and provide comments within five (5) working days. This will be conducted in conjunction with a meeting or conference call as coordinated with the Government. The Contractor shall incorporate written comments and other input received at the draft review meeting into a final task execution plan within five (5) working days of this meeting.

· The Contractor shall conduct site visits to installations as coordinated with the Government and identified during the execution plan and review process to collect the data necessary to meet the requirements of the PWS. All site visits shall be completed within 9 months of contract award.

· All deliverables under this task shall use the most current software versions unless otherwise directed by the COR.

· All deliverables including all associated intellectual property shall belong to the government. Deliverable items:

· L004 Task Order Plan and all other deliverables in Task 4.

3.5. Task 5: Information Assurance Support Services. The contractor shall provide help desk duty specific to the application, new application development support, network support, and Risk Management Framework (RMF) support. The following is a list of requirements to meet the overall program objectives:

· Support with implementing Security Technical Implementation Guide (STIG)

· Conducting routine scans using the Security Content Automation Protocol (SCAP) Compliance Checker (SCC) and Assured Compliance Assessment Solution (ACAS)

· Support with installing, maintaining, upgrading, and migrating software

· Responding to service outages

· Performing Restart and Recovery Procedures

· Periodically analyzing the system logs

· Performing network and interface monitoring, management, and troubleshooting

· Coordinating with the appropriate organizations to resolve network or related concerns

· Supporting scheduling, verifying, and storing full system backups

· Developing and maintaining system documentation for system operations, web server operations, backup and recovery, and system audit plans

· Documenting all system changes as part of the Change Management process

· On site customer support during normal business hours

· Web application helpdesk support (requirement is 5 days X 8 hours during normal business hours.)

· Review and update internal supporting documents that will be required for the MCCAST assessment engine. This includes maintaining documents like the Continuity of Operation, Concept of Operations, Disaster recovery, etc.

· Review, update, and staff documents to obtain the DoD Certification and Accreditation (Risk Management Framework) approval i.e., MCEN Authority to Operate and Authority to Connect.

3.5.1. Deliverable items:

· P005 QA Report

· Q005 Technical Report – Study/Services

3.6. Task 6: RTAM Training Systems Analytical Services (Option Task-1). The Contractor will be responsible for assisting in the following support: for the Training Support Centers, Installation Range Controls Training Transformation initiatives by participating in various joint working groups and action teams to support USMC activities associated with sustaining, upgrading, and modernizing USMC range and training areas (RTA's). The Contractor assists RTAM with reviewing and analyzing USMC training systems and equipment, planning documents, and assessing requirements, solutions, and investment strategies for RTAs, including joint operations, Opposing Forces, and space-based operations. Ancillary responsibilities include coordinating with and assisting stakeholders (e.g., MCOTEA, OSDNAVAIR, NAVSEA, USMC Installations, Joint Services, and Combatant Commands). The following is a non-limiting list of requirements to meet the overall program objectives:

· Ground Range Sustainment Program (GRSP) and Range Projects Web Sites System Administrator

· Review and evaluate GRSP and Range Projects requests

· Maintain monthly status reports on GRSP and Range Projects

· Assist in drafting and supporting the development of USMC RTA Capabilities and Requirements Documents including: Requirements Memorandum, Capabilities Development Documents with supporting annexes, Capability Requirements Change, and Letters of Clarification

· Conduct GRSP and Range Projects site visits to assist installations in developing and tracking requirements

· Conduct liaison visits with PMTRASYS to reconcile status of requirements

· Deliverable items:

3.7. Task 7: RTAM Program Analytical Services (Option Task-2). The Contractor shall provide additional analytical support, presentations, and other materials to assist RTAM with evaluating, developing, and drafting comprehensive plans to address range and training area operational constraints, e.g., air, land, and sea resources. The following is a list of requirements to meet the overall program objectives:

· Provide comment and review on all draft reports to Congress

· Provide comment and review on all Marine Corps orders, reports, studies, etc.

· Provide comment and review of all USMC Range Complex Management Plans

· Manage, track, review and comment on the Marine Corps Action Tracking System taskers for the Range Control Section, RTAM

· Deliverable items:

3.8. Task 8: Cloud Service Provider (CSP). The Contractor will provide the customer with a CSP environment, professional consulting, and services. The goal is to obtain a dynamic and scalable environment to be supplied per demand by task order. This task objective is to establish reliable, responsive, and cost-effective CSP cloud services and support that reduce total cost of ownership, improve manageability, reduce the complexity of existing data center administration, software, and operations, and provide an expanded service to the applications owners and end-users. The CSP cloud-computing environment will consist of approved services to include:

· Provide all support operations necessary to fully migrate and deploy MCRTAMS to the CSP environment.

· Conduct planning and creates technical architecture and design documents for cloud services capabilities using industry best-practices.

· Provide communications plans for all affected parties of the migration(s) to ensure end-user adoption, customer satisfaction, successful organizational process changes, and alignment with Customer policies, requirements, and goals. Capabilities shall include but are not limited to: Assistance with software license mobility where required; Migration status reporting including milestone and migration test plans and related rollback capabilities and plans.

· Provide DevOps support, including full-life-cycle product/tool selection, design, configuration, deployment, and support based on best practices, to rapidly and reliably build and deliver services, including provision and management of infrastructure, automated deployments, and performance and Application monitoring. Utilize CSP native services, third-party resources, and custom DevOps frameworks to increase the speed, availability, service levels, and quality of service for its end customers.

· Provide robust security design, configuration, and support focused on the integration points of end-user authentication (e.g., LDAP, CAC), cloud environment management authentication, and physical and logical security and certification (FedRAMP), audit and logging, etc., delivering a single comprehensive solution that can be leveraged across the organization reducing end user confusion and security management complexity as required. Provide subject matter expertise and assistance in documenting controls and obtaining the authority to operate to FISMA, NIST, and/or RMF standards as applicable.

· Public cloud region with FedRAMP accreditation

· Government community cloud regions for Federal, State, and Local stakeholders, with FedRAMP accredited and U.S. International Traffic in Arms Regulations (ITAR) compliant cloud services, and US Persons only.

· Contractor and CSP will comply with all required laws, rules, regulations, and standards, and these laws, rules, regulations, and standards shall apply equally to all parties involved in any aspect of managing, hosting, delivering, maintaining and/or supporting the cloud services.

3.9. DELIVERABLES. Monthly Status Reports (MSR). In addition to the deliverables required to support the specified tasks noted above, the Contractor shall provide monthly reports providing the status of all tasks assigned by the 5th of each month. These reports will be delivered to the COR. If the 5th falls on a weekend or an official holiday, the status report will be due on the first working day following the 5th. The Contractor will provide the government with all deliverables to the Contracting Officer’s Representative (COR). The MSR (electronic) will include task expenditures versus planned expenditures, technical progress made, schedule status, travel conducted, meetings attended, PCO-approved equipment/materials procured and excessed, issues, recommendations, and progress/results.

Table 4.

3.10 QUALITY ASSURANCE. Acceptable performance is defined as the production of timely, clear, and concise written documents in a format that lends itself to a standard Marine Corps Order (MCO). When an observation (by the COR) indicates defective performance, the COR shall require the contractor representative at the site to initial the observation. The initialing of the observation does not necessarily constitute concurrence with the observation; it is only an acknowledgment that the COR has been made aware of the defective performance.

3.10.1. Performance Evaluation Meetings. The Contracting Officer may require the Contractor Representative to meet with the Contracting Officer, Contracting Officer’s Representative (COR), or other government personnel as deemed necessary. The Contractor may request a meeting with the Contracting Officer and COR when they believe such a meeting is necessary. Written minutes of any such meetings shall be included in the contract file and signed by the Contractor Representative and the Contracting Officer. If the Contractor does not concur with any portion of the minutes. In that case, such non-concurrence shall be provided in writing to the Contracting Officer within 10 calendar days following receipt of the minutes.

3.11. ADMINISTRATION CONSIDERATIONS.

3.11.1. MCRTAMS HARDWARE/SOFTWARE MAINTENANCE AND SUSTAINMENT. The vendor will be required to maintain and sustain (lifecycle support) the MCRTAMS hardware and software. This support effort includes procuring software licenses and maintaining the Operating Systems, Oracle Database, servers, appliances, etc.

Table 5: MCRTAMS Hardware and Software maintenance and Sustainment Footprint

Switching

Cisco

Cisco

Storage

WD

Appliances

Fortinet

APC

IOS

APC

IOS

APC

IOS

SX Hosts

Dell

Dell

Physical Servers

Dell

Dell

Virtual Machines

RSA

RSA

Fortinet

Fortinet

Required software reaching end of life will be replaced with the appropriate version upgrades that are approved by the USMC in the DON Application and Database Management System (DADMS). The USMC IT Procurement approval process will be adhered to.

The Hardware and Software maintenance and sustainment costs should be included as a Firm Fixed Price cost in the offeror’s quote.

For the Optional Task-3 (Par 3.8) Cloud Service Provider, the implementation, maintenance, and sustainment costs should be included within the Firm Fixed Price cost for the task.

The contractor with coordinate with the COR and the Government project lead all major component upgrades (Server, Firewall, Switch) or system recapitalization requirements. Major component upgrades will be handled by the Government thought separate acquisition efforts. The contractor shall maintain the refreshed components via the Hardware and Software maintenance and sustainment support articulated above. The contractor shall not purchase any Hardware or Software without prior approval by the Government.

Further, if specific equipment models, software applications, or related support items are to be included as separate costs, these items must be identified in the Contractor’s proposal at the time of submission for consideration and pricing purposes.

3.12. Place of Performance. The primary place of performance shall be the Range and Training Area Management Branch, Marine Corps Base Quantico, VA. Workspace will be provided while working at the government location. The Government will provide user accounts and connectivity to the MCEN. Most of the work shall be performed between 0700 and 1630 on regular Government workdays, legal holidays excluded. The contractor may be required to provide off-installation office spaces if TECOM transitions to a new location and seating is severely limited.

3.13. Period of Performance. The period of performance of this task order shall be one (1) base year period with four (4) one (1) year option periods as follows:

3.13.1. This contract includes four (4) option periods, which the Government may unilaterally exercise. Exercising any option periods is contingent upon the Contractor having a current GSA Schedule contract when an option is exercised, including the Contractor maintaining its Small Business status. All terms and conditions applicable to the base year period shall extend to the options unless otherwise agreed upon. Onsite technical support for MCRTAMS is required: Monday through Friday, 0700 to 1630 (Except Federal Holidays).

3.14. Security Requirements. A Privacy and Security Non-Disclosure Statement must be delivered to the COR. Employees working under this contract must possess a Secret Security Clearance or an Interim Secret Clearance. Work on this project requires personnel to have access to Privacy Information. Personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a, and applicable agency rules and regulations.

3.14.1. Contractor employees shall identify themselves as Contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and formal and informal written correspondence.

3.14.2. Any information, records, or data the Contractor may have access to may be sensitive in nature. The Contractor shall not divulge any information about Government files, data processing activities or functions, user IDs/Passwords, or any other knowledge that may be gained to anyone not authorized to access such information. The Contractor shall be responsible for ensuring that other persons have the proper authorizations to access the information. The Contractor shall observe and comply with the security provisions at all Government facilities. Working on a Government Installation: Required ID badges shall be worn and displayed at all times. As assigned, the Contractor shall ensure that its personnel have completed background checks for its on-site personnel to facilitate access to work at government facilities. The Contractor shall provide each employee with an identification badge, which identifies, by photograph, the individual as an employee of the Contractor. These badges shall be worn at all times and presented for examination upon request from the Contracting Officer, COR, QA Personnel, Military Police, or any other Government Official with a need to see the badge. The Contractor and its employees shall be subject to all traffic, security, and registration regulations for personnel and vehicles. Copies of current regulations may be obtained from the Contracting Officer. All Contractor personnel attending meetings, answering Government telephones, and working on-site, where their Contractor status is unknown to third parties, must identify themselves as Contractors, including wearing ID badges, which identify them as Contractor personnel. Contractor personnel shall also ensure that when logged onto Government equipment, their profile shows them as Contractor personnel. Unless otherwise directed by the COR, all documents produced or revised by Contractors or developed through Contractor participation must be marked as “Contractor generated documents” or otherwise identified in a manner that discloses the Contractor’s participation.

4. Physical Security. The Contractor shall be responsible for ensuring all Government property provided for contractor use is properly secured at the end of each work period.

4.1. The Contractor shall immediately report to the COR or Contracting Officer any occurrences of lost or duplicate keys.

4.2. In the event keys, other than master keys, are lost or duplicated, the Contractor may be required, upon written direction of the Contracting Officer, to re-key or replace the affected lock or locks without cost to the Government. The Government may, however, at its option, replace the affected locks or perform rekeying and deduct the cost of such from the monthly payment due the Contractor.

4.3. The Contractor shall prohibit the use of keys issued by the Government by any persons other than the contractor’s employees. Opening of locked areas by contractor employees to permit entrance of persons other than contractor employees engaged in performance of contract work requirements in those areas is prohibited.

5. Documents. The Contractor shall be responsible for creating, maintaining, and disposing of the required Government documents and other federal records specifically cited in this Performance Work Statement (PWS). The disposition of all documents and federal records will be in accordance with National Archives and Records Administration NIR Job Number N1-127-08-4, dated 8/4/2008 (applies to MCRTAMS), and the Federal Records Management requirements.

6. Rights in Data and Software.

6.1. General: All research, reports, materials (including, but not limited to, all training materials, briefs, software including, but not limited to, application development items, web-related items, presentations, graphic works, photos, images, videos, GIS items, and other PWS related items) and information, and all associated intellectual property (hereinafter “Items”), in whatever form, created, generated, or produced and delivered in association with this PWS shall become the sole property of the Marine Corps and not the contractor, subcontractor, or individual author or researcher; therefore, the Marine Corps shall have the irrevocable, worldwide right to use, modify, reproduce, perform, display, release, or disclose such Items or other deliverable, in whole or in part, in any manner, and for any purpose whatsoever, and to have or authorize others to do so.

Upon delivery, the Marine Corps will have unrestricted access and use of all Deliverables. The Contractor will provide all deliverables in a version, format, and media used/usable and modifiable by the Marine Corps. Therefore, unless otherwise directed by the COR, the deliverable items identified in this PWS will be delivered in a media and electronic format compatible with resources currently being used by the Government.

6.2. Government Data. No data, materials, information, or other items created or provided expressly for this requirement shall be used by the Contractor for any purpose other than those purposes that are in support of and/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 any government confidential or classified material(s) and government-owned proprietary data, or personally identifiable information, obtained in the course of performance of services under any government task order as long as such data remains proprietary, confidential, sensitive or classified. Any information obtained in the course of duties or the performance of services under this effort, 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 the technical data, statistical data, amount of source of any income, profits, losses, or expenditures of any person, firm, partnership, corporation, or association is included in this clause. Contractor personnel (including any subcontractor personnel) shall not publish, divulge, disclose, or make known this information in any manner or to any extent not authorized by the PCO. The Contractor is required to provide confirmation that all documents and federal records are turned over to the COR at the conclusion of the period of performance.

6.3.