Download ITD Database Design Phase Report

ITD Database Design Phase Report
By:
Ron Parker
Software Creations
[email protected]
310.324.7032
310.324.9577 fax
ITD Database
Design Phase Report
1
5/14/17
Table of Contents
ITD Database Design Phase Report .................................................................................... 1
Table of Contents ............................................................................................................ 2
I. System Scope ............................................................................................................... 4
A. System Title ........................................................................................................ 4
B. Problem Statement and Purpose ......................................................................... 4
C. Constraints .......................................................................................................... 4
D. Specific Objectives ............................................................................................. 5
II. Conclusions and Recommendations........................................................................... 6
A. Conclusions ......................................................................................................... 6
B. Recommendations ............................................................................................... 6
III. Design Specification ................................................................................................. 7
A. External Design Requirement ............................................................................. 7
System Overview ........................................................................................................ 7
System Output Requirements ..................................................................................... 8
Systems Security and Software ........................................................................... 8
Instructional Technology Branch ...................................................................... 12
Technical Support Services............................................................................... 13
Telephone Systems Unit ................................................................................... 14
E-Rate / Planning Department .......................................................................... 16
System Input Requirements ...................................................................................... 18
Security ............................................................................................................. 19
System Interface Requirements ................................................................................ 19
Software Specifications and Requirements .............................................................. 19
Application Software ........................................................................................ 19
Database Engine................................................................................................ 20
MySQL ......................................................................................................... 20
Reporting Options ............................................................................................. 20
MS Access .................................................................................................... 20
Crystal Reports.............................................................................................. 20
MySQL Data Manager .................................................................................. 22
phpMyAdmin ................................................................................................ 22
DeZign for MySQL....................................................................................... 22
Equipment Specifications ......................................................................................... 23
B. Internal Design Requirement ............................................................................ 23
ITD Database Diagram ............................................................................................. 24
ITD Database Application Flowchart ....................................................................... 24
Main Menu ........................................................................................................ 24
Reporting........................................................................................................... 25
Systems Security and Software ......................................................................... 26
Telephone Systems Unit ................................................................................... 26
Technical Support Services............................................................................... 27
Instructional Technology Branch ...................................................................... 28
E-Rate / BB / Planning Dept. ............................................................................ 28
ITD Database
Design Phase Report
2
5/14/17
ITD Database Table Diagram ................................................................................... 29
ITD Database Table Layout ...................................................................................... 31
Administration .................................................................................................. 31
Administration Database ............................................................................... 31
Systems Security and Software ......................................................................... 32
Host Access Database ................................................................................... 32
Network Database ......................................................................................... 33
IP Database ................................................................................................... 36
Application Database .................................................................................... 37
Project Database............................................................................................ 37
Telephone Systems Unit - G288 ....................................................................... 38
Phone Systems Database............................................................................... 38
Circuit Database ............................................................................................ 38
Technical Support Services............................................................................... 39
Public Address / Intercom ............................................................................. 39
Alarm Database ............................................................................................. 40
MATV Database ........................................................................................... 40
Modular Classroom Database ....................................................................... 40
Instructional Technology Branch ...................................................................... 41
Grant Database .............................................................................................. 41
Technology Database .................................................................................... 41
Training Database ......................................................................................... 43
Planning Department / E-Rate Program ........................................................... 43
E-Rate / BB Database ................................................................................... 43
Proposition BB Database .............................................................................. 46
ITD Database Table Entity Relationship Diagrams .................................................. 46
Systems Security and Software ......................................................................... 46
Telephone Systems Unit ................................................................................... 47
Technical Support Services............................................................................... 47
Instructional Technology Branch ...................................................................... 48
E-Rate / BB / Planning Department .................................................................. 49
IV. Plans and Schedules ................................................................................................ 50
A. Major Milestones .............................................................................................. 50
ITD Database
Design Phase Report
3
5/14/17
I. System Scope
A. System Title
LAUSD Information Technology Division (ITD) Database.
B. Problem Statement and Purpose
The Los Angeles Unified School District Information Technology Division (ITD)
wishes to develop a database which will contain all ITD-related information for all
sites in the District.
Currently, much of the information ITD sections need to maintain on District
schools is either in a variety of incompatible database systems, individual
spreadsheets or not in electronic format at all. It is currently very difficult for ITD
administration to accurately access and assess the status of various ITD-related site
information, such as circuit, LDF or router data. In addition, it is difficult for ITD
staff who must perform technical support to access important ITD-related
information while out in the field.
The purpose of the new ITD Database is to provide a single source for all ITDrelated information on all sites in the District. It will be complete, unified and
accessible to all ITD staff, regardless of their location.
C. Constraints
The ITD Database Development Project constraints are:
1. The ITD Database needs to be developed in a manner which will make it
accessible to all ITD staff who need access to it.
2. Data creation and update within the database must be restricted to the ITD
sections responsible for producing the information. This means there must
be a password-protected system which will control specific users
create/update access to specific areas.
3. Some data elements have been defined while many have not.
4. The data elements come from several ITD sections. This will require some
sort of coordination for organization of data input responsibility.
5. Data should not be duplicated.
6. System should run in existing ITD computer environment.
7. Additional software and licensing costs for system should be minimal.
ITD Database
Design Phase Report
4
5/14/17
D. Specific Objectives
The specific ITD Database objectives:
1. Establish database which contains pertinent ITD-related information for all
sites in the Los Angeles Unified School District.
2. Database should be normalized as much as possible, and not contain data
duplicated elsewhere within ITD.
3. Database will contain the following information groups: School Grant Data,
E-Rate Status, T1 Circuit Data, Status of Administrative Connections, MDF,
IDF and LDF Locations, Public Address, Intercom, Phone Systems and
Analog Circuit Data.
4. Specific data elements for each information group will be defined, created
and maintained by the following ITD sections: Systems Security and
Software, Telephone Systems Unit, Technical Support Services, Planning
Department and Instructional Technology Branch.
5. Appropriate ITD staff will have access to database over a common interface.
6. Database will be password protected under a hierarchy that will permit only
the responsible ITD section staff to create/update/delete data elements that
his/her section is responsible for.
ITD Database
Design Phase Report
5
5/14/17
II. Conclusions and Recommendations
A. Conclusions
ITD is a very large and widespread organization. It is appropriate that the ITD
Database be designed to allow for access and update from multiple physical
locations as opposed to one.
The biggest problems encountered during the Study and Design Phases was the
ability to meet with the individuals from each responsible section in order to define
data elements in a timely manner.
B. Recommendations
It is recommended that the ITD Database Project move forward to the Development
Phase.
It is also recommended that:
1. A PC be made available for immediate development of the demonstration ITD
Database.
2. A procedure be established to mirror the LAUSD Site Database running on
the LAUSD DB2 mainframe system. This data will serve as the base for the
proposed ITD Database. This structure is defined in the “Internal Design
Requirement” section of this document.
3. ITD organize a committee to oversee the flow of database content and
determine desired output. As the ITD Database will allow for update from
multiple sources, it will be necessary to have a mechanism in place to both
organize the content as well as verify the validity and appropriateness of
content being added to the database. Also, there needs to be some sort of
approval mechanism for the final output specifications.
ITD Database
Design Phase Report
6
5/14/17
III. Design Specification
A. External Design Requirement
System Overview
A two-tiered system is proposed. That is, we are recommending a back-end database
with two front-ends. This will allow for the construction of two interfaces to the
database: A web-based interface and an MS Access interface. In addition, this
approach will provide for much more flexible reporting options (as listed in
“Reporting” section of “Software Specifications and Requirements” of this
document) as well as better security.
ITD Database
Design Phase Report
7
5/14/17
System Output Requirements
Output requirements are based upon actual reports or input screens generated by each
ITD section. In general, the output requirements should match the reporting
responsibilities for the data from the ITD sections involved. Examples of this output
for each section is listed below:
Systems Security and Software
T1 Installs
This report contains the following data elements:














TelCo
E-Rate Year
Complete
Admin Application
Elementary Report Card
IFS GUI
T610
Elem/T622
Sec/T520
Cafeteria
CDS Code
Location Code
ADN Circuit
Node
Note that in new ITD Database, all applications are defined in Application Table,
and assigned to specific sites in Application to Site Table. They are no longer
hard coded as fields in T1 Table.
ITD Database
Design Phase Report
8
5/14/17
LAUSD DS-1 Project Order Log
This report, consists of the following data elements:













ITEM – D3 Name + Channel Number
Location Code
School Name
Technician
T1 Circuit ID
Inter IP
Intra IP
ITD WAN IP
Site WAN IP
Node
Brand (Manufacturer) Name
Model
Model No.
ITD Database
Design Phase Report
9
5/14/17
3270 RISC6000 Detail Screen
Detail screen from current FileMaker database which contains District PCs that
access the District 3270 / RISC6000 mainframe systems.
ITD Database
Design Phase Report
10
5/14/17
Network Detail Screen
Detail screen from current FileMaker database which contains Network
information for sites throughout the District.
ITD Database
Design Phase Report
11
5/14/17
Instructional Technology Branch
Form 9
This is the current reporting requirement for ITB with respect to ITD related
information at sites throughout the District. Not viewed in image below is
additional field:

CDS Code
ITD Database
Design Phase Report
12
5/14/17
Technical Support Services
Technical Support Services Data Elements
Below are the data elements submitted by Pete Barale and Micheal O’Larte:
ITD Database
Design Phase Report
13
5/14/17
Telephone Systems Unit
Telephone Master Records Data Entry Screen
This comes from the mainframe phone billing system.
ITD Database
14
Design Phase Report
5/14/17
Phone Expense Report by Location
This is also generated by the mainframe phone billing system. It shows:





Location Code
Location Name
Phone
APPR Code
Expenses by month per phone for 12 months.
ITD Database
Design Phase Report
15
5/14/17
E-Rate / Planning Department
The following are examples of a Proposition BB data output requirement.
The following are examples of E-Rate data output requirements.
ITD Database
Design Phase Report
16
5/14/17
ITD Database
Design Phase Report
17
5/14/17
System Input Requirements
Only ITD staff will be able to input content to the ITD Database through a password
protected Staff Section. The specific requirements are listed in the “Internal Design
Requirement” section of this document, under “ITD Database Table Layout”.
ITD Database
Design Phase Report
18
5/14/17
ITD staff will only be able to input/update data for which his/her section is
responsible.
Security
Access to the ITD Database Application will be restricted to password protected
userids which will follow this level hierarchy:
00
Administrator
Super-users. These users can create/update/delete all records in the
database.
01
Section Administrator
These users can create/update/delete all records in their section
(i.e., Systems Security and Software, Telephone Systems Unit,
etc…). This includes the User Table.
02
Staff
These users can create/update/delete all records in their section
EXCEPT for User Table records.
System Interface Requirements
The interface will need to allow for all pertinent ITD staff, no matter their location, to
be able to access the database. With such a requirement, the most logical solution is
an Intranet, “Web-Based” (World Wide Web / Internet) interface for end-users to
access the ITD Database. The application should be run under any Netscape or
Internet Explorer browser above version 5. The extent to which the application is
accessible to end-users will be determined by ITD based upon its security concerns.
Software Specifications and Requirements
Application Software
The core ITD Database Application will be written in Java and utilize Java Servlet
and Java Server Pages (JSP) technology. The application will run under the
Windows NT or 2000 operating system and utilize Microsoft Internet Information
Service (IIS) as its web server.
ITD Database
Design Phase Report
19
5/14/17
Database Engine
MySQL
Today MySQL is the most popular open source database server in the world
with more than 2 million installations powering websites, datawarehouses,
business applications, logging systems and more. Customers such as Yahoo!
Finance, MP3.com, Motorola, NASA, Silicon Graphics, and Texas Instruments
use the MySQL server in mission-critical applications.
The MySQL database server embodies a software architecture that maximises
speed and customisability. Extensive reuse of pieces of code within the software
and an ambition to produce minimalistic but functionally rich features have
resulted in a database management system highly competitive in speed,
compactness, stability and ease of deployment. The separation of the core server
from the table handler makes it possible to run MySQL under strict transaction
control or with vary fast transactionless disk access, whichever is most
appropriate for the situation.
Reporting Options
MS Access
MS Access is a relational database management system which is part of the
Microsoft Office suite. It has a long history in the computer world for being one
of the simplest and easiest to use database tools available under Windows.
It is possible within MS Access to internally link to a MySQL database.
Effectively, you are able to create an MS Access front-end to a MySQL database
on the back-end. This opens up the possibility of using MS Access view and
reporting tools, with which may ITD staff may already be familiar, to
manipulate the ITD Database even though it is running on a different platform.
Crystal Reports
With Crystal Reports, you can easily deliver rich, interactive content from
virtually any data source, publish it to the Web in a variety of formats and
integrate it with applications.
Crystal Reports is published by Crystal Decisions Corporation (formerly
Seagate Inc.), best known for its high-quality computer hard drives. Starting in
1991, a version of Crystal was included in every copy of Microsoft's Visual
Basic and, as a result, Crystal has become the leading database report writer in
terms of installed base. Crystal Decisions reports more than 5 million copies
shipped. The program is included in more than 160 independent software
vendors.
ITD Database
Design Phase Report
20
5/14/17
Crystal can access more than 30 data sources using native drivers. In addition, it
can access any data source supported by an ODBC driver. The runtime engine
for Crystal can be distributed without charge.
The following is excerpted from the Crystal Decisions Web Site:
Wide variety of report types. Create virtually any report you can imagine
including subreports, conditional, summary, cross-tab, form, drill down, OLAP,
Top N, multiple details, mailing labels.
Fast and easy report creation. Powerful wizards, experts and built-in
functionality help novice and expert users quickly assemble highly interactive
reports. Customize your reports with logos, pictures, shapes and colors. An
extensive formula language gives developers full control over report formatting,
complex business logic and data selection.
Microsoft® Office Integration. Crystal Reports Add-ins for Microsoft Excel
and Microsoft Access make reporting from Office data a snap.
Interactive. Add charts, drill-down, alerting, parameter prompts, hyperlinks,
geographic mapping, field highlighting, running totals, Top N, Bottom N,
sorting to turn reports into compelling, interactive content.
Complex reports made easy. Address complex reporting requirements with
expert-driven features including grouping, sorting, subreports and cross-tabs, or
use the powerful formula editor.
Flexible information distribution. Publish reports to a variety of formats
including XML, PDF, DHTML, RTF, Word, Excel, text, email and version 7
.rpt format.
High performance report processing. Crystal Reports is up to 10 times faster
than version 7! Comprehensive support for SQL database servers enables faster
report processing and better use of network resources.
Crystal Reports is a Comprehensive web publishing system
Fast deployment. Rapidly deploy your web reporting solution using our new
web-based report management system. Wizards distribute existing reports to the
Web in just a few clicks.
Customizable. Customize ePortfolio, Crystal's web desktop, to match your
corporate identity or use the Crystal Web Wizard to create a tailored reporting
desktop within your corporate web site.
ITD Database
Design Phase Report
21
5/14/17
Easy to manage. The Crystal Management Console provides easy
administration of all objects, folders and servers.
Real-time or scheduled delivery. Deliver information real-time with report
streaming technology or automate content generation and delivery with the
flexible new scheduling feature.
Rich, interactive content. See interactive, presentation-quality reports in realtime, using zero-client DHTML, ActiveX® or Java™ viewers.
Access to all. Crystal Reports provides report access to all users, regardless of
platform or location, and supports popular infrastructures including Microsoft,
Netscape® and Lotus™ web servers.
MySQL Data Manager
Mysql Data Manager is web based mysql front-end with easy and intuitive
interface. It provides a powerful tool to remotely manage Mysql databases and
user access. This is multiplatform CGI script written in Perl. The current version
allows to:
- create and alter tables,
- search and edit data in spreadsheets,
- print the results,
- execute multiple SQL queries,
- save and edit SQL scripts,
- create and manage backup files,
- create and modify user accounts,
- set up its own initial parameters and modify options using web interface, and
more.
phpMyAdmin









