PWS_(final).docx

PERFORMANCE WORK STATEMENT (PWS)

CONTRACT VEHICLE: Multiple Award Schedule (MAS) 70, Information Technology 132-51

1.0 INTRODUCTION / BACKGROUND /OBJECTIVE / APPLICABLE DOCUMENTS

1.1.1 The Scope of the DEAMS Program includes administration of the Transportation Working Captial Fund and USAF General Fund. This initiative integrates disparate financial management systems into a single integrated system.

1.1.2. The DEAMS Program Strategy employs an incremental development approach, and focuses upon the rapid fielding of capability as follows:

Increment 1, Release 1: Deploys DEAMS functionality to Scott AFB, IL, and supporting Defense Finance and Accounting Service (DFAS) locations to enable Users to “use and learn” DEAMS and to validate the solution; and upon such validation, to deploy DEAMS to McConnell AFB and four additional Air Mobility Command non-Transportation Working Capital Fund (non-TWCF) bases. DEAMS will operate on the Global Command Support System-Air Force (GCSS-AF) or equivalent Government-furnished hosting environment.

Increment 1, Release 2: Deploys DEAMS to the remaining Air Mobility Command TWCF bases and MacDill AFB, FL.

Increment 1, Release 3: Upgrades DEAMS software to Oracle R-12 and retrofits existing sites.

Increment 1, Release 4: Deploys DEAMS to the U.S. Transportation Command (USTC) headquarters and the Army’s Surface Deployment and Distribution Command (SDDC) headquarters, both at Scott AFB, IL.

Increment 1, Release 5: Deploys DEAMS to remaining Air Force bases in the Continental U.S. (CONUS).

Increment 1, Release 6: Deploys DEAMS to Air Force bases in the European and Pacific theaters (PACAF and USAFE).

Increment 2, Release 1: Expands on the DEAMS solution to satisfy Government requirements and deploys the enhanced DEAMS solution to USAF installations in Air Force Space Command (AFSPC) and Air Force Materiel Command (AFMC).

Increment 2, Release 2: Expands on the DEAMS solution to satisfy Government requirements for Foreign Military Sales (FMS) and Contingency Operations.

The purpose of this Performance Work Statement (PWS) is to identify the tasks required to provide the required services and supplies in the Functional Program Office (FMO) transition from Fairview Heights, IL to Wright-Patterson AFB, OH. This requirement is to provide a comprehensive plan to assist the Government in maintaining current levels of test center services and transition these services to a Government/owned directed The DEAMS Program Strategy employs an incremental development approach, and focuses upon the rapid fielding of capability.

1.2. Background. Since the 1960s, the UASF has relied upon legacy systems that effectively prohibit Chief Financial Officer (CFO) Act compliance and clean audit opinions. In 2005, USTRANSCOM, USAF and DFAS entered into a partnership to replace these legacy accounting systems. In 2005, the Government selected the Oracle lli eBusiness Suite as the core Commercial-Off-The-Shelf (COTS) solution to meet the DEAMS Program goal. The Government subsequently contracted with a System Integrator (SI) for the Increment 1, Releases 1 & 2, to include the, Technology Development Phase of the DEAMS Program. The Government now seeks to select Designers for the Increment 1, Releases 3-6 efforts. In 2005, the Government also selected and contracted with Kearney & Company to provide Project Management and Financial Management Support Services. This effort included a range of services to support the blueprinting, configuration, and implementation of recommended financial solutions, and to provide efficient program management and financial management support.

This task order will require Testing and Integration services to include network administration support for functional testing of all assigned systems. This support will ensure all Independent Verification and Validation (IV&V) actions are completed to ensure Government authorized to operate (ATO) certification of this system as well as sustainment operations.

1.3. Objective. The objective of the resultant Task Order is to continue current hosting and maintaining the current DEAMS systems (test and production), and Sharepoint under the org domain and assist the government in identifying what hardware/software are required to be procured in transitioning/normalizing data to a .mil org. This includes ensuring the Government obtains DICAP, IATO and ATO certifications prior to transition to .mil domain.

1.4. Applicable Documents. The documents listed in Attachment A hereto shall be considered an integral part of the resultant Task Order.

2.0 TASK REQUIREMENTS

The Contractor shall support the tasks described below. The Government will issue to the Contractor written, project-specific task directives (Attachment B) to assign pre-defined tasks or otherwise describe special analyses and reports. Task directives will be signed and dated by an authorized Government representative and delivered to the Contractor representative responsible for managing the work.

