Attachment_1_-_PWS_-_IBM_Notes_V4.docx

RFP CC15HQR0015

Attachment 1: Performance Work Statement

OFFICE OF THE COMPTROLLER OF THE CURRENCY

PERFORMANCE WORK STATEMENT

IBM NOTES/DOMINO SUPPORT AND CONVERSION

April 24, 2015

Table of Contents

INTRODUCTION

The Office of the Comptroller of the Currency (OCC) is an independent bureau of the U.S. Department of the Treasury. Its primary mission is to charter, regulate, and supervise all national banks and Federal savings associations. OCC’s goal in supervising banks and Federal savings associations is to ensure that these entities operate in a safe and sound manner and in compliance with laws requiring fair treatment and access to credit and financial products.

Headquartered in Washington, D.C., the OCC has four district offices, an Office of the Ombudsman, and an office in London to supervise the international activities of national banks. To carry out the agency’s mission, bank examiners conduct on-site reviews of national banks and Federal savings associations (or Federal thrifts) and provide sustained supervision of these institutions’ operations. Examiners also analyze loan and investment portfolios, funds management, capital, earnings, liquidity, sensitivity to market risk for all national banks and Federal thrifts, and compliance with consumer banking laws for national banks and thrifts with less than $10 billion in assets. In addition, these examiners conduct audits to review internal and external controls, as well as evaluate management’s ability to identify and control risks.

Four business objectives support the OCC’s mission to:

· Ensure the safety and soundness of the national system of banks and savings associations

· Foster competition by allowing banks to offer new products and services

· Improve the efficiency and effectiveness of OCC supervision, including reducing financial regulatory burdens, and

· Ensure fair and equal access to financial services for all Americans.

The Chief Information Officer and the Information Technology Services (ITS) department are committed to ensuring that the OCC has the most productive and innovative technology available. ITS plays a major role in supporting the mission and objectives of the OCC by developing, maintaining, and supporting technology systems and applications.

ITS provides the infrastructure and applications in support of the OCC’s business objectives. ITS is comprised of the following organizational areas: 1) Application Services Delivery (ASD); 2) Infrastructure and Operations (I&O); 3) Operations, Strategy and Controls (OSC); 4) Security and Compliance Services (SCS); 5) IT Customer Support (ITCS); and 6) the Office of the CIO (OCIO).

1. TECHNOLOGY BACKGROUND

Commensurate with the commitment to employ productive and innovative technologies, the OCC has invested in IBM Lotus Notes and Domino (known as “Notes” throughout this document). Domino databases and applications provide a means for geographically dispersed individuals to effectively and efficiently share information across the OCC computer network. Shared information includes projects, requests, discussion topics, conferences, technical information (bulletin boards), and schedules.

Notes use is widespread, encompassing all OCC departments and staff levels, and is firmly entrenched in the day-to-day activities of bank examiners and staff from the Comptroller to clerks. All OCC employees have Notes installed on their personal computers as part of the standard desktop configuration. Currently there are more than 100 Notes databases in use at the OCC. The Domino environment consists of 6 partitioned Production instances and 5 Development instances of Domino.

2. DOCUMENT PURPOSE

The purpose of this Performance Work Statement (PWS) is to acquire Contractor services for server and user account administration, the upgrade of servers and clients to the next release or higher, Notes development, and the maintenance of existing Notes applications. The scope of work also includes ongoing technical and user support of the Notes applications, conversion of existing Notes applications to SharePoint and/or other OCC enterprise technologies, and the maintenance and operation of Notes services in a Production environment. The Contractor shall perform all tasks under the technical direction of the Contracting Officer’s Representative (COR).

The OCC requires adaptive, corrective, and perfective maintenance; enterprise testing; and user support on all existing Lotus Notes platforms/systems and applications throughout the agency. Additionally, the Contractor shall perform required server-side maintenance and upgrades. In FY2015, the IBM Domino servers shall be upgraded/migrated to new hardware and/or operating systems as mandated by National Institutes of Standards and Technology (NIST) guidelines and other compliance standards. The platform version of IBM Domino will be upgraded from 8.5.x to 9.x, in accordance with the IBM software lifecycle.

