USCA18BPAC1012.pdf

ORDER FOR SUPPLIES OR SERVICES

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

1. DATE OF ORDER 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.

USCA18BPAC1012

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)

USCA18BPAC1012 - Page 1 of 14

Supplies or Services and Prices/Costs

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

0001 Data Governance requirements in accordance with sections C.3.1 to C3.4 and C.4.1 to C.4.4 -

Estimated Costs

1 Not-To-

Exceed

$0.00 $0.00

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

0002 Data Governance requirements in accordance with sections C.3.1 to C3.4 and C.4.1 to C.4.4 - Fixed

Fee.

1 Not-To-

Exceed

$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.

Data Governance provides and enforces the established enterprise-wide data standards, common vocabulary, re-ports, and the use of standardized data. Data Governance will make it easier for JDAO and the AOUSC as a whole to integrate, synchronize and consolidate data from different departments, exchange data with other pro-gram offices in a common format, and communicate effectively through shared terms and report formats.

C.2 Current Environment JDAO is working to build an environment which supports a successful enterprise-wide data governance pro-gram, as our focus has largely been on working with AO and judiciary staff on a common business lexicon, definitions, and processes. The AOUSC has an established Data Governance Board comprised of representat-ives from business and system owners who come together to make the strategic decisions. As part of the Data Governance program, specific data stewards have the responsibility of turning policy into practice and bringing the standards to life.

JDAO develops, continuously enhances, maintains, and provides information technology system lifecycle sup-port to stakeholders that utilize JDAO existing data warehouses, New Streamline Timely Access to Statistics (NewSTATS), Court Integrated Resource Information System (CIRIS), and the Enterprise Data Warehouse (EDW), as well as other JDAO applications and systems. The existing data warehouses, data marts, and applic-ations 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 Infor-

USCA18BPAC1012 - Page 2 of 14 mix 11.7, MySQL 5.2, SQL Server 2005, 2008, iOS, and Oracle 11G Informix; COTS software includes, but is not limited to, IBM Change Data Capture, Oracle Golden Gate, Business Objects, SharePoint 2013, and Tableau visualization software. The Business Objects reporting environment software is XIR 4.2, and Data Ser-vices 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 provide predefined reports, ad-hoc query capabilities, online analytics, data maps, reports and dashboards that answer key business questions for major Judiciary program areas for purposes of analysis, planning, program monitoring, and decision making.

C.3 Scope The contractor shall assist the Government with the necessary analysis that will enable business users to make decisions based on well-managed and well-understood information assets and high-quality data. The Data Gov-ernance initiative requires the contractor to support the Government with the design, development, and delivery of (1) Subject Area Data Models, (2) Conceptual Data Models, and (3) Logical Data Models. These efforts shall be focused on the following five (5) program areas: Magistrate Judge Statistics through Automated Re-cords (MJSTAR), District Court Trials (DCT), Delayed Notice Search Warrant (DNSW), Bankruptcy, and Bankruptcy Court Trials.

Program/Project Data Description Number of Data Marts Number of Reports The Magistrate Judge Statistics Through Auto-mated Records System

(MJSTAR)

Contains information re-lated to magistrate judge workload statistics, which consists of docketed ma-gistrate judge duties entered into CM/ECF

1 48

District Court Trials

(DCT)

A trial is defined as “a con-tested proceeding before either a court or jury where evidence is introduced”.

Evidence is considered wit-ness testimony or exhibits presented.

2 33

Delayed Notice Search Warrant (DNSW)

The DNSW reporting re-quirement set forth in 18 U.S.C. § 3103a (d) requires judges to report any “warrant authorizing delayed notice (including any extension thereof) entered under this section or the denial of such war-rant (or request for exten-sion)....” Accordingly, the new statutory reporting re-quirement specifically ap-plies only where :( 1) the search instrument requested is a warrant (or an analog-ous search instrument that falls under the require-ments of Fed. R. Crim. P.

41), and (2) the judge acts

1 6

USCA18BPAC1012 - Page 3 of 14 on a request for delayed notice in conjunction with the search. The AO is re-quired to file annual reports to Congress summarizing data received from judges on delayed-notice search warrant applications. A re-port must be submitted to the Administrative Office each time a judge rules on a request for delay or for an extension to a previously authorized delay.

