Attachment 4 - Application Management Sample Task Order.doc

Defense Information Systems Agency

Chief Information Officer

DISA Information Technology Enterprise Support Services (DESS)

HC1047-12-D-XXXX

Task Order (TO) 0004 (Version 1.0)

31 January 2012 Table of Contents

11.

Task Order Contracting Officer Representative (TO COR)

12.

Task Order Title: DISA IT Enterprise Application Support

23.

Background

34.

Objectives

35.

Scope

46.

Specific Tasks

46.1 IT Enterprise Application Support

46.1.1 Tasks:

56.2 Intranet Services Operations and Maintenance

56.2.1 Tasks:

56.2.2 Subtask 1 – DISA Workspaces

66.2.3 Subtask 2 – Identity Management (IdM)

76.2.4 Subtask 3 – DISA Records Repository (DRR)

86.2.5 Subtask 4 – Intranet System Architecture

96.2.6 Subtask 5 – Systems and Database Administration

106.2.7 Subtask 6 – Configuration Management (CM)

126.2.8 Subtask 7 – Troubleshooting/Technical Help Desk Support

136.2.9 Subtask 8 – DISA Financial Management System (DFMS) Application

136.2.10 Subtask 9 – Knowledge Tree (KT) Application and Database Maintenance

146.2.11 Subtask 10 – SharePoint Application

157.

Place of Performance

157.1 Primary Place of Performance

157.2 Alternate Place of Performance

158.

Travel Requirements

159.

Period of Performance

1510.

Delivery Schedule

2411.

Service Level Agreements and Performance Metrics

2412.

Security Requirements

2412.1 The VAR/VAL should be sent via one of two methods.

2412.1.1 Method One

2412.1.2 Method Two

2713.

Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI)

2713.1 GFE/Access

2713.2

GFI

2714.

Other Pertinent Information or Special Considerations

2714.1 Identification of Potential Conflicts of Interest (COI).

2714.2 Identification of Non-Disclosure Requirements.

2714.3 Inspection and Acceptance Criteria.

2715.

Section 508 Accessibility Standards

1. Task Order Contracting Representative (TO COR)

1.1 Primary TO COR

Department of Defense Activity

Address Code (DODAAC):

HC1047

Fort George G. Meade, MD 20755-0549

1.2 Alternate TO COR

Department of Defense Activity

Address Code (DODAAC):

HC1047

Fort George G. Meade, MD 20755-0549

2. Task Order Title: DISA IT Enterprise Application Support Defense Information Systems Agency’s (DISA’s) Information Technology (IT) Enterprise Application Support

3. Background The Defense Information Systems Agency is a Combat Support Agency responsible for connecting US Forces and their coalition partners to the DoD’s Global Information Technology (IT) Enterprise. DISA provides IT networks, computing infrastructure, and enterprise services in direct support of US Warfighters to facilitate the seamless exchange of information on a global scale.

The mission of DISA’s Chief Information Officer (CIO) is to, “Lead and govern the delivery and operation of secure world-wide enterprise IT services enabling the efficient and effective execution of DISA’s global combat support missions.” In order to accomplish this mission, the DISA CIO must:

· Provide an efficient and effective IT infrastructure and services to support the Agency’s warfighting mission.

· Achieve a Mission Assurance posture that ensures the security and continuity of the Agency’s internal IT Enterprise’s infrastructure and services against an ever evolving spectrum of threats.

· Maintain compliance with all DoD information governance policies and legislation.

· Govern a common architecture and service delivery framework to drive efficiencies in business system investments and portfolio and knowledge management capabilities.

Directorate’s Background The Office of Information and Knowledge Management (CIO) under the Defense Information Systems Agency’s (DISA’s) Office of the Chief Information Officer (CIO) has a continuing requirement to provide quality management information systems and services in support of the DISA enterprise. CIO is responsible for the design, development, integration, implementation, and operations and maintenance (O&M) of internal enterprise level information systems supporting customers from across the Agency.

