MR21-014_TSO_RFI.pdf

Request for Information

MR21-014 06 April 2021

Subject: Technology Services Organization (TSO): Information Technology, Migration, Integration and Modernization Support Services

THIS IS A REQUEST FOR INFORMATION (RFI) ANNOUNCEMENT ONLY. This RFI is hereby issued for information and planning purposes only and does not constitute a solicitation. Responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. No funds are available to pay for the preparation of responses to this announcement and any information submitted by respondents is strictly voluntary.

The Marine Corps Installation Command, Contracting Office anticipates issuing a fair opportunity solicitation in fiscal year 2021 to satisfy the requirement for professional services in support of the United States Marine Corps’ various enterprise business systems. The current contract for these services is a cost-plus-fixed-fee type contract. The primary purpose of this RFI is to obtain industry feedback regarding the draft Performance Work Statement (PWS). Each respondent is asked to provide, at a minimum, the information outlined below:

1) Name of organization, CAGE Code, DUNS Number, Business Size Status (under NAICS 541519), telephone number, address, and email address for the primary point of contact.

2) A capabilities statement inclusive of brief descriptions of recent contracts of similar scope and magnitude that your organization has performed with regard to the tasks included in the PWS. Please include contract numbers and a reference point of contact, if possible, and indicate if the services are performed in the commercial market or for the Government/noncommercial entities.

3) Contract vehicles that would be available to the Government for the procurement of these services, such as General Service Administration (GSA) Federal Supply Schedules (FSS), GSA OASIS, etc.

NOTE: This information is for market research purposes only and does not preclude your company from responding to this notice.

4) Any concerns, suggestions, or general feedback in regard to the draft PWS. For instance, if any language is not clear in the PWS, please identify it in your response.

5) Questions that arise during your review of the draft PWS. NOTE: Questions will not be answered, but will be considered in future drafts of the PWS.

6) Recommendations on contract type (e.g., Indefinite Delivery/ Indefinite Quantity) and whether or not you believe the NAICS code to be an accurate representation of the requirement.

Responses shall be submitted electronically using Microsoft Word, Excel, or Adobe format, 11-pt. font minimum. Respondents are advised that the Government may be unable to receive other types of electronic files (e.g., *.zip) or files in excess of eight (8) megabytes. Responses are limited to fifteen (15) pages including graphics, not including the cover page.

RESPONDENTS WHO WISH TO REPLY TO THIS RFI SHOULD SEND RESPONSES VIA EMAIL

NLT 26 APRIL 2021 10:00 AM (LOCAL D.C. TIME) TO BRANDON.M.PAYNE@USMC.MIL

Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received that is marked Proprietary will be handled accordingly. Please be advised that all submissions become Government property and will not be returned. All government and contractor personal reviewing RFI responses will have signed non-disclosure agreements and understand their responsibility for proper use and protection from unauthorized disclosure of proprietary information as described 41 USC 423. The Government shall not be held liable for any damages incurred if proprietary information is not properly identified.

mailto:BRANDON.M.PAYNE@USMC.MIL

Performance Work Statement for

Information Technology, Migration, Integration and Modernization Support Services

- 2 -

1.0 Background

The Technology Services Organization (TSO) provides information technology support for software development, systems engineering, maintenance, and operations of Financial Management (FM) and Human Resource Management (HRM) Business Mission Area (BMA) systems in support of the Deputy Commandant, Programs and Resources (DC P&R), and Deputy Commandant, Manpower and Reserve Affairs (DC M&RA). DC M&RA employs integrated manpower systems across the Service enterprise that attracts, develops, retains, and supports our Marines, their families, and our civilian workforce as they pursue their professional aspirations and personal career goals. Collectively, these systems provide our commanders a picture of the human “steel” necessary to fight and win the Nation’s battles. DC P&R employs financial management and accounting systems across the Marine Corps enterprise that track the distribution of funds and processing of financial transactions. Collectively these systems are part of the FM

BMA.

