INTERNSHIP PROJECT DRAFT 12.09.

2025

PROJECT MEMBERS GUIDE

Smt. Vanitha D
1. Nehal Gupta
2. Pragna Udayakumar Kukarni Sc ‘G’

1.1 PROBLEM STATEMENT

“Construct a centralized Technologies Database system that enables efficient storage, retrieval, updating, and management of
information related to technologies developed by CASDIC. The system should support advanced querying capabilities to
view, edit, and update records, as well as generate customized reports based on user-defined specifications. The solution
should ensure data integrity, scalability, and ease of access for decision-making and analysis.”

1.2 MAJOR CAPABILITIES

I. Query & Search

1. Search technologies by TRL, category, funding, or collaborators

2. Filter by hardware/software qualification status
3. Query based on specs/configurable parameters (e.g., cost < 1Cr, weight < 5kg)
4. Compare against worldwide products across chosen parameters

II. Reports & Analytics

1. Generate tabular & graphical reports (TRL progress, cost over time, comparison charts)
2. Export reports (CSV, PDF, Excel)
3. Highlight gaps (e.g., missing SW qualification, TRL not achieved)

III. History Tracking

1. Version control for technologies (upgrades & changes)

2. Audit trail of modifications (who updated what & when)
3. Archived records for deprecated technologies

IV. Data Linking

1. Link technologies with projects, employees, patents, and publications

2. Show complete lifecycle view of a technology

V. Security & Access Control

 1. Role-based access (Admin, Researcher, Viewer)
2. Confidentiality tagging (Public / Restricted / Confidential / Top Secret)

VI. Dashboards

1. TRL distribution (pie chart)

2. Funding vs progress graph
3. Active vs Deprecated technologies

1.3 SYSTEM CAPABILITIES

Query, Report, and History

1. QUERY

Queries allow users to retrieve information from the database efficiently using configurable filters and
specifications.

Key Features:

• Basic Search
o By technology name, code, or category.
o By TRL start/achieved.
o By qualification status (HW/SW).
• Advanced Search
o By configurable parameters (e.g., Power > 500W, Cost < 1Cr, Latency < 10ms).
o By project association (which projects used this technology).
o By employee contribution (technologies worked on by a given scientist).
• Comparison Queries
o Compare CASDIC technologies vs. worldwide products across selected attributes.
o Query by funding details (funded by, amount range, year).
• Example Queries
o “Show all technologies with TRL ≥ 6 that are used in aerospace projects.”
o “List all technologies with SW qualification pending.”
o “Find all technologies where Power > 200W and Weight < 5kg.”

2. REPORT

Reports transform queried data into structured summaries and visual insights.
Key Features:

• Report Types
o TRL Progress Report → shows readiness evolution across technologies.
o Qualification Status Report → HW/SW readiness tracking.
o Funding & Collaboration Report → expenditure, collaborating companies.
o Employee Contribution Report → mapping employees to projects & technologies.
o Technology Comparison Report → side-by-side feature comparison.
• Output Formats
o Tabular Reports → sortable, filterable tables in the web UI.
o Visual Reports → bar charts, pie charts, line graphs for trends.
o Export Options → CSV, Excel, PDF.
• Configurable Parameters
o Timeframe (monthly, yearly, custom).
o Filters (TRL stage, department, project type).
o Metrics to include (cost, manpower, features, achievements).

3. HISTORY

The history module ensures accountability and traceability by tracking changes over time.

Key Features:

• Versioning
o Maintain historical versions of each technology entry.
o View what changed (TRL update, qualification achieved, new project added).
• Audit Trail
o Who made the change (employee/admin).
o When the change was made (timestamp).
o What was changed (old vs. new value).
• Lifecycle Tracking
o Track technology from start date → TRL milestones → deprecation.
o Keep record of achievements, awards, and worldwide comparison updates.
• Examples
o “Show history of TRL updates for Technology X.”
o “View all modifications made to funding details of Project Y.”
o “Retrieve decommissioned technologies with their final reports.”
2.1 EXISTING SYSTEMS

A. GENERIC R&D/TECHNOLOGY DATABASES

Examples:

• NASA TechPort – Manages technology projects with TRL tracking.

• DRDO Knowledge Repositories – Store project & technology information internally.
• IEEE Xplore / ACM Digital Library – Provides research publications but not lifecycle tracking.

Limitations:

• Focus only on project metadata or publications.

• Limited querying (mostly keyword search).
• No integrated comparison of technologies against global benchmarks.
• Weak linkage between employees, companies, projects, and technology specs.
• Reporting features often limited to static summaries.

B. ENTERPRISE PROJECT MANAGEMENT TOOLS

