Draft PWS - HQMC IT Functional Services and Support.pdf

Performance Work Statement (PWS) for

Headquarters Marine Corps Information Technology Functional Services and Support (HQMC IT FSS)

1.0 BACKGROUND:

The Administration and Resource Management Division (ARI) within Headquarters Marine Corps (HQMC) supports the Commandant of the Marine Corps, Marine Corps activities within the National Capital Region, and Marine Corps Commands worldwide by providing the following to help our customer’s better support the warfighter through: Responsive Support Services; Sound Policies; Timely Guidance; and Expert Program Management.

HQMC, ARI provides customers with IT solutions to improve processes and efficiency. Develop database applications, private and public websites while assuring compliance with DoD and Marine Corps Standards for structure, server placement, and content. Assist customers with major modifications, software conversions, system administration, maintenance support, and web enabling existing applications.

2.0 SCOPE:

The scope of this requirement shall be to support ARI’s day-to-day applications systems administration and maintenance, applications development, and applications Service Desk support. These services support workflow and related business logic required by HQMC to ensure access and functionality for end users at Marine Corps Bases and Stations world-wide.

This support shall be compliant with the underlying United States Marine Corps (USMC) information enterprise strategy and all other directives and orders. This support shall be scalable to support future requirements. The system infrastructure (software licenses, initial software configuration, hardware, administration, and basic IT infrastructure services) for the environment shall be provided by the Government.

The current maintained databases/applications are as follows:

SharePoint Databases - 162 Custom SharePoint Solutions - 29 SharePoint Sites - 12,567 (4 Terabytes of active data)

Any subsequent mention of DON TRACKER or SharePoint refers to both current and future states of the applications.

3.0 REQUIREMENTS:

Performance Objectives: The Contractor shall provide support and services in accomplishing the following objectives:

Develop complex applications using SharePoint and government approved custom solutions development tools.

Maintain and Support Microsoft SharePoint Products, Applications & Technologies, to include other implementation tools and add-on software.

Provide system administration and infrastructure support for a large SharePoint farm.

Maintain existing and create new MS SharePoint Sites for on-premise and government cloud portals.

Maintain Microsoft SharePoint 2013 Portal and any future versions (to include SharePoint Online support).

Engineering and administration of SQL centralized database environments.

Create and maintain SQL databases as needed.

Consolidated/Centralized Service Desk support (Tier I – III) for all HQMC Applications.

Maintenance and troubleshooting of HQMC Web/Portal Sites.

Provide advanced, application specific, training for Marine Corps standard systems, and custom-built applications.

Provide training manuals and deliver SharePoint User and Site Collection administrator training.

Maintain the Marine Corps data within the Department of the Navy TRACKER system (SIPR/NIPR - DON TRACKER); to include future states of the Marine Corps Tasker Systems.

Provide application and data migration support from eHQMC SharePoint to the Marine Corps Hybrid Cloud Services (HCS) Data Center.

3.1 TASK 1 - Transition-In Period:

3.1.1 Transition Support. The incumbent contractor may be required to provide transitional support. This support will include a transfer of functional roles and responsibilities and personal side-by-side assistance necessary to ensure no disruption to ARID mission support. During the transition period, the incumbent will 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 will be solely and fully owned by the Government. The Contractor will turnover such documents and information to the Government, if not already delivered, and will provide whatever assistance as needed to protect the Government’s rights to the intellectual property.

3.1.1.1 Transition-In. The Contractor will 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, will provide phase-in support for up to thirty (30) days. All transition activities must be completed 30 calendar days after the start date of the order. The Contractor will 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 must be approved by the COR.

The phase-in activities shall include such functions as:

o Transfer of knowledge, experience, and lessons learned to the new Contractor;

o Assist in startup to ensure no service disruption to HQMC ARI and a smooth transition;

o Transfer appropriate property, documentation, or personnel, as agreed to between the parties

(including but not limited to, code, devices, equipment, databases and systems, and IP, related to this PWS); and o 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.

CDRL A001 Transition-In Plan