TSO’s portfolio includes integrated Pay & Personnel, Financial Management (FM) and accounting systems in support of the United States Marine Corps (USMC), Department of the Navy (DON), and Department of Defense (DoD). Stakeholders under this effort include, but are not limited to: U.S. Air Force Reserve; Air National Guard; U.S. Navy; U.S. Navy Reserve; and Defense Finance and Accounting Service (DFAS).

1.1 Mission

TSO’s mission includes functional support for systems, studies, assessments, consulting, program and project management, and the integration and maintenance of the networks that supported systems will be operated. TSO provides development, design, production, and maintenance support of information technology systems; particularly pay, personnel and accounting systems, for the Marine Corps as well as DoD components, services, and agencies. It also provides administrative and Information Technology (IT) support to the Marine Corps Pay Requirements Directorate (MCPRD), Marine Corps Disbursing Operations and Systems Section (MCDOSS), Resource Fiscal Finance Branch (RFF), and Headquarters Marine Corps (HQMC) P&R, which are located in Indianapolis, Indiana, Kansas City, Missouri, and Quantico, Virginia.

1.2 Scope

The purpose of this contract is to provide professional, non-personal services for the USMC’s enterprise business systems, which cover a spectrum of technologies and platforms. Contractor support must include the following:

• Artificial Intelligence Support (includes Machine Learning, Deep Learning, and Robotics)

• Audit Support

• Cloud Migration

• Cybersecurity

• Data Analytics Support

• Data Governance

• Data Management

• Data Warehousing Support

• Database Administration and Maintenance Support

• Information Assurance Support

• Information Technology Service Management (ITSM) Support

• Maintenance and Enhancement of Legacy Applications

• Maintenance and Enhancement of Legacy Digital Board Room

• Network Engineering/Administration support

• New Application Development

• Project Management

• Providing information for manpower inquiries initiated by HQMC and external agencies

- 3 -

• Release Management

• Systems Engineering

• User Experience Design Support

• Website Design

2.0 Tasks

Specific task requirements and deliverables will be included in the Task Orders issued under this contract.

The Contractor must provide the following services and capabilities:

(1) Provide Software Development Lifecycle (SDLC) support to include data architecture, programming, system design and engineering, testing and release management for the information systems (IS) listed in Appendix A.

(2) Provide architectural, engineering, and technical support for Continuous Integration/Continuous Deployment (CI/CD) tools, Database Hosting Services, and Web Hosting Services.

(3) Provide Infrastructure and Operations support to the information systems and technologies listed in Appendix A

(4) Provide Cybersecurity support of the full lifecycle Authorization and Accreditation (A&A) of the information systems listed in Appendix A to include networks and data through analyses, documentation, review, validation and continuous monitoring. This effort should achieve and maintain cybersecurity compliance for each systems’ Authority-to-Connect (ATC) and Authority-to-Operate

(ATO).

(5) Provide pre- and post-migration Cloud Operations support for the following areas: transition to or from cloud service offerings; availability and performance monitoring; routine maintenance and patching;

backup and restore; access management; change management; incident/problem management; security management; and DevOps operations.

(6) Provide AI support (includes Machine Learning, Deep Learning, and Robotics) that may include subject matter expertise, architecture, engineering, data science, AI science, business analysis, business intelligence, project management, design, modeling, development, testing, operations, training and security.

(7) Provide support for internal control components such as: control environment; risk assessment; control activities; information and communication; and monitoring. Support for each control environment shall include one or more categories of objectives: operations, reporting, and compliance.

(8) Provide Mainframe Operations support of legacy systems to include: monitoring the execution of mainframe applications in multiple environments; performance monitoring and tuning; data recovery;

database monitoring and administration; troubleshooting system problems; updating or creating execution schedules; and managing inbound/outbound data for a multitude of systems.

(9) Develop Business Process Management (BPM) documentation and process improvement initiatives.

In scope changes to Task Orders under this Contract are anticipated and are primarily driven by law or legislation (e.g. National Defense Authorization Act (NDAA)) and regulatory, policy and procedural requirements (e.g., Joint Staff, DoD, DON, and Commandant of the Marine Corps (CMC), Warfighters, etc.). Other changes result from BPR efforts and technology advances necessary to improve business and technical efficiencies as well as the unpredictable nature of overseas contingencies.