The primary focus of CIO’s engineering support activities is to provide O&M support for a suite of applications and services known as DISA Intranet Services. DISA Intranet Services is comprised of the following: 1) DISA Workspaces, enterprise content management repository; 2) DISA Records Repository (DRR), electronic records management; 3) Identity Management (IdM); 4) Single-Sign-On (SSO) Service; 5) Central Authentication Directory (CAD) enterprise-level Lightweight Directory Access Protocol (LDAP); 6) Federated Search; 7) Business Intelligence (BI); and 8) DISA Restricted Web Content Hosting. In addition to the aforementioned Intranet Services, CIO is responsible for the O&M of customer applications such as the Chief Financial Executive’s (CFE) Knowledge Tree (KT), the DISA Financial Management System (DFMS), and the Office of the Chief of Staff’s (OCOS) Action Information Management System (AIMS).

A critical success factor for each of these applications and services is to ensure seamless integration with DISA’s enterprise portal, Defense Knowledge Online (DKO). CIO is responsible for the management and technical oversight of the DISA DKO implementation and all Agency integration efforts with the DKO portal.

To satisfy the operation and maintenance requirements for each of the applications and services, CIO currently receives system design, development, configuration management, system administration, database administration, security engineering, and system integration support services.

4. Objectives This task order is intended to acquire the contractor support personnel and technical competencies to assist CI6 with the delivery and operation and maintenance of DISA Intranet Services. This includes maintenance and operational support for existing CI6 products and services such as the DISA Workspaces, DISA Records Repository (DRR), Identity Management Service, DISA Financial Management System (DFMS), and Action Information Management System (AIMS) as well as the delivery of new capabilities through product enhancements, adoption of other Department of Defense (DoD) technologies, or the integration of new software code (Government-Off-The-Shelf (GOTS) and/or Commercial-Off-The-Shelf (COTS)).

The technical work under this task will require highly-skilled and trained personnel with experience in such products and technologies as Microsoft Sharepoint and Sequel Server, Oracle/BEA WebLogic application server, Tomcat application server, OpenText Collab 7.x, OpenText Records and Documents (VRD) 7.x, Netegrity (CA) SiteMinder, Sun IdentityManager, SunOne Directory Server (LDAP), Apache Regain Search, XML/Web Services, Oracle 9i and 10g, Adobe ColdFusion, IBM Cognos, and ASP (see Attachment 1, Table 1). The contractor support personnel will also provide expertise in the area of service-oriented architectures (SOA) and understand how each of the DISA Intranet Services fit into such an architecture and/or become more “SOA-like.” The contractor support personnel provided under this contract will interact with the requirements team to reconcile issues associated with requirements; negotiate delivery schedules with government program managers; design, develop and deploy systems; and support all other aspects of Information Technology (IT) system delivery such as configuration management, system testing, and system documentation.

5. Scope The scope of this Task Order includes DESS PWS task areas X, X, and X. The nature of the work conducted under this task will generally consist of the following:

· Systems Analysis

· System Implementation and Integration

· Application/ Web Service Development

· Application/ Web Service Retirement

· Change Management

· System Operations and Maintenance

· Data Backup and Recovery

· System Security

· Project Management and Support

· Technical Architecture Assessment

· Documentation

· Training

6. Specific Tasks

IT Enterprise Application Support

6.1.1 Tasks:

6.1.1.1 Provide support services to develop, document, structure, plan, implement, coordinate and monitor the delivery of IT applications.

6.1.1.2 Provide technical support to ensure all IT Enterprise services are provided efficiently and economically, while providing the intended service or capability.

6.1.1.3 Perform the application maintenance activities required to repair errors and defects of new or existing GOTS/COTS applications and associated databases to include: corrective and emergency maintenance to applications in production, preventive maintenance to mitigate future events that could disable or degrade service, adaptive maintenance to ensure application performance is not affected by changes to interfacing or new applications, and perfective maintenance to ensure that applications operate at peak efficiency.

6.1.1.4 Perform application development support activities associated with the development of application enhancements and related modifications, on new, existing or under development GOTS/COTS applications and databases to include, program management support, requirements and design support, programming and development support, integration and testing support, code migration support, software configuration management support, and technical change management support.

6.1.1.5 Provide classroom style and/or computer-based training services for existing, new or enhanced applications that are developed as Government Off-The-Shelf (GOTS), or Commercial Off-The-Shelf (COTS) applications, to include the development of any training documentation and materials.

