The following information and attached report should be considered "ARRL Board Confidential". At the Board meeting last week, staff committed to distributing a copy of the IT Project status report updated for 12/31/14. Prior iterations of the report have been distributed to the A&F Committee. The report is attached and encompasses projects from both the 2014 and 2015 Plans. It requires some explanation. The report is segregated in 4 sections along the lines of the identified IT resources: 1. Table 1a - Web application and software development projects; 2. Table 1b - LoTW software development projects; 3. Table 1c - Infrastructure projects 4. Table 1d - Projects completed in Q3/Q4 2014 The report was prepared by Michael Keane, K1MK, ARRL IT Manager and includes comments from him at the beginning. In addition, on page 7 of the report, I have included a chart of the overview of the software system design process that is referred to in the Tables. This was part of a presentation that Michael made to the A&F Committee in April of last year. As you will see, each project has a Estimated Time to Complete (ETC). The overall accuracy of those estimates depends heavily on where the specific project is in its particular life cycle. Estimates for projects in the "Inception" stage are obviously going to be less precise than those in the Construction stage. As a general rule of thumb, the estimates can be categorized as: * Prior to Systems Requirements Review -- estimates are of rough order of magnitude accuracy * Following System Requirements Review -- estimates should be refined to a factor of two or better * Following Preliminary Design Review -- 30% accuracy * Following Critical Design Review -- 10% accuracy As discussed during the Board meeting, IT resources are routinely over committed as shown in particular in Table 1a where the projects show an estimated ETC total of 60.5 months in comparison to the available resources of 23 months. The allocation of LoTW and Infrastructure projects is more in line with the available resources. I should also point out that the project highlighted in the Board minutes at Minute 30 (nominally referred to as the Volunteer Instructor Database) is encompassed in the project titled "AIS Education Module". This was noted at the Board meeting but I wanted to note it again here. We will be setting up a meeting in the near future to begin the process of developing the specifications for this project. I'm sure you will have questions and we will be happy to answer them. 73, Barry J. Shelley, N1VXY Chief Financial Officer ARRL, Inc. The National Association for Amateur Radio (860) 594-0212 www.arrl.org