3.2 TASK 2 - Management and Oversight: The Contractor shall manage and oversee all tasks and deliverables including assurance of resource alignment performance objectives and problem resolution are accomplished within the appropriate timeframes.

3.2.1 Status Reports. The Contractor shall develop and deliver Monthly Status Reports (MSRs), which must, at a minimum, include status of project schedule(s) and accomplishment(s), ticket resolutions, challenges encountered, and staffing resources during the reported month. This information should be incorporated into an Annual Report of accomplishments provided as a chronological narrative of each business solution development project completed within the specified period.

CDRL B001 Monthly Status Report CDRL B002 Annual Report

3.2.2 Quarterly Metrics Trend Analysis Report. The Contractor shall develop and deliver a Quarterly Metrics Trend Analysis Report to be due the 1st Thursday of each new quarter. This report shall include a more in-depth analysis of performance accomplishments checking for trends of work and activities such as help desk calls and trouble tickets generated, overall IT Center activities, production delays, server down time, etc., for the previous quarter.

CDRL B003 Quarterly Metrics Trend Analysis Report

3.2.3 Kick-off Meeting. The Contractor shall coordinate and execute a contract kick-off meeting within 7 days after contract award. Meeting Minutes shall be delivered to the COR and Contracting Officer within 5 days after meeting.

CDRL B004 Meeting Minutes

3.2.4 Schedule Planning. The Contractor shall maintain an accurate schedule of program events and recommended program schedules, including review and evaluation techniques, which provide for the earliest delivery schedule while at the same time satisfy all requirements. The Contractor shall notify the COR and the contracting officer in writing of any anticipated or projected work stoppages or delays that will impact schedules.

The contractor shall establish a Plan of Action and Milestone Chart (POA&M) for each development project depicting major tasks and events from start to completion of project.

CDRL B005 POA&M

3.2.5 Data Management. The Contractor shall manage all data and items required using Government-designated website. In addition, the Contractor shall maximize use of existing data and Government Off-The-Shelf products to enable re-use of technical information to be furnished to the Government. Any electronic databases or applications used to store, track, share, transmit or display information pertaining to this contract shall be web-based. Government use of any data management system shall not require installation of client software on Government computer systems (with the exception of government authorized web browsers and Microsoft Office products).

3.2.6 Configuration Management (CM). The Contractor shall provide advice and support of Government CM processes. The Contractor shall collaborate with ARI Government personnel to update system configurations in which changes will be provided to Government representatives for submission through a Configuration Control Board (CCB).

3.2.6.1 The Contractor shall also support Configuration Status Accounting (CSA). CSA is currently initiated and maintained using the existing Project Assets Library (PAL). The Contractor’s shall support this through documenting or updating configuration status on the MSRs. The Government will provide the overall configuration baseline at contract award. The Government will also provide the equipment and baseline data files on which the Contractor shall document, store and archive all configuration data.

3.2.6.2 Additionally, programming code for custom developed applications and custom SharePoint solutions is considered a configuration item and is the sole property of the Government. The Contactor shall establish and maintain a repository within the government portal environment for all programming code that is accessible by Government personnel.

CDRL B006 Programming Code

3.2.7 Cloud – SharePoint Support. The Contractor shall provide technical advice and assistance of a Government-approved cloud migration of the HQMC ARI SharePoint Portal to include all aspects of planning and coordination with internal and external organizations and companies for the testing, migration, and support of a cloud-based solution.

3.3 TASK 3 - Web Content Administration:

The Contractor shall provide web content administration support to include web content formatting from various sources to SharePoint; researching, editing, and proofing content for publishing to sites; reporting and logging of changes to sites; ensuring production of relevant information aligning sites’ audience, and marketing and organizational goals; participation in sites content creation, redesign, and optimization, targeting increase in site traffic and engagement; content review for quality and accuracy; evaluation of sites content and copy for data analysis-based improvements; creation of pages/sites, assignment of appropriate permissions, and posting of data to sites; creation of spreadsheets, documents, and/or presentations from raw data provided by ARI personnel, for posting on internal and externally accessible sites; updating information sites regarding maintenance, outages, or known issues; and maintenance of standard operating procedures (SOP) for web content administration. Frequency of various site support and maintenance will depend upon requests received from the six (6) ARI sections (multiple site per section).

