USCA18BPAC1010_v2.pdf

ORDER FOR SUPPLIES OR SERVICES

IMPORTANT: Mark all packages and papers with contract and/or order numbers.

1. DATE OF ORDER

07/17/2018

2. CONTRACT NO. (If any) 6. SHIP TO:

Office of Judiciary Data and Analysis Administrative Office of the United States Courts One Columbus Circle, N.E.

Suite 4-180 Washington, DC 20544-0001

3. ORDER NO.

USCA18BPAC1010

4. REQUISITION/REFERENCE NO.

Manish Patel, 202-502-3258 Procurement Management Division Administrative Office of the United States Courts One Columbus Circle, N.E.

Suite 3-250 Washington, DC 20544-0001

5. ISSUING OFFICE (Address correspondence to)

7. TO:

8. TYPE OF ORDER

a. PURCHASE

REFERENCE YOUR: ____________

Please furnish the following on the terms and conditions specified on both sides of this order and on the attached sheet, if any, including delivery as indicated.

X b. DELIVERY -- Except for billing instructions on the reverse, this delivery order is subject to instructions contained on this side only of this form and is issued subject to the terms and conditions of the above-numbered contract.

9. ACCOUNTING AND APPROPRIATION DATA 10. REQUISITIONING OFFICE

11. NOT USED 12. F.O.B. POINT

14. GOVERNMENT B/L NO. 15. DELIVER TO F.O.B. POINT ON

OR BEFORE (Date)

16. DISCOUNT TERMS13. PLACE OF

a. INSPECTION b. ACCEPTANCE

17. SCHEDULE

CLIN NO.

(a)

SUPPLIES OR SERVICES

(b)

QUANTITY

ORDERED

(c) UNIT (d)

UNIT PRICE

(e)

AMOUNT

(f)

QUANTITY

ACCEPTED

(g)

See Lines

SEE BILLING

INSTRUCTIONS

ON

REVERSE

18. SHIPPING POINT 19. GROSS SHIPPING WEIGHT 20. INVOICE NO.

$0.00 17(h) TOT.

(Cont.

pages)

21. MAIL INVOICE TO:

a. NAME

SHAWNIE S. QUIGLEY

b. STREET ADDRESS(or P.O. Box) Administrative Office of the U.S. Courts, Research & Statistical Modernization Div., DPS-JD-NSTA,

c. CITY Washington

d. STATE

DC

e. ZIP CODE 20544-0001

$0.00

17(i)

GRAND

TOTAL

22. UNITED STATES OF AMERICA BY (Signature)

23. NAME (Typed)

Manish Patel

TITLE: CONTRACTING/ORDERING OFFICER

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION NOT USABLE

OPTIONAL FORM 347 (REV. 02/2012)

Prescribed by GSA/FAR 48 CFR 53.213(f)

USCA18BPAC1010 - Page 1 of 19

Supplies or Services and Prices/Costs

CLIN NO. Supplies or Services Quantity Unit of Issue Unit Price Extended Amount

0001 Establish an Integrated Enterprise Data

Warehouse

0 Not-To-

Exceed

$0.00 $0.00

Extended Description:Perform migration activities in accordance with section C.3.1 and C.4.1 for the following eight (8) program areas:

For the purpose of this BPA call, the contractor shall focus on migration efforts for the following eight (8) program areas: 1) EDW - Defender Services Office

2) EDW - CM/ECF Bankruptcy

3) EDW - CM/ECF District

4) EDW - JIFMS

5) Magistrate Judge Statistics through Automated Records System (MJSTAR)

6) Delayed Notice Search Warrants (DNSW)

7) Wiretap

8) District Court Trials (DCT)

CLIN NO. Supplies or Services Quantity Unit of Issue Unit Price Extended Amount

0002 Provide full Business Intelligence (BI) Lifecycle

Support and Cybersecurity Services in accordance with sections C3.2, C.3.3, C.4.2, and C.4.3.

0 Not-To-

Exceed

$0.00 $0.00

CLIN NO. Supplies or Services Quantity Unit of Issue Unit Price Extended Amount

0003 Help Desk and SharePoint Support Services in accordance with sections C.3.4 and C.4.4.

0 Lot $0.00 $0.00

Descriptions/Specifications/Statement of Work

C-1 Requirements

C.1 Background The Judiciary Data & Analysis Office (JDAO) within the Administrative Office of the U.S. Courts (AOUSC) is responsible for the business intelligence decision support system that is used for analysis and reporting on the Judiciary’s personnel, financial, and the national case processing systems. JDAO provides support to the United States Federal Courts, which are comprised of 90 Bankruptcy Courts, 94 District Courts, and 13 Appellate Courts. In addition, JDAO provides information technology support regarding data access and visibility, data management, and data governance to the other offices within the AOUSC. JDAO provides full lifecycle sup-port for applications, systems, and data warehouses to meet the ongoing needs of its stakeholders, which in-volves the implementation of a new integrated enterprise data warehouse (IEDW) through the migration of new data sources and the consolidation of the existing data warehouses. There are currently three exiting data ware-houses within JDAO which are: New Streamline Timely Access to Statistics (NewSTATS), the Court Integ-rated Resource Information System (CIRIS), and the Enterprise Data Warehouse (EDW). The NewSTATS data warehouse is used for collecting, processing, analyzing, and reporting on the statistics of the federal court sys-tem. CIRIS is a data warehouse that is used to provide data regarding staffing within the Judiciary, and the EDW is used for the analysis and reporting on the Judiciary’s personnel, financial, national case processing sys-tem, as well as the federal defender and panel attorney program source systems.