create and drop databases
create, copy, drop and alter tables
delete, edit and add fields
execute any SQL-statement, even batch-queries
manage keys on fields
load text files into tables
create and read dumps of tables
export data to CSV values
administer multiple servers and single databases
DeZign for MySQL
ITD Database
Design Phase Report
22
5/14/17
"DeZign for MySQL" is a database development tool using an entity
relationship diagram. It visually supports the lay out of the entities and relations
and automatically generates SQL schemas for MySQL databases.
"DeZign for MySQL" supports the logical and physical data-level from a single
specification achieved by using automatic foreign key migration at design-time.
Multiple display options include entity/primary key/attributes inclusive foreign
keys/attributes exclusive foreign keys. "DeZign for MySQL also supports
domains (user defined datatypes). Reports generated by "DeZign For MySQL"
can be used for conveying complex designs in simplified format to managers at
various management levels. You can generate reports, datadictionaries and
MySQL databases in one click.
Equipment Specifications
A computer system will be required for ITD Database Server. Mimimum
requirements:







800 Mhz + PC
30+ Gigabytes Available Hard Disk Space
Windows (NT/2000) Operating System
TCP/IP Network Connectivity
Web Server (Microsoft IIS)
Database Engine (MySQL)
Report Writer Software (Crystal Reports Professional Edition)
B. Internal Design Requirement
The ITD Database should be designed to be as “normalized” as possible.
Normalization is a way of structuring database tables so that unique data is not
duplicated throughout the database, but rather joined as needed.
To this end, the database design is based upon a series of tables, grouped into small
“sub” database, and most linkable to the LAUSD Site Database. This Site Database
contains the Site Table, which consists of the location codes of all sites within the Los
Angeles Unified School District. Using this approach, all information in the ITD
Database will be searchable by LAUSD site (school, office, etc…).
Note that in general the relationship of all tables to the LAUSD Site Table will be
“Many to One”, that is, the record/column in the table in question is associated with
at most one record in the Site Table, while any Site record/column may be associated
with one or more records in the table in question.
ITD Database
Design Phase Report
23
5/14/17
ITD Database Diagram
ITD Database Application Flowchart
Main Menu
ITD Database
Design Phase Report
24
5/14/17
Reporting
Reporting consists of output of data stored in the database. This output is divided
into two categories:
1. Standard Output
This is the standard data output which is designed as part of the Java
application. This output is only available ONLINE. Generally, this is
simply the raw data from each table as it has been input. This output is
generated as a result of standard queries. The specific output and query
elements will be determined by the individual sections involved during the
Development Phase.
2. Custom Reports
This is output that is generated from Report Writer Software (Crystal
Reports, MySQL Data Manager, MS Access, etc…). The format and
specifications for these reports will be the responsibility of the specific
section which requires the report. Each section has wide latitude in terms of
ITD Database
Design Phase Report
25
5/14/17
Report Writer options, and should select a tool which best fits its particular
needs. Generally, the only requirement for the Report Writer is that it
support ODBC sources. New reports can be created on an ongoing basis.
Systems Security and Software
Telephone Systems Unit
ITD Database
Design Phase Report
26
5/14/17
Technical Support Services
ITD Database
Design Phase Report
27
5/14/17
Instructional Technology Branch
E-Rate / BB / Planning Dept.
ITD Database
Design Phase Report
28
5/14/17
ITD Database Table Diagram
Most tables will be linkable (or “joined”) to the LAUSD Site Table. There are some,
however, which will be joined by intermediate tables:




T3 Circuit Table
Network Circuit (Systems Security and Software) and Circuit (Phone Systems
Unit) Tables
Router Table
ITD Router Table
The reason for this is because these tables contain data elements which can link to
several sites; that is, you can have one circuit to multiple sites, one router handle
multiple sites, or one ITD router linked to multiple sites. So, rather than have the
same circuit data entered twice because it is used at two schools, we use an
intermediate “Circuit to Site” table which will allow us to indicate to the database that
this circuit is joined to two schools.
Also, there are some tables which are used to create “definitions” which are then used
in other tables which refer back to the Site Table. Some of these are:





IP Type Table (create IP descriptions for IP Table)
Port Table (create Port definitions to be used by IP Table)
Project Table (create Project definitions and assign to Sites using Project to
Site Table)
Application Table (create Application definitions and assign to Sites using
Application to Site Table)
Grant Table (create Grant descriptions and assign to Sites using Grant to Site
Table)
The following diagram shows the relationship between the databases, tables, and
LAUSD Site Table:
ITD Database
Design Phase Report
29
5/14/17
ITD Database
Design Phase Report
30
5/14/17
ITD Database Table Layout
Administration
Administration Database
This database is used for administration of the ITD Database. No one should
have access to this information other than ITD Staff responsible for maintaining
internal ITD Database and Application.

