Schedule Level of Detail for Metrics and Task Management in Project

What is a best practice for achieving the proper level of detail in MS Project Schedules?

I work in a manufacturing environment, where most tasks are ultimately driven by product delivery dates, but with each product, there are multiple steps involving different trades and departments at each step. In a schedule, the lowest level of detail needs to have task dependencies and resources assigned, however, this is usually a Level 3 "middle ground" level of detail (not too broad and not too specific), representing a window of a few days or a few weeks in which a certain group of steps needs to be completed so we can move to the next stage in the process. Each of these steps/tasks often need to be broken down into daily (or sometimes portions of a day) for the actual assigning and managing of tasks in the organization. Each of these subtasks could have multiple people working on them at different points. Obviously, the dates for these detailed task management assignments should dynamically move as the schedule is updated, but including too much detail in MS Project schedules is problematic when trying to update progress, especially with multiple resources assigned to a short-duration task. It almost seems that you should be able to assign task dependencies and resources to tasks at a certain level, then you should be able to break those tasks down into subtasks for the day-to-day managment of tasks, but this will cause your scheduling metric tools to go haywire. 

Has anyone experienced this challenge and what did you do to be able to break down your schedule into task management-level detail while still maintaining a coherent schedule which people can understand, and which meets the industry-standard schedule metrics of task dependencies, resources, and critical path traceability?