Moodle integration with Genius SIS - assertions and issues

My customer has been working with Genius SIS - which is a student administrative program that works with various LMS's, including moodle.

It is the front end for the account creation, courses, course sections, enrollments etc.  The idea is all account creation and enrollment for students taking moodle courses goes on in it.

My customer did not have a *complete understanding of how these things worked and related and this caused problems for us.  To his defense, he did ask for help from me and my colleague, which I was not willing to grant for other reasons, primarily because the system was his.  He choose it, he worked with it etc.  But, by not working with him on the Genius side, problems ensued.  Oye.

The following are assertions about how we are supposed to be using the product.

When a course is deployed in moodle - it must have its short name copy and pasted into the matching Genius Section name LMS ID.

Genius has courses, that are really just descriptions - the courses and their content live in moodle.  Genius has a name of a course and then has Sections of that course. 

Genius Sections MUST = a moodle course short name.
 Details of the section - including the ALL important LMS ID:

 Ensure that each Genius SECTION LMS ID is mapped to a deployed moodle course short name.

All student account creation is handled through Genius, excluding teachers, which is done in moodle.

Genius SIS facts:assertions

1. courses have sections
2. sections have LMS IDs
3. section LMS IDs match a moodle course shortname
4. enrollments are completed by choosing the student account - then the course section
5. the Report|Integration report in Genius is helpful for seeing if problems have occured with enrollments
6. New student accounts are created in Genius, not moodle
7. Moodle will create the student account when it reads from Genius
8. Moodle reads from Genius when a timed cron script is run
9. Enrollments appear in moodle courses as external DB
10. Accounts created in moodle have a authentication type of external DB
11. Accounts created in Genius must have a unique username and email
12. Enrollments in Genius must have a unique username and courseid
13. Students should log into Genius, not moodle
14. The Genius dashboard (home page) includes links to enrolled moodle courses
15. Signing into Genius and following a course link to moodle automatically signs the student into moodle
16. Updates to the student password via Genius propagate to moodle
17. Do not change the password in moodle - change it in Genius