Site Table
This is the LAUSD Site Table which is mirrored on an ongoing basis from
the LAUSD DB2 Mainframe tables: SISADM.LO, SISADM.LS,
SISADM.CA. This table contains all “sites” in the District.
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o

Location Code (5)
Name (20)
Address (30)
City (20)
Zip (5)
Location Type (2)
Phone (10)
Campus Code (5)
Fax Number (10)
CDS Code (20)
Board Member Code (1)
State Assembly District Code (2)
State Senate District Code (2)
Federal Congressional District Code (2)
City Council District Code (2)
County Supervisory District Code (2)
User Access Table
UserIDs used to access the ITD Database Application.
o
o
o
o
o
o
Username (20)
Password (20)
Name (50)
Organization / Section (50)
Phone (15)
E-Mail (60)
ITD Database
Design Phase Report
31
5/14/17
o User Level (2)
o Comments (115)
o Modified (TimeStamp)

User Access List Table
List of Sections that a UserID in User Access Table may access. Used to
give single non-Admin UserID access to multiple sections.
o Username (from User Access Table) (20)
o Section (20)
o Modified (TimeStamp)

Control Table
Single record with general ITD Database control elements.
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
Control Key (normally, just “KEY”) (5)
Control E-Mail (60)
Control Return E-Mail (60)
Contact E-Mail (60)
Primary URL (115)
Login URL (115)
Start URL (115)
Staff URL (115)
Document URL (115)
Document Directory (115)
Login Servlet (115)
Main Servlet (115)
Login Expiration (integer)
Staff Login Expiration (integer)
Domain (E-Mail) (40)
SMTP Host (E-Mail) (60)
Modified (TimeStamp)
Systems Security and Software
Host Access Database
Yvonne Greenidge ([email protected])

Host Access Table
PC’s used to access 3270, RISC 6000 systems throughout District.
ITD Database
Design Phase Report
32
5/14/17
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
Location Code (5)
Contact Name (40)
Contact Phone (20)
Contact E-Mail (60)
PC Type (60)
PC Serial # (40)
PC Location (60)
LU Server Address (20)
Mapper (10)
LU (8)
Sys A Port (5)
Sys B Port (5)
Last Modified By (20)
Date Last Modified (11)
Notes (300)
Network Database
Leo Tam ([email protected]),
Kim Ong ([email protected]), Dave Hernandez ([email protected])

Network Circuit Table
Digital circuit lines throughout District. Also contains some T1 (E-Rate)
install data. This table links to Circuit Table in Telephone Systems Unit
circuit Database. Duplicated information here is supplied by “join” to the
source table.
o
o
o
o
o
o
o
o
o
o
o