6.1.1.6 Perform technical analysis, as directed by the Government, to determine the ability of new or newly modified applications to successfully interoperate with existing inventory of DISA IT Enterprise Components and DoD provided Joint Enterprise Services.

Intranet Services Operations and Maintenance

6.1.2 Tasks:

6.1.2.1 The contractor will operate and maintain all environments, but at a minimum development, test and production versions of the Intranet Services, CFE systems, BI, and AIMS in accordance with CIO, DISA, DoD, and Federal Government policies and directives.

6.1.2.2 System operations, maintenance, and administration of CIO systems are a time intensive task that requires a significant number of hours to be worked after normal duty hours (0900-1500).

6.1.2.3 Typically, contractor personnel are directed by the Government to perform all system maintenance activities after 1900 EST. If maintenance (e.g., operating system patch application, version upgrade, web server configuration changes, etc.) is required on production servers, the contractor is required to start all maintenance activities after 1900 EST.

6.1.2.4 The vast majority of production maintenance activities occurs on Friday nights after 1900 EST and extends into the weekend. The contractor will perform these maintenance activities on an as-needed basis as determined by the Government TO COR.

6.1.2.5 For estimation purposes, it is anticipated that there will be two such activities per month, with an average of six hours per person, per maintenance activity, for the duration of the contract

6.1.3 Subtask 1 – DISA Workspaces

6.1.3.1 The contractor will operate and maintain OpenText Collab 7.x servers and customized applications built using the Collab application interfaces (APIs) in the DISA environment until DISA stands up the agency’s instantiation of 20xx. All new development on the OpenText Collab environment will cease unless otherwise directed by CIO management. With the efforts to deliver SharePoint to the Agency, the contractor will assume the requirement for migration of content from OpenText Collab 7.x to SharePoint 20xx.

6.1.3.2 The contractor will provide personnel to maintain the Intranet Services SSO service and its integration with the applications and services listed in Attachment B (Table 1). DISA is currently implementing a transition of their SSO-enabled applications off of the CIO‑maintained infrastructure to the DKO SSO infrastructure.

6.1.3.3 The contractor will be responsible for providing personnel to operate and maintain the existing CIO infrastructure as well as perform the analysis, design, transition plan, and integration engineering to migrate these applications to DKO.

6.1.3.4 The contractor will communicate any associated technical information requested by the DKO SSO engineering team, and develop and maintain supporting documentation associated with the SSO infrastructure.

6.1.3.5 The contractor will be responsible for developing and maintaining user synchronization between DKO and DISA directories (group synch), and ensuring all DISA users (and authorized guests) have the access they require. All new SSO system requests will be integrated with the DKO SSO solution.

6.1.4 Subtask 2 – Identity Management (IdM)

6.1.4.1 The contractor will provide personnel responsible for maintaining the Intranet Services IdM service and its integration with other DISA systems. The current IdM implementation is focused on providing CAC/PKI self-registration, directory synchronization, and account provisioning/de‑provisioning services for an estimated 15,000 DISA military, civilian, and contractor personnel.

6.1.4.2 The personnel provided to maintain this implementation must have expert knowledge of the Sun Identity Manager version 7 or later product and recommended product architectures. The specific tasks associated with the O&M of the IdM service include, but are not limited to, development of IdM workflows, SPML development, custom data/directory synchronization scripts outside of the IdM product, account provision, account de‑provisioning, Active Directory (AD) integration, LDAP integration, Microsoft Structured Query Language (MS SQL) integration, and Oracle integration.

6.1.4.3 The contractor is required to have specific knowledge for the design, development, and maintenance of the following:

6.1.4.4 Integration with the DISA Computing Services Directorate (CSD) delivery of the DISA Enterprise Email Solution.

6.1.4.5 An Account Approval Process module designed to provide account approval process workflow, account request review forms for Intranet Support and Approver/Sponsor, and rules for account creation request validation and checking account request status.

6.1.4.6 A provisioning/de-provisioning module designed to provide creating, updating, and disabling the accounts that presents the user in the LDAP directory and/or DKO directory service.

6.1.4.7 A Delegated Administration module designed to provide the ability to delegate individual system activities to administrators by providing limited control over specific organizations and objects within those organizations, filter administrator views of user creation and edition pages, and give administrators specific job duties in the form of capabilities.