Planning and execution of enterprise-wide upgrades of the IBM Notes workstation client shall be required as part of upcoming technology refresh. One of the core activities of the Contractor team shall be to support ITS roadmap initiatives as they pertain to the IBM Domino servers and IBM Notes client. The Contractor shall also provide support for the retirement and conversion of Notes applications to SharePoint or another OCC environment; this activity will include requirements gathering, validation and archival of Notes data, and subsequent retirement. All functionality, requirements, and code shall be documented before applications are removed from the Domino environment.

3. SCOPE OF WORK

The scope of work under this contract includes the following types of administration, support, and operations tasks:

· Server Administration

· Installation of Lotus Notes Upgrades/Updates and Other Software to Support the Notes Environment Customer Service for Tier-2 and Tier-3 Incidents

· Install, Maintain, and Test the Notes Client

· Enterprise Testing Support

· Notes Development and Maintenance

· Notes Conversion

· Transition Planning and Management.

4. TASKS

The Contractor shall perform all tasks in a manner that meets the highest level of professional and technical standards applicable to the particular subject area. All Contractor personnel shall be considered experts in the areas in which they work. All Contractor personnel shall routinely:

· Keep current with advances in software technology and share this knowledge with project team members;

· Respond promptly and courteously to requests for assistance whether from a ServiceNow incident report or direct contact;

· Document all work creating an effective audit trail;

· Support the standards of the OCC’s Change Management Process.

Furthermore, in support of these tasks, the vendor shall ensure IT deliverables (reports, upgrades, development, modifications) meet applicable standards of Section 508 of the Rehabilitation Act of 1973, as amended. For purposes of “reports”, the electronic documents shall be suitable for posting on the OCC Intranet. Specifically, the following technical and functional standards apply:

36 CFR 1194.21 – Software Applications and Operating Systems 36 CFR 1194.22 – Web based Intranent and Internet Information and Applications 36 CFR 1194.31 – Functional Performance Criteria

No exceptions for these standards are approved. Exceptions are only permitted when authorized by the OCC IT Accessibility Program.

Task 1: Server Administration

The Contractor shall administer the Notes servers to maintain the operability, functionality, reliability and responsiveness of the servers, databases and applications. The Contractor shall perform activities in support of the OCC Application Solutions Inventory (ASI), the primary purpose of which is to provide information about all application solutions maintained by Information Technology Services (ITS). The OCC Notes user community is approximately 3,500 licensed users. The Contractor shall support active Domino applications and converted SharePoint applications. A listing of active Domino and SharePoint applications is located in Appendix A of the PWS. The following are representative of the types of server administration activities the Contractor shall perform:

· Security Activities - Change operational, administrative, system, and application account passwords. Maintain a protected means of safeguarding and recovering these passwords. Maintain Access Control Lists (ACL) and groups. Perform quarterly review of the OCC’s Name and Address Book (NAB), servers, and certificates to verify that there are no unwanted cross certificates. Manage licenses.

· Database Activities - Maintain all IBM Notes databases. Periodically review database sizes, and create test, save, and troubleshoot agents. Copy databases to the Development and Production environments, as needed for development or reconfiguration of the development environment. Delete/retire databases quarterly, based on guidance from application owner. Restore databases from backups.

· Documentation activities - Track and document system problems revealed in logs, alerts, trouble calls, and warnings. Provide performance and statistical data for problem analysis.

· Server Booting – Reboot the Development servers reboot as needed. Verify the reboot of Production and Development servers and initiate trouble calls when servers are found to be down. Notify designated OCC staff of resulting server issues in a timely manner.

· Problem Resolution - Respond to trouble calls. Perform fault isolation and resolution. Restore service. Document and report on solutions.

· Monitoring Activities - Monitor system operability and functionality. Identify abnormal performance and system degradation and resolve outstanding issues to return applications to normal performance. Review logs for both the Production and Development servers monthly. Monitor Net IQ, GroupShield, and Site Scope alerts. Check for mail and replication events, and review, correct, and resend invalid and dead mail messages. Verify backups on Production servers. Notify designated OCC staff of issues.

· Application Solution Inventory (ASI)/OCC Agency Repository Activities – Add entries to the ASI database to document new applications, databases or ownership, as directed by the COR. Update existing entries as appropriate in accordance with the OCC’s change management process and the OCC software development life cycle (SDLC) methodology, if the SDLC is applicable. Please see Appendices C and D for further details regarding OCC’s change management process and SDLC methodology (these documents are subject to change).

Task 2: Software Upgrades/Updates

