List of Functional Requirements for Contracts module:

• 1. The contract module is user accessible and provides fields to record details pertaining to the collective bargaining agreement (or any other high level contract, such as Clubs IWA) or contract executed by each employer (i.e., stand-alone contract).
• 2. For each contract, the system carries all prior rates in addition to the current and known future rates, job classification, and benefits covered and waiting periods.
• 3. Contract data is not purged. The system maintains a complete historical record of all contract data.
• 4. Ability to scan contracts into the system – be able to retrieve copies of contracts from the system. Maintain an inventory of documents electronically. Make sure that side agreements that are scanned in are related to a specific Contract. Existing contract images are converted into the system during each data conversion build.
• 5. Provide (to the best of the system’s ability) reports that detect situations whereby an Employer is not in compliance with their contract.
• 6. Eligibility is tied into our Contracts database, which would contain, among other things, when specific benefits begin
• 7. Ability to maintain historical records regarding Schedule A Job classes and wage rates by Contract, as well as non-standard job classes and wage Rates.
• 8. Relate employers to contracts
• 9. Track payments received from employers each month via Consolidated Contribution Accounting Module and provisions of Contracts Module
• 10. While the majority of employers are subject to the same terms and conditions with regard to participation in the various Funds, the system provides the Funds the ability to maintain contracts having different provisions. Specifically, the agreements may vary and state that employer contributions are due to the Funds at different contribution rates, different effective dates and based on different units of work. Additionally, employers may have their own agreements with HTC or Local 6 regarding which of the benefit funds employers is obligated to contribute to. The system has the ability to provide the necessary calculations to verify that each employer is remitting contributions in accordance with the requirements of the CBA.
• 11. For each Contract, defining which of the 5 Funds is to have contributions remitted by the employers.
• 12. For each Contract, defining when contributions are to begin being remitted.
• 13. For each Contract, defining the contribution rates.
• 14. For each Employer, establishing which Contract they are to honor with respect to remitting contributions.
• 15. Replace old Craft Codes and Craft Names with new J-Codes and “real” Schedule A job titles.
• 16. Implement mapping of existing work records to new J-Codes and Schedule A job titles
• 17. Ability to assign each job an employment category with regards to the pension credit calculations – A (banquet waiters), B (checkroom/washroom attendants) and C (other).
• 18. Excis implemented default mapping of the Schedule A job titles to employment categories (A, B or C)
• 19. Ability to enter Opt-In/Opt-Out information for each benefit fund
• 20. Override employer contract provisions at the department level (e.g., enter different from other departments contribution rates)
• 21. During the conversion process, the system creates two actual (2006-2012) IWA and Clubs IWA high level contracts and two historical (2001-2006) IWA and Clubs IWA high level contracts. Based on the knowledge of which high level contract each employer is signatory to, the system also creates stand-alone contract for each employer. By default such stand-alone contract (with some exceptions for Clubs) inherits all the contract rules/provisions from the high level contract. Later on, all inherited contract rules/provision may be amended for the employer or some of its departments.