Information System Concept
for the Land Use Planning and Management Project at TCPD
Annex 6
DBMS for Permits
A6.1) Application procedure
The current permit approval system applied by TCPD is hardcopy based and involves ample labour and archiving inputs. The system is to be computerized and integrated into LUPMIS, with interfaces to the GIS component of LUPMIS, and also - in a later stage - to the databases of the other LSAs.
The process of applying for a building permit is currently as follows:
- TCPD (Development Control Unit) receives application
- Planning / Schedule Officer undertakes requisite processing of application
- Technical Sub-Committee meets to consider merits of application and offers appropriate advice both to applicant and to Statutory Planning Committee
- Statutory Planning Committee meets to take final decision on applications
- Secretary of Planning Authority prepares approved / deferred / rejected plan for signature and information of chairman and applicant
- Works Department receives approved plans for processing of issuance of building permit
- Applicant collects approved plan
Documents required for this process:
- Printed Site Plans
- Building Fence And Block Plans
- Clearance Letter from Lands Commission or Land Title Registry
- Working drawings
- Building Permit Application Form
- TCPD Form 1
- Enquiry letter of TCPD to Lands Commission (for official search)
- Environmental Impact Assessment Report and / or Structural Report and / or Fire Service Report (for multi-storey structure)
This current process of application, or any modifications in future, will be enhanced by the Permit DB, with possible data entry screens as shown below.
A6.2) Development and deployment
The Consultant recommends to set up a server-based DBMS system, accessible initially through the LAN of the District office, in a later stage also accessible through a secured system on a VPN or web-based protocol. A backup or mirror system should reside on the TCPD-HQ server.
- Phase 1: Revision of permit application procedures
- Phase 2: Definition of processes
- Phase 3: Evaluation of existing systems
- Phase 4: Decision of outsourcing or in-house development
- Phase 5: Development and coding
- Phase 6: Testing at HQ
- Phase 7: Installation at beta site
- Phase 8: Installation at pilot communities (LAN based)
- Phase 9: Dissemination in additional TCPD offices (LAN based)
- Phase 10: Setup of backup or mirror site at HQ
- Phase 11: On-line interfacing between District, Region and HQ
- Phase 12: Linkage to LSAs
Figure A6.1: Technical development phases of DBMS
A6.3) Sample
Entry screens can look like this (source):
Figure A6.2: Entry screen into Building Permit Database
Figure A6.3: Entry screen into Building Permit Database
A6.4) Database structure, early proposal
This list should be used as a start for discussion. Modifications and adjustment to the new planning approach, e.g. with stronger emphasis on land use planning and planning zones, have to be incorporated.
- 1. BuildPermits
- ClientId (key)
- PeriodFrom
- PeriodTo
- DescOfWork
- Purpose
- Level
- ProcessFee
- TotalValue
- Penalty
- TypeOfApplication
- Comment
- Reason
- DateApproved
- Meeting
- Year
- PermitNo
- PermitDate
- ReceiptNo
- DateReceived
- 2. ApplPermit (1:1 to table 1)
- ClientId (key)
- PeriodFrom
- PeriodTo
- DescOfWork
- Purpose
- Level
- ProcessFee
- TotalValue
- Penalty
- TypeOfApplication
- Comment
- Reason
- DateApproved
- Meeting
- Year
- PermitNo
- PermitDate
- ReceiptNo
- 3. Specifications (1:1 to table 2)
- ClientId (key)
- Spec0
- Spec1
- Spec2
- Spec3
- Spec4
- Spec5
- Spec6
- Spec7
- Spec8
- Spec9
- Spec10
- Spec11
- Spec12
- Spec13
- Spec14
- 4. Materials (n:1 to table 2)
- Id (key)
- ClientId
- PartId
- Material
- 5. PartOfBuilding (1:n to table 4)
- 6. ApplDev (1:1 to table 2)
- ClientId
- AreaId
- TypeId
- SerialNo
- Sector
- DateReceived
- ApplNo (key)
- PermitNo
- ApplName
- Address
- Telephone
- Location
- BuildLines1
- BuildLines2
- BuildLines3
- Splay
- Type
- Construct
- Action1
- Action2
- Action3
- Action4
- Action5
- Action6
- Comment
- ProcessFee
- Penalty
- Paid
- 7) Sectors (1:n to table 6)
- ApplNo (key)
- Status
- Reason
- DateAmended
- 8) Status (1:1 to table 6)
- ApplNo (key)
- Status
- Reason
- DateAmended
- 9) Payments (n:1 to table 6)
- ClientId
- ApplNo
- Date
- ReceiptNo (key)
- Amount
- PayMode
- ChequeNo
- Bank
- Cashier
- PayerType
- 10) LandUses (1:n to table 6)
- 11) Subuses (n:1 to table 10)
- 12) AreaPlots (n:1 to table 10)
- AreaId (key)
- LandMark
- PlotNo
- Block
- TypeId
- DevUsed
- PerUsed
- 13) PlanningArea (1:n to table 11)
- AreaId (key)
- AreaName
- SectorId
- ZipCode
- PlotsNo
- Location
- 14) Rates (no senior relation)
- Id (key)
- CategoryId
- Dexription
- Rate
- 15) RateCategory (1:n to table 14)
- CategoryId (key)
- Category
Last update: Dec 2007