OSPF Area (10)
Type (T1, DSL, ISDN, ADN, etc…) (20)
Circuit # (20)
T3 Circuit Name ((20)
T3 Channel # (01 – 28) (5)
T1 E-Rate Year (2)
Completed (on/off) (3)
Node City (30)
Date (11)
Technician (30)
Notes (300)
Network Circuit to Site Table
This table links individual circuits from Network Circuit Table to specific
sites and specific routers.
o Circuit # (20)
ITD Database
Design Phase Report
33
5/14/17
o Location Code (5)
o CDS Code (20)
o Router Serial # (20)

Router Table
Table of routers in District. Note that the router may be physically located at
one site, but be responsible for routing multiple sites. Use Router to Site
Table to determine what site(s) a specific router routes for.
o
o
o
o
o
o

Manufacturer (30)
Model (20)
Location Code (site where router is physically located) (5)
Location (location at site where router is located) (40)
Serial # (number to uniquely identify this router) (20)
Notes (300)
Router to Site Table
This table links individual routers from Router Table to specific sites that
they router for.
o Location Code (5)
o Router Serial # (20)

T3 Table
Table of T3 circuits in District.
o T3 Name (WLA01, etc…) (20)
o T3 Circuit ID (30)
o Channel # (01 – 28) (5)

ADN Circuit Table
Table of ADN circuits in District. Since these are going away, this is a
simple table to keep track of where they are/were located.
o
o
o
o
o
Location Code (5)
ADN Circuit ID (20)
Node (20)
Drop (20)
Notes (300)
ITD Database
Design Phase Report
34
5/14/17

WAN Table
Table of WAN addresses in District.
o
o
o
o

Location Code (5)
Circuit # (from Circuit Table) (20)
Site WAN Address (20)
ITD WAN Address (20)
LAN Table
Table of LAN addresses in District.
o Location Code (5)
o Site LAN Address (20)
o Circuit # (from Circuit Table) (20)

ITD Router Table
Table of ITD Routers used in District.
o
o
o
o
o

Manufacturer (30)
Model (20)
Serial # (20)
IP (20)
Notes (300)
ITD Router to Site Table
This table is used to link ITD routers to specific circuits and sites.
o
o
o
o

Location Code (5)
Circuit # (20)
Router IP (from ITD Router Table) (20)
T3 Interface (linked from T3 Table via Circuit Table + pulldown of
specific interface) (20)
LDF Table
This table will contain LDF information for all sites in District. No details
on info required have been made available at this time.
o Location Code (5)
ITD Database
Design Phase Report
35
5/14/17
o Notes (100)

MDF Table
MDF information for all sites in District.
o Location Code (5)
o Location (of MDF at site, building and room #) (40)

IDF Table
IDF information for all sites in District.
o
o
o
o
Location Code (5)
Location (of IDF at site) (40)
Manufacturer (30)
Model (20)
IP Database
Leo Tam ([email protected])

IP Type Table
Table of IP type definitions.
o Code (Voice, Wireless, Student VLAN, etc…) (30)
o Description (200)

IP Table
Table of all firewall IP’s assigned in District.
o
o
o
o
o
o
o

Location Code (5)
IP Type (from IP Type Table) (30)
System Admin (40)
IP (20)
Last Modified By (20)
Last Modified Date (11)
Notes (300)
Port Table
Ports allowed through firewall.
ITD Database
Design Phase Report
36
5/14/17
o IP (20)
o Port Number (10)
o Port Description (20)
Application Database
Leo Tam ([email protected]),
Vickie Frederick ([email protected])

Application Table
Applications, “admin” and otherwise, installed at sites. Examples are:
Elementary Report Card , IFS GUI, T610, Elem/T622, Sec/T520, Cafeteria,
Voice over IP.
o
o
o
o

Code (10)
Type (admin, end-user, etc…) (10)
Title (60)
Description (300)
Application to Site Table
This table links applications to specific sites. This will tell us what
applications are running at which sites. The “status” field is optional – not
known at this time what should actually be there.
o
o
o
o
Location Code (5)
Application Code (from application table) (10)
Status (should be a pulldown menu) (5)
Notes (300)
Project Database
Leo Tam ([email protected]),
Vickie Frederick ([email protected])

Project Table
District-Wide ITD Projects which are rolled out to sites.
o Code (10)
o Title (60)
o Description (300)
ITD Database
Design Phase Report
37
5/14/17

Project Status Table
The status of projects at specific sites. A set of anticipated status codes
should be defined for “status” pulldown menu.
o
o
o
o
o
o
Location Code (5)
Project Code (from project table) (10)
Status (should be a pulldown menu) (5)
Date (date of status) (11)
Cost (should only be filled when status is “complete”) (integer)
Notes (300)
Telephone Systems Unit - G288
Phone Systems Database
Sarah Tramel ([email protected]), Kathy Judge
([email protected])

Phone Systems Table
Table of phone systems at sites throughout the District.
o
o
o
o
o
o
o
o
o
o
o
o
o
Location Code (5)
System Type (PBX, Prologic, etc…) (20)
ID (IL# or other ID such as serial) (20)
Account # (20)
Capacity (# lines and instruments) (30)
Manufacturer (30)
Model (20)
Auxiliary Equipment (30)
Types of Sets (30)
Number of Sets (5)
Functions (30)
Leased (on/off) (3)
Notes (300)
Circuit Database
Sarah Tramel ([email protected]), Kathy Judge
([email protected])

Circuit Table
ITD Database
Design Phase Report
38
5/14/17
Table of all circuit lines (digital and analog) throughout the District. This
information will come from billing system, so should be most accurate.
o
o
o
o
o
o
o
o
o
o
o

Type (Voice, ISDN, DSL, AND, T1, etc…) (10)
Description (100)
Working # (20)
Billing # (20)
Circuit # (20)
Telco (10)
Status (10)
IL# (or some ID# for phone system)
T3 Circuit ID (20)
Node City (30)
Notes (300)
Circuit to Site Table
Table showing which circuits are assigned to which sites.
o Circuit #
o Location Code (5)
Technical Support Services
Public Address / Intercom
Michael O’Larte ([email protected]), Pete Barrale
([email protected])

Public Address/Intercom Table
Public Address and Intercom data for sites throughout the District.
o
o
o
o
o
o
o
o
o
o
o
Location Code (5)
Manufacturer (30)
Model (20)
Year (11)
# Switch Positions (3)
# Classrooms Connected (4)
E911 Compliant (on/off) (3)
Headend Location (by building and room #) (20)
Main PATC Location (by building and room #) (20)
Cable Type (10)
Phones or Switch and Speaker (15)
ITD Database
Design Phase Report
39
5/14/17

Return Call Buzzer Table
Table indicating which District sites have RCB. Used primarily for budget
purposes.
o Location Code (5)
o Return Call Buzzer (on/off) (3)

Network Table
Additional info supplied by this section with respect to network fiber.
o
o
o
o
Location Code (5)
Fiber Optic (on/off) (3)
Backbone Fiber Count (10)
Horizontal (fiber or copper) (10)
Alarm Database

Intrusion Alarm Table
Intrusion alarm systems at sites throughout District. Can have multiple
alarm systems at individual location.
o
o
o
o
o
o
o
o
Location Code (5)
Alarm # (1st, 2nd, 3rd, etc…) (integer)
Manufacturer (10)
Date of Install (10)
% of Site Covered (integer)
# of Panels (integer)
# of Zones (integer)
Last Assessment Date (10)
MATV Database

MATV Table
Table of MATVs throughout the District. Only one per site.
o
o
o
o
Location Code (5)
Manufacturer (10)
Headend Location (30)
% of Site Covered (3)
Modular Classroom Database
ITD Database
Design Phase Report
40
5/14/17

Modular Classroom Table
Table of portable/modular classrooms throughout the District.
o
o
o
o
o
o
o
o
o
Location Code (5)
Building Serial Number (10)
Telephone Connectivity (on/off) (3)
Tel Connect PBX (on/off) (3)
Tel Connect Intercom (on/off) (3)
LAN (on/off) (3)
Public Address/Intercom (on/off) (3)
Intrusion Alarm (on/off) (3)
Master Antenae Television (MATV) (on/off) (3)
Instructional Technology Branch
Grant Database
Athaur Ullah ([email protected])

Grant Table
Table showing District grant programs and totals.
o
o
o
o
o

Grant Code (5)
Grant Name (50)
Grant Objective (300)
Grant Target (Elm/MS/HS) (5)
# Schools Participating (3)
Grant to Site Table
Table showing which sites are participating in which Grant programs.
o Location Code (5)
o Grant Code (5)
Technology Database

Technology Table
Table showing District computer technology totals, by site. Essentially data
from Instructional Technology Branch “Form 9”.
ITD Database
Design Phase Report
41
5/14/17
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
Location Code (5)
School Name (40)
School Local District (2)
School CDS Code (20)
School Enrollment (integer)
School Classrooms (integer)
School Year Type (10)
School Schedule (10)
School Principal (40)
School Address (40)
School City (30)
School Zip (10)
School Phone (15)
IC PC-386 or later (integer)
IC PC-Without CD-Rom (integer)
IC PC-486/Pnt.With CD-Rom (integer)
IC 486/Pnt. Lap Top (integer)
IC Earlier Tn PPC (integer)
IC PPC G3/4 iMac (integer)
IC PwrBk Ibook (integer)
IC PDA Alpha Smt CE (integer)
Lab PC-386 or later (integer)
Lab PC-Without CD-Rom (integer)
Lab PC-486/Pnt. With CD-Rom (integer)
Lab 486/Pnt Lap Top (integer)
Lab Earlier Tn PPC (integer)
Lab PPC G3/4 iMac (integer)
Lab PwrBk Ibook (integer)
Lab PDA Alpha Smt CE (integer)
Lib/M PC-386 or later (integer)
Lib/M PC-Without CD-Rom (integer)
Lib/M PC-486/Pnt. With CD-Rom (integer)
Lib/M 486/Pnt Lap Top (integer)
Lib/M Earlier Tn PPC (integer)
Lib/M PPC G3/4 iMac (integer)
Lib/M PwrBk Ibook (integer)
Lib/M PDA Alpha Smt CE (integer)
Off. PC-386 or later (integer)
Off. PC-Without CD-Rom (integer)
Off. PC-486/Pnt. With CD-Rom (integer)
Off. 486/Pnt Lap Top (integer)
Off. Earlier Tn PPC (integer)
Off. PPC G3/4 iMac (integer)
Off. PwrBk Ibook (integer)
Off. PDA Alpha Smt CE (integer)
Lan Status (20)
ITD Database
Design Phase Report
42
5/14/17
o
o
o
o
o
o
o
o
o
o
o
Internet Access Classrooms (on/off) (3)
Date Lan Tested (10)
Est. Completion Date (10)
Magic # (integer)
# DHS Completed (integer)
# 2882 (integer)
Total HS Completed (integer)
Form 9 ES/MS (integer)
CTI Rd-1 (integer)
Waterford (integer)
# MM Computers Expected (the requirement / calculate using
enrollment & ratio) (integer)
o # MM Computers Received (integer)
o # MM Computers Needed (to reach requirement: Expected –
Received) (integer)
o Comments (300)
Training Database

Instructional Technology Training Status Table
Training status for all ITB training programs.
o Training Program Code (10)
o Training Program Description (100)
o Total Enrollment # (integer)

Training & Assessment Table
Table showing total teachers completing CTAP2 Proficiency Tool for 6
Basic Computer Skills. Instructional Technology Branch will provide this
information from CTAP2 software.
o
o
o
o
Location Code (5)
# Teachers Basic Level (integer)
# Teachers Intermediate Level (integer)
# Teachers Proficient (integer)
Planning Department / E-Rate Program
E-Rate / BB Database
James Alther ([email protected])
ITD Database
Design Phase Report
43
5/14/17

E-Rate Funding Summary Analysis
Funding Summary Analysis
o
o
o
o
o
o
o
o
o
o
o
o
o

Location Code (5)
E-rate Year (integer)
Site Name (60)
Total Budget (numeric)
E-Rate Funding Percent (numeric)
E-Rate Funds (numeric)
Approved E-Rate Funds (numeric)
COPS District Matching Funds (numeric)
Approved District Matching Funds (numeric)
COPS District Non E-Rate Funds (Electrical) (numeric)
Approved District Non E-Rate Funds (Electrical) (numeric)
Package (10)
Comments (200)
Equipment Installation Table
Equipment installed under E-Rate.
o
o
o
o
o
o
o
o

Location Code (5)
Location (at site) (40)
Date Installed (10)
Manufacturer (30)
Model (20)
Serial Number (30)
E-Rate Tag (20)
Comments (200)
E-Rate / BB Table
Table of E-Rate / Proposition BB information supplied by Jim Alther. No
further details provided.
o
o
o
o
o
o
o
o
o
E-Rate Year (integer)
Local District (2)
PKG (?) (10)
CDS Code (20)
Location Code (5)
Total Cert (?) (integer)
Board Member (60)
Site Name (60)
Switches (?) (10)
ITD Database
Design Phase Report
44
5/14/17
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
Vendor SW (?) (20)
Vendor yr5 (?) (20)
Site Address (80)
Site Principal Name (60)
Comp Total (?) (integer)
Site Phone (15)
Grades (?) (10)
Age (?) (10)
Site Type (what are options?) (20)
471 Appl (?) (10)
01 CLRM (?) (integer)
Safety & Tech Status (what are options?) (100)
Conduit Status (what are the options?) (100)
AC Year (?) (integer)
E-Rate Discount (integer)
Project Manager (60)
F/Reduced Percentage (?) (numeric)
Digital Connect (?) (10)
Digital HS Yr (?) (integer)
Seed NetW (?) (10)
El Lit Grant (?) (10)
MS Lit Grant (?) (10)
Time Warner (?) (10)
T-1 Yr (?) (integer)
RESP (?) (60)
S & T Year (?) (integer)
Vendor (60)
Vendor1 (?) (60)
Proposed E-Rate (numeric)
Probable E-Rate (numeric)
Entity Number (?) (20)
Fiber (Y/N) (3)
BB Completion (20)
BB Complete as of 7/23 (?) (20)
E-Rate Completion (20)
E-Rate % Completion (numeric)
Other Completion (20)
Other % Completion (numeric)
Funding Source (40)
E-Rate Funding Year (10)
LAN Status (?) (20)
Admin Con (?) (60)
BB (?) (10)
BB and E-Rate (?) (10)
BB Vendor (?) (60)
BB Equipment (?) (20)
ITD Database
Design Phase Report
45
5/14/17
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
Year 3 Equip (?) (20)
Y1-2 E-Rate Equip (?) (20)
Router (?) (30)
911 Compliant (Y/N) (3)
PBX (Y/N) (3)
School Site 2 (?) (60)
School Site 3 (?) (60)
School Site 4 (?) (60)
Entity (?) (10)
Yr5 Free (?) (integer)
% F & R (?) (numeric)
Discount (?) (numeric)
Weight (?) (integer)
NW Status as of Oct 8 2001 (?) (100)
Test & Accept Compl as of Oct 8 (?) (100)
Status Oct 8 NW % Comp (?) (100)
Est Comp Date (?) (10)
Yr5 Enrollment (?) (integer)
Proposition BB Database
James Alther ([email protected])
This data is currently provded in E-Rate database.
ITD Database Table Entity Relationship Diagrams
Systems Security and Software
The relationship to the Site Table of the Router to Site, ITD Router to Site, Circuit
to Site, Application to Site and Project to Site Tables is "Many to One". By
definition: "An entity in A is associated with at most one entity in B (being the Site
Table). An entity in B is associated with any number in A".
So, for example, a Circuit to Site Table record will consist of one Circuit ID and
one Location Code. The Circuit ID may be duplicated in this table, as may the
Location Code, but NOT the combination. And, this record will relate to just ONE
record in the Site Table -- the record which matches the Location Code. Doesn't
matter if you can have multiple Circuits at one Site or not -- every record in the
Circuit to Site Table will always only relate to ONE record in the Site Table.
ITD Database
Design Phase Report
46
5/14/17
Telephone Systems Unit
We assume here that one site may could have more than one Circuit record.
Technical Support Services
According to Technical Support Services, there can be multiple PA Systems,
Intrusion Alarms and Modular Classrooms per site. However, there can only be
one Return Call Buzzer, MATV and Network (table status) record per site.
ITD Database
Design Phase Report
47
5/14/17
Instructional Technology Branch
ITD Database
Design Phase Report
48
5/14/17
Note that the Training Status Table has no relationship to the Site Table.
E-Rate / BB / Planning Department
Note that the E-Rate Funding Summary Table relationship to the Site Table is
“Many to One” because you could have the same Location Code repeated for
multiple years.
ITD Database
Design Phase Report
49
5/14/17
IV. Plans and Schedules
A. Major Milestones
The following is the planned schedule for the ITD Database Project:
Phases and Assignments
Ron Parker
Start
Finish
Work
Mon 11/26/01 Tue 6/11/02 501 hrs
Research / Study / Needs Analysis Mon 11/26/01 Thu 11/29/01 30 hrs
Design
Mon 1/14/02 Wed 1/23/02 60 hrs
Development
Mon 1/28/02 Tue 3/12/02 255 hrs
Test
Tue 3/12/02 Tue 4/23/02 60 hrs
Implementation
Tue 4/23/02 Tue 5/14/02 60 hrs
Documentation
Tue 5/14/02 Tue 5/28/02 24 hrs
Training
Tue 5/28/02 Tue 6/11/02 12 hrs
The Design Phase is on budget but behind schedule by nearly 3 weeks. This is due,
primarily, to an inability to schedule meetings in a timely manner with key section
representatives.
We hope this will be less of a problem as we move into the Development Phase.
ITD Database
Design Phase Report
50
5/14/17