Attachment F.pdf

Attachment F

PROGRAM MANAGEMENT SUPPORT

TASK ORDER 01

STATEMENT OF WORK (SOW)

1. BACKGROUND

1.1 In the period after the tragic events of September 11, 2001 the requirement for a national information exchange and collaboration system became obvious. The Homeland Security Information Network (HSIN) evolved from a Department of Defense, state and local law enforcement program, implemented in early 2003, for sharing information and intelligence. That program, known as the Joint Regional Information Exchange System (JRIES), was transferred to the Department of Homeland Security in late 2003 and became HSIN in February 2004. HSIN was broadened to include not only the original intelligence sharing functions afforded to law enforcement but to also include, State Homeland Security Advisors, Governors’ offices, emergency services managers, first responders, and the National Guard. HSIN was also modified to include a component for cyber defense and for private sector entities concerned with infrastructure protection.

HSIN became the Department’s primary nation-wide solution for Sensitive But Unclassified (SBU) information sharing and collaboration. , HSIN provides secure, encrypted information exchange over the Internet, is an umbrella for several specialized information exchange networks and services, and is a system of collaborative communication tools used in routine, daily functions for information sharing, collaboration, alerting and prevention in support of national critical infrastructure protection and threat mitigation as determined by HSPD 5 and 7.

1.3 The Under Secretary for Intelligence and Analysis is the DHS Executive Agent for information sharing, and the Chair of the Information Sharing Governance Board (ISGB) has been designated the HSIN business owner. The Program Management Office, or PMO, undertakes the implementation and management of HSIN on behalf of the HSIN business owner. The HSIN PMO is currently responsible for the funding, effective management and operations of HSIN. It is also responsible for developing the technical capacity and business processes to address mission requirements. The PMO currently supports other DHS elements, federal, state, tribal, and local governmental organizations, and key private sector entities (coordinated through the respective Program Sponsors, such as HSIN-CS in Preparedness Infrastructure Partnerships Division) to develop validated requirements for HSIN capabilities, procedural implementations and associated training. The PMO supports the identification of technical, procedural and training requirements gathered from HSIN stakeholder communities.

1.4 Currently HSIN users include DHS, other federal departments, the 50 states, the US Territories, tribal areas, Washington, DC and local governmental jurisdictions including 53 major cities, private sector , selected counties, and four foreign countries. These users are served through a series of “Communities of Interest.” DHS plans to expand the functionality of HSIN, as well as the number of users significantly over the next five years. DHS plans to develop and implement a new, more capable and robust technical solution for HSIN, referred to as HSIN v 3.0. The contractor selected under this statement of work will support DHS’s plans for expansion through the specific tasks defined in Section 4.

2. OBJECTIVES

The objectives of this effort are to provide overall program management, development oversight, technical direction, and program support for the HSIN. The success of HSIN depends on the coordination and cooperation of multiple agencies and personnel at the Federal, state, and local levels, as well as the private sector. This effort shall support the need to ensure continued successful operation and expansion of the HSIN.

As the PMO Support contractor, the vendor will take all necessary steps to avoid conflict of interest when providing contract support to the PM. If this is not possible, the vendor and their subcontractors risk removal from this contract.

3. SCOPE

Overall management of the HSIN program in support of the Program Manager, maintaining day-to-day HSIN program operations, requirements management, monitoring all HSIN activities and contracts, performing quality assurance, coordinating activities among other contractors and Federal and state governments, working with the HSIN Leadership team refining the Program’s strategic direction.

4. SPECIFIC TASKS

All services provided under this task order must be compliant with DHS 4300B DHS National Security System Policy and the DHS 4300B National Security System Handbook.

Task 1 – Task Order Management

The contractor PM shall manage this task order, provide oversight of the project, and perform quality assurance activities over their efforts. The contractor shall develop and maintain a Task Order Management Plan (TOMP). The TOMP shall contain, at a minimum, plans for staffing, quality assurance, risk management, cost and schedule tracking for their execution of this task order. The TOMP shall include as appendices a project organizational chart, Work Breakdown Structure/Project Schedule, and spend plan forecasting monthly and cumulative project expenditures; the contractor shall update and deliver these three appendices monthly.

Less than five percent of the contractor lead’s time will be spent on task order management.

Task 2 - PM Support

2.1. Program Planning The contractor shall assist the federal HSIN PM in maintaining day-to-day operations and in ensuring coordination with the systems integrators supporting HSIN. The contractor shall update and maintain the Program Management Plan for the HSIN Program encompassing the work of all contractors and federal staff.