Installation of Lotus Notes Upgrades/ Updates and Other Software to Support the Platform

The Contractor shall identify the requirements for, and install all upgrades, to the next software version and/or releases. The Contractor shall install patches, software updates, and other applications required to support the OCC Notes environment. The OCC currently utilizes Percussion Notrix, but the agency may employ additional software throughout the life of this contract. Once the requirements are identified, the Contractor shall determine if the upgrades and updates can be successfully installed on the current operating system. The COR shall make the final determination as to whether or not to proceed with any upgrades or updates. Once the decision to proceed is conveyed, the Contractor shall follow the OCC’s change management process. The Contractor shall travel to the OCC Data Center in Ashburn, Virginia, during the installation of the upgrades and updates. The Contractor shall be responsible for writing the test scripts and ensuring all changes pass system testing prior to deployment to the Production servers.

Historically, OCC refreshes workstation hardware on a three (3) year cycle. The contractor will be responsible for testing, issue resolution and coordination with the ITS desktop imaging staff to develop a Notes client install to become part of the OCC standard desktop image. With the deployment of new workstations, the contractor will install the latest viable version of IBM Notes software. Upgrades/Patches of Domino server software are mandated when in response to security findings or End of Life for a product.

The following are representative activities for upgrades/updates not only of Notes, but of Percussion Notrix, a Notes-supported software, currently being used at the OCC:

· Planning Activities – Follow the OCC’s change management process to prepare the artifacts required in the Request for Change (RFC). The artifacts include a project plan, impact assessment, communication plan, release management plan, detailed test strategy and test scripts, implementation plan, and roll-back procedure. The Contractor shall present the detailed release management plan and potential impacts on the Notes applications and non-Notes systems to the OCC’s change-management board for approval prior to carrying out the plan. If the SDLC methodology is applicable, follow the SDLC guidelines.

· Software Upgrades and Patches – Identify the requirements for and install all upgrades, updates, service packs, and patches. Maintain current levels of security protection and reliability. Identify any upgrades, updates, service packs, and patches determined to be incompatible with current application specifications.

· Testing Activities – Install and test all upgrades, updates, service packs, and patches in the Development environment before installing them in the Production environment. Coordinate all test activities with the Enterprise Test Team (ETT) as described in the OCC’s change control management guidelines. All tests are to be performed in the Enterprise Test Lab (ETL) environment prior to being installed in Production. Create test applications, test scripts, and test data/IDs. Follow the OCC’s release schedule to deploy the software in Production. This work may include activities to be performed outside normal business hours. OCC application releases are performed typically during the second weekend of each month. The window for releases is from 6 PM ET on Friday evening through 6 PM ET on Sunday evening. This is a monthly testing effort. On occasion, more than one off hours test cycle will take place in a month. Annually, the Contractor should not expect more than 15 weekend testing efforts.

· Roll-Back Activities – Develop a Roll-Back Plan as required for system restoration. Identify the procedures required to restore prior iteration of the deployed product. Perform all roll-back activities with the COR’s approval. The Roll-Back Plan shall be incorporated in the RFC.

· Software Package Installation - Install software packages required to support the OCC Notes environment. The OCC currently utilizes Percussion Notrix, but the agency may employ additional software throughout the life of this contract.

Task 3: Customer Service for Tier-2 and Tier-3 Incidents

The Contractor shall respond to trouble calls received for Notes applications. The Contractor shall provide technical assistance to Notes users to address their Notes requirements. The Contractor shall standardize the tracking of all Notes-related trouble calls in an appropriate OCC provided ticketing or problem management system. Appendix B depicts the number of Tier-2 and Tier-3 tickets received over time. Incidents are defined as a work stoppage that requires resolution (lost/forgotten passwords, application or client software errors, unavailability of resources etc). Service Requests are tickets that require resolution but are not the result of a work stoppage (new user account, application access request etc.). Tasks are routine administration jobs (name changes, transfers, terminations). The following are representative of the types of customer-service activities the Contractor shall perform:

· User Account Administration – Create new user accounts. Change and delete accounts. Reset passwords. Ensure replication of all user-account administrative actions.

· Application Access – Grant, modify, and revoke application access. Maintain accurate user profile records of the names of users and the access they have been granted.