3.4 TASK 4 - Technical Writing:

The Contractor shall provide technical writing support to include creation and publication of technical documentation for data systems and procedures in line with the business processes of the HQMC Applications Development section. In addition, updates to the Risk Management Framework (RMF) documentation (current system: SharePoint) for the maintenance of systems accreditation; documents include, but are not limited to Privacy Impact Assessments (PIA), security controls, systems configuration and diagrams, memorandums of agreement (MOA), and other related RMF required documentation shall all be included in this effort. The Contractor shall also support the Application Development team in the creation of detailed documentation of all application solutions; to include creating new and maintaining existing user technical guides.

CDRL D001 RMF Documentation CDRL D002 User Technical Guides

3.5 TASK 5 – Cloud Application Development Support:

The Contractor shall support all applications of the SharePoint 2013 portal and any future versions. Equipment and software resources for the SharePoint environment will be provided by the Marine Corps. The Contractor shall support design, development, and implementation of SharePoint and custom solution applications; to include dashboards, which collectively and systematically capture, store, and share information to provide situational awareness (SA) and decision support to HQMC leadership. The Contractor shall analyze system requirements and design specifications in support of HQMC Staff Agencies; perform on-site design, build, testing, implementation, and maintenance of new web applications; and make updates/modifications, when needed, to existing web and database applications for HQMC organizations.

The Contractor shall support existing applications encompassing custom client-side code, SharePoint Web Parts, Complex workflows, InfoPath Forms, CorasWorks rollups/grid displays, etc.

Below are some of the tools the Contractor will use to support HQMC applications:

CorasWorks SharePoint Designer MS SQL 2012 or higher IIS .NET (current versions) Approved Backup Solution for SharePoint MS InfoPath Adobe Suite DocAve Visual Studio Microsoft Power Platform (Power Automate, Power BI, etc.)

3.5.1 The Contractor shall test (all test scripts/plans require Government approval prior to implementation), debug, and refine SharePoint and application business solutions to produce the product required by the written specifications or requirements document. They shall develop forms, views and reports as required.

3.5.3 The Contractor shall provide recommendations with regards to site collections within the current SharePoint environment in preparation for migration to future versions of SharePoint or cloud environments.

CDRL E001 SharePoint Migration Recommendations

3.5.4 The Contractor shall use government approved tools for O365 developers (Microsoft cloud-based technologies), and other government approved cloud platforms to develop business solution applications for government cloud environments.

3.6 TASK 6 – Systems Administration and Maintenance Support:

The Contractor shall support all databases, including maintenance of the SharePoint 2013 environment. Equipment and software resources for the SharePoint 2013 environment will be provided by the Marine Corps. The Contractor shall support the architecture, configuration, testing, and compliance of the portal. The overall compliance of the portal includes all activities related to Cyber Security requirements under the Risk Management Framework in order to maintain an Authority to Operate (ATO).

3.6.1 Database Administration (MS SQL Server). The Contractor shall perform database normalization/optimization, data modeling, database administration, database design, SQL programming and other related duties as assigned. ARI is currently supporting SQL Server 2012 or higher. The Contractor shall ensure the integrity and efficiency of databases via change control processes and database configuration. The Contractor shall manage SQL Server databases, perform system and application troubleshooting, plan, test, and execute database backup and recovery strategies.

CDRL F001 SQL Database Backup and Recovery Plan

This support includes:

o Maintenance and optimization of the SharePoint 2013 production and COOP environments o Manage and maintain vulnerability remediation for servers in line with cybersecurity requirements and reporting o Schedule and monitor full and incremental data backups of SharePoint and SQL servers o Restore loss or deleted data from backups upon request o Database administration of the centralized SQL database environment o Maintain a connection to the COOP environment to provide failover capability o Test and migrate sites and data from the SharePoint 2013 portal to future SharePoint versions or cloud environment o Repair or re-develop sites that have broken functionality upon upgrade o Maintain and update technical documentation (i.e. configuration changes to databases and source code etc.)