Task Requirements include project planning and execution; pre-deployment, deployment, and post-deployment/sustainment support; and the development, preparation, submission, and maintenance of task activity documentation, as required. Some Task Requirements are intentionally duplicative within the categories of Pre-Deployment, Deployment and Post- Deployment/Sustainment to facilitate the Contractor’s development of a comprehensive and supportable Work Breakdown Structure

The following support services shall be provided at the level required to effectively and efficiently support the operations and management of this task IAW the PWS. Furthermore, these services will be transitioned to a government directed/owned environment.

NOTE: The contractor shall be responsible maintaining both a test and development systems utilized by contractors and Government personnel. The testing and development systems will be used by DEAMS personnel as granted permission by the Government and administered by the contractor until transition to the .mil environment.

2.1. Task Order Management Plan (TOMP). The Contractor shall provide a TOMP that describes the technical approach, organizational resources, work breakdown structure, transition project plan and management controls proposed for task performance. The plan shall be provided to the Government 30 days after award and updated quarterly. This document will always be available for Government Review at all times.

2.2 Maintain Current Hosting of DEAMS systems. Test and support environments, as well as the DEAMS transition services to include the following:

2.2.1 Oracle Financial Software Support and Management

Provide expertise and knowledgeable support services to administer and transition Oracle Financials in a testing and development environment.

Provide testing and evaluation of software requirements by assigned personnel in current DEAMS environment.

Provide assistance and migration activities to include identifying all software, software scripts or other items to transition from current DEAMS SharePoint site to the new Government SharePoint site including transition of all permissions. The contractor shall provide written transition procedures.

Support functional testing plans and procedures throughout the development, integration, and sustainment efforts. The contractor shall provide written testing plans.

Provide systems for testing and development and grant access to both government and contractor personnel when authorized by the government. The contractor shall provide written access procedures.

Provide support to end users via toll-free and the defense services network for access of testing and development systems.

Provide installation procedures for the DEAMS Oracle software and provide Systems Configuration Management Plan within 30 days after award and update as required.

Transition Procedures

2.2.2 Web Site Development

Provide expertise and knowledgeable support services to fully implement and support program web site SharePoint for the testing and integration services. The contractor shall provide written procedures.

Provide equipment and services to support this site, along with routine maintenance and page development efforts. The contractor shall provide written maintenance procedures.

Provide two SQL database spaces for development, integration, and sustainment efforts in the data conversion and cleansing areas.

Provide web-site installation procedures, a web-site design and system configuration management plan within 30 days after award and update as required.

Transition procedures

2.2.3 Network Systems Support Services

Provide systems engineering and network connectivity support for Virtual Private Networks, File Transfer Protocol and Secure File Transfer Protocol for all systems and other support systems that the government determines necessary to support the DEAMS effort. The contractor shall provide written procedures.

Provide user data stored on network drives using physical media (CD/DVD).

Provide administrative services for all users of shared data stores and network drives to include migration activities to external data sources. The contractor shall provide written procedures.

Conduct security reviews to ensure secure and reliable communications are maintained. Provide Network Security Awareness and Results documenting the actual summary results maintained by the contractor for Government review.

Ensure assigned devices and associated network equipment is maintained and operational with minimum uptime of 95%. The contractor shall provide 48 hours notice to the Government for approval prior for maintenance. The Government understands that emergency maintenance to resolve down issues for Government directed changes take precedent and supersedes 48 hour notice.

Conduct testing and verify current contractor communication lines meet acceptable commercial standards.

Provide network security diagrams, and Communication and Network Connectivity Diagrams of the current system to the government. Changes to the configuration shall be documented and the network diagram updates provided to the government. The contractor shall include this information in the transition plan.

Identification of all current hardware devices and locations required to maintain the system. The contractor shall identify and document all devices and locations of equipment that directly support the DEAMS hosting service and requirements identified to support this task with services.

Transition procedures

2.2.4. Backup and Recovery. The contractor shall facilitate regular backups (full and incremental) of all data residing upon contractor owned/managed hardware that supports this task for DEAMS hosting. The contractor shall document servers/volumes/folders backed up and perform a monthly validation check to ensure backups can be restored. The contractor shall maintain a log to document actions taken to perform weekly incremental backup and full monthly backup. Backup and recovery test shall be reported quarterly to Government POC leadership as a contract deliverable. The contractor shall include these procedures in the transition plan.