USCA18BPAC1010 - Page 2 of 19

C.2 Current Environment JDAO develops, continuously enhances, maintains, and provides information technology system lifecycle sup-port to stakeholders that leverage NewSTATS, CIRIS, EDW, and other JDAO applications and systems. There are approximately 31,000 users within the judiciary that are geographically dispersed across the United States.

JDAO’s existing data warehouses (NewSTATS, CIRIS, and EDW) have adhered to the overall development process outlined by the Kimball methodology.

JDAO’s existing data warehouses, data marts, and application leverage approximately 108 virtual servers. The development and testing environments are located in the Ashburn Data Center, and the production environment is located in the San Diego Data Center. JDAO utilizes a combination of Red Hat 6, Windows Server 2008, 2012 and iOS Operating Systems; databases include Informix 11.7, MySQL 5.2, SQL Server 2005, 2008, 2014, iOS, and Oracle 11G Informix; COTS software includes, but is not limited to, IBM Change Data Capture, Or-acle Golden Gate, Business Objects, SharePoint 2013, Tableau visualization software, and metadata manage-ment tools. The Business Objects reporting environment software is XIR 4.2, and Data Services version 4.2.

NewSTATS has approximately 24 different subject/program areas, 600 database tables, 75 database views, 160 stored procedures, 37 universes, 704 reports and approximately 67 data services jobs. CIRIS has 8 universes and 106 reports. EDW has approximately 7,274 database tables, 731 database views, 109 stored procedures, 16 universes, and 57 data services jobs.

The existing data warehouses, listed in Attachment E - Data Warehouses, provide predefined reports and ad-hoc query capabilities and offer online analytics, data maps, reports and dashboards that answer key business ques-tions for major Judiciary program areas for purposes of analysis, planning, program monitoring, and decision making. The technical environment also contains Microsoft business intelligence tools such as SSIS (SQL Server Integration Services), SSRS (SQL Server Reporting Services), SQL Server Analytic Services (SSAS) and Power BI.

The projects listed below are representative of the remaining program areas that shall be migrated into the

IEDW.

• Adversary

• Appeals

• Bankruptcy Appellate Panel (BAP)

• Bankruptcy Court Trials (BCT)

• Civil

• Civil Justice Reform Act (CJRA)

• Criminal

• District Court Trials (DCT)

• Delayed Notice Search Warrants (DNSW)

• Federal Courts Management Statistics (FCMS)

• Grand Jury

• Judicial Complaints

• Magistrate Judge Statistics through Automated Records System (MJSTAR)

• Statistical Electronic Forms (SEF)

• Petit Jury

• Three Judge Hearings

• CIRIS Staffing/Resources: Detailed HR related information (will include all subject areas, e.g., staffing, buildings, etc.)

USCA18BPAC1010 - Page 3 of 19

• EDW- CFS 1 (Court Financial System)

• EDW- CJA 3.2;6.x (Criminal Justice Act)

• EDW-Human Resources (HR)

• EDW-Case Management Electronic Case Files (CM/ECF): Bankruptcy, District, and Appellate

• EDW-Judiciary Integrated Financial Management System (JIFMS)

• EDW-Procurement Management Division

• EDW- Defender Services Office

• Wiretap

• ICADS

C.3 Scope The contractor shall support the Judiciary Data & Analysis Office (JDAO) in four critical task areas (1) Estab-lish an Integrated Enterprise Data Warehouse (IEDW) through the consolidation and integration of existing data warehouses, data marts and applications; (2) Provide full Business Intelligence lifecycle support; (3) Cyberse-curity and (4) Help Desk Support Services.

Task areas 1, 2, and 3 require the contractor to assess the complexity of the task and propose a detailed project schedule for performing activities related to the analysis, design, development, testing, and implementation of each task in accordance with F-1 Deliverables. Each schedule shall include summary level and detailed tasks that include the assigned resources and durations for every task within the schedule.

The contractor shall employ a mature industry standard process for the management and execution of all project/task activities required to support the Government with the work outlined. In addition, the contractor shall ensure that all development efforts performed adhere to the AOUSC’s Information Technology Secure Software Development Best Practices described in Attachment 4 - Secure Software Development.

C.3.1 Establish an Integrated Enterprise Data Warehouse The Contractor shall establish an IEDW through the consolidation and integration of existing data warehouses, data marts and applications. Each program area/project shall require design, development, testing and imple-mentation of new ETL processes, universes, reports, and dashboards. The IEDW shall enable JDAO to provide full data analysis and reporting capabilities on a robust, scalable, and secure platform that can be leveraged by the entire Judiciary. The IEDW shall improve efficiency and reduce the duplication of effort, as well as the op-erating and maintenance costs.