3.6.1.1 In addition to setting up user accounts and documenting problems for management reports, the Contractor shall audit databases, address and resolve activities that cause user problems, and assist the development team with detecting application bugs.

CDRL F002 Updated database and server configuration documents

3.6.1.2 The Contractor shall manage database schemas, perform database logical backups, and manually or automatically load data into the database as required; install and manage maintenance and security upgrades;

and shall communicate and deliver timely work products associated with the programming activities of the above-identified systems.

CDRL F003 Work Product Documentation (i.e. database logical backups, maintenance and security upgrades)

3.6.2 Cloud Architect. The Contractor shall perform overall systems administration, maintenance and support for current and future versions of Microsoft SharePoint 2013 or higher and Microsoft Office SharePoint Server, and associated tools.

This support includes:

o Manage and maintain vulnerability remediation for servers in line with cybersecurity requirements and reporting o Configure, Troubleshoot, and Maintain Search Functionality o Coordinate and Collaborate with Network Infrastructure Team o Design and implement medium to large SharePoint intranet/extranet farm topologies using Microsoft

Best Practices o Assist in solving technical and performance problems within the portal infrastructure o Plan and implement Service Packs and Cumulative Updates of SharePoint Foundation and SharePoint server o Create and maintain documentation for SharePoint infrastructure, deployment, and service specifications o Collaborate with Infrastructure and DBA groups on backup/recovery operations and disaster recovery testing related to SharePoint implementation o Manage service applications, creating web applications, configuring Alternate Access Mapping

(AAM) and managing farm features and solutions o Create a SharePoint Configuration document that takes into account hardware, OS and software configuration, service accounts, IP addresses, host names, and the service application topology

3.6.3 Cloud – Migration Execution Support. The Contractor shall execute migration of up to 162 SharePoint sites (see para 2.0) and content from the existing on premise portal farm to government approved cloud services.

3.7 TASK 7 - DON TRACKER Support:

The Contractor shall provide task management support of DON TRACKER and provide DON TRACKER Training.

3.7.1 DON TRACKER Application Support. The Contractor shall provide Tier 2 technical task management support services (in line with 3.8 TASK 8) to USMC-wide customers in support of DON TRACKER system.

This includes addressing customer requests for application functionality and configuration issues. Tier 2 support will include analysis and determination of complex requests escalation to DON TRACKER Tier 3.

CDRL G001 DON TRACKER Support Plan

3.7.2 DON TRACKER Training. The Contractor shall provide DON TRACKER User Training via formal classroom instruction, web-based training, and VIP desk-side training. This includes developing training materials, updating when necessary; coordinating classroom or distance learning resources; delivery of instruction; and providing weekly attendance reports. Training will be offered on a rotational monthly basis and by special request. The classes are primarily for Marines, USMC civilians, and Contractors needing the training to perform services for Marine Corps agencies. Navy personnel can attend DON TRACKER classes on a space available basis. Classes shall be offered with more frequency when system upgrades or migrations occur.

CDRL G003 Updated Training Materials

3.8 TASK 8 - Applications Service Desk Support and Management:

The Contractor shall provide oversight of the Service Desk, management of manning and coverage, tracking and submission of reports and metrics, and trend analysis to support innovations or recommended changes and updates to policies or training. The Contractor shall utilize Remedy systems, and custom SharePoint Requests for Services (RFS) application, in support of processes to capture, record, and resolve user reported difficulties for all applications supported by HQMC ARI.

3.8.1 The Contractor shall provide Tier 1 services and support such as: answering phones and entering initial ticket information; helping to resolve simple issues; providing password resets and account unlocks as needed;

basic troubleshooting and problem resolution for supported applications; ticket escalation; and other first responder type assistance. Tier 2 level support is provided by specific technical support Contractors outside the Service Desk, depending on the request or problem (i.e., the MS SQL Database Administrator (DBA), Portal Farm Administrator, or Developers shall provide Tier 2/Tier 3 support to the Service Desk for SQL related area of responsibility questions/issues when needed). The Government estimates an average of 9,000 service desk tickets per fiscal year.