Examples:

• Jira, Trello, Asana → Track project progress.

• SAP PLM (Product Lifecycle Management) → Tracks industrial products.

Limitations:

• Generic tools → not customized for defense/technology R&D lifecycle.

• Focus on task/project management, not detailed TRLs, qualifications, funding, or comparisons.
• No deep historical versioning tied to scientific milestones.
• Expensive & over-engineered for research labs like CASDIC.

C. SCIENTIFIC PAPER/PATENT REPOSITORIES

Examples: Google Scholar, PatSeer, WIPO Patentscope.

Limitations:

• Provide publications/patents but no structured, queryable database for internal technologies.

• Don’t connect technologies with employees, projects, collaborations, and qualifications.
2.2 THE SOLUTION
How Our CASDIC Technologies Database is Better

Specialized for Defense R&D (CASDIC)

o Unlike generic tools, ours is tailored to technologies, subsystems, and projects in India’s defense
ecosystem.

Rich Schema Covering Entire Lifecycle

o Includes TRL progression, hardware/software qualification, projects, funding, collaborations,

employee contributions, worldwide comparisons, achievements — all in one unified system.

Advanced Querying

o Configurable filters (TRL, cost, manpower, readiness dates, features).

o Multi-dimensional queries (e.g., “Find technologies with TRL ≥ 6, qualified HW, and used in aerospace
projects funded after 2020”).

Reports Beyond Basic Data

o Funding breakdowns, TRL progress charts, qualification status reports, comparison reports.
o Export in PDF, Excel, CSV.
o Visual dashboards (graphs, timelines).

History & Audit Trail

o Tracks who changed what and when (important for defense accountability).
o Maintains versioning for each technology’s evolution.

Technology Comparison Capability

o Unique feature: CASDIC vs. worldwide products → side-by-side benchmarking.

Collaboration Mapping

o Direct links between employees, companies, and projects.

o Helps identify who contributed to what, fostering transparency and recognition.

Cost-Effective & Scalable

 o Built on open-source stack (Vite + React, [Link], MySQL).
o No licensing cost vs. enterprise PLM tools.
o Can scale as CASDIC’s technology base grows.

2.3 DATABASE INFORMATION

1. technologies : Main table, now with new TRL and dev project info.

Field Type Description

 Field Type Description

tech_id (PK) INT AUTO_INCREMENT Unique identifier

