If your primary table fields are really called those names, you have field/object naming issues to start with. If table II fields would need to be added/deleted as business conditions change (e.g. you add another department or entity and you need another field) you have normalization issues as well. If your fields hold calculated data, that is a potential big issue as well.
So this is my opinion: Access is for data 'storage', retrieval and doing what you might call relational grouping or presentation. It does some 'low level' aggregate functions but it's not nearly as powerful as Excel for that, nor would I use Access for charting. Given all that, you might want to do a bit of research on database normalization and the use of reserved words for design purposes and try to avoid more issues like the one related to calling a field "Date". There is so much info on the first that I say Google it and find some that make sense to you and maybe even reflect your project. As for names: http://allenbrowne.com/AppIssueBadWord.html
Given all that, I think you'd have to provide a lot more info if you're looking for normalization advice. One suggestion would be to post here a copy of the Excel file so we can see what you've got, and a comprehensive explanation of what you are trying to achieve. One thing that often doesn't work well for this sort of situation is if you provide unrelated example info that has little bearing on the real situation. Suggestions are given in response to text examples, only to find out that the real situation involves numbers.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.