Bankruptcy Filing bankruptcy can help a person by discarding debt or making a plan to repay debts. A bankruptcy case normally begins when the debtor files a petition with the bankruptcy court. A pe-tition may be filed by an in-dividual, by spouses to-gether, or by a corporation or other entity.

7 151

Bankruptcy Court Trials

(BCT)

BCT includes all trials, me-diations, arbitrations, chambers conferences, and other proceedings conduc-ted before the judge (or jury) which were initiated by a pleading, petition or complaint, whether filed in, referred to or transferred to the bankruptcy court

2 7

The detailed statistical data for Magistrate Judge Statistics through Automated Records (MJSTAR), District Court Trials (DCT), and Delayed Notice Search Warrant (DNSW), are collected via the Federal Judiciary's Dis-trict Case Management system for district courts. The statistical data then gets extracted from the court’s CM/ ECF database into an extraction file and is submitted to the Judiciary Data & Analysis Office via a secure FTP connection. The data is then loaded into JDAO’s New Streamline Timely Access to Statistics (NewSTATS) Data Warehouse for data analysis and reporting purposes.

MJSTAR data is detailed information regarding the judicial duties conducted and completed by magistrate judges, which includes data on all civil cases disposed of by magistrate judges with the parties’ consent under 28 U.S.C. § 636(c), and all petty offense and misdemeanor criminal cases disposed of by magistrate judges un-der 18 U.S.C. § 3401. District courts employ various methods of referring cases to magistrate judges. In some courts, all civil cases are automatically referred to magistrate judges for all pretrial case management duties. In other courts, district judges may pick and choose the duties to be referred to magistrate judges on an ad hoc basis.

District Court Trial data is specifically related to a contested proceeding before either a court or jury in which evidence is introduced. Evidence is considered witness testimony or exhibits presented. District Court Trial data

USCA18BPAC1012 - Page 4 of 14 is used to help determine staffing allocation projections and the need for judicial officers, as well as senior judge certifications.

The USA Patriot Improvement and Reauthorization Act of 2005, Pub. L. No. 109-177 requires any federal or state judge who issues or denies a federal warrant authorizing delayed notice, or an extension of such a war-rant’s reporting period, to file a report with the AO on the warrant. (18 U.S.C. § 3103a (d) (1).) The report must include the offense specified in the warrant or application, the period of delay authorized, the number and duration of any extensions, and the action taken on the application. The AOUSC is required to report annually to Congress on the information submitted by judges for the preceding fiscal year. This report must include the number of applications for delayed-notice search warrants and extensions, and the number of warrants and ex-tensions granted or denied. (18 U.S.C. § 3103 a (d) (2).).

The delayed-notice search warrant reporting requirement took effect on March 9, 2006. Under § 3103a (d) (2), the Administrative Office is required to submit a summary of the data to Congress "beginning with the fiscal year ending September 30, 2007." The AO developed a reporting form for judges’ use in submitting informa-tion to the AO in accordance with the statute.

The detailed statistical data for the Bankruptcy program area are collected via the Federal Judiciary's Bank-ruptcy Case Management system for bankruptcy courts. The bankruptcy statistical data is extracted from the court’s CM/ECF database and put into an extraction file that gets submitted to the Judiciary Data & Analysis Office via a secure FTP connection. The data is then loaded into JDAO’s New Streamline Timely Access to Statistics (NewSTATS) Data Warehouse for data analysis and reporting purposes.

There are different types of bankruptcies, which are usually referred to by their chapter in the U.S. Bankruptcy Code. The data that is collected is related to individuals that may file Chapter 7 or Chapter 13 bankruptcy, de-pending on the specifics of their situation. Municipalities—cities, towns, villages, taxing districts, municipal utilities, and school districts may file under Chapter 9 to reorganize. Businesses may file bankruptcy under Chapter 7 to liquidate or Chapter 11 to reorganize. Chapter 12 provides debt relief to family farmers and fisher-men. Bankruptcy filings that involve parties from more than one country are filed under Chapter 15.

The detailed statistical data for Bankruptcy Court Trials are collected via theB-102 Form from within the AOUSC Statistical Electronic Forms (SEF) website. The data is then automatically loaded into JDAO’s New Streamline Timely Access to Statistics (NewSTATS) Data Warehouse for data analysis and reporting pur-poses.

