File size: 59,438 Bytes
d48703d | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 | ---
tags:
- sentence-transformers
- sentence-similarity
- feature-extraction
- dense
- generated_from_trainer
- dataset_size:88
- loss:CachedMultipleNegativesRankingLoss
base_model: sentence-transformers/all-mpnet-base-v2
widget:
- source_sentence: udyam registration cancel <udyam_no> is still pending for cancellation
and its passing more than <NUM> days issue delayed cancellation of udyam registration
context the user is reporting that the cancellation of udyam registration for
udyam-up- <NUM> - <NUM> is still pending and has been delayed for more than <NUM>
days. details - udyam registration no udyam-up- <NUM> - <NUM> cancellation status
pending
sentences:
- Policy and Schemes. Definition of MSMEs (Clarifications related to definition)
Policy. this category pertains to grievances seeking policy interpretation and
clarification regarding the definition and classification of micro small and medium
enterprises msmes under the micro small and medium enterprises development msmed
act <NUM> as amended . the category encompasses disputes or doubts related to
the application of turnover investment and structural factors to specific enterprise
cases. key issues include turnover and investment threshold calculations treatment
of export turnover or goods and services tax gst classification of enterprises
as micro small or medium clubbing of multiple units or related businesses under
a single msme identity the category also captures concerns arising from the transition
between old and revised msme definitions including impact of reclassification
on eligibility continuity of benefits already availed applicable financial year
for revised criteria grievances in this category are clarification-driven rather
than system-error driven arising from the intersection of policy intent numerical
calculations and enterprise structure. example issues include turnover classification
discrepancies my turnover is within limits but udyam shows a higher msme category
please clarify the correct classification as per policy. export turnover treatment
export turnover has been included while determining msme status kindly clarify
whether it should be excluded. post-migration classification changes after migration
from uam to udyam my enterprise category has changed despite no change in investment
please confirm if this is correct. revised definition impact on eligibility due
to the revised msme definition my eligibility under schemes is affected kindly
clarify whether benefits already availed will continue. the operational procedural
policy and institutional causes of these grievances include
- Policy and Schemes. DBT / IT desk including Annual Report. dbt it desk including
the annual report in msme refers to the data dbt wing functioning under the office
of the development commissioner msme which is responsible for administering direct
benefit transfer dbt of subsidies under msme schemes managing it and digital infrastructure
and compiling the ministry s annual report. the wing oversees end-to-end dbt processes
for scheme reimbursements such as ict and cloud computing subsidies where msmes
initially incur eligible expenses and subsequently receive reimbursements directly
into aadhaar-linked bank accounts through the public financial management system
often after technical verification by agencies like telecommunications consultants
india limited. it ensures compliance with national dbt standards in coordination
with the dbt mission and national informatics centre maintains and upgrades msme
it systems including the udyam registration portal supports cloud-based it adoption
for msmes undertakes data analytics and mis reporting and onboards schemes to
the national dbt framework. the wing also prepares the annual report of the ministry
of msme consolidating performance indicators financial outlays scheme outcomes
udyam registration trends and macro-level contributions such as msme share in
gdp and employment which are used for parliament cabinet briefings and policy
evaluation. while this framework promotes transparency leak-proof subsidy delivery
evidence-based policymaking and digital efficiency stakeholders frequently raise
grievances related to dbt execution data accuracy it reliability and reporting
quality. examples of grievances include msmes experiencing delays in receipt of
approved ict or cloud service subsidies due to pfms transaction or verification
glitches reimbursement failures arising from aadhaar bank account linkage mismatches
despite valid udyam registration inaccuracies or under-reporting of scheme achievements
udyam registrations or msme gdp contribution in the annual report affecting policy
advocacy and planning temporary downtime or access issues on udyam or other msme
it portals during registration or subsidy claim periods and gaps in mis capture
where scheme data duplications or leakages are not properly reflected in dbt dashboards
or the annual report prompting appeals for correction and system strengthening.
- UAM/Udyam Registration/Certificate related issues. Time Taken for Cancellation
of UDYAM Certificate (Technical). this category refers to grievances concerning
delays in processing requests for cancellation of an existing udyam registration.
when a business owner submits a request to cancel a registration the request is
expected to be processed within a reasonable timeframe. however in some cases
users report that the cancellation request remains pending for an extended period.
grievances under this category usually involve complaints where the enterprise
owner has already submitted a cancellation request but the status continues to
show as pending or unprocessed. entrepreneurs may also report that they cannot
proceed with other actions related to their registration because the cancellation
has not yet been completed. in some situations users may have submitted the request
multiple times or may be seeking clarification about the delay in processing the
cancellation. these grievances are typically raised by msme proprietors partners
company directors or authorized representatives who previously requested cancellation
of their enterprise registration. business owners who closed their operations
or who submitted cancellation due to incorrect registration details may seek updates
on the status of their request. compliance managers accountants or consultants
handling enterprise registrations may also raise grievances when the cancellation
process takes longer than expected or prevents further registration-related actions
from being completed.
- source_sentence: sri fund for new unit iron handicrafts manufacturing unit issue
application for self reliant fund sri fund for new unit context the user is requesting
application for self reliant fund sri fund for a new unit specifically for an
iron handicrafts manufacturing unit. details - fund type sri fund unit type new
unit industry iron handicrafts manufacturing
sentences:
- UAM/Udyam Registration/Certificate related issues. Updation of Email ID/Mobile
No. Linked to UDYAM Certificate. this category includes grievances related to
updating or correcting the email id or mobile number associated with an existing
udyam registration. contact details provided during registration are used for
communication verification and authentication when accessing the enterprise profile
on the portal. if these contact details become outdated incorrect or inaccessible
the enterprise owner may face difficulty receiving otps accessing the portal or
managing the registration information. common grievances under this category include
requests to change the registered mobile number or email address because the original
number is no longer active the sim card has been lost the email account is no
longer accessible or the contact details were entered incorrectly during registration.
some complaints arise when the registered contact details belong to an employee
or consultant who is no longer associated with the enterprise preventing the current
owner from receiving verification messages. in other cases entrepreneurs report
that they cannot update contact details because the system requires authentication
through the old mobile number or email which they no longer have access to. these
grievances are typically raised by msme owners proprietors partners directors
of companies or authorized representatives responsible for managing business registrations.
small business owners who registered their enterprise personally may request updates
when their phone number or email changes. in some cases accountants consultants
or administrative staff handling compliance activities may also submit grievances
when they cannot access the registration due to outdated contact details. this
category therefore represents issues related specifically to correcting or updating
communication details associated with an existing udyam certificate.
- Marketing and Skilling. Export Promotion/WTO. the export promotion and wto-related
initiatives for msmes comprise a set of integrated measures under india s ministry
of msme and the ministry of commerce to strengthen the export ecosystem for micro
small and medium enterprises. these include the export promotion mission with
a long-term financial outlay to support msme exports interest subvention on pre-
and post-shipment export credit to reduce borrowing costs credit guarantee coverage
for collateral-free export finance and reimbursement support for participation
in international trade fairs buyer meets and market development activities with
higher assistance for first-time exporters and priority groups. the initiatives
also provide policy and legal support to msmes in matters related to wto compliance
trade remedies such as anti-dumping cases and dispute settlement issues. together
with complementary export facilitation instruments these measures aim to enhance
msme competitiveness diversify export markets integrate enterprises into global
value chains support labour-intensive sectors and sustain msmes significant contribution
to india s overall exports. examples of common grievances under these initiatives
include interest subvention limitations an msme exporter reaches the prescribed
annual credit ceiling midway through the year resulting in partial interest relief
despite continued export shipments. credit guarantee shortfall an exporter seeking
higher-value export finance receives lower-than-expected guarantee coverage due
to risk assessment norms increasing collateral or margin requirements. trade fair
reimbursement rejection a first-time exporter is denied marketing assistance reimbursement
because the overseas exhibition attended was not on the approved list despite
generating confirmed buyer interest. wto-related support inadequacy an msme facing
an anti-dumping investigation receives limited financial assistance for legal
and advisory expenses leaving a large portion of costs uncovered. implementation
or rollout delays eligible exporters are unable to access benefits during pilot
or initial phases due to delays by banks or implementing agencies in operationalising
scheme guidelines.
- Starter, Credit and Finance. Self Reliant Fund (SRI Fund). the self reliant india
sri fund is a category designed to address grievances raised by growth-stage msme
owners manufacturing or technology-focused enterprises and startups transitioning
into a scale phase. the primary purpose of the sri fund is to provide equity support
to scalable msmes. however several issues and challenges hinder its effective
implementation leading to grievances from the target beneficiaries. key issues
and scenarios <NUM> . inability to access daughter funds lack of clarity on which
funds to approach no publicly available list or contact details referred by sidbi
to fund managers who do not respond no acknowledgment after submitting an expression
of interest <NUM> . excessive delays in the investment process due diligence stretching
over many months without a clear decision repeated requests for similar documents
frequent postponement of investment committee meetings leaving enterprises in
prolonged uncertainty <NUM> . rejection without transparency proposals declined
without stated reasons applications marked unsuitable despite meeting published
eligibility criteria verbal assurances of support later withdrawn without formal
communication <NUM> . eligibility and interpretation disputes fund managers applying
scheme guidelines inconsistently disputes over turnover thresholds treating registered
msmes as ineligible startups applying unclear sectoral restrictions unevenly across
applicants <NUM> . post-approval or post-commitment issues term sheets issued
but funds not disbursed conditions altered after approval funds backing out due
to internal policy changes operational procedural policy or institutional causes
- source_sentence: recently we registered ourselves for udyam registration but after
scanning the qr code verification is failing. issue qr code verification failure
for udyam registration context the user is reporting that qr code verification
is failing after registering for udyam registration. details - registration type
udyam registration verification issue qr code verification failure
sentences:
- Technology, Quality and Institutions. Related to NSIC. this category encompasses
grievances related to the support and facilitation services provided by the national
small industries corporation nsic to micro small and medium enterprises msmes
. the scope of this category includes issues arising from the areas of raw material
assistance market access and risk mitigation through guarantees. specifically
it covers situations where approved raw material assistance is not released on
time supplier coordination fails after nsic approval material supplied through
nsic is delayed or does not meet specifications or documentation and regional
office processes stall procurement. the category also captures failures in marketing
support including - delayed or missing inclusion in tenders gem or psu vendor
listings - late communication of bid opportunities - problems in nsic-sponsored
exhibitions or buyer-connect programs additionally it includes issues related
to performance and emd guarantees such as - delayed issuance - incorrect formats
- non-renewal despite payment - rejection by psus - lack of response when guarantees
are invoked these grievances typically result in missed orders blocked working
capital contract delays or loss of business credibility and arise from execution
coordination or service delivery breakdowns rather than policy interpretation.
the category is further divided into the following subcategories <NUM> . corporate
communication single point registration scheme and exhibition consortia and tender
marketing <NUM> . internal audit and law recovery <NUM> . human resource <NUM>
. vigilance law recovery <NUM> . international cooperation <NUM> . bank guarantee
monitoring <NUM> . finance accounts <NUM> . national sc st hub <NUM> . chief vigilance
officer <NUM> . contract procurement grievance officer <NUM> . digital services
facilitation and training <NUM> .space marketing cell event management cell <NUM>
.raw material assistance bank guarantee bill discounting bank tieup csr administration
<NUM> .technology liaison officer for sc st pwd cmr <NUM> .epf trust superannuation
pension trust <NUM> .center public information officers cpio <NUM> .company secretary
- Policy and Schemes. Definition of MSMEs (Clarifications related to definition)
Policy. this category pertains to grievances seeking policy interpretation and
clarification regarding the definition and classification of micro small and medium
enterprises msmes under the micro small and medium enterprises development msmed
act <NUM> as amended . the category encompasses disputes or doubts related to
the application of turnover investment and structural factors to specific enterprise
cases. key issues include turnover and investment threshold calculations treatment
of export turnover or goods and services tax gst classification of enterprises
as micro small or medium clubbing of multiple units or related businesses under
a single msme identity the category also captures concerns arising from the transition
between old and revised msme definitions including impact of reclassification
on eligibility continuity of benefits already availed applicable financial year
for revised criteria grievances in this category are clarification-driven rather
than system-error driven arising from the intersection of policy intent numerical
calculations and enterprise structure. example issues include turnover classification
discrepancies my turnover is within limits but udyam shows a higher msme category
please clarify the correct classification as per policy. export turnover treatment
export turnover has been included while determining msme status kindly clarify
whether it should be excluded. post-migration classification changes after migration
from uam to udyam my enterprise category has changed despite no change in investment
please confirm if this is correct. revised definition impact on eligibility due
to the revised msme definition my eligibility under schemes is affected kindly
clarify whether benefits already availed will continue. the operational procedural
policy and institutional causes of these grievances include
- UAM/Udyam Registration/Certificate related issues. QR Code Printed on UDYAM Certificate
Not Readable (Technical). this category includes grievances related to qr codes
printed on the udyam certificate that cannot be scanned or read properly. the
qr code is intended to allow quick verification of the certificate and its associated
enterprise information. if the qr code cannot be scanned users may face difficulty
verifying the certificate or sharing it for official purposes. grievances under
this category typically involve situations where the qr code on the downloaded
or printed certificate appears blurred distorted or unresponsive when scanned
with a qr reader. some users report that the qr code does not open any verification
page after scanning while others find that the scanning application fails to recognize
the code at all. these issues may arise due to errors during certificate generation
problems with the downloaded file or printing-related distortions that make the
qr code unreadable. these grievances are generally raised by msme owners proprietors
partners directors or authorized representatives who use the udyam certificate
as official documentation for their enterprise. small business owners who attempt
to share the certificate for verification purposes may discover that the qr code
is not functioning correctly. consultants accountants or administrative staff
responsible for maintaining business documentation may also submit grievances
when they identify that the qr code on the certificate cannot be scanned or verified.
- source_sentence: insurancy company national insurance company limited branch name
of insurance company branch if other khamgaon branch date of application <NUM>
- <NUM> - <NUM> policy number <NUM> my claim is kept pending even after submitting
all the documents after changing all the requirements as changed by various surveyors.
issue delayed insurance claim under national insurance company limited context
the user is reporting that the insurance claim submitted on <NUM> - <NUM> - <NUM>
with policy number <NUM> is still pending despite submission of all required documents
as per changes made by various surveyors. details - policy number <NUM> claim
submission date <NUM> - <NUM> - <NUM> branch khamgaon
sentences:
- Technology, Quality and Institutions. Official Language Related Issues. official
language related issues in msme administration concern the implementation of hindi
rajbhasha in accordance with the official languages act <NUM> as amended across
the ministry of msme its development institutes field offices and attached organizations.
this framework mandates progressive use of hindi in official work bilingual hindi
english documentation replies in hindi to communications received in hindi availability
of hindi-enabled software on computers and regular training in hindi typing and
computing for officials. the ministry monitors compliance through official language
implementation committees quarterly progress reviews rajbhasha inspections and
conferences while ensuring that citizens charters schemes portals and public-facing
information are available bilingually. these measures aim to improve accessibility
for hindi-speaking msmes enhance transparency and inclusiveness strengthen regional
outreach especially in hindi-belt states and fulfill constitutional and administrative
obligations without restricting the use of english where required. examples of
grievances include non-hindi reply an msme submits an application or grievance
in hindi to a development institute but receives a response only in english contrary
to official language correspondence rules. bilingual documentation gap key documents
such as annual reports scheme guidelines or notices are issued only in english
or with incomplete hindi translations limiting accessibility for hindi-speaking
stakeholders. training shortfall field office staff are unable to type or process
files in hindi despite mandated hindi software and training provisions causing
delays in rajbhasha compliance. portal language issue hindi versions of portals
like udyam or champions contain missing pages partial translations or technical
glitches preventing rural or hindi-only users from completing registrations or
filing grievances. awareness and communication lapse regional msmes are not informed
in hindi about official language conferences workshops or policy updates leading
to missed participation and reduced stakeholder engagement.
- Starter, Credit and Finance. Insurance Claim related issues. this category encompasses
grievances related to insurance claims associated with various government-backed
and private insurance products. the scope includes <NUM> . esic employees state
insurance corporation insurance benefits <NUM> . epfo employees provident fund
organisation -linked insurance benefits including edli employees deposit linked
insurance <NUM> . cgtmse credit guarantee fund trust for micro and small enterprises
-linked insurance elements <NUM> . private or general business insurance products
where a government department psu public sector undertaking or bank acts as an
intermediary or implementing authority the category covers a range of issues including
opaque rejection decisions undocumented policy exclusions administrative closure
without explanation shifting of risk and liability onto msmes micro small and
medium enterprises or employees document and data mismatches across multiple systems
such as aadhaar uan universal account number employer filings bank records insurance
portals delays and non-responsiveness at esic epfo insurer field office levels
manual bottlenecks officer transfers lack of accountability jurisdictional overlaps
involving labour compliance banking conditions inter-agency disputes between insurers
banks employers and labour authorities example issues include rejected esic medical
reimbursement claims due to ineligibility despite continuous contribution history
denied epfo edli insurance claims due to alleged break in service caused by employer-side
portal errors rejected bank-linked business insurance claims based on undisclosed
policy clauses unhonoured cg
- Technology, Quality and Institutions. Support for entrepreneurial and managerial
development of SMEs through incubators- an NMCP Scheme. the support for entrepreneurial
and managerial development of smes through incubators scheme under the national
manufacturing competitiveness programme nmcp is an initiative of the ministry
of msme designed to nurture innovative technology-driven and knowledge-based ideas
by providing structured incubation support through approved business incubators
hosted in technical academic or research institutions. under the scheme financial
assistance of up to <NUM> lakh is provided per idea or incubated unit for product
development testing validation and commercialisation with an overall ceiling of
<NUM> . <NUM> lakh per incubator to support up to <NUM> ventures. in addition
host institutions may receive up to <NUM> . <NUM> lakh for minor infrastructure
and facility upgrades to strengthen incubation capabilities. the scheme follows
a tripartite arrangement among the ministry the host institution and the incubatee
with incubated enterprises contributing <NUM> to <NUM> of project costs depending
on their category. through access to laboratories workshops shared infrastructure
mentoring technical guidance and early-stage seed funding the scheme aims to transform
innovative ideas into viable and sustainable micro and small enterprises expand
the base of innovation-led entrepreneurship and move msmes beyond traditional
manufacturing and service activities. examples of common grievances under the
incubator scheme include instalment release delay after approval the host institution
receives only a partial initial instalment delaying laboratory setup and stalling
progress for multiple approved incubated ventures. idea selection bias a technically
sound student or individual entrepreneur proposal is rejected despite meeting
eligibility criteria due to preference given to existing msmes by the host incubator.
mentoring shortfall an incubated unit receives sanctioned financial assistance
but does not get the promised industry mentoring technical handholding or market
linkage support needed for commercialization. infrastructure inadequacy the limited
infrastructure grant is insufficient to procure essential workshop or testing
equipment restricting practical experimentation and prototype development. contribution
dispute a micro enterprise is asked to contribute a higher percentage of project
cost applicable to small enterprises creating financial strain and disputes during
project execution.
- source_sentence: dear sir mam i am trying to register udyam with my pan but error
showing udyam registration has already done through this pan and i have not registered
earlier so please guide me aadhaar <uam_no> pan <pan_no> mobile <phone_no> issue
clarification on existing udyam registration context the user is requesting clarification
as the udyam registration portal indicates that registration has already been
done through the pan although the user states that no registration was made. details
- aadhar no <NUM> pan no gnips2021g mobile no <NUM>
sentences:
- UAM/Udyam Registration/Certificate related issues. Cancellation of UDYAM Certificate
Request. this category includes grievances related to requests for cancellation
or deactivation of an existing udyam registration. in some cases businesses that
were previously registered as msmes may no longer operate may have undergone structural
changes or may have been registered incorrectly. when such situations occur the
enterprise owner may wish to cancel the existing udyam certificate to prevent
incorrect records or to allow proper registration in the future. grievances under
this category typically include requests to cancel a registration because the
business has permanently closed the enterprise was registered by mistake or the
registration was created with incorrect information. some entrepreneurs also request
cancellation when duplicate registrations exist for the same enterprise and they
want only one valid record to remain. another common grievance arises when the
enterprise was registered earlier under outdated or incorrect details and the
owner wants the registration cancelled before creating a new one with correct
information. these grievances are usually raised by proprietors partners directors
of companies or authorized representatives of msmes who are responsible for maintaining
the official records of the enterprise. small business owners who registered their
enterprises earlier but later discontinued operations may also request cancellation
to avoid confusion or misuse of the registration. in some cases accountants consultants
or compliance officers working on behalf of the enterprise may submit the grievance
if they identify that the existing udyam registration is no longer valid or should
be removed from the records.
- Marketing and Skilling. National SC ST HUB. national sc-st hub nssh is a central
sector scheme launched in <NUM> by the ministry of micro small and medium enterprises
and implemented by the national small industries corporation to empower scheduled
caste and scheduled tribe entrepreneurs and strengthen their participation in
the msme ecosystem. the scheme focuses on capacity building market access financial
facilitation and handholding support while also operationalizing the mandatory
<NUM> procurement target for sc st owned mses under the public procurement policy
for mses <NUM> . through a network of national sc-st hub offices across the country
the hub assists eligible sc st entrepreneurs holding at least <NUM> ownership
and control in activities such as udyam and gem registration participation in
government tenders access to credit and skill upgradation. financial support is
provided in the form of reimbursements for testing and certification charges from
recognized laboratories bank loan processing and bank guarantee fees membership
fees of export promotion councils onboarding costs for e-commerce and government
procurement platforms and fees for short-term skill and management training programs
at reputed institutions. by reducing entry barriers and providing structured handholding
nssh aims to enhance competitiveness ensure inclusive growth and enable sc st
entrepreneurs to scale up operations and integrate with formal supply chains.
examples of grievances reported under the scheme include rejection of reimbursement
claims where testing or certification expenses exceed the prescribed financial
ceiling despite compliance with quality standards blockage of financial assistance
due to delays or discrepancies in caste certificate verification even when enterprises
are otherwise registered as sc st-owned instances where sc st msmes fail to secure
tenders despite the mandated procurement quota because of non-compliance by procuring
cpses partial reimbursement of approved training or capacity-building expenses
owing to scheme-specific limits leading to out-of-pocket costs for entrepreneurs
and gaps in timely support from local nssh offices particularly in remote or north-eastern
regions affecting onboarding to procurement portals and access to scheme benefits.
- UAM/Udyam Registration/Certificate related issues. Existing / Unauthorized UDYAM
Registration Against PAN. this category refers to grievances where an entrepreneur
discovers that a udyam registration already exists against their pan either due
to duplicate registration or because someone else created the registration without
their authorization. since pan is used as a key identifier for enterprise registration
the presence of an existing registration can prevent the legitimate owner from
creating a new one or managing the enterprise details. grievances under this category
usually include complaints about duplicate registrations created for the same
enterprise or multiple registrations linked to the same pan. some business owners
report that when they attempt to register their enterprise the system indicates
that a registration already exists even though they are unaware of creating one
earlier. in other cases entrepreneurs may find that an employee consultant former
partner or third party registered the enterprise using the business pan without
informing the owner. there may also be situations where an earlier registration
contains incorrect enterprise information leading to confusion about the valid
record. such grievances are generally raised by business proprietors partners
of partnership firms directors of companies or authorized representatives responsible
for registering the enterprise under msme. these complaints may also be submitted
by compliance managers accountants or consultants who are attempting to complete
the msme registration process for the business but encounter an existing record
linked to the pan. the purpose of raising this grievance is to identify the existing
registration verify its legitimacy and resolve conflicts arising from duplicate
or unauthorized registrations associated with the enterprise s pan.
pipeline_tag: sentence-similarity
library_name: sentence-transformers
metrics:
- pearson_cosine
- spearman_cosine
model-index:
- name: SentenceTransformer based on sentence-transformers/all-mpnet-base-v2
results:
- task:
type: semantic-similarity
name: Semantic Similarity
dataset:
name: Unknown
type: unknown
metrics:
- type: pearson_cosine
value: .nan
name: Pearson Cosine
- type: spearman_cosine
value: .nan
name: Spearman Cosine
---
# SentenceTransformer based on sentence-transformers/all-mpnet-base-v2
This is a [sentence-transformers](https://www.SBERT.net) model finetuned from [sentence-transformers/all-mpnet-base-v2](https://huggingface.co/sentence-transformers/all-mpnet-base-v2). It maps sentences & paragraphs to a 768-dimensional dense vector space and can be used for semantic textual similarity, semantic search, paraphrase mining, text classification, clustering, and more.
## Model Details
### Model Description
- **Model Type:** Sentence Transformer
- **Base model:** [sentence-transformers/all-mpnet-base-v2](https://huggingface.co/sentence-transformers/all-mpnet-base-v2) <!-- at revision e8c3b32edf5434bc2275fc9bab85f82640a19130 -->
- **Maximum Sequence Length:** 128 tokens
- **Output Dimensionality:** 768 dimensions
- **Similarity Function:** Cosine Similarity
<!-- - **Training Dataset:** Unknown -->
<!-- - **Language:** Unknown -->
<!-- - **License:** Unknown -->
### Model Sources
- **Documentation:** [Sentence Transformers Documentation](https://sbert.net)
- **Repository:** [Sentence Transformers on GitHub](https://github.com/huggingface/sentence-transformers)
- **Hugging Face:** [Sentence Transformers on Hugging Face](https://huggingface.co/models?library=sentence-transformers)
### Full Model Architecture
```
SentenceTransformer(
(0): Transformer({'max_seq_length': 128, 'do_lower_case': False, 'architecture': 'MPNetModel'})
(1): Pooling({'word_embedding_dimension': 768, 'pooling_mode_cls_token': False, 'pooling_mode_mean_tokens': True, 'pooling_mode_max_tokens': False, 'pooling_mode_mean_sqrt_len_tokens': False, 'pooling_mode_weightedmean_tokens': False, 'pooling_mode_lasttoken': False, 'include_prompt': True})
(2): Normalize()
)
```
## Usage
### Direct Usage (Sentence Transformers)
First install the Sentence Transformers library:
```bash
pip install -U sentence-transformers
```
Then you can load this model and run inference.
```python
from sentence_transformers import SentenceTransformer
# Download from the 🤗 Hub
model = SentenceTransformer("sentence_transformers_model_id")
# Run inference
sentences = [
'dear sir mam i am trying to register udyam with my pan but error showing udyam registration has already done through this pan and i have not registered earlier so please guide me aadhaar <uam_no> pan <pan_no> mobile <phone_no> issue clarification on existing udyam registration context the user is requesting clarification as the udyam registration portal indicates that registration has already been done through the pan although the user states that no registration was made. details - aadhar no <NUM> pan no gnips2021g mobile no <NUM>',
'UAM/Udyam Registration/Certificate related issues. Existing / Unauthorized UDYAM Registration Against PAN. this category refers to grievances where an entrepreneur discovers that a udyam registration already exists against their pan either due to duplicate registration or because someone else created the registration without their authorization. since pan is used as a key identifier for enterprise registration the presence of an existing registration can prevent the legitimate owner from creating a new one or managing the enterprise details. grievances under this category usually include complaints about duplicate registrations created for the same enterprise or multiple registrations linked to the same pan. some business owners report that when they attempt to register their enterprise the system indicates that a registration already exists even though they are unaware of creating one earlier. in other cases entrepreneurs may find that an employee consultant former partner or third party registered the enterprise using the business pan without informing the owner. there may also be situations where an earlier registration contains incorrect enterprise information leading to confusion about the valid record. such grievances are generally raised by business proprietors partners of partnership firms directors of companies or authorized representatives responsible for registering the enterprise under msme. these complaints may also be submitted by compliance managers accountants or consultants who are attempting to complete the msme registration process for the business but encounter an existing record linked to the pan. the purpose of raising this grievance is to identify the existing registration verify its legitimacy and resolve conflicts arising from duplicate or unauthorized registrations associated with the enterprise s pan.',
'Marketing and Skilling. National SC ST HUB. national sc-st hub nssh is a central sector scheme launched in <NUM> by the ministry of micro small and medium enterprises and implemented by the national small industries corporation to empower scheduled caste and scheduled tribe entrepreneurs and strengthen their participation in the msme ecosystem. the scheme focuses on capacity building market access financial facilitation and handholding support while also operationalizing the mandatory <NUM> procurement target for sc st owned mses under the public procurement policy for mses <NUM> . through a network of national sc-st hub offices across the country the hub assists eligible sc st entrepreneurs holding at least <NUM> ownership and control in activities such as udyam and gem registration participation in government tenders access to credit and skill upgradation. financial support is provided in the form of reimbursements for testing and certification charges from recognized laboratories bank loan processing and bank guarantee fees membership fees of export promotion councils onboarding costs for e-commerce and government procurement platforms and fees for short-term skill and management training programs at reputed institutions. by reducing entry barriers and providing structured handholding nssh aims to enhance competitiveness ensure inclusive growth and enable sc st entrepreneurs to scale up operations and integrate with formal supply chains. examples of grievances reported under the scheme include rejection of reimbursement claims where testing or certification expenses exceed the prescribed financial ceiling despite compliance with quality standards blockage of financial assistance due to delays or discrepancies in caste certificate verification even when enterprises are otherwise registered as sc st-owned instances where sc st msmes fail to secure tenders despite the mandated procurement quota because of non-compliance by procuring cpses partial reimbursement of approved training or capacity-building expenses owing to scheme-specific limits leading to out-of-pocket costs for entrepreneurs and gaps in timely support from local nssh offices particularly in remote or north-eastern regions affecting onboarding to procurement portals and access to scheme benefits.',
]
embeddings = model.encode(sentences)
print(embeddings.shape)
# [3, 768]
# Get the similarity scores for the embeddings
similarities = model.similarity(embeddings, embeddings)
print(similarities)
# tensor([[1.0000, 0.7751, 0.1988],
# [0.7751, 1.0000, 0.2777],
# [0.1988, 0.2777, 1.0000]])
```
<!--
### Direct Usage (Transformers)
<details><summary>Click to see the direct usage in Transformers</summary>
</details>
-->
<!--
### Downstream Usage (Sentence Transformers)
You can finetune this model on your own dataset.
<details><summary>Click to expand</summary>
</details>
-->
<!--
### Out-of-Scope Use
*List how the model may foreseeably be misused and address what users ought not to do with the model.*
-->
## Evaluation
### Metrics
#### Semantic Similarity
* Evaluated with [<code>EmbeddingSimilarityEvaluator</code>](https://sbert.net/docs/package_reference/sentence_transformer/evaluation.html#sentence_transformers.evaluation.EmbeddingSimilarityEvaluator)
| Metric | Value |
|:--------------------|:--------|
| pearson_cosine | nan |
| **spearman_cosine** | **nan** |
<!--
## Bias, Risks and Limitations
*What are the known or foreseeable issues stemming from this model? You could also flag here known failure cases or weaknesses of the model.*
-->
<!--
### Recommendations
*What are recommendations with respect to the foreseeable issues? For example, filtering explicit content.*
-->
## Training Details
### Training Dataset
#### Unnamed Dataset
* Size: 88 training samples
* Columns: <code>sentence_0</code> and <code>sentence_1</code>
* Approximate statistics based on the first 88 samples:
| | sentence_0 | sentence_1 |
|:--------|:-------------------------------------------------------------------------------------|:-------------------------------------------------------------------------------------|
| type | string | string |
| details | <ul><li>min: 46 tokens</li><li>mean: 118.39 tokens</li><li>max: 128 tokens</li></ul> | <ul><li>min: 128 tokens</li><li>mean: 128.0 tokens</li><li>max: 128 tokens</li></ul> |
* Samples:
| sentence_0 | sentence_1 |
|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| <code>sub - request for clarification on msme dev act <NUM> . dear sir <NUM> . your august office is kindly requested to define the specific word _x0080__x009c_tender _x0080__x009d_ as referred in the public procurement policy for micro and small enterprises mse _x0080__x0099_s order gazetted notification no. d.l.- <NUM> <NUM> dtd. <NUM> . <NUM> . <NUM> sub sec <NUM> heading as price quotation in tenders and further word _x0080__x009c_rate contract _x0080__x009d_ as referred in sub sec <NUM> developing micro and small enterprises vendors before substitution dt. <NUM> . <NUM> . <NUM> as extracted. _x0080__x009c_7. developing micro and small enterprise vendors. _x0080__x0093_the central ministries or departments or public sector undertakings shall take necessary steps to develop appropriate vendors by organizing vendor development programmes or buyer-seller meets and entering into rate contract with micro and small enterprises for a specified period in respect of periodic requirements also. _x...</code> | <code>Policy and Schemes. Related to Public Procurement by PSUs. this category pertains to grievances related to public sector undertakings psus violating or diluting mandatory msme procurement norms under the public procurement policy for msmes <NUM> and related guidelines including gem . the scope encompasses cases where psus fail to meet prescribed msme procurement quotas deny msmes their l1 price-matching rights bypass eligible msme vendors despite valid registration or design tenders with disproportionate eligibility conditions that effectively exclude msmes. key issues and scenarios within this category include failure to meet msme procurement quotas denial of l1 price-matching rights to msmes bypassing eligible msme vendors despite valid registration designing tenders with disproportionate eligibility conditions such as excessive turnover requirements prior psu experience requirements high emd pbg requirements unnecessary technical specifications post-award payment delays including wi...</code> |
| <code>banks approved clcs-tu loan for new machines but subsidy claim is rejected over minor tech list mismatch despite empanelled vendor. this ties up my finance without <NUM> aid. release subsidy and simplify verification for tech upgrades.special clcs-tu for sc st promises <NUM> subsidy but nodal agency delays processing my plant machinery finance claim for months with extra document demands. please fast-track special aid and approve higher subsidy for sc st beginners. issue delayed subsidy claim and non-approval under clcs-tu and special clcs for sc st context the user is reporting delayed subsidy claim and non-approval under clcs-tu and special clcs for sc st schemes citing minor technical list mismatch and extra document demands and requesting simplification of verification and fast-tracking of special aid. details - issue with clcs-tu loan minor tech list mismatch issue with special clcs for sc st delayed processing and extra document demands requested action simplify verification and ...</code> | <code>Starter, Credit and Finance. Credit Linked Capital Subsidy for Technology Upgradation (CLCS- TU) & Special CLCS for SC&ST. credit linked capital subsidy scheme for technology upgradation clcss tu and the special clcs for sc st entrepreneurs is a flagship technology modernisation program of the ministry of micro small and medium enterprises designed to help micro and small manufacturing enterprises upgrade to proven state-of-the-art technologies. under the standard clcss tu eligible mses receive an upfront capital subsidy of <NUM> on institutional term loans used for purchasing approved plant and machinery subject to a maximum subsidy of <NUM> lakh on an eligible investment ceiling of <NUM> crore across notified sub-sectors. the scheme is implemented through nodal agencies such as small industries development bank of india national bank for agriculture and rural development and national institute for entrepreneurship and small business development with technical vetting by expert bodies...</code> |
| <code>i am unable to change enterprise name or trade name in my udayam certificate pls give proper solution issue update of enterprise trade name in udyam certificate context the user is requesting an update of the enterprise trade name in the udyam certificate. details - enterprise trade name update required</code> | <code>UAM/Udyam Registration/Certificate related issues. Update Company/Owner Name Details. this category includes grievances related to corrections or updates to the name of the enterprise or the name of the owner associated with a udyam registration. accurate naming details are important for maintaining correct enterprise records and ensuring that the information recorded in the registration reflects the official business identity. grievances under this category typically arise when the name of the enterprise or the owner s name recorded during registration contains an error or needs to be updated due to changes in the business structure. for example the enterprise name may have been entered incorrectly during registration or the owner s name may not match official identification documents. in some cases the enterprise name may change due to business rebranding conversion of the business structure or correction of typographical errors made during the registration process. users may also re...</code> |
* Loss: [<code>CachedMultipleNegativesRankingLoss</code>](https://sbert.net/docs/package_reference/sentence_transformer/losses.html#cachedmultiplenegativesrankingloss) with these parameters:
```json
{
"scale": 20.0,
"similarity_fct": "cos_sim",
"mini_batch_size": 32,
"gather_across_devices": false
}
```
### Training Hyperparameters
#### Non-Default Hyperparameters
- `per_device_train_batch_size`: 32
- `per_device_eval_batch_size`: 32
- `num_train_epochs`: 5
- `fp16`: True
- `multi_dataset_batch_sampler`: round_robin
#### All Hyperparameters
<details><summary>Click to expand</summary>
- `do_predict`: False
- `eval_strategy`: no
- `prediction_loss_only`: True
- `per_device_train_batch_size`: 32
- `per_device_eval_batch_size`: 32
- `gradient_accumulation_steps`: 1
- `eval_accumulation_steps`: None
- `torch_empty_cache_steps`: None
- `learning_rate`: 5e-05
- `weight_decay`: 0.0
- `adam_beta1`: 0.9
- `adam_beta2`: 0.999
- `adam_epsilon`: 1e-08
- `max_grad_norm`: 1
- `num_train_epochs`: 5
- `max_steps`: -1
- `lr_scheduler_type`: linear
- `lr_scheduler_kwargs`: None
- `warmup_ratio`: None
- `warmup_steps`: 0
- `log_level`: passive
- `log_level_replica`: warning
- `log_on_each_node`: True
- `logging_nan_inf_filter`: True
- `enable_jit_checkpoint`: False
- `save_on_each_node`: False
- `save_only_model`: False
- `restore_callback_states_from_checkpoint`: False
- `use_cpu`: False
- `seed`: 42
- `data_seed`: None
- `bf16`: False
- `fp16`: True
- `bf16_full_eval`: False
- `fp16_full_eval`: False
- `tf32`: None
- `local_rank`: -1
- `ddp_backend`: None
- `debug`: []
- `dataloader_drop_last`: False
- `dataloader_num_workers`: 0
- `dataloader_prefetch_factor`: None
- `disable_tqdm`: False
- `remove_unused_columns`: True
- `label_names`: None
- `load_best_model_at_end`: False
- `ignore_data_skip`: False
- `fsdp`: []
- `fsdp_config`: {'min_num_params': 0, 'xla': False, 'xla_fsdp_v2': False, 'xla_fsdp_grad_ckpt': False}
- `accelerator_config`: {'split_batches': False, 'dispatch_batches': None, 'even_batches': True, 'use_seedable_sampler': True, 'non_blocking': False, 'gradient_accumulation_kwargs': None}
- `parallelism_config`: None
- `deepspeed`: None
- `label_smoothing_factor`: 0.0
- `optim`: adamw_torch_fused
- `optim_args`: None
- `group_by_length`: False
- `length_column_name`: length
- `project`: huggingface
- `trackio_space_id`: trackio
- `ddp_find_unused_parameters`: None
- `ddp_bucket_cap_mb`: None
- `ddp_broadcast_buffers`: False
- `dataloader_pin_memory`: True
- `dataloader_persistent_workers`: False
- `skip_memory_metrics`: True
- `push_to_hub`: False
- `resume_from_checkpoint`: None
- `hub_model_id`: None
- `hub_strategy`: every_save
- `hub_private_repo`: None
- `hub_always_push`: False
- `hub_revision`: None
- `gradient_checkpointing`: False
- `gradient_checkpointing_kwargs`: None
- `include_for_metrics`: []
- `eval_do_concat_batches`: True
- `auto_find_batch_size`: False
- `full_determinism`: False
- `ddp_timeout`: 1800
- `torch_compile`: False
- `torch_compile_backend`: None
- `torch_compile_mode`: None
- `include_num_input_tokens_seen`: no
- `neftune_noise_alpha`: None
- `optim_target_modules`: None
- `batch_eval_metrics`: False
- `eval_on_start`: False
- `use_liger_kernel`: False
- `liger_kernel_config`: None
- `eval_use_gather_object`: False
- `average_tokens_across_devices`: True
- `use_cache`: False
- `prompts`: None
- `batch_sampler`: batch_sampler
- `multi_dataset_batch_sampler`: round_robin
- `router_mapping`: {}
- `learning_rate_mapping`: {}
</details>
### Training Logs
| Epoch | Step | spearman_cosine |
|:-----:|:----:|:---------------:|
| 1.0 | 3 | nan |
| 2.0 | 6 | nan |
| 3.0 | 9 | nan |
| 4.0 | 12 | nan |
| 5.0 | 15 | nan |
### Framework Versions
- Python: 3.12.12
- Sentence Transformers: 5.2.3
- Transformers: 5.0.0
- PyTorch: 2.10.0+cu128
- Accelerate: 1.12.0
- Datasets: 4.0.0
- Tokenizers: 0.22.2
## Citation
### BibTeX
#### Sentence Transformers
```bibtex
@inproceedings{reimers-2019-sentence-bert,
title = "Sentence-BERT: Sentence Embeddings using Siamese BERT-Networks",
author = "Reimers, Nils and Gurevych, Iryna",
booktitle = "Proceedings of the 2019 Conference on Empirical Methods in Natural Language Processing",
month = "11",
year = "2019",
publisher = "Association for Computational Linguistics",
url = "https://arxiv.org/abs/1908.10084",
}
```
#### CachedMultipleNegativesRankingLoss
```bibtex
@misc{gao2021scaling,
title={Scaling Deep Contrastive Learning Batch Size under Memory Limited Setup},
author={Luyu Gao and Yunyi Zhang and Jiawei Han and Jamie Callan},
year={2021},
eprint={2101.06983},
archivePrefix={arXiv},
primaryClass={cs.LG}
}
```
<!--
## Glossary
*Clearly define terms in order to be accessible across audiences.*
-->
<!--
## Model Card Authors
*Lists the people who create the model card, providing recognition and accountability for the detailed work that goes into its construction.*
-->
<!--
## Model Card Contact
*Provides a way for people who have updates to the Model Card, suggestions, or questions, to contact the Model Card authors.*
--> |