2.2 Risk Management The contractor shall maintain a process to identify risks and provide suggestions for mitigating the risks. The contractor shall prepare monthly reports indicating progress, cost, issues, identified risks, or impediments to progress. In addition, the contractor will roll up risks associated with each of the projects that make up the HSIN Program. The contractor will work with the project PMs to mitigate risks and communicate possible conflicts.

2.3 Integrated Master Scheduling The contractor shall roll up and maintain an integrated master schedule coordinating all activities of the program. The contractor shall also conduct a monthly Program Review for the government Program Manager and other designated staff encompassing the status of the work of all contractors and federal staff. Finally, the contractor shall review the Concept of Operations (CONOPS) annually with relevant stakeholders and make necessary updates.

2.4 Document Management As part of program management, the contractor shall maintain the HSIN centralized repository of program documentation, products, and deliverables. The contractor shall provide deliverable and document management services for all major program documents including responses to oversight bodies such as Government Accountability Office (GAO), DHS Office of Inspector General (OIG), and the Office of Management and Budget (OMB). These documents shall be uploaded into a repository. The contractor will develop and monitor a workflow acceptance process for all SELC documents and contractor deliverable acceptance.

2.5 Configuration Control The contractor shall also support the Configuration Control Board by coordinating and facilitating biweekly meetings, performing quality review on each proposed system change request or problem report, and biweekly reviewing and auditing the requirements database. The contractor shall manage the configuration control process.

2.6 Management Information Reporting and CPIC support The contractor shall provide management information reports to internal and external partners on a routine, recurring, and as-needed basis. Federal managers use this information to assess the programs. The contractor will update nPRS monthly and update milestones. The contractor will work with the PM to align information provided in the Exhibit 300, nPRS, and the OMB dashboard.

2.6.1. Earned Value Management The contractor shall track the progress of the development contractor using industry standard earned value management suitable for agile development. Standard EVM reports will be collected, analyzed, and results combined into the overall Program monthly reporting.

2.7 Governance Review Board Support The contractor shall support all ARB and ITAR reviews. The contractor will track all questions and conditions for approval. The contractor shall work with the PM to incorporate timely reviews into the program schedule. The contractor shall help the PM with contract updates.

2.8 Pricing and Budgeting Support The contractor shall support the HSIN PM in producing pricing estimates for contracts and option years. The contractor shall be knowledgeable on the full Life Cycle Cost Estimation documentation required for each investment including Independent Government Cost Estimates (IGCE) and Task Order modifications.

2.9 License and Inventory support The contractor shall assist the federal PM in tracking software licenses and managing GFE. This includes T&E lab equipment, GFE laptops loaned to contractors, and security token provisioning.

Task 3 –Technical Management

3.1 Technical Monitoring In conjunction with both the DHS and the Program Configuration Control Boards, the contractor shall monitor the use of technology supporting HSIN to ensure that the system is making best use of the existing or target technical architecture. The contractor shall review for suitability proposed HSIN design, and technical solutions. The contractor also shall review system development activities (the COTR will provide access) for conformance to government development standards as appropriate to the CIO standards and industry best practices. The contractor shall provide recommendations to the government for technical improvements to HSIN as business or technology requirements change, and as applicable new technologies reach maturity.

3.2 DHS Data Center Liaison The contractor shall assist the federal PM in managing the relationship with each of the two major DHS Data Centers. The contractor shall maintain a schedule of activities for implementing the HSIN platform in the data centers. The contractor shall provide weekly and monthly status on all activities associated with the data centers.

3.3 Identity Management (IDM) Implementation and Integration The contractor shall support integration of an Enterprise ready IDM solution with the latest HSIN platform. This includes being knowledgeable with all aspects of IDM and the HSIN tiered security strategy.

3.4 Global Federated Identity and Privilege Management (GFIPM) Support The contractor shall provide technical and business support for implementing all aspects of GFIPM and other interoperability solutions and becoming interoperable with the other major SBU information sharing solutions.

3.5 Development Support The contractor shall provide technical development resources sandbox support.

Task 4 – Enterprise Architecture and Portal Consolidation Support

4.1 Program EA Reviews The contractor shall provide support for all EAB data calls, required documents and briefings. The contractor shall track all EAB questions and conditions for approval. The contractor shall work with the PM to incorporate timely reviews into the program schedule. The contractor shall collect all information necessary for Technical Insertion Packages. If called upon, the contractor shall represent either the HSIN or COP Programs before the EAB.