2.2.5 Disaster Recovery Procedures. The contractor shall develop a backup and restoration plan for all testing data. This plan should address the restoration of services should hardware failure occur. The Government understands that testing data does not require the same level of redundancy as actual live data, but the plan should address relevantly quick response and restoration of the services in this contract. A copy of the plan shall be provided to the Government within 60 calendar days of award and updated quarterly. The contractor shall include this in the transition plan.

2.2.6 System Availability/Administration. The contractor shall maintain the AF DEAMS site at a minimum of 95% availability per month for the life of the contract (exclusive of Air Force system downtime) and shall have less than a 1% log-in failure rate due to communication issues. The contractor shall provide a monthly report identifying downtime, system errors related to the DEAMS hosting environment. The Government understands that the internal Government communication problems cannot be identified and corrected by the contractor; but the contractor shall identify and suspected AF communication issue in each monthly report. The contractor shall track, perform, and report trend analysis for unscheduled disruptions and system failures, at a minimum by interface, port, location and resources at the quarterly Management meeting.

The contractor shall manage their server resources, procedures, and performance. This includes server startup, shutdown, diagnostics, and data integrity management for all elements of the AF DEAMS system.

All routine maintenance (e.g. weekly software or hardware updates) shall occur between Friday, 2200 Eastern – Saturday, 0800 Eastern or Saturday 2200 Eastern – Sunday, 0800 Eastern. This shall ensure that the system is available to our global users during normal working hours.

At a minimum, the contractor shall post a notice on each DEAMS host site regarding scheduled interruptions at least two (2) weeks in advance of interruption unless Government approved. Users should be notified of the upcoming service interruption as part of the login process. The Government shall also be notified by the contractor via the Government provided e-mail within the same timeframe.

The contractor shall report to the Government all unscheduled disruption of service within 4 hours of occurrence or the next duty day if outside of normal duty hours. Normal duty hours are Monday through Friday, 0715-1615 Central, excluding Federal holidays.

The contractor shall include system administration procedures in the transition plan.

2.3 System Data Security Design. The contractor shall ensure that the current .org domain follows the guidelines below:

Protect DCPS data from unauthorized access

Provide a secure data transmission capability (e.g., secure socket layer enabled web site) for all data transmitted to and from the host site.

Security practices shall ensure system security certification and accreditation through the existing Department of Defense certification and accreditation process, currently the Department of Defense Information Assurance Certification and Accreditation Process (DIACAP). The contractor shall develop, prepare, route, and respond to inquiries in processing the accreditation package. The contractor shall assist Government personnel in an expedited manner to obtain approval to operate prior to being granted full operational capability.

DIACAP Requirements: The contractor shall complete and maintain all documentation required for compliance with the DIACAP (or other replacement accreditation). Certification and accreditation is required to operate at all intervals determined by DoD 8500.2, Information Assurance Implementation, February 6, 2003.

The contractor shall comply with all DIACAP documentation and performance requirements. Work shall be completed according to policy, processes, and procedures contained in DoDI 8510.01, DoD Information Assurance Certification and Accreditation Process (DIACAP), and AFI 33-210, Air Force Certification and Accreditation (C&A) Program (AFCAP, or other applicable regulation/instruction). The contractor shall document and test information assurance (IA) controls in accordance with applicable instructions, i.e., AFI 33-200, Information Assurance Management, para 3.16 IA Controls.

The contractor shall produce an Interim Authority to Operate (IATO) request package and submit it to the Government in accordance with DoDI 8500.2, Information Assurance Implementation, February 6, 2003, AFI 33-200, Information Assurance (IA Management), December 23, 2008 and AFI 33-210, Air Force Certification and Accreditation (CA) Program (AFCAP) Information, December 23, 2008. Additional reference material shall be used as required for compliance with these publications. The Government will ensure access to the eMass system. The contractor will commence the DICAP process upon contract award. The contractor will provide (a draft or initial) status report to the government on the required steps, timelines, and identify any other requirements 30 days after award, and every 15 days until complete. The government will provide necessary access and coordination of government personnel to ensure that this status update is complete and detailed. The contractor shall maintain all documentation on the .mil environment for the DIACAP process on DEAMS to ensure all updates and major system changes are reflected. The IATO package shall be prepared using Microsoft Office suite tools and submitted within the government established timeframes.