6.1.4.8 Installation and configuration of additional database and directory connectors to DISA systems to further synchronize DISA identity information across all DISA systems.

6.1.4.9 Ability to provide a DISA identity service to facilitate the sharing of DISA identity information with the DoD Joint Enterprise Directory Service (JEDS).

6.1.4.10 Implementation and maintenance of a series of IdM-based web services to provide the means for DISA systems to consume and utilize the DISA identity information that is brokered by the DISA IdM service. These web services will include out-of-the-box web services from the Sun Identity Manager product as well as any custom web services identified by the Government TO COR.

6.1.4.11 In addition to the Sun IdM solution, Intranet Services has developed a custom java application for enterprise user management. This application is known as “UserTool” and is tracked under the IdM service for configuration management purposes. The UserTool is a small java application running on Tomcat, Enterprise Edition (J2EE) application server. The application allows Intranet Support and other application administrators the ability to establish, reset, update, and delete users and their associated passwords, permissions, and groups.

6.1.4.12 The contractor will provide personnel that are able to administer the WebLogic application server as well develop new, or update existing, software code for the UserTool.

6.1.5 Subtask 3 – DISA Records Repository (DRR)

6.1.5.1 In the process of CIO standing up Sharepoint 20xx, a full assessment will be completed on the requirements associated with Records Management and a recommendation will be made to either stay on the OpenText application or move to the new recommended product. Until the decision is made, all new development on the DRR environment will cease unless otherwise directed by CIO management.

6.1.5.2 The contractor will provide personnel responsible for maintaining the OpenText Records and Documents (VRD)-based electronic records management (ERM) code and custom configurations (known within DISA as the DISA Records Repository (DRR)).

6.1.5.3 The contractor will provide personnel with expert knowledge of the VRD product and be able support the O&M of the application.

6.1.5.4 The personnel provided will have relevant experience with customization of the VRD interface; and administration of the VRD database, directory (and/or integration with enterprise LDAP directories), WebLogic application server, and all associated security permissions.

6.1.5.5 In addition, the personnel provided should have sound experience with HTML, XML (exports), and JavaScript (manipulation of attributes).

6.1.5.6 The contractor will have specific knowledge and experience required to: configure and maintain the E-mail Integration feature for transferring e-mails from outlook directly into VRD; implement and configure the Microsoft Office Suite Plug-In to transfer documents from Microsoft Word, Excel or PowerPoint directly into VRD; develop a mechanism to facilitate the integration between VRD and other DISA internal systems (e.g., content management repositories, shared drives, etc.); configure the VRD Archiver and transfer to an external Achiver device such as CDROM, optical disk, or a magnetic tape; integrate with an external generator such as Adobe Lifecycle PDF Generator to provide a means for converting all permanent documents into the National Archives and Records Administration (NARA) required PDF format; and administer as well as develop new, or update existing, software code for the custom java web application used to manage users/groups.

6.1.6 Subtask 4 – Intranet System Architecture

6.1.6.1 The contractor will provide personnel responsible for providing systems architecture support, desktop integration support, technical guidance, and technical direction for all CIO managed systems.

6.1.6.2 The lead system architect will function as the technical project manager and will be responsible for providing the government with expert consulting services for all technical matters. It is also anticipated that the lead architect will provide technical leadership and guidance to the contractor development and system administration staff to ensure technical consistency across the platforms. This role requires knowledge of a broad range of technology concepts and solutions that can be applied to the design, development, operations, and maintenance of all systems and related activities.

6.1.6.3 The contractor will be responsible for responding to architecture changes required to comply with DISA and DoD standards and technology initiatives.

6.1.6.4 The government anticipates a significant push to provide more Service Oriented Architecture (SOA) capabilities in FY10. As such, the lead system architect should be well versed in SOA and SOA implementation.

6.1.6.5 The contractor will provide an assessment of the existing Intranet Services architecture and develop a plan of action for moving the existing architecture into one more in-line with SOA principles. The plan should address how CIO can best utilize existing services, with a particular focus on the services provided to DISA by the Net-Centric Enterprise Services (NCES) program.

6.1.7 Subtask 5 – Systems and Database Administration

