Appendix A Statement of Work.docx

SOW for DS Specialized Iterative Software Development and Support Services

SBU - CONTRACTING AND ACQUISITIONS

Table of Contents

1. INTRODUCTION

1.1. BACKGROUND

The purpose of this Task Order is to provide the Office of the Chief Technology Officer (DS/EX/CTO) technical support for the development, evolution, enhancement and deployment support (Integration) to the Regional Security Office Local Vetting (RESOLVE), Industrial Security Management System (ISMS), Domestic Workers Management System (DWMS),Security Incidents Management and Analysis System (SIMAS), and other applications developed under the ArrisFederal Base Platform (ArrisFed). Task support will also include development, evolution, enhancement and deployment support (Integration) for the integration of threat and intelligence management and reporting components into existing or updated systems.

1.2. AGENCY MISSION

The U.S. Department of State is the lead institution for the conduct of American diplomacy and the Secretary of State is the President’s principal foreign policy advisor. The Foreign Service is a corps of more than 12,000 employees dedicated to representing the United States of America abroad and responding to the needs of United States citizens living and traveling around the world. The Department’s Civil Service, totaling more than 9,000 employees, provides continuity and expertise in accomplishing all aspects of the Department’s mission. There are also more than 37,000 Foreign Service National Staff at overseas posts.

1.3. SCOPE

The scope of this Task Order is to acquire technical support for CTO in the full software development life cycle (SDLC) which includes development, evolution, enhancement and deployment for CTO applications such as RESOLVE, ISMS, DWMS, SIMAS and other Arris Federal based applications. Task support will also include development, evolution, enhancement and deployment support (Integration) for the integration of threat and intelligence management and reporting components into existing or updated systems and technical support for CTO process management and administration initiatives. All development and implementation work needs to adhere to all applicable security requirements and standards (ex. NIST, FISMA, etc.).

2. PERFORMANCE BASED SCOPE OF WORK

2.1. TASK 1 – PROVIDE PROJECT MANAGEMENT

The Contractor shall provide program management and project management support under this Task Order. This includes the management and oversight of all activities performed by Contractor personnel, including subcontractors, to satisfy the requirements identified in the Performance Based Scope of Work (PBSOW). The Contractor shall identify a Project Manager (PM) by name who shall provide management, direction, administration, quality control, and leadership of the execution of this Task Order. The PM shall facilitate high- level task order management activities and shall oversee the work and shall execute low- level DS/CTO specific project management tasks defined by the Office’s pre-defined Project Life Cycle (PLC).

2.1.1. SUBTASK 1 – COORDINATE A PROJECT KICK-OFF MEETING

The Contractor PM shall schedule and coordinate a Project Kick-Off Meeting at the location approved by the Government. The meeting will provide an introduction between the Contractor personnel and Government personnel who will be involved with the Task Order. The meeting will provide the opportunity to discuss technical, management, security issues, and travel authorization and reporting procedures. At a minimum, the attendees shall include Key Contractor personnel, key stakeholders, and any other relevant Government personnel. The Contractor shall provide the following at the Kick-Off meeting:

· Draft Project Management Plan (PMP)

2.1.2. SUBTASK 2 – PREPARE A MONTHLY STATUS REPORT (MSR)

The Contractor PM shall develop and provide an MSR using Microsoft (MS) Office Suite applications, by the 10th of each month via electronic mail to the Technical Point of Contact (TPOC) and the COR. The MSR shall include the following:

· Activities during reporting period, by task (include: on-going activities, new activities, activities completed; progress to date on all above mentioned activities). Start each section with a brief description of the task.

· Problems and corrective actions taken. Also include issues or concerns and proposed resolutions to address them.

· Personnel gains, losses, and status (security clearance, etc.).

· Government actions required.

· Schedule (show major tasks, milestones, and deliverables; planned and actual start and completion dates for each).

· Summary of trips taken, conferences attended, etc. (attach trip reports to the MSR for the relevant reporting period).

· Accumulated invoiced cost for each CLIN up to the previous month.

· Projected cost of each CLIN for the current month.

2.1.3. SUBTASK 3 – CONVENE TECHNICAL STATUS MEETINGS

The Contractor PM shall convene a monthly Contract Activity and Status Meeting with the TPOC, COR, and other vital Government stakeholders. The purpose of this meeting is to ensure all stakeholders are informed of the monthly activities and MSR, provide opportunities to identify other activities and establish priorities, and coordinate resolution of identified problems or opportunities. The Contractor PM shall provide minutes of these meetings, including attendance, issues discussed, decisions made, and action items assigned, to the COR within the timeframe specified in Section 3.4 following the meeting.

2.1.4. SUBTASK 4 – PREPARE A PROJECT MANAGEMENT PLAN (PMP)

The Contractor shall document all support requirements in a PMP. The PMP shall:

· Describe the proposed management approach.

· Contain detailed Standard Operating Procedures (SOPs) for all tasks.

· Include milestones, tasks, and subtasks required by this Task Order.

· Provide for an overall Work Breakdown Structure (WBS) and associated responsibilities and partnerships between Government organizations.

· Include the Contractor’s QCP.

The Contractor shall provide the Government with a draft PMP at Kick-Off meeting, upon which the Government will make comments within timeframe specified in Section 3.4. The final PMP shall incorporate the Government’s comments within timeframe specified in Section 3.4.

2.1.5. SUBTASK 5 – UPDATE THE PROJECT MANAGEMENT PLAN (PMP)

The PMP is an evolutionary document that shall be updated annually at a minimum. The Contractor shall work from the latest Government-approved version of the PMP.

2.1.6. SUBTASK 6 – UPDATE QUALITY CONTROL PLAN (QCP)

The Contractor shall update the QCP submitted with their quote and provide a final QCP as specified in Section 5. The Contractor shall periodically update the QCP, as specified in Section 5, as changes in program processes are identified.

2.1.7. SUBTASK 7 – PERFORM DS/CTO PROJECT LIFECYCLE ACTIVITIES

The Contractor Project Manager (PM) shall perform low-level project management activities as required by the DS/CTO Project Life Cycle (PLC). These activities include producing project management artifacts along with facilitating reviews and acceptance of the management work products.

2.1.8. SUBTASK 8 – PREPARE TRIP REPORTS

The Government will identify the need for a Trip Report when the request for travel is submitted. The contractor shall keep a summary of all long-distance travel including, but not limited to, the name of the employee, location of travel, duration of trip, and point of contact (POC) at travel location.

2.2. TASK 2 – DEVELOPMENT, EVOLVE, ENHANCE AND DEPLOY UPDATES AND INTEGRATION TO SUPPORTED SYSTEMS

The Contractor will provide technical and analytic support to CTO in the development, implementation and integration of several enhancements for the evolution of the Regional Security Officer Local Vetting (RESOLVE), Industrial Service Management System (ISMS), Domestic Workers Management System (DWMS), Security Incidents Management and Analysis System (SIMAS) and other on-going systems. Support will include the integration of threat and intelligence management and reporting components into new, existing or updated systems. The systems will provide a collaborative platform as the primary workflow application to maintain a centralized view of all interactions and interfaces relative to case management activities. These systems will operate in parallel with legacy systems with implemented components integrating more effective web-based architectures. The components enhanced and developed in this activity will be produced using an iterative and modular methodology to support interoperability to reduce risk and support rapid delivery of incremental functionality.

This effort is managed by CTO in a blended environment where no one vendor has direct control over the product outcome; rather CTO is the integration manager for the component or modular level products.

All work is overseen by CTO to meet federal and Bureau performance requirements and must support government-wide initiatives related to the control, handling and dissemination of classified and controlled unclassified information, and be compatible with other agency systems to support Information Sharing Environment initiatives. The Contractor, in concert with CTO staff, will support activities under the following subtasks:

2.2.1. SUBTASK 1 – IMPLEMENTATION PLAN

The Implementation Plan shall be to develop, edit/update, review and/or evaluate implementation as requested in order to accurately describe the tasks necessary to develop and implement several features into a security / criminal investigations management and reporting system existing within the Bureau’s technical environment. Implementation development, corrections, updates, reviews and/or evaluations will be conducted on the supporting documentation existing or prepared for CTO in support of the system. CTO management will provide review, comment and approval of implementation plans.

A status on activities, findings, recommendations and risks shall be included in the Weekly Task Order Report.

2.3. IMPLEMENTATION ACTIVITIES

Conduct software development and implementation activities in support of Subtasks 1 and perform the technical tasks necessary to develop, deploy, and support numerous enhancements to the Regional Security Officer Local Vetting (RESOLVE), Investigative Management System and Security Incidents Management and Analysis System (SIMAS). Provide analysis and support to other identified security / criminal investigations, intelligence and threat management and reporting systems existing in the Bureau’s technical environment. Known features and enhancements include:

a. Preliminary Inquiries and other new security incident types

b. Enhancements to Information Discovery, Analytics, and Batch Processing

i. Enhanced Analytics Capabilities

c. Information Sharing

i. NIEM-Compliant Data Feed

ii. Enhanced Application Capabilities

iii. Integration with other DS systems including DSIAS, HITS, and myLGP / RSOTools and others which may be developed during the course of this order

d. Geospatial Enhancements (Scope / timeframe TBD determined by CTO FTE)

i. Incorporate external Properties Data Feed as a layer

ii. Incorporate additional geo layers with custom icons, controls and security attributes for each

iii. Other Geospatial Enhancements

e. Innovation & Future Considerations

i. Proof-of-Concepts / Prototypes

ii. Data Visualizations

iii. Capture requirements for future considerations

2.3.1. ACTIVITY 1: INFORMATION DISCOVERY, ANALYTICS, AND BATCH DATA PROCESSING

The Contractor shall perform engineering activities for capabilities supporting Information Discovery, Analytics, and batch Data Processing.

Such activities shall include:

a. Produce a system integration design describing integration of the existing security reporting system with the data processing cluster systems;

b. Building initial analytics capabilities utilizing the newly created data processing environment;

c. Provide enhancements to the existing Information Discovery capabilities within the security reporting system.

Deliverable: System integration design Deliverable: Functioning information discovery and analytics capabilities.

2.3.2. ACTIVITY 2: INFORMATION SHARING/DATA EXCHANGE

The Contractor shall engineer and build, enhance or modify information sharing and data exchange capabilities for existing security management and reporting systems (RESOLVE, ISMS, DWMS, and SIMAS). These capabilities shall be in support of data sharing with external (non DOS) entities. Where appropriate, the Contractor shall enhance the existing security incident reporting system to provide technical capabilities facilitating the information sharing initiative (e.g. new roles and/or workflows) and supporting needed data exchange interfaces.

Deliverable: Functioning system enhancements supporting the data sharing initiative. Deliverable: Functioning generation of XML for data sharing: NIEM Compliant XML and/or ISE-SAR Functional Standard 1.5 compliant.

2.3.3. ACTIVITY 3: GEOSPATIAL ENHANCEMENTS

The Contractor shall implement various geospatial enhancements to the existing security reporting system if directed by the CTO FTE / Product Owner. The Contractor shall enhance the existing system to consume and display diplomatic facility and property data on read-only layers of the map (from a Data Feed). The Contractor shall also provide enhancements to support additional editable geo layers (including appropriate security controls for viewing, creating, editing, and deleting features). Various other geospatial enhancements may be defined and prioritized by DS/CTO. Prioritization of these other enhancements will be performed with regard to the status and priority of other activities defined in this task order.

Deliverable: Functioning geospatial system enhancements: as determined by DS/CTO.

2.3.4. ACTIVITY 4: SOLUTION ARCHITECTURE AND DESIGN

The Contractor shall provide a Solution Architect to deliver solution architecture and design services in support of the engineering activities of this task order.

The activities shall include producing architectural design artifacts, detailed design artifacts, and facilitating the realization of these designs in the resulting system enhancements.

Deliverable: Architecture Designs and Software Designs.

2.3.5. ACTIVITY 5: USER EXPERIENCE DESIGN/SECTION 508 COMPLIANCE

The Contractor shall provide a User Experience Designer to deliver user experience and user interface (UI) design services in support of the engineering activities system capabilities of this task order. The designs shall include HTML5 and CSS considerations.

All electronic and information technology (EIT) products and services produced or procured through this contract must meet the applicable accessibility standards at 36 CFR 1194, unless an agency exception to this requirement exists. 36 CFR 1194 implements Section 508 of the Rehabilitation Act of 1973, as amended, and is viewable at http://www.section508.gov. If any existing functionality or new functionality is determined to not meet Section 508 standards, the Contractor will create an implementation plan to bring the application within compliance and report the status to the CTO FTE and the Product Owner.

Deliverable: User experience and user interface designs.

Deliverable: Inclusion of interface designs into the functioning system.

2.3.6. ACTIVITY 6: SOFTWARE REQUIREMENTS DEVELOPMENT

The Contractor shall provide a Requirements and Business Analyst to perform requirements elicitation and development activities for the capabilities described under this task order. The analyst must use the current DS/CTO requirement templates.

Deliverable: Project Requirement Document(s)

2.3.7. ACTIVITY 7: INNOVATION AND FUTURE CONSIDERATIONS

As a non-primary activity, the Contractor may be tasked to support various innovation efforts for future capabilities of the security incident reporting system. This may include documenting future consideration draft requirement packages, providing rapid prototyping proof-of-concepts, generating new capability concepts, prototyping data visualizations and analytics reports, and exploration in the capabilities of cross-security domain data transfer, mobile application development, and rules-based system event processing.

Deliverable: Innovation Artifacts (e.g. proof-of-concepts, prototypes, future consideration draft requirements, etc.)

2.4. GENERAL SUPPORTING ACTIVITES

The major features identified above all require further clarification through requirements elicitation and documentation. All new major features identified for development, their requirements and technical designs, must be approved by CTO management prior to integration into the production system.

A status on software engineering activities for the development of the system shall be included in the Weekly Task Order Report. Report detail shall include descriptions of activities related to the following when applicable.

· Documentation

· Functional Specifications/Design Documents for the system.

· Software Requirements Specification Document for the User Interface

· Configuration management plan. In accordance with existing DS policies and procedures

· Implementation and Integration

· Customization, development, product configuration and performance tuning

2.4.1. SUBTASK 4 – SUPPORT DOCUMENTATION

Assist in the development of operational support documentation in support of tasks resulting from Subtask 3. The transition support documentation will provide the information needed by operations staff to support routine, common issues related to day-to- day use of the software system implemented to meet the CTO product requirements. It will provide detailed product-to-use configuration and implementation information which may be utilized in the development of an Operation’s Standard Operating Procedure (SOP).

2.4.2. SUBTASK 5 – WEEKLY TASK ORDER PERFORMANCE REPORT

Weekly Task Order Performance Report for Subtasks 1-4 shall include detailed analysis of evaluated components, comparison with other products/solutions and summary presentation briefing of the report recommendation.

2.5. TASK 3 – ARRISFEDERAL BASED APPLICATION SUPPORT

The Contractor shall provide on-going support for previously developed Arris Federal based applications such as RESOLVE, ISMS and others. Support will include software maintenance, modernization development, operational changes, upgrade support and technical corrective development. CTO will request support in this area based on validated requirements from application owners. CTO will request a project proposal and cost estimate. Each of these will be evaluated and approved by DS/CTO prior to any work proceeding in this task area.

2.6. TASK 4 – DEVELOPMENT SURGE SUPPORT

The Contractor shall provide the ability to support the ability to surges in development to one or more of the applications supported. The surge ability should allow the Contractor to support longer running development activities on projects without reducing or stopping support to the other supported applications. An example of this would be if a business / product owner had additional functionality to be implemented that significantly changed the originally planned workload for a significant period of time. Surge support requirements will be coordinated with the work area FTE and COR to discuss whether additional resources should be brought on to meet the requested schedules. This request could be based on additional functionality requested by one or more projects or the volume of the requests causing delays to one or more project schedules.

3. DRAFT DELIVERABLES

The Government will provide written acceptance, comments, and/or change requests, if any, within 10 workdays from Government receipt of the draft deliverable.

Upon receipt of the Government comments, the Contractor shall have 10 workdays to incorporate the Government's comments and/or change requests and to resubmit the deliverable in its final form.

3.1. WRITTEN ACCEPTANCE/REJECTION BY THE GOVERNMENT

The CO/COR will provide notification of acceptance or rejection of all final deliverables within 15 workdays (unless specified otherwise in Section 5). All notifications of rejection will be accompanied with an explanation of the specific deficiencies causing the rejection.

3.2. NON-CONFORMING PRODUCTS OR SERVICES

Non-conforming products or services will be rejected. Deficiencies will be corrected, by the Contractor, within 10 workdays of the rejection notice. If the deficiencies cannot be corrected within 10 workdays, the Contractor will immediately notify the COR of the reason for the delay and provide a proposed corrective action plan within 10 workdays.

3.3. TASK ORDER PERFORMANCE MEASURES AND STANDARDS

Performance measures and standards will be in accordance with Section 4.

3.4. SCHEDULE AND MILESTONE DATES

The following schedule of milestones will be used by the COR to monitor timely progress under this Task Order.

The following abbreviations are used in this schedule: NLT: No Later Than TOA: Task Order Award All references to Days: Government Workdays Deliverables are due the next Government workday if the due date falls on a holiday or weekend.

The Contractor shall deliver the deliverables listed in the following table:

Project Start (PS)

At TOA

the next month)

3.5. DELIVERABLES MEDIA

The Contractor shall deliver all electronic versions by email, as well as placing in the DS/EX/CTO designated repository. The following are the required electronic formats, whose versions must be compatible with the latest, commonly available version on the market.

Any custom developed programming code generated under this TO must be provided in its raw, un-compiled format, to the TPOC or designee for quality inspection and archival purposes.

4. PERFORMANCE REQUIREMENTS SUMMARY

Performance Standards

Refer to Section 3.4, SCHEDULE AND MILESTONE DATES

Final documentation must be in Microsoft Suite 2007 or current DOS version. Final documentation must be spell checked, grammar checked, and accepted by the Government.

100% of delivery dates specified by the PBSOW, COR and/or the SOP (if applicable) are met.

5. KEY PERSONNEL

The following are the minimum personnel who shall be designated as “Key.” The Contractor shall propose appropriate labor categories for these positions. The Government does not intend to dictate the composition of the ideal team to perform this Task Order. Therefore, the Government encourages and will evaluate additional Key Personnel as proposed by the offeror.

SME/Lead Software Engineer 2 postions The Government desires that Key Personnel be assigned for the duration of the Task Order. Key Personnel may be replaced or removed subject to the clause titled - Special Contract Requirements, Key Personnel Substitution.

5.1. SME/Lead Software Engineer

It is required that one of the SME/Lead Software Engineer possesses a Top Secret security clearance the other tat the Secret (or higher) Security clearance.

EXPERIENCE: The SME/Lead Software Engineer should possess the following:

· A minimum of 10 years’ experience related to IT systems development and IT project management;

· Significant knowledge and familiarity with Bureau of Diplomatic Security environment, technical IT applications and mission;

· At least 5 years of experience developing custom applications in .Net, Java, JavaScript & PL/SQL;

· Experience in data, object and UML modeling techniques, standards and best practices;

· Experience implementing complex systems in large enterprise environments;

· Experience leading development teams;

· Knowledgeable of DOS policy requirements for IT systems;

· Experience developing optimized data structures and reports; and

· Experience operating in a multi-vendor multi-contract environment

EDUCATION – Bachelor’s Degree, Computer, IT disciplines

6. TRANSITION / PHASE-OUT SUPPORT

Prior to the end of the final period of performance, the Contractor shall develop a Phase-Out Plan of contracted operations including a first draft at the mid-point of the last option year of the contract, with updates at 60 calendar days and 30 calendar days remaining. All plans are subject to Government-approval. The Contractor phase-out procedures shall not disrupt or adversely affect the day-to-day operations and shall result in a smooth and orderly transfer of responsibility to the successor. In the event the current Contractor is not awarded the follow-on contract the Contractor shall:

· Continue to satisfy on-going work requirements;

· Ensure incumbent Contractor personnel who are experienced in the contracted functions are available to explain procedures for performing DOS work to incoming Contractor personnel;

· Ensure that all Government-furnished property is accounted for and returned; when necessary, participate in joint inventories;

· Submit a final invoice, a final copy of all recurring reports, along with a narrative report on the success and difficulties during phase-out within 30 calendar days after the end of the Phase-Out Period; and,

· Ensure that the final invoice, reports, and all files submitted during the Phase-out Period are accurate and complete, and that these files provide the same high level of quality provided during the base and option periods.

7. Clearance Requirements Contractor is required to have a Facility Clearance of TOP SECRET. All Contractor personnel assigned to this contract shall possess SECRET or TOP SECRET personnel security clearances issued commensurate with the level of access required, prior to contract performance. Some staff may require SCI access which will be determined by the USG based on requirements.

8. Period of Performance The Contractor shall complete performance according for a base period of twelve (12) months, with one (1) twelve(12)-month options, which may be exercised at the discretion of the government.

The Contractor shall perform the services of this Task Order eight (8) hours per day between the hours of 8:15 a.m. and 5:00 p.m., with 45-minutes for lunch, Monday through Friday, excluding Federal Government holidays. All Contractor personnel shall perform during these normal working hours and must be present during the core hours of 9:00 a.m. through 3:00 p.m., Monday through Friday. Teleworking is permissible in accordance with Department policies as approved by CTO and DS on an individual basis.

9. Place of Performance The primary work location will be DS/EX/CTO offices in the Rosslyn/Arlington VA and DC metropolitan area. Work may also be authorized at the contractor’s facility, which should be located no more than 50 miles from the DS headquarters building in Rosslyn, VA.

10. Travel Local travel is anticipated for this requirement. Overseas travel that may include travel to areas designated as High Treat by the Department may also be required. Travel will be authorized based on approval of the USG Task Area Lead and the COR. Reimbursement for all travel cost will be in accordance with applicable travel regulations (domestic or overseas).