name VARCHAR(255) Technology name
category VARCHAR(100) Domain/subsystem
production_start_date DATE Start of development
last_usage_date DATE NULL Last use (NULL = still active)
status ENUM("In Development","In Use","Deprecated") Current status
trl_start TINYINT TRL at project start
trl_achieved TINYINT TRL achieved
trl_description TEXT Description of achieved TRL level
budget DECIMAL(15,2) Project funding
ENUM("Public","Restricted","Confidential","Top
security_level Security classification
Secret")
location VARCHAR(255) Deployment site
tech_stack TEXT Technologies used
salient_features TEXT Highlights
achievements TEXT Awards/milestones
image_path VARCHAR(255) Path to image/diagram
Technology development project
dev_proj_name VARCHAR(255)
name
dev_proj_number VARCHAR(100) Project number/code
dev_proj_code VARCHAR(100) Internal code
funding_details TEXT Source & funding details

2. technology_specs :For capturing specs/configurable parameters per technology.

Field Type Description
spec_id (PK) INT AUTO_INCREMENT
tech_id (FK) INT Links to technologies
Name of parameter (e.g., Power,
parameter_name VARCHAR(255)
Weight, Latency)
parameter_value VARCHAR(255) Value (e.g., 500W, 2.5kg, 10ms)
unit VARCHAR(50) Measurement unit (optional)
TRUE = user-configurable,
configurable BOOLEAN
FALSE = fixed

3. qualification_hw : Status of hardware qualification for the technology.

Field Type Description

hw_id (PK) INT AUTO_INCREMENT

tech_id (FK) INT Links to technologies
requirement TEXT Hardware requirement
 Field Type Description

Status (e.g., Prototype, Production

achieved_status VARCHAR(255)
Ready)
date_achieved DATE Date qualification achieved

4. qualification_sw : Status of software qualification for the technology.

Field Type Description

sw_id (PK) INT AUTO_INCREMENT

tech_id (FK) INT Links to technologies
requirement TEXT Software requirement
achieved_status VARCHAR(255) Status (e.g., Tested, Certified)
date_achieved DATE Date qualification achieved

5. Versions : Stores technology version/product-types history.

Field Type Description

version_id (PK) INT AUTO_INCREMENT

tech_id (FK) INT Links to technologies
version_number VARCHAR(50) e.g., v1.0, Mk-II
release_date DATE Release date
notes TEXT Additional notes

6. Companies : Stores companies that collaborated.

Field Type Description

company_id (PK) INT AUTO_INCREMENT
name VARCHAR(255) Company name
country VARCHAR(100) Country of origin
role VARCHAR(100) Role in collaboration

7. Projects : Stores CASDIC projects that used these technologies.

Field Type Description

project_id (PK) INT AUTO_INCREMENT

name VARCHAR(255) Project name
description TEXT Project description
start_date DATE When project started
end_date DATE NULL NULL = ongoing
8. Employees : Stores CASDIC employees.

Field Type Description

employee_id (PK) INT AUTO_INCREMENT
name VARCHAR(255) Employee name
designation VARCHAR(100) Job title
department VARCHAR(100) Department
email VARCHAR(255) Contact email

9. Patents : Stores patents related to a technology.

Field Type Description

patent_id (PK) INT AUTO_INCREMENT
tech_id (FK) INT Related technology
title VARCHAR(255) Patent title
patent_number VARCHAR(100) Unique patent ID
date_filed DATE Filing date
date_granted DATE Grant date

10. Publications : Stores research papers/reports.

Field Type Description

pub_id (PK) INT AUTO_INCREMENT
tech_id (FK) INT Related technology
title VARCHAR(255) Publication title
authors TEXT Authors list
journal VARCHAR(255) Journal/Conference name
year YEAR Year published
link VARCHAR(255) URL/link

3.1 QUERIES - EXAMPLES

Query SQL Statement Purpose / Use Case

sql SELECT tech_name, trl_start, trl_achieved, To identify mature

1. Get all technologies
trl_description FROM technologies WHERE trl_achieved technologies ready for
with TRL ≥ 6 >= 6; deployment.
2. List technologies sql SELECT tech_name, hw_status, hw_achieved_date FROM To track technologies
with pending technologies WHERE hw_status != 'Qualified'; needing further
 Query SQL Statement Purpose / Use Case
hardware hardware validation.
qualification
sql SELECT t.tech_name, p.project_name FROM See which
technologies t JOIN project_technologies pt ON
3. Technologies used technologies
t.tech_id = pt.tech_id JOIN projects p ON p.project_id
in a given project = pt.project_id WHERE p.project_name = 'Aerospace
contributed to a
Radar System'; specific project.
sql SELECT e.emp_name, [Link], t.tech_name FROM
4. Employees who To find CASDIC staff
employees e JOIN employee_technologies et ON e.emp_id
worked on a given who contributed to a
= et.emp_id JOIN technologies t ON et.tech_id =
technology t.tech_id WHERE t.tech_name = 'Stealth Coating'; particular technology.
sql SELECT c.tech_name AS casdic_tech, w.product_nameBenchmark
5. Compare CASDIC AS world_product, w.scale_parameter, [Link] FROM
CASDIC’s technology
technology vs technologies c JOIN tech_comparisons tc ON c.tech_id =
against international
worldwide equivalent tc.tech_id JOIN world_products w ON tc.world_id =
w.world_id WHERE c.tech_name = 'AI Guidance System'; alternatives.
sql SELECT t.tech_name, f.funding_agency, [Link],
To analyze cost and
6. Funding details for [Link] FROM technologies t JOIN funding f ON t.tech_id
funding sources for a
a given technology = f.tech_id WHERE t.tech_name = 'Quantum Communication
Module'; technology.
sql SELECT t.tech_name, h.old_value, h.new_value,
7. TRL progress
h.change_date, h.changed_by FROM technologies t JOIN To track how TRL
history of a
history h ON t.tech_id = h.tech_id WHERE h.field_name evolved over time.
technology = 'TRL' AND t.tech_name = 'Nano-satellite Propulsion';

To prepare a report on
sql SELECT YEAR(creation_date) AS year, COUNT(*) AS
8. Generate TRL number of matured
num_technologies FROM technologies WHERE trl_achieved
report by year >= 6 GROUP BY YEAR(creation_date) ORDER BY year;
technologies each
year.
9. Find all To filter mature
sql SELECT tech_name, trl_achieved, sw_status FROM
technologies with technologies that also
technologies WHERE trl_achieved >= 5 AND sw_status =
TRL ≥ 5 and SW 'Qualified';
passed software
qualified qualification.
To track retired
10. List sql SELECT tech_name, last_date_usage,
technologies and
decommissioned reason_for_deprecation FROM technologies WHERE
last_date_usage < CURDATE();
reasons for
technologies
discontinuation.