6.1.7.1 The contractor will provide personnel to be responsible for providing systems and database administration of all CIO environments (at a minimum, this includes development, test, and production instances). There are approximately 60 servers under the technical and management control of CIO. Although CIO operates and maintains Windows servers, the primary focus of this system administration task will be on the operation and maintenance of Unix‑based servers (currently Solaris 8 and Solaris 10). This task includes, but is not limited to, building servers, upgrading operating system versions (e.g., migrate servers from Solaris 8 to 10), applying Security Technical Implementation Guides (STIGs), applying security patches mandated by the DISA Vulnerability Management System (VMS), and performing regular maintenance to ensure maximum availability for all environments.

6.1.7.2 The contractor will be responsible for maintaining all system and database backup and restoration procedures to ensure that good, workable database and system backup files are available for system and database restoration activities. Backup schedules for each system are to be executed in accordance with the schedule identified by the Government customer and/or system owner.

6.1.7.3 As needed, the contractor will work with the system hosting provider (e.g., Defense Enterprise Computing Centers (DECCs) or the DISA Information Systems Center (DISC)) to identify roles and responsibilities related to providing data and system backups. Any deficiencies identified will be sent to the Government TO COR in writing upon discovery.

6.1.7.4 The contractor will provide system and database backup and restoration procedure documents to the Government as directed by the Government TO COR.

6.1.7.5 The contractor will use government‑available tools to generate metrics that provide insight into content and system usage.

6.1.7.6 For estimation purposes, it is anticipated that (1) FTE is required for database administration and (1-2) FTEs for system administration will be needed to perform O&M activities for the server environment. It is common for system and database administrators to work longer than average work weeks (i.e., ~50 hrs).

6.1.8 Subtask 6 – Configuration Management (CM)

6.1.8.1 The contractor will perform configuration management of all production CIO commercial software products, DISA-specific source code, and related technical documentation.

6.1.8.2 As new systems are deployed, or customizations and configurations are released, the contractor will be responsible for all aspects of deployment, to include providing full configuration management over the system baselines for all environments (at a minimum, this includes development, test, and production instances).

6.1.8.3 The contractor will be responsible for the development and documentation of the configuration management plans for each system/application/service under CIO control.

6.1.8.4 The contractor will develop and document an overarching configuration management plan that documents the general procedures, tools, system platforms, personnel, roles, and responsibilities that apply to every CIO system/application/service.

6.1.8.5 The contractor will also develop and deliver a CM plan document for each individual system/application/service that captures the specific CM procedures that are only applicable to that particular system/application/service.

6.1.8.6 The contractor will be responsible for providing personnel responsible for 100% of all CM-related activities within CIO. The CM personnel assigned to this task should have expert knowledge of the government supplied tools (Serena Software’s TeamTrack and Version Management System (VMS)).

6.1.8.7 The contractor will provide and assign a configuration manager that will be responsible for overseeing all system releases to ensure the established policies and procedures are being followed and all software code and configurations are maintained under configuration management control. All system baselines will be documented in sufficient detail by the contractor to allow for full system recovery from established CM procedures.

6.1.8.8 The contractor will be responsible for providing training on software configuration management tools, policies, and procedures. Training will be provided as requested by the Government TO COR and/or at the discretion of the lead configuration manager. Tools used in support of configuration management activities include Version Manager and TeamTrack.

6.1.8.9 The contractor will be responsible for documenting and delivering the metrics associated with each change to the production system baseline (version release). Each version release metrics report will include the following information:

1. Problem Change Request (PCR) Metrics

a. Number of PCRs originally assigned to release

b. Number of PCRs removed from the release

c. Number of PCRs added to the release

d. Number of Final PCRs assigned to the release

e. Number of PCRs meeting code freeze

f. Number of PCRs deployed to Test

g. Number of PCRs deployed to Test post-Test Window

h. Number of PCRs passed in test environment

i. Number of PCRs deployed to Prod post-Outage Window

j. Number of PCRs that passed initial production verification

k. Number of PCRs that passed final production verification

l. Number of new PCRs generated

2. Resource Expenditure Metrics

a. Total Man-hours spent on development

b. Total Man-hours spent on production deployment

c. Total Man-hours spent on production verification testing

d. Total Man-hours spent on developer fixes (PCR rework)

3.

Percentage of Completion

a. Percentage of PCRs making it to test