4.2 EA Alignment The contractor shall provide support for aligning the platform and services with the DHS EA.

4.3 Consolidation Planning The contractor shall work with designated portal owners and the OAT Enterprise Architect to develop project management plans for each portal to be consolidated onto the HSIN platform.

4.4 Migration Support The contractor shall provide support for each portal during all stages of the portal consolidation process.

4.5 Engineering Support- As required and requested the Contractor shall provide implementation and development project team resources to support the consolidation, integration, or interoperability of existing DHS Sensitive but Unclassified (SBU) Information Sharing and Collaboration Portals or Applications on the HSIN Platform.

Task 5 - Requirements and Release Management

5.1 Requirements Analysis The contractor shall create and maintain a document of all requirements for the HSIN. The contractor shall also develop and maintain the Requirement Traceability Matrix and Use Cases/Mission scenarios, documented and stored in a requirements repository consistent with industry best practices. Experience with requirements management tools is required.

5.2 Release Management The contractor shall assist the federal PM with maintaining the release management strategy. The contractor shall assist the federal HSIN PM in compiling requirements into release packages capable of being implemented with an agile development methodology.

Task 6 - Agile Development Support

6.1 Scrum Manager The contractor shall provide an experienced and qualified scrum master to lead the systems integration contractor’s scrum manager. This individual shall also work with the requirements team, outreach team, and the release manager.

Task 7 - Testing Support

7.1 Test Lab Support The contractor shall maintain the HSIN test lab schedule, manage testing configurations, and when requested assist in testing.

7.2 User Acceptance Testing Support The contractor shall assist with user acceptance testing. The contractor will manage necessary access control paperwork necessary to enable users to access the test environment.

Task 8 - Operations & Maintenance (O&M) Support

8.1 O&M Liaison The contractor shall provide coordination support for the HSIN PM with the contractor O&M vendor. This includes coordinating with the iCCB, release management, testing, and status reporting.

(Optional) Task 9 - Minor Portal Development Services

9.1 Development When requested, the contractor shall provide development resources to support minor releases after the platform has achieved FOC.

5. DELIVERABLES/DELIVERY SCHEDULE

All deliverables shall be prepared in the contractor format using Microsoft Office Suite tools and delivered electronically to the COTR and alternate COTR. Weekly deliverables are due by 3PM on Friday. All days listed are calendar days. Monthly deliverables are due on the 5th business day.

SOW Task # Deliverable Title Due Date

1 Task Order Management Plan 14 calendar days (CDs)after award

2.1 Program Management Plan Update 30 CDs after TO award

2.1 Integrated Project Team Charters As required, PMO

2.1, 2.6 Program Performance Reports Monthly 2.1, 2.6 Program Status Meetings Weekly, 2.1, 2.6 Program Reviews Monthly

2.2 Risk Management Plan Update 30 CDs after TO award

2.2 Program Risk Analysis Reports Monthly

2.3 Master Schedule Implementation Plan

30 CDs after TO award

2.3 Master Schedule Revisions Weekly, on the 5th of the Mo

2.4 Document Management Plan 30 CDs after TO award

2.5 Configuration Control Board Packages As required

2.6 CPIC - Operational Analysis Annually as part of the Exhibit

300 submission

2.6 CPIC Products including the OMB 300 Annually as part of the Exhibit

2.6 Earned Value Management Reports Monthly, on the 15th of the Mo

2.9 HSIN License and Warranty Inventory Annually

3 Technology Monitoring Reports Quarterly, 15th of the Mo

4.3 Portal Consolidation Project and

Implementation Plans One for each consolidation/project implementation plan due in accordance with the directions given by the Portal Consolidation

IPT

5.1 Requirements for HSIN 3.0, Initial

Requirements Traceability Matrix, and Use Cases, User Stories, Agile Backlog

As required

5.1 Requirements Updates to Traceability

Matrix and User Stories

Monthly, on the 5th of the Mo

5.2 Release Management Plan Update 30 CDs after TO award

5.2 Release Packages As required

7 Testing Schedule Updated Monthly

6. GOVERNMENT-FURNISHED EQUIPMENT (GFE)/GOVERNMENT

FURNISHED INFORMATION (GFI)

All referenced GFI will be provided by the COTR, including products and materials from other contractors on which this contractor shall perform quality assurance review. The actual HSIN system hardware and software are owned and operated by the government, although the HSIN can be accessed on any computer connected to the Internet.

7. SECURITY

7.1 General

7.1.1 DHS has determined that performance of this contract requires that the contractor, subcontractor(s), vendor(s), etc., have access to classified National Security Information (herein known as classified information) at the Secret level, and will require access to sensitive but unclassified (SBU) information. Classified information is government information that requires protection in accordance with Executive Order 12958, Classified National Security Information and supplementing directives. SBU is unclassified information for official use only.

7.1.2 All personnel to this contract will have at least an Interim SECRET clearance. The contractor will abide by the requirements set forth in the DD Form 254, Contract Security Classification Specification, included in the contract, and the National Industrial Security Program Operating Manual (NISPOM) for the protection of classified information at its cleared facility, if applicable, as directed by the Defense Security Service. If the contractor has access to classified information at a DHS or other government facility, it will abide by the requirements set by the agency.

7.2 Security Requirements

(a) This applies to the extent that this contract involves access to information classified “Secret.”

(b) The Contractor shall comply with—

(1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DOD 5220.22-M); and

(2) Any revisions to that manual, notice of which has been furnished to the Contractor.

(c) If, subsequent to the date of this contract, the security classification or security requirements under this contract are changed by the Government and if the changes cause an increase or decrease in security costs or otherwise affect any other term or condition of this contract, the contract shall be subject to an equitable adjustment as if the changes were directed under the Changes clause of this contract.

(d) The Contractor agrees to insert terms that conform substantially to the language of this clause, including this paragraph (d) but excluding any reference to the Changes clause of this contract, in all subcontracts under this contract that involve access to classified information.

7.3 Employment Eligibility

7.3.1 The contractor must agree that each employee working on this contract will have a Social Security Card issued and approved by the Social Security Administration. The contractor shall be responsible to the Government for acts and omissions of his own employees and for any subcontractor(s) and their employees.

7.3.2 Subject to existing law, regulations, and other provisions of this contract, illegal or undocumented aliens shall not be employed by the contractor, or with this contract. The Contractor will ensure that this provision is expressly incorporated into any and all subcontracts or subordinate agreements issued in support of this contract.

7.4 Suitability Determination

7.4.1 DHS shall have and exercise full control over granting, denying, withholding or terminating unescorted government facility and/or sensitive Government information access for Contractor employees, based upon the results of a background investigation.

DHS may, as it deems appropriate, authorize and make a favorable entry on duty (EOD) decision based on preliminary security checks. The favorable EOD decision would allow the employees to commence work temporarily prior to the completion of the full investigation. The granting of a favorable EOD decision shall not be considered as assurance that a full employment suitability authorization will follow as a result thereof.

7.4.2 The granting of a favorable EOD decision or a full employment suitability determination shall in no way prevent, preclude or bar the withdrawal or termination of any such access by DHS, at any time during the term of the contract. No employee of the Contractor shall be allowed unescorted access to a Government facility without a favorable EOD decision or suitability determination by the Security Office. Contract employees assigned to the contract not needing access to sensitive DHS information or recurring access to DHS’ facilities will not be subject to security suitability screening.

7.4.3 Contract employees awaiting an EOD decision may begin work on the contract provided they do not access sensitive Government information. Limited access to Government buildings is allowable prior to the EOD decision if the Contractor is escorted by a government employee. This limited access is to allow Contractors to attend briefings, non-recurring meetings and begin transition work.

7.5 Background Investigations

7.5.1 Contract employees (to include applicants, temporaries, part-time and replacement employees) under the contract, needing access to sensitive information, shall undergo a position sensitivity analysis based on the duties each individual will perform on the contract. The results of the position sensitivity analysis shall identify the appropriate background investigation to be conducted. All background investigations will be processed through the Security Office. Prospective contractor employees shall submit the following completed forms to the Security Office through the COTR no more than 30 days before the starting date of the contract or 30 days prior to entry on duty of any employees, whether a replacement, addition, subcontractor employee, or vendor:

Standard Form 85P, “Questionnaire for Public Trust Positions” FD Form 258, “Fingerprint Card” (2 copies) Conditional Access to Sensitive But Unclassified Information Non-Disclosure Agreement Disclosure and Authorization Pertaining to Consumer Reports Pursuant to the Fair

Credit Reporting Act

7.5.2 Required forms will be provided by DHS at the time of award of the contract. Only complete packages will be accepted by the Security Office. Specific instructions on submission of packages will be provided upon award of the contract.

7.5.3 Be advised that unless an applicant requiring access to sensitive information has resided in the United States for three of the past five years, the government may not be able to complete a satisfactory background investigation. In such cases, DHS retains the right to deem an applicant as ineligible due to insufficient background information.

7.5.4 The use of non-U.S. citizens, including Lawful Permanent Residents (LPRs), is not permitted in the performance of this contract for any position that involves access to or development of any DHS IT system. DHS will consider only U.S. citizens and LPRs for employment on this contract. DHS will not approve LPRs for employment on this contract in any position that requires the LPR to access or assist in the development, operation, management or maintenance of DHS IT systems. By signing this contract, the contractor agrees to this restriction. In those instances where other non-IT requirements contained in the contract can be met by using LPRs, those requirements shall be clearly described.

7.6 Continued Eligibility

7.6.1 If a prospective employee is found to be ineligible for access to government facilities or information, the COTR will advise the contractor that the employee shall not continue to work or to be assigned to work under the contract.

The Security Office may require drug screening for probable cause at any time and/ or when the contractor independently identifies, circumstances where probable cause exists.

The contractor will report any adverse information coming to their attention concerning contract employees under the contract to DHS’ Security Office. Reports based on rumor or innuendo should not be made. The subsequent termination of employment of an employee does not obviate the requirement to submit this report. The report shall include the employees’ name and social security number, along with the adverse information being reported.

7.6.2 The Security Office must be notified of all terminations/resignations within five days of occurrence. The contractor will return any expired DHS issued identification cards and building passes, or those of terminated employees to the COTR. If an identification card or building pass is not available to be returned, a report must be submitted to the COTR, referencing the pass or card number, name of individual to whom issued, the last known location and disposition of the pass or card.

7.7 Security Management

7.7.1 The Contractor shall appoint a senior official to act as the Corporate Security Officer. The individual will interface with the Security Office through the COTR on all security matters, to include physical, personnel and protection of all Government information and data accessed by the Contractor.

7.7.2 The COTR and the Security Office shall have the right to inspect the procedures, methods, and facilities utilized by the Contractor in complying with the security requirements under this contract. Should the COTR determine that the Contractor is not complying with the security requirements of this contract; the Contractor will be informed in writing by the Contracting Officer of the proper action to be taken in order to effect compliance with such requirements.

7.8 Information Technology Security Clearance

7.8.1 When sensitive government information is processed on DHS telecommunications and automated information systems, the Contractor agrees to provide for the administrative control of sensitive data being processed and to adhere to the procedures governing such data as outlined in DHS IT Security Program Publication DHS Management Directive 4300. Contractor personnel must have favorably adjudicated background investigations commensurate with the defined sensitivity level.

7.8.2 Contractors who fail to comply with DHS security policy are subject to having their access to DHS IT systems and facilities terminated, whether or not the failure results in criminal prosecution. Any person who improperly discloses sensitive information is subject to criminal and civil penalties and sanctions under a variety of laws (e.g., Privacy Act).

7.9 Information Technology Security Training and Oversight

7.9.1 All Contractor employees using DHS automated systems or processing DHS sensitive data will be required to receive Security Awareness Training. This training will be provided by the appropriate component agency of DHS.

7.9.2 Contractors, who are involved with management, use, or operation of any IT systems that handle sensitive information within or under the supervision of DHS, shall receive periodic training at least annually in security awareness and accepted security practices and systems rules of behavior.

7.9.3 All personnel who access DHS information systems will be continually evaluated while performing these duties. Supervisors should be aware of any unusual or inappropriate behavior by personnel accessing systems. Any unauthorized access, sharing of passwords or other questionable security procedures should be reported to the local Security Office or Information System Security Officer (ISSO).

7.10 Non-Disclosure of Protected Critical Infrastructure Information

7.10.1 The parties agree to implement an interim rule promulgating new regulations at Title 6 Code of Federal Regulations Section 29.8 (c) to govern procedures for handling critical infrastructure information. The regulations detailed in the interim rule, which was effective upon publication pursuant to Section 808 of the Congressional Review Act, were promulgated pursuant to Title II, Section 214 of the Homeland Security Act of 2002, known as the Critical Infrastructure Information Act of 2002 (CII Act).

7.10.2 The contractor shall comply with all requirements of the Protected CII (PCII) Program set out in the CII Act, in the implementing regulations published in the Interim Rule, and in the PCII Procedures Manual as they may be amended from time to time, and shall safeguard Protected CII in accordance with the procedures contained therein.