For the purpose of this BPA call, the contractor shall focus on migration efforts for the following eight (8) pro-gram areas: 1) EDW - Defender Services Office

2) EDW - CM/ECF Bankruptcy

3) EDW - CM/ECF District

4) EDW - JIFMS

5) Magistrate Judge Statistics through Automated Records System (MJSTAR)

6) Delayed Notice Search Warrants (DNSW)

7) Wiretap

8) District Court Trials (DCT) C.3.2 Provide full Business Intelligence (BI) Lifecycle Support The contractor shall provide full Business Intelligence (BI) Lifecycle Support. The contractor shall provide the full range of technical services necessary to sustain BI applications and processes within the development, test-ing, and production environments, which will include expanding the IEDW BI architecture and develop addi-tional ETL, reporting, dashboard, and SharePoint capabilities in order to address defects, emerging require-ments, or enhance functional and technical requirements resulting from JDAO’s decision to incorporate addi-tional data sources.

C.3.3 Cybersecurity

USCA18BPAC1010 - Page 4 of 19

The contractor shall work in concert with the Government and other AOUSC contract staff to establish and doc-ument a process for safeguarding JDAO’s information and information systems. The contractor shall follow the guidance as outlined in the AO’s Information Technology Security Office’s Information Technology Frame-work (Attachment 1 - Judiciary Info Sec Framework), along with the Guide to Implementing the Judiciary In-formation Security Framework (Attachment 2 - Security Framework Guide). Together, these documents provide details regarding how to implement the Framework.

