Need help with ERD problems

ERD The Intercollegiate Athletic database supports the customers, facilities, locations within facilities, employees, and resources to s approved, one or more event plans are made and the cleanup of an event. An event plan consists of one or more event plan lines EERD scheduling and the operation of events along with tracking support events. To schedule an omer initiates an event request with the Intercollegiate A thletic Department. If an event request . ypically, event plans are made for the setup, the operation, .For each event request, the database records the unique event number, the date held, the date requested, the date authorized, the status, an estimated cost, the estimated audience, the facility number (required), and the ustomer number (required) For each event plan, the database records the unique plan number, notes about the plan, the work date, the . activity (Getup, operation, or cleanup), the employee number (optional), and the event number (required) . For each event plan line, the database records the line number (unique within a plan number), the plan number (required), the starting time, the ending time, the resource number (required), the location number (required), and the quantity of resources required For cach customer, the database records the unique customer number, the name, the address, the contact name, the phone, the e-mail address, and the list of events requested by the customer. A customer is not stored in the database until submitting an event request. For each facility, the database records the unique facility number, the facility name, and the list of events in which the facility is requested For each employee, the database records the unique employee number, the name, the department name, the email address, the phone number, and the list of event plans supervised by the employee. . . For each location, the database records the related facility number, the location number (unique within a facit ity), the name, and the list of event plan lines in which the location is used. For each resource, the database records the unique resource number, the name, the . event plan lines in which the resource is needed. ERD The Intercollegiate Athletic database supports the customers, facilities, locations within facilities, employees, and resources to s approved, one or more event plans are made and the cleanup of an event. An event plan consists of one or more event plan lines EERD scheduling and the operation of events along with tracking support events. To schedule an omer initiates an event request with the Intercollegiate A thletic Department. If an event request . ypically, event plans are made for the setup, the operation, .For each event request, the database records the unique event number, the date held, the date requested, the date authorized, the status, an estimated cost, the estimated audience, the facility number (required), and the ustomer number (required) For each event plan, the database records the unique plan number, notes about the plan, the work date, the . activity (Getup, operation, or cleanup), the employee number (optional), and the event number (required) . For each event plan line, the database records the line number (unique within a plan number), the plan number (required), the starting time, the ending time, the resource number (required), the location number (required), and the quantity of resources required For cach customer, the database records the unique customer number, the name, the address, the contact name, the phone, the e-mail address, and the list of events requested by the customer. A customer is not stored in the database until submitting an event request. For each facility, the database records the unique facility number, the facility name, and the list of events in which the facility is requested For each employee, the database records the unique employee number, the name, the department name, the email address, the phone number, and the list of event plans supervised by the employee. . . For each location, the database records the related facility number, the location number (unique within a facit ity), the name, and the list of event plan lines in which the location is used. For each resource, the database records the unique resource number, the name, the . event plan lines in which the resource is needed