Bankruptcy court trial data are collected by each judge’s courtroom deputy or other designated court staff. The Clerk’s office staff should coordinate with chambers to ensure that data on all other bankruptcy court activities are captured and reported (such as conferences in chambers or travel for intracircuit and intercircuit assign-ments). Each court is required to report judicial activities to the Administrative Office of the U.S. Courts (AO) each month by the 10th of the following month. A Statistics Electronic Form (SEF) B-102 102 report for every active judge is required every month; even if only to report that the judge did not conduct any trials or other proceedings that particular month.

The B-102 Report is designed to collect information on the types of matters heard in the bankruptcy courts and the cumulative, monthly time expended on these matters. These data assist the Judiciary in determining the al-location of existing resources and the need for additional resources. The person charged with completing the re-port (usually the judge’s courtroom deputy) must take care in completing the report, especially in determining whether or not a particular activity falls within the definition of "trial" or "other proceeding."

The contractor shall assess the complexity of each task within this BPA Call and propose a detailed project schedule for performing the work 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. In addition, the contractor shall provide weekly and monthly project status reports that include financial reports for resources associated with the work as outlined within this BPA Call.

USCA18BPAC1012 - Page 5 of 14

C.3.1 Develop, and Deliver JDAO Subject Area Data Models The contractor shall work with the Government to develop Subject Area Models (SAM) for each of the follow-ing five (5) statistical program areas, which are the Magistrate Judge Statistics through Automated Records (MJSTAR), District Court Trials (DCT), Delayed Notice Search Warrant (DNSW), Bankruptcy, and Bank-ruptcy Court Trials program areas.

In order to gain an understanding of each data program area, the contractor shall review existing program docu-mentation, which includes the project charters and/or project management plans, the functional and technical re-quirements, as well as design documentation. The contractor shall produce a Subject Area Model/Diagram for each data program utilizing a commercial-off-the-shelf (COTS) software (either Erwin or MS Visio). The mod-els shall be used to anchor the starting and end points for data architecture as they shall include the key business entities, key relationships between the entities and the mapping of the entities to the business relationships for each of the data program areas.

C.3.2 Develop and Deliver Enterprise-level Subject Area Data Models for JDAO and the AOUSC The contractor shall work with the Government to develop enterprise-level Subject Area Models (SAM) for the Judiciary Data & Analysis Office and the Administrative Office of the United States Courts (AOUSC). The Ma-gistrate Judge Statistics through Automated Records (MJSTAR), District Court Trials (DCT), and Delayed No-tice Search Warrant (DNSW) program areas are to be considered "District" data and the Bankruptcy data is comprised of the Bankruptcy program area and Bankruptcy Court Trials. This effort shall require the contractor to incorporate some, if not all, of the individual statistical Subject Area Model entity related information into the enterprise-level Subject Area Models. The Contractor shall produce the enterprise Subject Area Models/ Diagrams utilizing a commercial-off-the-shelf (COTS) software (either Erwin or MS Visio). The enterprise-level models shall be used to anchor the starting and end points for enterprise data architecture and shall be the basis for mapping and sharing data across JDAO and the AOUSC.

C.3.3 Develop, Deliver, and Maintain JDAO and AOUSC Conceptual Data Models The contractor shall support the Government with developing, delivering, enhancing and maintaining conceptu-al data models for each of the following five (5) program areas, which are the Magistrate Judge Statistics through Automated Records (MJSTAR), District Court Trials (DCT), Delayed Notice Search Warrant (DNSW), Bankruptcy, and Bankruptcy Court Trials program areas. The contractor shall review the related program area requirements documentation prior to developing the conceptual data models for each of the statistical program areas. Conceptual data models are considered to be business models that are used to document business know-ledge from a data perspective. The models shall be developed using standard data modeling practices and include business entities and the relationships between the entities. The Contractor shall produce conceptual data models for each program area utilizing a commercial-off-the-shelf (COTS) software (either Erwin or MS Visio), as directed by the Government.