C.3.4 Help Desk and SharePoint Support Services The contractor shall be responsible for providing SharePoint support, as well as Tier II and Tier III help desk support, which includes, but is not limited to responding to requests for assistance, answering technical ques-tions, responding to issues regarding the various functional areas of the IEDW, applications and systems, (e.g., data, statistics, interfaces, dashboards, SharePoint sites and content, reports, queries, performance and system response times). The contractor shall support issues reported via phone, email, and via the AO’s approved IM software chat capabilities, (e.g., SKYPE for Business, or Lotus Note's Sametime at the appropriate security levels). Tier II Help Desk receive an average of about 2,000 critical or high priority issues each year and ap-proximately an additional 2,000 issues that are not considered high priority. All reported issues shall be respon-ded to in accordance with Section C.4.4.1. Tier I is excluded, as Tier I Help Desk support is centrally managed within the AOUSC and provided by the Department of Technology Service National Support Desk.

The contractor shall install, test, and validate all Linux, Windows, Oracle, SQL Server, MY SQL Informix, and third party patches applicable to JDAO's applications, including the on premise version of SharePoint, existing data warehouses and the IEDW each month. This activity shall be performed in the sandbox, development, test-ing, staging, and production environments each month and all errors must be resolved prior to deploying patches to the production environment, and any issues resulting from the monthly patches shall be tracked via JIRA, HEAT or some similar approved tool within the AOUSC

JIRA shall be used by the contractor to submit defects or enhancements, for the appropriate internal JDAO project team members to consider developing the requested functionality and include it in a future software patch or release.

In order to provide efficient help desk support, the contractor shall be expected to acquire the necessary skills to support newly released versions of databases (Informix and Oracle), operating systems (Red Hat Linux and Windows Server), and software (SAP’s Business Objects suite, Tableau, and IBM’s Change Data Capture soft-ware), while simultaneously supporting the current and previous versions of the databases, operating systems, and software.

C.4 Specific Requirements C.4.1 Establish an Integrated Enterprise Data Warehouse

C.4.1.1 Project Schedule: The contractor shall prepare a detailed project schedule in accordance with F-1 De-liverables for performing activities related to the analysis, design, development, testing, and implementation of each project. Each schedule shall include summary level and detailed tasks that include the assigned resources and durations for each.

C.4.1.2 Develop/Update Communications Plan: The contractor shall produce a Communications Plan for each program area/project. The Communications Plan is used to set the standard for how project team members communicate and ensures that everyone receives the necessary information. The Communications Plan shall in-clude who should be given specific project information based on project role, when that information should be delivered, and what communication channels will be used to deliver the information.

C.4.1.3 Develop/Update Risk Management Plan and Register: The Contractor shall produce a Risk Plan and Register for each program area/project. The Risk Management Plan will be used to define how the risks that are associated with each project will be identified, analyzed, and managed. It shall describe how risk man-agement activities will be performed, recorded, and monitored throughout the lifecycle of the project. The Risk Management Plan shall include reference to the use of a Risk Register that will be used to document, track , and

USCA18BPAC1010 - Page 5 of 19 report on project related risks, and issues. The Register shall be a separate living document that will be updated on a biweekly basis. The Risk Register shall include the Risk ID, name and description of risks, project area severity, likelihood, ownership, action/mitigation plan, etc.

C.4.1.4 Develop/Update Functional and Technical Requirements: The contractor shall perform activities re-quired to gather and document the Functional and Technical Requirements for each program area/project. The Contractor shall produce one combined Functional and Technical Requirements document per project. The doc-ument shall include the functional, performance and security requirements, as well as report mockups. The doc-ument shall be peer reviewed by the Contractor and submitted to the Government for approval before proceed-ing into the design phase. The Contractor shall be responsible for creating a project schedule based on all ap-proved requirements.

C.4.1.5 Gap Analysis: Based on the functionality assessment of existing program areas/project and the docu-mentation review of program areas/projects that have already been migrated into the IEDW, the Contractor shall produce a Gap Analysis document that outlines any missing functionality or documentation. The Gap Analysis shall identify the deficiencies in detail and describe the action necessary to address those deficiencies, as the Gap Analysis will be used to ensure the deficiencies are not repeated when integrating the remaining program areas/projects into the IEDW.

C.4.1.6 Source System Data Analysis: The contractor shall inventory and assess source systems data for qual-ity, volume, and form. The emphasis shall be placed on those sources used to populate the IEDW. The con-tractor shall lead data mapping sessions with the Government and identified Source System Owners to identify and document source system tables/columns and data mapping rules needed to populate the IEDW Oracle data-base. The contractor shall use the analysis to produce a source to target mapping document that will be used to support the development of the IEDW interfaces.

C.4.1.7 Develop/Update Functional and Technical Design: The contractor is responsible for translating re-quirements provided by government stakeholders and SME’s into complete detailed functional and technical design specifications that address the functional and technical requirements within each program area/project.

The Contractor shall review, update, or establish the necessary data models and database designs for each project that will be migrated into the IEDW. The Contractor shall produce one combined Functional and Tech-nical Design document per project. The document shall be peer reviewed by the Contractor and submitted to the Government for approval before proceeding into the development phase.

C.4.1.8 Capacity Planning: The contractor shall review and estimate the database sizes of the JDAO systems, applications, and data warehouses, including the Integrated Enterprise Data Warehouse for the capacity plan-ning purposes. The Contractor shall estimate and document the database sizes and growth rate for each through the use of an automated process that should monitor and predict the size of all databases, tables and number of rows. The Contractor shall produce a quarterly report and provide it to the Government that will in-clude existing and projected size of databases, tables, and the number of rows in order to ensure that the IEDW will be able to support future growth and a growing customer base. Capacity planning should also take into ac-count not only storage but also CPU utilization, network bandwidth and if additional components being added will stress the system which may require additional hardware.

C.4.1.9 Refine Data Models (Logical and Physical): The contractor shall update the Data Models for the IEDW database to reflect new and modified entities and data elements that are needed to support the functional and technical requirements for each program area/project. The contractor shall include a well-defined set of data elements that have a common business vocabulary that supports dimensional reporting and tracking of his-torical trends. In addition, the contractor shall maintain a data dictionary that includes the logical name, defini-tion, and related business common vocabulary terms. Requirements also include that all changes to physical database objects, tables, and columns are implemented using Data Definition Language scripts generated by Er-win.

C.4.1.10 Database Validation: The contractor shall work in concert with the Government and other AO Of-

USCA18BPAC1010 - Page 6 of 19 fice and contract staff to ensure the testing and production database environments are able to support the integ-ration of remaining program/projects into the IEDW. This effort includes reviewing and updating tables, in-dexes, triggers, and validating data through quality assurance tests, as well as database tuning as necessary.

C.4.1.11 Design and Development: The contractor shall design and develop ETL functionality that will inter-face and extract data from a variety of systems internal to the AO. JDAO’s goal of integrating data from mul-tiple environments will enable automation of information exchange, which will allow users the ability to share information efficiently. Based on business rules provided, the contractor shall develop ETL processes and pro-cedures to transfer the data from source systems through the system into the target databases, which requires the contractor to define and capture metadata and rules associated with ETL processes. In addition, the contractor shall be required to document and monitor, manage, and validate data activity including the data extraction, transformation, movement, and data loading processes and procedures. The contractor shall produce a detailed design document that describes the data intake, transformation, data flow and loading processes throughout the

IEDW.

C.4.1.12 Report and Universe Design and Development: The contractor shall design the universe and reports based on approved functional and technical requirements, and design documents. The contractor shall config-ure the Business Object’s BI suite of tools; input metadata; document and code universes, and reports based on those requirements. The contractor shall develop the presentation layer, reports and dashboards (canned and ad-hoc) so users can easily understand the purpose and behavior of the functions within the system without a lot of trial and error, assistance, or extensive training.

C.4.1.13 Functional, Integration and Performance Testing: The contractor shall conduct test planning, cre-ate necessary test data, draft test cases and record results, as well as a Requirements Traceability Matrix (RTM) to prove the functional and technical specifications required for each project were developed and tested. The RTM shall include the requirement number, title, type, and description, design reference, as well as code refer-ence, test Case, test objective, test status, last build, and last date tested. The contractor will execute functional, integration, and performance testing events. Functional testing requires the contractor to verify the functionality developed meets requirements. The effort will involve evaluating and comparing each software function with the business requirements and testing by providing related input so that the output can be evaluated to see how it conforms, relates, or varies. Integration testing requires the contractor to verify that the developed functional-ity is working properly from end-to-end. Performance testing is the process of determining the speed and effect-iveness of the functionality included in each project. The performance testing process shall be executed through the use of a Government provided COTS product and will involve quantitative tests done by measuring the re-sponse times or the number of MIPS (millions of instructions per second) at which the system functions.

C.4.1.14 Support User Acceptance Testing: User Acceptance Testing (UAT) will be performed by the Gov-ernment and court units. It is a process used to determine whether the work performed on the system by the con-tractor meets or exceeds system performance baselines. The contractor shall facilitate and support the Govern-ment's Acceptance Testing, including the participation in test execution, and the documentation of the test res-ults.

C.4.1.15 Implementation: The contractor shall perform activities related to the implementation of each project, which include but is not limited to producing a Deployment Plan with the necessary rollback proced-ures and release notes for end users. The Deployment Plan shall define the steps that must be completed in or-der to deploy changes into a target system environment. The Deployment Plan will include the schedule and re-source information, the engagement and promotion strategy, deployment methods, and technology infrastruc-ture and support considerations. Release Notes shall be produced and provided to end users for software or pro-gram areas/projects that are already in use and are delivered when an update is released.

C.4.1.16 Training: The contractor shall develop a training approach and materials, which will include, but is not limited to a Training Plan and User Guide. The Training Plan shall describe the tasks associated with train-ing end users of varying degrees of technical ability. The Training Plan shall take into consideration the learn-ing, objectives, target audience, training material, content, and the distribution mechanisms for offering training.

USCA18BPAC1010 - Page 7 of 19

In addition, the contractor shall produce a User Guide to be used to give assistance to end users and shall in-clude instructions and guidance on how to use the new functionality and where to find further help, and contact details.

C.4.1.17 BI Support & Development: The contractor shall develop and enhance reports, applications, ETL processes, dashboards, and dimensional cubes using approved JDAO tools (i.e., Business Objects and Tableau, etc.);

C.4.1.18 Architecture Support: The contractor shall work with the Government and other AO contract staff to enhance, expand, maintain, and monitor JDAO’s Business Intelligence (BI) architecture in order to create the IEDW and improve operations and ensure the infrastructure is able to meet JDAO’s emerging ETL, analysis, re-porting and dashboard requirements.

C.4.1.19 Data Mart Consolidation & Standardization: The contractor shall ensure the completion of the IEDW through the consolidation and integration of JDAO’s existing data warehouses, data marts, and applica-tions. This effort will allow JDAO to retire the legacy systems in order to provide an accurate and comprehens-ive view of the Judiciary’s personnel, financial, national caseload systems, as well as the federal defender and panel attorney program data. The contractor shall review and consolidate the file layouts, process flows, reports, transformations (ETL), which includes all scheduled jobs, as well as court feedback processes.

C.4.2 Provide Full Business Intelligence (BI) Lifecycle Support

C.4.2.1 Project Schedule: The contractor shall prepare a detailed project schedule for performing activities re-lated to the analysis, design, development, testing, and implementation of each project. Each schedule shall in-clude summary level and detailed tasks that include the assigned resources and durations for each.

C.4.2.2 Develop/Update Functional and Technical Requirements: The contractor shall perform activities re-quired to gather and document the Functional and Technical Requirements for each program area/project. The contractor shall produce one combined Functional and Technical Requirements document per project. The doc-ument shall include the functional, performance and security requirements, as well as report mockups. The doc-ument shall be peer reviewed by the contractor and submitted to the Government for approval before proceed-ing into the design phase. The contractor shall be responsible for creating a project schedule based on all ap-proved requirements.

C.4.2.3 Develop/Update Functional and Technical Design: The contractor is responsible for translating re-quirements provided by government stakeholders and SME’s into complete detailed functional and technical design specifications that address the functional and technical requirements within each program area/project.

The contractor shall review, update, or establish the necessary data models and database designs for each project that will be migrated into the IEDW. The contractor shall produce one combined Functional and Tech-nical Design document per project. The document shall be peer reviewed by the Contractor and submitted to the Government for approval before proceeding into the development phase.

C.4.2.4 Capacity Planning: The contractor shall review and estimate the database sizes of the JDAO systems, applications, and data warehouses, including the Integrated Enterprise Data Warehouse for the capacity plan-ning purposes. The Contractor shall estimate and document the database sizes and growth rate for each through the use of an automated process that should monitor and predict the size of all databases, tables and number of rows in order to ensure that the IEDW will be able to support future growth. Capacity planning should also take into account not only storage but also CPU utilization, network bandwidth and if additional components being added will stress the system which may require additional hardware. The Contractor shall provide this information to the Government on a quarterly basis.

C.4.2.5 Refine Data Models (Logical and Physical): The contractor shall update the Data Models for the IEDW database to reflect new and modified entities and data elements that are needed to support the functional and technical requirements for each program area/project. The contractor shall include a well-defined set of

USCA18BPAC1010 - Page 8 of 19 data elements that have a common business vocabulary that supports dimensional reporting and tracking of his-torical trends. In addition, the contractor shall maintain a data dictionary that includes the logical name, defin-ition, and related business common vocabulary terms. Requirements also include that all changes to physical database objects, tables, and columns are implemented using Data Definition Language scripts generated by Er-win that follow approved naming standards.

C.4.2.6 ETL Design and Development: The contractor shall design and develop ETL functionality that will in-terface and extract data from a variety of systems internal to the AO. JDAO’s goal of integrating data from mul-tiple environments will enable automation of information exchange, which will allow users the ability to share information efficiently. Requirements include modifying the design and development of the ETL processes to accommodate changes in source systems and new business user requirements. The Contractor shall be respons-ible for monitoring, managing, and validating data activity, which includes the end-to-end data extraction, trans-formation, movement, and data loading processes and procedures. In addition, requirements include that the Contractor shall produce a detailed design document that describes the data intake, transformation, data flow and loading processes throughout the IEDW. The Contractor is also responsible to adhering to Audit Balance Control (ABC) standards as part of ETL, following best practices for performance and restart ability.

C.4.2.7 Universe, Report, and SharePoint Design and Development: The contractor shall design the uni-verse, reports, SharePoint sites and contents based on approved functional and technical requirements, and design documents. The contractor shall configure SharePoint and the Business Object’s BI suite of tools; input metadata; document and code universes, and reports based on those requirements. The contractor shall develop the presentation layer, reports and dashboards (canned and ad-hoc) in an intuitive manner, so users can easily understand the purpose and behavior of the functions within the system without a lot of trial and error, assist-ance, or extensive training. These should be developed using approved naming standards.

C.4.2.8 Testing - Functional, Integration and Performance: The contractor shall conduct test planning, cre-ate necessary test data, draft test cases and record results, as well as a Requirements Traceability Matrix (RTM) to prove the functional and technical specifications required for each project were developed and tested. The RTM shall include the Requirement number, title, type, and description, as well as the design reference, code reference, test case, test objective, test status, and last build and last date tested. The contractor will execute functional, integration, and performance testing events. Functional testing requires the contractor to verify the functionality developed meets requirements. The effort will involve evaluating and comparing each software function with the business requirements and testing by providing related input so that the output can be evalu-ated to see how it conforms, relates, or varies. Integration testing requires the contractor to verify that the de-veloped functionality is working properly from end-to-end. Performance testing is the process of determining the speed and effectiveness of the functionality included in each project. The performance testing process shall be executed through the use of a COTS product and will involve quantitative tests done by measuring the re-sponse times or the number of MIPS (millions of instructions per second) at which a system functions.

C.4.2.9 Support User Acceptance Testing: User Acceptance Testing (UAT) will be performed by the Govern-ment and court units. It is a process used to determine whether the work performed on the system by the Con-tractor meets requirements. The contractor shall facilitate and support the Government's Acceptance Testing, in-cluding the participation in test execution, and the documentation of test cases and test results. The Contractor shall obtain Government approval before migrating to production.

C.4.2.10 Implementation: The contractor shall perform activities related to the implementation of each project, which includes but is not limited to producing a Deployment Plan with the necessary rollback procedures, com-munication plans and timeline. The Deployment Plan shall define the steps that must be completed in order to deploy changes into a target system environment. The Deployment Plan will include the schedule and resource information, the engagement and promotion strategy, deployment methods, and technology infrastructure, and release notes. Release Notes shall be produced and provided to end users for software or program areas/projects that are already in use and are delivered when an update is released.

C.4.2.11 Training: The contractor shall develop a training approach and materials, which will include, but is

USCA18BPAC1010 - Page 9 of 19 not limited to a Training Plan and User Guide. The Training Plan shall describe the tasks associated with train-ing end users of varying degrees of technical ability. The Training Plan shall take into consideration the learn-ing, objectives, target audience, training material, content, and the distribution mechanisms for offering training.

In addition, the contractor shall produce a User Guide which will be used to give assistance to end users and shall include instructions and guidance on how to use the new functionality and where to find further help, and contact details.

C.4.2.12 The contractor shall provide ongoing support and maintenance of JDAO’s infrastructure services, which involves maintaining application code and configurations used to extend the commercial off the shelf tools used by JDAO for ad-hoc reporting and analysis, ETL processing, as well as the modification and publica-tion of dashboards, and custom java applications used to obtain user input needed for integrated business pro-cesses and applications.

C.4.2.13 The contractor shall capture, document, update and track the versions of JDAO’s software, which in-cludes, but is not limited to: operating systems, firmware, database versions, commercial off-the-shelf (COTS) software, service packs, as well as the versions custom developed applications;

C.4.2.14 The contractor shall modify and/or update processes in accordance with changes in business require-ments, organizational standards, technical architecture, and political/legislative directives;

C.4.2.15 Requirements include providing operations and maintenance support to ensure continuous reliability and availability of JDAO’s data warehouses, data marts, and applications. In addition, the contractor shall mon-itor and validate the data extraction, transformation, and loading (ETL) processes to ensure accuracy of EDW data and maintenance of the metadata associated with ETL procedures.

C.4.2.16 The contractor shall maintain a library of all project related documentation using SharePoint.

C.4.3 Cybersecurity

C.4.3.1 Patches: The contractor shall ensure patches and upgrades are applied regularly to stay current with se-curity settings and technology changes. All software and systems should be no more than one version behind the most current available.

C.4.3.2 Secure Software Development Best Practices: The contractor shall ensure that the development projects listed in section 3.1 are developed according to the Attachment 4 - Secure Software Development.

C.4.3.3 Schedule: The contractor shall prepare a project schedule that includes summary level and detailed tasks with the assigned resources and durations for each project that is required to complete a System Security Plan (SSP).

C.4.3.4 Security Plan: The contractor shall produce a System Security Plan for all JDAO applications using Attachment 3 - System Security Plan as a guide.

C.4.3.5 Perform regular maintenance and upgrades: The contractor shall install, test, and validate all Linux, Windows, Oracle, Informix, and third party patches applicable to JDAO's applications, including the existing data warehouses and the IEDW regularly to ensure software and systems are not more than one version older than the most current available. This activity shall be performed in the sandbox, development, testing, staging, and production environments each month and all errors must be resolved prior to deploying patches to the pro-duction environment, and any issues resulting from the monthly patches shall be tracked via HEAT. Report of upgrades and maintenance performed shall be provided each time an upgrade occurs.

C.4.4 Help Desk

C.4.4.1 Help Desk Support Services: The contractor shall provide help desk support during the normal busi-

USCA18BPAC1010 - Page 10 of 19 ness hours of 7:00AM - 7:00PM EST, Monday-Friday, excluding Government holidays. The contractor shall provide on call after hour support, including Government holidays, as requested by the Government. Acceptable resolution times for Tier II and Tier III are outlined in the table below. The contractor shall meet with the Gov-ernment Help Desk Lead monthly to discuss issues reported, issues corrected and escalated and provide a writ-ten summary of the meeting.

Severity 1

CRITICAL

Severity 2

HIGH

Severity 3

MEDIUM

Severity 4

LOW

Business Exposure – application failure results in:

Critical business exposure High business exposure Possible business exposure Potential business exposure

Work Outage – application failure causes staff to:

Unable to perform a signific-ant portion of job

Unable to perform signific-ant portion of job

Unable to perform some small portion of job, still able to complete most tasks

Unable to perform minor portion of job, still able to complete most tasks

Number of Users – application failure can affect:

All (or nearly all) users Large number of users Small number of users Limited number of users

Work-around Feasibility – application failure requires alternate processing:

NONE (task cannot be per-formed in any other way or an emergency solution needs to be activated)

Task can be performed in some other way (may not be acceptable)

There is likely an acceptable work around to the issue

There is an acceptable and implemented work around to the issue

Target Response Time:

Within 15 minutes Within 30 business Minutes of request

Within 4 hours of request Within 8 hours of request

• The response times listed above are for issues reported during normal business hours

USCA18BPAC1010 - Page 11 of 19

Acceptable Resolution Time:

Within 4 hours Within 8 hours Within 3 Workday Within 4 workdays

• The above resolution times are flexible with the following exceptions: end of fiscal year processing, new reports requested as result of Congressional mandates, and new report requirements due to statutory changes

C.4.4.2 HEAT Software: The contractor shall be responsible for utilizing HEAT, a commercial off-the shelf (COTS) software tool used to record, track, route, and report on issues that have been escalated from Tier I to Tier’s II and/or III. The HEAT system is used by all help desk personnel to communicate with the users, (e.g., when requesting additional information, or providing a resolution to a reported issue).

C.4.4.3 Standard Operating Procedures (SOP): The contractor shall acknowledge receipt of all Tier II and Tier III submitted issues within 24 hours and shall provide a Standard Operating Procedures (SOP) document for repeatable tasks.

C.4.4.4 Patches & Upgrades: The contractor shall install, test, and validate all Linux, Windows, Oracle, Infor-mix, and third party patches applicable to JDAO's applications, including the existing data warehouses and the IEDW each month. This activity shall be performed in the sandbox, development, testing, staging, and produc-tion environments each month and all errors must be resolved prior to deploying patches to the production en-vironment, and any issues resulting from the monthly patches shall be tracked via JIRA, HEAT or some similar approved tool within the AO;

C.4.4.5 Work Request Documentation: JIRA shall be used by the contractor to submit defects or enhance-ments, for the appropriate internal JDAO project team members to consider developing the requested function-ality and include it in a future software patch or release.

C.4.4.6 Help Desk Support Skills: In order to provide efficient help desk support, the contractor is expected to acquire the necessary skills to support newly released versions of databases (Informix and Oracle), operating systems (Red Hat Linux and Windows Server), and software (SAP’s Business Objects suite, Tableau, and IBM’s Change Data Capture software), while simultaneously supporting the current and one previous version of the databases, operating systems, and software.

C.5 Meetings C.5.1 Kick-off Meeting A kick-off meeting will be held between the contractor, the Contracting Officer, the COR and designated gov-ernment representatives within 5 business days of the award date or other mutually agreed upon timeframe. The kick-off meeting will be held at the Government’s facility in Washington, DC.

The meeting is intended to:

• Initiate the communication process between the Government and contractor by introducing key task parti-cipants and discussing roles and responsibilities.

• To ensure the contractor has a full understanding of the scope of work and requirements.

C.5.2 Meetings The contractor shall participate in bi-weekly meetings with the Government at which the Contractor will provide and discuss an activity report. This report, at a minimum, shall address, as applicable:

• The status of all on-going enhancement efforts (addressing schedule and performance);

USCA18BPAC1010 - Page 12 of 19

• Identification of problems encountered and plan for resolution;

• The activities and deliverables planned for the current month;

• Any customer complaints regarding data accuracy, data management and timeliness of data generation and reporting (and the response provided); and

• The Contractor shall provide copies of briefing materials to each participant in the meeting.

• The Contractor shall prepare meeting minutes and deliver the meeting minutes to the COR within three working days following the meeting.

Applicable Clauses

F-1 Deliverables

The contractor shall provide the deliverables listed below and provide two (2) electronic copies for each deliver-able. The Government will review documentation submitted by the contractor and provide comments within ten

(10) business days.

Section Deliverable Frequency Recipients C.4.1.1 Detailed project schedule that includes all tasks, ob-jectives, milestones and re-sources for each project

Due upon completion of planning phase of each project and will update the schedule on a weekly basis

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.2 Communication Plan (who, what, when, and how project information is shared)

Due upon completion of planning phase of each project and prior to the start of the requirements phase

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.3 Risk Management Plan and Register (identifies issues and risks to the project and impact, including mitigation strategy

The Plan and register will be completed upon comple-tion of the planning phase of each project; register will be updated through project completion on a biweekly basis

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.4 Functional/Technical Re-quirements Document

Upon completion of the re-quirements phase of each project and prior to the start of the development phase

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.5 Gap Analysis Due upon completion of planning phase of each project

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.6 Source System Data Ana-lysis Document

Due upon completion of the design phase of each project

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.7 Functional and Technical Design Document

Upon completion of source system data analysis phase

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.8 Capacity Planning Docu- Upon completion of the Contracting Officer’s Rep-

USCA18BPAC1010 - Page 13 of 19 ment planning phase of each project resentative (COR), and the Government Project Man-ager

C.4.1.9 Logical and Physical Data Models

Complete in parallel with the functional and technical design (4.1.7)

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.11 ETL Design Document Upon completion of the design phase of each project and prior to the start of the development phase

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.12 Report and Universe Design Document

Upon completion of the design phase of each project and prior to the start of the development phase

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.13 Requirements Traceability Matrix

Upon completion of the de-velopment phase of each project

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.14 Test Cases w/results Upon completion of the testing phase of each project

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.15 Deployment Plan Upon completion of User Acceptance Testing

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.15 Release Notes Upon completion of User Acceptance Testing

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.16 Training Plan Upon completion of User Acceptance Testing

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.1.16 User Guide Upon completion of User Acceptance Testing

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.2.1 Detailed project schedule that includes all tasks, ob-jectives, milestones, and re-sources for each project

Due upon completion of planning phase of each project and shall update the schedule on a weekly basis

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.2.2 Functional/Technical Re-quirements Document

Upon completion of the re-quirements phase of each project and prior to the start of the development phase

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C. 4.2.3 Functional/Technical Design Document

Upon completion of the design phase of each project and prior to the start of the development phase

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.2.4 Capacity Planning Docu-ment

Upon completion of the planning phase of each

Contracting Officer’s Rep-resentative (COR), and the

USCA18BPAC1010 - Page 14 of 19 project Government Project Man-ager

C.4.2.5 Logical and Physical Data Models

To be completed in parallel with functional/technical design document (4.2.3)

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.2.6 ETL Design Document Upon completion of the design phase of each project and prior to the start of the development phase

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.2.7 Report and Universe Design Document

Upon completion of the design phase of each project and prior to the start of the development phase

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.2.8 Requirements Traceability Matrix

Upon completion of the de-velopment phase of each project

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.2.9 Test Cases w/results Upon completion of the testing phase of each project

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.2.10 Deployment Plan Upon completion of User Acceptance Testing

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.2.10 Release Notes Upon completion of User Acceptance Testing

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.2.11 Training Plan Upon completion of User Acceptance Testing

Contracting Officer’s Rep-resentative (COR), and the Government Project Man-ager

C.4.2.11 User Guide Upon completion of User Acceptance Testing

Contracting…