CDRL H001 Help Desk Support Plan CDRL H002 Weekly Ticket Update

CDRL H003 Knowledge Articles CDRL H004 Standard Operating Procedures

3.8.2 Service Desk Hours of Operation. The Contractor shall maintain Service Desk coverage Monday through Friday, with the exception of Federal Government holidays, between the hours of 6:00 am through 8:00 pm (local time).

3.9 TASK 9 - Transition-Out Plan

3.9.1 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 days prior to expiration of this Contract. The Contractor shall identify how it will coordinate with any subsequent incoming contractor and/or Government personnel to transfer knowledge regarding the following:

o Project management processes;

o Points of contact;

o Location of technical and project management documentation;

o Status of ongoing technical initiatives;

o Appropriate contractor–to-contractor coordination to ensure a seamless transition;

o Transition of Key Personnel;

o Schedules and milestones; and o Actions required of the Government.

The Contractor shall also establish and maintain effective communication with the incoming contractor/Government personnel for the period of the transition via weekly status meetings.

The contractor shall also complete or perfect transfer of all tangible and intangible (intellectual) property and licenses.

The Contractor shall implement its Transition-Out Plan NLT 90 calendar days prior to expiration of this contract.

CDRL J001 Transition-Out Plan

4.0 PERFORMANCE REQUIREMENTS SUMMARY (PRS):

Surveillance of Contractor performance is the method used by the Government to determine whether the Contractor is effectively and efficiently complying with all terms and conditions of the contract. The functional expertise of the Contracting Officer’s Representative (COR) plays a critical role in adequately evaluating contractor performance.

The below listed methods of surveillance shall be used in the administration of the Quality Assurance Surveillance Plan (QASP) and the standards are delineated by the PWS in the Performance Requirements Summary (PRS) set forth below:

PERFORMANCE

OBJECTIVE / PWS

PARAGRAPH

PERFORMANCE STANDARDS ACCEPTABLE

QUALITY LEVEL

METHOD OF

SURVEILLANCE

3.1 TASK 1 –Transition-

In Plan

A draft of Transition-in Plan must be deliver during Project Kick-Off Meeting

98%

COR and government leads inspection

3.2 TASK 2 –

Management and Oversight

- Timely submission of Monthly Status Reports within 10 business days after reporting period.

- Timely submission of Quarterly Metrics Trend Analysis Reports within 5 business days after reporting period.

95%

COR inspection

3.3 TASK 3 – Web

Content Administration

- Timely, complete and accurate documentation/record of work accomplished for each assigned project

Customer Feedback/Survey

3.4 TASK 4 – Technical

Writing

- Technical documentation produced within 25 days of project completions

95% COR and government

3.5 TASK 5 – Cloud

Application Development

- Development of business solutions to fully meet agency requests for support.

Customer Feedback/Survey

3.6 TASK 6 - Systems

Administration and Maintenance Support

- Configuration, maintenance and support activities to ensure continued operational status of systems and related databases

95% COR and government

3.7 TASK 7 – DON

TRACKER Support;

3.7.1 Application Support

- Maintenance and support activities to ensure continued operational status of system and related databases

95% COR and government leads inspection

3.7 TASK 7 – DON

TRACKER Support;

3.7.2 Training

- Conduct monthly Task Management training for USMC customers

95% COR inspection

3.8 TASK 8 – Help Desk

Support

- Consistent Tier One/Tier Two customer support provided for customer inquiries and requests

- Effective communication and coordination with external Help Desks provided for customer support

- Complete assigned trouble tickets and report status to customer within >48 hours;

- Document all service request maintaining accuracy;

97%

Customer survey/feedback

- Maintain a first call resolution rate of 94% utilizing the custom SharePoint request for services application.

3.9 TASK 9 - Transition-

Out Plan

Draft a Transition-Out Plan no 90 day prior to expiration of contract.

97% COR and government

5.0 SUBSTITUTION OF PERSONNEL:

The Contractor shall identify resources with its offer to fulfill the PWS requirements. No substitutions shall be made except in accordance with this requirement.