The contractor shall work with the Government to develop one Enterprise Conceptual Data Model for JDAO and one for the AOUSC. These two models are comprised of the Magistrate Statistics through Automated Re-cords (MJSTAR), District Court Trials (DCT), Delayed Notice Search Warrant (DNSW), Bankruptcy, and Bankruptcy Court Trials program areas. The development of the two Enterprise Conceptual Data Models shall require the Contractor to utilize standard data modeling practices and incorporate most, if not all, of the indi-vidual conceptual data model subject areas, entities, and relationships into the enterprise conceptual data mod-els. The AOUSC Enterprise Conceptual Data Models shall provide a high-level, top-down picture of how the AOUSC utilizes data related to the Magistrate Judge Statistics through Automated Records (MJSTAR), District Court Trials (DCT), Delayed Notice Search Warrant (DNSW) program areas, Bankruptcy program and Bankruptcy Court Trials. The contractor shall be required to assist with developing and implementing a strategy to update, maintain, and automate approved updates to the data models.

The contractor shall produce the Enterprise Data Models utilizing a commercial-off-the-shelf (COTS) software tool (either Erwin or MS Visio).

C.3.4: Develop, Deliver, and Maintain JDAO and AOUSC Logical Data Models The contractor shall support the Government with developing, delivering, enhancing and maintaining logical data models for each of the following five (5) program areas, which are the Magistrate Judge Statistics through

USCA18BPAC1012 - Page 6 of 14

Automated Records (MJSTAR), District Court Trials (DCT), Delayed Notice Search Warrant (DNSW), Bank-ruptcy, and Bankruptcy Court Trials program areas. Logical Data Models are used to represent the data archi-tecture in a graphical way without any regard to the database involved in storing the data. The logical data models shall be developed using standard data modeling practices and will provide all relationships between en-tities specified using primary keys and foreign keys and all attributes within an entity are listed. The Contractor shall produce conceptual data models for each program area utilizing Erwin, a commercial-off-the-shelf (COTS) software tool currently used by the AOUSC.

The Contractor shall work with the Government to develop one Enterprise Logical Data Models for JDAO and one for the AOUSC. These two models are comprised of the Magistrate Statistics through Automated Records (MJSTAR), District Court Trials (DCT), Delayed Notice Search Warrant (DNSW), Bankruptcy, and Bank-ruptcy Court Trials program areas. The development of the two Enterprise Logical Data Models shall require the contractor to utilize standard data modeling practices and incorporate most, if not all, of the individual logic-al data model entities and their relationships, as well as their attributes into the enterprise logical data models.

The contractor shall be required to assist with developing and implementing a strategy to update, maintain, and automate approved updates to the data models.

C.4 Specific Requirements C.4.1 Establish JDAO Subject Area Models

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 development of five (5) JDAO subject area data models. The schedule shall include summary level and detailed tasks that include the assigned resources and durations for each task.

C.4.1.2 Subject Area Model Diagrams: The contractor shall document and deliver a JDAO Subject Area Data Model diagram that represents five (5) program areas which are Magistrate Judge Statistics through Automated Records (MJSTAR), District Court Trials (DCT), and Bankruptcy program areas. The diagram shall include the key business entities and their relationships. The diagrams shall be peer reviewed by the contractor and submit-ted to the Government for approval before initiating the enterprise-level Subject Area Models.

C.4.1.3 Subject Area CRUD Matrix: The contractor shall document and deliver a CRUD Matrix CRUD is an acronym that refers to the certain actions related to a data entity. The C represents create and store new data; R

– represents retrieve and read data; the U- represents updates or modifications then stores the data; and D-represents to delete or remove the data. The CRUD matrix is an effective way to capture and display activities and permissions within a system and is useful when identifying the usage of data entities.

C.4.1.4 JDAO Enterprise Subject Area Models: The contractor shall produce a JDAO Enterprise Subject Area Models, which is comprised of the Bankruptcy program and Bankruptcy Court Trials program area data and district data, which is comprised of the Magistrate Statistics through Automated Records (MJSTAR), Dis-trict Court Trials (DCT), Delayed Notice Search Warrant (DNSW) program areas. The diagrams shall include the key business entities and their relationships and must be peer reviewed by the Contractor before delivering to the Government.

