FDA sub graph

:begin;
CREATE INDEX ON :Investment(Identifier);
CREATE INDEX ON :Metric(ID);
CREATE INDEX ON :Project(Id);
CREATE CONSTRAINT ON (node:`UNIQUE IMPORT LABEL`) ASSERT (node.`UNIQUE IMPORT ID`) IS UNIQUE;
:commit;
CALL db.awaitIndexes(300);
:begin;
UNWIND [{_id:54, properties:{Updated_Date:876, Planned_Cost:0.334, name:"FDA ORA ALM Laboratory Information Management System (LIMS) Proof of Concept", Start_days_after_2000:3561, Project_delay:0, Cost_Variance:0.008, Id:"2168", Planned_Duration:729}}, {_id:55, properties:{Updated_Date:582, Planned_Cost:1.644, name:"FDA ORA ALM Electronic Laboratory Exchange Network (eLEXNET) Support 1", Start_days_after_2000:3855, Project_delay:0, Cost_Variance:0.126, Id:"2171", Planned_Duration:538}}, {_id:56, properties:{Updated_Date:968, Planned_Cost:0.786, name:"FDA ORA ALM Quality Management Information System (QMiS) Support 1", Start_days_after_2000:3469, Project_delay:0, Cost_Variance:0.038, Id:"2173", Planned_Duration:786}}, {_id:58, properties:{Updated_Date:533, Planned_Cost:5.192, name:"FDA ORA MARCS Program Management and Technical Integration (PMTI)", Start_days_after_2000:3903, Project_delay:0, Cost_Variance:-0.122, Id:"2150", Planned_Duration:364}}, {_id:59, properties:{Updated_Date:253, Planned_Cost:0.116, name:"FDA ORA MARCS Food Safety Modernization Act (FSMA)", Start_days_after_2000:4183, Project_delay:1, Cost_Variance:-0.002, Id:"2151", Planned_Duration:76}}, {_id:60, properties:{Updated_Date:514, Planned_Cost:1.359, name:"FDA ORA MARCS Authorization, Roles, and Responsibilities Management Services (ARRMS) 2", Start_days_after_2000:3922, Project_delay:0, Cost_Variance:0.014, Id:"2152", Planned_Duration:307}}, {_id:61, properties:{Updated_Date:514, Planned_Cost:2.248, name:"FDA ORA MARCS Entry Manager (EM)", Start_days_after_2000:3922, Project_delay:0, Cost_Variance:-1.885, Id:"2154", Planned_Duration:417}}, {_id:62, properties:{Updated_Date:512, Planned_Cost:0.677, name:"FDA ORA MARCS Predictive Risk-based Evaluation and Dynamic Import Compliance Targeting (PREDICT)", Start_days_after_2000:3924, Project_delay:0, Cost_Variance:-0.024, Id:"2155", Planned_Duration:364}}, {_id:63, properties:{Updated_Date:514, Planned_Cost:1.294, name:"FDA ORA MARCS Document Generator Services (DGS)", Start_days_after_2000:3922, Project_delay:44, Cost_Variance:0.004, Id:"2156", Planned_Duration:364}}, {_id:64, properties:{Updated_Date:514, Planned_Cost:2.742, name:"FDA ORA MARCS Work Assignment and Accomplishment Manager (WAAM) 2", Start_days_after_2000:3922, Project_delay:0, Cost_Variance:-0.027, Id:"2157", Planned_Duration:364}}, {_id:65, properties:{Updated_Date:181, Planned_Cost:0.688, name:"FDA ORA MARCS Authorization, Roles, and Responsibilities Management Services (ARRMS) 2-Supplemental", Start_days_after_2000:4255, Project_delay:0, Cost_Variance:0.073, Id:"2160", Planned_Duration:185}}, {_id:66, properties:{Updated_Date:203, Planned_Cost:4.856, name:"FDA ORA MARCS Software Acquisition for Oracle Technologies", Start_days_after_2000:4233, Project_delay:0, Cost_Variance:0, Id:"2167", Planned_Duration:57}}, {_id:68, properties:{Updated_Date:371, Planned_Cost:0.507, name:"FDA ORA RBIS Center and External Integration", Start_days_after_2000:4216, Project_delay:0, Cost_Variance:0.025, Id:"2038", Planned_Duration:318}}, {_id:69, properties:{Updated_Date:329, Planned_Cost:0.584, name:"FDA ORA RBIS Data Warehouse, Data Marts, and Universes", Start_days_after_2000:4170, Project_delay:7, Cost_Variance:0.014, Id:"2039", Planned_Duration:144}}, {_id:70, properties:{Updated_Date:255, Planned_Cost:0.316, name:"FDA ORA RBIS Firm Master List Services (FMLS) Enhancements", Start_days_after_2000:4244, Project_delay:0, Cost_Variance:-0.023, Id:"2040", Planned_Duration:289}}, {_id:71, properties:{Updated_Date:315, Planned_Cost:2.085, name:"FDA ORA RBIS Report Development Support", Start_days_after_2000:4272, Project_delay:0, Cost_Variance:-1.506, Id:"2041", Planned_Duration:365}}, {_id:72, properties:{Updated_Date:290, Planned_Cost:0.275, name:"FDA ORA RBIS Data Evaluation and Recommendations", Start_days_after_2000:4272, Project_delay:0, Cost_Variance:-0.028, Id:"2042", Planned_Duration:231}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Project;
UNWIND [{_id:776, properties:{Description:"% of IT Service Requests Approved According to Established Prioritization Criteria", Metric_results:"Not Met", ID:"3512", Measurement_category:"103-Mission and Business Results - Management of Government Resources"}}, {_id:777, properties:{Description:"Number of active users utilizing RBIS ORADSS per year. Making reporting capabilities available to end users enables them to complete their work. These reports are used throughout the ORA work flows. Supports Congressional Justification Performance Measure (CJ) 214205, 224201, 234202, 234203, 244202, 244203, 253201, 254201, and 214201.", Metric_results:"Not Met", ID:"3298", Measurement_category:"115-Customer Results - Service Accessibility"}}, {_id:778, properties:{Description:"Number of firms cross matched with Dunn & Bradstreet (D&B) in RBIS FMLS. D&B contains information on firms worldwide. ORA uses this information to improve the quality of firm data that is used throughout the ORA work flows. This produces more accurate firm information for end users. Supports with CJ 214205, 224201, 234202, 234203, 244202, 244203, 253201, 254201, 214201, 214202, and 214204.", Metric_results:"Met", ID:"3299", Measurement_category:"114-Customer Results - Service Quality"}}, {_id:779, properties:{Description:"Number of objects available in RBIS ORADSS. This allows end users increased access to data without having to navigate the underlying data structures.", Metric_results:"Met", ID:"3300", Measurement_category:"202-Process and Activities - Productivity"}}, {_id:780, properties:{Description:"Number of legacy reports remaining to be migrated. RBIS ORADSS is completing the migration of old reports to the FDA standard COTS reporting tool. This will standardize the development and maintenance of reports for ORA.", Metric_results:"Not Met", ID:"3301", Measurement_category:"213-Technology - Efficiency"}}, {_id:781, properties:{Description:"Number of calls to the match and address validation service. RBIS FMLS is called to match firm information received with what is already in the firm database. Fuzzy logic is used to match received information to existing firm identifiers. If no current firm identifier can be matched, then a new firm identifier is made. This results in better information available for ORA work flows. Supports with CJ 214205, 224201, 234202, 234203, 244202, 244203, 253201, 254201, 214201, 214202, and 214204.", Metric_results:"Met", ID:"3302", Measurement_category:"214-Technology - Information and Data"}}, {_id:782, properties:{Description:"ROI. Maintain or reduce Cost per dollar collected through UFFRS", Metric_results:"Met", ID:"3596", Measurement_category:"201-Process and Activities - Financial"}}, {_id:783, properties:{Description:"Maintain or reduce unscheduled down time as a result of application/UFFRS defects", Metric_results:"Met", ID:"3597", Measurement_category:"215-Technology - Reliability and Availability"}}, {_id:784, properties:{Description:"Maintain or reduce Cost per User", Metric_results:"Met", ID:"3598", Measurement_category:"211-Technology - Technology Costs"}}, {_id:785, properties:{Description:"Reduce execution time for key reports", Metric_results:"Met", ID:"3599", Measurement_category:"203-Process and Activities - Cycle Time and Timeliness"}}, {_id:786, properties:{Description:"Increase the number of BIRS users generating special reports", Metric_results:"Met", ID:"3600", Measurement_category:"111-Customer Results - Customer Benefit"}}, {_id:787, properties:{Description:"Maintain or increase the number of regulatory actions that are  supported by UFFMS", Metric_results:"Met", ID:"3601", Measurement_category:"102-Mission and Business Results - Support Delivery of Services"}}, {_id:0, properties:{Description:"Percentage of identified Standard Operating Procedures under document control and management in QMiS. Outcome: improvement in consistently valid results.", ID:"3485", Measurement_category:"204-Process and Activities - Quality"}}, {_id:1, properties:{Description:"Percentage of ORA labs and District Offices with consistent and well-defined national quality factors in QMiS. Outcome: defined, accepted, universal culture of quality with reduced errors and support for laboratory accreditation. Aligns with 2012 Congressional Justification Performance Measure (CJ) 214206.", ID:"3486", Measurement_category:"204-Process and Activities - Quality"}}, {_id:2, properties:{Description:"Percentage of labs converted from manual to automated data entry into eLEXNET. Outcome: Reduction in FTE time required and improved response to changing conditions to support protection. Aligns with 2012 CJ 214303 and 214305.", ID:"3487", Measurement_category:"111-Customer Results - Customer Benefit"}}, {_id:164, properties:{Description:"SE: Increase the number of SE rooms", Metric_results:"Met", ID:"3499", Measurement_category:"206-Process and Activities - Management and Innovation"}}, {_id:170, properties:{Description:"Percentage of concomitant drugs in adverse event reports with validated active ingredient or trade name ", ID:"3476", Measurement_category:"111-Customer Results - Customer Benefit"}}, {_id:171, properties:{Description:"Time for retrieval of complete product information including manufacturing, regulatory, substance and labeling.", Metric_results:"Met", ID:"3474", Measurement_category:"203-Process and Activities - Cycle Time and Timeliness"}}, {_id:172, properties:{Description:"SE: maintain optimal response time as new rooms are added to the Scientific Enclave.", Metric_results:"Met", ID:"3500", Measurement_category:"215-Technology - Reliability and Availability"}}, {_id:173, properties:{Description:"DCM: Median Hours to respond and resolve Severity One outages", Metric_results:"Met", ID:"3501", Measurement_category:"113-Customer Results - Timeliness and Responsiveness"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Metric;
UNWIND [{_id:174, properties:{Description:"HPC: Increase immunity for running jobs from power outgages lasting up to 6 minutes", Metric_results:"Met", ID:"3498", Measurement_category:"101-Mission and Business Results - Services for Citizens"}}, {_id:175, properties:{Description:"HPC: Increase aggregarte avilability of spare capacity across all clusters.", Metric_results:"Met", ID:"3497", Measurement_category:"202-Process and Activities - Productivity"}}, {_id:176, properties:{Description:"DCM: Percentage of uptime at Contractor Host Data Center (CHDC) Platform Reliablity", Metric_results:"Met", ID:"3502", Measurement_category:"114-Customer Results - Service Quality"}}, {_id:177, properties:{Description:"Length of time from receipt of a non-electronic report until report is available in a database for reviewers", ID:"3475", Measurement_category:"103-Mission and Business Results - Management of Government Resources"}}, {_id:298, properties:{Description:"DCM: Percentage of uptime of FDA Critical Applications", Metric_results:"Met", ID:"3503", Measurement_category:"114-Customer Results - Service Quality"}}, {_id:299, properties:{Description:"Reduction in Operations and Maintenance Costs", ID:"3472", Measurement_category:"211-Technology - Technology Costs"}}, {_id:300, properties:{Description:"HPC: Decrease time a batch job waits before resources become available on a cluster", Metric_results:"Met", ID:"3496", Measurement_category:"101-Mission and Business Results - Services for Citizens"}}, {_id:301, properties:{Description:"Number of ORA labs with LIMS functionality. Outcome: increased laboratory surge capacity, improved tracking of inventory - e.g., reagents - and equipment calibration, resulting in cost savings. Provides equipment calibration, records for legal actions. Aligns with CJ 214305.", ID:"3489", Measurement_category:"216-Technology - Effectiveness"}}, {_id:302, properties:{Description:"Cost avoided by eliminating a separate drug quality system", ID:"3473", Measurement_category:"201-Process and Activities - Financial"}}, {_id:303, properties:{Description:"Number of hours of unplanned system downtime for eLEXNET er year. eLEXNET is a 24x7 system. Outcome: Greater reliability and availability in case of a health emergency or bioterrorism threat. Aligns with CJ 214305.", Metric_results:"Met", ID:"3488", Measurement_category:"215-Technology - Reliability and Availability"}}, {_id:754, properties:{Description:"Number of defects of fixed", Metric_results:"Not Met", ID:"3490", Measurement_category:"215-Technology - Reliability and Availability"}}, {_id:755, properties:{Description:"Incerase number of applications using SSO", Metric_results:"Met", ID:"3491", Measurement_category:"213-Technology - Efficiency"}}, {_id:756, properties:{Description:"Increase number of BLA Communications", Metric_results:"Met", ID:"3492", Measurement_category:"101-Mission and Business Results - Services for Citizens"}}, {_id:757, properties:{Description:"Reduce time for contractor to contact client on TroubleTickets ", Metric_results:"Met", ID:"3493", Measurement_category:"113-Customer Results - Timeliness and Responsiveness"}}, {_id:758, properties:{Description:"Increase number of Business Data refreshes in PreProd", Metric_results:"Met", ID:"3494", Measurement_category:"114-Customer Results - Service Quality"}}, {_id:759, properties:{Description:"Maintain SLA response times for resolution of severity 2 trouble tickets", Metric_results:"Met", ID:"3495", Measurement_category:"213-Technology - Efficiency"}}, {_id:760, properties:{Description:"Percentage of user requirements accomplished for portal configuration for eLEXNET. Outcome: Increased user satisfaction and system usage which reduces the use of telephone, etc. This results in greater staff efficiency.", ID:"3484", Measurement_category:"111-Customer Results - Customer Benefit"}}, {_id:761, properties:{Description:"Percentage validated OTC trade names in adverse event reports", ID:"3477", Measurement_category:"202-Process and Activities - Productivity"}}, {_id:762, properties:{Description:"Percentage of electronic reports from manufacturers that must go through a manual process to validate a trade name since the trade name cannot be validated automatically against existing dictionary", ID:"3478", Measurement_category:"213-Technology - Efficiency"}}, {_id:763, properties:{Description:"Number of hours of unplanned down time due to applications the Prior Notice Center. The Bioterrorism Act of 2002 requires prior notice for imported food shipments. These need to be processed on a 24x7 basis. If the system is down, then these have to be processed manually. MARCS support for this activity on a 24x7 basis is key to food security. Aligns with 2012 Congressional Justification Performance Measure (CJ) 214201.", ID:"3479", Measurement_category:"114-Customer Results - Service Quality"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Metric;
UNWIND [{_id:764, properties:{Description:"Percentage of field work flows designed for offline use. Activities that occur outside of a government facility (field activities) make up a significant portion of the work of ORA. Often these are in areas with no network connectivity. Providing the ability to conduct such work on a computer is key to improving the efficiency of field staff for imports, domestics, and foreign activities. Aligns with CJ 214205, 224201, 234202, 234203, 244202, 244203, 253201, and 254201.", ID:"3480", Measurement_category:"112-Customer Results - Service Coverage"}}, {_id:765, properties:{Description:"Number of imported products screened per year. FDA has to screen a product within two hours to meet CBP requirements to support the free flow of trade. The number of imported items has been steadily increasing and is projected to continue. PREDICT is used for risk based screening to support this throughput. Only a small portion of product can be inspected, so this screening is critical to protecting the public health. Supports CJ 214202 and 214204.", Metric_results:"Not Met", ID:"3481", Measurement_category:"202-Process and Activities - Productivity"}}, {_id:766, properties:{Description:"Percentage of work flows handled via a Business Process Management System (BPMS) supported by an Enterprise Service Bus in a Service Oriented Architecture. This is the new MARCS architecture. Work flows in the past have crossed multiple legacy systems. This produces a disjointed approach. With the BPMS, these work flows will be united, increasing efficiency and the ability to share data within FDA. Aligns with CJ 214205, 224201, 234202, 234203, 244202, 244203, 253201, and 254201.", ID:"3482", Measurement_category:"216-Technology - Effectiveness"}}, {_id:767, properties:{Description:"Percentage of MARCS functionality re-engineered from legacy systems into new components. Legacy systems have outdated architectures and, sometimes, are on obsolete technologies. Re-engineering these into the new MARCS architecture increases reliability and efficiency. Aligns with CJ 214205, 224201, 234202, 234203, 244202, 244203, 253201, and 254201.", ID:"3483", Measurement_category:"213-Technology - Efficiency"}}, {_id:768, properties:{Description:"% of IT Budget Devoted to Training and Skills Enhancement", ID:"3504", Measurement_category:"114-Customer Results - Service Quality"}}, {_id:769, properties:{Description:"% of IT Budget Devoted to R&D and Innovation", ID:"3505", Measurement_category:"206-Process and Activities - Management and Innovation"}}, {_id:770, properties:{Description:"Median # of Days to Deploy an R&D Environment in Production", ID:"3506", Measurement_category:"113-Customer Results - Timeliness and Responsiveness"}}, {_id:771, properties:{Description:"# of ITI Managers with FACPPM Certification ", Metric_results:"Not Met", ID:"3507", Measurement_category:"103-Mission and Business Results - Management of Government Resources"}}, {_id:772, properties:{Description:"Median # of Days to Resolve Severity One Outages", Metric_results:"Met", ID:"3508", Measurement_category:"203-Process and Activities - Cycle Time and Timeliness"}}, {_id:773, properties:{Description:"Number of Days Critical Business Services are Unavailable (Excluding Planned Outages)", Metric_results:"Met", ID:"3509", Measurement_category:"215-Technology - Reliability and Availability"}}, {_id:774, properties:{Description:"% of IT Service Requests Submitted with ITI Risk Assessment", ID:"3510", Measurement_category:"103-Mission and Business Results - Management of Government Resources"}}, {_id:775, properties:{Description:"% of ITI Services that Meet Published SLAs", ID:"3511", Measurement_category:"114-Customer Results - Service Quality"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Metric;
UNWIND [{_id:1025, properties:{name:"1-Services for Citizens"}}, {_id:1041, properties:{name:"4-Management of Government Resources"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Business_Area;
UNWIND [{_id:466, properties:{name:"MYTHICS, INC", ID:"W91QUZ06A0003"}}, {_id:469, properties:{name:"ELECTRONIC DATA SYSTEMS CORPORATION", ID:"HHSF223200850014I"}}, {_id:471, properties:{name:"SCENPRO, INC.", ID:"HHSF223201000039I"}}, {_id:473, properties:{name:"CNI INFORMATION TECHNOLOGY, LLC", ID:"HHSF223200850012I "}}, {_id:475, properties:{name:"CNI PROFESSIONAL SERVICES, LLC", ID:"HHSF223200950026I "}}, {_id:501, properties:{name:"HUMANTOUCH LLC", ID:"HHSF223200850020I"}}, {_id:503, properties:{name:"BUCCANEER COMPUTER SYSTEMS & SERVICE, INC.", ID:"HHSF223200850017I"}}, {_id:507, properties:{name:"PANAMERICA COMPUTERS, INC.", ID:"HHSF223200950003B"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Supplier;
UNWIND [{_id:1033, properties:{name:"753-Financial Management"}}, {_id:1035, properties:{name:"733-Knowledge Management"}}, {_id:1068, properties:{name:"711-Tracking and Workflow"}}, {_id:1112, properties:{name:"701-Customer Relationship Management"}}, {_id:1143, properties:{name:"754-Asset / Materials Management"}}, {_id:1152, properties:{name:"751-Data Management"}}, {_id:1204, properties:{name:"745-Reporting"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Service;
UNWIND [{_id:1898, properties:{planned_Costs:"0.076", Actual_duration:"73 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-08-01", No_Child_Activity:"1", name:"287623: RBIS CEI Center Views", description:"Validate requirements and functionality for Center Views", Actual_start_delay:"17 days", Id:"8353", status:"Completed - Closed", Planned_Duration:"90 days"}}, {_id:1899, properties:{planned_Costs:"0.004", Actual_duration:"76 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-08-15", No_Child_Activity:"1", name:"287623: RBIS CEI SERS Integration", description:"This task evaluates requirements to integrate ORADSS with the MARCS SERS application", Actual_start_delay:"0 days", Id:"8355", status:"Completed - Closed", Planned_Duration:"76 days"}}, {_id:1900, properties:{planned_Costs:"0.076", Actual_duration:"122 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-07-07", No_Child_Activity:"1", name:"287707: RBIS DWDMU CMS Data Mart", description:"Compliance Management System (CMS) is a stand alone legacy system under MARCS. This will provide reporting capabilities that have in the past not been available to the end users of CMS.", Actual_start_delay:"-6 days", Id:"8357", status:"Completed - Closed", Planned_Duration:"61 days"}}, {_id:1901, properties:{planned_Costs:"0.066", Actual_duration:"164 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-06-02", No_Child_Activity:"1", name:"287707: RBIS DWDMU Work Force Reporting Enhancements Requirements and Design", description:"This is focusing on reworking the old tables that contain work force information and providing an updated universe and reports to support work planning and accomplishment monitoring activities. This activity focuses on requirements and design.", Actual_start_delay:"-13 days", Id:"8362", status:"Completed - Closed", Planned_Duration:"127 days"}}, {_id:1902, properties:{planned_Costs:"0.127", Actual_duration:"38 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-08-01", No_Child_Activity:"1", name:"287707: RBIS DWDMU Work Force Reporting Enhancements Development, Test, and Implementation", description:"This is focusing on reworking the old tables that contain work force information and providing an updated universe and reports to support work planning and accomplishment monitoring activities. This activity focuses on development, test, and implementation.", Actual_start_delay:"53 days", Id:"8363", status:"Completed - Closed", Planned_Duration:"71 days"}}, {_id:1903, properties:{planned_Costs:"0.077", Actual_duration:"122 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-07-01", No_Child_Activity:"1", name:"287707: RBIS DWDMU  Report Migrations Automated Conversion", description:"This is migrating a number of currently existing reports from the desktop based Business Objects application to the web based version. This will make these reports more available and easier to maintain and modify.", Actual_start_delay:"0 days", Id:"8365", status:"Completed - Closed", Planned_Duration:"49 days"}}, {_id:1904, properties:{planned_Costs:"0.022", Actual_duration:"59 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-08-19", No_Child_Activity:"1", name:"287707: RBIS DWDMU Report Migrations Manual Conversions of Often Used Reports", description:"This is migrating a number of currently existing reports from the desktop based Business Objects application to the web based version. This will make these reports more available and easier to maintain and modify.", Actual_start_delay:"14 days", Id:"8366", status:"Completed - Closed", Planned_Duration:"66 days"}}, {_id:1905, properties:{planned_Costs:"0.127", Actual_duration:"126 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-06-27", No_Child_Activity:"1", name:"287707: RBIS DWDMU OPAS Modernization to BO Voyager", description:"This is to modernize the Business Objects (BO) COTS to use improved and newer functionality.", Actual_start_delay:"0 days", Id:"8369", status:"Completed - Closed", Planned_Duration:"79 days"}}, {_id:1906, properties:{planned_Costs:"0.021", Actual_duration:"74 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-08-18", No_Child_Activity:"1", name:"287707: RBIS DWDMU OPAS Modernization to Informatica 9", description:"This is to modernize the Informatica COTS to use improved and newer functionality. Informatica is used for data aggregation, manipulation, and analysis.", Actual_start_delay:"0 days", Id:"8370", status:"Completed - Closed", Planned_Duration:"67 days"}}, {_id:2247, properties:{planned_Costs:"0.246", Actual_duration:"54 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-09-08", No_Child_Activity:"1", name:"286120: PMTI Program and Project Deliverables", description:"This includes program and project management deliverables that are produced or significantly updated once during the execution of this project. This includes a Quality Assurance Plan (QAP), a Quality Assurance Surveillance Plan (QASP), Program Management Plan (PMP), Work Breakdown Structure (WBS) and dictionary, Risk Management Plan (RMP), Communications Plan (CP), Configuration Management Plan (CMP), Task Order Schedule (TOS), and Integrated Master Schedule (IMS).", Actual_start_delay:"0 days", Id:"9211", status:"Completed - Closed", Planned_Duration:"54 days"}}, {_id:2248, properties:{planned_Costs:"1.248", Actual_duration:"180 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-09-08", No_Child_Activity:"1", name:"286120: PMTI Program and Project Management Recurring Meetings and Deliverables, Including Stage Gates 1", description:"This includes a number of activities that are recurring such as weekly meetings and status reports.  Also included are IMS updates, risk list updates, Contract Performance Reports (CPR) for EVM, Stage Gates, internal meetings, other meetings with FDA, and other program and project management activities.", Actual_start_delay:"0 days", Id:"9212", status:"Completed - Closed", Planned_Duration:"180 days"}}, {_id:2249, properties:{planned_Costs:"1.268", Actual_duration:"183 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-03-08", No_Child_Activity:"1", name:"286120: PMTI Program and Project Management Recurring Meetings and Deliverables, Including Stage Gates 2", description:"This includes a number of activities that are recurring such as weekly meetings and status reports.  Also included are IMS updates, risk list updates, Contract Performance Reports (CPR) for EVM, Stage Gates, internal meetings, other meetings with FDA, and other program and project management activities.", Actual_start_delay:"0 days", Id:"9213", status:"Completed - Closed", Planned_Duration:"183 days"}}, {_id:2250, properties:{planned_Costs:"0.568", Actual_duration:"180 days", output_type:"Usable Functionality", Start_Date_Planned:"2010-09-08", No_Child_Activity:"1", name:"286120: PMTI Technical Integration 1", description:"This includes work for IT security, system architecture, and data integration.", Actual_start_delay:"0 days", Id:"9215", status:"Completed - Closed", Planned_Duration:"180 days"}}, {_id:2251, properties:{planned_Costs:"0.616", Actual_duration:"183 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-03-08", No_Child_Activity:"1", name:"286120: PMTI Technical Integration 2", description:"This includes work for IT security, system architecture, and data integration.", Actual_start_delay:"0 days", Id:"9216", status:"Completed - Closed", Planned_Duration:"183 days"}}, {_id:2252, properties:{planned_Costs:"0.123", Actual_duration:"180 days", output_type:"Usable Functionality", Start_Date_Planned:"2010-09-08", No_Child_Activity:"1", name:"286120: PMTI Release Integration 1", description:"This provides support for smaller releases only involving legacy systems.", Actual_start_delay:"0 days", Id:"9218", status:"Completed - Closed", Planned_Duration:"180 days"}}, {_id:2253, properties:{planned_Costs:"0.123", Actual_duration:"183 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-03-08", No_Child_Activity:"1", name:"286120: PMTI Release Integration 2", description:"This provides support for smaller releases only involving legacy systems.", Actual_start_delay:"0 days", Id:"9219", status:"Completed - Closed", Planned_Duration:"183 days"}}, {_id:2254, properties:{planned_Costs:"0.1", Actual_duration:"136 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-02-01", No_Child_Activity:"1", name:"286120: PMTI Release Integration MARCS 0.5 to Pre-Production", description:"This provides support for MARCS 0.5 release.  Performance and user acceptance testing, security testing, promotion to Production.", Actual_start_delay:"0 days", Id:"9221", status:"Completed - Closed", Planned_Duration:"136 days"}}, {_id:2255, properties:{planned_Costs:"0.05", Actual_duration:"96 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-06-03", No_Child_Activity:"1", name:"286120: PMTI Release Integration MARCS 0.5 to Production", description:"This provides support for MARCS 0.5 release.  Performance and user acceptance testing, security testing, promotion to Production.", Actual_start_delay:"0 days", Id:"9222", status:"Completed - Closed", Planned_Duration:"96 days"}}, {_id:2256, properties:{planned_Costs:"0.5", Actual_duration:"309 days", output_type:"Usable Functionality", Start_Date_Planned:"2010-11-02", No_Child_Activity:"1", name:"286120: PMTI Release Integration MARCS 1.0 to Pre-Production", description:"This provides support for MARCS 1.0 release. System integration testing, promotion to Pre-Production.", Actual_start_delay:"0 days", Id:"9224", status:"Completed - Closed", Planned_Duration:"153 days"}}, {_id:2257, properties:{planned_Costs:"0.15", Actual_duration:"155 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-04-05", No_Child_Activity:"1", name:"286120: PMTI Release Integration MARCS 1.0 to Production", description:"This provides support for MARCS 1.0 release.  Performance and user acceptance testing, security testing, promotion to Production. ", Actual_start_delay:"0 days", Id:"9225", status:"Completed - Closed", Planned_Duration:"155 days"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Activity;
UNWIND [{_id:2258, properties:{planned_Costs:"0.2", Actual_duration:"159 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-04-01", No_Child_Activity:"1", name:"286120: PMTI Release Integration MARCS 1.1", description:"This provides support for MARCS 1.1 release. This includes testing, configuration management, promotion through environments, and coordination with ORA and OIM.", Actual_start_delay:"0 days", Id:"9226", status:"Completed - Closed", Planned_Duration:"159 days"}}, {_id:2259, properties:{planned_Costs:"0.116", Actual_duration:"77 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-06-15", No_Child_Activity:"1", name:"286177: Food Safety Modernization Act (FSMA) Parent Activity", description:"This project implemented functionality for Section 304 of FSMA. This is Prior Notice functionality required for 801(m) screening that had a legislative deadline for implementation and involved changes to Operational and Administrative System for Imports Support (OASIS) and Prior Notice System Interface (PNSI).", Actual_start_delay:"0 days", Id:"9227", status:"Completed - Closed", Planned_Duration:"76 days"}}, {_id:2260, properties:{planned_Costs:"0.141", Actual_duration:"98 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-09-27", No_Child_Activity:"1", name:"286202: ARRMS 2 Requirements Validation and Decision Analysis", description:"This conducted a survey and investigation into COTS products available and produced a recommendation for a COTS to fulfill most of the requirements for ARRMS.", Actual_start_delay:"0 days", Id:"9229", status:"Completed - Closed", Planned_Duration:"98 days"}}, {_id:2261, properties:{planned_Costs:"0.288", Actual_duration:"124 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-10-27", No_Child_Activity:"1", name:"286202: ARRMS 2 Requirements Validation and Decision Analysis", description:"This validated requirements to determine which ones would be fulfilled by a COTS and which ones would need custom development. ", Actual_start_delay:"0 days", Id:"9230", status:"Completed - Closed", Planned_Duration:"124 days"}}, {_id:2262, properties:{planned_Costs:"0.242", Actual_duration:"144 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-02-14", No_Child_Activity:"1", name:"286202: ARRMS 2 Requirements Validation Integration with ALM and RBIS", description:"This validated requirements for integrating with ALM and RBIS in the future.", Actual_start_delay:"0 days", Id:"9231", status:"Completed - Closed", Planned_Duration:"144 days"}}, {_id:2263, properties:{Actual_duration:"191 days", planned_Costs:"0.5", output_type:"Key Deliverable", Start_Date_Planned:"2011-01-21", No_Child_Activity:"1", name:"286202: ARRMS 2 Design ", description:"This produced a design for incorporating the COTS chosen by FDA.", Actual_start_delay:"0 days", Id:"9232", status:"Completed - Closed", Planned_Duration:"191 days"}}, {_id:2264, properties:{Actual_duration:"24 days", planned_Costs:"0.188", output_type:"Usable Functionality", Start_Date_Planned:"2011-06-13", No_Child_Activity:"1", name:"286202: ARRMS 2 Development", description:"This is to produce functionality for roles and organizations.", Actual_start_delay:"24 days", Id:"9233", status:"Completed - Closed", Planned_Duration:"48 days"}}, {_id:2289, properties:{planned_Costs:"0.268", Actual_duration:"112 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-09-27", No_Child_Activity:"1", name:"286212: EM Business Requirements ", description:"This gathered requirements for Entry Query business considerations.", Actual_start_delay:"0 days", Id:"9272", status:"Completed - Closed", Planned_Duration:"112 days"}}, {_id:2290, properties:{planned_Costs:"0.367", Actual_duration:"127 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-01-18", No_Child_Activity:"1", name:"286212: EM Functional, Non Functional, and User Interface Requirements", description:"This gathered requirements for Entry Query functionality, user interface, and non functional considerations.", Actual_start_delay:"0 days", Id:"9273", status:"Completed - Closed", Planned_Duration:"127 days"}}, {_id:2291, properties:{planned_Costs:"0.357", Actual_duration:"161 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-01-03", No_Child_Activity:"1", name:"286212: EM Preliminary Design", description:"This produced a preliminary design for Entry Query functionality within EM.", Actual_start_delay:"37 days", Id:"9275", status:"Completed - Closed", Planned_Duration:"191 days"}}, {_id:2320, properties:{planned_Costs:"0.215", Actual_duration:"131 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-04-05", No_Child_Activity:"1", name:"286217: WAAM 2 Inspections Development Iterations 3 and 4", description:"MARCS uses an iterative approach to development. For Inspections, four iterations were used to build out functionality, verify that it is correct, and then expand on that functionality. This is the second two of those iterations.", Actual_start_delay:"43 days", Id:"9317", status:"Completed - Closed", Planned_Duration:"168 days"}}, {_id:2321, properties:{planned_Costs:"0.082", Actual_duration:"131 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-04-05", No_Child_Activity:"1", name:"286217: WAAM 2 Inspections Test", description:"This is for conducting unit and regression testing for Inspections functionality.", Actual_start_delay:"43 days", Id:"9318", status:"Completed - Closed", Planned_Duration:"174 days"}}, {_id:2322, properties:{planned_Costs:"0.061", Actual_duration:"172 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-10-15", No_Child_Activity:"1", name:"286217: WAAM 2 Import Field Exams Business Requirements ", description:"This is to gather business requirements for Import Field Exams. This focused on migrating and enhancing current functionality. It also included an examination of import and domestic field examination types to determine where terminology and method could be appropriately shared between the two.", Actual_start_delay:"0 days", Id:"9321", status:"Completed - Closed", Planned_Duration:"112 days"}}, {_id:2323, properties:{planned_Costs:"0.033", Actual_duration:"155 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-02-07", No_Child_Activity:"1", name:"286217: WAAM 2 Import Field Exams Functional Requirements", description:"This is to gather functional requirements for Import Field Exams", Actual_start_delay:"0 days", Id:"9322", status:"Completed - Closed", Planned_Duration:"67 days"}}, {_id:2324, properties:{planned_Costs:"0.045", Actual_duration:"81 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-07-07", No_Child_Activity:"1", name:"286217: WAAM 2 Import Field Exams Non Functional and User Interface Requirements", description:"This is to gather non functional and user interface requirements for Field Exams.", Actual_start_delay:"0 days", Id:"9323", status:"Completed - Closed", Planned_Duration:"55 days"}}, {_id:2325, properties:{planned_Costs:"0.091", Actual_duration:"103 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-06-15", No_Child_Activity:"1", name:"286217: WAAM 2 Import Field Exams Design", description:"This produced a design for WAAM that supports Import Field Exams functionality and also includes considerations for the Domestic Field Exams.", Actual_start_delay:"0 days", Id:"9324", status:"Completed - Closed", Planned_Duration:"103 days"}}, {_id:2326, properties:{planned_Costs:"0.121", Actual_duration:"140 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-05-09", No_Child_Activity:"1", name:"286217: WAAM 2 Import Field Exams Development", description:"This produced code to realize Import Field Exam functionality.", Actual_start_delay:"0 days", Id:"9325", status:"Completed - Closed", Planned_Duration:"140 days"}}, {_id:2327, properties:{planned_Costs:"0.037", Actual_duration:"42 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-08-15", No_Child_Activity:"1", name:"286217: WAAM 2 Import Field Exams Test", description:"This is for conducting unit and regression testing for Import Field Exam functionality.", Actual_start_delay:"0 days", Id:"9326", status:"Completed - Closed", Planned_Duration:"42 days"}}, {_id:2328, properties:{planned_Costs:"0.051", Actual_duration:"167 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-01-13", No_Child_Activity:"1", name:"286217: WAAM 2 Work Planner Business Requirements", description:"One of the challenges faced by ORA is typing work performed correctly. There are a number of existing categories for work, but sometimes the definitions of these are not clear. There are also a number of situations that arise where someone performing Field work could classify that work in different ways using the current work taxonomy. This was addressed in this requirements gathering in order to make it more intuitive for Field users to classify their work according to what they actually do and give the ORA management structure the ability to plan work and pull reports.", Actual_start_delay:"0 days", Id:"9329", status:"Completed - Closed", Planned_Duration:"167 days"}}, {_id:2329, properties:{planned_Costs:"0.036", Actual_duration:"41 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-07-01", No_Child_Activity:"1", name:"286217: WAAM 2 Work Planner Functional, Non Functional, and User Interface Requirements", description:"This is to gather requirements for building Work Planner.", Actual_start_delay:"0 days", Id:"9330", status:"Completed - Closed", Planned_Duration:"41 days"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Activity;
UNWIND [{_id:2330, properties:{planned_Costs:"0.032", Actual_duration:"93 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-02-22", No_Child_Activity:"1", name:"286217: WAAM 2 Work Planner Design for User Interface and Logical", description:"This produced a design for WAAM that supports Work Planner for the annual plan for user interfaces and logical software and data considerations.", Actual_start_delay:"0 days", Id:"9332", status:"Completed - Closed", Planned_Duration:"93 days"}}, {_id:2331, properties:{planned_Costs:"0.024", Actual_duration:"91 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-05-26", No_Child_Activity:"1", name:"286217: WAAM 2 Work Planner Design for Services Specifications", description:"This produced a design for WAAM that supports Work Planner for the annual plan. This took into account functionality that will be needed from the various MARCS services.", Actual_start_delay:"0 days", Id:"9333", status:"Completed - Closed", Planned_Duration:"91 days"}}, {_id:2332, properties:{planned_Costs:"0.103", Actual_duration:"111 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-06-07", No_Child_Activity:"1", name:"286217: WAAM 2 Work Planner Design for Physical Data, Security, Interfaces, and Data Synchronization", description:"This produced a design for WAAM that supports Work Planner for the annual plan. This took into account the physical data design, security ramifications, interface specifications, and considerations for migrating data.", Actual_start_delay:"0 days", Id:"9334", status:"Completed - Closed", Planned_Duration:"100 days"}}, {_id:2333, properties:{planned_Costs:"0.167", Actual_duration:"175 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-04-04", No_Child_Activity:"1", name:"286217: WAAM 2 Work Planner Development", description:"This produced code to realize Work Planner functionality.", Actual_start_delay:"0 days", Id:"9335", status:"Completed - Closed", Planned_Duration:"172 days"}}, {_id:2334, properties:{planned_Costs:"0.078", Actual_duration:"69 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-07-19", No_Child_Activity:"1", name:"286217: WAAM 2 Work Planner Test", description:"This is for conducting unit and regression testing for Work Planner functionality.", Actual_start_delay:"0 days", Id:"9336", status:"Completed - Closed", Planned_Duration:"69 days"}}, {_id:2335, properties:{planned_Costs:"0.145", Actual_duration:"132 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-10-08", No_Child_Activity:"1", name:"286217: WAAM 2 Domestic Field Exams, Sample Collection, National Sample Distributor, and Other Business Requirements", description:"WAAM will need to support all of the regulatory work flows in ORA since it will be the hub of work within MARCS. This is to start collecting requirements for these future work types. This is for business related requirements that often deal with how to standardize procedures and approaches amongst different organizational units.", Actual_start_delay:"0 days", Id:"9338", status:"Completed - Closed", Planned_Duration:"132 days"}}, {_id:2336, properties:{planned_Costs:"0.113", Actual_duration:"152 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-04-27", No_Child_Activity:"1", name:"286217: WAAM 2 Domestic Field Exams, Sample Collection, National Sample Distributor, and Other Functional, Non Functional, and User Interface Requirements", description:"WAAM will need to support all of the regulatory work flows in ORA since it will be the hub of work within MARCS. This is to start collecting requirements for these future work types. This is to gather requirements for realizing functionality.", Actual_start_delay:"0 days", Id:"9339", status:"Completed - Closed", Planned_Duration:"146 days"}}, {_id:2339, properties:{planned_Costs:"4.856", Actual_duration:"57 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-08-04", No_Child_Activity:"1", name:"286298: Software Acquisition for Oracle Technologies Parent Activity", description:"This is a software acquisition of COTS technologies. This includes an expansion of the licenses for the BPMS (Business Process Management Suite) (including Enterprise Service Bus (ESB) and Service Oriented Architecture (SOA)), Oracle Identity Management (IDM) Suite, WebCenter, Oracle Policy Automation (OPA), and Real User Experience Insight (RUEI). The license expansion for the BPMS includes enough licenses for all FDA users. A number of FDA Centers have expressed interest in using this platform for their systems. MARCS has a primary focus on integration across the organization and as the BPMS would help further this goal, these licenses have been expanded to enable organization wide integration. IDM will give MARCS a comprehensive COTS solution to provide the specialized functionality and fine grained security control envisioned. This will require some custom code to realize envisioned functionality. The custom code will be developed under Authorization, Roles, and Responsibilities Management Services (ARRMS) 2 - Supplemental. IDM may also be leveraged as an FDA wide solution in the future. The implementation of IDM will be used by every component within MARCS. This has been vetted with the FDA CIO and HHS CIO and conforms to HHS standard security. WebCenter provides robust user interface and portal capabilities. This COTS will be used to implement User Workspace Enhancement Services (UWES), which is part of the Support Services project. UWES will provide a standardized user experience customized based on user role and single user preferences. OPA is a rules engine that will have a number of applications in MARCS ranging from inspection preparation, intelligent questionnaires, and import screening support. RUEI is a tool that can be used from a centralized location to determine the experience that an end user at a remote site is having. ORA is a geographically dispersed organization. In this sense, the user community for MARCS is different from Center user communities since the vast majority of users are not in the Washington, DC metropolitan area. This tool will give ORA and OIM a new ability to understand what is actually happening at user sites and will enable a systematic approach towards improving performance and reliability in the Field. The software acquired will be used in all of the MARCS projects going forward to one degree or another and will enable MARCS functionality that will be realized in releases.", Actual_start_delay:"0 days", Id:"9364", status:"Completed - Closed", Planned_Duration:"57 days"}}, {_id:2340, properties:{planned_Costs:"0.032", Actual_duration:"75 days", output_type:"Key Deliverable", Start_Date_Planned:"2009-10-01", No_Child_Activity:"1", name:"287489: LIMS Proof of Concept Analysis", description:"This focused on conducting an analysis of current manual work flows involving the use of the 431 form in ORA laboratories. This form is used by bench analysts to record the actions taken during sample analyses. Data is hand written onto this form. Once complete, the data is manually entered into the legacy MARCS Field Accomplishments and Compliance Tracking System (FACTS). This is an outdated approach to collecting this data and results in a good amount of analyst time being spent on filling out this form and entering data rather than conducting lab work. The analysis looked at ways to approach making this form electronic.", Actual_start_delay:"0 days", Id:"9366", status:"Completed - Closed", Planned_Duration:"75 days"}}, {_id:2341, properties:{planned_Costs:"0.072", Actual_duration:"149 days", output_type:"Usable Functionality", Start_Date_Planned:"2009-12-16", No_Child_Activity:"1", name:"287489: LIMS Proof of Concept Phase 1", description:"Based on the results of the analysis it was determined that the most general approach to handling this information was to build a set of forms using FileMaker Pro for use on both tablet laptops and a handheld device. The tablet laptops may be placed on small mobile carts which can be wheeled to various locations within a static laboratory in a building. The handheld device can be used in static laboratories and also in the two mobile laboratory units. Phase 1 built out basic functionality on these two platforms for use within one ORA laboratory.", Actual_start_delay:"0 days", Id:"9367", status:"Completed - Closed", Planned_Duration:"142 days"}}, {_id:2342, properties:{planned_Costs:"0.125", Actual_duration:"160 days", output_type:"Usable Functionality", Start_Date_Planned:"2010-05-10", No_Child_Activity:"1", name:"287489: LIMS Proof of Concept Phase 2", description:"Phase 2 expands on the work of phase 1 to build out all of the forms needed to collect the data that currently goes on a 431 form. This includes basic user login and a database at the single ORA laboratory where this was tested.", Actual_start_delay:"5 days", Id:"9368", status:"Completed - Closed", Planned_Duration:"165 days"}}, {_id:2343, properties:{planned_Costs:"0.05", Actual_duration:"164 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-10-25", No_Child_Activity:"1", name:"287489: LIMS Proof of Concept Phase 3", description:"Phase 3 focused on analyzing and testing approaches to aggregating data collected from multiple laboratory sites so that it could be automatically picked up and fed back into MARCS FACTS.", Actual_start_delay:"0 days", Id:"9369", status:"Completed - Closed", Planned_Duration:"164 days"}}, {_id:2344, properties:{planned_Costs:"0.055", Actual_duration:"175 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-04-08", No_Child_Activity:"1", name:"287489: LIMS Proof of Concept Phase 4", description:"Phase 4 expands the proof of concept to two additional labs to gather user feedback and test the effectiveness of the implementation.", Actual_start_delay:"0 days", Id:"9370", status:"Completed - Closed", Planned_Duration:"175 days"}}, {_id:2347, properties:{planned_Costs:"0.097", Actual_duration:"169 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-10-13", No_Child_Activity:"1", name:"287496: eLEXNET Common Login 1", description:"Requirements and Preliminary Design for Common Login.", Actual_start_delay:"0 days", Id:"9383", status:"Completed - Closed", Planned_Duration:"169 days"}}, {_id:2348, properties:{planned_Costs:"0.061", Actual_duration:"179 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-04-01", No_Child_Activity:"1", name:"287496: eLEXNET Common Login 2", description:"Design and Development for Common Login.", Actual_start_delay:"0 days", Id:"9384", status:"Completed - Closed", Planned_Duration:"179 days"}}, {_id:2349, properties:{planned_Costs:"0.077", Actual_duration:"94 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-09-28", No_Child_Activity:"1", name:"287496: eLEXNET Common Login 3", description:"Test and Implementation for Common Login.", Actual_start_delay:"0 days", Id:"9385", status:"Completed - Costs Pending", Planned_Duration:"105 days"}}, {_id:2350, properties:{planned_Costs:"0.191", Actual_duration:"157 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-02-14", No_Child_Activity:"1", name:"287496: eLEXNET Interagency Database for Dioxin", description:"Enhancing the current eLEXNET database to include DIOXIN specific data fields; centralizing interagency database to incorporate FDA (ORA, CVM and CFSAN), USDA and EPA dioxin analytical results in addition to geographical and collection information. ", Actual_start_delay:"0 days", Id:"9386", status:"Completed - Closed", Planned_Duration:"157 days"}}, {_id:2351, properties:{Actual_duration:"162 days", planned_Costs:"0.084", output_type:"Key Deliverable", Start_Date_Planned:"2010-07-22", No_Child_Activity:"1", name:"287496: eLEXNET Outreach 1", description:"Develop outreach strategies and approaches for reaching out to three pirmary stakeholder groups - state labs, government labs, and private labs. This focuses on reaching out to state labs first due to the heavy reliance of these labs on manual data exchange.", Actual_start_delay:"0 days", Id:"9388", status:"Completed - Closed", Planned_Duration:"162 days"}}, {_id:2352, properties:{Actual_duration:"119 days", planned_Costs:"0.064", output_type:"Key Deliverable", Start_Date_Planned:"2011-01-01", No_Child_Activity:"1", name:"287496: eLEXNET Outreach 2", description:"Outreach to stakeholder groups with an emphasis on government labs and state lab follow up outreach.", Actual_start_delay:"0 days", Id:"9389", status:"Completed - Closed", Planned_Duration:"119 days"}}, {_id:2353, properties:{Actual_duration:"85 days", planned_Costs:"0.049", output_type:"Key Deliverable", Start_Date_Planned:"2011-05-01", No_Child_Activity:"1", name:"287496: eLEXNET Outreach 3", description:"Outreach to stakeholder groups with an emphasis on private labs and government and state lab follow up outreach.", Actual_start_delay:"0 days", Id:"9390", status:"Completed - Closed", Planned_Duration:"85 days"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Activity;
UNWIND [{_id:2354, properties:{planned_Costs:"0.232", Actual_duration:"103 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-11-17", No_Child_Activity:"1", name:"287496: eLEXNET Methods Module 1", description:"Requirements and Design for the Methods Module.", Actual_start_delay:"0 days", Id:"9392", status:"Completed - Closed", Planned_Duration:"103 days"}}, {_id:2355, properties:{planned_Costs:"0.371", Actual_duration:"142 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-03-01", No_Child_Activity:"1", name:"287496: eLEXNET Methods Module 2", description:"Development, Test, and Implemenation of the Methods Module.", Actual_start_delay:"0 days", Id:"9393", status:"Completed - Closed", Planned_Duration:"142 days"}}, {_id:2356, properties:{planned_Costs:"0.209", Actual_duration:"158 days", output_type:"Usable Functionality", Start_Date_Planned:"2010-11-01", No_Child_Activity:"1", name:"287496: eLEXNET Laboratory Expansion 1", description:"Develop make available supporting customized data transfer for new labs.", Actual_start_delay:"0 days", Id:"9395", status:"Completed - Closed", Planned_Duration:"158 days"}}, {_id:2357, properties:{planned_Costs:"0.209", Actual_duration:"101 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-04-11", No_Child_Activity:"1", name:"287496: eLEXNET Laboratory Expansion 2", description:"Develop make available supporting customized data transfer for new labs.", Actual_start_delay:"0 days", Id:"9396", status:"Completed - Closed", Planned_Duration:"101 days"}}, {_id:2358, properties:{Actual_duration:"32 days", planned_Costs:"0.06", output_type:"Usable Functionality", Start_Date_Planned:"2010-09-17", No_Child_Activity:"1", name:"287509: QMiS Release 1.0", description:"This is the initial release of the MasterControl COTS tool at FDA. This was allowed to operate with Security waivers. This includes the activities to support a minimal first release.", Actual_start_delay:"0 days", Id:"9402", status:"Completed - Closed", Planned_Duration:"32 days"}}, {_id:2359, properties:{Actual_duration:"34 days", planned_Costs:"0.052", output_type:"Key Deliverable", Start_Date_Planned:"2010-09-17", No_Child_Activity:"1", name:"287509: QMiS Release 1.1.1", description:"This is the second release of the MasterControl COTS tool at FDA. This resolves all of the security issues associated with the previous release. This includes work on upgrading the COTS to a newer version, a System Security Plan, and a Contingency Plan.", Actual_start_delay:"0 days", Id:"9404", status:"Completed - Closed", Planned_Duration:"34 days"}}, {_id:2360, properties:{Actual_duration:"154 days", planned_Costs:"0.237", output_type:"Usable Functionality", Start_Date_Planned:"2010-10-22", No_Child_Activity:"1", name:"287509: QMiS Release 1.1.2", description:"This is the second release of the MasterControl COTS tool at FDA. This resolves all of the security issues associated with the previous release. This includes design and configuration of Single Sign On, full security assessment, and testing in Pre-Production. This also includes temporary COTS licenses and professional services.", Actual_start_delay:"0 days", Id:"9405", status:"Completed - Closed", Planned_Duration:"154 days"}}, {_id:2361, properties:{Actual_duration:"125 days", planned_Costs:"0.174", output_type:"Usable Functionality", Start_Date_Planned:"2011-03-28", No_Child_Activity:"1", name:"287509: QMiS Release 1.1.3", description:"This is the second release of the MasterControl COTS tool at FDA. This resolves all of the security issues associated with the previous release. This includes promotion to Production and final release. This also includes temporary COTS licenses and professional services.", Actual_start_delay:"0 days", Id:"9406", status:"Completed - Closed", Planned_Duration:"125 days"}}, {_id:2362, properties:{Actual_duration:"63 days", planned_Costs:"0.04", output_type:"Key Deliverable", Start_Date_Planned:"2010-09-17", No_Child_Activity:"1", name:"287509: QMiS Training 1", description:"This includes training for OIM technical personnel and training for end users for Release 1.0. This is focused on getting technical personnel up to speed and getting end users started on limited functionality, mostly related to document control.", Actual_start_delay:"0 days", Id:"9408", status:"Completed - Closed", Planned_Duration:"63 days"}}, {_id:2363, properties:{Actual_duration:"144 days", planned_Costs:"0.04", output_type:"Key Deliverable", Start_Date_Planned:"2010-11-01", No_Child_Activity:"1", name:"287509: QMiS Training 2", description:"This includes training for OIM technical personnel for Release 1.1. This focuses on producing FDA in house technical expertise.", Actual_start_delay:"0 days", Id:"9409", status:"Completed - Closed", Planned_Duration:"144 days"}}, {_id:2364, properties:{Actual_duration:"109 days", planned_Costs:"0.055", output_type:"Key Deliverable", Start_Date_Planned:"2011-01-10", No_Child_Activity:"1", name:"287509: QMiS Training 3", description:"This includes training for end users for Release 1.1. This includes the development of training materials and courses for end users.", Actual_start_delay:"0 days", Id:"9410", status:"Completed - Closed", Planned_Duration:"109 days"}}, {_id:2365, properties:{planned_Costs:"0.128", output_type:"Key Deliverable", Start_Date_Planned:"2011-06-14", No_Child_Activity:"1", name:"287509: QMiS Training 4", description:"This includes training for end users for Release 1.1. This provides full training to end users.", Actual_start_delay:"0 days", Id:"9411", status:"In-progress", Planned_Duration:"73 days"}}, {_id:2755, properties:{planned_Costs:"0.067", Actual_duration:"60 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-08-26", No_Child_Activity:"1", name:"286255: FDA ORA MARCS ARRMS 2 - Supplemental Startup Project Key Deliverables", description:"Includes SRA Project Startup activities, the Project Initiation and Kickoff, development of the Project Management Plan Addendum, the project schedule, the Test Plan Addendum, and the Logical Data Model and Data Dictionary. ", Actual_start_delay:"0 days", Id:"12398", status:"Completed - Closed", Planned_Duration:"60 days"}}, {_id:2756, properties:{planned_Costs:"0.428", Actual_duration:"95 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-09-19", No_Child_Activity:"1", name:"286255: FDA ORA MARCS ARRMS 2 - Supplemental Agile Iterations", description:"Includes Sprint Execution for four sprints (Planning, Requirements, Design, Development, System Test, User Demonstration, User Testing) to complete functionality that will facilitate adding a user, establishing and maintaining user authorizations, maintaining user, role and organization data, facilitating authorization integration with MARCS components, integration with Oracle Identity Management products and reporting.  Also include production of associated documentation and Stage Gates (Planning, High Level Requirements & Design).", Actual_start_delay:"0 days", Id:"12399", status:"Completed - Costs Pending", Planned_Duration:"95 days"}}, {_id:2757, properties:{planned_Costs:"0.193", output_type:"Usable Functionality", Start_Date_Planned:"2011-12-15", No_Child_Activity:"1", name:"286255: FDA ORA MARCS ARRMS 2 - Supplemental Test and Delivery", description:"Includes Regression and final System Testing, the consolidation of documentation from the Sprint package in the development of final EPLC artifacts, the development of the System Test Report, the Version Description Document (VDD) and Project Closeout.", Actual_start_delay:"0 days", Id:"12400", status:"In-progress", Planned_Duration:"74 days"}}, {_id:2811, properties:{planned_Costs:"0.145", Actual_duration:"166 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-07-18", No_Child_Activity:"1", name:"287623: RBIS CEI PREDICT Integration Phase 1 ", description:"This will produce an interface with Mission Accomplishments and Regulatory Compliance Services (MARCS) Predictive Risk-based Evaluation and Dynamic Import Compliance Targeting (PREDICT) to support daily transfer of transactional data from PREDICT into the ORADSS Data Warehouse (DW) and the planned PREDICT Data Mart (DM). This will produce Extract, Transform, and Load (ETL) functionality to transfer data from PREDICT to ORADSS.  This task covers work that will be completed during the first phase of PREDICT Integration.  ", Actual_start_delay:"0 days", Id:"12531", status:"Completed - Closed", Planned_Duration:"166 days"}}, {_id:2812, properties:{planned_Costs:"0.015", Actual_duration:"30 days", output_type:"Usable Functionality", Start_Date_Planned:"2012-01-01", No_Child_Activity:"1", name:"287623: RBIS CEI PREDICT Integration Phase 2 PREDICT Acceptance", description:"This will produce an interface with Mission Accomplishments and Regulatory Compliance Services (MARCS) Predictive Risk-based Evaluation and Dynamic Import Compliance Targeting (PREDICT) to support daily transfer of transactional data from PREDICT into the ORADSS Data Warehouse (DW) and the planned PREDICT Data Mart (DM). This will produce Extract, Transform, and Load (ETL) functionality to transfer data from PREDICT to ORADSS.  This task covers work that will be completed during the second phase of PREDICT Integration.", Actual_start_delay:"0 days", Id:"12532", status:"Completed - Closed", Planned_Duration:"89 days"}}, {_id:2813, properties:{Actual_duration:"76 days", planned_Costs:"0.062", output_type:"Usable Functionality", Start_Date_Planned:"2011-08-01", No_Child_Activity:"1", name:"287623: RBIS CEI DSS ", description:"This will provide functionality enabling Center Views to access RBIS content through the Decision Sharing Services web service layer provided in MARCS instead of relying on direct database access.", Actual_start_delay:"14 days", Id:"12533", status:"Completed - Closed", Planned_Duration:"90 days"}}, {_id:2814, properties:{planned_Costs:"0.094", Actual_duration:"178 days", output_type:"Usable Functionality", Start_Date_Planned:"2012-03-12", No_Child_Activity:"1", name:"287623: RBIS CEI CV Enhancements", description:"This task provides for implementation of prioritized change requests for the Center Views application after SRA completes the transition to the RBIS team.", Actual_start_delay:"-98 days", Id:"12534", status:"Completed - Closed", Planned_Duration:"80 days"}}, {_id:2815, properties:{planned_Costs:"0.111", Actual_duration:"212 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-11-01", No_Child_Activity:"1", name:"287623: RBIS CEI MARCS 1.0 Integration", description:"This task covers MARCS 1.0 Integration activities, such as Informatica work, that extends beyond making the data available within RBIS itself.", Actual_start_delay:"0 days", Id:"12535", status:"Completed - Closed", Planned_Duration:"150 days"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Activity;
UNWIND [{_id:2816, properties:{planned_Costs:"0.068", Actual_duration:"108 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-07-18", No_Child_Activity:"1", name:"287707: RBIS DWDMU PREDICT Data Mart", description:"This will build a data mart for MARCS PREDICT. PREDICT data is not currently included within ORADSS. This will make running reports and performing analysis that correlates PREDICT screening and risk scores with actual results in MARCS Entry Review, MARCS Operational and Administrative System for Import Support (OASIS) and MARCS Field Accomplishments and Compliance Tracking System (FACTS). This is for requirements and design.", Actual_start_delay:"-3 days", Id:"12536", status:"Completed - Closed", Planned_Duration:"42 days"}}, {_id:2817, properties:{planned_Costs:"0.146", Actual_duration:"136 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-08-17", No_Child_Activity:"1", name:"287708: RBIS FMLS Enhancements Registration Integration Requirements and Design ", description:"Integrate FDA registration systems with FMLS.  Registration systems will likely include eLIST, Shell Egg and Tobacco registration.  eLIST is an FDA Center system for registration and listing. Regulated firms must register with FDA on a periodic basis. In addition, these firms must provide a listing of regulated products produced by the firm. This information is used to produce Firm Establishment Identifiers (FEI) that are used throughout the ORA regulatory work flows. The goal of this is to provide an automated integration point for pushing this information to FMLS. This focuses on requirements and design.", Actual_start_delay:"0 days", Id:"12538", status:"Completed - Closed", Planned_Duration:"136 days"}}, {_id:2818, properties:{planned_Costs:"0.127", output_type:"Usable Functionality", Start_Date_Planned:"2012-01-01", No_Child_Activity:"1", name:"287708: RBIS FMLS Enhancements Registration Integration Development, Test, and Implementation ", description:"Integrate FDA registration systems with FMLS.  Registration systems will likely include eLIST, Shell Egg and Tobacco registration.  eLIST is an FDA Center system for registration and listing. Regulated firms must register with FDA on a periodic basis. In addition, these firms must provide a listing of regulated products produced by the firm. This information is used to produce Firm Establishment Identifiers (FEI) that are used throughout the ORA regulatory work flows. The goal of this is to provide an automated integration point for pushing this information to FMLS. This focuses on development, test, and implementation.", Actual_start_delay:"0 days", Id:"12539", status:"In-progress", Planned_Duration:"150 days"}}, {_id:2819, properties:{planned_Costs:"0.019", Actual_duration:"105 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-08-17", No_Child_Activity:"1", name:"287708: RBIS FMLS Enhancements D&B Real Time Integration ", description:"Integrate FMLS with a to-be-defined Dunn and Bradstreet web service to perform real-time firm looking, instead of waiting for a monthly firm refresh from D&B to RBIS.", Actual_start_delay:"0 days", Id:"12540", status:"Completed - Closed", Planned_Duration:"105 days"}}, {_id:2820, properties:{planned_Costs:"0.015", Actual_duration:"75 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-08-17", No_Child_Activity:"1", name:"287708: RBIS FMLS Enhancements Center Views-MARCS 0.5 Requirements ", description:"Identify requirement gaps between Center Views and MARCS 0.5 release.", Actual_start_delay:"0 days", Id:"12541", status:"Completed - Closed", Planned_Duration:"75 days"}}, {_id:2821, properties:{planned_Costs:"0.009", Actual_duration:"75 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-08-15", No_Child_Activity:"1", name:"287708: RBIS FMLS Enhancements Mapping Capability Requirements ", description:"Identify a new geospatial mapping capability to integrate into ORADSS.", Actual_start_delay:"2 days", Id:"12542", status:"Completed - Closed", Planned_Duration:"77 days"}}, {_id:2822, properties:{planned_Costs:"0.393", output_type:"Usable Functionality", Start_Date_Planned:"2011-09-12", No_Child_Activity:"1", name:"287709: RBIS RDS Deski to Webi", description:"This task migrates a number of currently existing reports from the desktop-based Business Objects application to the web-based version, making these reports more available and easier to maintain and modify.", Actual_start_delay:"0 days", Id:"12543", status:"In-progress", Planned_Duration:"181 days"}}, {_id:2823, properties:{planned_Costs:"0.211", Actual_duration:"181 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-09-12", No_Child_Activity:"1", name:"287709: RBIS RDS Monthly ORADSS Release FY12H1", description:"This task implements report enhancements to existing data marts based on prioritized change requests during FY12H1.", Actual_start_delay:"0 days", Id:"12545", status:"Completed - Closed", Planned_Duration:"181 days"}}, {_id:2824, properties:{planned_Costs:"0.185", output_type:"Usable Functionality", Start_Date_Planned:"2012-03-12", No_Child_Activity:"1", name:"287709: RBIS RDS Monthly ORADSS Release FY12H2", description:"This task implements report enhancements to existing data marts based on prioritized change requests during FY12H2.", Actual_start_delay:"0 days", Id:"12546", status:"In-progress", Planned_Duration:"183 days"}}, {_id:2825, properties:{planned_Costs:"0.031", Actual_duration:"110 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-09-12", No_Child_Activity:"1", name:"287709: RBIS RDS DPEM Enhancements", description:"Enhance Table reports based on DPEM requirements.", Actual_start_delay:"0 days", Id:"12547", status:"Completed - Closed", Planned_Duration:"141 days"}}, {_id:2826, properties:{Actual_duration:"74 days", planned_Costs:"0.12", output_type:"Usable Functionality", Start_Date_Planned:"2011-09-12", No_Child_Activity:"1", name:"287709: RBIS RDS FY12H1", description:"This is the first six months of this activity and includes the following. The Online Reporting Analysis and Decision Support System (ORADSS) contains well over a thousand reports. This will undertake a review of these reports to see what can be consolidated. In addition, it will provide a number of new reports to users. The types and number of reports is continually changing as the needs of users changes. ORADSS provides historical information and reporting capabilities to Mission Accomplishments and Regulatory Compliance Services (MARCS).  Essentially, this makes every user of MARCS a user of ORADSS. As MARCS continues to build towards a unified data structure, this will require changes in ORADSS in order to provide historical information and reporting capabilities. These changes in MARCS will result in a number of changes to reports on the ORADSS side. In addition, ORADSS will also provide historical information and reporting capabilities for the Automated Laboratory Management (ALM) Laboratory Management Information System (LIMS). LIMS is planning to produce pilots in FY12. This will also lay the groundwork for providing reports for LIMS users.  During the first six months, the focus will be on undertaking a review of existing reports and evaluating usage statistics.", Actual_start_delay:"111 days", Id:"12549", status:"Completed - Closed", Planned_Duration:"181 days"}}, {_id:2827, properties:{planned_Costs:"1.145", output_type:"Usable Functionality", Start_Date_Planned:"2012-03-12", No_Child_Activity:"1", name:"287709: RBIS RDS FY12H2", description:"This is the second six months of this project and includes the following. The Online Reporting Analysis and Decision Support System (ORADSS) contains well over a thousand reports. This will undertake a review of these reports to see what can be consolidated. In addition, it will provide a number of new reports to users. The types and number of reports is continually changing as the needs of users changes. ORADSS provides historical information and reporting capabilities to Mission Accomplishments and Regulatory Compliance Services (MARCS).  Essentially, this makes every user of MARCS a user of ORADSS. As MARCS continues to build towards a unified data structure, this will require changes in ORADSS in order to provide historical information and reporting capabilities. These changes in MARCS will result in a number of changes to reports on the ORADSS side. In addition, ORADSS will also provide historical information and reporting capabilities for the Automated Laboratory Management (ALM) Laboratory Management Information System (LIMS). LIMS is planning to produce pilots in FY12. This will also lay the groundwork for providing reports for LIMS users.  During the second six months, the focus will be on consolidating existing reports and implementing new reports and enhancements. ", Actual_start_delay:"0 days", Id:"12550", status:"In-progress", Planned_Duration:"183 days"}}, {_id:2828, properties:{planned_Costs:"0.029", Actual_duration:"110 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-09-12", No_Child_Activity:"1", name:"287710: RBIS Data Evaluation Vendor Selection ", description:"This is the first phase of this project and includes the following. RBIS has grown organically over time. With the recently awarded contract that places RBIS under one contractor, the changes in Mission Accomplishments and Regulatory Compliance Services (MARCS), and the expected addition of Automated Laboratory Management (ALM) Laboratory Information Management System (LIMS), it is time to review the design of RBIS. This will conduct a full review of the technical structure and implementation of the Online Reporting Analysis and Decision Support System (ORADSS) and Firm Master List Services (FMLS). RBIS provides the historical information, reporting capabilities, and firm information that are needed by MARCS and ALM. Changes in MARCS and ALM need to be accommodated in RBIS in order to provide end user functionality. In this activity, the first six months of the project, the Contractor will find a subcontractor specializing in this area in order to provide recommendations to the Government. ", Actual_start_delay:"0 days", Id:"12551", status:"Completed - Closed", Planned_Duration:"110 days"}}, {_id:2829, properties:{planned_Costs:"0.246", Actual_duration:"120 days", output_type:"Usable Functionality", Start_Date_Planned:"2012-01-01", No_Child_Activity:"1", name:"287710: RBIS Data Evaluation and Recommendations", description:"This is the second phase of this project and includes the following. The contractor will evaluate data in FMLS and ORADSS, looking particularly at Extract, Transform, and Load (ETL) strategy and provide recommendations to the Government as to how to best restructure RBIS to handle expected future growth. This will also result in a road map to align RBIS future development with MARCS and ALM.", Actual_start_delay:"0 days", Id:"12552", status:"Completed - Closed", Planned_Duration:"120 days"}}, {_id:2292, properties:{Actual_duration:"100 days", planned_Costs:"0.212", output_type:"Key Deliverable", Start_Date_Planned:"2011-05-27", No_Child_Activity:"1", name:"286212: EM Final Design", description:"This produced a final design for Entry Query functionality within EM.", Actual_start_delay:"54 days", Id:"9276", status:"Completed - Closed", Planned_Duration:"154 days"}}, {_id:2293, properties:{planned_Costs:"0.538", output_type:"Usable Functionality", Start_Date_Planned:"2011-06-14", No_Child_Activity:"1", name:"286212: EM Development", description:"This is producing some of the Entry Query functionality.  The rest will be produced later once more functionality from OASIS and Entry Review has been migrated to EM.  This is due to technical dependences.", Actual_start_delay:"49 days", Id:"9277", status:"In-progress", Planned_Duration:"143 days"}}, {_id:2294, properties:{planned_Costs:"0.251", output_type:"Usable Functionality", Start_Date_Planned:"2011-06-27", No_Child_Activity:"1", name:"286212: EM Test", description:"This will conduct unit and regression testing on some of the Entry Query functionality.", Actual_start_delay:"77 days", Id:"9278", status:"In-progress", Planned_Duration:"144 days"}}, {_id:2295, properties:{planned_Costs:"0.255", Actual_duration:"183 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-03-01", No_Child_Activity:"1", name:"286212: EM Field Exam and Sample Collection Requirements", description:"This is for gathering requirements for the field exam and sample collection functionality that exists in OASIS that will be migrated to FWM and WAAM.", Actual_start_delay:"0 days", Id:"9279", status:"Completed - Closed", Planned_Duration:"183 days"}}, {_id:2296, properties:{planned_Costs:"0.19", Actual_duration:"105 days", output_type:"Usable Functionality", Start_Date_Planned:"2010-09-29", No_Child_Activity:"1", name:"286215: PREDICT ETL for Control Agents and Database Connections", description:"This is focused on improving the ETL that is currently in place.  This will provide faster and more reliable data transfer.", Actual_start_delay:"0 days", Id:"9282", status:"Completed - Closed", Planned_Duration:"100 days"}}, {_id:2297, properties:{planned_Costs:"0.075", Actual_duration:"158 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-02-14", No_Child_Activity:"1", name:"286215: PREDICT ETL for Test and Documentation", description:"This is focused on improving the ETL that is currently in place.  This will provide faster and more reliable data transfer.", Actual_start_delay:"0 days", Id:"9283", status:"Completed - Closed", Planned_Duration:"158 days"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Activity;
UNWIND [{_id:2298, properties:{planned_Costs:"0.175", Actual_duration:"157 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-01-10", No_Child_Activity:"1", name:"286215: PREDICT DnB Requirements and Design", description:"FDA is developing the capability to access and leverage the extensive world wide database that DnB has for firm information. This will help to standardize how firms are identified and tracked within FDA. This is especially useful when dealing foreign firms where names need to be transliterated from non Latin alphabets. This transliteration has historically introduced errors in firm information. Improved quality in firm information will help make PREDICT and import screening for 801(a) more effective. This will help FDA process the 20,000,000+ products that are imported each year.", Actual_start_delay:"0 days", Id:"9285", status:"Completed - Closed", Planned_Duration:"144 days"}}, {_id:2299, properties:{planned_Costs:"0.045", Actual_duration:"146 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-03-25", No_Child_Activity:"1", name:"286215: PREDICT DnB Development and Test", description:"FDA is developing the capability to access and leverage the extensive world wide database that DnB has for firm information. This will help to standardize how firms are identified and tracked within FDA. This is especially useful when dealing foreign firms where names need to be transliterated from non Latin alphabets. This transliteration has historically introduced errors in firm information. Improved quality in firm information will help make PREDICT and import screening for 801(a) more effective. This will help FDA process the 20,000,000+ products that are imported each year.", Actual_start_delay:"0 days", Id:"9286", status:"Completed - Closed", Planned_Duration:"146 days"}}, {_id:2300, properties:{planned_Costs:"0.192", Actual_duration:"153 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-04-28", No_Child_Activity:"1", name:"286215: PREDICT Rules Studio", description:"This includes requirements, design, and some development for Rules Studio. Currently, when rules for PREDICT need to be modified, added, or removed, technical contract personnel need to make these modifications. This is to produce functionality that will allow non technical FTEs to make these modifications, additions, or deletions.", Actual_start_delay:"0 days", Id:"9287", status:"Completed - Closed", Planned_Duration:"153 days"}}, {_id:2301, properties:{planned_Costs:"0.253", Actual_duration:"140 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-09-27", No_Child_Activity:"1", name:"286216: DGS Requirements for DGS", description:"This gathered requirements for DGS functionality for MARCS.", Actual_start_delay:"0 days", Id:"9290", status:"Completed - Closed", Planned_Duration:"140 days"}}, {_id:2302, properties:{planned_Costs:"0.06", Actual_duration:"60 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-06-06", No_Child_Activity:"1", name:"286216: DGS Requirements for Integration with QMiS", description:"This gathered requirements for integration with Automated Laboratory Management (ALM) Quality Management Information System (QMiS)", Actual_start_delay:"0 days", Id:"9291", status:"Completed - Closed", Planned_Duration:"60 days"}}, {_id:2303, properties:{planned_Costs:"0.135", Actual_duration:"139 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-10-20", No_Child_Activity:"1", name:"286216: DGS Decision Analysis", description:"An industry survey and analysis of COTS products was conducted.  This resulted in a recommended product to implement the functionality envisioned for DGS.", Actual_start_delay:"0 days", Id:"9292", status:"Completed - Closed", Planned_Duration:"139 days"}}, {_id:2304, properties:{planned_Costs:"0.288", Actual_duration:"87 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-01-31", No_Child_Activity:"1", name:"286216: DGS Preliminary Design", description:"This produced a preliminary design for DGS.", Actual_start_delay:"0 days", Id:"9294", status:"Completed - Closed", Planned_Duration:"87 days"}}, {_id:2305, properties:{Actual_duration:"110 days", planned_Costs:"0.123", output_type:"Key Deliverable", Start_Date_Planned:"2011-04-29", No_Child_Activity:"1", name:"286216: DGS Final Design", description:"This produced a final design for DGS.", Actual_start_delay:"0 days", Id:"9295", status:"Completed - Closed", Planned_Duration:"110 days"}}, {_id:2306, properties:{Actual_duration:"189 days", planned_Costs:"0.357", output_type:"Usable Functionality", Start_Date_Planned:"2011-04-22", No_Child_Activity:"1", name:"286216: DGS Development", description:"This is producing code that realizes the DGS functionality using a COTS and some custom code.", Actual_start_delay:"0 days", Id:"9296", status:"Completed - Closed", Planned_Duration:"129 days"}}, {_id:2307, properties:{Actual_duration:"168 days", planned_Costs:"0.078", output_type:"Usable Functionality", Start_Date_Planned:"2011-05-25", No_Child_Activity:"1", name:"286216: DGS Test ", description:"This is for conducting unit and regression testing on DGS functionality.", Actual_start_delay:"0 days", Id:"9297", status:"Completed - Closed", Planned_Duration:"124 days"}}, {_id:2308, properties:{planned_Costs:"0.081", Actual_duration:"49 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-09-27", No_Child_Activity:"1", name:"286217: WAAM 2 RAC Requirements Validation", description:"RAC requirements were gathered in WAAM, but these requirements needed to be verified in relation to the use of the legacy Recall Enterprise System (RES) for supporting the work of ORA Field users.", Actual_start_delay:"0 days", Id:"9300", status:"Completed - Closed", Planned_Duration:"49 days"}}, {_id:2309, properties:{planned_Costs:"0.101", Actual_duration:"149 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-11-02", No_Child_Activity:"1", name:"286217: WAAM 2 RAC Design for User Interface and Logical", description:"This produced a design for WAAM that supports RAC functionality and also includes considerations for the future work management in relation to other types of Field activities for user interfaces and logical software and data considerations.", Actual_start_delay:"0 days", Id:"9302", status:"Completed - Closed", Planned_Duration:"149 days"}}, {_id:2310, properties:{planned_Costs:"0.048", Actual_duration:"68 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-03-04", No_Child_Activity:"1", name:"286217: WAAM 2 RAC Design for Services Specifications", description:"This produced a design for WAAM that supports RAC functionality and also includes considerations for the future work management in relation to other types of Field activities.  This took into account functionality that will be needed from the various MARCS services.", Actual_start_delay:"0 days", Id:"9303", status:"Completed - Closed", Planned_Duration:"68 days"}}, {_id:2311, properties:{planned_Costs:"0.062", Actual_duration:"28 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-05-11", No_Child_Activity:"1", name:"286217: WAAM 2 RAC Design for Physical Data, Security, Interface, and Data Synchronization", description:"This produced a design for WAAM that supports RAC functionality and also includes considerations for the future work management in relation to other types of Field activities. This took into account the physical data design, security ramifications, interface specifications, and considerations for migrating data.", Actual_start_delay:"0 days", Id:"9304", status:"Completed - Closed", Planned_Duration:"28 days"}}, {_id:2312, properties:{planned_Costs:"0.208", Actual_duration:"247 days", output_type:"Usable Functionality", Start_Date_Planned:"2010-11-02", No_Child_Activity:"1", name:"286217: WAAM 2 RAC Development and Support for FWM and eSAF", description:"This produced code to realize RAC functionality that will support work flows realized in Field Work Manager (FWM) and the legacy Electronic State Access to FACTS (eSAF)", Actual_start_delay:"0 days", Id:"9306", status:"Completed - Closed", Planned_Duration:"162 days"}}, {_id:2313, properties:{planned_Costs:"0.127", Actual_duration:"179 days", output_type:"Usable Functionality", Start_Date_Planned:"2011-03-31", No_Child_Activity:"1", name:"286217: WAAM 2 RAC Development and Support for RES", description:"This produced code to realize RAC functionality that will support work flows realized in the legacy Recall Enterprise System (RES).", Actual_start_delay:"0 days", Id:"9307", status:"Completed - Closed", Planned_Duration:"113 days"}}, {_id:2314, properties:{Actual_duration:"229 days", planned_Costs:"0.145", output_type:"Usable Functionality", Start_Date_Planned:"2011-02-09", No_Child_Activity:"1", name:"286217: WAAM 2 RAC Test", description:"This is for conducting unit and regression testing for RAC functionality. ", Actual_start_delay:"0 days", Id:"9308", status:"Completed - Closed", Planned_Duration:"172 days"}}, {_id:2315, properties:{planned_Costs:"0.165", Actual_duration:"147 days", output_type:"Key Deliverable", Start_Date_Planned:"2010-10-13", No_Child_Activity:"1", name:"286217: WAAM 2 Inspections Requirements", description:"This produced requirements documentation.  One of the goals is to increase the use of fielded data to eliminate redundant data entry and improve searching and reporting capabilities.", Actual_start_delay:"0 days", Id:"9310", status:"Completed - Closed", Planned_Duration:"147 days"}}, {_id:2316, properties:{planned_Costs:"0.102", Actual_duration:"179 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-02-18", No_Child_Activity:"1", name:"286217: WAAM 2 Inspections Design for User Interface and Logical", description:"This produced a design for WAAM that supports Inspections functionality and also includes considerations for the future work management in relation to other types of Field activities for user interfaces and logical software and data considerations.", Actual_start_delay:"0 days", Id:"9312", status:"Completed - Closed", Planned_Duration:"179 days"}}, {_id:2317, properties:{planned_Costs:"0.033", Actual_duration:"161 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-04-18", No_Child_Activity:"1", name:"286217: WAAM 2 Inspections Design for Services Specifications", description:"This produced a design for WAAM that supports Inspections functionality and also includes considerations for the future work management in relation to other types of Field activities. This took into account functionality that will be needed from the various MARCS services.", Actual_start_delay:"0 days", Id:"9313", status:"Completed - Closed", Planned_Duration:"141 days"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Activity;
UNWIND [{_id:2318, properties:{planned_Costs:"0.069", Actual_duration:"33 days", output_type:"Key Deliverable", Start_Date_Planned:"2011-08-24", No_Child_Activity:"1", name:"286217: WAAM 2 Inspections Design for Physical Data, Security, Interfaces, and Data Synchronization", description:"This produced a design for WAAM that supports Inspections functionality and also includes considerations for the future work management in relation to other types of Field activities. This took into account the physical data design, security ramifications, interface specifications, and considerations for migrating data.", Actual_start_delay:"0 days", Id:"9314", status:"Completed - Closed", Planned_Duration:"20 days"}}, {_id:2319, properties:{planned_Costs:"0.167", Actual_duration:"182 days", output_type:"Usable Functionality", Start_Date_Planned:"2010-11-02", No_Child_Activity:"1", name:"286217: WAAM 2 Inspections Development Iterations 1 and 2", description:"MARCS uses an iterative approach to development. For Inspections, four iterations were used to build out functionality, verify that it is correct, and then expand on that functionality. This is the first two of those iterations.", Actual_start_delay:"0 days", Id:"9316", status:"Completed - Closed", Planned_Duration:"153 days"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Activity;
UNWIND [{_id:53, properties:{Investment_type:"Major", Changes_to_Baseline:"6.0", Identifier:"009-000005318", name:"FDA ORA Automated Laboratory Management", Last_Baseline:"2012-02-23", Summary:"ALM encompasses QMiS, eLEXNET, and LIMS. It provides for ORA wide program quality, sample analysis information sharing across ORA and with external partners, and increased throughput via laboratory automation. ALM aligns directly with Strategic Goal 2, Objective C of the HHS strategic plan: Advance Scientific Knowledge and Innovation; Invest in the regulatory sciences to improve food/medical product safety; and to meet FDA Strategic Goal 4: Improve the Quality/Safety of Manufactured Products/Supply Chain. QMiS supports program quality across FDA. This includes the review, continuous improvement, and auditing of work product from the regulatory work flows of ORA. QMiS also directly supports the accreditation of the 16 ORA labs. eLEXNET allows the exchange of lab analysis data between over 100 public health labs at the Federal, state, and local levels including an interface with DHS' National Bio-surveillance Integration System. It is the system for the Food Emergency Response Network and is thus an integral piece in protecting against bioterrorism. LIMS is an envisioned ORA wide COTS solution for automating laboratory work that is currently done manually. This will significantly increase throughput and is expected to at least double the current capacity of ORA laboratories. This is a key component to supporting the FDA Science Strategic Plan. Primary beneficiaries of ALM are quality managers, organizations participating in eLEXNET, and the personnel in the ORA labs. This extends to the public as ALM enables protecting and promoting the public health.ALM will result in reduced response times in health emergencies due to increased laboratory throughput and leveraging external partners and in increased quality for repeatability of results and directly supports the ORA mission of protecting and promoting the public health.ALM has significant dependencies on both MARCS and RBIS for work flow and reporting.ALM forms a comprehensive solution for sample analysis that incorporates quality, internal laboratories, and external partners. It is a proven success in leveraging external partners through cooperative agreements and a useful and reliable IT system.ALM has a planned end date of 9/30/2014. FDA is exploring the possibility of combining ALM, MARCS, and RBIS into one investment since together they support ORA regulatory work flows. This analysis will be completed in FY12. ALM is now being reported as ending pending the results of this analysis.", Performance_Gap:"ORA is a geographically dispersed organization with many processes having grown up organically over decades. QMiS addresses these differences by using a systematic approach towards quality and standardization. This involves a cultural change within the organization and will take time to be accepted.  eLEXNET provides a proven method of interfacing with external partners, particularly DHS. In the case of a bioterrorism emergency, cooperation between Federal agencies and private partners will be paramount. eLEXNET provides a robust, fully redundant, and reliable system to do this.  ORA has seen a steep growth in the demand for sample analysis while many essential processes are not yet automated. All of the 16 ORA laboratories use manual paper based processes.  LIMS is being implemented to change this to automate the laboratories from top to bottom. This will increase accuracy, throughput, and staff efficiency. The demand for sample analysis work from the ORA laboratories is only expected to grow.  Without an automated system, it will be virtually impossible for laboratories using manual processes to meet the needs of the organization.  eLEXNET was the first system at FDA to take a SOA approach coupled with a BPMS. Both LIMS and MARCS are being designed to extend this approach. This provides ORA with an architecture that supports integration and information interchange from the ground up. SOA provides the technical backbone for this approach. The BPMS standardizes the approach to defining, describing, mapping, and implementing work flows and enables Federal business personnel to build and modify work flows as graphical and English language tools do not require a technical background. This produces a more accurate and useful final product work flow and cuts modification time.  ALM fills the current performance gap by providing improved quality, external partner communications, and laboratory automation. This improves repeatability, communication, addresses chain of custody legal needs, increases laboratory throughput, and reduces response time to public health emergencies.  Not fully funding ALM will delay these benefits and could result in ORA laboratories not being able to process samples as needed by the organization.", Business_Case:"299", Enhancement_spend_$m:12.555, Evaluation_by_CIO:"4"}}, {_id:57, properties:{Investment_type:"Major", Changes_to_Baseline:"5.0", Identifier:"009-000005317", name:"FDA ORA Mission Accomplishments and Regulatory Compliance Services", Last_Baseline:"2012-02-22", Summary:"The MARCS program is the primary IT mechanism for realizing ORA program goals that supports all FDA Field activities (except laboratories) including domestics, imports, and enforcement.  MARCS directly supports the surveillance and promotes the safety of all FDA regulated products except tobacco. It also directly supports the programs of the FDA Offices OF, OMPT, and OGROP, and FDA Centers CBER, CDER, CDRH, CFSAN, and CVM. MARCS is a Business Process Improvement (BPI) effort built from the ground up with integration in mind and forms an Enterprise Resource Planning system that spans all of the electronic work flows of ORA except for processes specific to ORA laboratories. It aligns directly with Strategic Goal 2, Objective C of the HHS strategic plan: Advance Scientific Knowledge and Innovation; Invest in the regulatory sciences to improve food and medical product safety and enables FDA Centers to meet FDA Strategic Goal 4: Improve the Quality and Safety of Manufactured Products and the Supply Chain.  FDA uses MARCS to: plan FDA field activities and assign staff to inspections, investigations, recalls, and other compliance activities; track and control samples and the results of laboratory analysis; collect and maintain information from field activities; collect performance data, particularly that related to FDAAA; send Prior Notice for food imports to Customs and accept import product information from Customs for screening; screen some 20 million import lines a year based on calculated risk (PREDICT); collect information about the facilities FDA regulates and those in the import supply chain for risk-based targeting; provide FDA Centers with information on inspections, compliance actions, recalls, laboratory analysis and facilities.   Primary beneficiaries of MARCS are the FDA personnel conducting surveillance and regulatory activities.  This extends to the public as MARCS enables these surveillance and regulatory activities.  MARCS is closely coupled with two other major ORA investments, ALM and RBIS.  ALM provides functionality for ORA laboratories and quality.  RBIS provides reporting and information on some 5 million foreign and domestic firms.  Together, these three investments provide for all of the regulatory workflows of ORA. MARCS also interacts with FURLS, eLIST, and a number of smaller systems at FDA.", Performance_Gap:"Because much of the data and work conducted by the FDA Centers converge within ORA, ORA faces a particular set of performance gaps - e.g., the ability to integrate data in various formats with divergent data definitions; work flows that begin in a number of different states and progress through various organizations; functionalities that are divided into different systems; and the fragility of point-to-point integration schemes that have been built up over time.MARCS is a complete departure from the past which was characterized by organic growth in response to particular needs without an ability to consider the holistic Agency needs. MARCS is being built from the ground with SOA using an ESB coupled with a BPMS and technologies to support offline and Remote Access Device (RAD) usage. SOA allows MARCS to build and reuse functionality that in the past has been duplicated multiple times with different implementations. Now, functionalities can be shared both across MARCS and with other related programs including ALM and RBIS. The ESB solves the problem of fragile point-to-point integration resulting in more robust and higher performance systems. The BPMS standardizes the approach to defining, describing, mapping, and implementing work flows. This also brings the building and modifying of work flows closer to Federal business personnel as the graphical and English language tools do not require a technical background. This produces a much more accurate and useful work flow in the final product and shortens times to modify work flows. MARCS is producing shared services in accordance with point 6 of the 25 point IT reform plan.Much of the work performed by ORA personnel is done in remote areas without network connectivity. This has never been comprehensively addressed by ORA.  MARCS is designed to inherently support off-line/on-line operations through RADs - handheld devices that will improve the efficiency of field staff in completing work not done in an FDA office and when connectivity may be intermittent. MARCS is doing a holistic RADs implementation based on field integration and infrastructure requirements.If MARCS is not fully funded, then the movement towards this future structure will be delayed and work will need to continue to support poorly performing systems that keep breaking down as more demand and integration is placed onto them. Continuing to operate with these legacy systems will undermine ORAs ability to perform its mission.", Business_Case:"310", Enhancement_spend_$m:20.181, Evaluation_by_CIO:"4"}}, {_id:67, properties:{Investment_type:"Major", Changes_to_Baseline:"7.0", Identifier:"009-000005316", name:"FDA ORA Regulatory Business Information Services", Last_Baseline:"2012-02-23", Summary:"RBIS provides data availability and data quality for all of the ORA regulatory activities. RBIS supports all FDA Field activities including domestics, imports, and enforcement.  It aligns directly with Strategic Goal 2, Objective C of the HHS strategic plan: Advance Scientific Knowledge and Innovation; Invest in the regulatory sciences to improve food and medical product safety and enables FDA Centers to meet FDA Strategic Goal 4: Improve the Quality and Safety of Manufactured Products and the Supply Chain. RBIS includes  1 Online Reporting, Analysis, and Decision Support System (ORADSS): a centralized data warehouse and reporting structure focused primarily on data availability for historical information.  2 Firms Master List Services (FMLS): a master, authoritative source focused primarily on data quality for approximately 5 million foreign and domestic firms which produce products regulated by the FDA.The reporting and firm information are used throughout the ORA work flows to support import screening, inspections, investigations, field exams, sample collections, sample analysis, recalls, case management, other compliance activities, and work planning.  This information is used both to support every-day operations and to analyze and plan for the future.Primary beneficiaries of RBIS are the FDA personnel who access these integrated systems for analysis and decision-making that is used to protect public health and safety and communicate to the public. FDA management also benefits from the information RBIS provides to help in planning and identifying risks. Over 6,000 users throughout FDA use RBIS.RBIS is closely coupled with two other major ORA investments, ALM and MARCS.  ALM provides functionality for ORA laboratories and quality.  MARCS is the primary IT system for all regulatory activities outside of the labs and quality. Together, these three investments provide for all of the regulatory workflows of ORA.RBIS also interacts with FURLS, eLIST, and a number of smaller systems at FDA. In addition, RBIS interacts with Dunn and Bradstreet (D&B) information so that FDA can access the large data set of firm information held by D&B to improve domestic and foreign firm data quality.", Performance_Gap:"RBIS fills the current performance gap by providing for 1 Standardized access to reports and other historical information. ORADSS contains a centralized data warehouse that includes subsets of information pertaining to particular activities. This is made available to non-technical users via COTS solutions. Users can access canned reports or create ad hoc reports without needing specialized knowledge of the underlying data structures. This allows the data to be made available to the largest possible user audience. More advanced users can query the data warehouse directly to support data mining and analysis.2 Standardized firm information that allows for reliable firm identification.  FMLS contains information on some 5 million firms. FDA must maintain information on companies around the world that manufacture, produce, or process regulated items. Within this universe of firms, there are always new companies, companies going out of business, and companies that are merging. FDA receives approximately 10,000 new or unrecognized firms per week. Sometimes these are not new firms, but firms that FDA already has in its database that need to be matched. This is especially true of foreign firms in nations that do not utilize a Latin alphabet. FMLS is continually used to match, clean up, delete, merge, and unmerge firm names in order to provide FDA with an accurate list of the firms that are producing regulated items. This is accomplished through using a set of rules to manage firms, fuzzy logic, and manual analysis. This emphasis on the data quality of the firms tracked by FDA supports all of the regulatory workflows of ORA.If RBIS is not fully funded then data availability, data quality, or both will suffer. The functionality provided by RBIS is closely tied to that provided by ALM or MARCS.  Information generated in ALM or MARCS will find its way into RBIS.  This is actively used by FDA personnel in order to support the every day operations of ORA and the Centers.", Business_Case:"318", Enhancement_spend_$m:6.211, Evaluation_by_CIO:"4"}}, {_id:268, properties:{Investment_type:"Major", Changes_to_Baseline:"4.0", Identifier:"009-000005315", Last_Baseline:"2012-03-09", Performance_Gap:"FAERS directly supports Federal mandate to collect adverse event reporting as defined in 42 CFR 310.305, 314.80, 314.98 and 600.80. This effort supports the goal of e-Government by creating consolidated and efficient electronic access to adverse event reporting information. This, along with the system's capabilities of accepting adverse event reports, facilitates real-time transfer of information, improves the FDA's responsiveness to the American public, consumers, industry, and healthcare providers. FAERS provides enhanced analyses to support safety evaluators and other Agency medical officers with appropriate tools to conduct analytic processes and reporting. This will be accomplished through a robust adverse event report system enabling daily decision-making, on-demand adverse event reporting by safety evaluators and medical officers. FAERS will provide consistent and prompt adverse event reports to the user community, Congress, FOIA, health care industry, manufacturing organizations, as well as a host of other external stakeholders. FAERS will subsume a myriad of aging legacy and disparate systems, ultimately providing enhanced capabilities for adverse event reporting.  This System provides a technology upgrade in both hardware and software to meet the growing demand of functionality and performance from business. The Enterprise Architecture of FAERS provides the optimal platform for continued program expansion, such as the expanded automation of data mining and ongoing safety issues to support Federal mandates. This investment facilitates a robust pharmacovigilance and analytic process for adverse event reporting and tracking. Disparate systems will be subsumed by FAERS. As a result of FAERS, business processes will be streamlined, creating efficiencies in work-flow processes for its user communities.  This project seeks to bridge multiple gaps within the CDER and CBER adverse event reporting domain. This project seeks to create a higher level of adverse event consistency, as well as data integrity. If this project is not fully funded, adverse event reporting will be compromised and user communities will not be able to efficiently and effectively analyze, report and track adverse event reporting.", Summary:"The Food and Drug Administration (FDA) is responsible for monitoring the safety of FDA regulated products in order to protect and promote public health. Analysis of adverse event and safety report information is critical to achieving this goal. The FDA needs to modernize its aging systems, improve its analytic capabilities, and make it easier for the public to submit adverse event and safety reports to the FDA.  FAERS (FDA Adverse Event Reporting System) is a Web-based Oracle database application and Business Intelligence data warehouse that will replace legacy AERS (Adverse Event Reporting System).  FAERS will contain post-market adverse event reports associated with drugs and biologic products.  These adverse event reports are submitted to FDA by manufacturers, healthcare professionals, and consumers.  FDA will use FAERS for regulatory compliance, and to monitor for adverse events and medication errors that might occur with approved products.  FAERS is an Oracle operational database. Operational databases can store large amounts of data, and allow users to quickly enter, revise, and retrieve information from one system.  When FAERS replaces AERS, FAERS will contain more than six million adverse event reports, and the dataset will continually change as new reports or follow up information is entered into the database.", Enhancement_spend_$m:2.961, Evaluation_by_CIO:"3"}}, {_id:269, properties:{Investment_type:"Major", Changes_to_Baseline:"7.0", Identifier:"009-000005323", Last_Baseline:"2012-02-24", Performance_Gap:"FDA's regulatory mission could not be met without the fees mandated by User Fee legislation and collected, managed and reported through UFFRS. The fees processed are a significant portion of FDA's budget. Many FDA missions would suffer if user fees are tracked from collection to work performed. Three quarters of the annual investment budget is for O&M activities that support user fee management. They include:- licenses support from the COTS vendors and technical upgrades to the COTS product to maintain our vendor support agreements; - software upgrades to remain compliant with increasing security requirements and FDA's Production environment;  - help desk support; operation of the critical interfaces with UFMS including nightly extract, transfer, and load activities (ETL); - ongoing training, and changes needed to retain compatibility with UFMS. The cost for such support is reflected in the recently awarded contracts for fixed price operational support for the next five years. Although UFFRS meets current requirements, the user fee environment has been and continues to be dynamic. Changes expected in the next three years include: full implementation of the Food Safety Modernization Act; actions on Generic Drugs that will affect User Fees collections; demands for integrating additional data sources to improve the capabilities of BIRS; and a planned Oracle database upgrade. Changes to the FDA budget may require realignment that will trigger additional forecasting and reporting needs since User Fees are a significant source of FDA revenues; UFS, BIRS and Hyperion will require modification. Estimates for these costs are included in the new contracts.The ability to collect and adequately track and report approximately one billion dollars in revenue generated by user fees is critical to FDA and to HHS. Failure to maintain the automated capability to ensure adequate collection and accountability would have a serious negative impact on FDA. Comprehensive requirements for reporting are included in the legislation which FDA must meet to satisfy Congress and industry, as well as the general public. In addition, significant cuts could require partial or total termination of current contracts. The User Fee program is a valued source of revenue for FDA and many of its programs.  Cuts to the UFFMS investment which would make it less able to collect and manage User Fees  would be counter-productive at best.", Summary:"The UFFRS investment supports the Division of User Fees (DUF) within FDA's Office of Financial Management (OFM). DUF is responsible for managing User Fees in compliance with the OMB Circular A-25 other relevant Legislative or Executive actions. Investment business functions include Fee collection, accounting, and reporting of the approximately $3,000,000,000 collected annually in user fees. It also includes automated support for FDA strategic planning, budgeting, and budget execution that depends on the successful collection and distribution of mandated user fees.  UFFMS functions directly enable compliance with the following legislation: Animal Drug User Fee Act (ADUFA); Animal Generic Drug User Fee Act (AGDUFA); Color Certification (CERTS); Exports Certificate (Exports); Medical Device User Fee Act (MDUFMA); Mammography Quality Standards Act (MQSA); Prescription Drug User Fee Act (PDUFA); Family Smoking Prevention and Tobacco Control Act (Tobacco).Contracts that support UFFRS operate, maintain and enhance three systems that collectively support the spending plans for the User Fee program and associated 5 year plans, and prepare the cost reporting needed to ensure statutory triggers are met. Contracts that support UFFRS operate, maintain and enhance three systems that collectively support the spending plans for the User Fee program and associated 5 year plans, and prepare the cost reporting needed to ensure statutory triggers are met.   1) The User Fee System (UFS) processes accounts receivable for user fee invoicing, collections, reconciliation with UFMS and detail reporting. 2) FDA's Hyperion reporting system captures data at a summarized level, rather than at an individual transaction level.  It is used to project the impact of User Fees FDA budgets, obligations, and expenditures. 3) The Business Intelligence Reporting System (BIRS) supports managerial reporting needs including web assess to user fee information.  BIRS uses Oracle Business Intelligence Enterprise Edition Plus (OBIEE) to provide business visibility and insight into the collection and use of User Fee revenues.  UFFRS systems interface with HHS' Unified Financial Management System (UFMS) for both payment related processes, budget management and report generation, and changes to UFMS operations or features must be reflected in the UFFRS systems.", Enhancement_spend_$m:2.296, Evaluation_by_CIO:"4"}}, {_id:270, properties:{Investment_type:"Major", Changes_to_Baseline:"7.0", Identifier:"009-000005345", Last_Baseline:"2012-02-22", Performance_Gap:"ADIMS directly supports the goal of e-Government by creating consolidated and efficient electronic access to the most up-to-date and complete information within the Agency. This, along with the system's capabilities of accepting electronic submissions and facilitating real-time transfer of information, improves the FDA's responsiveness to the American public, consumers, industry, and healthcare providers. Provides enhanced communications and data flow in support of the regulatory review and safety processes. This is accomplished through a unified set of systems that enable access to information and tools used in daily decision-making by drug review and safety evaluation teams. Further consolidates the receipt, tracking, management, and reporting of information about clinical investigation and market submissions for human drugs and therapeutics biologics. Absorbs and better manages the submission and tracking of Establishment Evaluation Requests as part of the ADIMS support of the drug application review process. Now incorporates relevant Substance and Ingredient information. Focused reporting project will provide consistent and prompt reports to the user community, Congress, FOIA, and the health care industry. Reporting is approximately 40% of the end-user experience and this will now be accomplished through a common interface system. Eliminates redundant systems, and consolidates and migrates functionality and maintenance into a smaller set of systems; while at the same time providing legacy tasks with enhanced capabilities. Provides upgrades of technology in both hardware and software to meet the growing demand of functionality and performance from business. Provides the platform for continued program expansion, such as the expanded automation of support tracking processes for drug product and therapeutic biologic product review; as well as drug safety issues. Meets performance goals of PDUFA. It is critical that the ADIMS Investment continues to maintain and enhance existing systems, consolidate functionality, as well as invest in new capabilities to further meet growing business needs and new legislative or regulatory requirements.", Summary:"The Automated Drug Information Management System (ADIMS) is being developed as an integrated, fully electronic information management system for the receipt, validation, evaluation, reporting, and dissemination of drug application, safety and efficacy data. As the core enterprise architecture for FDA's pre-market drug review process, ADIMS aims to integrate or replace all relevant systems. The system will seamlessly unify multiple applications into one application which will include single sign-on access to information and tools used in daily decision-making. The Document Archiving, Reporting, and Regulatory Tracking System (DARRTS) will be the backbone of the system. Over fifty large and small systems will be integrated into ADIMS, including the Corporate Oracle Management Information System (COMIS), the Electronic Document Room (EDR), and the Division File System (DFS).  As the volume of technologically advanced electronic information coming into FDA escalates, the need for a robust information management system becomes more critical. In addition to facilitating the drug review and approval process, this integrated data management system will collect and evaluate electronic clinical data and facilitate the identification of trends and other important drug regulatory review information (e.g., potential product safety issues). Also, the validation and back-up capabilities of ADIMS will facilitate data verification and correction with increased efficiency. Consolidating current stovepipe and stand-alone drug information systems into a cohesive, easily supportable platform will give reviewers the ability to access information from a single interface, thus reducing redundancy. This will improve data quality and performance objectives, as well as reduce time and resources required to keep multiple systems updated. As a result, ADIMS will directly support the e-Government initiative by creating efficient, electronic access to current and complete information within the Agency. ADIMS also supports the HHS strategic goal to improve health care quality, safety, cost and value by allowing real-time transfer of information. In addition to this, the capability to accept electronic submissions will improve the FDA's responsiveness to consumers, industry, and healthcare providers.", Enhancement_spend_$m:10.206, Evaluation_by_CIO:"3"}}, {_id:271, properties:{Investment_type:"Major", Changes_to_Baseline:"3.0", Identifier:"009-000005354", Last_Baseline:"2011-02-28", Performance_Gap:"The ICT21 Initiative designs & builds this purpose driven, data centric environment for the FDA. The Initative increases the Agency's capabilities to: respond to emerging technologies & challenges, strengthen product development & approval, improve manufacturing & product quality, strengthen post-approval surveillance & safety, support electronic prescribing, & improve clinical decision making. Results are achieved by collecting & combining clinical & other important & pertinent data from industry, government agencies & outside entities into integrated databases & networks to expand the scientific computations & computational sciences at the FDA. The FDA continues to widen the use of analytics for large datasets which integrate multiple clinical & diagnostic endpoints, through increased use of clustering & grid computing to improve collaboration among & within entities interacting with the FDA. The new ICT21 bioinformatics platform supports the FDA's growing mission within 2-10 years & the PMA goal-Expanded e-Government - Disaster Management, & the DHHS goal of increasing scientific R&D.", Summary:"Development of new information technologies, driven by accelerating computational processing & substantial growth in data volume, is causing transformation to all aspects of the FDA operations. New types & vastly larger quantities of data to be processed by the FDA, from multiple clinical & diagnostic endpoints from industry submissions & collaborations with other research sources, reuse of existing data within & among the FDA centers & other government agencies (i.e. NIH, CMS, CDC, VA, DoD, etc.), & outside entities including foreign countries, are examples of the complexity & number of information sources the FDA handles today. The number of sources & data elements increases as the need for complex inputs for safety evidence & efficacy information, genomics, metabolic network & clinical trials modeling, data markers type data, integrated data & networks, & food imports expands. The FDA is increasing its use of electronic health records data to acquire pertinent information for its pharmacovigilance efforts causing expanded participation in programs & initiatives to define of the records standards & networks to assure appropriate data are gathered for use in such activities as safety & efficacy, & genomics & data markers. To meet these challenges, the FDA is modernizing its capacity & communication capabilities by creating an agency-wide bioinformatics IT platform. The ICT21 Initiative designs & builds this purpose driven, data centric environment for the FDA. The imitative increases the Agency's capabilities to: respond to emerging technologies & challenges, strengthen product development & approval, improve manufacturing & product quality, strengthen post-approval surveillance & safety, support electronic prescribing, & improve clinical decision making. Results are achieved by collecting & combining clinical & other important & pertinent data from industry, government agencies & outside entities into integrated databases & networks to expand the scientific computations & computational sciences at the FDA. The FDA continues to widen the use of analytics for large datasets which integrate multiple clinical & diagnostic endpoints, through increased use of clustering & grid computing to improve collaboration among & within entities interacting with the FDA. The new ICT21 bioinformatics platform supports the FDA's growing mission within 2-10 years & the PMA goal-Expanded e-Government - Disaster Management, & the DHHS goal of increasing scientific R&D.", Enhancement_spend_$m:9.668, Evaluation_by_CIO:"3"}}, {_id:277, properties:{Investment_type:"Major", Changes_to_Baseline:"2.0", Identifier:"009-000006267", Last_Baseline:"2012-02-24", Performance_Gap:"FDA relies extensively on IT to fulfill its mission and to support related administrative needs. In December 2007, the FDA Science Board reported that FDA's mission was at risk due to an aging and inadequate IT infrastructure. FDA has made significant progress in addressing this weakness through the ICT21 investment. This investment established a state-of-the art consolidated Data Center environment. The OI investment provides FDA with the ability to sustain this progress and continued advancement. This investment provides essential IT infrastructure services critical to ensuring FDA's basic operational capability and is key enabler in FDA's ability to advance its scientific capabilities.  If this investment isn't fully-funded, the consequences would be devastating. Ultimately, the FDA would not be able to fulfill its mission without this investment.", Summary:"The Operational Infrastructure (OI) investment provides operational support and maintenance for FDA's enterprise IT infrastructure environment. This investment delivers basic IT infrastructure services and operational capability FDA needs to meet its mission and strategic priorities. In FY2011, FDA successfully completed a major IT infrastructure consolidation and modernization initiative through the ICT21 investment. The new consolidated environment provides FDA with an advanced computing infrastructure that is secure, highly virtualized, and scalable to meet FDA's growing needs.  In FY2013, support for the consolidated Data Centers will be managed under the OI investment. This investment will ensure that benefits achieved from consolidation are sustained by providing service offerings in each of the following technology service categories:1.        Capital Expenditures2.       Data Center Services3.       Technology Supporting Services4.      Licenses & Maintenance Services5.       Internet/Intranet Services6.      Telecom Services7.       FDA Mail Services8.      Agency System Operations Services9.      Field Connectivity Services10.    Office of Information Management Support Services Additional cost savings and efficiencies are also being pursued through key management initiatives: (1)Improve FDA's approach to managing its IT infrastructure portfolio; (2) Improve integrated release planning process with systems development teams and business owners; (3) Improve acquisition strategy for IT infrastructure and reduce costs by negotiating more appropriate set of rates.", Enhancement_spend_$m:0, Evaluation_by_CIO:"4"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Investment;
UNWIND [{_id:267, properties:{Code:"10", Name:"Food and Drug Administration"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Bureau;
UNWIND [{_id:1042, properties:{name:"404-Information and Technology Management"}}, {_id:1046, properties:{name:"110-Health"}}, {_id:1081, properties:{name:"402-Financial Management"}}, {_id:1213, properties:{name:"109-General Science and Innovation"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Business_Function;
UNWIND [{_id:465, properties:{Description:"TAS::75 4554::TAS ORACLE - ANNUAL MAINTENANCE OF EXISTING LICENSE W/CREDIT OF $290,239.43", Contract_size:"54.260897", ID:"21337"}}, {_id:467, properties:{Description:"TAS::75 4554::TAS ORACLE - ANNUAL MAINTENANCE OF EXISTING LICENSE W/CREDIT OF $290,239.43", Contract_size:"54.260897", ID:"21338"}}, {_id:468, properties:{Description:"EDS TO#3, CONTRACTOR OWNED, CONTRACTOR OPERATED HOSTED DATA CENTER", Contract_size:"210.67890099999997", ID:"21386"}}, {_id:470, properties:{Description:"ARRA::YES::ARRA TAS::75 1701::TAS  ARRAOS- SERVICES TO CONVERT LEGACY DATA TO STANDARDIZED FORMATS", Contract_size:"5.94745", ID:"21388"}}, {_id:472, properties:{Description:"TAS::75 0600::TAS   MODERN ANALYTICAL TOOLS SECURITY", Contract_size:"0.180539", ID:"21389"}}, {_id:474, properties:{Description:"TAS::75 0600::TASCSC-CDER AUTOMATION-EDR TO JANUS (TASK ORDER  XX UNDER ELMS CONTRACT)", Contract_size:"0.348408", ID:"21391"}}, {_id:500, properties:{Description:"WHITE OAK DATA CENTER EQUIPMENT", Contract_size:"26.740875", ID:"21428"}}, {_id:502, properties:{Description:"BUCCANEER AWARD OF TASK ORDER 2", Contract_size:"39.523449", ID:"21429"}}, {_id:504, properties:{Description:"FDA EMAIL - TASK ORDER UNDER ICT21 CONTRACT", Contract_size:"20.969576999999997", ID:"21430"}}, {_id:505, properties:{Description:"AWARD OF CUSTOMER SUPPORT SERVICES (CSS) TASK ORDER", Contract_size:"36.425145", ID:"21431"}}, {_id:506, properties:{Description:"TAS::75 0600::TAS PC REFRESH BUY", Contract_size:"12.942542999999999", ID:"21432"}}] AS row
CREATE (n:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Contract;
:commit;
:begin;
UNWIND [{start: {_id:57}, end: {_id:466}, properties:{}}, {start: {_id:57}, end: {_id:466}, properties:{}}, {start: {_id:271}, end: {_id:469}, properties:{}}, {start: {_id:271}, end: {_id:471}, properties:{}}, {start: {_id:271}, end: {_id:473}, properties:{}}, {start: {_id:271}, end: {_id:475}, properties:{}}, {start: {_id:277}, end: {_id:501}, properties:{}}, {start: {_id:277}, end: {_id:503}, properties:{}}, {start: {_id:277}, end: {_id:503}, properties:{}}, {start: {_id:277}, end: {_id:501}, properties:{}}, {start: {_id:277}, end: {_id:507}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:uses_Supplier]->(end) SET r += row.properties;
UNWIND [{start: {_id:268}, end: {_id:1152}, properties:{}}, {start: {_id:67}, end: {_id:1204}, properties:{}}, {start: {_id:57}, end: {_id:1068}, properties:{}}, {start: {_id:53}, end: {_id:1068}, properties:{}}, {start: {_id:269}, end: {_id:1033}, properties:{}}, {start: {_id:270}, end: {_id:1035}, properties:{}}, {start: {_id:271}, end: {_id:1143}, properties:{}}, {start: {_id:277}, end: {_id:1112}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:is_a_type_of]->(end) SET r += row.properties;
UNWIND [{start: {_id:64}, end: {_id:2308}, properties:{}}, {start: {_id:64}, end: {_id:2309}, properties:{}}, {start: {_id:64}, end: {_id:2310}, properties:{}}, {start: {_id:64}, end: {_id:2311}, properties:{}}, {start: {_id:64}, end: {_id:2312}, properties:{}}, {start: {_id:64}, end: {_id:2313}, properties:{}}, {start: {_id:64}, end: {_id:2314}, properties:{}}, {start: {_id:64}, end: {_id:2315}, properties:{}}, {start: {_id:64}, end: {_id:2316}, properties:{}}, {start: {_id:64}, end: {_id:2317}, properties:{}}, {start: {_id:64}, end: {_id:2318}, properties:{}}, {start: {_id:64}, end: {_id:2319}, properties:{}}, {start: {_id:64}, end: {_id:2320}, properties:{}}, {start: {_id:64}, end: {_id:2321}, properties:{}}, {start: {_id:64}, end: {_id:2322}, properties:{}}, {start: {_id:64}, end: {_id:2323}, properties:{}}, {start: {_id:64}, end: {_id:2324}, properties:{}}, {start: {_id:64}, end: {_id:2325}, properties:{}}, {start: {_id:64}, end: {_id:2326}, properties:{}}, {start: {_id:64}, end: {_id:2327}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:has_task]->(end) SET r += row.properties;
UNWIND [{start: {_id:64}, end: {_id:2328}, properties:{}}, {start: {_id:64}, end: {_id:2329}, properties:{}}, {start: {_id:64}, end: {_id:2330}, properties:{}}, {start: {_id:64}, end: {_id:2331}, properties:{}}, {start: {_id:64}, end: {_id:2332}, properties:{}}, {start: {_id:64}, end: {_id:2333}, properties:{}}, {start: {_id:64}, end: {_id:2334}, properties:{}}, {start: {_id:64}, end: {_id:2335}, properties:{}}, {start: {_id:64}, end: {_id:2336}, properties:{}}, {start: {_id:66}, end: {_id:2339}, properties:{}}, {start: {_id:54}, end: {_id:2340}, properties:{}}, {start: {_id:54}, end: {_id:2341}, properties:{}}, {start: {_id:54}, end: {_id:2342}, properties:{}}, {start: {_id:54}, end: {_id:2343}, properties:{}}, {start: {_id:54}, end: {_id:2344}, properties:{}}, {start: {_id:55}, end: {_id:2347}, properties:{}}, {start: {_id:55}, end: {_id:2348}, properties:{}}, {start: {_id:68}, end: {_id:1898}, properties:{}}, {start: {_id:68}, end: {_id:1899}, properties:{}}, {start: {_id:69}, end: {_id:1900}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:has_task]->(end) SET r += row.properties;
UNWIND [{start: {_id:69}, end: {_id:1901}, properties:{}}, {start: {_id:69}, end: {_id:1902}, properties:{}}, {start: {_id:69}, end: {_id:1903}, properties:{}}, {start: {_id:69}, end: {_id:1904}, properties:{}}, {start: {_id:69}, end: {_id:1905}, properties:{}}, {start: {_id:69}, end: {_id:1906}, properties:{}}, {start: {_id:58}, end: {_id:2247}, properties:{}}, {start: {_id:58}, end: {_id:2248}, properties:{}}, {start: {_id:58}, end: {_id:2249}, properties:{}}, {start: {_id:58}, end: {_id:2250}, properties:{}}, {start: {_id:58}, end: {_id:2251}, properties:{}}, {start: {_id:58}, end: {_id:2252}, properties:{}}, {start: {_id:58}, end: {_id:2253}, properties:{}}, {start: {_id:58}, end: {_id:2254}, properties:{}}, {start: {_id:58}, end: {_id:2255}, properties:{}}, {start: {_id:58}, end: {_id:2256}, properties:{}}, {start: {_id:58}, end: {_id:2257}, properties:{}}, {start: {_id:58}, end: {_id:2258}, properties:{}}, {start: {_id:59}, end: {_id:2259}, properties:{}}, {start: {_id:60}, end: {_id:2260}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:has_task]->(end) SET r += row.properties;
UNWIND [{start: {_id:60}, end: {_id:2261}, properties:{}}, {start: {_id:60}, end: {_id:2262}, properties:{}}, {start: {_id:60}, end: {_id:2263}, properties:{}}, {start: {_id:60}, end: {_id:2264}, properties:{}}, {start: {_id:61}, end: {_id:2289}, properties:{}}, {start: {_id:61}, end: {_id:2290}, properties:{}}, {start: {_id:61}, end: {_id:2291}, properties:{}}, {start: {_id:61}, end: {_id:2292}, properties:{}}, {start: {_id:61}, end: {_id:2293}, properties:{}}, {start: {_id:61}, end: {_id:2294}, properties:{}}, {start: {_id:61}, end: {_id:2295}, properties:{}}, {start: {_id:62}, end: {_id:2296}, properties:{}}, {start: {_id:62}, end: {_id:2297}, properties:{}}, {start: {_id:55}, end: {_id:2349}, properties:{}}, {start: {_id:62}, end: {_id:2298}, properties:{}}, {start: {_id:62}, end: {_id:2299}, properties:{}}, {start: {_id:62}, end: {_id:2300}, properties:{}}, {start: {_id:63}, end: {_id:2301}, properties:{}}, {start: {_id:63}, end: {_id:2302}, properties:{}}, {start: {_id:63}, end: {_id:2303}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:has_task]->(end) SET r += row.properties;
UNWIND [{start: {_id:63}, end: {_id:2304}, properties:{}}, {start: {_id:63}, end: {_id:2305}, properties:{}}, {start: {_id:55}, end: {_id:2350}, properties:{}}, {start: {_id:55}, end: {_id:2351}, properties:{}}, {start: {_id:63}, end: {_id:2306}, properties:{}}, {start: {_id:55}, end: {_id:2352}, properties:{}}, {start: {_id:55}, end: {_id:2353}, properties:{}}, {start: {_id:55}, end: {_id:2354}, properties:{}}, {start: {_id:63}, end: {_id:2307}, properties:{}}, {start: {_id:55}, end: {_id:2355}, properties:{}}, {start: {_id:55}, end: {_id:2356}, properties:{}}, {start: {_id:55}, end: {_id:2357}, properties:{}}, {start: {_id:56}, end: {_id:2358}, properties:{}}, {start: {_id:56}, end: {_id:2359}, properties:{}}, {start: {_id:56}, end: {_id:2360}, properties:{}}, {start: {_id:56}, end: {_id:2361}, properties:{}}, {start: {_id:56}, end: {_id:2362}, properties:{}}, {start: {_id:56}, end: {_id:2363}, properties:{}}, {start: {_id:56}, end: {_id:2364}, properties:{}}, {start: {_id:56}, end: {_id:2365}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:has_task]->(end) SET r += row.properties;
UNWIND [{start: {_id:65}, end: {_id:2755}, properties:{}}, {start: {_id:65}, end: {_id:2756}, properties:{}}, {start: {_id:65}, end: {_id:2757}, properties:{}}, {start: {_id:68}, end: {_id:2811}, properties:{}}, {start: {_id:68}, end: {_id:2812}, properties:{}}, {start: {_id:68}, end: {_id:2813}, properties:{}}, {start: {_id:68}, end: {_id:2814}, properties:{}}, {start: {_id:68}, end: {_id:2815}, properties:{}}, {start: {_id:69}, end: {_id:2816}, properties:{}}, {start: {_id:70}, end: {_id:2817}, properties:{}}, {start: {_id:70}, end: {_id:2818}, properties:{}}, {start: {_id:70}, end: {_id:2819}, properties:{}}, {start: {_id:70}, end: {_id:2820}, properties:{}}, {start: {_id:70}, end: {_id:2821}, properties:{}}, {start: {_id:71}, end: {_id:2822}, properties:{}}, {start: {_id:71}, end: {_id:2823}, properties:{}}, {start: {_id:71}, end: {_id:2824}, properties:{}}, {start: {_id:71}, end: {_id:2825}, properties:{}}, {start: {_id:71}, end: {_id:2826}, properties:{}}, {start: {_id:71}, end: {_id:2827}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:has_task]->(end) SET r += row.properties;
UNWIND [{start: {_id:72}, end: {_id:2828}, properties:{}}, {start: {_id:72}, end: {_id:2829}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:has_task]->(end) SET r += row.properties;
UNWIND [{start: {_id:268}, end: {_id:1046}, properties:{}}, {start: {_id:67}, end: {_id:1042}, properties:{}}, {start: {_id:57}, end: {_id:1046}, properties:{}}, {start: {_id:53}, end: {_id:1046}, properties:{}}, {start: {_id:269}, end: {_id:1081}, properties:{}}, {start: {_id:270}, end: {_id:1046}, properties:{}}, {start: {_id:271}, end: {_id:1213}, properties:{}}, {start: {_id:277}, end: {_id:1042}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:has_business_function]->(end) SET r += row.properties;
UNWIND [{start: {_id:53}, end: {_id:54}, properties:{}}, {start: {_id:53}, end: {_id:55}, properties:{}}, {start: {_id:53}, end: {_id:56}, properties:{}}, {start: {_id:57}, end: {_id:58}, properties:{}}, {start: {_id:57}, end: {_id:59}, properties:{}}, {start: {_id:57}, end: {_id:60}, properties:{}}, {start: {_id:57}, end: {_id:61}, properties:{}}, {start: {_id:57}, end: {_id:62}, properties:{}}, {start: {_id:57}, end: {_id:63}, properties:{}}, {start: {_id:57}, end: {_id:64}, properties:{}}, {start: {_id:57}, end: {_id:65}, properties:{}}, {start: {_id:57}, end: {_id:66}, properties:{}}, {start: {_id:67}, end: {_id:68}, properties:{}}, {start: {_id:67}, end: {_id:69}, properties:{}}, {start: {_id:67}, end: {_id:70}, properties:{}}, {start: {_id:67}, end: {_id:71}, properties:{}}, {start: {_id:67}, end: {_id:72}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:pays_for]->(end) SET r += row.properties;
UNWIND [{start: {_id:57}, end: {_id:465}, properties:{}}, {start: {_id:57}, end: {_id:467}, properties:{}}, {start: {_id:271}, end: {_id:468}, properties:{}}, {start: {_id:271}, end: {_id:470}, properties:{}}, {start: {_id:271}, end: {_id:472}, properties:{}}, {start: {_id:271}, end: {_id:474}, properties:{}}, {start: {_id:277}, end: {_id:500}, properties:{}}, {start: {_id:277}, end: {_id:502}, properties:{}}, {start: {_id:277}, end: {_id:504}, properties:{}}, {start: {_id:277}, end: {_id:505}, properties:{}}, {start: {_id:277}, end: {_id:506}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:lets_contract]->(end) SET r += row.properties;
UNWIND [{start: {_id:1042}, end: {_id:1041}, properties:{}}, {start: {_id:1046}, end: {_id:1025}, properties:{}}, {start: {_id:1081}, end: {_id:1041}, properties:{}}, {start: {_id:1213}, end: {_id:1025}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:serves]->(end) SET r += row.properties;
UNWIND [{start: {_id:466}, end: {_id:465}, properties:{}}, {start: {_id:466}, end: {_id:467}, properties:{}}, {start: {_id:469}, end: {_id:468}, properties:{}}, {start: {_id:471}, end: {_id:470}, properties:{}}, {start: {_id:473}, end: {_id:472}, properties:{}}, {start: {_id:475}, end: {_id:474}, properties:{}}, {start: {_id:501}, end: {_id:500}, properties:{}}, {start: {_id:503}, end: {_id:502}, properties:{}}, {start: {_id:503}, end: {_id:504}, properties:{}}, {start: {_id:501}, end: {_id:505}, properties:{}}, {start: {_id:507}, end: {_id:506}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:delivers]->(end) SET r += row.properties;
UNWIND [{start: {_id:277}, end: {_id:768}, properties:{}}, {start: {_id:277}, end: {_id:769}, properties:{}}, {start: {_id:277}, end: {_id:770}, properties:{}}, {start: {_id:277}, end: {_id:771}, properties:{}}, {start: {_id:277}, end: {_id:772}, properties:{}}, {start: {_id:277}, end: {_id:773}, properties:{}}, {start: {_id:277}, end: {_id:774}, properties:{}}, {start: {_id:277}, end: {_id:775}, properties:{}}, {start: {_id:277}, end: {_id:776}, properties:{}}, {start: {_id:67}, end: {_id:777}, properties:{}}, {start: {_id:67}, end: {_id:778}, properties:{}}, {start: {_id:67}, end: {_id:779}, properties:{}}, {start: {_id:67}, end: {_id:780}, properties:{}}, {start: {_id:67}, end: {_id:781}, properties:{}}, {start: {_id:269}, end: {_id:782}, properties:{}}, {start: {_id:269}, end: {_id:783}, properties:{}}, {start: {_id:269}, end: {_id:784}, properties:{}}, {start: {_id:269}, end: {_id:785}, properties:{}}, {start: {_id:269}, end: {_id:786}, properties:{}}, {start: {_id:269}, end: {_id:787}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:judged_by]->(end) SET r += row.properties;
UNWIND [{start: {_id:270}, end: {_id:754}, properties:{}}, {start: {_id:270}, end: {_id:755}, properties:{}}, {start: {_id:270}, end: {_id:756}, properties:{}}, {start: {_id:270}, end: {_id:757}, properties:{}}, {start: {_id:270}, end: {_id:758}, properties:{}}, {start: {_id:270}, end: {_id:759}, properties:{}}, {start: {_id:53}, end: {_id:760}, properties:{}}, {start: {_id:53}, end: {_id:0}, properties:{}}, {start: {_id:53}, end: {_id:1}, properties:{}}, {start: {_id:53}, end: {_id:2}, properties:{}}, {start: {_id:53}, end: {_id:303}, properties:{}}, {start: {_id:53}, end: {_id:301}, properties:{}}, {start: {_id:271}, end: {_id:300}, properties:{}}, {start: {_id:271}, end: {_id:175}, properties:{}}, {start: {_id:271}, end: {_id:174}, properties:{}}, {start: {_id:271}, end: {_id:164}, properties:{}}, {start: {_id:271}, end: {_id:172}, properties:{}}, {start: {_id:271}, end: {_id:173}, properties:{}}, {start: {_id:271}, end: {_id:176}, properties:{}}, {start: {_id:271}, end: {_id:298}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:judged_by]->(end) SET r += row.properties;
UNWIND [{start: {_id:268}, end: {_id:299}, properties:{}}, {start: {_id:268}, end: {_id:302}, properties:{}}, {start: {_id:268}, end: {_id:171}, properties:{}}, {start: {_id:268}, end: {_id:177}, properties:{}}, {start: {_id:268}, end: {_id:170}, properties:{}}, {start: {_id:268}, end: {_id:761}, properties:{}}, {start: {_id:268}, end: {_id:762}, properties:{}}, {start: {_id:57}, end: {_id:763}, properties:{}}, {start: {_id:57}, end: {_id:764}, properties:{}}, {start: {_id:57}, end: {_id:765}, properties:{}}, {start: {_id:57}, end: {_id:766}, properties:{}}, {start: {_id:57}, end: {_id:767}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:judged_by]->(end) SET r += row.properties;
UNWIND [{start: {_id:267}, end: {_id:268}, properties:{}}, {start: {_id:267}, end: {_id:67}, properties:{}}, {start: {_id:267}, end: {_id:57}, properties:{}}, {start: {_id:267}, end: {_id:53}, properties:{}}, {start: {_id:267}, end: {_id:269}, properties:{}}, {start: {_id:267}, end: {_id:270}, properties:{}}, {start: {_id:267}, end: {_id:271}, properties:{}}, {start: {_id:267}, end: {_id:277}, properties:{}}] AS row
MATCH (start:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.start._id})
MATCH (end:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`: row.end._id})
CREATE (start)-[r:responsible_for]->(end) SET r += row.properties;
:commit;
:begin;
MATCH (n:`UNIQUE IMPORT LABEL`)  WITH n LIMIT 20000 REMOVE n:`UNIQUE IMPORT LABEL` REMOVE n.`UNIQUE IMPORT ID`;
:commit;
:begin;
DROP CONSTRAINT ON (node:`UNIQUE IMPORT LABEL`) ASSERT (node.`UNIQUE IMPORT ID`) IS UNIQUE;
:commit;