Mainframe Natural Adabas(W2)

BVMS (Bus Vehicle Maintenance System) is a Mainframe Natural/ADABAS application used to manage our fleet of Revenue Bus vehicles, located at the various NJ Transit Garages, detailing all their maintenance.  
This application is used to track all the maintenance details for each Bus, from its initial procurement to final decommission, including all maintenance services, repairs parts replacement, etc.  This includes tracking all the parts in each bus along with the related procurement, inventory, decommission, etc.  
Scope
Purpose
The purpose of this engagement is to provide technical, analytical, and strategic support services for the Bus Vehicle Maintenance System (BVMS), a legacy application operating in NJ TRANSIT’s IBM mainframe environment. The Contractor shall provide comprehensive lifecycle services including analysis, documentation, maintenance, enhancement, and user support.
Objectives
The Contractor shall ensure that BVMS remains stable, supportable, accurate, and aligned with NJ TRANSIT Bus and Garage maintenance teams’ operational needs by delivering:
Reliable application support
Understanding of NJ TRANSIT’s Clear business requirements
Accurate and current documentation
High-quality maintenance and enhancement services
Proactive performance tuning using diagnostic and optimization tools
Strategic modernization and re-platforming guidance
Knowledge transfer to NJ TRANSIT personnel
Scope Boundaries
Included in this engagement:
BVMS application analysis, support, and documentation
Integration support for other NJ Transit systems that interact with BVMS
Maintenance of Natural/ADABAS code and associated online/batch workflows
Performance analysis and execution optimization of the Natural/ADABAS codebase
Excluded from this engagement:
Support for non-BVMS applications unless explicitly included
Hardware or software procurement
Enterprise-wide fleet management system redevelopment

Application Support and Maintenance
The Contractor shall support and maintain the BVMS application on the NJ Transit mainframe.  Key responsibilities are:
Manage the full application lifecycle of BVMS, including budgeting, funding, billing, and accounting for capital projects.
Engage with end users to gather business requirements and provide system support.
Provide ongoing application support, maintenance, and implement requested changes.
Address short-term maintenance needs and resolve system defects.
Performance SLA:
Any issues impacting Bus operations needs to be resolved be able to provide 7x24 on-call support .
All critical/emergency application changes shall be completed within 4 hours or sooner, depending on the business criticality of the change.
All normal application changes shall be completed within 1 business day or sooner, depending on the business criticality of the change.
Any application change requiring more than 1 business day should be reviewed with the NJ Transit lead, target delivery ETA documented and adhered to.
System Documentation (Updated as Required)
The Contractor shall develop and maintain comprehensive system documentation. Documentation shall be created or updated whenever new system changes are implemented.
Documentation should include, minimally:
Architecture diagrams, module descriptions, data structures, and data flows
Functional descriptions of business rules, processes, and workflows
Natural, ADABAS, JCL, and batch processing documentation
Interface specifications to other NJ Transit Bus and Garage related systems
Revision logs with date, author, and scope of update
Performance SLA:
Documentation updates shall be completed within 2 business days of final migration of any approved system change.
Documentation gaps identified jointly by NJ TRANSIT and Contractor shall be addressed within 5 business days.
Business Requirements Documentation
Contractor shall collect, analyze, and validate business requirements from end users.
Deliverables include:
Requirements statements
Stakeholder sign-off
Requirements traceability matrix
Performance SLA:
Critical/Emergency changes
Requirements sessions scheduled within 30 minutes of request.
Requirements documents delivered within 2 business days of implementation.
Normal changes
Requirements sessions scheduled within 1 business day of request.
Requirements documents delivered within 2 business days of final interview.


Professional Services Supporting
Capital Planning Tool (CPAS)
Background
CPAS (Capital Project Accounting System) is a Mainframe Natural/ADABAS application used to manage the Budgets, Funding, Billing and other related Accounting details for all NJ Transit Capital Projects.  
This application handles the entire project lifecycle from Grants administration, Receipts, Payments, etc. along with the various reporting needs to support Project Management/Tracking, Legal, Funding, Grant, etc.
Scope
Purpose
The purpose of this engagement is to provide technical, analytical, and strategic support services for the Capital Project Accounting System (CPAS), a legacy application operating in NJ TRANSIT’s IBM mainframe environment. The Contractor shall provide comprehensive lifecycle services including analysis, documentation, maintenance, enhancement, and user support.
Objectives
The Contractor shall ensure that CPAS remains stable, supportable, accurate, and aligned with NJ TRANSIT Capital Project team’s operational needs by delivering:
Reliable application support
Understanding of NJ TRANSIT’s business requirements
Accurate and current documentation
High-quality maintenance and enhancement services
Proactive performance tuning using diagnostic and optimization tools
Strategic modernization and re-platforming guidance
Knowledge transfer to NJ TRANSIT personnel
Scope Boundaries
Included in this engagement:
CPAS application analysis, support, and documentation
Integration support for AR, AP, GL, and other NJ Transit systems
Maintenance of Natural/ADABAS code and associated online/batch workflows
Performance analysis and execution optimization of the Natural/ADABAS codebase
Excluded from this engagement:
Support for non-CPAS applications unless explicitly included
Hardware or software procurement
Enterprise-wide financial system redevelopment