Guidance on Substitutions. All substitution requests must be submitted, in writing, at least fifteen (15) days [thirty

(30) days if security clearance is to be obtained] in advance of the proposed substitutions to the Contracting Officer and the COR.

Substitution Requirements. All requests for substitutions must provide a detailed explanation of the circumstances necessitating the proposed substitution to the Contracting Officer and the COR.

NOTE: All proposed substitutes must have qualifications that are equal to or higher than the qualifications required of the resource to be replaced.

6.0 PLACE OF PERFORMANCE:

Services shall be provided off-site, on-site, or a combination thereof, depending on program requirements. The anticipated places of performance shall be at the Pentagon and sites identified by the COR during performance of this effort.

In addition, contractor employees may be required to work at home (adhoc), or at the contractor's facility in cases of unforeseen conditions (e.g., government office closings, severe weather, pandemic conditions, etc.) which is to be worked out between the contractor employee and their employer.

7.0 HOURS OF OPERATION:

Contractor support and Service Desk coverage is required Monday through Friday, with the exception of Federal Government holidays. Contractor support are authorized to work a flexible schedule between the hours of 6:30 am through 8:00 pm (local time) to ensure that these hours are covered.

The Contractor shall conduct business as necessary to meet the requirements of this PWS. The contractor may be required to adjust its work schedules to accommodate work requirements.

Hours of Operation: The Contractor will not be required to provide services during the below listed Federal Holidays:

The Government observes and the contractor may not have access to federal work space or the COR on the following legal holidays and any other day determined to be a holiday by the President of the United States and Public Law:

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day

Columbus Day Inauguration Day (only valid for DC, VA and MD)

8.0 GOVERNMENT FURNISHED INCIDENTALS:

The Government shall provide contractor personnel assigned to work on-site with all incidentals such as work space, desk, chairs, telephones, computers and fax machines.

9.0 SUMMARIZATION OF DATA RIGHTS:

Data, Software and Intellectual Property Rights. In accordance with the DFARS data rights clauses associated with this effort, without limitation, all reports, materials (including, but not limited to, all training and training-related materials including, but not limited to, all SOPs, lessons learned, analyses/evaluations and analyses/evaluation criteria, on-line course materials, computer software/applications and hardware, source code, interfaces, tools, works, and other related items) data, information, and all electronic/digital files and other items described herein, and any other items, (hereinafter referred to individually or collectively as the Work or Works) that are first created, generated, or produced and required to be delivered under, or as a result of, this PWS shall be provided to the U.S.

Government/Marine Corps with the level of intellectual property/data rights provided by such DFARS data rights clauses.

Such data rights and related clauses include, but may not be limited to: DFARS Clauses 252.227-7012 – Patent License and Release Contract; 252.227-7013 Rights in Technical Data--Noncommercial Items; 252.227-7014 Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation; 252.227-7015 Technical Data–Commercial Items, 252.227-7017 - Identification and Assertion of Use, Release, or Disclosure Restrictions; 252.227-7019 Validation of Asserted Restrictions--Computer Software; 252.227-7020 - Rights in Special Works; 252.227-7025 - Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends; 252.227-7027 Deferred Ordering of Technical Data or Computer Software; and 252.227- 7028 - Technical Data or Computer Software Previously Delivered to the Government and 252.227-7037 Validation of Restrictive Markings on Technical Data.

Using the format described by DFARS 252.227-7017, the Contractor will provide the COR with a data rights assertion listing for all deliverables including both non-commercial and commercial technical data and computer software. Furthermore, the contractor shall not use the contractor’s or a third-party’s proprietary data, information, software, items and/or other materials for any purpose without meeting the requirements of DFARS clauses 252.227-7020 and/or 252.227-7025, and without the specific, written approval by the Contracting Officer, prior to start of any work.

Moreover, except as provided in writing by the Contracting Officer, no Work, information, material and/or other item created, generated, produced and required to be delivered under, or as a result of, this PWS/effort shall be used by the Contractor or any of its employees/agents, subcontractors and/or representatives, for any purpose other than for the support and performance of this PWS. Still further, 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 data remains proprietary, confidential, sensitive, or classified.

