02 PWS ACOP-CITM-NCIRP 28 January 2021.docx

DRAFT Performance Work Statement (PWS)

PART 1 - Introduction

G-2X ACOP/CITM/NATO Sustainment and Development Support

28 January 2021

1. General: This is a non-personal services contract to provide Sustainment and Development Support of the Department of Army’s Army Counterintelligence Operations Portal (ACOP), Counterintelligence Threat Management (CITM), and NATO Counterintelligence Reporting Portal (NCIRP). The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1 Description of Services/Introduction: The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform Sustainment and Development Support of the Department of Army’s Army Counterintelligence Operations Portal (ACOP), Counterintelligence Threat Management (CITM), and NATO Counterintelligence Reporting Portal (NCIRP) as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

1.2 Background: INSCOM executes mission command of operational intelligence and security forces; conducts, synchronizes, and integrates worldwide multi-discipline and all-source intelligence and security operations; and delivers linguist support and intelligence related advanced skills training, acquisition support, logistics, communications, and other specialized capabilities in support of Army, Joint, and Coalition commands and the U.S. Intelligence Community.

1.2.1 The Army Counterintelligence Operations Portal (ACOP) is a mission enabler for the reporting, management, and analysis of Counterintelligence (CI) Investigations, Operations, Covering Agent Program and Research Development and Acquisition (CAP/RDA), Technical Surveillance Countermeasures (TSCM), Polygraph, and Administrative module. ACOP is a light, web‐based capability, allowing all echelons of CI Agents, leadership, select analysts and management to fuse, analyze, report, manage and track the full spectrum of national security investigations.

1.2.2 Prior to the development and ultimate implementation of ACOP, national security investigations were reported and managed solely by excel spreadsheets, antiquated access databases, SharePoint sites, and Microsoft Outlook. This promoted stovepipes of information, increased workload, and inability to achieve a Common Operating Picture (COP) of investigations.

1.2.3 CITM is currently an information integration and visualization capability used by CI personnel to access, link, share, geospatially display, and aggregate information from multiple isolated databases and external information sources on Secure Internet Protocol Router Network (SIPRNet). Developing CITM within ACOP will ultimately replace antiquated capability. Additionally, it will improve the Common Operating Picture (COP), for both friendly disposition and activities and threat incidents, Foreign Intelligence Service activities and locations. It will also provide a single place for ACOP users to access their CI operational and investigative information for analysis and develop a better understanding of ongoing activities in their assigned areas of responsibility. For example, analysis of information from ACOP could help to determine pattern of life, associates, co-travelers based on activities in space and time, areas of common concern in a geospatial area, times of activity, shared topics or activities of interest, and the impact of routes on activities. CITM will provide effective mission management and prioritization in CI Field Offices, CI Analysis offices, and CI Support offices allowing these CI offices to prioritize activities and identify threat mitigation measures. In addition, this will allow users to go to one platform that visualizes CI information in a CI COP. This capability would replace antiquated capabilities

1.2.4 NCIRP provides Army Counterintelligence (ACI) and NATO Agents with a single system acting as both a reporting and management tool for all documents and supporting attachments related to NATO Investigations, Operations, Covering Agent Program and Research Development and Acquisition (CAP/RDA), Technical Surveillance Countermeasures (TSCM), and Polygraph. NCIRP will allow ACI and NATO Agents, leadership, select analysts, and all levels of management to fuse, analyze, visualize, manage, and track the full spectrum of CI Activities.

1.3 Objectives: The objective of this PWS is to provide the technical, functional and performance characteristics of the work to be performed, identifies essential functions to be performed, identifies performance factors, including the location of the work, the units of work, the quantity of work units, and the standards and timeliness of the work units. It serves as the scope of work and is the basis for all work to be performed.