C.4.1.5 Weekly Status Report: The contractor shall produce a weekly status report and provide it to the Gov-ernment in MS Word or PowerPoint. The status report shall include completed tasks, as well as planned activit-ies and tasks for the upcoming week and must specify enough detail for the Government to discern ongoing tasks from other work or evolving tasks.

C.4.1.6 Monthly Project Status and Financial Reports: The contractor shall provide the Government with an Excel spreadsheet that includes detailed financial information that reflects the tracking of the burn rate for re-sources associated with this BPA Call In addition, the contractor shall produce a monthly status report and provide it to the Government. The status report shall be delivered in PowerPoint and include the status of the high-level project activities and milestones, target completion dates for the project milestones, risks to the project and proposed mitigation strategy .

USCA18BPAC1012 - Page 7 of 14

C.4.2 Establish AOUSC Enterprise Subject Area Models

C.4.2.1 Project Schedule: The contractor shall prepare a detailed project schedule in accordance with F-1 De-liverables for performing activities related to the development of five (5) AO Subject Area Models that have been defined by the Government. The schedule shall include summary level and detailed tasks that include as-signed resources and durations for each task.

C.4.2.2 AOUSC Subject Area Model Diagram: The contractor shall produce two (2) AOUSC Enterprise Sub-ject Area Models. One model shall be for bankruptcy which is comprised of the Bankruptcy program and Bank-ruptcy Court Trials program area data and one for district, which is comprised of the Magistrate Statistics through Automated Records (MJSTAR), District Court Trials (DCT), Delayed Notice Search Warrant (DNSW) program areas. The diagrams shall include the key business entities and their relationships and must be peer re-viewed by the Contractor and considered final before delivering to the Government.

C.4.2.3 Subject Area CRUD Matrix: The contractor shall document and deliver a CRUD Matrix. CRUD is an acronym that refers to the certain actions related to a data entity. The C represents create and store new data;

R – represents retrieve and read data; the U- represents update and/ or modifies then store the data; and D-represents to delete or remove the data. The CRUD matrix is an effective way to capture and display activities and permissions within a system and is useful when identifying the usage of data entities.

C.4.2.4 Weekly Status Report: The contractor shall produce a weekly status report and provide it to the Gov-ernment in MS Word or PowerPoint. The status report shall include completed tasks, as well as planned activit-ies and tasks for the upcoming week and must specify enough detail for the Government to discern ongoing tasks from other work or evolving tasks.

C.4.2.5 Monthly Project Status and Financial Reports: The contractor shall provide the Government with an Excel spreadsheet that includes detailed financial information that reflects the tracking of the burn rate for re-sources associated with this BPA Call. In addition, the Contractor shall produce a monthly status report and provide it to the Government. The status report shall be delivered in PowerPoint and include the status of the high-level project activities and milestones, target completion dates for the project milestones, risks to the project and proposed mitigation strategy .

C.4.3 Develop, Deliver, and Maintain JDAO and AOUSC Conceptual Data Models C.4.3.1 Project Schedule: The contractor shall prepare a detailed project schedule in accordance with F-1 De-liverables for performing activities related to the JDAO and the AOUSC Enterprise Conceptual Data Models.

The schedule shall include summary level and detailed tasks that include assigned resources and durations for each task.

C.4.3.2 JDAO Conceptual Data Models: The contractor shall produce conceptual data models for the five (5) identified program areas, which are the Magistrate Judge Statistics through Automated Records (MJSTAR), District Court Trials (DCT), Delayed Notice Search Warrant (DNSW), Bankruptcy program, and Bankruptcy Court Trials data. The models shall include the key business entities and their relationships.

C.4.3.3 JDAO Enterprise Conceptual Data Model: The contractor shall produce a JDAO Enterprise Concep-tual Data Model The data model shall contain district and bankruptcy related information, which will be com-prised of the Magistrate Judge Statistics through Automated Records (MJSTAR), District Court Trials (DCT), and Delayed Notice Search Warrant (DNSW), Bankruptcy program and Bankruptcy Court Trials data.

C.4.3.4 AOUSC Enterprise Conceptual Data Model: The contractor shall produce an AOUSC Enterprise Conceptual Data Model. The data model shall be for district data and bankruptcy data, which will be comprised of the Magistrate Judge Statistics through Automated Records (MJSTAR), District Court Trials (DCT), and Delayed Notice Search Warrant (DNSW), Bankruptcy program and Bankruptcy Court Trials data. The AOUSC Enterprise Conceptual Data Model shall include subject areas, entity types and their relationships. The contract-