· Incident Resolution – Monitor ServiceNow, the Enterprise Problem Management System (eProMs) or other problem reporting mechanisms to provide technical support for troubleshooting, diagnosis, escalation, and resolution of Tier-II and Tier-III issues associated with application performance. Contact the requestor, determine the nature of the incident, resolve the issue, and close the incident ticket in ServiceNow. Standardize the problem-resolution descriptions to facilitate knowledge transfer between team members.

· User Support – Address user questions to facilitate the effective operation and performance of the Lotus Notes applications. Provide incidental training and desk-side support to users, as needed.

Task 4: Install, Maintain, and Test the Notes Client

The Contractor shall support the installation, maintenance, and testing of Notes client software and desktop images. Representative activities shall include:

· Installation Activities – Install client software on new desktop images. Install/configure new users. Software is part of the standard OCC workstation image. Some users may require assistance in configuring the Notes client (approximately 2/week)

· Image Maintenance – Maintain and document client image files. (During PC Refresh activities which are scheduled to occur in FY2016)

· Testing Activities - Test new images, new or enhanced applications for the ITS Desktop Engineering group. Monthly when Microsoft patches and/or other software is deployed for testing

· Coordinate all test activities with the ETT as described in the OCC’s change management process. All tests are to be performed in the ETL prior to being installed in Production.

· Create test applications and test data/IDs to support testing activities, so that Production applications maintain integrity.

Task 4.1: Enterprise Testing Support The Contractor shall perform regression testing to sustain Notes continuous operability and functionality. The Contractor shall be responsible for writing the Notes test scripts. Some of the testing work may include activities to be performed outside of normal business hours. Some examples of activities in this area include:

· Monthly Microsoft Security Updates/Patches for Workstations and Servers

· Monthly Application Release Testing (ART)

· Monthly Infrastructure Release Testing (IRT).

· Unscheduled Release Testing (approximately twice per year)

· Ad-Hoc Security and Compliance Testing

· New Desktop Image Testing (OCC workstations are refreshed on a three year cycle)

Task 5: Notes Development and Maintenance The Contractor shall provide development support to existing Notes applications at the OCC. Support shall include developing new applications; performing adaptive, perfective, and corrective maintenance; and refreshing existing technology. All development activities shall pass user acceptance testing (UAT) prior to being deployed in Production. The Contractor shall also provide knowledge transfer regarding new technology to support Notes. Representative development activities include:

· User Data Requirement Activities – Meet with business unit managers and system administrators. Gather user requirements and determine the inputs, forms, processes, views, and database sources involved. Provide an estimate of the work required. Develop definitions that specify conditions or constraints regarding the extraction of data. If the SDLC methodology is applicable, follow the SDLC guidelines.

· Planning Activities – Follow the OCC’s change management process to prepare the artifacts required in the RFC. The artifacts include the project plan, impact assessment, communication plan, release management plan, detailed test strategy and test scripts, implementation plan, and the roll-back plan. The Contractor shall present the detailed release management plan and the potential impacts on Notes applications and non-Notes systems to the OCC’s change-management board for approval before carrying out the plan. If the SDLC methodology is applicable, follow the SDLC guidelines.

· Design and Development Activities – Design and develop Notes applications, bulletin boards, and databases for use with both Notes clients and Web browsers. Prepare objects and create supporting code. Where possible, employ existing bulletin board templates. Construct SQL queries. Employ third-party reporting tools. Provide design and development artifacts in accordance with the OCC SDLC.

· Beta Application Activities – Develop, construct, and release for UAT beta versions of applications that emulate performance in Production. Prepare draft documentation, test transaction data, test plans, and test scripts. Configure user access and controls.

· Testing Activities – Develop a test strategy/plan to verify that each requirement has been addressed. All tests are to be performed in the ETL. Create test applications and test data/IDs. All activities shall pass user acceptance testing prior to being deployed in Production. Follow the OCC’s release schedule for deployment in Production. Some of the testing work may include activities to be performed outside of normal business hours.

· Maintenance Activities – Perform corrective, adaptive, and perfective maintenance. Corrective maintenance includes modifications to applications that fix problems caused by design, logic, or coding errors. Adaptive maintenance includes modifications mandated in response to policies, procedures, laws, or regulations governing the OCC’s programs that require changes and/or updates within the OCC’s technical architecture. Perfective maintenance includes enhancements to maintain application viability in Production to meet customer requirements.

· Monitoring Activities – Monitor application operability and functionality, identify abnormal performance and degradation, and complete resolve outstanding issues return applications to normal performance.