The Contractor must support operational events and schedules such as but not limited to: software releases/implementations; routine and ad hoc maintenance windows; hardware installation; version upgrades; and patching. Schedule adjustments for ad hoc and emergent requirements are anticipated due to business continuity plans for unplanned incidents, federal holidays, furloughs, or shutdowns. The Contractor must perform all assigned tasks regardless of required schedule adjustments.

3.0 Administrative Tasks

- 4 -

All items generated by the Contractor, including, but not limited to, research, reports, materials, briefs, presentations, processed information, processed data, model and simulation documentation, visualizations, diagrams, and general or analytical reports, created, generated, or produced under this requirement 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 right to use, modify, reproduce, perform, display, release, or disclose such items, in whole or in part, in any manner, for Government purposes only, and to have or authorize others to do so for Government purposes only.

3.1 Program Management

The Contractor must meet the requirements of this Contract and its Task Orders in accordance with the Performance Requirements Summary (PRS). The Contractor shall provide a Program Management Plan within 5 days of accepting a task order that includes a summary of the Contractor’s activities to manage this requirement, all scheduled objectives and milestones, and status updates of current Task Orders.

3.2 Post-Award Conference

The Contractor shall coordinate and conduct the Post-Award Conference within seven (7) business days of contract award at the Indianapolis site or virtually, as appropriate. The meeting shall provide an introduction between the Contractor and Government personnel who will be involved with the contract.

Discussions at the meeting shall include: technical, management, and security issues; travel authorization;

and reporting procedures (e.g., initial report suspense dates for all recurring programs; quality assurance;

and contract deliverables).

3.3 Management Reviews

The Contractor shall coordinate and conduct monthly Management Reviews (MR’s). These reviews must provide a forum for the Contractor, Procuring Contacting Officer (PCO), Contracting Officer Representative (COR) and key Government staff to discuss critical management topics including:

Contractor Performance; Workload; Process Improvement; Current funding status; and other topics identified by the Contractor or Government. The Contractor shall prepare and submit an agenda no later than two (2) business days prior to the MR and provide a subsequent memorandum for the record (MFR) that summarizes the critical management topics discussed no later than five (5) business days after each MR to the COR. MR’s may be held at the BMO Building in Indianapolis or virtually, as appropriate. The Government will review the MR agenda and MFR and provide any revisions (i.e., additional topics) as needed prior to approval and distribution.

3.4 Transition Plan

The Contractor shall implement the Transition Plan and keep the Government fully informed of status throughout the transition period. Throughout the Transition-In/Transition-Out periods, it is essential that interruptions or delays to work in progress, that would impact the mission, be minimized.

1) Transition In – Transition ensures the incoming Contractor the opportunity to maximize capture of the existing pool of expertise, develop a thorough understanding of the existing system life-cycle management processes and system requirements, as well as allow for knowledge transfer with the incumbent Contractor. The Contractor shall present the Transition Plan at the post-award kick-off meeting and within five (5) business days of the kick-off meeting, provide a finalized Transition Plan that addresses the migration of assigned workload. All transition-in activities will be based on a transition period of no more than ninety (90) calendar days. The transition shall ensure minimum disruption to TSO operations. The Contractor shall minimize service degradation during and after transition. The Contractor will receive support not only from the Government, but also from the incumbent Contractor who is contractually obligated to support transition activities.

- 5 -

The government reserves the right to identify key positions and to review resumes to ensure that key positions are filled with contractors with adequate training and expertise to accomplish key task requirements.

Although specifically identified as Transition-In activities, coordinating and performing facility and Common Access Card (CAC) badge issuance at the Government work location, and monitoring physical security of assigned spaces and visitor access in the Government work location, will continue throughout the life of the contract for all employees including civilians, contractor and military.