9.1 Access to Proprietary Data or Computer Software:

a) Performance under this contract may require that the Contractor have access to technical data, computer software, or other sensitive data of another party (including an affiliated party) who asserts that such data or software is proprietary. Therefore, the Contractor must comply with DFARS 252.227-7025 when appropriate.

If access to such data or software is required and needs to be provided, the Contractor shall enter into a written agreement (NDA) with such party prior to gaining access to such data or software. The agreement shall address, at a minimum, (1) access to, and use of, the proprietary data or software exclusively for the purposes of performance of the work required by this contract, and (2) safeguards to protect such data or software from unauthorized use or disclosure for so long as the data or software remains proprietary. In addition, the agreement shall not impose any limitation upon the Government or its employees with respect to such data or software. A copy of the executed agreement shall be provided to the Contracting Officer prior to the start of any work under this effort. The Government may unilaterally modify the contract to list those third parties with which the Contractor has agreement(s).

b) The Contractor agrees to: (1) indoctrinate its personnel who will have access to the data as to the restrictions under which access is granted; (2) not disclose the data to another party or other Contractor personnel except as authorized by the above-described NDA and the Contracting Officer; (3) not engage in any other action, venture, or employment wherein this information will be used, other than under this contract, in any manner inconsistent with the spirit and intent of this requirement; (4) not disclose the data to any other party, including, but not limited to, joint venture, affiliate, successor, or assign of the Contractor; and (5) reproduce any restrictive stamp, marking, or legend on each use of the data whether in whole or in part.

c) The restrictions on use and disclosure of the data and software described above also apply to such information received from the Government through any means to which the Contractor has access in the performance of this contract that contains proprietary or other restrictive markings.

d) The Contractor agrees that it will promptly notify the Contracting Officer of any attempt by an individual, company, or Government representative not directly involved in the effort to be performed under this contract to gain access to such proprietary information. Such notification shall include the name and organization of the individual, company, or Government representative seeking access to such information.

e) The Contractor shall include this requirement in subcontracts of any tier which involve access to information covered by paragraph (a), substituting "subcontractor" for "Contractor" where appropriate.

f) Compliance with this requirement is a material requirement of this contract.

10.0 SECURITY REQUIREMENTS:

All tasks will be conducted in full compliance with DoD security regulations. The government will provide assistance to the personnel supporting this requirement in obtaining workplace access during the period of support.

All access documentation will be returned to the government at the completion of the support services or upon termination or resignation of employment. Compliance with all USMC communications regulations pertaining to access to e-mail and Internet activities is mandatory. Failure to comply with security requirements is grounds for termination.

The Contractor(s) shall be required to wear a contractor identification badge at all times while on government property. Badges must be clearly visible at all times while on Government property. The Contractor and its representatives will not release any information concerning this effort to any third party without first obtaining written authorization from the government Contracting Officer.

The Contractor(s) shall be required to obtain Government Common Assess Cards (CACs) to perform this effort.

The Contractor(s) are also required to have a SECRET clearance to access Government systems in support of

HQMC (ARI).

Access to US military sites is a privilege that may be granted, denied, or withdrawn by the Marine Corps. Denial or withdrawal may occur as a result of any type of misconduct or incident determined contrary to the best interest of the Marine Corps mission, protection of property, welfare of personnel and for any other infraction determined justifiable for denying access.

10.1 The Contractor shall comply with the following:

a. No employee or representative of the contractor will be admitted on a Marine Corps site unless they furnish satisfactory proof of United States citizenship or, if an alien, that their residence and employment within the United States is legal.

b. All Contractor employees must possess a valid picture identification card issued by a State or Federal agency.

c. Contractor employees shall conduct themselves in a proper, efficient, courteous and business-like manner.

d. Contractor employees entering Marine Corps sites shall comply with all security requirements in effect during the contract periods and shall be subject to such checks as may be deemed necessary. The Contractor should contact each installation prior to beginning work on-site to ensure the Contractor understands and can comply with individual installation security requirements