USCA18BPAC1012 - Page 8 of 14 or shall peer review the model before delivering to the Government.

C.4.3.5 Weekly Status Report: The contractor shall produce a weekly status report and provide it to the Gov-ernment in MS Word or PowerPoint. The status report shall include completed tasks, as well as planned activit-ies and tasks for the upcoming week and must specify enough detail for the Government to discern ongoing tasks from other work or evolving tasks.

C.4.3.6 Monthly Project Status and Financial Reports: The contractor shall provide the Government with an Excel spreadsheet that includes detailed financial information that reflects the tracking of the burn rate for re-sources associated with this BPA Call. In addition, the Contractor shall produce a monthly status report and provide it to the Government. The status report shall be delivered in PowerPoint and include the status of the high-level project activities and milestones, target completion dates for the project milestones, risks to the project and proposed mitigation strategy.

C.4.4 Develop, Deliver, and Maintain JDAO and AOUSC Logical Data Models C.4.4.1 Project Schedule: The contractor shall prepare a detailed project schedule in accordance with F-1 De-liverables for performing activities related to the JDAO and the AOUSC Logical Data Models. The schedule shall include summary level and detailed tasks that include assigned resources and durations for each task.

C.4.4.2 JDAO Logical Data Models: The contractor shall produce logical data models for the five (5) identi-fied program areas, which are the Magistrate Judge Statistics through Automated Records (MJSTAR), District Court Trials (DCT), Delayed Notice Search Warrant (DNSW), Bankruptcy program, and Bankruptcy Court Trials data. The logical data models shall be developed using standard data modeling practices and shall provide all relationships between entities using primary keys and foreign keys and all attributes within an entity shall be listed. The contractor shall peer review the models before delivering to the Government.

C.4.4.3 JDAO Enterprise Logical Data Model: The contractor shall produce a JDAO Enterprise Logical Data Model. The data model shall contain district and bankruptcy related information, which will be com-prised of the Magistrate Judge Statistics through Automated Records (MJSTAR), District Court Trials (DCT), and Delayed Notice Search Warrant (DNSW), Bankruptcy program and Bankruptcy Court Trials data. The model shall be developed using standard data modeling practices and will provide all relationships between en-tities using primary keys and foreign keys and all attributes within an entity shall be listed.

C.4.4.4 AOUSC Enterprise Logical Data Model: The contractor shall produce an AOUSC Enterprise Logical Data Model. The data model shall be for district data and bankruptcy data, which will be comprised of the Ma-gistrate Judge Statistics through Automated Records (MJSTAR), District Court Trials (DCT), and Delayed No-tice Search Warrant (DNSW), Bankruptcy program and Bankruptcy Court Trials data. The development of the Enterprise Logical Data Model shall require the contractor to review all related program area documentation, (e.g., project charters, requirements documentation and any design documentation), and interview stakeholders as appropriate. The contractor shall utilize standard data modeling practices and include most, if not all, of the individual data model entities, attributes, and entity relationships using their primary and foreign keys. The data model shall be peer reviewed by the contractor before delivering to the Government. In addition, the contractor shall be required to assist with developing and implementing a strategy to update, maintain, and automate ap-proved updates to the data model.

C.4.4.5 Weekly Status Report: The contractor shall produce a weekly status report and provide it to the Gov-ernment in MS Word or PowerPoint. The status report shall include completed tasks, as well as planned activit-ies and tasks for the upcoming week and must specify enough detail for the Government to discern ongoing tasks from other work or evolving tasks.

C.4.4.6 Monthly Project Status and Financial Reports: The contractor shall provide the Government with an Excel spreadsheet that includes detailed financial information that reflects the tracking of the burn rate for re-sources associated with this BPA Call. In addition, the Contractor shall produce a monthly status report and provide it to the Government. The status report shall be delivered in PowerPoint and include the status of the high-level project activities and milestones, target completion dates for the project milestones, risks to the

USCA18BPAC1012 - Page 9 of 14 project and proposed mitigation strategy .

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 rep-resentatives within 5 business days of the contract 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; and