2) Transition Out – The Contractor shall provide a draft Transition-Out plan for transitioning work from itself to a follow-on incoming Contractor. The draft Transition-Out plan shall address how the Contractor will formally coordinate with the Government and subsequent incoming Contractor management and staff in order to transition services. The Transition-Out Plan must ensure no product or service disruption or degradation during and after a transition from this contract to the subsequent contract

3.5 Quarterly Status Meeting

The Contractor shall plan and conduct Quarterly Status Meetings (QSM’s). The primary purpose of these meetings is to review contract performance status and address contract-related issues. At a minimum, the meeting will include appropriate contractor representative(s), the Contracting Officer, the Contracting Officer’s Representative (COR), and Government technical personnel, as appropriate; however, the contracting officer may choose to include other Government attendees. Meetings will be held via a phone conference call. The Contractor is responsible for setting up the phone conference facilities. Each meeting will cover the following topics, as appropriate:

• Contract/Task Order Performance Status

• Performance Issues encountered or expected (e.g., potential delays)

• Required Government actions

• Compliance with task order staffing/key personnel requirements

• Discussion on Contractor performance against PRS metrics

• CLIN-related issues or funding limitations

• New or in-process modifications

• Potential upcoming task order requests

• Clause compliance (e.g., 52.219-9 Small Business Subcontracting Plan)

• Invoice submission/payment issues

• Contractor Performance Assessment Report System (CPARS) status

• Continuous Improvement ideas for current contract and/or future contract(s)

• List of current employees supporting this contract and its Task Orders

The Contractor shall provide meeting minutes within five (5) days of each QSM to the Contracting Officer and COR.

The COR will send out a Task Order Tracker prior to the QSM and if any updates are necessary, the Contractor will provide updates to the Contracting Officer. The Task Order Tracker will include information such as Contractor name, contract number, task order number(s), award date(s), period of performances, teaming partners/subcontractors used by the prime contract along with their business size designations, task order value(s).

4.0 Place of Performance

- 6 -

Contractor support is required for the Government's facilities located in Quantico, VA and Indianapolis, IN;

