DIGIT - Projects functional details
Projects are the first work entity defined by the State/Department/ULB or any executing authority. This consists of basic details like IDs, descriptions, addresses, sub-project details, project types, start and end dates etc.
Projects may not focus on just construction or civil works. A health campaign, an office decoration, a pre-contractual phase with an IT vendor for new software, new service delivery initiatives etc are examples of projects.
Users: Junior Engineer or Assistant Engineer who creates Works Projects for the ULB/Department
Description
JE creates projects with the below-mentioned attributes.
A project can have sub-projects as well depending on the way of executing the project.
When a project is divided into sub-projects, each will have the same attributes to be captured as the main project.
A project can be sent for approval depending on the need.
Usually, the administrative sanction is done on projects by EO. Post approval, detailed and abstract estimates are done.
Once the admin sanctions the project, the fund is also blocked for the respective heads of accounts.
Project status -
Created
In progress
Approved
Rejected
Cancelled
Once a project is created on the UI, the system generates a unique ID for each project/sub-project.
ID: PROJ/<ULB/Department Code>/<Year>/<month>/<Date>/<running sequence number>
The project details capture the financial details such as the funding source for the project. These details, however, are not part of the Project Service but are captured as part of the Program Service.
The table below provides the list of project attributes.
A project can be divided into multiple sub-projects, each with its own workflows/business requirements defined.
Field | Data Type | Required (Y/N) | Validations / Comments |
---|---|---|---|
Id
NA
Y
System generated UUID
Name
Alphanumeric
Y
MinChar 2 - Max Char - NA Ex - Construction of School Building
Project Type
MDMS Data
Y
Should be pre-defined master data Ex - Building
Project Sub Type
MDMS Data
N
Should be pre-defined master data. Estimate templates are linked to a project subtype Ex - School Building
Project Group
MDMS Data
Y
Should be pre-defined master data. Contract & Assetisation terms are defined based on this value. Ex - Capital Works
Address
Y
Address of the main project.
Proposed Start date
Date
N
Proposed End date
Date
N
Parent
ID
N
Parent Project ID
Status
MDMS Data
Y
Created, Rejected, Cancelled, In-progress, Completed
Owning Department
MDMS Data
Y
Reference No
Alphanumeric
N
MinChar 2 - Max Char - NA Reference No to Offline File if any
Description
Alphanumeric
N
MinChar 2 - Max Char - NA Description of the Project
Documents
Attachments
N
Upto 5 Documents each of 5 MB Document Attachments
Create Project with no sub projects
Create Project with Sub projects
Capturing Financial details of project (Part of Program service)
Capturing Sub Project Details
Project Created Successfully
View Project
Projects Inbox
Inbox Table