• To ensure the Contractor has a full understanding of the objectives and requirements.

C.5.2 In addition, the contractor shall participate in monthly meetings with the Government at which it will dis-cuss the project activity report. This report, at a minimum, shall address, as applicable:

• Identification of problems encountered and plan for resolution;

• The activities and deliverables planned for the current month;

• Any Risks to the project and proposed mitigation strategy for each;

C.5.3 Contractor shall also participate in meetings on a to-be-determined basis depending on the challenges/ complexity of the activity to be monitored.

C.5.4 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

Clause(s) Incorporated By Reference, see Clause B-5 Clause Title Date

4-60 Allowable Cost and Payment APR 2013

4-65 Fixed Fee APR 2013

4-85 Limitation of Cost APR 2013

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.

Document Section Deliverable De-scriptions

Date Due or Fre-quency

Form Recipient(s)

C.4.1.1 Detailed project schedule that in-cludes all tasks, ob-jectives, milestones and resources for each of the JDAO Subject Area Models

Initial schedule due 45 days after con-tract award and shall be reviewed and updated on a weekly basis

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.1.2 JDAO Subject Area Due 60 days after 2 (electronic copies) Contracting Officer’s

USCA18BPAC1012 - Page 10 of 14

Document Section Deliverable De-scriptions

Date Due or Fre-quency

Form Recipient(s)

Model Diagrams contract award Representative (COR), and the Gov-ernment Project Manager

C.4.1.3 JDAO Subject area CRUD Matrix

Due upon comple-tion of all draft sub-ject area models but no later than seven

(7) months after con-tract award

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.1.4 JDAO Enterprise Subject Area Models Diagrams

Due 90 days after contract award.

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.1.5 Status Report Weekly

2 (electronic copies) Contracting Officer’s Representative

(COR), and the Gov-ernment Project

Manager C.4.1.6 Monthly Project

Status and Financial Reviews

Monthly (1st Tues-day after the report-ing month)

2 (electronic copies) Contracting Officer’s Representative

(COR), and the Gov-ernment Project

Manager C.4.2.1 Detailed project schedule that in-cludes all tasks, ob-jectives, milestones and resources for each of the AO Sub-ject Area Models

Due 5 days after the JDAO Enterprise Subject Area Models have been completed and delivered to the Government.

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.2.2 AOUSC Subject Area Models (Bankruptcy and District)

Due 120 days after contract award

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.2.3 CRUD Matrix for AOUSC Subject Areas CRUD Matrix

Due upon comple-tion of all draft sub-ject area models, but no later than six (6) months after contract award

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.2.4 Status Report Weekly

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.2.5 Monthly Project Status and Financial Reviews

Monthly (1st Tues-day after the report-ing month)

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-

USCA18BPAC1012 - Page 11 of 14

Date Due or Fre-quency

Form Recipient(s) ernment Project Manager

C.4.3.1 Detailed project schedule that in-cludes all tasks, ob-jectives, milestones and resources for the conceptual data models

Due 60 days after contract award.

Schedule can be up-dated and/or revised on a bi-weekly basis, if necessary and ap-proved by the Gov-ernment.

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.3.2 JDAO Conceptual Data Models

Due 90 days after contract award.

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.3.3 Initial JDAO Enter-prise Subject Area Model

Due 120 days after contract award

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.3.4 Final JDAO Enter-prise Subject Area Model

Due 10 days after the Government has peer reviewed the initial model and provided feedback

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.3.4 Initial AOUSC En-terprise Subject Area Model

Due 140 days after contract award

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.3.5 Final AOUSC Enter-prise Subject Area Model

Due 10 days after the Government has peer reviewed the initial model and provided feedback

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.3.6 Status Report Weekly

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.3.7 Monthly Project Status and Financial Reviews

Monthly (1st Tues-day after the report-ing month)

2 (electronic copies) Contracting Officer’s Representative (COR), and the Gov-ernment Project Manager

C.4.4.1 Detailed project schedule that in-cludes all tasks, ob-jectives, milestones and resources for the conceptual data

Due180 days after contract award.

Schedule can be up-dated and/or revised on a bi-weekly basis, if necessary and ap-

2 (electronic copies) Contracting Officer’s Representative