however, alternate locations may be defined at the Task Order level. Contractors will not be provided on-site work space unless specifically stated in the task order. Performance of tasks under this contract will require access to the Marine Corps Enterprise Network (MCEN). Access to the MCEN will require a MCEN computer image and a Department of Defense Command Access Card (CAC). Touch labor for MCEN image issues can only be accomplished at a MCEN service center. Issuing CAC’s can only be accomplished at a DEER/RAPIDS site (see https://idco.dmdc.osd.mil/idco/).

5.0 Period of Performance

There will be a five-year ordering period for this requirement beginning on or about 15 May 2022. The Government’s core hours are 0900-1500 Eastern Time zone; however, alternate hours of support may be defined at the Task Order level.

6.0 Key Personnel

Contractor personnel will be providing services at the Service Component (3-4 Star) and Operational Force level of command. Contractor personnel need to be skilled in developing executive-level correspondence and management programs involving executive level participants. Contractor personnel need to be proficient in briefing to senior Military (e.g., O-6 level and above); Military Commanders and their staffs;

organizational leaders; and peers. Contractor personnel should expect to work with a diverse and often conflicting group of stakeholders from a cross-section of all staff divisions/efforts.

The Key Personnel assigned to this Contract are considered to be essential to the work being performed;

however, additional Key Personnel may be defined at the task order level. The Government prefers these key personnel to meet or exceed the following criteria:

• Program Manager – The Program Manager (PM) is responsible for all aspects of the Contract and its

Task Orders. The PM must ensure all schedules and reporting requirements are met and provide oversight and quality assurance on all services and deliverables. The PM has lead responsibility for all contractor personnel and must ensure all contractor personnel are adequately trained and fully qualified for their respective roles.

o Education – Bachelor’s degree in the field of Business or IT o Experience:

8 years or more leading IT support contracts for defense enterprise IT business systems;

Proficiency in business system process improvement and performance management.

• Senior Systems Engineer/Architect – The Senior Systems Engineer/Architect is responsible for analyzing, planning, designing, documenting, and managing the implementation of complex and secure IT solutions. The Senior Systems Engineer/Architect oversees the architecture and delivery of systems, applications and processes underlying customer IS infrastructure, which includes:

infrastructure planning; application support; analysis; assessment; studies; design; development;

testing; setup; technical documentation; and reporting.

o Education – Bachelor's degree in the field of IT.

o Experience:

8 years or more in engineering and designing IT systems;

5 years or more leading system engineering/architecture and design efforts;

Experience in concept exploration, requirements definition, analysis, process design, systems design, integration testing and evaluation within complex environments.

Ability to lead and support development and maintenance teams through the IT life cycle using structured processes such as Agile.

Experienced in development of architecture compliant operational and systems views.

https://idco.dmdc.osd.mil/idco/

- 7 -

6.1 Substitution of Key Personnel

• General Provision – The Contractor agrees to assign to this contract/task order those persons identified as key personnel whose resumes were submitted with its proposal and who are necessary to fulfill the requirements of this contract/task order. No substitutions of key personnel shall be made except in accordance with this clause.

• Guidance on Substitutions – During the first ninety (90) days of the contract/task order performance period, no key personnel substitutions by the Contractor will be made unless substitutions are necessitated by an individual's sudden illness, death, termination of employment or non-acceptance of an offer of employment. In any of these events, the Contractor shall promptly notify the Contracting Officer and provide the information required by Section below. After the initial ninety (90) day period, all proposed substitutions must be submitted to the Contracting Officer and provide information required under this clause, in writing, at least ten (10) days in advance of the proposed substitutions, when possible.

• Request for Substitution – All requests for substitutions must provide a detailed explanation of the circumstances necessitating the proposed substitution, a resume for the proposed substitute, and any other information requested by the Contracting Officer. All proposed substitutes must have qualifications equal to or higher than the qualifications stated in the PWS. The Contracting Officer or his/her authorized representative will evaluate such requests and promptly notify the Contractor of his/her approval or disapproval thereof.

7.0 Personnel, Training, and Certification Requirements

The Contractor shall ensure that their personnel are eligible for and maintain required conditions of employment; security clearance eligibility, identification tokens, and base passes (if required), for its employees. The Contractor shall be responsible for maintaining training, certification, and specific position requirements for employees and its sub-contractor’s employees under this contract. The Contractor shall return all applicable base passes upon termination of employment or completion of this contract to the Pass and Identification Section and certification of receipt shall be obtained.

Contractor Personnel Appearance and Identification

The contractor’s employees shall be easily recognized as contractor employees. This may be accomplished by either (1) the contractor employee wearing distinctive clothing bearing the company’s name/LOGO and employee’s name, or (2) the contractor employee wearing an identification badge bearing the company's name and the employee's name, with the badge worn or attached to the employee's outer garment at all times. Clothing or badges shall be provided by the contractor. If the contractor is unable to obtain the employee’s badge for whatever reason, the cognizant Pass and ID Office will be notified within 24 hours.

During the task order performance period, contractors shall immediately report instances of lost or stolen badges to the issuing Pass and ID Office. The contractor shall establish and provide dress code and grooming standards for all contract employees. This shall take into account safety aspects of services being render, location of deployment, and consideration of the Marine Corps high standards.

Contractor personnel and their subcontractors must identify themselves as contractors or subcontractors during meetings, telephone conversations, in electronic messages, or correspondence related to this contract. In email correspondence with the Government, it should be clear that the employee is a contractor employee (i.e., annotate in signature block). Contractor-occupied facilities (on Department of the Navy or other Government installations) such as offices, separate rooms, or cubicles must be clearly identified with contractor supplied signs, name plates or other identification, showing that these are work areas for contractor or subcontractor personnel.

Removal of Contractor’s Employees

- 8 -

The contractor agrees to utilize only experienced, responsible and capable people in the performance of work. The contractor shall not employ persons for work on this contract if such employee is identified to the contractor by the Contracting Officer as a potential threat to the health, safety, security, general well-being, or operational mission of the command and its population. The Contacting Officer may require that the contractor remove from the Government job employees who endanger persons or property, whose continued employment under this contract is inconsistent with the interest of military security, or who is determined by the Contracting Officer or Contracting Officers Representative as being incapable of rendering the services in accordance with the contract. The removal of an employee from a military installation shall not relieve the contractor of the requirement to continue performance of any applicable Task Order.

Prohibition of Employment

The contractor shall not employ any person who is or was an employee of the U.S. Government if employing that person would create a conflict of interest or an appearance of a conflict which may violate Department of Defense 5500.7, Joint Ethics Regulations; unless such person seeks and receives approval in accordance with DOD 5500.7R, Joint Ethics Regulation.

Foreign Participation: Foreign participation in this acquisition and subsequent contract/Task Orders will be restricted due to national security considerations. Classified Military Information is a national security asset and shall be shared with foreign governments only when there is a clearly defined benefit to the DoD (DoDD 5230.11 paragraph 4.1). The contractor shall ensure subcontractor partner companies are not fully controlled by foreign entities unless approval is received by DoD.

7.1 Annual Training

DoD- and DoN-mandated information assurance training may be required under this Contract. The Contractor shall ensure all Contractor personnel complete required annual training as determined by the Government training officer. Contractor personnel assigned to perform DON IT functions shall receive the requisite information assurance, security awareness, and functional competency training as required by their designated level of access and scope of duties

7.2 Security Training and Education

The following Government-provided training represents the minimum requirements for security education for all Contractor personnel:

1) Indoctrination of personnel upon employment by the DON in the basic principles of security