DIACAP package Authority to Operate (ATO) shall be submitted through the Government to the system’s Certifying Authority as soon as all relevant requirements are satisfied in the eMASS system. The contractor will ensure all documentation is maintained on the .mil environment through the submission, IATO and ATO process. The contractor shall ensure this is included in the Transition Plan. The contractor will ensure that the required documentation is submitted within the established timeframes as per the DICAP procedures.

package and any security issues in the transition plan.

2.3.1 System Data Security. The contractor shall manage security for the system as specified in paragraph 2.3 above and conduct Authority to Operate (ATO) maintenance as required. After approval is granted, the system shall be maintained at a level to maintain a current and valid DIACAP (or other replacement accreditation process) certification.

2.4. Software - License Agreement Inventory. The contractor shall maintain an existing electronic spreadsheet inventory of software products provided and authorized by the Government in use to support the DEAMS systems. Inventory documents shall be updated no later than 30 calendar days of any change. The contractor shall include this information in the transition plan.

2.5 Equipment Inventory. The contractor shall maintain inventory of all existing equipment to support the DEAMS systems. This equipment may include: servers, workstations, printers, laptops, and monitors, where applicable. The contractor shall be responsible for maintaining IT information in accordance with AFI 33-112. The contractor shall perform and maintain inventory in accordance with local IT policy. A copy of the semi-annual inventory shall be submitted as a deliverable.

2.6 Transition form .org to .mil domain

2.6.1 Transition existing DEAMS .org to a Government Directed Environment .mil includes but not limited to:

2.6.2 The contractor shall support and provide a transition plan to a Government Directed Site. This transition will include 5 instances of Oracle Financial software to validate patches and test processes of various aspects of the DEAMS Solution (CIE, Pre-Production, Production, R12, and Conversion Instance).

2.6.3 The contractor shall support and transition of current Sharepoint to a Government Directed Site with access and appropriate security levels to include 2 SQL Databases spacees for conversion and data cleansing by all DEAM personnel.

2.6.4 Provide certification and accreditation (DIACAP) support to migrate current commercial hosted SharePoint to a government environment.

2.6.5 Provide network security testing and certification support as required to meet acceptable security directives and common commercial security requirements, DICAP. This may include preparing the DICAP required documentation.

2.6.6 The contractor shall support the Secure File Transfer Protocol (SFTP) service to a Government Directed Site to transfer DCPDS files and other data files after data field configuration to ensure accurate processing into DEAMS. The contractor will document in writing the transition procedures and provide as a deliverable.

2.6.7 The contractor shall provide and transition existing data to a Government Directed Virtual Private Network (VPN). The contractor shall provide existing system information to ensure new .mil domain will have secure access to the instances on .org domain. This will ensure access by Government personnel to the Oracle on Demand instances prior to transition of data. The contractor shall document in writing the transition procedures and provide as a deliverable.

2.6.8 The contractor shall provide transition support for network administration, system engineering, and desktop support services, to ensure configuration and transition of data to a Government or .mil domain. The contractor shall document in writing transition procedures and provide as a deliverable.

2.6.9 The contractor shall identify equipment test and integration requirements to transition to a Government Directed Site. This transition includes security management for testing and integration services, dedicated project server use for Government and contractor personnel.

2.7 Transition Plans. The Contractor shall develop and deliver to the Government a transition plan. The Contractor shall develop this Transition Plans with a view to transitioning from the existing .org to the .mil domain while maintaining program integrity and minimizing the impact of such transitions upon the DEAMS Program. The Contractor shall take all commercially reasonable measures necessary to achieve a successful transition from the existing domain the .mil domain.

2.7.1. Phase-in Plan: The Contractor shall develop and deliver to the Government a plan to complete the transition from the .org to the .mil environment. Such Phase-in Plan shall present a clear understanding of the phase-in tasks required as well as identification of hardware, software and other communication requirements need to support the transition. As described in the above paragraphs and identify the issues likely to arise in completing this task, and the Contractor’s recommendation to resolve such issues. The Phase-in Plan shall include a clear and feasible strategy for delivering services required within the periods specified by the Plan and shall include a detailed plan-of-action and milestones to transition the functions identified in this PWS. The Phase-in Plan shall include, at a minimum:

Development and submission of required deliverables as described in Section 2 of the PWS;

Interface with the Government during phase-in, to include meetings or status reports, as required;