1.4 Scope: The Contractor shall provide the Sustainment and Development support of the Department of Army’s Army Counterintelligence Operations Portal (ACOP), Counterintelligence Threat Management (CITM), and NATO Counterintelligence Reporting Portal (NCIRP) as defined in this Performance Work Statement except for those items specified as government furnished property and services support of the defined requirements to provide a sustainable solution for the CI community to include development of the TSCM, Polygraph, Administrative Module, Search, CITM capabilities, and NCIRP capabilities. The contractor shall maintain the staffing levels to meet the requirements and schedules. The contractor shall meet all certification requirements for all personnel performing work under this PWS/Task Order. The contractor shall provide quality high performing contractors to perform development and sustainment work on ACOP, CITM, and NCIRP.

The contractor shall provide Sustainment and Development support for all subtask areas to include:

· Task Planning, Preparation, and Execution (Establish Baseline and Metrics);

· Resource Management (Personnel);

· Task/Project Budget Management and Cost Reporting (Cost Controls);

· Schedule and Task Performance Oversight;

· Risk Management;

· Quality Assurance and Controls;

· Reporting and Deliverables Management;

· Security Management;

· Strategic Planning;

· Situation Assessment and Recommendations;

· Anticipatory Support (as required).

· Bi-monthly teleconferences between the COR, ACOP/CITM/NCIRP Project Mangers

1.5 Period of Performance: The period of performance for this task order shall be for a 12 months base period to include a 30 day Transition period and four (1) one year option periods (48 Months), which may, in the Government’s sole discretion, be extended for up to an additional 12 Months in the form of 4 Option periods, which may be exercised separately, in whole or in part, by the Contracting Officer in one month or more increments (FAR 52.217‐9, Option to Extend the Term of the Contract). In addition to the priced option periods, the Government reserves the right to extend the services by up to an additional 6 months (FAR 52.217‐8, Option to Extend Services).

1.6 General Information

1.6.1 Quality Control: The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program is the means by which he assures himself that his work complies with the requirement of the contract. The contractor shall submit the Quality Control Plan within 30 days after contract award or with the contractor’s proposal if it is an evaluation factor, three copies of a comprehensive written QCP shall be submitted to the KO and COR within 5 working days when changes are made thereafter. After acceptance of the quality control plan the contractor shall receive the contracting officer’s acceptance in writing of any proposed change to his QC system.

Deliverable: A001 – Quality Control Plan

1.6.2 Quality Assurance: The government shall evaluate the contractor’s performance under this contract in accordance with the Government’s Quality Assurance Surveillance Plan. This plan is primarily focused on what the Government must do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.3 Recognized Holidays: Recognized holidays are:

Access to Government spaces will not be available without prior authorization from the COR on weekends or when the facility is closed due to local or national emergencies, administrative closings, or the following federally observed holidays:

The contractor shall provide a sufficient number of fully trained and qualified employees to meet all reporting requirements and deliverables. The contractor must at all times maintain an adequate workforce for uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed.

In addition to days designated as holidays, the Government observes the following days that contractor personnel will not be required to report to work:

· Any other day designated by Federal Statute

· Any other day designated by Executive Order

· Presidential Inauguration Day

Any other day designated by Presidential Proclamation

1.6.4 Hours of Operation:

1.6.4.1 Hours of Operations (CONUS): Unless additional hours during the workday are coordinated in advance and approved in writing by the COR, the contractor is responsible for conducting business, no more than 10 work hours per day, 40 hours per work week, between the core hours of 0600 and 1800, Monday through Friday, except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. Lunch and union time are not considered productive time and are not billable. The contractor shall incorporate the INSCOM established core hours of 0900 through 1500 hours. Extended hours and weekends to support end‐users and urgent requirements may be necessary on an as‐needed basis up to 24 hours a quarter. If the hours required in a billing period cannot be fulfilled because of a Government‐created circumstance, the contractor, COR and contracting officer will discuss an alternate billing arrangement on a case‐by‐case basis. The contractor must at all times maintain an adequate workforce for the performance of all tasks defined within this PWS when the Government facility is not closed. Upon mutual agreement of the COR and the contractor, contractor personnel may shift work hours from the Monday to Friday schedule to weekends to support Reserve Units who are drilling or for other units that may conduct training in such periods. Any such shift will be hour for hour, meaning that any hour worked on the weekend would be offset by a corresponding reduction during the Monday through Friday period. There is no change to the labor rates for work performed during weekend periods.