2) Orientation of personnel who will have access to classified information or assignment to sensitive duties (including IT duties) at the time of assignment, regarding command security requirements

3) On-the-job training in specific security requirements for the duties assigned

4) Annual refresher briefings for personnel who have access to classified information

5) Counterintelligence briefings annually for personnel who have access to information classified Secret or above

6) Special briefings as circumstances dictate

7) Debriefing upon termination of access

7.3 Certification

- 9 -

Contractor personnel supporting specific Cybersecurity (CY) functions must have or obtain the appropriate DoD-approved CY baseline certification (available at https://public.cyber.mil/cw/cwmp/dod-approved- 8570-baseline-certifications/) prior to onboarding and being assigned tasks. No waivers will be authorized.

Contractor personnel are required to allow the applicable certification authority to release certification information to the DoD. All Information Assurance Technical (IAT) personnel shall complete training (e.g., formal, computer based training (CBT), web-based, or classroom instruction) on the operating system(s) and/or any security devices/services/tools.

8.0 Task Order Management

JIRA is a commercial-off-the-shelf (COTS) issues management tool that the Government has tailored to manage the communications of requirements and deliverables for Task Orders under this Contract. JIRA will be used to monitor Task Order progress and completion, deliverable status, and other coordination elements, as required. The flexibility of JIRA has allowed the TSO manage a large number of business and IT support functions. The TSO JIRA Tasking and Deliverable Standing Operating Procedure (SOP) can be found in Appendix B.

The TSO follows both an 18-month iterative SDLC and a monthly Agile SDLC. These SDLC schedules, timelines, and processes will impact work under this contract and will be factored into each Task Orders and subsequent JIRA ticket, as much as practicable.

9.0 Performance Requirements Summary (PRS)

The Contractor shall be evaluated on established Performance Standards (PS’s) and associated Acceptable Quality Levels (AQL’s) as follows:

Service Performance Standard AQL Method of Surveillance

Timeliness* Tasks completed and deliverables submitted by the required date as provided in the Task Order

95% completed by required date

Inspection

Accuracy

All defects in deliverables corrected prior to final acceptance. Deliverables meet the requirements established in each Task Order

Less than 10% defects in deliverables on first submission

Inspection

Responsiveness Attendance and active participation at all MR's, QSM's, and all meetings defined at the Task Order level

No less than 95% attendance COR Review

*Note: Deliverables are not counted as late when, on a case by case basis, the COR approves later deliverable submission. The COR’s approval of a late deliverable submission or failure to strictly enforce delivery requirements will not be deemed a waiver of the applicable delivery requirements for future deliverables.

The Contractor must correct and resubmit rejected deliverables within three (3) business days or by the required completion date.

10.0 Government Furnished Equipment and Information

10.1 Government Furnished Equipment (GFE)

GFE may be provided at the Task Order level, as required.

10.2 Government Furnished Information (GFI)

- 10 -

GFI may be provided at the Task Order level, as required. The Contractor must follow TSO defined processes, procedures, and practices to safeguard and control all GFI provided.

11.0 Clearance, Access, and Security Requirements

General

Contractor personnel shall be United States citizens, in accordance with DoD 5220.22-M, National Industrial Security Program, 2-207, 2-208, and 2-209. Exceptions to this requirement may be made in accordance with DoD 52220.22-M, 2-209, Guidelines for Conducting Pre-Nomination Personal Interviews.

Eligibility will not be established for persons who hold a foreign passport.

Contractor personnel shall have knowledge of and comply with all standard DoD, Marine Corps, and TSO security procedures, which include those listed under Section 10.0, Applicable Directives. The Contractor shall immediately report any violation of stated regulations to the Contractor’s FSO, the Government Security Manager, and the COR.

11.1 Common Access Card (CAC) Eligibility

All Contractor personnel shall have a minimum of a National Agency Check with Inquiries (NACI) background investigation with a favorable eligibility determination to meet Homeland Security Presidential Directive (HSPD) 12 requirements in order to receive a CAC. Those Contractor personnel who are unable to obtain a favorable or higher eligibility determination will not receive a CAC. Contractor personnel not receiving a “favorable” suitability determination will have their CAC revoked. Contractor personnel ineligible or unable to receive a CAC cannot perform on this Contract

The TSO Personnel Security Office will monitor status and verify successful acceptance SF 86s and subsequently track that all Contractor personnel have been appropriately cleared and receive a “favorable” suitability determination.

11.2 Information Technology (IT) Requirements

1) IT-I – access to critical sensitive information; employees assigned to Cybersecurity, Network, Database, System Administration, Application Administration, and Production Operations unless designated as having a need to access classified material.