b. Percentage of PCRs passing initial production verification

c. Percentage of PCRs passing final production verification

4.

Named Resources

a. Deployers

b. System/Database Administrators

c. Testers

6.1.8.10 The measures of greatest importance are the percentage of PCRs making it to test, passing initial production verification, and those passing final production verification. An acceptable standard for each measure is:

1. Percent of PCRs making it to test – 90%

2. Percent of PCRs passing initial production verification – 90%

3. Percent of PCRs passing final production verification – 95%

6.1.8.11 The CM metrics report will be included as an appendix or supporting document to the Software Version Description (SVD) document. The SVD should document all of the software code, configurations, and/or PCRs that were included in every system baseline release. The SVD may be on an individual application level, or it may combine all CIO applications that modified their system baseline during a version release activity. The SVD w/metrics is due within (5) business days following the completion of each production version release. If the team does not meet the acceptable standard for any one of the measures outlined above, a secondary report will be developed and delivered to the Government to document the reasons behind the sub-standard delivery, and the plan of action to address the issues identified. The secondary report is due within (2) weeks of the version release.

6.1.9 Subtask 7 – Troubleshooting/Technical Help Desk Support

6.1.9.1 The contractor will work with the Intranet Support Help Desk to resolve technical issues identified by the DISA user population or its customers.

6.1.9.2 The contractor will be responsible for monitoring help desk tickets pertaining to technical issues that cannot be resolved by Help Desk personnel, troubleshooting these issues, and updating Help Desk personnel on their status.

6.1.9.3 Additional FTEs are not required under this subtask as they are assumed to be absorbed by each specific engineering task.

6.1.10 Subtask 8 – DISA Financial Management System (DFMS) Application

6.1.10.1 The contractor will assist in the operation and maintenance of the DFMS applications, servers, and databases. The DFMS application is primarily a custom, GOTS software system developed by CIO contractors over the last six years. The current version of DFMS is a .ASP application running on Windows 2003 servers and utilizing Internet Information Server (IIS) 6.x. The DFMS application consists of an enterprise financial management database that serves as the data repository for a number of financial‑related applications. Knowledge of the DFMS (i.e., previous experience with) is highly encouraged due to little system documentation is currently available.

6.1.10.2 The majority of DFMS activities planned for the period of performance is O&M of the current system. The only enhancements planned at this time include the continued redesign of the DFMS database. PCRs from the user community drive a significant portion of the front-end user interface enhancements. Traditionally, there are a number of database scripting tasks that are required, including developing SQL queries, triggers, views, etc. to be able to provide end-users and other system managers with the DFMS data they need. This will continue to be the case for the coming year. Finally, the DFMS administrator/developer will be responsible for ensuring the application integrates with the DISA Enterprise SSO service to enable user account authentication to the DFMS application.

6.1.11 Subtask 9 – Knowledge Tree (KT) Application and Database Maintenance

6.1.11.1 The contractor will provide personnel to be responsible for the operation and maintenance of the KT applications, servers, and databases. The KT application is primarily a COTS product (Knowledge Tree Document Management) with contractor developed customizations and configurations added to the software baseline.

6.1.11.2 The contractor will be responsible for providing personnel to maintain the software system developed by CIO contractors over the last three years. It utilizes the current version of KnowledgeTree enterprise document management and workflow product. The application runs on the Apache Tomcat J2EE application server, uses Windows IIS 6.0 as the webserver, and connects to an Oracle database backend.

6.1.11.3 The majority of KT activities planned for the period of performance are O&M of the current system. PCRs from the user community drive a significant portion of the front-end user interface enhancements. Traditionally there are a number of workflow development/configuration tasks, user account management activities, and report design and development efforts. The KT developer/administrator will also be responsible for a number of user account management activities. Finally, the KT administrator/developer will be responsible for ensuring that the application integrates with the DKO SSO service to enable user account authentication to the KT application.

6.1.12 Subtask 10 – SharePoint Application

6.1.12.1 This contractor will provide personnel responsible for a full system life cycle support for all current and new application development projects and initiatives within the Microsoft SharePoint framework.

6.1.12.2 The contractor will provide personnel an expert on the Microsoft SharePoint product to support design, development, implementation, integration, consolidation (with other instantiations of SharePoint with the agency, if directed by management), and operations and maintenance.