· Documentation Activities – Develop and document user, application, and system needs for new and existing functional capabilities. Prepare and document work plans, schedules, and technical approach recommendations. Analyze and document defects. Create deployment instructions, release notes, requirements documents, help files, end-user instructions, RFC artifacts, SDLC artifacts, and alternatives analysis (to include the risks, advantages, and disadvantages of different courses of action and a recommendation of the best alternative). Create and update database and application descriptions. Update the ASI to reflect current information related to new or existing applications.

· Tracking Activities – Track all development and maintenance requests in the ITS Notes Tracking Database and in ServiceNow.

· User Training Activities – Prepare and execute a Training Plan, where necessary. to promote application acceptance. Identify the target audience for training. Document the training requirements and recommend an appropriate training format (e.g., classroom training, brown-bag tutorials, or one-on-one sessions). Create and maintain training materials, training aids, and the training schedule.

· Coordination Activities – Serve as a liaison between the groups working on a project to facilitate effective communication. Groups may include business units, software developers, database administrators and designers, and vendors. Coordinate and schedule meetings, disseminate and collect information, and server as the point-of-contact (POC) for selected tasks.

· Technology Consulting – Review and evaluate the specifications and capabilities of new or improved technologies and provide recommendations regarding the integration of these technologies.

· Knowledge Transfer – Plan and implement methods and procedures to share knowledge with the relevant stakeholders and team members to ensure that no critical body of knowledge resides uniquely in one individual.

Task 6: Notes Conversion The Contractor shall engage in activities that facilitate the migration or conversion of existing Notes applications to SharePoint and/or other OCC enterprise technologies. The applications and associated complexity indicators are located in Appendix A:

Prior to Conversion

· Analysis - Analyze the current Notes application functions and prepare to discuss the functionality of each application.

· Application Documentation - Document detailed descriptions of the application functional requirements, including functional flow charts, processing flow charts, and external connectivity flow charts.

· Formatting – Format the Notes data for use in SharePoint and/or other OCC enterprise technologies.

· Data Conversion – Extract/convert the Notes data in a format that is compatible with the receiving technology to preserve data integrity.

· Cleanup – Remove test processes/agents, views, and any design elements that do not represent the functional requirements of the application.

· Adaptive Maintenance – Perform adaptive maintenance on Notes applications in order to facilitate the conversion/migration.

Post Conversion

· Verification – Verify that the functionality previously available in the Notes applications are available in the converted applications.

· Documentation – Document the conversion process.

· Support and Maintenance – Support and maintain the converted applications.

Task 7: Transition Planning and Management The Contractor shall provide transition support at the end of the period of performance (POP) specified in this PWS. At the end of its POP, the Contractor shall provide a plan for transitioning work from the current contract to a follow-on contract. Transition management shall focus on leveraging common technologies, rationalized assets, and optimized processes, while remaining flexible in response to OCC’s dynamic operational environment.

The Contractor shall provide a Transition Plan that supports a 90-day transition period or less. The Contractor shall collaborate with ITS to develop a plan that successfully transitions the scope of work specified in this PWS to the new Contractor and/or the designated OCC employee(s). Specifically, the Contractor shall:

· Transition Plan: Create a detailed transition plan that covers each application and function that describes how the Contractor shall take ownership in a period of within 90 calendar days or less. The initial draft plan shall be submitted with the Contractor’s proposal. A revised plan shall be presented to the OCC within 7 calendar days after contract award. A final plan shall be presented within 14 calendar days after contract award for OCC approval. The transition plan shall include, but is not limited to, the following.

· Transition Scope and approach

· Recruiting approach

· Internal resources required

· External resource requirements

· Risks & issues

· Milestone schedule

· Communications Plans

· Knowledge Transfer requirements

· Transition of historic data to new Contractor system

· Government-approved training and certification process

· Transfer of hardware warranties and software licenses (if applicable)

· Transfer of all necessary business and/or technical documentation

· Transfer of compiled and uncompiled source code, to include all versions, baselines, maintenance updates and patches (if applicable)

· Understanding applicable OCC briefing and personnel in-processing procedures

· Understanding of OCC processes (e.g., release management)

· Location, use, and access to team collaboration sites (e.g., SharePoint)

· Source control procedures

