FDA sub graph 0

CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:0.008, Id:"2168", Planned_Cost:0.334, Planned_Duration:729, Project_delay:0, Start_days_after_2000:3561, Updated_Date:876, name:"FDA ORA ALM Laboratory Information Management System (LIMS) Proof of Concept", `UNIQUE IMPORT ID`:0});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:0.126, Id:"2171", Planned_Cost:1.644, Planned_Duration:538, Project_delay:0, Start_days_after_2000:3855, Updated_Date:582, name:"FDA ORA ALM Electronic Laboratory Exchange Network (eLEXNET) Support 1", `UNIQUE IMPORT ID`:1});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:0.038, Id:"2173", Planned_Cost:0.786, Planned_Duration:786, Project_delay:0, Start_days_after_2000:3469, Updated_Date:968, name:"FDA ORA ALM Quality Management Information System (QMiS) Support 1", `UNIQUE IMPORT ID`:2});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:-0.122, Id:"2150", Planned_Cost:5.192, Planned_Duration:364, Project_delay:0, Start_days_after_2000:3903, Updated_Date:533, name:"FDA ORA MARCS Program Management and Technical Integration (PMTI)", `UNIQUE IMPORT ID`:3});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:-0.002, Id:"2151", Planned_Cost:0.116, Planned_Duration:76, Project_delay:1, Start_days_after_2000:4183, Updated_Date:253, name:"FDA ORA MARCS Food Safety Modernization Act (FSMA)", `UNIQUE IMPORT ID`:4});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:0.014, Id:"2152", Planned_Cost:1.359, Planned_Duration:307, Project_delay:0, Start_days_after_2000:3922, Updated_Date:514, name:"FDA ORA MARCS Authorization, Roles, and Responsibilities Management Services (ARRMS) 2", `UNIQUE IMPORT ID`:5});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:-1.885, Id:"2154", Planned_Cost:2.248, Planned_Duration:417, Project_delay:0, Start_days_after_2000:3922, Updated_Date:514, name:"FDA ORA MARCS Entry Manager (EM)", `UNIQUE IMPORT ID`:6});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:-0.024, Id:"2155", Planned_Cost:0.677, Planned_Duration:364, Project_delay:0, Start_days_after_2000:3924, Updated_Date:512, name:"FDA ORA MARCS Predictive Risk-based Evaluation and Dynamic Import Compliance Targeting (PREDICT)", `UNIQUE IMPORT ID`:7});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:0.004, Id:"2156", Planned_Cost:1.294, Planned_Duration:364, Project_delay:44, Start_days_after_2000:3922, Updated_Date:514, name:"FDA ORA MARCS Document Generator Services (DGS)", `UNIQUE IMPORT ID`:8});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:-0.027, Id:"2157", Planned_Cost:2.742, Planned_Duration:364, Project_delay:0, Start_days_after_2000:3922, Updated_Date:514, name:"FDA ORA MARCS Work Assignment and Accomplishment Manager (WAAM) 2", `UNIQUE IMPORT ID`:9});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:0.073, Id:"2160", Planned_Cost:0.688, Planned_Duration:185, Project_delay:0, Start_days_after_2000:4255, Updated_Date:181, name:"FDA ORA MARCS Authorization, Roles, and Responsibilities Management Services (ARRMS) 2-Supplemental", `UNIQUE IMPORT ID`:10});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:0, Id:"2167", Planned_Cost:4.856, Planned_Duration:57, Project_delay:0, Start_days_after_2000:4233, Updated_Date:203, name:"FDA ORA MARCS Software Acquisition for Oracle Technologies", `UNIQUE IMPORT ID`:11});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:0.025, Id:"2038", Planned_Cost:0.507, Planned_Duration:318, Project_delay:0, Start_days_after_2000:4216, Updated_Date:371, name:"FDA ORA RBIS Center and External Integration", `UNIQUE IMPORT ID`:12});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:0.014, Id:"2039", Planned_Cost:0.584, Planned_Duration:144, Project_delay:7, Start_days_after_2000:4170, Updated_Date:329, name:"FDA ORA RBIS Data Warehouse, Data Marts, and Universes", `UNIQUE IMPORT ID`:13});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:-0.023, Id:"2040", Planned_Cost:0.316, Planned_Duration:289, Project_delay:0, Start_days_after_2000:4244, Updated_Date:255, name:"FDA ORA RBIS Firm Master List Services (FMLS) Enhancements", `UNIQUE IMPORT ID`:14});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:-1.506, Id:"2041", Planned_Cost:2.085, Planned_Duration:365, Project_delay:0, Start_days_after_2000:4272, Updated_Date:315, name:"FDA ORA RBIS Report Development Support", `UNIQUE IMPORT ID`:15});
CREATE (:Project:`UNIQUE IMPORT LABEL` {Cost_Variance:-0.028, Id:"2042", Planned_Cost:0.275, Planned_Duration:231, Project_delay:0, Start_days_after_2000:4272, Updated_Date:290, name:"FDA ORA RBIS Data Evaluation and Recommendations", `UNIQUE IMPORT ID`:16});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"HPC: Increase immunity for running jobs from power outgages lasting up to 6 minutes", ID:"3498", Measurement_category:"101-Mission and Business Results - Services for Citizens", Metric_results:"Met", `UNIQUE IMPORT ID`:17});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"HPC: Increase aggregarte avilability of spare capacity across all clusters.", ID:"3497", Measurement_category:"202-Process and Activities - Productivity", Metric_results:"Met", `UNIQUE IMPORT ID`:18});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"DCM: Percentage of uptime at Contractor Host Data Center (CHDC) Platform Reliablity", ID:"3502", Measurement_category:"114-Customer Results - Service Quality", Metric_results:"Met", `UNIQUE IMPORT ID`:19});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"% of IT Service Requests Approved According to Established Prioritization Criteria", ID:"3512", Measurement_category:"103-Mission and Business Results - Management of Government Resources", Metric_results:"Not Met", `UNIQUE IMPORT ID`:20});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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.", ID:"3298", Measurement_category:"115-Customer Results - Service Accessibility", Metric_results:"Not Met", `UNIQUE IMPORT ID`:21});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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.", ID:"3299", Measurement_category:"114-Customer Results - Service Quality", Metric_results:"Met", `UNIQUE IMPORT ID`:22});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Number of objects available in RBIS ORADSS. This allows end users increased access to data without having to navigate the underlying data structures.", ID:"3300", Measurement_category:"202-Process and Activities - Productivity", Metric_results:"Met", `UNIQUE IMPORT ID`:23});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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.", ID:"3301", Measurement_category:"213-Technology - Efficiency", Metric_results:"Not Met", `UNIQUE IMPORT ID`:24});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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.", ID:"3302", Measurement_category:"214-Technology - Information and Data", Metric_results:"Met", `UNIQUE IMPORT ID`:25});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"ROI. Maintain or reduce Cost per dollar collected through UFFRS", ID:"3596", Measurement_category:"201-Process and Activities - Financial", Metric_results:"Met", `UNIQUE IMPORT ID`:26});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Maintain or reduce unscheduled down time as a result of application/UFFRS defects", ID:"3597", Measurement_category:"215-Technology - Reliability and Availability", Metric_results:"Met", `UNIQUE IMPORT ID`:27});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Maintain or reduce Cost per User", ID:"3598", Measurement_category:"211-Technology - Technology Costs", Metric_results:"Met", `UNIQUE IMPORT ID`:28});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Reduce execution time for key reports", ID:"3599", Measurement_category:"203-Process and Activities - Cycle Time and Timeliness", Metric_results:"Met", `UNIQUE IMPORT ID`:29});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Increase the number of BIRS users generating special reports", ID:"3600", Measurement_category:"111-Customer Results - Customer Benefit", Metric_results:"Met", `UNIQUE IMPORT ID`:30});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Maintain or increase the number of regulatory actions that are  supported by UFFMS", ID:"3601", Measurement_category:"102-Mission and Business Results - Support Delivery of Services", Metric_results:"Met", `UNIQUE IMPORT ID`:31});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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", `UNIQUE IMPORT ID`:32});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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", `UNIQUE IMPORT ID`:33});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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", `UNIQUE IMPORT ID`:34});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"SE: Increase the number of SE rooms", ID:"3499", Measurement_category:"206-Process and Activities - Management and Innovation", Metric_results:"Met", `UNIQUE IMPORT ID`:35});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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", `UNIQUE IMPORT ID`:36});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Time for retrieval of complete product information including manufacturing, regulatory, substance and labeling.", ID:"3474", Measurement_category:"203-Process and Activities - Cycle Time and Timeliness", Metric_results:"Met", `UNIQUE IMPORT ID`:37});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"SE: maintain optimal response time as new rooms are added to the Scientific Enclave.", ID:"3500", Measurement_category:"215-Technology - Reliability and Availability", Metric_results:"Met", `UNIQUE IMPORT ID`:38});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"DCM: Median Hours to respond and resolve Severity One outages", ID:"3501", Measurement_category:"113-Customer Results - Timeliness and Responsiveness", Metric_results:"Met", `UNIQUE IMPORT ID`:39});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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", `UNIQUE IMPORT ID`:40});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"DCM: Percentage of uptime of FDA Critical Applications", ID:"3503", Measurement_category:"114-Customer Results - Service Quality", Metric_results:"Met", `UNIQUE IMPORT ID`:41});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Reduction in Operations and Maintenance Costs", ID:"3472", Measurement_category:"211-Technology - Technology Costs", `UNIQUE IMPORT ID`:42});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"HPC: Decrease time a batch job waits before resources become available on a cluster", ID:"3496", Measurement_category:"101-Mission and Business Results - Services for Citizens", Metric_results:"Met", `UNIQUE IMPORT ID`:43});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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", `UNIQUE IMPORT ID`:44});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Cost avoided by eliminating a separate drug quality system", ID:"3473", Measurement_category:"201-Process and Activities - Financial", `UNIQUE IMPORT ID`:45});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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.", ID:"3488", Measurement_category:"215-Technology - Reliability and Availability", Metric_results:"Met", `UNIQUE IMPORT ID`:46});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Number of defects of fixed", ID:"3490", Measurement_category:"215-Technology - Reliability and Availability", Metric_results:"Not Met", `UNIQUE IMPORT ID`:47});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Incerase number of applications using SSO", ID:"3491", Measurement_category:"213-Technology - Efficiency", Metric_results:"Met", `UNIQUE IMPORT ID`:48});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Increase number of BLA Communications", ID:"3492", Measurement_category:"101-Mission and Business Results - Services for Citizens", Metric_results:"Met", `UNIQUE IMPORT ID`:49});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Reduce time for contractor to contact client on TroubleTickets ", ID:"3493", Measurement_category:"113-Customer Results - Timeliness and Responsiveness", Metric_results:"Met", `UNIQUE IMPORT ID`:50});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Increase number of Business Data refreshes in PreProd", ID:"3494", Measurement_category:"114-Customer Results - Service Quality", Metric_results:"Met", `UNIQUE IMPORT ID`:51});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Maintain SLA response times for resolution of severity 2 trouble tickets", ID:"3495", Measurement_category:"213-Technology - Efficiency", Metric_results:"Met", `UNIQUE IMPORT ID`:52});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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", `UNIQUE IMPORT ID`:53});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Percentage validated OTC trade names in adverse event reports", ID:"3477", Measurement_category:"202-Process and Activities - Productivity", `UNIQUE IMPORT ID`:54});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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", `UNIQUE IMPORT ID`:55});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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", `UNIQUE IMPORT ID`:56});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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", `UNIQUE IMPORT ID`:57});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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.", ID:"3481", Measurement_category:"202-Process and Activities - Productivity", Metric_results:"Not Met", `UNIQUE IMPORT ID`:58});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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", `UNIQUE IMPORT ID`:59});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {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", `UNIQUE IMPORT ID`:60});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"% of IT Budget Devoted to Training and Skills Enhancement", ID:"3504", Measurement_category:"114-Customer Results - Service Quality", `UNIQUE IMPORT ID`:61});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"% of IT Budget Devoted to R&D and Innovation", ID:"3505", Measurement_category:"206-Process and Activities - Management and Innovation", `UNIQUE IMPORT ID`:62});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Median # of Days to Deploy an R&D Environment in Production", ID:"3506", Measurement_category:"113-Customer Results - Timeliness and Responsiveness", `UNIQUE IMPORT ID`:63});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"# of ITI Managers with FACPPM Certification ", ID:"3507", Measurement_category:"103-Mission and Business Results - Management of Government Resources", Metric_results:"Not Met", `UNIQUE IMPORT ID`:64});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Median # of Days to Resolve Severity One Outages", ID:"3508", Measurement_category:"203-Process and Activities - Cycle Time and Timeliness", Metric_results:"Met", `UNIQUE IMPORT ID`:65});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"Number of Days Critical Business Services are Unavailable (Excluding Planned Outages)", ID:"3509", Measurement_category:"215-Technology - Reliability and Availability", Metric_results:"Met", `UNIQUE IMPORT ID`:66});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"% of IT Service Requests Submitted with ITI Risk Assessment", ID:"3510", Measurement_category:"103-Mission and Business Results - Management of Government Resources", `UNIQUE IMPORT ID`:67});
CREATE (:Metric:`UNIQUE IMPORT LABEL` {Description:"% of ITI Services that Meet Published SLAs", ID:"3511", Measurement_category:"114-Customer Results - Service Quality", `UNIQUE IMPORT ID`:68});
CREATE (:Supplier:`UNIQUE IMPORT LABEL` {ID:"W91QUZ06A0003", name:"MYTHICS, INC", `UNIQUE IMPORT ID`:69});
CREATE (:Supplier:`UNIQUE IMPORT LABEL` {ID:"HHSF223200850014I", name:"ELECTRONIC DATA SYSTEMS CORPORATION", `UNIQUE IMPORT ID`:70});
CREATE (:Supplier:`UNIQUE IMPORT LABEL` {ID:"HHSF223201000039I", name:"SCENPRO, INC.", `UNIQUE IMPORT ID`:71});
CREATE (:Supplier:`UNIQUE IMPORT LABEL` {ID:"HHSF223200850012I ", name:"CNI INFORMATION TECHNOLOGY, LLC", `UNIQUE IMPORT ID`:72});
CREATE (:Supplier:`UNIQUE IMPORT LABEL` {ID:"HHSF223200950026I ", name:"CNI PROFESSIONAL SERVICES, LLC", `UNIQUE IMPORT ID`:73});
CREATE (:Supplier:`UNIQUE IMPORT LABEL` {ID:"HHSF223200850020I", name:"HUMANTOUCH LLC", `UNIQUE IMPORT ID`:74});
CREATE (:Supplier:`UNIQUE IMPORT LABEL` {ID:"HHSF223200850017I", name:"BUCCANEER COMPUTER SYSTEMS & SERVICE, INC.", `UNIQUE IMPORT ID`:75});
CREATE (:Supplier:`UNIQUE IMPORT LABEL` {ID:"HHSF223200950003B", name:"PANAMERICA COMPUTERS, INC.", `UNIQUE IMPORT ID`:76});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"73 days", Actual_start_delay:"17 days", Id:"8353", No_Child_Activity:"1", Planned_Duration:"90 days", Start_Date_Planned:"2011-08-01", description:"Validate requirements and functionality for Center Views", name:"287623: RBIS CEI Center Views", output_type:"Key Deliverable", planned_Costs:"0.076", status:"Completed - Closed", `UNIQUE IMPORT ID`:77});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"76 days", Actual_start_delay:"0 days", Id:"8355", No_Child_Activity:"1", Planned_Duration:"76 days", Start_Date_Planned:"2011-08-15", description:"This task evaluates requirements to integrate ORADSS with the MARCS SERS application", name:"287623: RBIS CEI SERS Integration", output_type:"Usable Functionality", planned_Costs:"0.004", status:"Completed - Closed", `UNIQUE IMPORT ID`:78});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"122 days", Actual_start_delay:"-6 days", Id:"8357", No_Child_Activity:"1", Planned_Duration:"61 days", Start_Date_Planned:"2011-07-07", 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.", name:"287707: RBIS DWDMU CMS Data Mart", output_type:"Usable Functionality", planned_Costs:"0.076", status:"Completed - Closed", `UNIQUE IMPORT ID`:79});
CREATE (:Business_Area:`UNIQUE IMPORT LABEL` {name:"1-Services for Citizens", `UNIQUE IMPORT ID`:80});
CREATE (:Business_Area:`UNIQUE IMPORT LABEL` {name:"4-Management of Government Resources", `UNIQUE IMPORT ID`:81});
CREATE (:Service:`UNIQUE IMPORT LABEL` {name:"753-Financial Management", `UNIQUE IMPORT ID`:82});
CREATE (:Service:`UNIQUE IMPORT LABEL` {name:"733-Knowledge Management", `UNIQUE IMPORT ID`:83});
CREATE (:Service:`UNIQUE IMPORT LABEL` {name:"711-Tracking and Workflow", `UNIQUE IMPORT ID`:84});
CREATE (:Service:`UNIQUE IMPORT LABEL` {name:"701-Customer Relationship Management", `UNIQUE IMPORT ID`:85});
CREATE (:Service:`UNIQUE IMPORT LABEL` {name:"754-Asset / Materials Management", `UNIQUE IMPORT ID`:86});
CREATE (:Service:`UNIQUE IMPORT LABEL` {name:"751-Data Management", `UNIQUE IMPORT ID`:87});
CREATE (:Service:`UNIQUE IMPORT LABEL` {name:"745-Reporting", `UNIQUE IMPORT ID`:88});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"93 days", Actual_start_delay:"0 days", Id:"9332", No_Child_Activity:"1", Planned_Duration:"93 days", Start_Date_Planned:"2011-02-22", description:"This produced a design for WAAM that supports Work Planner for the annual plan for user interfaces and logical software and data considerations.", name:"286217: WAAM 2 Work Planner Design for User Interface and Logical", output_type:"Key Deliverable", planned_Costs:"0.032", status:"Completed - Closed", `UNIQUE IMPORT ID`:89});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"91 days", Actual_start_delay:"0 days", Id:"9333", No_Child_Activity:"1", Planned_Duration:"91 days", Start_Date_Planned:"2011-05-26", 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.", name:"286217: WAAM 2 Work Planner Design for Services Specifications", output_type:"Key Deliverable", planned_Costs:"0.024", status:"Completed - Closed", `UNIQUE IMPORT ID`:90});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"111 days", Actual_start_delay:"0 days", Id:"9334", No_Child_Activity:"1", Planned_Duration:"100 days", Start_Date_Planned:"2011-06-07", 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.", name:"286217: WAAM 2 Work Planner Design for Physical Data, Security, Interfaces, and Data Synchronization", output_type:"Key Deliverable", planned_Costs:"0.103", status:"Completed - Closed", `UNIQUE IMPORT ID`:91});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"175 days", Actual_start_delay:"0 days", Id:"9335", No_Child_Activity:"1", Planned_Duration:"172 days", Start_Date_Planned:"2011-04-04", description:"This produced code to realize Work Planner functionality.", name:"286217: WAAM 2 Work Planner Development", output_type:"Key Deliverable", planned_Costs:"0.167", status:"Completed - Closed", `UNIQUE IMPORT ID`:92});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"69 days", Actual_start_delay:"0 days", Id:"9336", No_Child_Activity:"1", Planned_Duration:"69 days", Start_Date_Planned:"2011-07-19", description:"This is for conducting unit and regression testing for Work Planner functionality.", name:"286217: WAAM 2 Work Planner Test", output_type:"Key Deliverable", planned_Costs:"0.078", status:"Completed - Closed", `UNIQUE IMPORT ID`:93});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"132 days", Actual_start_delay:"0 days", Id:"9338", No_Child_Activity:"1", Planned_Duration:"132 days", Start_Date_Planned:"2010-10-08", 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.", name:"286217: WAAM 2 Domestic Field Exams, Sample Collection, National Sample Distributor, and Other Business Requirements", output_type:"Key Deliverable", planned_Costs:"0.145", status:"Completed - Closed", `UNIQUE IMPORT ID`:94});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"152 days", Actual_start_delay:"0 days", Id:"9339", No_Child_Activity:"1", Planned_Duration:"146 days", Start_Date_Planned:"2011-04-27", 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.", name:"286217: WAAM 2 Domestic Field Exams, Sample Collection, National Sample Distributor, and Other Functional, Non Functional, and User Interface Requirements", output_type:"Key Deliverable", planned_Costs:"0.113", status:"Completed - Closed", `UNIQUE IMPORT ID`:95});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"57 days", Actual_start_delay:"0 days", Id:"9364", No_Child_Activity:"1", Planned_Duration:"57 days", Start_Date_Planned:"2011-08-04", 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.", name:"286298: Software Acquisition for Oracle Technologies Parent Activity", output_type:"Key Deliverable", planned_Costs:"4.856", status:"Completed - Closed", `UNIQUE IMPORT ID`:96});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"75 days", Actual_start_delay:"0 days", Id:"9366", No_Child_Activity:"1", Planned_Duration:"75 days", Start_Date_Planned:"2009-10-01", 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.", name:"287489: LIMS Proof of Concept Analysis", output_type:"Key Deliverable", planned_Costs:"0.032", status:"Completed - Closed", `UNIQUE IMPORT ID`:97});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"149 days", Actual_start_delay:"0 days", Id:"9367", No_Child_Activity:"1", Planned_Duration:"142 days", Start_Date_Planned:"2009-12-16", 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.", name:"287489: LIMS Proof of Concept Phase 1", output_type:"Usable Functionality", planned_Costs:"0.072", status:"Completed - Closed", `UNIQUE IMPORT ID`:98});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"160 days", Actual_start_delay:"5 days", Id:"9368", No_Child_Activity:"1", Planned_Duration:"165 days", Start_Date_Planned:"2010-05-10", 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.", name:"287489: LIMS Proof of Concept Phase 2", output_type:"Usable Functionality", planned_Costs:"0.125", status:"Completed - Closed", `UNIQUE IMPORT ID`:99});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"164 days", Actual_start_delay:"-13 days", Id:"8362", No_Child_Activity:"1", Planned_Duration:"127 days", Start_Date_Planned:"2011-06-02", 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.", name:"287707: RBIS DWDMU Work Force Reporting Enhancements Requirements and Design", output_type:"Usable Functionality", planned_Costs:"0.066", status:"Completed - Closed", `UNIQUE IMPORT ID`:100});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"38 days", Actual_start_delay:"53 days", Id:"8363", No_Child_Activity:"1", Planned_Duration:"71 days", Start_Date_Planned:"2011-08-01", 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.", name:"287707: RBIS DWDMU Work Force Reporting Enhancements Development, Test, and Implementation", output_type:"Usable Functionality", planned_Costs:"0.127", status:"Completed - Closed", `UNIQUE IMPORT ID`:101});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"122 days", Actual_start_delay:"0 days", Id:"8365", No_Child_Activity:"1", Planned_Duration:"49 days", Start_Date_Planned:"2011-07-01", 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.", name:"287707: RBIS DWDMU  Report Migrations Automated Conversion", output_type:"Usable Functionality", planned_Costs:"0.077", status:"Completed - Closed", `UNIQUE IMPORT ID`:102});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"59 days", Actual_start_delay:"14 days", Id:"8366", No_Child_Activity:"1", Planned_Duration:"66 days", Start_Date_Planned:"2011-08-19", 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.", name:"287707: RBIS DWDMU Report Migrations Manual Conversions of Often Used Reports", output_type:"Usable Functionality", planned_Costs:"0.022", status:"Completed - Closed", `UNIQUE IMPORT ID`:103});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"126 days", Actual_start_delay:"0 days", Id:"8369", No_Child_Activity:"1", Planned_Duration:"79 days", Start_Date_Planned:"2011-06-27", description:"This is to modernize the Business Objects (BO) COTS to use improved and newer functionality.", name:"287707: RBIS DWDMU OPAS Modernization to BO Voyager", output_type:"Usable Functionality", planned_Costs:"0.127", status:"Completed - Closed", `UNIQUE IMPORT ID`:104});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"74 days", Actual_start_delay:"0 days", Id:"8370", No_Child_Activity:"1", Planned_Duration:"67 days", Start_Date_Planned:"2011-08-18", description:"This is to modernize the Informatica COTS to use improved and newer functionality. Informatica is used for data aggregation, manipulation, and analysis.", name:"287707: RBIS DWDMU OPAS Modernization to Informatica 9", output_type:"Usable Functionality", planned_Costs:"0.021", status:"Completed - Closed", `UNIQUE IMPORT ID`:105});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"54 days", Actual_start_delay:"0 days", Id:"9211", No_Child_Activity:"1", Planned_Duration:"54 days", Start_Date_Planned:"2010-09-08", 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).", name:"286120: PMTI Program and Project Deliverables", output_type:"Key Deliverable", planned_Costs:"0.246", status:"Completed - Closed", `UNIQUE IMPORT ID`:106});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"180 days", Actual_start_delay:"0 days", Id:"9212", No_Child_Activity:"1", Planned_Duration:"180 days", Start_Date_Planned:"2010-09-08", 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.", name:"286120: PMTI Program and Project Management Recurring Meetings and Deliverables, Including Stage Gates 1", output_type:"Key Deliverable", planned_Costs:"1.248", status:"Completed - Closed", `UNIQUE IMPORT ID`:107});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"183 days", Actual_start_delay:"0 days", Id:"9213", No_Child_Activity:"1", Planned_Duration:"183 days", Start_Date_Planned:"2011-03-08", 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.", name:"286120: PMTI Program and Project Management Recurring Meetings and Deliverables, Including Stage Gates 2", output_type:"Key Deliverable", planned_Costs:"1.268", status:"Completed - Closed", `UNIQUE IMPORT ID`:108});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"180 days", Actual_start_delay:"0 days", Id:"9215", No_Child_Activity:"1", Planned_Duration:"180 days", Start_Date_Planned:"2010-09-08", description:"This includes work for IT security, system architecture, and data integration.", name:"286120: PMTI Technical Integration 1", output_type:"Usable Functionality", planned_Costs:"0.568", status:"Completed - Closed", `UNIQUE IMPORT ID`:109});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"183 days", Actual_start_delay:"0 days", Id:"9216", No_Child_Activity:"1", Planned_Duration:"183 days", Start_Date_Planned:"2011-03-08", description:"This includes work for IT security, system architecture, and data integration.", name:"286120: PMTI Technical Integration 2", output_type:"Usable Functionality", planned_Costs:"0.616", status:"Completed - Closed", `UNIQUE IMPORT ID`:110});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"180 days", Actual_start_delay:"0 days", Id:"9218", No_Child_Activity:"1", Planned_Duration:"180 days", Start_Date_Planned:"2010-09-08", description:"This provides support for smaller releases only involving legacy systems.", name:"286120: PMTI Release Integration 1", output_type:"Usable Functionality", planned_Costs:"0.123", status:"Completed - Closed", `UNIQUE IMPORT ID`:111});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"183 days", Actual_start_delay:"0 days", Id:"9219", No_Child_Activity:"1", Planned_Duration:"183 days", Start_Date_Planned:"2011-03-08", description:"This provides support for smaller releases only involving legacy systems.", name:"286120: PMTI Release Integration 2", output_type:"Usable Functionality", planned_Costs:"0.123", status:"Completed - Closed", `UNIQUE IMPORT ID`:112});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"136 days", Actual_start_delay:"0 days", Id:"9221", No_Child_Activity:"1", Planned_Duration:"136 days", Start_Date_Planned:"2011-02-01", description:"This provides support for MARCS 0.5 release.  Performance and user acceptance testing, security testing, promotion to Production.", name:"286120: PMTI Release Integration MARCS 0.5 to Pre-Production", output_type:"Usable Functionality", planned_Costs:"0.1", status:"Completed - Closed", `UNIQUE IMPORT ID`:113});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"96 days", Actual_start_delay:"0 days", Id:"9222", No_Child_Activity:"1", Planned_Duration:"96 days", Start_Date_Planned:"2011-06-03", description:"This provides support for MARCS 0.5 release.  Performance and user acceptance testing, security testing, promotion to Production.", name:"286120: PMTI Release Integration MARCS 0.5 to Production", output_type:"Usable Functionality", planned_Costs:"0.05", status:"Completed - Closed", `UNIQUE IMPORT ID`:114});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"309 days", Actual_start_delay:"0 days", Id:"9224", No_Child_Activity:"1", Planned_Duration:"153 days", Start_Date_Planned:"2010-11-02", description:"This provides support for MARCS 1.0 release. System integration testing, promotion to Pre-Production.", name:"286120: PMTI Release Integration MARCS 1.0 to Pre-Production", output_type:"Usable Functionality", planned_Costs:"0.5", status:"Completed - Closed", `UNIQUE IMPORT ID`:115});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"155 days", Actual_start_delay:"0 days", Id:"9225", No_Child_Activity:"1", Planned_Duration:"155 days", Start_Date_Planned:"2011-04-05", description:"This provides support for MARCS 1.0 release.  Performance and user acceptance testing, security testing, promotion to Production. ", name:"286120: PMTI Release Integration MARCS 1.0 to Production", output_type:"Usable Functionality", planned_Costs:"0.15", status:"Completed - Closed", `UNIQUE IMPORT ID`:116});
CREATE (:Bureau:`UNIQUE IMPORT LABEL` {Code:"10", Name:"Food and Drug Administration", `UNIQUE IMPORT ID`:117});
CREATE (:Contract:`UNIQUE IMPORT LABEL` {Contract_size:"54.260897", Description:"TAS::75 4554::TAS ORACLE - ANNUAL MAINTENANCE OF EXISTING LICENSE W/CREDIT OF $290,239.43", ID:"21337", `UNIQUE IMPORT ID`:118});
CREATE (:Contract:`UNIQUE IMPORT LABEL` {Contract_size:"54.260897", Description:"TAS::75 4554::TAS ORACLE - ANNUAL MAINTENANCE OF EXISTING LICENSE W/CREDIT OF $290,239.43", ID:"21338", `UNIQUE IMPORT ID`:119});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"159 days", Actual_start_delay:"0 days", Id:"9226", No_Child_Activity:"1", Planned_Duration:"159 days", Start_Date_Planned:"2011-04-01", description:"This provides support for MARCS 1.1 release. This includes testing, configuration management, promotion through environments, and coordination with ORA and OIM.", name:"286120: PMTI Release Integration MARCS 1.1", output_type:"Usable Functionality", planned_Costs:"0.2", status:"Completed - Closed", `UNIQUE IMPORT ID`:120});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"77 days", Actual_start_delay:"0 days", Id:"9227", No_Child_Activity:"1", Planned_Duration:"76 days", Start_Date_Planned:"2011-06-15", 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).", name:"286177: Food Safety Modernization Act (FSMA) Parent Activity", output_type:"Usable Functionality", planned_Costs:"0.116", status:"Completed - Closed", `UNIQUE IMPORT ID`:121});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"98 days", Actual_start_delay:"0 days", Id:"9229", No_Child_Activity:"1", Planned_Duration:"98 days", Start_Date_Planned:"2010-09-27", 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.", name:"286202: ARRMS 2 Requirements Validation and Decision Analysis", output_type:"Key Deliverable", planned_Costs:"0.141", status:"Completed - Closed", `UNIQUE IMPORT ID`:122});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"124 days", Actual_start_delay:"0 days", Id:"9230", No_Child_Activity:"1", Planned_Duration:"124 days", Start_Date_Planned:"2010-10-27", description:"This validated requirements to determine which ones would be fulfilled by a COTS and which ones would need custom development. ", name:"286202: ARRMS 2 Requirements Validation and Decision Analysis", output_type:"Key Deliverable", planned_Costs:"0.288", status:"Completed - Closed", `UNIQUE IMPORT ID`:123});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"144 days", Actual_start_delay:"0 days", Id:"9231", No_Child_Activity:"1", Planned_Duration:"144 days", Start_Date_Planned:"2011-02-14", description:"This validated requirements for integrating with ALM and RBIS in the future.", name:"286202: ARRMS 2 Requirements Validation Integration with ALM and RBIS", output_type:"Key Deliverable", planned_Costs:"0.242", status:"Completed - Closed", `UNIQUE IMPORT ID`:124});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"191 days", Actual_start_delay:"0 days", Id:"9232", No_Child_Activity:"1", Planned_Duration:"191 days", Start_Date_Planned:"2011-01-21", description:"This produced a design for incorporating the COTS chosen by FDA.", name:"286202: ARRMS 2 Design ", output_type:"Key Deliverable", planned_Costs:"0.5", status:"Completed - Closed", `UNIQUE IMPORT ID`:125});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"24 days", Actual_start_delay:"24 days", Id:"9233", No_Child_Activity:"1", Planned_Duration:"48 days", Start_Date_Planned:"2011-06-13", description:"This is to produce functionality for roles and organizations.", name:"286202: ARRMS 2 Development", output_type:"Usable Functionality", planned_Costs:"0.188", status:"Completed - Closed", `UNIQUE IMPORT ID`:126});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"112 days", Actual_start_delay:"0 days", Id:"9272", No_Child_Activity:"1", Planned_Duration:"112 days", Start_Date_Planned:"2010-09-27", description:"This gathered requirements for Entry Query business considerations.", name:"286212: EM Business Requirements ", output_type:"Key Deliverable", planned_Costs:"0.268", status:"Completed - Closed", `UNIQUE IMPORT ID`:127});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"127 days", Actual_start_delay:"0 days", Id:"9273", No_Child_Activity:"1", Planned_Duration:"127 days", Start_Date_Planned:"2011-01-18", description:"This gathered requirements for Entry Query functionality, user interface, and non functional considerations.", name:"286212: EM Functional, Non Functional, and User Interface Requirements", output_type:"Key Deliverable", planned_Costs:"0.367", status:"Completed - Closed", `UNIQUE IMPORT ID`:128});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"161 days", Actual_start_delay:"37 days", Id:"9275", No_Child_Activity:"1", Planned_Duration:"191 days", Start_Date_Planned:"2011-01-03", description:"This produced a preliminary design for Entry Query functionality within EM.", name:"286212: EM Preliminary Design", output_type:"Key Deliverable", planned_Costs:"0.357", status:"Completed - Closed", `UNIQUE IMPORT ID`:129});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"131 days", Actual_start_delay:"43 days", Id:"9317", No_Child_Activity:"1", Planned_Duration:"168 days", Start_Date_Planned:"2011-04-05", 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.", name:"286217: WAAM 2 Inspections Development Iterations 3 and 4", output_type:"Usable Functionality", planned_Costs:"0.215", status:"Completed - Closed", `UNIQUE IMPORT ID`:130});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"131 days", Actual_start_delay:"43 days", Id:"9318", No_Child_Activity:"1", Planned_Duration:"174 days", Start_Date_Planned:"2011-04-05", description:"This is for conducting unit and regression testing for Inspections functionality.", name:"286217: WAAM 2 Inspections Test", output_type:"Usable Functionality", planned_Costs:"0.082", status:"Completed - Closed", `UNIQUE IMPORT ID`:131});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"172 days", Actual_start_delay:"0 days", Id:"9321", No_Child_Activity:"1", Planned_Duration:"112 days", Start_Date_Planned:"2010-10-15", 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.", name:"286217: WAAM 2 Import Field Exams Business Requirements ", output_type:"Key Deliverable", planned_Costs:"0.061", status:"Completed - Closed", `UNIQUE IMPORT ID`:132});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"155 days", Actual_start_delay:"0 days", Id:"9322", No_Child_Activity:"1", Planned_Duration:"67 days", Start_Date_Planned:"2011-02-07", description:"This is to gather functional requirements for Import Field Exams", name:"286217: WAAM 2 Import Field Exams Functional Requirements", output_type:"Key Deliverable", planned_Costs:"0.033", status:"Completed - Closed", `UNIQUE IMPORT ID`:133});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"81 days", Actual_start_delay:"0 days", Id:"9323", No_Child_Activity:"1", Planned_Duration:"55 days", Start_Date_Planned:"2011-07-07", description:"This is to gather non functional and user interface requirements for Field Exams.", name:"286217: WAAM 2 Import Field Exams Non Functional and User Interface Requirements", output_type:"Key Deliverable", planned_Costs:"0.045", status:"Completed - Closed", `UNIQUE IMPORT ID`:134});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"103 days", Actual_start_delay:"0 days", Id:"9324", No_Child_Activity:"1", Planned_Duration:"103 days", Start_Date_Planned:"2011-06-15", description:"This produced a design for WAAM that supports Import Field Exams functionality and also includes considerations for the Domestic Field Exams.", name:"286217: WAAM 2 Import Field Exams Design", output_type:"Key Deliverable", planned_Costs:"0.091", status:"Completed - Closed", `UNIQUE IMPORT ID`:135});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"140 days", Actual_start_delay:"0 days", Id:"9325", No_Child_Activity:"1", Planned_Duration:"140 days", Start_Date_Planned:"2011-05-09", description:"This produced code to realize Import Field Exam functionality.", name:"286217: WAAM 2 Import Field Exams Development", output_type:"Usable Functionality", planned_Costs:"0.121", status:"Completed - Closed", `UNIQUE IMPORT ID`:136});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"42 days", Actual_start_delay:"0 days", Id:"9326", No_Child_Activity:"1", Planned_Duration:"42 days", Start_Date_Planned:"2011-08-15", description:"This is for conducting unit and regression testing for Import Field Exam functionality.", name:"286217: WAAM 2 Import Field Exams Test", output_type:"Usable Functionality", planned_Costs:"0.037", status:"Completed - Closed", `UNIQUE IMPORT ID`:137});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"167 days", Actual_start_delay:"0 days", Id:"9329", No_Child_Activity:"1", Planned_Duration:"167 days", Start_Date_Planned:"2011-01-13", 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.", name:"286217: WAAM 2 Work Planner Business Requirements", output_type:"Key Deliverable", planned_Costs:"0.051", status:"Completed - Closed", `UNIQUE IMPORT ID`:138});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"41 days", Actual_start_delay:"0 days", Id:"9330", No_Child_Activity:"1", Planned_Duration:"41 days", Start_Date_Planned:"2011-07-01", description:"This is to gather requirements for building Work Planner.", name:"286217: WAAM 2 Work Planner Functional, Non Functional, and User Interface Requirements", output_type:"Key Deliverable", planned_Costs:"0.036", status:"Completed - Closed", `UNIQUE IMPORT ID`:139});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"164 days", Actual_start_delay:"0 days", Id:"9369", No_Child_Activity:"1", Planned_Duration:"164 days", Start_Date_Planned:"2010-10-25", 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.", name:"287489: LIMS Proof of Concept Phase 3", output_type:"Key Deliverable", planned_Costs:"0.05", status:"Completed - Closed", `UNIQUE IMPORT ID`:140});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"175 days", Actual_start_delay:"0 days", Id:"9370", No_Child_Activity:"1", Planned_Duration:"175 days", Start_Date_Planned:"2011-04-08", description:"Phase 4 expands the proof of concept to two additional labs to gather user feedback and test the effectiveness of the implementation.", name:"287489: LIMS Proof of Concept Phase 4", output_type:"Usable Functionality", planned_Costs:"0.055", status:"Completed - Closed", `UNIQUE IMPORT ID`:141});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"169 days", Actual_start_delay:"0 days", Id:"9383", No_Child_Activity:"1", Planned_Duration:"169 days", Start_Date_Planned:"2010-10-13", description:"Requirements and Preliminary Design for Common Login.", name:"287496: eLEXNET Common Login 1", output_type:"Key Deliverable", planned_Costs:"0.097", status:"Completed - Closed", `UNIQUE IMPORT ID`:142});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"179 days", Actual_start_delay:"0 days", Id:"9384", No_Child_Activity:"1", Planned_Duration:"179 days", Start_Date_Planned:"2011-04-01", description:"Design and Development for Common Login.", name:"287496: eLEXNET Common Login 2", output_type:"Usable Functionality", planned_Costs:"0.061", status:"Completed - Closed", `UNIQUE IMPORT ID`:143});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"94 days", Actual_start_delay:"0 days", Id:"9385", No_Child_Activity:"1", Planned_Duration:"105 days", Start_Date_Planned:"2011-09-28", description:"Test and Implementation for Common Login.", name:"287496: eLEXNET Common Login 3", output_type:"Usable Functionality", planned_Costs:"0.077", status:"Completed - Costs Pending", `UNIQUE IMPORT ID`:144});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"157 days", Actual_start_delay:"0 days", Id:"9386", No_Child_Activity:"1", Planned_Duration:"157 days", Start_Date_Planned:"2011-02-14", 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. ", name:"287496: eLEXNET Interagency Database for Dioxin", output_type:"Usable Functionality", planned_Costs:"0.191", status:"Completed - Closed", `UNIQUE IMPORT ID`:145});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"162 days", Actual_start_delay:"0 days", Id:"9388", No_Child_Activity:"1", Planned_Duration:"162 days", Start_Date_Planned:"2010-07-22", 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.", name:"287496: eLEXNET Outreach 1", output_type:"Key Deliverable", planned_Costs:"0.084", status:"Completed - Closed", `UNIQUE IMPORT ID`:146});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"119 days", Actual_start_delay:"0 days", Id:"9389", No_Child_Activity:"1", Planned_Duration:"119 days", Start_Date_Planned:"2011-01-01", description:"Outreach to stakeholder groups with an emphasis on government labs and state lab follow up outreach.", name:"287496: eLEXNET Outreach 2", output_type:"Key Deliverable", planned_Costs:"0.064", status:"Completed - Closed", `UNIQUE IMPORT ID`:147});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"85 days", Actual_start_delay:"0 days", Id:"9390", No_Child_Activity:"1", Planned_Duration:"85 days", Start_Date_Planned:"2011-05-01", description:"Outreach to stakeholder groups with an emphasis on private labs and government and state lab follow up outreach.", name:"287496: eLEXNET Outreach 3", output_type:"Key Deliverable", planned_Costs:"0.049", status:"Completed - Closed", `UNIQUE IMPORT ID`:148});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"103 days", Actual_start_delay:"0 days", Id:"9392", No_Child_Activity:"1", Planned_Duration:"103 days", Start_Date_Planned:"2010-11-17", description:"Requirements and Design for the Methods Module.", name:"287496: eLEXNET Methods Module 1", output_type:"Key Deliverable", planned_Costs:"0.232", status:"Completed - Closed", `UNIQUE IMPORT ID`:149});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"142 days", Actual_start_delay:"0 days", Id:"9393", No_Child_Activity:"1", Planned_Duration:"142 days", Start_Date_Planned:"2011-03-01", description:"Development, Test, and Implemenation of the Methods Module.", name:"287496: eLEXNET Methods Module 2", output_type:"Usable Functionality", planned_Costs:"0.371", status:"Completed - Closed", `UNIQUE IMPORT ID`:150});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"158 days", Actual_start_delay:"0 days", Id:"9395", No_Child_Activity:"1", Planned_Duration:"158 days", Start_Date_Planned:"2010-11-01", description:"Develop make available supporting customized data transfer for new labs.", name:"287496: eLEXNET Laboratory Expansion 1", output_type:"Usable Functionality", planned_Costs:"0.209", status:"Completed - Closed", `UNIQUE IMPORT ID`:151});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"101 days", Actual_start_delay:"0 days", Id:"9396", No_Child_Activity:"1", Planned_Duration:"101 days", Start_Date_Planned:"2011-04-11", description:"Develop make available supporting customized data transfer for new labs.", name:"287496: eLEXNET Laboratory Expansion 2", output_type:"Usable Functionality", planned_Costs:"0.209", status:"Completed - Closed", `UNIQUE IMPORT ID`:152});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"32 days", Actual_start_delay:"0 days", Id:"9402", No_Child_Activity:"1", Planned_Duration:"32 days", Start_Date_Planned:"2010-09-17", 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.", name:"287509: QMiS Release 1.0", output_type:"Usable Functionality", planned_Costs:"0.06", status:"Completed - Closed", `UNIQUE IMPORT ID`:153});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"34 days", Actual_start_delay:"0 days", Id:"9404", No_Child_Activity:"1", Planned_Duration:"34 days", Start_Date_Planned:"2010-09-17", 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.", name:"287509: QMiS Release 1.1.1", output_type:"Key Deliverable", planned_Costs:"0.052", status:"Completed - Closed", `UNIQUE IMPORT ID`:154});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"154 days", Actual_start_delay:"0 days", Id:"9405", No_Child_Activity:"1", Planned_Duration:"154 days", Start_Date_Planned:"2010-10-22", 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.", name:"287509: QMiS Release 1.1.2", output_type:"Usable Functionality", planned_Costs:"0.237", status:"Completed - Closed", `UNIQUE IMPORT ID`:155});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"125 days", Actual_start_delay:"0 days", Id:"9406", No_Child_Activity:"1", Planned_Duration:"125 days", Start_Date_Planned:"2011-03-28", 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.", name:"287509: QMiS Release 1.1.3", output_type:"Usable Functionality", planned_Costs:"0.174", status:"Completed - Closed", `UNIQUE IMPORT ID`:156});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"63 days", Actual_start_delay:"0 days", Id:"9408", No_Child_Activity:"1", Planned_Duration:"63 days", Start_Date_Planned:"2010-09-17", 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.", name:"287509: QMiS Training 1", output_type:"Key Deliverable", planned_Costs:"0.04", status:"Completed - Closed", `UNIQUE IMPORT ID`:157});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"144 days", Actual_start_delay:"0 days", Id:"9409", No_Child_Activity:"1", Planned_Duration:"144 days", Start_Date_Planned:"2010-11-01", description:"This includes training for OIM technical personnel for Release 1.1. This focuses on producing FDA in house technical expertise.", name:"287509: QMiS Training 2", output_type:"Key Deliverable", planned_Costs:"0.04", status:"Completed - Closed", `UNIQUE IMPORT ID`:158});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"109 days", Actual_start_delay:"0 days", Id:"9410", No_Child_Activity:"1", Planned_Duration:"109 days", Start_Date_Planned:"2011-01-10", description:"This includes training for end users for Release 1.1. This includes the development of training materials and courses for end users.", name:"287509: QMiS Training 3", output_type:"Key Deliverable", planned_Costs:"0.055", status:"Completed - Closed", `UNIQUE IMPORT ID`:159});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_start_delay:"0 days", Id:"9411", No_Child_Activity:"1", Planned_Duration:"73 days", Start_Date_Planned:"2011-06-14", description:"This includes training for end users for Release 1.1. This provides full training to end users.", name:"287509: QMiS Training 4", output_type:"Key Deliverable", planned_Costs:"0.128", status:"In-progress", `UNIQUE IMPORT ID`:160});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"60 days", Actual_start_delay:"0 days", Id:"12398", No_Child_Activity:"1", Planned_Duration:"60 days", Start_Date_Planned:"2011-08-26", 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. ", name:"286255: FDA ORA MARCS ARRMS 2 - Supplemental Startup Project Key Deliverables", output_type:"Key Deliverable", planned_Costs:"0.067", status:"Completed - Closed", `UNIQUE IMPORT ID`:161});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"95 days", Actual_start_delay:"0 days", Id:"12399", No_Child_Activity:"1", Planned_Duration:"95 days", Start_Date_Planned:"2011-09-19", 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).", name:"286255: FDA ORA MARCS ARRMS 2 - Supplemental Agile Iterations", output_type:"Usable Functionality", planned_Costs:"0.428", status:"Completed - Costs Pending", `UNIQUE IMPORT ID`:162});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_start_delay:"0 days", Id:"12400", No_Child_Activity:"1", Planned_Duration:"74 days", Start_Date_Planned:"2011-12-15", 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.", name:"286255: FDA ORA MARCS ARRMS 2 - Supplemental Test and Delivery", output_type:"Usable Functionality", planned_Costs:"0.193", status:"In-progress", `UNIQUE IMPORT ID`:163});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"166 days", Actual_start_delay:"0 days", Id:"12531", No_Child_Activity:"1", Planned_Duration:"166 days", Start_Date_Planned:"2011-07-18", 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.  ", name:"287623: RBIS CEI PREDICT Integration Phase 1 ", output_type:"Usable Functionality", planned_Costs:"0.145", status:"Completed - Closed", `UNIQUE IMPORT ID`:164});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"30 days", Actual_start_delay:"0 days", Id:"12532", No_Child_Activity:"1", Planned_Duration:"89 days", Start_Date_Planned:"2012-01-01", 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.", name:"287623: RBIS CEI PREDICT Integration Phase 2 PREDICT Acceptance", output_type:"Usable Functionality", planned_Costs:"0.015", status:"Completed - Closed", `UNIQUE IMPORT ID`:165});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"76 days", Actual_start_delay:"14 days", Id:"12533", No_Child_Activity:"1", Planned_Duration:"90 days", Start_Date_Planned:"2011-08-01", 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.", name:"287623: RBIS CEI DSS ", output_type:"Usable Functionality", planned_Costs:"0.062", status:"Completed - Closed", `UNIQUE IMPORT ID`:166});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"178 days", Actual_start_delay:"-98 days", Id:"12534", No_Child_Activity:"1", Planned_Duration:"80 days", Start_Date_Planned:"2012-03-12", description:"This task provides for implementation of prioritized change requests for the Center Views application after SRA completes the transition to the RBIS team.", name:"287623: RBIS CEI CV Enhancements", output_type:"Usable Functionality", planned_Costs:"0.094", status:"Completed - Closed", `UNIQUE IMPORT ID`:167});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"212 days", Actual_start_delay:"0 days", Id:"12535", No_Child_Activity:"1", Planned_Duration:"150 days", Start_Date_Planned:"2011-11-01", description:"This task covers MARCS 1.0 Integration activities, such as Informatica work, that extends beyond making the data available within RBIS itself.", name:"287623: RBIS CEI MARCS 1.0 Integration", output_type:"Usable Functionality", planned_Costs:"0.111", status:"Completed - Closed", `UNIQUE IMPORT ID`:168});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"108 days", Actual_start_delay:"-3 days", Id:"12536", No_Child_Activity:"1", Planned_Duration:"42 days", Start_Date_Planned:"2011-07-18", 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.", name:"287707: RBIS DWDMU PREDICT Data Mart", output_type:"Usable Functionality", planned_Costs:"0.068", status:"Completed - Closed", `UNIQUE IMPORT ID`:169});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"136 days", Actual_start_delay:"0 days", Id:"12538", No_Child_Activity:"1", Planned_Duration:"136 days", Start_Date_Planned:"2011-08-17", 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.", name:"287708: RBIS FMLS Enhancements Registration Integration Requirements and Design ", output_type:"Usable Functionality", planned_Costs:"0.146", status:"Completed - Closed", `UNIQUE IMPORT ID`:170});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_start_delay:"0 days", Id:"12539", No_Child_Activity:"1", Planned_Duration:"150 days", Start_Date_Planned:"2012-01-01", 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.", name:"287708: RBIS FMLS Enhancements Registration Integration Development, Test, and Implementation ", output_type:"Usable Functionality", planned_Costs:"0.127", status:"In-progress", `UNIQUE IMPORT ID`:171});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"105 days", Actual_start_delay:"0 days", Id:"12540", No_Child_Activity:"1", Planned_Duration:"105 days", Start_Date_Planned:"2011-08-17", 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.", name:"287708: RBIS FMLS Enhancements D&B Real Time Integration ", output_type:"Usable Functionality", planned_Costs:"0.019", status:"Completed - Closed", `UNIQUE IMPORT ID`:172});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"75 days", Actual_start_delay:"0 days", Id:"12541", No_Child_Activity:"1", Planned_Duration:"75 days", Start_Date_Planned:"2011-08-17", description:"Identify requirement gaps between Center Views and MARCS 0.5 release.", name:"287708: RBIS FMLS Enhancements Center Views-MARCS 0.5 Requirements ", output_type:"Usable Functionality", planned_Costs:"0.015", status:"Completed - Closed", `UNIQUE IMPORT ID`:173});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"75 days", Actual_start_delay:"2 days", Id:"12542", No_Child_Activity:"1", Planned_Duration:"77 days", Start_Date_Planned:"2011-08-15", description:"Identify a new geospatial mapping capability to integrate into ORADSS.", name:"287708: RBIS FMLS Enhancements Mapping Capability Requirements ", output_type:"Usable Functionality", planned_Costs:"0.009", status:"Completed - Closed", `UNIQUE IMPORT ID`:174});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_start_delay:"0 days", Id:"12543", No_Child_Activity:"1", Planned_Duration:"181 days", Start_Date_Planned:"2011-09-12", 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.", name:"287709: RBIS RDS Deski to Webi", output_type:"Usable Functionality", planned_Costs:"0.393", status:"In-progress", `UNIQUE IMPORT ID`:175});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"181 days", Actual_start_delay:"0 days", Id:"12545", No_Child_Activity:"1", Planned_Duration:"181 days", Start_Date_Planned:"2011-09-12", description:"This task implements report enhancements to existing data marts based on prioritized change requests during FY12H1.", name:"287709: RBIS RDS Monthly ORADSS Release FY12H1", output_type:"Usable Functionality", planned_Costs:"0.211", status:"Completed - Closed", `UNIQUE IMPORT ID`:176});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_start_delay:"0 days", Id:"12546", No_Child_Activity:"1", Planned_Duration:"183 days", Start_Date_Planned:"2012-03-12", description:"This task implements report enhancements to existing data marts based on prioritized change requests during FY12H2.", name:"287709: RBIS RDS Monthly ORADSS Release FY12H2", output_type:"Usable Functionality", planned_Costs:"0.185", status:"In-progress", `UNIQUE IMPORT ID`:177});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"110 days", Actual_start_delay:"0 days", Id:"12547", No_Child_Activity:"1", Planned_Duration:"141 days", Start_Date_Planned:"2011-09-12", description:"Enhance Table reports based on DPEM requirements.", name:"287709: RBIS RDS DPEM Enhancements", output_type:"Usable Functionality", planned_Costs:"0.031", status:"Completed - Closed", `UNIQUE IMPORT ID`:178});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"74 days", Actual_start_delay:"111 days", Id:"12549", No_Child_Activity:"1", Planned_Duration:"181 days", Start_Date_Planned:"2011-09-12", 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.", name:"287709: RBIS RDS FY12H1", output_type:"Usable Functionality", planned_Costs:"0.12", status:"Completed - Closed", `UNIQUE IMPORT ID`:179});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_start_delay:"0 days", Id:"12550", No_Child_Activity:"1", Planned_Duration:"183 days", Start_Date_Planned:"2012-03-12", 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. ", name:"287709: RBIS RDS FY12H2", output_type:"Usable Functionality", planned_Costs:"1.145", status:"In-progress", `UNIQUE IMPORT ID`:180});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"110 days", Actual_start_delay:"0 days", Id:"12551", No_Child_Activity:"1", Planned_Duration:"110 days", Start_Date_Planned:"2011-09-12", 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. ", name:"287710: RBIS Data Evaluation Vendor Selection ", output_type:"Usable Functionality", planned_Costs:"0.029", status:"Completed - Closed", `UNIQUE IMPORT ID`:181});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"120 days", Actual_start_delay:"0 days", Id:"12552", No_Child_Activity:"1", Planned_Duration:"120 days", Start_Date_Planned:"2012-01-01", 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.", name:"287710: RBIS Data Evaluation and Recommendations", output_type:"Usable Functionality", planned_Costs:"0.246", status:"Completed - Closed", `UNIQUE IMPORT ID`:182});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"100 days", Actual_start_delay:"54 days", Id:"9276", No_Child_Activity:"1", Planned_Duration:"154 days", Start_Date_Planned:"2011-05-27", description:"This produced a final design for Entry Query functionality within EM.", name:"286212: EM Final Design", output_type:"Key Deliverable", planned_Costs:"0.212", status:"Completed - Closed", `UNIQUE IMPORT ID`:183});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_start_delay:"49 days", Id:"9277", No_Child_Activity:"1", Planned_Duration:"143 days", Start_Date_Planned:"2011-06-14", 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.", name:"286212: EM Development", output_type:"Usable Functionality", planned_Costs:"0.538", status:"In-progress", `UNIQUE IMPORT ID`:184});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_start_delay:"77 days", Id:"9278", No_Child_Activity:"1", Planned_Duration:"144 days", Start_Date_Planned:"2011-06-27", description:"This will conduct unit and regression testing on some of the Entry Query functionality.", name:"286212: EM Test", output_type:"Usable Functionality", planned_Costs:"0.251", status:"In-progress", `UNIQUE IMPORT ID`:185});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"183 days", Actual_start_delay:"0 days", Id:"9279", No_Child_Activity:"1", Planned_Duration:"183 days", Start_Date_Planned:"2011-03-01", 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.", name:"286212: EM Field Exam and Sample Collection Requirements", output_type:"Key Deliverable", planned_Costs:"0.255", status:"Completed - Closed", `UNIQUE IMPORT ID`:186});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"105 days", Actual_start_delay:"0 days", Id:"9282", No_Child_Activity:"1", Planned_Duration:"100 days", Start_Date_Planned:"2010-09-29", description:"This is focused on improving the ETL that is currently in place.  This will provide faster and more reliable data transfer.", name:"286215: PREDICT ETL for Control Agents and Database Connections", output_type:"Usable Functionality", planned_Costs:"0.19", status:"Completed - Closed", `UNIQUE IMPORT ID`:187});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"158 days", Actual_start_delay:"0 days", Id:"9283", No_Child_Activity:"1", Planned_Duration:"158 days", Start_Date_Planned:"2011-02-14", description:"This is focused on improving the ETL that is currently in place.  This will provide faster and more reliable data transfer.", name:"286215: PREDICT ETL for Test and Documentation", output_type:"Usable Functionality", planned_Costs:"0.075", status:"Completed - Closed", `UNIQUE IMPORT ID`:188});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"157 days", Actual_start_delay:"0 days", Id:"9285", No_Child_Activity:"1", Planned_Duration:"144 days", Start_Date_Planned:"2011-01-10", 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.", name:"286215: PREDICT DnB Requirements and Design", output_type:"Usable Functionality", planned_Costs:"0.175", status:"Completed - Closed", `UNIQUE IMPORT ID`:189});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"146 days", Actual_start_delay:"0 days", Id:"9286", No_Child_Activity:"1", Planned_Duration:"146 days", Start_Date_Planned:"2011-03-25", 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.", name:"286215: PREDICT DnB Development and Test", output_type:"Usable Functionality", planned_Costs:"0.045", status:"Completed - Closed", `UNIQUE IMPORT ID`:190});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"153 days", Actual_start_delay:"0 days", Id:"9287", No_Child_Activity:"1", Planned_Duration:"153 days", Start_Date_Planned:"2011-04-28", 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.", name:"286215: PREDICT Rules Studio", output_type:"Key Deliverable", planned_Costs:"0.192", status:"Completed - Closed", `UNIQUE IMPORT ID`:191});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"140 days", Actual_start_delay:"0 days", Id:"9290", No_Child_Activity:"1", Planned_Duration:"140 days", Start_Date_Planned:"2010-09-27", description:"This gathered requirements for DGS functionality for MARCS.", name:"286216: DGS Requirements for DGS", output_type:"Key Deliverable", planned_Costs:"0.253", status:"Completed - Closed", `UNIQUE IMPORT ID`:192});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"60 days", Actual_start_delay:"0 days", Id:"9291", No_Child_Activity:"1", Planned_Duration:"60 days", Start_Date_Planned:"2011-06-06", description:"This gathered requirements for integration with Automated Laboratory Management (ALM) Quality Management Information System (QMiS)", name:"286216: DGS Requirements for Integration with QMiS", output_type:"Key Deliverable", planned_Costs:"0.06", status:"Completed - Closed", `UNIQUE IMPORT ID`:193});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"139 days", Actual_start_delay:"0 days", Id:"9292", No_Child_Activity:"1", Planned_Duration:"139 days", Start_Date_Planned:"2010-10-20", description:"An industry survey and analysis of COTS products was conducted.  This resulted in a recommended product to implement the functionality envisioned for DGS.", name:"286216: DGS Decision Analysis", output_type:"Key Deliverable", planned_Costs:"0.135", status:"Completed - Closed", `UNIQUE IMPORT ID`:194});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"87 days", Actual_start_delay:"0 days", Id:"9294", No_Child_Activity:"1", Planned_Duration:"87 days", Start_Date_Planned:"2011-01-31", description:"This produced a preliminary design for DGS.", name:"286216: DGS Preliminary Design", output_type:"Key Deliverable", planned_Costs:"0.288", status:"Completed - Closed", `UNIQUE IMPORT ID`:195});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"110 days", Actual_start_delay:"0 days", Id:"9295", No_Child_Activity:"1", Planned_Duration:"110 days", Start_Date_Planned:"2011-04-29", description:"This produced a final design for DGS.", name:"286216: DGS Final Design", output_type:"Key Deliverable", planned_Costs:"0.123", status:"Completed - Closed", `UNIQUE IMPORT ID`:196});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"189 days", Actual_start_delay:"0 days", Id:"9296", No_Child_Activity:"1", Planned_Duration:"129 days", Start_Date_Planned:"2011-04-22", description:"This is producing code that realizes the DGS functionality using a COTS and some custom code.", name:"286216: DGS Development", output_type:"Usable Functionality", planned_Costs:"0.357", status:"Completed - Closed", `UNIQUE IMPORT ID`:197});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"168 days", Actual_start_delay:"0 days", Id:"9297", No_Child_Activity:"1", Planned_Duration:"124 days", Start_Date_Planned:"2011-05-25", description:"This is for conducting unit and regression testing on DGS functionality.", name:"286216: DGS Test ", output_type:"Usable Functionality", planned_Costs:"0.078", status:"Completed - Closed", `UNIQUE IMPORT ID`:198});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"49 days", Actual_start_delay:"0 days", Id:"9300", No_Child_Activity:"1", Planned_Duration:"49 days", Start_Date_Planned:"2010-09-27", 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.", name:"286217: WAAM 2 RAC Requirements Validation", output_type:"Key Deliverable", planned_Costs:"0.081", status:"Completed - Closed", `UNIQUE IMPORT ID`:199});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"149 days", Actual_start_delay:"0 days", Id:"9302", No_Child_Activity:"1", Planned_Duration:"149 days", Start_Date_Planned:"2010-11-02", 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.", name:"286217: WAAM 2 RAC Design for User Interface and Logical", output_type:"Key Deliverable", planned_Costs:"0.101", status:"Completed - Closed", `UNIQUE IMPORT ID`:200});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"68 days", Actual_start_delay:"0 days", Id:"9303", No_Child_Activity:"1", Planned_Duration:"68 days", Start_Date_Planned:"2011-03-04", 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.", name:"286217: WAAM 2 RAC Design for Services Specifications", output_type:"Key Deliverable", planned_Costs:"0.048", status:"Completed - Closed", `UNIQUE IMPORT ID`:201});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"28 days", Actual_start_delay:"0 days", Id:"9304", No_Child_Activity:"1", Planned_Duration:"28 days", Start_Date_Planned:"2011-05-11", 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.", name:"286217: WAAM 2 RAC Design for Physical Data, Security, Interface, and Data Synchronization", output_type:"Key Deliverable", planned_Costs:"0.062", status:"Completed - Closed", `UNIQUE IMPORT ID`:202});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"247 days", Actual_start_delay:"0 days", Id:"9306", No_Child_Activity:"1", Planned_Duration:"162 days", Start_Date_Planned:"2010-11-02", 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)", name:"286217: WAAM 2 RAC Development and Support for FWM and eSAF", output_type:"Usable Functionality", planned_Costs:"0.208", status:"Completed - Closed", `UNIQUE IMPORT ID`:203});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"179 days", Actual_start_delay:"0 days", Id:"9307", No_Child_Activity:"1", Planned_Duration:"113 days", Start_Date_Planned:"2011-03-31", description:"This produced code to realize RAC functionality that will support work flows realized in the legacy Recall Enterprise System (RES).", name:"286217: WAAM 2 RAC Development and Support for RES", output_type:"Usable Functionality", planned_Costs:"0.127", status:"Completed - Closed", `UNIQUE IMPORT ID`:204});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"229 days", Actual_start_delay:"0 days", Id:"9308", No_Child_Activity:"1", Planned_Duration:"172 days", Start_Date_Planned:"2011-02-09", description:"This is for conducting unit and regression testing for RAC functionality. ", name:"286217: WAAM 2 RAC Test", output_type:"Usable Functionality", planned_Costs:"0.145", status:"Completed - Closed", `UNIQUE IMPORT ID`:205});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"147 days", Actual_start_delay:"0 days", Id:"9310", No_Child_Activity:"1", Planned_Duration:"147 days", Start_Date_Planned:"2010-10-13", 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.", name:"286217: WAAM 2 Inspections Requirements", output_type:"Key Deliverable", planned_Costs:"0.165", status:"Completed - Closed", `UNIQUE IMPORT ID`:206});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"179 days", Actual_start_delay:"0 days", Id:"9312", No_Child_Activity:"1", Planned_Duration:"179 days", Start_Date_Planned:"2011-02-18", 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.", name:"286217: WAAM 2 Inspections Design for User Interface and Logical", output_type:"Key Deliverable", planned_Costs:"0.102", status:"Completed - Closed", `UNIQUE IMPORT ID`:207});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"161 days", Actual_start_delay:"0 days", Id:"9313", No_Child_Activity:"1", Planned_Duration:"141 days", Start_Date_Planned:"2011-04-18", 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.", name:"286217: WAAM 2 Inspections Design for Services Specifications", output_type:"Key Deliverable", planned_Costs:"0.033", status:"Completed - Closed", `UNIQUE IMPORT ID`:208});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"33 days", Actual_start_delay:"0 days", Id:"9314", No_Child_Activity:"1", Planned_Duration:"20 days", Start_Date_Planned:"2011-08-24", 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.", name:"286217: WAAM 2 Inspections Design for Physical Data, Security, Interfaces, and Data Synchronization", output_type:"Key Deliverable", planned_Costs:"0.069", status:"Completed - Closed", `UNIQUE IMPORT ID`:209});
CREATE (:Activity:`UNIQUE IMPORT LABEL` {Actual_duration:"182 days", Actual_start_delay:"0 days", Id:"9316", No_Child_Activity:"1", Planned_Duration:"153 days", Start_Date_Planned:"2010-11-02", 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.", name:"286217: WAAM 2 Inspections Development Iterations 1 and 2", output_type:"Usable Functionality", planned_Costs:"0.167", status:"Completed - Closed", `UNIQUE IMPORT ID`:210});
CREATE (:Investment:`UNIQUE IMPORT LABEL` {Business_Case:"299", Changes_to_Baseline:"6.0", Enhancement_spend_$m:12.555, Evaluation_by_CIO:"4", Identifier:"009-000005318", Investment_type:"Major", Last_Baseline:"2012-02-23", 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.", 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.", name:"FDA ORA Automated Laboratory Management", `UNIQUE IMPORT ID`:220});
CREATE (:Investment:`UNIQUE IMPORT LABEL` {Business_Case:"310", Changes_to_Baseline:"5.0", Enhancement_spend_$m:20.181, Evaluation_by_CIO:"4", Identifier:"009-000005317", Investment_type:"Major", Last_Baseline:"2012-02-22", 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.", 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.", name:"FDA ORA Mission Accomplishments and Regulatory Compliance Services", `UNIQUE IMPORT ID`:221});
CREATE (:Investment:`UNIQUE IMPORT LABEL` {Business_Case:"318", Changes_to_Baseline:"7.0", Enhancement_spend_$m:6.211, Evaluation_by_CIO:"4", Identifier:"009-000005316", Investment_type:"Major", Last_Baseline:"2012-02-23", 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.", 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.", name:"FDA ORA Regulatory Business Information Services", `UNIQUE IMPORT ID`:222});
CREATE (:Investment:`UNIQUE IMPORT LABEL` {Changes_to_Baseline:"4.0", Enhancement_spend_$m:2.961, Evaluation_by_CIO:"3", Identifier:"009-000005315", Investment_type:"Major", 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.", `UNIQUE IMPORT ID`:223});
CREATE (:Investment:`UNIQUE IMPORT LABEL` {Changes_to_Baseline:"7.0", Enhancement_spend_$m:2.296, Evaluation_by_CIO:"4", Identifier:"009-000005323", Investment_type:"Major", 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.", `UNIQUE IMPORT ID`:224});
CREATE (:Investment:`UNIQUE IMPORT LABEL` {Changes_to_Baseline:"7.0", Enhancement_spend_$m:10.206, Evaluation_by_CIO:"3", Identifier:"009-000005345", Investment_type:"Major", 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.", `UNIQUE IMPORT ID`:225});
CREATE (:Investment:`UNIQUE IMPORT LABEL` {Changes_to_Baseline:"3.0", Enhancement_spend_$m:9.668, Evaluation_by_CIO:"3", Identifier:"009-000005354", Investment_type:"Major", 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.", `UNIQUE IMPORT ID`:226});
CREATE (:Investment:`UNIQUE IMPORT LABEL` {Changes_to_Baseline:"2.0", Enhancement_spend_$m:0, Evaluation_by_CIO:"4", Identifier:"009-000006267", Investment_type:"Major", 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.", `UNIQUE IMPORT ID`:227});
CREATE (:Business_Function:`UNIQUE IMPORT LABEL` {name:"404-Information and Technology Management", `UNIQUE IMPORT ID`:228});
CREATE (:Business_Function:`UNIQUE IMPORT LABEL` {name:"110-Health", `UNIQUE IMPORT ID`:229});
CREATE (:Business_Function:`UNIQUE IMPORT LABEL` {name:"402-Financial Management", `UNIQUE IMPORT ID`:230});
CREATE (:Business_Function:`UNIQUE IMPORT LABEL` {name:"109-General Science and Innovation", `UNIQUE IMPORT ID`:231});
CREATE (:Contract:`UNIQUE IMPORT LABEL` {Contract_size:"210.67890099999997", Description:"EDS TO#3, CONTRACTOR OWNED, CONTRACTOR OPERATED HOSTED DATA CENTER", ID:"21386", `UNIQUE IMPORT ID`:240});
CREATE (:Contract:`UNIQUE IMPORT LABEL` {Contract_size:"5.94745", Description:"ARRA::YES::ARRA TAS::75 1701::TAS  ARRAOS- SERVICES TO CONVERT LEGACY DATA TO STANDARDIZED FORMATS", ID:"21388", `UNIQUE IMPORT ID`:241});
CREATE (:Contract:`UNIQUE IMPORT LABEL` {Contract_size:"0.180539", Description:"TAS::75 0600::TAS   MODERN ANALYTICAL TOOLS SECURITY", ID:"21389", `UNIQUE IMPORT ID`:242});
CREATE (:Contract:`UNIQUE IMPORT LABEL` {Contract_size:"0.348408", Description:"TAS::75 0600::TASCSC-CDER AUTOMATION-EDR TO JANUS (TASK ORDER  XX UNDER ELMS CONTRACT)", ID:"21391", `UNIQUE IMPORT ID`:243});
CREATE (:Contract:`UNIQUE IMPORT LABEL` {Contract_size:"26.740875", Description:"WHITE OAK DATA CENTER EQUIPMENT", ID:"21428", `UNIQUE IMPORT ID`:244});
CREATE (:Contract:`UNIQUE IMPORT LABEL` {Contract_size:"39.523449", Description:"BUCCANEER AWARD OF TASK ORDER 2", ID:"21429", `UNIQUE IMPORT ID`:245});
CREATE (:Contract:`UNIQUE IMPORT LABEL` {Contract_size:"20.969576999999997", Description:"FDA EMAIL - TASK ORDER UNDER ICT21 CONTRACT", ID:"21430", `UNIQUE IMPORT ID`:246});
CREATE (:Contract:`UNIQUE IMPORT LABEL` {Contract_size:"36.425145", Description:"AWARD OF CUSTOMER SUPPORT SERVICES (CSS) TASK ORDER", ID:"21431", `UNIQUE IMPORT ID`:247});
CREATE (:Contract:`UNIQUE IMPORT LABEL` {Contract_size:"12.942542999999999", Description:"TAS::75 0600::TAS PC REFRESH BUY", ID:"21432", `UNIQUE IMPORT ID`:248});
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;
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:69}) CREATE (n1)-[r:uses_Supplier]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:69}) CREATE (n1)-[r:uses_Supplier]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:70}) CREATE (n1)-[r:uses_Supplier]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:71}) CREATE (n1)-[r:uses_Supplier]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:72}) CREATE (n1)-[r:uses_Supplier]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:73}) CREATE (n1)-[r:uses_Supplier]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:74}) CREATE (n1)-[r:uses_Supplier]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:75}) CREATE (n1)-[r:uses_Supplier]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:75}) CREATE (n1)-[r:uses_Supplier]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:74}) CREATE (n1)-[r:uses_Supplier]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:76}) CREATE (n1)-[r:uses_Supplier]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:138}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:139}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:89}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:90}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:91}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:92}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:93}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:94}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:95}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:223}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:87}) CREATE (n1)-[r:is_a_type_of]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:222}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:88}) CREATE (n1)-[r:is_a_type_of]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:84}) CREATE (n1)-[r:is_a_type_of]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:220}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:84}) CREATE (n1)-[r:is_a_type_of]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:224}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:82}) CREATE (n1)-[r:is_a_type_of]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:225}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:83}) CREATE (n1)-[r:is_a_type_of]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:86}) CREATE (n1)-[r:is_a_type_of]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:85}) CREATE (n1)-[r:is_a_type_of]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:199}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:200}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:201}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:202}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:203}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:204}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:205}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:206}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:207}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:208}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:209}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:210}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:130}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:131}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:132}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:133}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:134}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:135}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:136}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:137}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:11}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:96}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:0}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:97}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:0}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:98}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:0}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:99}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:0}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:140}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:0}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:141}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:1}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:142}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:1}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:143}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:12}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:77}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:12}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:78}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:13}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:79}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:13}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:100}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:13}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:101}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:13}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:102}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:13}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:103}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:13}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:104}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:13}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:105}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:3}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:106}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:3}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:107}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:3}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:108}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:3}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:109}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:3}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:110}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:3}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:111}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:3}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:112}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:3}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:113}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:3}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:114}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:3}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:115}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:3}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:116}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:3}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:120}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:4}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:121}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:5}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:122}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:5}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:123}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:5}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:124}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:5}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:125}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:5}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:126}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:6}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:127}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:6}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:128}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:6}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:129}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:6}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:183}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:6}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:184}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:6}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:185}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:6}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:186}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:7}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:187}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:7}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:188}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:1}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:144}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:7}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:189}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:7}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:190}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:7}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:191}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:8}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:192}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:8}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:193}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:8}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:194}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:8}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:195}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:8}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:196}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:1}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:145}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:1}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:146}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:8}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:197}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:1}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:147}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:1}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:148}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:1}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:149}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:8}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:198}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:1}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:150}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:1}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:151}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:1}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:152}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:2}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:153}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:2}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:154}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:2}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:155}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:2}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:156}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:2}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:157}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:2}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:158}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:2}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:159}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:2}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:160}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:10}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:161}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:10}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:162}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:10}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:163}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:12}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:164}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:12}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:165}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:12}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:166}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:12}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:167}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:12}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:168}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:13}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:169}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:14}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:170}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:14}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:171}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:14}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:172}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:14}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:173}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:14}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:174}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:15}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:175}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:15}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:176}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:15}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:177}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:15}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:178}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:15}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:179}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:15}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:180}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:16}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:181}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:16}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:182}) CREATE (n1)-[r:has_task]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:69}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:118}) CREATE (n1)-[r:delivers]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:69}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:119}) CREATE (n1)-[r:delivers]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:70}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:240}) CREATE (n1)-[r:delivers]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:71}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:241}) CREATE (n1)-[r:delivers]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:72}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:242}) CREATE (n1)-[r:delivers]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:73}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:243}) CREATE (n1)-[r:delivers]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:74}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:244}) CREATE (n1)-[r:delivers]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:75}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:245}) CREATE (n1)-[r:delivers]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:75}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:246}) CREATE (n1)-[r:delivers]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:74}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:247}) CREATE (n1)-[r:delivers]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:76}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:248}) CREATE (n1)-[r:delivers]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:225}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:47}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:225}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:48}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:225}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:49}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:225}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:50}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:225}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:51}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:225}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:52}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:220}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:53}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:223}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:229}) CREATE (n1)-[r:has_business_function]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:222}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:228}) CREATE (n1)-[r:has_business_function]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:229}) CREATE (n1)-[r:has_business_function]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:220}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:229}) CREATE (n1)-[r:has_business_function]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:224}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:230}) CREATE (n1)-[r:has_business_function]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:225}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:229}) CREATE (n1)-[r:has_business_function]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:231}) CREATE (n1)-[r:has_business_function]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:228}) CREATE (n1)-[r:has_business_function]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:118}) CREATE (n1)-[r:lets_contract]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:119}) CREATE (n1)-[r:lets_contract]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:240}) CREATE (n1)-[r:lets_contract]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:241}) CREATE (n1)-[r:lets_contract]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:242}) CREATE (n1)-[r:lets_contract]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:243}) CREATE (n1)-[r:lets_contract]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:244}) CREATE (n1)-[r:lets_contract]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:245}) CREATE (n1)-[r:lets_contract]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:246}) CREATE (n1)-[r:lets_contract]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:247}) CREATE (n1)-[r:lets_contract]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:248}) CREATE (n1)-[r:lets_contract]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:220}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:0}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:220}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:1}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:220}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:2}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:3}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:4}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:5}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:6}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:7}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:8}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:9}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:10}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:11}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:222}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:12}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:222}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:13}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:222}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:14}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:222}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:15}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:222}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:16}) CREATE (n1)-[r:pays_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:228}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:81}) CREATE (n1)-[r:serves]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:229}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:80}) CREATE (n1)-[r:serves]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:230}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:81}) CREATE (n1)-[r:serves]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:231}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:80}) CREATE (n1)-[r:serves]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:61}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:62}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:63}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:64}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:65}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:66}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:67}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:68}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:20}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:222}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:21}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:222}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:22}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:222}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:23}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:222}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:24}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:222}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:25}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:224}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:26}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:224}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:27}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:224}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:28}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:224}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:29}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:224}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:30}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:224}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:31}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:220}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:32}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:220}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:33}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:220}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:34}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:220}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:46}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:220}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:44}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:43}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:18}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:17}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:35}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:38}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:39}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:19}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:41}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:223}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:42}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:223}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:45}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:223}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:37}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:223}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:40}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:223}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:36}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:223}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:54}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:223}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:55}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:56}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:57}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:58}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:59}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:60}) CREATE (n1)-[r:judged_by]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:117}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:223}) CREATE (n1)-[r:responsible_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:117}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:222}) CREATE (n1)-[r:responsible_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:117}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:221}) CREATE (n1)-[r:responsible_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:117}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:220}) CREATE (n1)-[r:responsible_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:117}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:224}) CREATE (n1)-[r:responsible_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:117}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:225}) CREATE (n1)-[r:responsible_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:117}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:226}) CREATE (n1)-[r:responsible_for]->(n2);
MATCH (n1:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:117}), (n2:`UNIQUE IMPORT LABEL`{`UNIQUE IMPORT ID`:227}) CREATE (n1)-[r:responsible_for]->(n2);
MATCH (n:`UNIQUE IMPORT LABEL`)  WITH n LIMIT 20000 REMOVE n:`UNIQUE IMPORT LABEL` REMOVE n.`UNIQUE IMPORT ID`;
DROP CONSTRAINT ON (node:`UNIQUE IMPORT LABEL`) ASSERT (node.`UNIQUE IMPORT ID`) IS UNIQUE;