Approach to maintaining quality and minimizing disruption during phase-in; and Development and dissemination of written operating instructions, procedures, and control directives.

2.7.2 Phase-out Plan: The Contractor shall submit to the Government a Phase-out Plan sixty (60) calendar days prior to the expiration or termination of this Task Order. The Phase-out Plan shall include at a minimum:

Plans to retain staffing levels necessary to maintain required through the day of Task Order expiration or termination; and

Plans to perform a physical inventory of any Government Furnished Equipment, including the certification and reconciliation of material-on-hand.

2.8 On-Call Support/Emergency Support/Contingency Support. Contractor personnel shall augment government employees to provide for "Non-Duty Support Hours" on 7 days a week, 24 hours per day basis. On-call support shall be required for all services provided here to support the DEAMS effort. Once the contractor employee is contacted, the contractor shall have 4 hours to respond to the emergency and shall provide any and all necessary support to resolve the problem. This contractor employee is considered to be in an "On-Call" status - that is, the contractor is off-duty and conducting normal activities. The solution may be implemented outside the normal duty station and the individual may be required to report for duty as required.

Contractor personnel who are on an "On-Call status" shall be available for immediate action and shall be prepared to provide support upon notification. These personnel shall be required to carry a pager or cell phone furnished by the Contractor.

3.0 Requirements/Expertise and Experience. The contractor shall be an Oracle Partner with Plantinum Level certification. A copy of this certification must be provided with vendor response.

Expertise/Experience: The contractor’s quote shall include the resumes of the proposed key staffing, documenting personnel expertise and experience available to support this requirement. Documented expertise and experience and the ability to demonstrate knowledge/skills/abilities with the items (i.e. technologies, organizations, systems, processes, etc.) listed below is highly desirable for the contractor staffing proposed to complete the task activities.

While each individual contractor employee may not possess expertise and experience in each area identified in the subsequent paragraphs, the Government requires that the overall contractor staff possess the aggregate skills, expertise, and experience in each of the areas identified to successfully complete all task requirements. All contractor personnel shall be capable of working independently

Familiarity with the Air Force Material Command Familiarity with DoD and United States Air Force Financial Management Functional familiarity with Oracle Federal Financials Technical familiarity with Oracle Federal Financials Experience with Oracle Federal Financial audit capabilities Familiarity with Air Force legacy financial management systems and processes Expertise in operational Air Force Financial Data Structure Expertise in operational Air Force Data Panel Expertise in operational Air Force Data Dictionary

4.0 Quality Assurance and Quality Control

4.1 Contractor Quality Control Plan

The Contractor shall be responsible for quality assurance and quality control of all services performed and all items delivered under this contract/order.

The Contractor shall prepare and maintain a QCP as a guide for implementing quality assurance and quality control procedures. The Contractor shall submit the QCP to the Government for information and acceptance. The Government has the right to require revision of the Contractor’s QCP should its implementation fail to control the quality of items and/or services delivered under this contract.

The QCP shall include an explanation of the processes and procedures for ensuring satisfactory performance and delivery of quality items and/or services. Additionally, as a minimum, the QCP shall include the following items.

· A description of the inspection system to cover all major services and deliverables. The description shall include specifics as to the areas to be inspected on both a scheduled and unscheduled basis, frequency of inspections, and the title of inspectors.

· A description of the methods to be used for identifying and preventing defects in the quality of service performed.

· A description of the records to be kept to document inspections and corrective or preventative actions taken.

· All records of inspections performed shall be retained and made available to the Government upon request throughout the task order performance period, and for the period after task order completion, until final settlement of any claims under this task order.

The Contractor shall implement a quality program based on its QCP. In compliance with the QCP, the Contractor shall manage, surveil, assess, improve and/or correct contract performance to ensure the quality of the services and deliverable products, as a minimum, meet the level of quality required by the Government Functional Managers or Technical Representatives.

In the event of quality concerns, identified by the Government, the Contractor shall immediately take corrective action in response to Government required changes to the QCP.

The QCP shall be delivered to the Government as stipulated in the Delivery Schedule, see Paragraph 5.0 of this PWS.

4.2 Government Quality Assurance Surveillance Plan (QASP). The Government will evaluate Contractor performance under this contract / delivery order in accordance with the attached Quality Assurance Surveillance Plan (QASP). The purpose of this evaluation is to ensure that Contractor performance meets Government requirements. The Government reserves the unilateral right to change the QASP at anytime during contract performance provided the changes are communicated to the Contractor by the effective date of the change. The Performance Standards (provided in the Performance Criteria Matrix) and Surveillance Objectives, Measures, and Expectations are included as attachments to the QASP.