2) IT-II – access to non-critical sensitive information or Secret Clearance; applies to all contractor staff not required to have IT-I, IT-III, or No Clearance.

3) IT-III – for personnel who need access to the TSO facilities in Indianapolis, but do not need access to non-critical, sensitive information.

4) Access to classified materials – contractor personnel performing under the cybersecurity tasks of this contract will need access to classified material up to the Secret level in order to view, track, and input responses to cybersecurity threats.

5) No Clearance – Consultants or Professional Services brought in to consult or advise on projects not requiring access to NIPR or sensitive but unclassified information.

Documentation Submission

For access to classified information, the Contractor Facility Security Officer (FSO) will coordinate with the DSS in submitting the SF86 and fingerprint.

11.3 Security Clearances

- 11 -

In order to have access to non-critical sensitive information within the Marine Corps, Contractor personnel are required to have either a favorably adjudicated background investigation or interim security clearance.

Pre-investigative (interim) access is generally granted in accordance with DoD 5220.22-M, 2-211 and DoDM 5200.02, when the following criteria are met:

• Standard Form 86 (SF 86): Questionnaire for National Security Positions favorable reviewed

• Acceptable proof of citizenship

• Favorable review of local personnel, base, military police, medical, and security records, as applicable

• An appropriate national security investigation opened by the Investigative Service Provider (ISP) (e.g.

OPM) when an applicant previously held a valid security clearance and has a break in service of not more than 24 months

• Favorable review of FBI Criminal History Report (Special Access Check (SAC)) (fingerprints results)

• Has a Need-to-Know

• Completed SF-312, Non-Disclosure Agreement (NDA) prior to requesting access to the information systems.

All Contractor personnel with access to classified material shall complete and sign an SF 312, “Classified Information Nondisclosure Agreement.” All access to classified material by Contractor Personnel, including oral and visual, will be under the supervision and control of cleared Government personnel. The sponsoring Government activity will provide on-site storage capability for all classified material. Off-site storage of classified material is prohibited.

12.0 Privacy Act and HIPAA

All services performed relative to the requirements identified in this PWS allow access to unclassified or sensitive information covered by the Privacy Act of 1974 and other DoD and USMC regulations. Some information provided by the Contractor during the application process may be subject to the Health Insurance Portability and Accountability Act (HIPAA).

13.0 Travel

The Contractor shall coordinate travel arrangements with the COR. Any travel under this contract must be specifically requested in writing by the Contractor and approved by the COR, prior to incurring any travel expense. The Contractor shall submit the written request to the COR at least five (5) days in advance of the travel dates, as practicable. The travel request shall include as a minimum, the following:

• Contract number

• Date, time, and place of proposed travel

• Purpose of travel and how it relates to the contract

• Contractor’s estimated cost of travel with a breakdown of the estimated costs of transportation, lodging, meals, and incidentals; and

• Name(s) of individual(s) traveling.

The COR shall review and approve/disapprove (as appropriate) all travel requests submitted giving written email notice of such approval or disapproval to the Contractor.

Travel Reimbursement

The Contractor shall adhere to FAR 31.205-46. Travel costs will be priced separately and funded by the Government on a cost reimbursable basis at the Task Order. The Contractor will not be reimbursed for travel expenses unless audited records for transportation contain evidence, such as original receipts, substantiating actual expenses incurred for travel. Local travel (50 miles radius from assigned place of performance (per Task Order)) will not be covered under this contract as a travel cost transaction.

- 12 -

The contract includes a not-to-exceed funding limitation for travel costs. When the Contractor expects total funding expended for reimbursable travel to reach 85 percent of the total funds available on the travel CLIN, the Contractor shall notify the KO and the COR and any other Government official identified by the KO. The notice shall state the estimated amount of additional funds required to continue performance for the period specified in the contract. The Contractor shall not exceed or incur costs that exceed the amount of funding stated on the reimbursable travel CLIN. The Government is not obligated to reimburse the Contractor for otherwise reimbursable travel in excess of the funded amount stated on the reimbursable travel CLIN.

The Contractor is not obligated to continue performance of any reimbursable work under this Contract or otherwise incur costs for reimbursable travel in excess of the funded amount stated on the reimbursable travel CLIN unless the KO notifies the Contractor in writing that the funded amount stated under the applicable reimbursable travel CLIN has been increased. In the event notification is made orally, such notification shall be followed up in writing within two working days.

Change orders shall not be considered an authorization to exceed the funded amount stated under the reimbursable travel CLIN unless they contain a statement expressly increasing the funded amount of that reimbursable CLIN by a sufficient amount to cover the change order.

14.0 Other Direct Costs

Other Direct Costs (ODC’s) will be priced separately on task orders as FFP, if required. The contractor will provide substantiating information to justify ODC prices as fair and reasonable at the Task Order level.

ODC’s may include specialized equipment, software, or services required by the Contractor to complete a required task. Some examples include; continuous integration and continuous deployment (CI/CD) tools;

Development, Security, Operations (DevSecOps) tools; and Mobile application development tools.

15.0 Non-Personal Services

Contractor employees performing services under this contract and its Task Orders will be controlled, directed, and supervised at all times by Contractor management personnel. Contractor management shall ensure all employees comply with the performance work standards outlined in this PWS. Contractor employees shall perform their duties independent of, and without the supervision of, any Government official or other Defense Contractor. The tasks, duties, and responsibilities set forth in this PWS shall not be interpreted or implemented in any manner that results in any Contractor employee creating or modifying federal policy, obligating the appropriated funds of the United States Government, overseeing the work of federal employees, providing direct personal services to any federal employee, or otherwise violating the prohibitions set forth in Subparts 7.5 and 37.1 of the Federal Acquisition Regulation (FAR). The Government will grant Contractor access to the facilities and will perform the inspection and acceptance of the completed work.

16.0 Enterprise-Wide Contractor Manpower Reporting Application (ECMRA)

The contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for enterprise business systems 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.

- 13 -

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

https://www.sam.gov/ https://www.sam.gov/