SharePoint RFP - Section B - M.doc

DOC document 956 KB Posted

Attached to
SharePoint Integration and Support Services Federal contract opportunity
Solicitation number
HSCETC-10-R-00015
Issued by
Immigration and Customs Enforcement

About this file

Section B - M

View the file

Other files for this federal contract opportunity

Other files attached to SharePoint Integration and Support Services, newest first.
File Type Posted
HSCETC-10-R-00015 A0003.pdf PDF
Attachment 3-Pricing Matrix.xls XLS spreadsheet
Attach 7DD254.pdf PDF
Attach 4 OCIO.doc DOC document
A0002 Sol 55-64.pdf PDF
Attach 1 SOW —
A0002 Sol 116-131.pdf PDF
A0002 Sol 5-54.pdf PDF
Attach 2 PPQ.doc DOC document
Attach 6ClassContract.pdf PDF
A0002CoverSheet.pdf PDF
A0002 Sol 65-115.pdf PDF
HSCETC-10-R-00015P0001.pdf PDF
RFPQuestionSharePoint 4 20 20 final.pdf PDF
SharePoint RFP Tech - ICE_MOSS 20Intranet 20Physical 20Production 20Topology_jpg.jpg JPG image
SharePoint RFP - Section A.pdf PDF
SharePoint RFP Tech - SLM 20Hand 20Book.pdf PDF
SharePoint RFP - Attach 4 - OCI Disclosure Forms.pdf PDF
SharePoint RFP Tech - 33443 Information Assurance Program Policy FINAL asof 20100309.doc DOC document
SharePoint RFP Tech - DHS_Sensitive_Systems_Policy_4300A_v7dot1.doc DOC document
SharePoint RFP Tech - Table of Contents - ICE- OCIO Technical Documents .doc DOC document
SharePoint RFP Tech - DHS 20MD 20140-02.pdf PDF
SharePoint RFP Tech - SLM 20Test 20Evaluation.pdf PDF
SharePoint RFP - Attach 2 -Past Perf Questions.pdf PDF
SharePoint RFP Tech - Standards Web Services .doc DOC document
SharePoint RFP - Response to Questions Asked at Pre-Proposal Conference —
SharePoint RFP Tech - IA Program Policy-Handbook FINAL as of 20090127.doc DOC document
SharePoint RFP Tech - SLM 20Tech 20Ref 20guide 20Book.pdf PDF
SharePoint RFP - Attach 3 - Pricing Matrix.pdf PDF
SharePoint RFP Tech - Systems 20Assurance 20Plan.pdf PDF
SharePoint RFP - Attach 1- TO SOW.pdf PDF
SharePoint - Pre-Proposal Conference Presentation —
SharePoint - Pre-Proposal Conference - List of Registrants.xls XLS spreadsheet
SharePoint - Answers to Questions on Draft SOW.doc DOC document
SharePoint - Registration Form.doc DOC document
SharePoint - SOW.doc DOC document
SharePoint - SOW_Task Order1.doc DOC document
Show all 37

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

SECTION B: SUPPLIES/SERVICES PRICE/COST SCHEDULE

B-1 SUPPLIES AND SERVICES

The Government intends to award multiple awards to one or more contractors as a total Small Business set-aside. All contractors within a Small Business concern will be considered equal competitors for acquisitions provided to that Small Business for competition.

B-1.1 The contractor shall provide Information Technology (IT) services in support of the Department of Homeland Security (DHS), Immigrations and Customs Enforcement (ICE), Office of the Chief Information Officer (OCIO).

B-1.2 These required services and supplies shall be provided in accordance with the requirements specified in Section C, DESCRIPTION/SPECIFICATIONS /STATEMENT OF WORK for IT support and services of Office SharePoint Server version 2007 and will be specific detailed in individual task orders issued in accordance with Sections G, H, and I.

B-2 CONTRACT LINE ITEM DESCRIPTIONS.

The Contractor shall furnish all personnel, facilities, equipment, material, supplies, and services (except as may be expressly set forth in this contract as furnished by the Government) and otherwise do all things necessary to, or incident to, performing and providing the following items of work: SharePoint Integration and Support Services B-2.1 Offeror is to input hours, unit prices, Contract Line Item Number (CLIN) total amounts, annual total contract value amounts, and a summary of all contract years with an estimated total value of the contract in accordance with the CLIN structure represented on the SF-33.

B-3. PERFORMANCE

Performance under this contract, actual hours and reimbursable amounts will be specified in individual task orders. Reference Section I clauses entitled “Ordering” (FAR 52.216-18), “Ordering Limitations” (FAR 52.216-19) and “Indefinite Quantity” (FAR 52.216-22)

B-3.1 The period of performance is addressed under Section F DELIVERIES OR PERFORMANCE.

B-4 ORDERING ACTIVITY

The Department of Homeland Security (DHS), Immigrations and Customs Enforcement (ICE) is the sole authority to request services under this contract.

B-5 TYPE OF CONTRACT