5.0 DELIVERABLES

Table 1 summarizes the deliverables and due dates prescribed under this section.

Reporting The contractor shall create and maintain reports as outlined in the deliverables section of this PWS. Reports must be delivered in electronic format commonly used in office environments throughout the Air Force. Examples of this software standard are (Excel, MS Word, PowerPoint, etc.). All reports must be delivered by the times and frequency indicated. Reports are to be completed in a professional and accurate way to minimize misunderstanding and confusion.

5.1. Contractor Submission. The Contractor shall submit Task Order Deliverables to the Government under cover of a letter describing the Deliverable and written on the Contractor’s letterhead. The Contractor shall transmit Deliverable and cover letter electronically through the GSA web-based procurement system, Information Technology Solutions Shop (ITSS), and to any other destination, required by the Government’s authorized representative. The Contractor shall also provide to the Government hard copies of Deliverable and cover letter, as required. The Contractor shall produce deliverables using software tools and versions, as required.

5.2. Government Review. Within 10 business days of receipt of a Deliverable under this Task Order, the Government will review each Deliverable (or any resubmission thereof) and accept or reject the Deliverable in writing, with or without comment. Should the Government reject the Deliverable with comment, the Contractor shall, within 5 business days of receipt of such comment, resubmit the Deliverable amended in accordance with comments, or provide a rationale for declining to do so.

5.3. Deliverable Rights. All documentation, including but not limited to, documented processes, procedures, software tools and applications, test materials, text, notes , electronic files, data, new capabilities or modification of existing applications, source code and records generated, modified, acquired or produced by the Contractor under this Task Order (Produced Materials) shall become the property of the Government. The Government shall have unlimited rights to all Produced Materials, including the right to modify, distribute and publish same. The Contractor shall deliver electronic copies of all Produced Materials to the Government quarterly and upon expiration or termination this Task Order by either party for any reason.

5.4. Monthly Invoice. The contractor shall provide a monthly invoice to be submitted simultaneously with the monthly status report. The invoice shall include but not be limited to:

· Supporting documentation for travel costs. Invoices including travel costs shall include supporting documentation as required by the Federal Travel Regulation (FTR) (receipts for all costs $75.00 or greater). Invoice submissions including travel costs shall include completed travel expense sheets (i.e. travel voucher) for each trip for each employee. All travel costs shall be compiled into the Government provided travel expense sheet (Attachment C or approved contractor trip report/voucher). The travel expense sheet shall be submitted with the invoice.

5.5 Monthly Status Report. The Contractor shall submit to the Government a Monthly Status Report of services performed (and to be performed) under this Task Order, concurrent with the Monthly Invoice. Monthly Status Reports shall include the status of tasks, schedules, deliverables, current and cumulative task funding (including direct labor costs and travel costs), outstanding issues, and proposals to resolve these issues. The “Status of Tasks” portion of the Monthly Status Report shall include a summary description and schedule of tasks completed during the reporting period, tasks currently underway but incomplete and tasks assigned with out-of-reporting-period delivery dates.

A staffing report shall be integrated into the monthly status report and include, but is not limited to, the following:

• Include the Contract number and Project Number.

• Identify the COTR assigned.

• Include reporting period.

• Include the client's agency and location.

• Include the date the Contract was issued.

• Include the following:

· Services Provided

· Personnel assigned and their skill levels

· Each report must contain the following statement:

• "I certify to the best of my knowledge and belief that the above identified employee(s) provided the firm-fixed price services as identified." The signature and date of the (Contractor) Program Manager or his/her designee must directly follow this statement.

The Contractor shall deliver the data items listed in the table, below.

Other Reporting Requirements. In addition to the Deliverables identified above, the Contractor shall:

· Report to the COTR as soon as possible any issue that may potentially affect performance under this Task Order;

· Document oral reports with written reports within 24 hours, when directed by the COTR; and

· Provide, in writing to the COTR, a report of any discussion with the Government that may potentially affect the terms or conditions of this Task Order, or may otherwise be construed as proposing amendments to or additional requirements under this Task Order.