· Transition Execution: Support the incorporation and management of the application transition plan/schedule into the ITS Integrated Master Schedule.

· Transition Execution: Conduct transition activities identified in the Transition plan and schedule.

· Transition Execution: Until all transition activities are complete, (a) provide transition status in the weekly status report, and (b) conduct a weekly status meeting with each application team to discuss transition progress.

· Transition Completion: Provide a transition briefing 60 days after the start of the plan, which summarizes the results of the transition and any outstanding issues or risks.

· Transition Assistance: Provide prompt and efficient transition assistance as requested by the COR in the event that some or all of Contractor’s work is reallocated.

· End of Performance Period Transition Support: At the end of the POP described in this PWS, the Contractor shall assist in the transition to the replacement Contractor and provide:

· A Transition Plan that includes the following content:

· Transition scope and approach

· The resources, both internal and external, required to support the transition

· Risks and issues associated with the transition

· A transition schedule

· A Communication Plan for the transition

· Knowledge-transfer requirements for the transition

· A description of how historic data will be transferred to the new Contractor’s system(s)

· The Government-approved training and certification process

· The approach to transferring hardware warranties and software licenses (if applicable)

· The approach to transferring all business and technical documentation

· The approach to transferring both compiled and uncompiled source code, to include all versions, baselines, maintenance updates, and patches (if applicable)

· A description of the location and usage of team collaboration sites (e.g., SharePoint sites).

In addition, the Contractor shall:

5. REPORTING DELIVERABLES

The Contractor shall provide monthly status reports in Microsoft Word format by noon on the last working day of the month. At a minimum, the status report shall include:

· The month and year of the status report

· The submission date of the status report

· A description of the administrative activities for the month

· A description of the administrative issues for the month

· The development activities for the month, including the name of the activity, the type of activity, the impacted database(s), the associated business unit, the description of the work completed, and the assigned developer.

· The development issues for the month

· Other activities related to OCC IBM Notes/Domino activities for the month

Furthermore, a chart of the expected major deliverables under the tasks associated with this contract is provided below:

6. CONSTRAINTS

System Development Life Cycle (SDLC) The Contractor shall follow the OCC SDLC standards and create and maintain the SDLC artifacts as required. The SDLC requires representatives from OCC technical units to be involved during all phases of the development life cycle. “Involvement” may include simple notification, or it may involve conducting presentations to OCC personnel, responding to questions from these personnel, and seeking approvals from particular OCC business units (such as Security, Technical Infrastructure, Data Management, Customer Support, Section 508, Records Management, and Quality Assurance) responsible for ensuring architectural conformance and adherence to operational and performance standards.

As appropriate, the Contractor may request a waiver from OCC’s SDLC Program Manager. The waiver must include a justification for the deviation from the specified SDLD process or requirement, and it is subject to approval. The waiver may be revoked if the OCC develops concerns about deliverable quality or controls.

OCC Change Management Process The Contractor shall follow the OCC’s Change Management Process standards for all work products.

7. QUALITY CONTROL

The Contractor shall develop and maintain an effective quality control (QC) program to ensure services are performed in accordance with the PWS and the Performance Requirements Summary (PRS) provided by the OCC. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s quality control program is the means by which the company assures the work complies with the requirements of the contract. The Contractor shall provide a draft Quality Control Plan (QCP) with its proposal. A final QCP is due 30 calendar days after contract award. After acceptance of the QCP by the CO, the contractor shall obtain the CO’s acceptance in writing of any proposed changes to this QC system.

8. QUALITY ASSURANCE

The Government will evaluate the Contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP) below. This plan is primarily focused on what the Government will do to ensure that the Contractor has performed in accordance with the performance standards and its QCP. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s). The Government will review Monthly Progress Reports (MPR) and will attend regular task-performance review meetings with the contractor to survey the quality of products and services.

Please see Appendix E for the Quality Assurance Surveillance Plan associated with this requirement.

9. BUSINESS HOURS

Work under this contract shall generally be performed during the core business hours of 8:00AM through 5:00PM, Eastern Time, Monday through Friday, excluding Federal holidays. At times, performance outside of the core business hours may be requested so as not to interfere with production operations. The Contractor shall be requested to provide contact information for staff who may be contacted outside of the core business hours. Prior approval from the Contracting Officer or the COR must be obtained before any work may be done outside of the core business hours.

10. PERIOD OF PERFORMANCE

The base period of performance for this task order shall be October 1, 2015 through September 30, 2016, with four (4) one-year options.

11. PLACE OF PERFORMANCE

Work shall be performed at the OCC Headquarters (HQ) located at 400 Seventh St. SW, Washington, D.C., and on-site at facilities in or near OCC HQ (e.g. the OCC Data Center in Ashburn, Virginia).

12. CONTRACT TYPE

This contract shall be a hybrid firm-fixed-price / labor-hours contract.

13. KEY PERSONNEL

The following contract positions, at minimum, are key and determined to be essential by the Government:

Key Personnel Listing Title

IBM Notes/Domino Administrator

Senior IBM Notes/Domino Developer

IBM Notes/Domino Developer/Analyst-Tester

The Contractor shall identify the responsibilities for each key position and submit a resume for each of the persons designated as key personnel. The resumes should demonstrate that the proposed key personnel are fully qualified in terms of specific skills and skill levels and that they have pertinent technical management experience on jobs of similar scope. Resumes shall include the following content:

Position Description - Provide a brief description of the duties for this position.

Summary of Qualifications - Provide a brief summary of why the person is qualified for the position.

Education (and Training) – Identify the degree(s) earned, the major field of study, and the name of the college or university.

Professional and/or Technical Certifications - List certifications earned, the name of the certifying body, and the year awarded. List only those certifications that are relevant to the scope of work described in this call.

Employment History - Provide the name of the employer, the total period of employment with the employer, and a reverse chronological listing of job assignments. List only job assignments relevant to the individual’s proposed role in support of this call. For each job assignment, show the candidate's:

Position description or labor category and duration of assignment, including month and year Major customer(s) and program(s) served on the assignment Specific relevance of the work performed, including accomplishments or innovations in technical or managerial performance.

The resumes should demonstrate the depth and breadth of the key personnel’s experience performing work that is similar in scope, size, and complexity to that described in this PWS. Individual resumes are limited to three (3) 8.5 x 11-inch pages each, with a font size no smaller than 12 points. The format of the resumes is left to the discretion of the Contractor; however, all resumes included in the Contractor’s proposal must follow the same format. Resumes should be provided in an appendix to the Contractor’s technical proposal.

Minimum Key Personnel Experience Requirements IBM Notes/Domino Administrator:

· Education: B.A. or B.S. degree (preferably in an Information Technology/Computer Science related field)

· General and Specialized Experience: The Administrator must have at least five (5) years of direct experience working as an IBM Notes/Domino Administrator, with some of this experience accrued within the past two (2) years.

· Note: If the proposed employee does not have the requisite Bachelor’s degree, a total of ten (10) years of direct experience working as an IBM Notes/Domino Administrator may be used in lieu of the degree requirement, with some of this experience accrued within the past two (2) years.

Senior IBM Notes/Domino Developer:

· Education: B.A. or B.S. degree (preferably in an Information Technology/Computer Science related field)

· General and Specialized Experience: The Senior Developer must have at least five (5) years of direct experience working as an IBM Notes/Domino Developer, with some of this experience accrued within the past two (2) years.

· Note: If the proposed employee does not have the requisite Bachelor’s degree, a total of ten (10) years of direct experience working as an IBM Notes/Domino Developer may be used in lieu of the degree requirement, with some of this experience accrued within the past two (2) years.

IBM Notes/Domino Developer Analyst-Tester:

· Education: B.A. or B.S. degree (preferably in an Information Technology/Computer Science related field)

· General and Specialized Experience: The Analyst-Tester must have at least three (3) years of direct experience working as an IBM Notes/Domino Developer Analyst-Tester, with some of this experience accrued within the past two (2) years.

· Note: If the proposed employee does not have the requisite Bachelor’s degree, a total of five (5) years of direct experience working as an IBM Notes/Domino Analyst-Tester may be used in lieu of the degree requirement, with some of this experience accrued within the past two (2) years.

LIST OF AppendiCES

1. Appendix A – Domino Applications (Excel file)

2. Appendix B – Lotus Notes Statistics (2 pages)

3. Appendix C – Enterprise Change Management Plan (28 pages, including title/tables of contents pages)

4. Appendix D – Systems Development Life Cycle (98 pages, including title/table of contents pages)

5. Appendix E – Quality Assurance Surveillance Plan (10 pages, including title/table of contents pages) image1.png