6.1.12.3 The contractor will perform system architecture, capacity assessments, and recommend plans for system changes or upgrades.

6.1.12.4 The contractor will perform system architecture change and upgrade plans approved by the Government. The contractor will provide SharePoint end user training to personnel when requested by the Government COR/TO COR.

6.1.12.5 The contractor will provide development support for deployed customizations and configurations, application administration, system troubleshooting, software patch installation, and coordination with Microsoft technical support on all identified software issues.

6.1.12.6 The majority of SharePoint activities planned for this period of performance is all of the effort that supports the initial implementation of the agency's SharePoint instantiation in one of DISA's computing centers, which will consist of basic OOTB SharePoint functionality (Phase 1/Baseline) in a DoD secure environment. Future enhancements will be delivered in planned phases.

7. Place of Performance Primary Place of Performance The Contractor shall perform work in Government provided office space located in the DISA Headquarters campus located on Fort Meade, MD.

Alternate Place of Performance Contractor employees may be required to work at home, another approved DISA activity within the local travel area, or at the contractor's facility in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, etc.). Any equipment such as laptops or phones provided to Contractor personnel shall be returned at the termination of the engagement or at another time mutually agreeable to both parties. Contracting Officer Representative (COR)/Task Order COR (TO COR) approval is required. Contractor shall prepare all deliverables and other contract documentation utilizing contractor resources. The contractor shall continue to provide the same level of support as stated in the PWS. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer may request an equitable adjustment.

8. Travel Requirements Contractor travel is anticipated to support the requirements named in this document. The Contractor shall project anticipated travel in the quote, and obtain approval from the COR/TO COR prior to actual travel. The Contractor shall submit invoices for direct costs related to travel no later than 30 days following the end of travel. Travel, per diem, and other direct costs will be reimbursed in accordance with the US Government Joint Travel Regulations (JTR).

9. Period of Performance The period of performance for this Task Order is twelve (12) months from date of award.

10. Delivery Schedule Due dates for all deliverables assocated with this Task Order are identified in the table below.

Final: 30 Calandar Days after contract award

Windows 7

1. Image Design for NIPR and SIPR.

2. Initial Operational Capability (IOC) Results & Recommendations Document

Windows 7

1. Image Design for NIPR and SIPR.

2. Initial Operational Capability (IOC) Results & Recommendations Document

Final: Due 60 days after contract award

Final: Due as negotiated with Government TO COR

Final: Due as negotiated with Government TO COR

Project Server:

1. Architecture

2. Design Spec

3. Production Implementation Plan

Draft: Due 30 Business Days after contract mod

Final: Due as negotiated with Government TO COR

9 Performance Requirements Summary (PRS)

The contractor is required to meet all performance standards specified in the summary below at the acceptable quality level (AQL).

11. Service Level Agreements and Performance Metrics

INCLUDE ANY PERFORMANCE MEASURES OR REFERENCE THE APPENDIX FOR SERVICE LEVEL AGREEMENTS

12. Security Requirements The work to be performed under this contract is up to and including the Secret level and positions are IT-II for systems access. All personnel performing services under this contract will be designated ADP Sensitivity Level II (ADP-II), and will have a favorably completed National Agency Check (NAC), or an Interim Secret clearance prior to performance.

The Contractor will forward a Visit Authorization Letter (VAL) to the Primary COR listed at beginning of this PWS for all employees prior to the beginning of each contracting/task order period of performance and as new contractor employees are assigned to the contract:

The VAR/VAL should be sent via one of two methods.

12.1.1 Method One

Per direction of DISA Security and the Chief of Security for Computing Services Operations, Visit Authorization Letters (VALs) or Visit Requests (VARs) for contract personnel that will be working for Computing Services either on- or off-site will be forwarded via Joint Personnel Adjudication System (JPAS) to the VAR Center using the following SMO Code: DKABAA10.

For those companies submitting the VALs via JPAS, they will also provide a copy of the VALs to the TO CORs of the contract for creation of records in the Contractor Verification System (CVS) so that Common Access Cards can be obtained for the contractors that require them.

12.1.2 Method Two

For those companies that do not have the capability to send VALs via JPAS, they can send the VALs via e-mail to the TO CORs.