5.6 The Contractor shall remove all Contractor-owned property from Government facilities by close of business on the last day of the Task Order. The Contractor shall coordinate phase-out activities with the incoming contractor to effect smooth and orderly transition at the end of the Task Order period. With the exception of information technology training, which will be provided by the Government, the Contractor shall provide on-the-job training and knowledge transfer (including application access, database access, functional designs, technical designs, architectural documentation, etc.) to the incoming contractor, as required.

5.7 Provide training. The contractor shall provide 2 two hour training sessions for four Government/contractor personnel during the transition out phase. This training shall include software/hardware installation, backup and recovery procedures, web site installation procedures; network installation procedures and system administration. The contractor shall provide training manuals, handouts, and job aids in both electronic and hard copy format.

6.0 PERFORMANCE

The Contractor shall not perform any work beyond the scope, terms, conditions or requirements of this Task Order without the express, written approval of the CO.

6.1. Great Lakes Task Order. The selected Contractor shall perform all work in accordance with the General Services Administration (GSA), Federal Acquisition Service, Great Lakes Region, Task Order. Government certification that the Contractor has provided satisfactory services will be contingent upon the Contractor performing in accordance with the terms and conditions of the referenced Contract and Task Order, this PWS, the approved technical and cost quotes, and any amendments. Representatives of the DEAMS Functional Management Office (FMO), GSA and the Contractor shall meet as requested by the FMO, at a place and time to be determined by the FMO.

6.2. Kickoff Meeting. Within 7 calendar days of Task Order award, the Contractor shall initiate work on this Task Order by meeting with FMO and GSA representatives to ensure a common understanding of the requirements, expectations, and ultimate deliverables under this Task Order. The Contractor shall discuss its understanding of the project and review any background information and materials provided by the FMO. The Contractor shall also discuss the scope of work, the deliverables to be produced, the proposed organization of work efforts, and the conduct of the project generally; any assumptions made, and anticipated results. The Contractor shall make a concerted effort to gain a thorough understanding of the FMO’s expectations of performance under this Task Order. Nothing discussed in this or in any subsequent meeting, however shall be construed as adding, deleting, or modifying any term, condition, requirement, specification or delivery date under this Task Order.

6.3. Period of Performance. The Base Period of Performance under this Task Order shall be 01 December 12 through 30 November 13. The Contractor’s quote shall also include two six month option periods as identified below. The Option Period may be exercise at the Government’s discretion.

Base Period: 01 December 12 through 30 November 13 Six Month Option: 01 December 13 through 31 May 14 Six Month Option: 01 June 14 through 30 November 14

6.4 Place of Performance. The place of performance for this task order will be contractor site.

6.5. Travel. The Contractor shall also perform non-local travel in support of this Task Order, as required by the Government. The COTR, or his appointed representative, shall have sole authority to approve non-local travel requests necessary to support Task Order performance. Travel required under this Task Order may include CONUS or OCONUS travel. Not later than 5 business days prior to the Contractor’s estimated dated of departure, the Contractor shall submit to the COTR, via ITSS, cost estimates for such travel. Federal Travel Regulations apply. The Contractor shall be responsible for all travel arrangements including airline, hotel, and rental car reservations. The Contractor shall make every commercially reasonable effort to schedule travel far enough in advances to take advantage of reduced airfares. The Contractor shall stay in Government furnished lodging, if available. The contractor shall complete attachment C travel expense sheet and include with monthly invoice.

6.5.1. Hours of Work. The Contractor shall provide on-site support during standard business hours, generally 0700 to 1600 CT (0800 to 1700 ET). In the normal course, Contractor workweeks shall not exceed 40 hours, Monday through Friday. Contractor personnel shall observe all Federal Holidays. The Contractor shall also support the Government during non-standard or additional duty hours, as required. Non-standard and additional duty hours shall be coordinated with the COTR.

6.6. Personnel Retention. The contractor quote shall describe a thorough and sound program management approach and organizational construct to hire, train, and retain personnel. The Contractor shall make every commercially reasonable effort to retain personnel in order to ensure the continuity of services performed under this Task Order. The Contractor shall make every commercially reasonable effort to ensure continuity of operations during periods of personnel turnover and absences longer than one week in duration.

6.6.1. Personnel Turnover. If it should become necessary to substitute or replace personnel, the Contractor shall notify the COTR in writing of any intent to substitute or replace personnel as soon as the Contractor becomes aware of such intent, and shall submit to the COTR through ITSS the resume(s) of proposed Replacement Candidates within 14 calendar days of such notification for Government acceptance. Contractor personnel shall not be assigned to support task activities prior to Government acceptance and contractor personnel resumes submitted via ITSS.

6.6.2. Availability. Once the Government has approved the Replacement Candidate resume, the candidate shall be available to begin work under this Task Order within 14 calendar days.

7.0 Government Furnished Equipment, Information and ACCESS. The Government will provide the following resources to the Contractor:

General reference documentation necessary to accomplish the Task Order requirements described above, including master plans, strategic plans, databases, reports, data, drawings; and

Photo identification for each Contractor employee, including a Common Access Card and Restricted Area Badge (as required), where the Contractor complies with all security requirements necessary to obtain such identification.

Government-furnished equipment, information and access cards shall remain the property of the Government.

The Contractor shall return all Government furnished equipment, information and access cards to the government at the expiration or termination of this Task Order.

7.1 Contractor Furnished Equipment. The contractor shall provide:

A page for the on-call support.

8.0 SECURITY

8.1 General security information. This is a classified contract because selected positions require an eligibility determination of SECRET. The persons filling these positions shall have a favorable eligibility determination based on a National Agency Check with Local Agency Checks and Credit Checks (NACLC). These persons will be the only persons allowed access to information classified at the SECRET or CONFIDENTIAL level. No other contractor employees shall access classified information at any time regardless if they have an eligibility determination of SECRET or not. The majority of the daily work associated with this PWS is at the UNCLASSIFIED level. The remaining contractor employees assigned to support of this Task Order shall obtain a National Agency Check with written Inquires background investigation (NACI), except where the employees already hold a current US Government security clearance. The National Agency Check shall be completed and obtained at the contractor’s expense and is the required background investigation for issuance of a DoD Common Access Card (CAC).

8.2 Personnel Security Requirements. The contractor’s, subcontractors, and/or partner’s personnel performing services under this contract, shall be citizens of the United States of America. No dual citizens will be authorized interim or final security clearance determinations. US Citizens who have foreign government (expired or active) passports will not be able to hold interim or final security clearances within DOD. These contractors who maintain or have in their possession a passport issued by a foreign country are considered dual-citizens. The contractor, subcontractor(s), and/or partner(s) shall possess the capability to articulate well, speak and write fluently in the English Language, and comprehend the English Language. Upon contract award, the contactor shall submit the names of contractor personnel to the government unit security manager for vetting through JPAS to ensure investigative and clearance requirements have been satisfied. Contractor is required to assure any employees requiring a clearance, be initiated through DISCO (Defense Industrial Security Clearance Office) for background investigations prior to employment. Government unit security manager will have to initiate and submit NACI’s for CAC and LAN access for personnel on the contract that have not had a past clearance (secret or top secret) or past suitability determination background investigation (NAC/NACI). This will be completed before the COR/Trusted Agent (TA) creates and approves a Common Access Card (CAC) in the DOD Contract Verification System (CVS) for each employee.

8.3 Information systems background investigation requirements. Contractor personnel with access to Information Assurance (IA) administrative privileges and/or who will monitor DOD Information Technology (IT) systems or software as designated by DOD 8500.1/5200.2-R may be rated at the various levels listed in the paragraphs below. The stipulation of the numbers and what IT/Automated Data Processing (ADP) levels the contractors will have is approved by the COR or the CO before the start of the contract. The contractor shall not divulge any financial, planning, programming, or budgeting information without the express consent of the Government as outlined in Operational Security (OPSEC) and Information Security regulations. The contractor shall comply with all appropriate provisions of applicable security regulations. Specific security requirements are identified in the DD Form 254, DOD Contract Security Classification Specification. A draft DD Form 254 is attached to the contract. Final DD 254 form will be coordinated with Government POCs after award. The following guidance will be followed when determining background investigation and clearance levels for this contract depending on requirements.

8.4 Information Technology (IT)-I/Automated Data Processing (ADP)-I/Critical Sensitive Positions:

Those positions in which the contractor is directly responsible for the planning, direction, and implementation of a computer security program; major responsibility for the direction, planning and design of a computer system, including the hardware and software; or can access a system during the operation or maintenance in such a way, and with a relatively high risk for causing grave damage, or realize a significant personal gain.

8.4.1 (IT-I/ADP-I or Critical Sensitive) Background Investigation Requirements:

Positions designated by the Government as Critical Sensitive/ADP-I/IT-I rating require an Single Scope…