The resulting contract will be an, multiple awarded, Indefinite Delivery, Indefinite Quantity (IDIQ) contract with Firm-Fixed Price (FFP) ( pre-negotiated loaded hourly labor rates), and or Cost-Plus-Fixed-Fee (CPFF) and Cost Reimbursable ( Other Direct Costs (ODC) CLINs.

B-6 CONTRACT MINIMUM AND MAXIMUM QUANTITIES

In accordance with Section I clause 52.216.22 entitled “Indefinite Quantity” the minimum guaranteed valued under this contract is $2,500.00 per contract. This contract minimum will be met by the issuance of individual task orders. In addition to contract minimum, the Government may order additional quantities up to the maximum of $272 million dollars. The contract maximum represents ICE/OCIO’s total requirement for the life of the contract (including options, if exercised). It is intended that the contract requirements will be meet through multiple contract vehicles: however, each contract must have the capacity to meet the total maximum required. The contract maximum is established for the purpose of assuring adequate contract support is available to sustains ICE/OCIO’s

B-7 NAICS/PSC

NAICS Code for this acquisition is 541512, Computer Systems Design Services and PSC Code: D302, ADP Systems Development Services

SECTION C: STATEMENT OF WORK

C-1 PROJECT TITLE

ICE SharePoint Integration and Support Services

C-2 BACKGROUND

ICE’s mission is to protect national security by enforcing our nation's customs and immigration laws. This responsibility includes such tasks as border security, targeting international street gangs, cyber crimes, intellectual property rights, and secure communities. In addition to the Chief Information Office and headquarters complement, ICE includes five operating divisions: Federal Protective Service, Intelligence, Investigations, International Affairs, and Detention and Removal Operations. To promote information sharing and business process automation throughout the agency, the ICE Collaboration Tool (ICECT) is under development for distribution to interested offices throughout ICE.

The Office of the Chief Information Officer (OCIO) is the organization responsible for information technology in ICE. OCIO is responsible for supporting business processes with the design, development, programming, testing, implementation, technical support and maintenance of ICE automated systems to include, but not limited to, the management of all ICE computer facilities and systems which also includes hardware, software, data, video, wireless and voice telecommunications and their related financial resources and applications. OCIO is responsible for identifying and evaluating new technologies for insertion into the current technical architecture in support of ICE business processes.

The Immigration and Customs Enforcement (ICE) is dependent upon information technology to fulfill its mission. The dynamic growth in workload and staffing has resulted in the expanded use of information technology by ICE users. As enhanced performance requirements are identified by the agency to address business process automation within the various programs the need to provide specific, improved, faster and more robust functionality, responsiveness and availability for ICE production applications.

An essential and fundamental tool in addressing many of the above requirements is the enhancement of the ICE Collaboration Tool (ICECT). This state of the art application environment provides a highly integrated set of enterprise class tools capable of providing business automation, custom workflow, document and information sharing and powerful customization capabilities. Without this modern capability, ICE cannot efficiently fulfill its mission. Consequently, ICE seeks to continue to enhance, expand, and upgrade the ICECT in order to ensure this environment continues to address the agency’s needs now and in the future.

C-3 SCOPE

The scope of this contract is to provide the ICE all necessary management, supervision, materials, services, support, maintenance, identification, and performance resources for the ICECT environment operational and maintenance activities. The Contractor shall support existing and prospective ICECT sites as the agency expands the ICECT operational model to include additional ICE programs as required. The tasks under this contract include supporting validation and measurement of system integration in the areas of collaboration, security, connected systems, operational efficiency and deployments, installation, testing, documentation, problem resolution and maintenance of the ICECT production and other related environments.

The Contractor shall be able to perform and support all aspects associated with Microsoft Office SharePoint Server 2007 including administration, operations, development, troubleshooting, design and implementation of these environmental solutions. This work shall be performed in accordance and consistent with the objectives of this contract and SOW. The contractor shall be knowledgeable of records management 5015.2 Specification, historic preservation regulations, and the ICE System Lifecycle Methodology. The Contractor shall provide developer and support expertise to develop, implement and maintain solutions and transfer knowledge to the Government; Support validation and measurement of system integration in the areas of collaboration, security, connected systems, operational efficiency and deployments. The Contractor shall provide technical and programmatic support on major task area projects, including planning and budgeting; defining the technology architecture; establish project requirements, priorities and deadlines; coordinate resources across projects; analyze, cost, schedule and technical performance; and develop integrated project schedules across multiple teams working on development activities. The Contractor shall stay abreast of emerging technologies and shall provide the technical expertise and support identifying, coordinating and implementing new technologies into the ICE environment.

The Contractor shall work around the government’s schedule to minimize disruptions. The Contractor shall handle all aspects of system design and development, installation and conduct performance testing to assure that connections meet specifications. This is a centralized approach for addressing the ICECT environment operational needs for the ICECT environment at a reasonable cost.

ICE requires an Indefinite Delivery – Indefinite Quantity (IDIQ) contract that will allow the Systems Development Division flexibility to accomplish its mission in a constantly moving environment. This contract is a hybrid comprised of Firm Fixed Price, Cost-Plus Fixed Fee, and Cost Reimbursement Clines.

C-4.0 APPLICABLE DOCUMENTS

The Contractor shall comply with all technology standards and architecture policies, processes, and procedures defined in ICE OCIO Architecture Division publications. These publications include, but are not limited to, the following:

· ICE System Lifecycle Management (SLM) Handbook

· ICE Enterprise Systems Assurance Plan

· ICE Architecture Test and Evaluation Plan

· ICE Web Standards and Guidelines

· ICE Technical Reference Model and Standards Profile

The Contractor shall not deviate from the SLM Process (including any tailored SLM work pattern) without express approval granted by the Government via the formal Request for Deviation (RFD) Process. If a deviation from the SLM Process is desired, the Program Manager must submit a formal RFD to the Architecture Division for adjudication. The Contractor shall not proceed with the deviation unless the Architecture Division approves the formal request and grants a waiver to deviate from the SLM Process. If the Architecture Division approves the RFD, the Contractor shall comply with all stipulations specified within the approval notification.

C-4.1 DHS HLS EA Compliance

All solutions and services shall meet DHS Enterprise Architecture policies, standards, and procedures as it relates to this SOW and associated Task Order. Specifically, the contractor shall comply with the following Homeland Security Enterprise Architecture (HLS EA) requirements:

· All developed solutions and requirements shall be compliant with the HLS EA.

· All IT hardware or software shall be compliant with the HLS EA Technology Reference Model (TRM) Standards and Products Profile.

· All data assets, information exchanges and data standards, whether adopted or developed, shall be submitted to the DHS Enterprise Data Management Office (EDMO) for review and insertion into the DHS Data Reference Model.

· The Contractor shall utilize a SharePoint (SP) development environment consisting of hardware and software products compliant with HLS EA standards. If the Contractor SP development environment will not consist of hardware and software products found in the DHS Technology Reference Model (TRM), a TIP must be compiled and submitted for EA approval to the DHS EACOE (Enterprise Architecture Center of Excellence). The TIP consists of a number of technical documents necessary to obtain EA approval for the software and/or hardware that is not currently listed on the DHS TRM. The TIP must be submitted and approved PRIOR to purchase of the Contractor SP development environment’s hardware and software products.

C-5 SPECIFIC TASKS

The anticipated Contract Line Item Numbering (CLIN) structure is:

Tasks
Task Type
Program Management
Firm Fixed Price
ICECT GSS Operations and Development Support
Cost Plus Fixed Fee
Special Projects (Optional)
Firm Fixed Price
Other Direct Costs (i.e. travel, equipment/software, miscellaneous)
Cost Reimbursable

The Contractor shall provide the required expertise to implement solutions and transfer knowledge to the Government and support validation and measurement of system integration in the areas of collaboration, security, connected systems, operational efficiency and deployments.

The Contractor shall define the technology architecture and ensure that the following processes are integrated: ICE Systems Lifecycle Management (SLM), Information Systems Security, Certification and Accreditation (C&A), and Capital Planning and Investment Control (CPIC). The Contractor shall collaborate with DHS efforts as directed to represent the ICE Program Office.

The Contractor shall provide site administration and site configuration support for 32 agency program collaboration sites and sub-sites as necessary.

The Contractor shall provide technical and programmatic support on major task area projects from initiation through implementation, including planning, budgeting, development, implementation, and operations and maintenance. Under the direction of the ICE Task Manager and other Government Subject Matter Experts (Sees), the Contractor shall establish project requirements; priorities and deadlines; and coordinate resources across projects.

The Contractor shall provide support for the following categories, as appropriate in support of individual task requirements that meet or exceed the respective areas described below;

C.5.1 Contractor’s Labor Categories C-5.1.1 Contractor’s Program Management

The Contractor shall assign a qualified Contractor’s Program Manager to provide project management coordination, oversight, planning, and administration of major task area projects to ensure that they are completed on time and under budget at the appropriate quality and performance measures.

The Contractor’s Program Manager shall be responsible for the oversight of all Task Orders including high-level program management support for this Task Area. The program management functions shall include, (1) assuring that project activities and deliverables are accomplished within the general scope of the task order on time, (2) monitoring and tracking the availability of the funds for authorized work and projects, (3) ensuring that all meetings are attended by the appropriate staff, (4) resolving task order level management and programmatic issues, (5) monitoring/ensuring task order performance within budget and schedule, (6) reviewing all reports for accuracy and performing trends and performance analysis, (7) monitoring and tracking appropriate approval procedures for the authorization of the Other Direct Costs (Odds), (8) performing quality control and implementing quality control measures, and (9) facilitating/maintaining effective interaction and coordination between ICE project leads and the contractor. Given the dynamic environment within ICE, the Program Manager shall closely monitor tasks and provide advanced notification of any deviation from budget, schedule, or resources.

The Contractor’s Program Manager (or an authorized designee) shall provide weekly status reports to the Government that includes accomplishments, status of ongoing activities, issues, recommendations for problem resolution, and upcoming activities. The Program Manager shall ensure that the COTR is provided an updated monthly listing of all Contractors’ staff to include Subcontractors. The Contractor’s Program Manager/designee shall track and invoice special projects within this Statement of Work (SOW) that may be specifically funded by the Congress, Office of Management and Budget (OMB), or DHS.

The Contractor’s Program Manager/designee shall meet with the Government on a weekly or ad hoc basis. The Contractor’s Manager/designee shall monitor the performance of their personnel, identify any degraded quality of service, and propose corrective actions to the Government up to and including employee termination.

The Contractor’s Program Manager shall ensure the Contractor has the capacity to provide resources and support 9x5 Monday through Friday, unless other support requirements are specifically outlined in the Task SOW. The Contractor shall be prepared to demonstrate the capacity and capability to support and provide resources to ensure coverage and projected staffing levels are appropriately addressing the requirement.

In addition to the task level activities, the Contractor’s Program Manager/designee shall provide oversight, management, coordination, and administrative support, as necessary to meet the requirements, objectives, and ICE priorities as identified by the COTR, Task Manager, or designee. This includes but is not limited to:

· Setting the overall direction, defining processes, setting standards, and providing leadership of the practice

· Ensuring smooth daily operation

· Ensuring and accountability for work activities, projects, and work assignments

· Ensuring optimal utilization of resources and growth

· Managing teams of subject matter experts and maintaining meeting minutes

· Prioritizing requirements consistent with the ICE priorities

· Ensuring work necessary work activities, projects, and assignments are included in the tasks, work breakdown structure (WBS), work plans, quality control plans, and other areas of which this contractor supports the government

· Effectively and accurately communicating progress to Government Task Managers and executive managers

· Managing scope and expectations while ensuring timelines, milestones, and schedules are being met

· Coordinating external and internal resources and ICE priorities

· Ensuring all contract employees and subcontractors adhere to the ICE security policies, directives and guidance

· Manage development and submission of contract deliverables

The Contractor’s Program Manager shall provide for each project a detailed charter, project management plan, work breakdown structure (WBS) with scheduled milestones, implementation plan, training plan, and transition document. These deliverables shall be consistent with the general management approach used in ICE and may detail the coordination of roles and responsibilities of other entities. The project management plan shall describe the project management control mechanisms, configuration and change management factors, reporting requirements, contingencies, and performance measures for the major milestones.

C-5.1.2 ICECT GSS Operations and Development Support C-5.1.3 Architecture Support The Contractor should be prepared to provide Architectural SME support and guidance to existing government resources in evaluating systems, solutions and configurations and making recommendations for solutions to agency tasks and requirements. This guidance will range across existing infrastructure and network framework, application architecture, application development, application security (guidelines and policies), operational guidelines to determine the best design for supporting Ice’s implementation of SharePoint and features and solutions that will reside within that framework. The Architect/Contractor shall also provide SME support in the area of SharePoint supporting resources such as SQL Server, SQL Server Reporting Services, InfoPath Forms Service, Reporting Business Analytics and Integration services as well as any application development as necessary. The Architect/Contractor shall provide assistance in establishing a well-designed governance plan, to include requirements management, to support the efficient use of the SharePoint framework being setup for the agency.

C-5.1.4 Development Support The Contractor should be prepared to provide custom development support for applications, workflows, forms, web parts and other .Net platform specific technologies. Developer’s skills and experience will be categorized into four areas; Senior Application Developer, Intermediate Application Developer, InfoPath Forms Designer/Developer, and Web Designer. These technical personnel shall provide the level of expertise needed to use and develop applications, forms, web parts and SharePoint sites in a SharePoint 2007 environment for both customized and out-of-the-box resources. The level of development will vary from client to client depending on requirements.

All developers (except web developer) must be familiar with CAML , C#, .Net Framework, coding to the SharePoint Server 2007 Object Model and other basic SharePoint development skills. The following paragraphs describe the levels of expertise for the specific type of development resources that may be required.

C-5.1.5 Intermediate Application Developer

Application Developers must have significant experience in developing SharePoint features, solution files, sites, managing SharePoint lists, document libraries and files, development of basic serial and parallel workflows, user profiles, security, Kip’s and Excel services. They must be familiar with best practices in extending and utilizing 3rd party plug-in and tools for SharePoint.

C-5.1.6 Senior Application Developer

Senior Application Developers must have significant experience in developing SharePoint features, solution files, sites, managing SharePoint lists, document libraries and files, development of basic serial and parallel workflows, user profiles, security, Kip’s and Excel services. They must be familiar with best practices in extending and utilizing 3rd party plug-in and tools for SharePoint. Additionally, the Sr. Application developers should be able to demonstrate competency in C#, ASP.Net, SharePoint Services v3.0, thorough understanding of the SharePoint Server 2007 Object Model and developing server side code that utilizes that API. Their duties will also include requirements definition, system and site design, source code testing review of developed code, deployment of code from a development environment to a staging environment.

C-5.1.7 InfoPath Designer/Developer

The InfoPath Designer must be familiar with XSL Transformation (XSLT); XML Schemas including the ability to define the structure of an XML document, including element names and rich data types, which elements can appear in combination, and which attributes are available for each element; Extensible Hypertext Markup Language (XHTML); XML Path Language (Path); The Document Object Model (DOM) and possess a clear understanding of this specification; XML Signatures and other technologies that are used and supported by the InfoPath service and application. The InfoPath designer should be thoroughly familiar with creation, deployment, versioning, reuse and management of InfoPath forms and libraries within the SharePoint Server 2007 environment. InfoPath designers should be prepared to provide custom and managed code in support of more complex and custom requirements necessary to develop form based solutions. This developer may be required to attend meetings where the site/application requirements will require the use of InfoPath forms.

C-5.1.8 Web Developer/Designer

The Web Developer will require knowledge in the creation, modification, deployment and management of web based design files such as SharePoint Master Pages, CSS, basic Style Sheets, SharePoint Navigation elements and general page and site usage experience for determining and designing usable pages. They should also have experience in applying web technologies to standard SharePoint files such as the Master pages, Layout pages, site definitions, etc.

These personnel should be able to attend client meetings and make valuable contributions to the overall SharePoint Development team.

C-5.1.9 Requirements Analyst

The Requirements Analyst shall provide support in gathering SharePoint Application and Site requirements for various Programs and Offices within the Agency. These duties will include interviewing clients to determine which requirements the SharePoint applications can be supported “out of the box” and which will require custom development. They should possess the ability to map user requirements to SharePoint functionality within a document. The Analyst may also be required to provide training as necessary.

C-5.1.10 Application Project Manager

The Application Program Manager will work closely with the Government SharePoint project manager to ensure that all task requirements and requests are addressed in a timely and professional manner, and to address all problems that arise in the process of developing solutions for SharePoint sites and applications. The Application Program Manager shall also engage the various aspects of ICE Program, Division, Branch and offices to understand their requirements for SharePoint functionality and presence. This position will require meeting with and representing the ICE SharePoint team with various ICE programs and offices. This position will manage all subprojects’ progress from creation through deployment and will track the various elements associated with establishing SharePoint Sites and applications. This tracking will include the attendance of SLM milestone and gate reviews as necessary that are associated with getting the sites and applications deployed. This position will prepare and deliver technical presentations to the Government. This position will work closely with and coordinate with other members of the SharePoint development team to ensure task and sub-tasks are being addressed and remain on schedule.

C-5.1.11Training Specialist

The training specialist shall be responsible for supporting the development of various training plans, user guides and other training documentation related to the education and instruction on the use, support, and maintenance of applications, sites and forms developed by the BSS. Trainers will be required to provide hands on training to users and to other potential system trainers as appropriate. They will coordinate the scheduling, reservation of resources and facilities for training related activities. Trainers will work closely with technical writers and testers to ensure they thoroughly understand the application(s) they are documenting and/or developing training materials for.

C-5.1.12 Application/Site Tester

The Tester shall create and execute test plans based on the requirements gathered for the purpose of validating developed sites/applications within the SharePoint 2007 environment. The Tester must have experience creating test plans based on a requirements document within a SharePoint environment. The tester must have experience with the SharePoint Server 2007 application and testing experience with this platform.

C-5.1.13 Technical Writer

The Technical Writer shall support the creation, modification and maintenance of system related documentation to include SLM and security documentation. The Technical Writer shall also be involved in the development of application user guides, reference material, training guides, presentations and varying policy related documents. Other documentation will vary but could include environment cataloguing, documenting system requirements, generating manual reports and other similar documentation requirements.

C-5.1.14 MOSS 2007 SharePoint Site Administrator

The SharePoint Site Administrator shall provide support in troubleshooting site problems, addressing site permission concerns, creating and configuring sites and sub sites, assisting in the definition of site resources, the performance of site administration for numerous collaboration sites, modification of site master pages and site definitions, development of basic InfoPath forms (basic refers to forms that contain no managed code or custom functionality), the recovery of lost documents or site resources, some training (telephonic or electronic as necessary), etc. The administrators activities will not be limited to the activities described here but will span across the collaborative environment as necessary. The Site administrator must be thoroughly familiar with the administration and configuration options available within SharePoint sites and subsides as well as several years of practical experience in this role.

The Contractor shall provide on-going application O&M support (troubleshooting, support for change requests/enhancements, analysis, development, testing, SLM activities, etc.) for existing applications.

The Contractor shall also support requests for new applications and the evaluation/assessment of third-party software. These activities involve extremely detailed levels of work and coordination in order to properly execute while adhering to the required ICE System Lifecycle Methodology.

A pool of specific skill sets experienced in performing the steps necessary to deploy an application is also necessary.

In addition to the typical steps associated with the deployment of an application there will be ad-hoc data calls and task/project related reporting requests that the contractor will be required to provide support on as necessary.

The Contractor shall assist ICE with the planning and migration of the ICECT to the DHS SharePoint COE.

The Contractor shall prepare and present white papers and progress reports for management using project management applications to analyze costs, schedules, and technical performance of the work.

The Contractor shall coordinate among the task leaders, project managers, and Government organizations to develop integrated project schedules across multiple teams working on engineering activities.

The Contractor shall stay abreast of emerging technologies and shall provide the technical expertise and support identifying, coordinating and implementing new technologies into the ICECT environment.

The ICECT Contingency Plan will be reviewed and tested on an annual basis, as required by DHS of all IT systems. Testing is done through coordination with the appropriate contractor security testing personnel. Once fully deployed, the ICECT Contingency Plan will be tested and validated, and results will be uploaded into Trusted Agent FISMA (TAF).

DHS/ICE requires that all IT Contingency Plans be exercised annually. Backup and restoration procedures, as well as other routine contingency-related matters, are part of the annual test exercise.

Contract performance shall be coordinated by Ice’s Office of the Chief Information Officer (OCIO), Systems Development Division, Administrative Systems Branch.

C-5.2 Special Projects (Optional) Special Projects in this SOW are specifically funded by the Congress, Office of Management and Budget (OMB), or DHS. The work activities, assignments, or projects may be related to other CLINS within this SOW and this Task Areas. All work activities, assignments, or projects under the special projects must be tracked, monitored, and invoiced separately.

C-5.2.1 Smart Mobile Collaborative Application Development

This optional task incorporates the use of next generation mobile computing technologies to expand on the collaborative functionality currently in use within the ICECT. This task will include, but not be limited to, the evaluation and recommendation on appropriate implementation of Smart Collaborative technologies; Utilization of Smart collaborative technologies to develop business-2-employee (B2E) application(s) that will be deliverable to mobile handheld devices. These applications may be hosted within the ICECT GSS or the ICE Websphere Environment and carry the potential for requirements that could expand computing resources within the environment these technologies are ultimately hosted. Any development activities performed under this option will adhere to the ICE System Lifecycle methodology.

C-5.2.2 Task Management System (TMS) Support

Contractor shall provide development and operational support for the ICE implementation of the Handysoft BizFlow COTS software, internally renamed OCIO Task Management System (TMS). BizFlow is a web-based Business Process Management (BPM) solution that seamlessly automates and integrates ad-hoc tasks with structured processes to enable assignment and routing of tasks / documents throughout the organization to drive visibility, control and productivity across all tasks within an organization. This application will be used to manage the receipt, creation, distribution, tracking, archival, and disposition of tasks/assignments across the OCIO organization. BizFlow includes an adaptor that integrates with SharePoint, which will be used as the user interface via webparts and as a document and version control repository.

Contractor support shall provide support in various aspects of the development of requirements, documentation, development of custom workflows and forms, development of related reports, operations, training and overall support of the TMS application to various ICE Programs. Any development activities performed under this option will adhere to the ICE System Lifecycle methodology.

SECTION D: PACKAGING AND MARKING

THIS PAGE WAS INTENTIONALLY LEFT BLANK

SECTION E: INSPECTION AND ACCEPTANCE

E-1 52.246-4 INSPECTION OF SERVICES—FIXED-PRICE (1996)

(a) Definition. “Services,” as used in this clause, includes services performed, workmanship, and material furnished or utilized in the performance of services.

(b) The Contractor shall provide and maintain an inspection system acceptable to the Government covering the services under this contract. Complete records of all inspection work performed by the Contractor shall be maintained and made available to the Government during contract performance and for as long afterwards as the contract requires.

(c) The Government has the right to inspect and test all services called for by the contract, to the extent practicable at all times and places during the term of the contract. The Government shall perform inspections and tests in a manner that will not unduly delay the work.

(d) If the Government performs inspections or tests on the premises of the Contractor or a subcontractor, the Contractor shall furnish, and shall require subcontractors to furnish, at no increase in contract price, all reasonable facilities and assistance for the safe and convenient performance of these duties.

(e) If any of the services do not conform with contract requirements, the Government may require the Contractor to perform the services again in conformity with contract requirements, at no increase in contract amount. When the defects in services cannot be corrected by reperformance, the Government may—

(1) Require the Contractor to take necessary action to ensure that future performance conforms to contract requirements; and

(2) Reduce the contract price to reflect the reduced value of the services performed.

(f) If the Contractor fails to promptly perform the services again or to take the necessary action to ensure future performance in conformity with contract requirements, the Government may—

(1) By contract or otherwise, perform the services and charge to the Contractor any cost incurred by the Government that is directly related to the performance of such service; or

(2) Terminate the contract for default.

(End of clause)

E-2 52.246-5 INSPECTION OF SERVICES—COST-REIMBURSEMENT (APR 1984)

(a) Definition. “Services,” as used in this clause, includes services performed, workmanship, and material furnished or used in performing services.

(b) The Contractor shall provide and maintain an inspection system acceptable to the Government covering the services under this contract. Complete records of all inspection work performed by the Contractor shall be maintained and made available to the Government during contract performance and for as long afterwards as the contract requires.

(c) The Government has the right to inspect and test all services called for by the contract, to the extent practicable at all places and times during the term of the contract. The Government shall perform inspections and tests in a manner that will not unduly delay the work.

(d) If any of the services performed do not conform with contract requirements, the Government may require the Contractor to perform the services again in conformity with contract requirements, for no additional fee. When the defects in services cannot be corrected by reperformance, the Government may—

(1) Require the Contractor to take necessary action to ensure that future performance conforms to contract requirements; and

(2) Reduce any fee payable under the contract to reflect the reduced value of the services performed.

(e) If the Contractor fails to promptly perform the services again or take the action necessary to ensure future performance in conformity with contract requirements, the Government may—

(1) By contract or otherwise, perform the services and reduce any fee payable by an amount that is equitable under the circumstances; or

(2) Terminate the contract for default.

SECTION F: DELIVERIES OR PERFORMANCE

F-1 .0 DELIVERABLES AND DELIVERY SCHEDULE

F-1.1 Deliverables and Delivery Schedule

The deliverables identified below are the minimum required deliverables, and additional deliverables may be required by individual task order. The Contractor shall provide deliverables associated with the work project, assignments, and activities by electronic delivery to the Contracting Officer’s Technical Representative (COTR’s)e-mail address using Microsoft Office 2003 or newer file formats.

F-1.1.1 Deliverable Number 1: Task Area Weekly/Monthly Report

The Contractor shall provide separate weekly and cumulative monthly status reports for each Subtask listed in the Statement of Work. The status report shall include accomplishments, status of ongoing activities, management issues, recommendations for problem resolution, and upcoming activities. The status report shall identify any completed travel and projects and provide planned travel and resources required for the next 30 days (see Deliverable Matrix).

The Contractor shall provide the Progress Reports to the ICE Task Manager and COTR and the reports shall include but is not limited to significant accomplishments and/or issues. Progress Reports shall include, at a minimum, the following topics in the order indicated, with a detailed explanation of issues:

· Title of project

· Associated CLINs

· Date Assigned

· Projected Completion Date

· Assigned by

· Reporting period

· Progress of project during the reporting period

· Identification of significant accomplishments or issues noted

· Planned solutions of issues, including risks to cost, schedule or performance elements of the task order

· Schedule - percent or degree completed by task to date, critical path analysis, ability to meet contract schedule, reasons for slippage, and path to recovery

· Cost - analysis of actual costs incurred in relation to budget and progress to date, burn rates, and cost estimate to complete project within budget.

· Other items as required (e.g., trip reports, meeting minutes, etc.).

F-1.1.2 Deliverable Number 2: Quarterly GFP Inventory Reports

The Contractor shall provide the inventory listing to the COTR in electronic format. This listing shall also include all ODC pending and/or committed. The format shall be Microsoft Excel compatible (see deliverable matrix).

The Contractor shall maintain the asset management systems by the ICE Task Manager in compliance with the 98% accuracy rate set forth by ICE. The Contractor shall provide weekly inventory reports to the ICE Task Manager. The Contractor shall provide written notification within 24 hours to the ICE Task Manager and COTR on any and all issues/concerns regarding inventory control.

F-1.1.3 Deliverable Number 3: Monthly ODC Listing

The Contactor shall provide the COTR a monthly ODC listing of all the ODCs for the month. This shall included but is not limited to the task area, work number, cost and work status. The listing shall be provided to the COTR in electronic format on the close of business (COB) of the second Monday of each Month. The format must be Microsoft Excel compatible (see deliverable matrix).

F-1.1.4 Deliverable Number 4: Quality Control Plan (QCP)

The Contractor shall provide a QCP for this Task Area. The QCP shall provide details of how the contractor intends to perform quality control checks, the process for tracking issues, communication strategy, and the quality control measures for all areas and responsibilities of this Task Area to include but not limited to all deliverables, all CLINs and work activities, assignments, and projects. The Contractor shall be prepared to address COTR concerns and requirements as well to include the QCP Report schedule and due date.

The Contractor shall provide the draft QCP to the COTR within 15 working days of award for the Government to review. When the COTR provides the comments back to the Contractor the Contractor shall incorporate the comments and provide the final QCP to the COTR and CO within 10 working days.

F-1.1.5 Deliverable Number 5: Monthly QCP Report

The Contractor shall provide the COTR a copy of the monthly QCP in electronic format (as needed). The format shall be Microsoft Excel compatible.

F-1.1.6 Deliverable Number 6: Security Report

The Contractor shall provide the COTR the security report as required by the COTR.

F-1.1.7 Deliverable Number 7: Employee Listing

The Contractor shall provide a monthly listing of all contractor staff to include Subcontractors. This report shall also include the hours used versus hours projected by CLIN, position, and employee, or as required by the COTR. The listing is due to the COTR by the seventh working day of the month. The schedule shall be included in the QCP. This listing shall include but not limited to the following fields:

Position

Position ID number

Task Area

Employment Status (Active, Terminated, Pending EOD, Released)

Status Date

Risk Level

Security Status (EOD, Terminated, Pending EOD, Released)

Work Location

F-1.1.8 Deliverable Number 8: Ad Hoc Reports

The Contractor shall provide, develop, maintain, update, store, and distribute ad-hoc reports as requested by the ICE Task Manager. Examples include: Design Reviews; User Acceptance Testing (UAT) Analysis Summary Reports; Technical Reference Model (TRM); SLM Technical Review Summaries; SLM Letters to the File; Document Assessment reports; Standards Profile; Standards Documentation; simulation and modeling analyses; technology patterns; configuration management operating procedures; and any deliverables associated with requirements management or domain planning. (See deliverable matrix)

F-1.1.9 Deliverable Number 9: Transition Plan

The Contractor shall be responsible for the transition of all technical activities by CLINs. The Contractor shall complete the technical transition within 60 days of being formally notified. The technical activities, which shall be included as part of the technical transition, consist of but are not limited to the transition plans for:

· Inventory and orderly transfer of all Government Furnished Equipment/Property (GFE/GFP), software and licenses.

· Transfer of documentation currently in process with Task Order award.

· Transfer of all Software coding in process with the Task Order award.

· Establishment of a facility for housing hardware, if any.

· Coordinating the body of work with the current Contractor and turnover of tasking, staffing, etc.

The Contractor’s transition plan shall be approved by the Government Task Manager and shall contain a milestone schedule of events and system turnovers. The plan shall address transitioning systems with no disruption in operational services. The Contractor shall provide the draft transition with their proposal and a revised transition plan within 90 working days of being formally notified of the Task Order. To ensure the necessary continuity of services and to maintain the current level of support, the OCIO ICE will retain services of the incumbent Contractor for the transition period, if required, to fully support the transition of CLIN requirements to the successor vendor by providing personnel and documentation required to facilitate a successful transition.

F-1.1.10 Deliverable Number 10: Technology Insertion Package (TIP)

The Contractor shall utilize a Microsoft Office SharePoint Server (SP) development environment consisting of hardware and software products compliant with HLS EA standards. If the Contractor SP development environment will not consist of hardware and software products found in the DHS Technology Reference Model (TRM), a TIP must be compiled and submitted for EA approval to the DHS EACOE (Enterprise Architecture Center of Excellence). The TIP consists of a number of technical documents necessary to obtain EA approval for the software and/or hardware that is not currently listed on the DHS TRM. The TIP must be submitted and approved PRIOR to purchase of the Contractor SP development environment’s hardware and software products.

F-1.1.11 Deliverable Number 11: Information Technology Security Plan

A Draft IT Security Plan is due with the Contractor’s proposal. The final IT Security Plan shall be submitted 30 days after contract award.

DELIVERABLE MATRIX

DEL. #
FREQ
DATE OF SUBMISSION
COPIES
ICE DISTRIBUTION
Task Area Weekly/Monthly Report
1
Weekly/

Monthly

15th of the following month
3 (electronic)
COTR

Task Manager

CO

Quarterly GFP Inventory Reports
2
Quarterly
15th working day of the quarter (i.e., January, April, July, and October)
2 (electronic)
COTR

Task Manager

Monthly ODC Listing
3
Monthly
COB of the second Monday of each Month
1 (electronic)
COTR
Quality Control Plan
4
With Proposal
With each Task Order Proposal
1
CO
Monthly QCP Report
5
As needed
Monthly
2

(electronic)

TM

COTR

Security

Report

6
weekly
COB every 3rd Wednesday
2
TM

COTR

Employee Listing
7
Monthly
Monthly
2
CO

COTR

Ad Hoc Reports
8
As Requested
When Requested
1(electronic)
COTR
Transition Plan
9
With proposal
Initial: with proposal

Task Order: Within 90 days of award

1(electronic)
CO
Technology Insertion Package
10
As needed
When requested
3(electronic)
Task Manager

COTR

DHS EACOE

IT Security Plan
11
With Proposal
A Draft IT Security Plan is due with the Contractor’s proposal. The final IT Security Plan shall be submitted 30 days after contract award.
3(electronic)
Task Manager

COTR

ICE Information Assurance Division

Additional deliverables may be established for specific task orders based on specific requirements.

F-1.2 Acceptance Criteria

ICE will accept or reject deliverables. If rejected, the Contractor shall make corrections as specified and resubmit the deliverable for review and approval. All deliverables are subject to the ICE Government Task Manager’s review and approval. The Contractor must obtain the Government’s Task Manager sign-off approval accepting the work. If a deliverable is rejected, the Contractor will have to make corrections as specified by the Government Task Manager and resubmit the deliverable for review and approval to the COTR and Government Task Manager. The Contractor shall also inform the COTR in writing within five (5) days of the rejection and shall identify what measures that have been put into place to reduce future rejection of deliverables.

F-2 PLACE OF PERFORMANCE

Work for each task order under this contract will be performed primarily at Contractor’s facilities. Frequent travel to DHS offices in the Washington, DC metropolitan area for meetings and briefings will be required. It is preferred that the Contractor’s operating facility should be within the Washington, DC metropolitan area for travel time to the DHS, ICE OCIO Office located at 801 I Street NW, Washington DC. Occasional travel to sites outside of the Washington, DC area is required in conjunction with the performance of contract project requirements.

The Contractor shall ensure that all supporting personnel are available during ICE core hours (9 a.m. – 3 p.m.). Normal operations must be carried on during an 8-hour period between the hours of 6:00 a.m. and 6:00 p.m., Monday through Friday. The Contractor shall provide support on an on-call basis after normal business hours. The Contractor must plan and have the capability to provide 24x7, 365 days a year critical security support to mitigate the risk of a Day Zero attack with minimal notice, not to exceed 2 hours.

F-3 PERIOD OF PERFORMANCE

A 12-month base period (which incorporates a 90 calendar day transition in period) plus four 12-month option periods.

Year
Period of Performance
Base Year
June 01, 2010 – May 31, 2011
Option Year 1
June 01, 2011 – May 31, 2012
Option Year 2
June 01, 2012 – May 31, 2013
Option Year 3
June 01, 2013 – May 31, 2014
Option Year 4
June 01, 2014 – May 31, 2015

SECTION G: CONTRACT ADMINISTRATION DATA

G-1 COMMITMENT OF GOVERNMENT TO AWARD A CONTRACT AND EXPENDITURE OF FUNDS

This solicitation does not commit the Government to award a contract. The Government reserves the right to reject any or all proposals. The Contracting Officer is the only individual who can legally commit the Government to the expenditure of public funds in connection with the proposed procurement.

G-2 TECHNICAL DIRECTION AND SURVEILLANCE

(a) Performance of the work under this contract shall be subject to the surveillance and written technical direction of the Contracting Officer's Technical Representative (COTR), who shall be specifically appointed by the Contracting Officer in writing. Technical direction is defined as a directive to the Contractor which approves approaches, solutions, designs, or refinements; fills in details or otherwise completes the general description of work of documentation items; shifts emphasis among work areas or tasks; or otherwise furnishes guidance to the Contractor. Technical direction includes the process of conducting inquiries, requesting studies, or transmitting information or advice by the COTR, regarding matters within the general tasks and requirements in Section C of this contract.

(b) The COTR does not have the authority to, and shall not, issue any technical direction which:

(1) constitutes an assignment of additional work outside the Performance Work Statement;

(2) Constitutes a change as defined in the contract clause entitled "Changes";

(3) In any manner causes an increase or decrease in the total estimated contract cost, the fixed fee (if any), or the time required for contract performance;

(4) Changes any of the expressed terms, conditions, or specifications of the contract; or

(5) Interferes with the Contractor's right to perform the specifications of the contract.

(c) All technical directions shall be issued in writing by the COTR via e-mail

(d) The Contractor shall proceed promptly with the performance of…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .