ADGSS_ATTACHMENT_B_TASK_ORDER_0001_(AVAILABILITY_OF_FUNDS).pdf

ATTACHMENT B: TASK ORDER 0001 (Availability of Funds) FSA SERENA DEPLOYMENT FOR FIMs PHASE 2 STATEMENT OF WORK (SOW)

1.0 Scope.

Federal Student Aid’s (FSA’s) current technical and application architecture environment contains a wide range of client-server, web-based, database, and commercial off-the-shelf (COTS) software systems. For the purposes of this requirement, the Serena Service Manager 2.0, Serena Work Center, and Serena Business Manager 10.1.5.1 or greater will be utilized as the development platform.

The business goal of this initiative is to continue the phase improvement of the FOIA Integrity Management system (FIMs). Phase 1 (deployed into production in 2014) focused on the FOIA request, task assignment, and request summary of simple requests.

The primary operational focus of FIMs Phase 2 is on improving cost recovery functionality; and, integration with the Department’s FOIAXpress system. The areas of development include:

A. Phase 1 – FIMs Function Enhancements:

A.1. FIMs Phase 1 outstanding backlog enhancement items. Reference Appendix B – FIMs

Phase 1 Backlog A.2. Enhanced reporting capabilities to track trends and other metrics

B. Phase 2 - Bidirectional seamless integration with FOIAXpress:

B.1. Support a two-way sync between FOIAXpress and the FIMs solution

B.1.1. Ability to automatically receive FOIA request in FIMs as they are generated in FOIAXpress

B.1.2. Ability to automatically update FIMs request summary (including cost recovery) information back to FOIAXpress

B.2. Ability to render documents stored in FIMs from FOIAXpress

Vendor is to provide customized development including workflow applications and operational reporting using the Serena Business Manager (SBM) & Serena Service Management (SSM) & Serena Work Center software tools in FSA’s Enterprise Business Collaboration (EBC).

The objective is to use Vendor services to enable the FSA’s Technology Office and Correspondence Services Team to deploy improved FIMs enhancements to the Phase 1 solution, and provide a bidirectional seamless integration with FOIAXpress and the FSA FIMs solution (FIMs Phase 2).

2.0 Background.

The FIMs integration with FOIAXpress currently involves a number of manual steps supported by Microsoft Office based tools, duplicating data and documents in disparate systems. Many of these tools will require redesign in view of current business needs and be integrated within a workflow structure to offer users within FSA and the Department of Education FOIA Community visibility and control over the overall process. The Vendor shall support the development of custom solutions using SBM and FSA connectivity tools to improve the current manual business processes and integration with FOIAXpress.

FSA SERENA DEPLOYMENT FOR FIMS PHASE 2 SOW 1

2.1 Current and Development Software Architecture.

A. Databases: Oracle, MySql, SQLServer;

B. Microsoft (2010) suite of tools: (Access, Word, Excel, Outlook, PowerPoint, Project, Visio);

C. Development languages: C, C#, .Net, TCL, Java, HTML, JQuery, JavaScript;

D. Frameworks: .Net primarily used with SharePoint projects; JEE custom web applications E. Technology: UML: Primarily used in requirements and design documentation; XML; XSLT;

F. Architectural Components:

1) Visual Studio – used on .Net and SharePoint system design projects;

2) IBM WebSphere Application Server:

G. Web services technologies: SOAP, WSDL, and UDDI;

H. IBM Rational CLM solution:

a) Rational Team Concert (RTC) – Change Management

b) Rational Requirements Composer (RRC)

c) Rational Quality Manager (RQM)

d) Rational Functional Tester (RFT)

I. Configuration management: ClearQuest, ClearCase, CVS J. Firewall and intrusion detection software;

K. Data management products: ER/Studio for Embarcadero L. Enterprise Business Collaboration (EBC) Software and Services. Reference Appendix B – EBC

Software & Services

2.2 FSA Compliance Requirements.

A. FSA IT Standards: https://studentaid.ed.gov/about/contracting-info/it-standards) B. Enterprise Test Management Standards: https://studentaid.ed.gov/about/contracting-info/it-standards#fsa-testing C. Lifecycle Management Methodology (LMM) https://studentaid.ed.gov/about/contracting-info/it-standards D. FSA Compliance Requirements - Reference Appendix A

2.3 Requirements.

A. Elicit and document the detail functional and technical requirements to support the three key functional development areas defined above.

B. Deploy and configure the FIMs Phase 2 solution to meet business objectives through listening to and reviewing documented customer requirements and legacy system design (FIMs Phase 1).

C. Develop solution design documents based on approved functional and technical requirement documents.

D. Define technical and business solutions and perform incident level resolutions at an expert level for all incidents in Serena Business Manager.

E. The Vendor shall collaborate with FSA, its partners and other vendors, as identified by the TO COR, to develop best system administrative practice(s) and reliable technical solutions between Enterprise Business Collaboration (EBC) environment and SharePoint internal facing environment.

FSA SERENA DEPLOYMENT FOR FIMS PHASE 2 SOW 2

https://studentaid.ed.gov/about/contracting-info/it-standards https://studentaid.ed.gov/about/contracting-info/it-standards%23fsa-testing https://studentaid.ed.gov/about/contracting-info/it-standards%23fsa-testing

F. Ability to electronically update FOIAXpress with FIMs cost recovery information Permission based access to workflows

G. Creation of applications & workflows with conditional routing, alerts and reminders H. Adding and managing user groups and roles I. Design intelligent forms J. Operational reports for the FOIA management and FOIA Business Unit personnel K. Deployment of applications to test and production environments L. The ability to generate, print and/or save to PDF FOIA cost recovery forms M. Ability to electronically receive FOIA requests when updated to FOIAXpress

2.4 Key Personnel.

The Government requires a balanced team of key personnel to ensure that both operational and technical aspects of the contract are successful. 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 the contract.

Therefore, the Government encourages and will evaluate additional Key Personnel as proposed by the contractor.

A. Project Manager - Responsible for ensuring that the IPT completes the project; collaborates with the IPT to develop the Project Plan or Work Book Schedule;; manages the team’s performance of all project tasks; secure acceptance and approval of deliverables from the Business Owner and responsible stakeholders; responsible for communication, including status reporting, risk management, escalation of issues that cannot be resolved within the IPT; ensures the project is delivered on budget, on schedule, and within scope.

A. Business Systems Analyst (Intermediate) - Works with the business to elicit and document requirements appropriate to project size and complexity. Knowledge transfer to development and test teams. May be team lead for business analysts. Collaborates with team and escalates issues to COR/CO as necessary. Experience with:

1) IBM Rational CLM solution:

a. Rational Team Concert (RTC) – Change Management

b. Rational Requirements Composer (RRC)

c. Rational Quality Manager (RQM)

d. Rational Functional Tester (RFT)

B. Serena Solution Development Specialist (Senior) - Makes solid recommendations based on analysis and provide explanations for operational results for business users; Design/implement workflows within SBM; Routine maintenance and monitoring of SBM system, documentation and testing; in collaboration with the BA will help to lead users through requirements gathering, definition, and documenting the requirements; Support the IPT in the requirements gathering and documentation, analysis, design, development, testing, demonstrating and deploying Serena SBM workflows to meet user's requirements; Update SBM application software components; Oversight SBM activities include: Workflow Design including Sub tasking/Post Items, Application Scripting, Relational/Sub-relational fields, Auxiliary tables (Interactive and

FSA SERENA DEPLOYMENT FOR FIMS PHASE 2 SOW 3

externally managed), Security/groups and roles design. Notifications including: Rules, Escalations, Email Recorder Features, Custom Forms Design including: JavaScript/jQuery, Form Actions, Embedded Objects/Reports, Reporting to include Extensive Report Design (within user environment), Dashboards, Calendar Reports, Multi-table reports, Embedded SQL inside report parameters, Work Center, Feature Design, Troubleshooting; Specialized experience using Orchestrations and web services with an understanding of APIs; Data Importing; Routine monitoring of SBM logs; Troubleshoot complex problems that come from end users that require research and new solutions; Define and implement application level architecture design

While the vendor will be held responsible for delivering quality functioning code, a separate requirement for testing each Sprint and end-to-end System testing will be sent out via a separate RFQ.

Per standard practice, a separation of duties between software development and system testing is required.

The Vendor resource must possess the following competencies:

All key personnel shall meet the following criteria:

a) Hold or be able to hold a 6C Public Trust security clearance.

b) Qualifications are submitted to Government for review and approval.

c) Be available during normal working hours.

d) Given two hours’ notice, be able to meet with designated Government personnel, including the

Contracting Officer and the Contracting Officer’s Technical Representative.

2.4 Resource Capabilities.

A. Ability to develop a formed implementable detailed functional requirements document; to include use cases; wireframes; product backlog; user stories; data specification and data model.

B. Ability to quickly understand, develop enhancements to, implement and interface to already functioning business process workflow solutions, including, but not limited to, forms, workflow processes, detail scripting and data models.

C. Ability to develop effective strategies in reusing components to minimize ongoing operations and maintenance costs.

D. Ability to provide three levels of software testing (unit, integration & per-system testing).

E. Ability to develop Serena business process models, user interface development, reporting, configuration management, security models, and overall solution architectures based on Serena best practices.

F. Ability to configure Serena and other FSA tools to interface with web services for the purposes of creating a bidirectional seamless integration with FOIAXpress

G. Possess administration and custom development experience with Serena Business Manager, Serena Service Management and Serena Work Center Software tools.

H. Ability to perform development activities in an agile development process, including several “Sprints” that deliver functioning workflows.

I. 6C Public Trust security clearance.

FSA SERENA DEPLOYMENT FOR FIMS PHASE 2 SOW 4

2.5 Place and Hours of Performance.

The work will be performed primarily at the Contractor’s facility. Occasional travel will be required to FSA’s headquarters located at 830 First Street, NE, Washington, DC, 20202, as requested and approved by the COR or in specific TOs.

When working at Government facilities, work will be accomplished during normal duty hours (8 AM - 5 PM) unless otherwise approved by the COR.

A project schedule, including identified on-site days, shall be developed within 30 days of award with the TO COR, FSA Project Manager, and Vendor.

2.6 Period of Performance.

The period of performance shall be seven (7) months from date of Task Order Award.

2.7 Project Milestones.

The following table is a draft schedule of the proposed Sprints. The actual Sprint content and schedule shall be determined based on discussions with the vendor and FSA staff, with approval by the FSA Contracting Officer

Project Milestones Duration Phase 1 - Phase 1 Enhancement Backlog 50 days Phase 1 - Detailed Design Document Update Phase 1 - Detailed Requirements Document Update Phase 1 - Phase 1 Enhancements backlog are identified in red in … Phase 1 - Testing (unit, integration) Phase 1 - Testing (end-to-end system testing) Phase 1 - Implementation Plan Phase 1 - Deploy solution into production environment Phase 2 - Bidirectional seamless integration with FOIAXpress 90 days Phase 2 - Detailed Requirements Document Update Phase 2 - Detailed Design Document Update Phase 2 - Design Proof of Concept Phase 2 - Development Phase 2 - Testing (unit, integration) Phase 2 - Testing (end-to-end system testing) Phase 2 - Implementation Plan Phase 2 - Service Delivery Review (SDR) Phase 2 - Test Readiness Review (TRR) Phase 2 - Production Readiness Review (PRR) (w/ Security Documents)

FSA SERENA DEPLOYMENT FOR FIMS PHASE 2 SOW 5

Phase 2 - Solution Source Code Phase 2 - Deploy solution into production environment

2.8 Deliverables.

The table below identifies scheduled due dates (To be determined at award), deliverable alignment with FSA’s Lifecycle Management Methodology (LMM), and the type of review, classified as Delivery Standard (DS). The numbers of days listed in the deliverable schedule are business days. All deliverables will be accepted according to the deliverable review and acceptance guidelines. Please note that update cycles will repeat until Contractor deliverables are accepted.

Once awarded the Contractor shall provide the Deliverable Schedule dates for Government approval.

Deliverables shall be provided according to a schedule that meets the Government’s availability for review – do not provide more than three deliverables for review per review cycle.

Delivery Standard (DS)

a. 10 business days for FSA to review and comment

b. 5 business days for Contractor to respond with updates

c. 5 business days for FSA to accept/reject updates

Acceptance Criteria:

The Contractor shall provide the deliverables identified in the following Deliverables List in accordance with the schedule approved by the Government. The Contractor may be required to provide additional deliverables either upon Government request or as proposed by the Contractor. In addition, the Contractor shall update deliverables as necessary or as directed.

All deliverables shall be in the format as stated by the FSA’s Lifecycle Management Methodology (LMM) and the templates and exemplars in LMM standards library. All documentation shall be free of grammar and typo errors and provide details in plain English for stakeholders.

Deliverable Acceptance Criteria Schedule

Work Breakdown Schedule

The Contractor shall submit a detailed project schedule or WBS. The WBS shall include the project milestones, stage gates, tasks, duration’s resources and dependencies.

10 days after TO award

Functional/Technical Requirements Document

The Contractor shall submit update FIMs 1.0 requirements document detailing FIMs 2.0 functional/technical requirements approved by the business owners and Integrated Project Team.

Based on TO work breakdown schedule

(WBS)

FSA SERENA DEPLOYMENT FOR FIMS PHASE 2 SOW 6

Updated FIMs Design Document

The Contractor shall update FIMs release 1.0 design document detailing the design options and approach to satisfy FIMs release 2.0 requirements.

Design document will continue to follow FSA standard system design document format as described in the http://studentaid.ed.gov/about/contracting-info/it-standards template.

5 days before the start of each new Phase

Requirement Decomposition - Agile/Scrum Artifact by Sprint includes:

Epics; Stories; tasks

The contractor shall provide a decomposition of all requirements described in the FIMs requirements document Phase II. The contractor will decompose the use cases specific to FIMs Phase II describing the Epic (describing high level pieces of functionality) Stories (smaller discrete pieces of functionality) Tasks (steps taken to complete a story). User stories should describe how the requirement(s) are going to be implemented.

5 after the design document is approved

User Demo(s) At the end of each sprint the contractor shall participate in the sprint review with the system product owners. The contractor will walk through and demo all the requirements/stories completed for each sprint. The product owner will sign off on all successfully completed and error free stories.

As specified in the project schedule

Unit, Integration & Pre-System Test Cases (functional and non-functional for all testing types)

Test cases for unit, integration & pre-system testing. Test cases should be clearly documented with appropriate steps for retesting. The contractor shall follow FSA's Enterprise Test Management Standards to enable seamless transition/communication with the independent system test vendor.

Based on TO work breakdown schedule

(WBS)

New Software Builds Based on approvals received from the product owners during the sprint review the contractor shall provide an error free deployable build. The build shall include all requirements/stories earmarked as the scope of work for the sprint.

As specified in the project schedule

Update Implementation Plan

The contractor shall update the implementation plan describing in detail the steps to deploy the updated code to test, stage & production.

As specified in Project Schedule

Only the TO COR or TO CO can formally accept work products and or deliverables.

FSA SERENA DEPLOYMENT FOR FIMS PHASE 2 SOW 7

2.9 Type of Contract/Payment Schedule.

The contract is to be on firm fixed price basis.

The specific requirements for scheduled time on site will be determined early in the planning for this contract. TO COR with the PM will work with the vendor to establish scheduling. Schedule will be developed in accordance with FSA’s overall project schedule for this phase. Once completed the TO COR will approve agreed schedule to be used.

Appendix B – EBC Software & Services.

Product Current Versions Bamboo Solutions - List Rollup 6.0 Bamboo Solutions - Poll Webpart 1.4 HiSoftware Compliance Sheriff for SharePoint 3.2.4 Idera Diagnostic Manager 2.7.1.2 Idera Enterprise Manager 4.9.6 K2 Blackpearl (4.6.8) 4.12060.1600.0 K2 Case Management Framework K2 for SharePoint 2010 (4.6.8) 4.12060.1600.0 Metalogix Control Point 5.4 Metalogix Diagnostic Manager 4.1 Metalogix Migration Manager 5.0.1.11 Metalogix Migration Manager (Web Service Extention) 5.0.1.11 Metalogix Migration Manager for SharePoint - File Share 4.2.1100 Metalogix SharePoint Extensions Webservice 4.1.1307 Metalogix Storage Point 4.1 Microsoft Fast Search Server 2010 for SharePoint (October Hotfix - KB2553402) 14.0.6126.5002 Microsoft Office Communications Server

2007 R2 (OCS) 3.5.6907.0

Microsoft Project Server 2010 (June 2014

CU) 14.0.7125.5000

Microsoft Project Server 2010 SP2 (November 2014 CU) 14.0.7125.5000

FSA SERENA DEPLOYMENT FOR FIMS PHASE 2 SOW 8

Microsoft SharePoint Designer 2010 14.0.6029.1000 Microsoft SharePoint Server 2010 Enterprise (SP2) - (June 2014 CU) 14.0.7125.5002 Microsoft SharePoint Server 2010 Enterprise (SP2) - (November 2014 CU) 14.0.7137.5000 Microsoft SQL Server 2008 R2 (SP2) 10.52.4000.0 OCS\Archiving Server 3.5.6907.0 OCS\Monitoring Server 3.5.6907.0 Office Web Applications 2010 14.0.7015.1000 Serena Business Manager 10.1.4.1 Serena Service Manager 5.2.0 Serena Work Center

Team Improver OrgChart Web Part 3.9 UMT Project Essentials 2.0.4816.1002

FSA SERENA DEPLOYMENT FOR FIMS PHASE 2 SOW 9