1 / 12

OPMIS Officer Programs Management Information System 2001

Learn about the history, objectives, and technology upgrade plans for OPMIS, a decision support tool for CNET headquarters. Find out why an upgrade is necessary and the benefits of a server-based approach. Contact points provided.

mron
Download Presentation

OPMIS Officer Programs Management Information System 2001

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OPMIS OFFICER PROGRAMS MANAGEMENT INFORMATION SYSTEM2001 PCO/PXO Conference

  2. OPMIS – a brief history • Current version implemented in ’92 • Purpose • Collector of management information for CNET • Headquarters decision support tool • Does not focus on Unit IT needs • Developed using MS DOS Oracle

  3. OPMIS Objectives • Redesign current DOS Oracle application • Eliminate redundant development by NROTC Units • Develop WEB accessible application where possible • Better address the needs of the customer • Use server based architecture to reduce PC support requirements

  4. Why Upgrade OPMIS? • Oracle DOS version not supported • Requires re-boot from Windows • Lacks integration • To the desktop (Word, Excel, Powerpoint) • To the WEB • Forces Unit application development • Single user access • Does not address Unit requirements

  5. Technology Upgrade Plans • Better address Unit requirements • Implement Unit intranets • Use/augment Unit LAN infrastructure • Use WEB where possible • Integrate desktop & database • Word forms, recruiting letters, etc.

  6. NROTC Unit Strategy • Server at Each NROTC Unit • Running Microsoft NT Terminal Server • CITRIX Metaframe as required • Microsoft Office Products • Access by All Staff Members • Consortium Access from Member Units • Headquarters Requirements as a By-product

  7. Why a Server Based Approach? • Application maintained at server not client • Reduces remote support/trouble desk requirements • Changes passed to 70 servers vice 800 PC’s • Compatibility with existing unit LANS • Novell, Unix, NT, Apple Talk, etc. • Extremely low communication bandwidth • Only passes key clicks, mouse movements and screen paints

  8. OPMIS Server Deployment • On-going through September 2001 • Dollars for deployment expire Oct 2001 • CIO desire to deploy prior to NMCI • Virtual Private Network (VPN) at each unit • Allows access to NMCI without impacting EDU requirements • Will require involvement by university network administration

  9. CURRENT INITIATIVES • OPMIS Technology Upgrade • Headquarters Selection/Placement – done • Summer Cruise – done • Student administration • Prototype to CNET staff – Sept. 01 • Prototype to NROTC Units – Oct. 01 • Site Integration testing – Nov. 01 • Phased implementation – Dec. 01 • NROTC Unit requirements

  10. Points of Contact • Connie Thomsen • (850) 452-1001 ext 1341 DSN 922-1001 • connie.thomsen@cnet.navy.mil • Charlie Odom (Technical Support) • (850) 452-1001 ext 1238 DSN 922-1001 • charlie.odom@cnet.navy.mil • Code 612 (OPMIS Questions) • (850) 452-1001 ext 1343

More Related