7.10.3 The contractor shall ensure that each of its employees, consultants and subcontractors who work on the PCII Program have executed Non-Disclosure Agreements (NDAs) in a form prescribed by the PCII Program Manager. The contractor shall ensure that each of its employees, consultants and subcontractors has executed a NDA and agrees that none of its employees, consultants or subcontractors will be given access to Protected CII without having previously executed a NDA.

8. PERIOD OF PERFORMANCE

9.1 Transition Period: 45 days

9.2 Base period: 320 calendar days

9.3 Option Period 1: 6 months after base period

9.4 Option Period 2: 6 months after option period

9.0 KEY PERSONNEL

9.1 Key Personnel The (1) HSIN Project Manager, (2) HSIN Technical Lead, (3) Scrum Master shall be designated as Key Personnel.

9.1.1 The HSIN Project Manager shall perform the duties enumerated in the SOW. The minimum qualifications are:

9.1.1.1 Four (4) to six (6) years of specific experience in managing large, complex projects in a task order/contract environment; experience performing the day-to-day management of overall contract/task order support operations involving multiple projects and groups of personnel; experience organizing, directing and coordinating the planning and production of contract/task order support activities; excellent written and oral communication skills; experience managing the client interface at the senior levels of the client organization. Has the ability to establish and alter, as necessary, technical approach to directly affect task order/contract support activities. Knowledge of the DHS SELC and PMI certification (or demonstrated understanding and experience with the PMBOK).

9.1.1.2 A Bachelor’s degree from an accredited institution of higher learning and a Secret security clearance with eligibility for access to Sensitive Compartmented Information (SCI).

9.1.2 The HSIN Technical Lead shall provide identification/fixing of problems within existing systems, design/implementation of new systems and enhancement of existing systems. Participate in analysis, design and new construction of next generation IT systems. Be responsible for understanding the needs of the customers and the realities of commercially available IT products, and creating requirements that will allow implementation by the architecture and engineering team and COTS products. The minimum qualifications are:

9.1.2.1 Four (4) to six (6) years of specific experience as a systems engineer on one or more IT portal platform development efforts is preferred, must have technical background with a focus on IT systems, must possess experience of system engineering in one or more areas including telecommunications concepts, computer languages, operating systems, database/DBMS and middleware and have experience managing other team members. Must have experience with Microsoft SharePoint implementation.

9.1.2.2 A four year college degree from an accredited institution of higher learning and a Secret security clearance with eligibility for access to Sensitive Compartmented Information (SCI).

9.1.3 The Scrum Master shall perform the duties enumerated in the SOW. The minimum qualifications are:

9.1.3.1 Four (4) to six (6) years of specific experience in managing large, complex agile development projects in a task order/contract environment; experience performing the day-to-day scrum management duties; experience organizing, directing and coordinating the planning and production of user story from the Program backlog; excellent written and oral communication skills; experience managing the client interface at the senior levels of the client organization.

Knowledge of the DHS SELC and PMI certification (or demonstrated understanding and experience with the PMBok).

9.1.3.2 A Bachelor’s degree from an accredited institution of higher learning and a Secret security clearance with eligibility for access to Sensitive Compartmented Information (SCI).

9.1.4

9.1.6 Substitution of Key Personnel

The Contractor shall notify the TO CO and TO COTR prior to making any changes in Key Personnel. All proposed substitutes shall have qualifications equal to or better than the qualifications of the person to be replaced. The TO CO and TO COTR must be notified in writing of any proposed substitutions at least fifteen (15) business days in advance of the proposed substitution. The notification shall include:

9.1.6.1 An explanation of the circumstances necessitating the substitution; and

9.1.6.2 A resume of the proposed substitute.

The TO CO and the TO COTR will evaluate substitutions and notify the Contractor of their approval or disapproval in writing.

9.2 Removal of Contractor Employees

The Contracting Officer, through COTR recommendations, may require dismissal from work of those contractor employees which he/she deems incompetent, careless, insubordinate, unsuitable or otherwise objectionable, or whose continued employment he/she deems contrary to the public interest or inconsistent with the best interest of national security. The contractor must fill out, and cause each of its employees on the contract work to fill out, for submission to the Government, such forms as may be necessary for security or other reasons.

10. OTHER CONSIDERATIONS

10.1 All data, regardless of media, is owned solely by the Government; any use without government/owner permission is prohibited

10.2 The successful contractor is precluded from bidding on any development and/or HSIN integration requirements proposed for quotation or proposals