1.6.4.1.1. For other than firm fixed price contracts, the contractor will not be reimbursed when the government facility is closed for the above reasons. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential. The contractor is authorized to telework, work from home, and company office.

1.6.4.2 Hours of Operations (OCONUS): 650th core hours are 0900-1500 CET or 0300-0900 EST.

1.6.5 Place of Performance: The places of performance are HQ INSCOM, Ft Belvoir, VA, 902d MI Group, Fort Meade, MD, 650th MI Group, Belgium, within a fifty mile radius of the National Capital Region (NCR), and Russell Knox Building Quantico, VA, and the Contractor’s facilities.

1.6.6 Type of Contract: The government will award a Cost Plus Fixed Fee (CPFF) type contract with Cost reimbursement Contract Line Items (CLINs) for Other Direct Costs (ODCs).

1.6.7 Security Requirements: Contractor personnel performing work under this contract must have an active Top Secret with Sensitive Compartmented Information (TS/SCI) (SI, TK, G and HCS security clearance in accordance with DOD 5200.2-R at time of the proposal submission, and must maintain the level of security required for the life of the contract. Future work related to this contract may require a TS/SCI with Counterintelligence Polygraph (TS/SCI w/CI Poly) clearance. The security requirements are in accordance with the attached DD254. Personnel must perform within the security limitations of AR 381-10, USSID 18, and other security regulations.

1.6.7.1 Additional Security Requirements: The Contractor and any subcontractors performing under this contract must have an active facility clearance at the level of Top Secret at time of award. No interim facility clearances are allowed. This effort requires access to classified Government information at U.S. Government facilities. Physical, personnel, information and operational security measures are part of the security specifications as outlined in the DD Form 254 and contractor shall comply in accordance with DIAM 50-5 and other Government security regulations, manuals, and directives.

1.6.7.1.1 The Government reserves the right to direct any contractor employee to be removed for substandard performance, directly or indirectly, whenever there is probable cause to believe, that such action is warranted in the interest of national security.

1.6.7.1.2 Off- Duty Employment: Contractor personnel, consultants, and subcontractor personnel shall neither employ nor establish a compensatory arrangement with any person who is an employee of the United States Government, either civilian or military, without verifying that the employee has complied with the Joint Ethics Regulation (DoD 5500.7‐R) and any appropriate department regulation pertaining to off‐duty employment for Government personnel.

1.6.7.1.2 Security Classification Guidance or Guides: Contractors shall, to the extent practicable, advise, and assist in the development of the original Contract Security Classification Specification. It is the contractor’s responsibility to understand and apply all aspects of the classification guidance. Users of classification guides are also encouraged to notify the originator of the guide when they acquire information that suggests the need for change in the instructions contained in the guide. Classification guidance is, notwithstanding the contractor’s input, the exclusive responsibility of the GCA, and the final determination of the appropriate classification for the information rests with that activity. The Contract Security Classification Specification is a contractual specification necessary for performance on a classified contract. If a classified contract is received without a Contract Security Classification Specification, the contractor shall advise the GCA.

1.6.7.2 Physical Security: The contractor shall be responsible for safeguarding all Government equipment, information and property provided for contractor use. The contractor employees and vehicles are subject to checks before entering or exiting INSCOM. All contractor personnel shall conform to all INSCOM, Department of Army, Department of Defense, and US Government Policies and Procedures relating to workplace security and safety at all times. The contactor shall report security and safety violations immediately to the Contracting Officer Representative (COR)/Contract Manager. Lost Government-issued security badges must be reported immediately to COR/Contract Manager and HQ INSCOM Security Office. The contractor shall be responsible for securing all Government owned hardware, software, and facilities that contractor personnel will be using. At the close of each work period, Government facilities, equipment, and materials shall be secured. The following personal items are prohibited inside classified INSCOM workspaces at all times: cell phones/ Blackberries, portable USB memory drives, other portable USB devices, external hard drives, cameras, MP3 players, scanning devices, digital flash cards/disks, personal laptop computers, camera/USB watches and wireless transmitters.

1.6.7.2.1 Key Control. The Contractor shall establish and implement methods of making sure all keys/key cards issued to the Contractor by the Government are not lost or misplaced and are not used by unauthorized persons. NOTE: All references to keys include key cards. No keys issued to the Contractor by the Government shall be duplicated. The Contractor shall develop procedures covering key control that shall be included in the Quality Control Plan. Such procedures shall include turn-in of any issued keys by personnel who no longer require access to locked areas. The Contractor shall immediately report any occurrences of lost or duplicate keys/key cards to the Contracting Officer.

1.6.7.2.2. In the event keys, other than master keys, are lost or duplicated, the Contractor shall, upon direction of the Contracting Officer, re-key or replace the affected lock or locks; however, the Government, at its option, may replace the affected lock or locks or perform re-keying. When the replacement of locks or re-keying is performed by the Government, the total cost of re-keying or the replacement of the lock or locks shall be deducted from the monthly payment due the Contractor. In the event a master key is lost or duplicated, all locks and keys for that system shall be replaced by the Government and the total cost deducted from the monthly payment due the Contractor.

1.6.7.2.3. The Contractor shall prohibit the use of Government issued keys/key cards by any persons other than the Contractor’s employees. The Contractor shall prohibit the opening of locked areas by Contractor employees to permit entrance of persons other than Contractor employees engaged in the performance of assigned work in those areas, or personnel authorized entrance by the Contracting Officer.

1.6.7.3 Lock Combinations. The Contractor shall establish and implement methods of ensuring that all lock combinations are not revealed to unauthorized persons. The Contractor shall ensure that lock combinations are changed when personnel having access to the combinations no longer have a need to know such combinations. These procedures shall be included in the Contractor’s Quality Control Plan.

1.6.8 Special Qualifications: For all tasks performed under this PWS, the contractor shall provide support for the Roles and Responsibilities of Section 508 of the Rehabilitation Act and they must have and maintain all of the certifications per DOD Directive 8570.01-M -- IAT II as it applies. Additionally, personnel must satisfy the Personnel Security Standard for IT-1 per AR 25-2 paragraph 4.1-4.14.

1.6.9 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officers Representative (COR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings, the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. The contractor shall provide meeting minutes to the COR for review and approval within 1-2 business days. These meetings shall be at no additional cost to the government.

Deliverable: A002 – Post Award Conference Meeting Minutes/Periodic Progress Meetings

1.6.10 Contracting Officer Representative (COR): The (COR) will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance: maintain written and oral communications with the Contractor concerning technical aspects of the contract: issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinate availability of government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

1.6.11 Key Personnel: The contractor shall provide the identified task order key personnel aligned to the position descriptions (see Technical Exhibit 3) with personnel meeting the stated qualifications for each position identified. The contractor shall provide rationale for a candidate that has credentials that are not specifically stated but are equivalent to the stated credentials. The contractor’s rationale must be clear and convincing in order for it to be considered. The following are designated as key personnel:

· Program Manager/Project Manager

· Sr. System Administrator (designated as mission critical)

· Sr. Systems Architect (designated as mission critical)

· Sr. Software Engineer/System Integrator (designated as mission critical)

· Sr. Software Engineer/Machine Learning

· Sr. Cloud Architect

1.6.11.1 Key Personnel Qualifications:

QUALIFICATIONS FOR KEY PERSONNEL

Project Manager/Program Manager

Project Management Professional (PMP) Certification or DAU A Level III certification in Program Management. A Bachelor’s degree in Systems Engineering, Software Engineering, or Computer Science. Must have10 years demonstrated experience as a Software Project Manager and/or 10 years demonstrated experience as a DevOps Manager, and Sustainment Project Manager.

Active TOP SECRET/SCI clearance

Sr. System Administrator

DoD 85701.01-M IAT Level III certification and compliance upon hire. Bachelors in Computer Science or the combination of 10 years of computer Science education and associated experience. Professional series Certification within the product groups technology scope (e.g., VCP, CDX5-DCV). Seven years related experience in VM template design. 10 Years of experience in providing Tier II/Tier III system administration support to infrastructure. Requires privileged access to a DoD Information System, network, or enclave environment. Experience in containerization, orchestration of data services, or orchestration or modular system.

Active TOP SECRET/SCI clearance

Sr. Software Engineers/Integrator

DoD 85701.01-M IAT, Level II certification and compliance upon hire. Refer to Table C3.T5. IAT Level II function of DoD 8570.07M. Bachelor’s Degree in Systems Engineering, Software Engineering, or Computer Science. Ten (10) years demonstrated experience in design, development, fielding, and sustainment of Java based web applications. Java Web application design and development experience. Experience in development of HTML, JavaScript, CSS, SQL, Perl, graphics creation with Photoshop, Illustrator (Adobe Creative Suite), multimedia creating with Flash, action Script, (Macromedia Studio). Exposure and /or experience with some or all of the following, ASP, PHP, React, NIFI, JavaScript, HTML, CSS, Java Server pages and Java, XML, PHP Oracle, MS SQLServer, ColdFusion Server, CFML, CF Script IIS, Sencha Software tool, Python, and Windows Server 2016R@ or higher. Experience in writing and reviewing SOPs, process documents, CONOPS, and other technical documents. Experience in multi-tiered architectures; (Web, API, database tiers); Windows and Unix systems; IIS Web servers; Multi-component, multi-tiered Systems integration; Understanding of load balancers; Understanding of networking with multi-tiered architectures.

1.6.11.2 Replacement of Key Personnel. The contractor shall notify the Contracting Officer (KO) prior to making any change in key personnel. Prior to directing any of the proposed key personnel to other programs or functional areas, the contractor shall submit justification to substitute key personnel at least two weeks prior to the substitution. Justification shall be in sufficient detail, to include the replacement’s resume, to permit evaluation of the impact of the proposed change on the program and its schedule. The contractor shall not substitute or change the Key Personnel without prior written consent of the KO. The contractor shall demonstrate to the satisfaction of the KO that the qualifications of the prospective personnel are equal to or better than the qualifications set forth in 5.6.13 and Technical Exhibit 4 of this PWS.

1.6.11.3 Personnel Replacement, Backfill, and Vacancies.

1.6.11.3.1 Personnel Replacement. In the event the contractor’s performance is unsatisfactory to the Government, the COR reserves the right to request and receive a remedy from the contractor to achieve satisfactory performance.

1.6.11.3.2 Backfill. When the contractor becomes aware that an employee will be or is unavailable to work for a continuous period exceeding ten business days, the contractor shall immediately notify the COR and backfill the position no later than the eleventh business day. The contractor shall notify the COR of its plan to backfill the position prior to employee assignment.

1.6.11.3.3 Vacancies. When the contractor becomes aware that an employee will be leaving the task order, the contractor shall immediately notify the COR and backfill the position with personnel of equal or superior qualifications no later than the eleventh business day and permanently fill the position within forty‐five calendar days. The contractor shall notify the COR of its plan to fill the position prior to employee assignment.

1.6.12 Identification of Contractor Employees. All contractor personnel attending meetings, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public, they are Government officials. Contractor personnel shall also ensure all documents or reports they produce are suitably marked as contractor products or contractor participation is appropriately disclosed. Contractor personnel shall wear the appropriate security/identification badges when required. The contractor shall be responsible for ensuring employees assigned to this task order comply with the applicable laws and regulations of the host country and any political subdivisions thereof. The contractor is also responsible for ensuring such employees comply with military rules and regulations when employed in areas under the jurisdiction of the applicable U.S. Forces Commander. Contractor personnel supporting this effort shall possess all state and local licenses required for the performance of specific duties under this PWS.

1.6.13 Contractor Travel. Contractor personnel travel includes local travel in the National Capitol Region, various CONUS locations, and OCONUS locations that may include Belgium, Germany, Italy, Korea, and Hawaii.

1.6.14 Other Direct Costs. This category includes but is not limited to, travel (outlined in 1.6.13), reproduction, and shipping expenses associated with training activities and visits to contractor facilities. It could also entail the renting of suitable training venues, software licenses and hardware buys. To the extent possible, all anticipated ODCs associated with performance shall have an established price and competed. Other Direct Costs must not be the primary purpose of the task order. Any ODC amount shall be approved by the COR prior to expenditure.

1.6.15 - Intellectual Property Rights: The government shall possess full government purpose rights to all ACOP, CITM, and NCIRP software developed as a result of the contractor execution of this PWS (e.g., full, or partial software performance of the agreed upon contract/subcontract). As used herein, software includes but not limited to, source code, object code, executable code, application programs directing the operation of computing systems, and any machine readable instruction configured to enable the enhanced functionality of ACOP, CITM, and NCIRP.

The Government understands that Intellectual Property (IP), such as trademarks, copyrights, patents, and trade secrets may originate as a result of contractor execution of the PWS. The contractor shall inform the KO and COR of the creation of any items/subject matter which the contractor believes may potentially warrant copyright protection, trademark protection, patent protection or trade secret protection. If the contractor fails to inform the KO and COR, the contractor is precluded from seeking IP protection of any subject matter associated with the performance of this contract until the Government is notified of the existence of said IP protectable subject matter.

IP protectable subject matter which originates based on the contractor’s performance of this contract shall be reviewed by the Government. Upon review by the Government, the contractor and Government shall, with the Army Office of General Counsel (OGC) oversight, determine the appropriate owner of the IP or if the IP ownership should be shared between the contractor(s) and the Government.

If it is determined that the contractor is responsible for the creation of the IP protectable subject matter (i.e., contractor owns IP) or that ownership will be shared, the government reserves the right to negotiate a licensing arrangement consistent with regulatory provisions articulated in the Federal Acquisition Regulation (FAR) and the Defense Federal Acquisition Supplement (DFARS).

1.6.15.1 Patent Rights under this contract: The FAR’s provisions on patents are contained generally in FAR Subparts 27.2 and 27.3. The triggering event under the FAR for determining the party’s right’s is whether there has been a “subject invention,” which “means any invention of the contractor made in the performance work under a Government contract.” Further, “invention” means “any invention or discovery that is or may be patentable or otherwise protectable under title 35 of the U.S. Code, or any variety of plant that is or may protectable under the Plant Variety Protection Act (7 U.S.C. 2321, et seq.)”.

The contractor’s right to assert title will depend upon whether the contractor discloses a subject invention need to be one that, with any certified, is patentable.

The Government will have unlimited rights to all documents/material/code produced under this task order in accordance with the data and patent rights clauses in the contract.

The Government retains ownership to software and application tools; upon completion of this contract all information will be turned over to the U.S. Government and is U.S. Government property.

1.6.16 Organizational Conflict of Interest: Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications, or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.1.6.17 Phase In /Phase Out Period. To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the Contractor shall have personnel on board, during the first thirty (30) days of contract award. During the phase in period, the Contractor shall become familiar with performance requirements in order to commence full performance of services on the contract start date.

The following activities must occur during the phase-in period:

(i) Prior to charging direct time on any contract (excluding the Transition CLIN), the Contractor shall ensure that personnel have been approved in writing by the COR as meeting the position qualifications.

(ii) The Contractor shall submit requests for physical and network access at performance locations.

(iii) The Contractor shall ensure that all CMEs complete Information Assurance (IA) Training (required for Government systems access) and obtain a completion Certificate prior to entry on duty (EOD). The Contractor shall ensure all completion Certificates are sent to the responsible COR to confirm compliance prior to EOD. Initially, non-CAC access to AKO is required to complete IA training. However, CMEs must obtain a CAC prior to EOD.

1.6.18 In/Out Processing: The Contractor’s Facility Security Officer (FSO) must provide to the COR the following information on all CMEs for input into the INSCOM In/Out Processing Portal.

Personnel Requirements:

1.6.18.1 All CMEs directly allocated to an INSCOM HQ/MSC contract will be In/Out processed through the HQ INSCOM/MSC In/Out Processing Portal by the COR with the assistance of information provided by FSO (see table 1.6.15.1).

1.6.18.1.1 All CMEs will be eligible to receive a CAC. The COR will provide instructions and assistance on how to obtain a CAC as needed. Prior to the arrival of the personnel, the Contractor shall provide all Joint Personnel Adjudication System (JPAS) information to the COR. Prior to working at the site assigned, all Contractor personnel must schedule and complete in-processing with the INSCOM Special Security Office (SSO) at their assigned locations within 72 hours of being assigned to the contract

1.6.18.1.2 All CMEs directly allocated to a HQ INSCOM/MSC contract must be Read-On/Read-Off by a Security Specialist at an HQ INSCOM or assigned MSC facility. CMEs will NOT be Read-On/Read-Off and facility access will NOT be granted if the required information has not been entered into the HQ INSCOM/MSC In/Out Processing Portal prior to arrival and prior to departure. In the instance of Out Processing, this may affect Contractor Performance Assessment Reporting System (CPARS) reporting on your organization.

1.6.18.1.3 The COR or Government Program Manager will be responsible for inputting Contractor in/out processing information to the INSCOM Contractor portal for processing. (http://kmportal/sites/g1/default.aspx)

1.6.18.2 Transition out Plan: The Contractor shall provide a Transition–Out Plan per PRS#1 with their technical proposal for this contract. The Transition-Out Plan shall facilitate the accomplishment of a seamless transition from the ‘departing’ incumbent to an ‘incoming’ prime Contractor/Government personnel at the expiration of this contract. The transition period shall not exceed 30 days. The Contractor shall provide the Government with an outgoing transition plan. Transition Out Plan shall be submitted no later than sixty (60) calendar days prior to the end of the contract that provides for conveying all work and associated materials in their possession to the Government. The outgoing transition plan shall include the proposed date of ending the Contractor’s billable contract work. The outgoing transition plan shall also include the date of terminating network access, date of submitting all related security access badges, Common Access Cards (CAC), SIPRNet Tokens, and out‐processing procedures at the secure work facilities to include the government secure facility. All data (GitLab, code, documents, etc.), and data rights to ACOP, CITM, and NCIRP belong to the government. The contractor shall provide all data, and data rights for ACOP, CITM, and NCIRP to the government either in DI2E and/or GIT. The COR shall review and approve the outgoing transition plan prior to its execution.

The departing prime Contractor shall identify how it will work with the incoming prime Contractor and / or Government personnel to transfer knowledge regarding the following:

· Project Management process;

· Points of contact;

· Location of technical and project management documentation;

· Status of ongoing technical initiatives;

· Appropriate Contractor to Contractor coordination to ensure a seamless transition;

· Transition of key personnel;

· Identify schedules and milestones;

· Identify actions required of the Government.

Deliverable A003: – Transition Out Plan

1.6.18.2.1 The departing Contractor shall establish and maintain effective communication with the incoming prime Contractor and Government personnel for the period of the transition via weekly status meetings.

1.6.18.2.2 Throughout the transition period the incoming Contractor shall receive necessary GFI/GFE in support of handing over GFI/GFP.

1.6.18.2.3 During the first ten (10) calendar days of the transition period the incoming Contractor will be in an administrative startup period (e.g. hiring / transitioning personnel, securing clearances, TESA approvals where necessary, etc.).

1.6.18.2.4 During the transition period the outgoing prime Contractor shall remain responsible for all systems and facilities sustainment activities until relieved by the Government direction. This is normally the first thirty (30) days of the transition period.

1.6.18.2.5 During the next thirty (30) calendar days of the transition period, the departing prime Contractor will support the incoming prime Contractor who shall assume all responsibility. Upon relief of the baseline responsibilities, the outgoing prime Contractor shall focus on contract closeout activities while providing limited sustainment support to those areas where adequate knowledge transfer had not occurred.

1.6.19 Required Training and Other Requirements:

1.6.19.1 Antiterrorism (AT) Considerations: In accordance with DFARS 225.272 Antiterrorism/force protection, and DoD Instruction O-2000.16, Volume 1, DoD Antiterrorism Standards, the contractor is hereby advised that it shall comply with the policies and procedures of the U.S. Antiterrorism Officer (ATO) at each installation where work is being performed. DoD Instruction O-2000.16, Volume 1, (Change 1) is available at the INSCOM Antiterrorism Portal Page at https://kmportal.mi.army.mil /sites/g3/AT/Shared%20Documents/Forms/AT%20Resources.aspx. (On the site search for DoD Instruction O-2000.16, Volume 1, (Change 1). Information with regard to the INSCOM procedures and policies on the use of the Antiterrorism and Operations Security Review Coversheet in all contract requirements packages can be found at https://kmportal.mi.army.mil/sites/g3/AT/Shared%20Documents/Antiterrorism%20and%20Operations%20Security%20Review%20Coversheet%20in%20all%20contract%20requirements%20packages.pdf. A modification to the contract will be the instrument of notification for this action. The contractor may submit a request for an equitable adjustment for any directly incurred costs for compliance with these policies and procedures, following the modification incorporating the policy and procedures guidance. Equitable adjustment requests shall be in compliance with clauses.

1.6.19.2 Antiterrorism and Force Protection (AT/FP): AR 350-1, Army Training and Leadership Development, Section II, G-3/5/7, Antiterrorism and Force Protection (AT/FP). Specific Army standards for AT/FP training are listed in chapter 5, AR 525-13, Individual AT/FP training is mandatory for all soldiers, Department of the Army civilians (DAC) and DoD contractors and is strongly recommended for family members prior to travelling outside the 50 United States and its territories and possessions for any reason, including mobilization, temporary duty, permanent change of station, and leave. There is also an AT/FP training requirement for personnel stationed outside the United States. Individual AT/FP training is valid for one (1) year and must be documented.

1.6.19.3 AT Level I Training: All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities and controlled access areas shall complete AT Level 1 awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. The contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee to the COR/ACOR or to the contracting officer, if a COR/ACOR is not assigned, within 15 calendar days after completion of training by all employees and subcontractor personnel. AT Level 1 awareness training is available at the following website: https://jkodirect.jten.mil/Atlas2/page/login/Login.jsf

1.6.19.4 AT Awareness Training for Contractor Personnel Traveling Overseas: This requires US based contractor employees and associated sub-contractor employees to make available and to receive government provided area of responsibility (AOR) specific AT awareness training as directed by AR 525-13. Specific AOR training content is directed by the combatant commander with the unit ATO being the local point of contact.

1.6.19.5 iWATCH Training (This standard language is for contractor employees with an area of performance within an Army-controlled installation, facility, or area): The contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity Authorization to Operate (ATO). This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR/ACOR. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employee’s commencing performance. iWATCH training results shall be reported to the COR/ACOR not later than 45 calendar days after contract award.

1.6.20 Access and General Protection/Security Policy and Procedures: Contractor and all associated subcontractors’ employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office (PMO) Director of Emergency Services (DES) or Security Office. Contractor workforce must comply with all personal identity verification requirements as directed by DoD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

1.6.20.1 All material produced by the contractor which will be released to the general public will be subject to OPSEC and Security reviews from the INSCOM OPSEC Officer, Security Officer and INSCOM Public Affairs Office prior to release

1.6.20.2 For Contractors Requiring Common Access Card (CAC): Before CAC issuance, the contractor employee requires, at a minimum, a favorably adjudicated National Agency Check with Inquiries (NACI) or an equivalent or higher investigation in accordance with Army Directive 2014-05. The contractor employee will be issued a CAC only if duties involve one of the following: (1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an initial CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI.

1.6.20.3 For Contractors that Do Not require Common Access card (CAC) but Require Access to a DoD Facility or Installation: Contractor and all associated subcontractor employees shall comply with adjudication standards and procedures using the National Crime Information Center interstate identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility access and local security policies and procedures (provided by government representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

1.6.20.4 For Contract Requiring Performance or Delivery in a Foreign Country: Use language from DFARS Clause 252.225-7043, Antiterrorism/Force Protection for Defense Contractors outside the United States (OCONUS). The clause shall be used in solicitations and contracts that require performance or delivery in a foreign country. This clause applies to both contingencies and non-contingency support.