(COR), and the Gov-ernment Project

Manager

USCA18BPAC1012 - Page 12 of 14

Date Due or Fre-quency

Form Recipient(s) models proved by the Gov-ernment.

C.4.4.2 Deliver JDAO Lo-gical Data Models

Due 210 days after contract award.

2 (electronic cop-ies)MS VISIO and

PDF, or Erwin

Contracting Officer’s Representative

(COR), and the Gov-ernment Project

Manager C.4.4.3 Initial JDAO Enter-prise Logical Data Models

Due nine months after contract award.

2 (electronic cop-ies)MS VISIO and PDF, or Erwin

Contracting Officer’s Representative

(COR), and the Gov-ernment Project

Manager C.4.4.3 Final JDAO Enter-prise Logical Data Model

Due 11 months after contract award.

2 (electronic cop-ies)MS VISIO and

PDF, or Erwin

Contracting Officer’s Representative

(COR), and the Gov-ernment Project

Manager C.4.4.4 Initial AOUSC En-terprise Logical Data Model

Due 14 months after contract award.

2 (electronic cop-ies)MS VISIO and PDF, or Erwin

Contracting Officer’s Representative

(COR), and the Gov-ernment Project

Manager C.4.4.4 Final AOUSC Enter-prise Logical Data Model

Due 16 months after contract award.

2 (electronic cop-ies)MS VISIO and PDF, or Erwin

Contracting Officer’s Representative

(COR), and the Gov-ernment Project

Manager C.4.4.5 Status Report

Weekly 2 (electronic copies) Contracting Officer’s

Representative (COR), and the Gov-ernment Project Manager

C.4.4.6 Monthly Project Status and Financial

Reviews

Monthly (1st Tues-day after the report-ing month)

2 (electronic copies) Contracting Officer’s Representative

(COR), and the Gov-ernment Project

Manager

F-2 Place of Performance and Hours of Operation

The contractor shall perform work at the AOUSC building located at One Columbus Circle Northeast, Wash-ington, DC 20002 or at contractor site pending approval by the COR. Normal business hours are from 8:30AM to 5:00PM EST Monday through Friday. Occasional after hour support and weekend work may be required.

The Government will provide ample notice for any work required outside of normal business hours. Normal workdays are Monday through Friday except US Federal Holidays.

F-3 Period of Performance

The period of performance is from the date of award for approximately eighteen months.

H-1 Key Personnel

USCA18BPAC1012 - Page 13 of 14

The following position is considered key personnel by the government under this BPA call pursuant to clause 2-65 Key Personnel in base agreement. The specific skills, experience, and qualifications are described below.

This positions must be filled by contractor personnel. Subcontractor personnel are not permitted to serve as key personnel.

Technical Project Manager:

• Primary responsibility is for the management of IT projects, which includes technical leadership, quality assurance and decision oriented recommendations;

• Provides day-to-day management of technical projects and organizes, directs, and coordinates the planning and production of project deliverables, which requires meeting project commitments, including communic-ations with sponsors, stakeholders, etc.

• May also lead or assist in the planning, introduction, and implementation of projects for new systems and technologies.

Experience: Minimum of six (6) years of experience with the management of multi-disciplined IT application/soft-ware development projects. Experience in applying agile concepts and methodologies with data warehousing/busi-ness intelligence development is desired, but not required.

Education: Bachelor’s degree in Computer Science, or Information Systems and holds a Project Management Professional (PMP) certification.

H-2 Travel

Local travel within the Washington, D.C. Metro area is expected but will not be reimbursed. Any travel outside of a 50-mile radius of Washington DC must be approved by the COR and will be in accordance with Clause 7-45 Travel that is included in the base agreement.

H-3 Government Furnished Information and Equipment

The Government will furnish to contractor employees performing work on government premises on-site office space, furniture, telephone service (for official government business only), and other necessary equipment and supplies applicable to performing the requirements set forth in this BPA Call. For contractor personnel working off government premises, the Government will be provide the applicable equipment and software to perform the requirements outlined in this BPA Call. The contractor shall be responsible for proper utilization and safeguard-ing of all Government property provided for contractor use. Contractor employees must immediately report damage, theft, or loss of Government property.

USCA18BPAC1012 - Page 14 of 14