10.2 Security Clearances. Upon reporting to work on this contract, all contractor personnel (including administrative and subcontractor personnel) shall possess, at a minimum, a favorable adjudication for SECRET eligibility.

10.3 Security Certifications. All Contractor personnel who will be on-site or require elevated system permissions shall have at the appropriate security certification (currently at least Security+) to meet IAM Level I or IAT Level II requirements.

10.4 Physical Security. The Contractor is responsible for safeguarding all Government property and information provided in performance of this task order. At the close of each work period, the Contractor is responsible for ensuring Government facilities, equipment, and materials are secured. Contractor employees will be subject to all ARI security procedures and any other applicable installation access and security regulations.

10.5 Contract Security Classification Specification. A DD254 - Contract Security Classification Specification is required for this effort. The Contractor is responsible for implementing the provisions of the DoDM 5105.21, and it’s Navy Supplement, in support of this effort. Classified work may be required to be performed under this effort.

The contractor shall have at time of award a SECRET facility security clearance (FCL). Due to the nature and scope of work performed, contractor personnel will require 24-hour access to all designated ARI facilities.

11.0 NON-DISCLOSURE AGREEMENTS:

All contractor personnel will be required to sign non-disclosure agreements in order to protect the integrity of all operational information, processes or solutions pertaining to the ARI and all USMC, proprietary or sensitive information, materials, items provided, used or accessed during this effort for the United States Marine Corps regardless of the information’s underlying classification level.

12.0 PRIVACY ACT:

Work on this project requires that Contractor personnel have access to Privacy Information. In addition, personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a and applicable agency rules and regulations.

Contractor personnel will be expected to sign a Non-Disclosure Form, which will be provided to the Contracting Officer or the COR prior to commencing work. Contractor acknowledges that criminal penalties under section 1106(a) of the Social Security Act (42 USC 1306(a)), including possible imprisonment, may apply with respect to any disclosure of information in the file(s) that is inconsistent with the terms of the agreement. Contractor further acknowledges that criminal penalties under the Privacy Act (5 USC 552a(I)(3), as amended) may apply if USMC determines Contractor, or any individual employed or affiliated therewith, knowingly and willfully obtained the file(s) or distributed information under false pretenses.

13.0 SECTION 508 COMPLIANCE REQUIREMENTS:

All electronic and information technology (EIT) procured through this effort must meet the applicable accessibility standards at 36 CFR 1194. 36 CFR 1194 implements Section 508 of the Rehabilitation Act of 1973, as amended, and is viewable at http://www.section508.gov.

14.0 NMCARS 5237.102-90 Enterprise-wide Contractor Manpower Reporting Application (ECMRA).

(a) DOD contracting activities awarding or administering contracts shall incorporate the following Enterprise-wide Contractor Manpower Reporting Application (ECMRA) standard language into all contracts which include services, provided the organization that is receiving or benefiting from the contracted service is a Department of Defense organization, including reimbursable appropriated funding sources from non-DOD executive agencies where the Defense Component requiring activity is the executive agent for the function performed. The reporting requirement does not apply to situations where a Defense Component is merely a contracting agent for another executive agency.

Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:

(1) W, Lease/Rental of Equipment;

(2) X, Lease/Rental of Facilities;

(3) Y, Construction of Structures and Facilities;

(4) D, Automatic Data Processing and Telecommunications, IT and Telecom- Telecommunications Transmission (D304) and Internet (D322) ONLY;

(5) S, Utilities ONLY;

(6) V, Freight and Shipping ONLY.

(b)The standard language to be inserted is:

“The contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for LTS IT Support via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:

(1) W, Lease/Rental of Equipment;

(2) X, Lease/Rental of Facilities;

(3) Y, Construction of Structures and Facilities;

(4) D, Automatic Data Processing and Telecommunications, IT and Telecom- Telecommunications Transmission (D304) and Internet (D322) ONLY;

(5) S, Utilities ONLY;

(6) V, Freight and Shipping ONLY.

The contractor is required to completely fill in all required data fields using the following web address:

https://www.sam.gov.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://www.sam.gov.