NIAPS Glossary of Terms

NIAPS Glossary of Terms
Amendment Server	The amendment server is the central repository for all Distance Support data and is located at NSWC Crane Division. NIAPS is installed on US Navy vessels. The amendment server is a data transfer agent which ensures the safe and secure transfer of data between the ship and NSWC Crane Division. The amendment server holds the master catalog of all amendments.
Amendments	"Amendments," as they relate to NIAPS, are highly compressed files readable only by the NIAPS system that contain changes to web based content, training materials, ship manuals, technical drawings, human resource data, sensor data and other data that is intended to reside on NIAPS. Amendments are generated and published through dedicated amendment servers (also known as Knowledge Management Centers) by the NIAPS team at NSWC Crane.
Application	Any software product that uses an existing operating system software program to provide the user with a specific capability or function that is independent of other “applications.” If it is dependent on other applications it becomes a system. See "system."
Application Owner	See Product Owner
Client Side Application	As it pertains to a NIAPS request type, a "client side application" is a product that is installed on client workstations and accesses data on NIAPS using the shipboard LAN. "Client-side" refers to operations that are performed by the client in a client–server relationship in a computer network. A client-side executable is an application that runs on a user's local computer or workstation and connects to a server as necessary. Operations may be performed client-side because they require access to information or functionality that is available on the client but not on the server, because the user needs to observe them or provide input, or because the server lacks the processing power to perform the operations in a timely manner for all of the clients it serves. Programs that run on a user's local computer without ever sending or receiving data over a network are not considered clients, and so the operations of such programs would not be considered client-side operations. Product examples that are this type of NIAPS request: eSOMS, Sailor to Engineer (S2E), ATIS.
Code Freeze	Code Freeze is a NIAPS milestone at which point all code for a NIAPS candidate must be received for testing. No functional changes to the application candidate are allowed after code freeze. Bug fixes are allowed after this milestone but only up until the Code Lockdown milestone date. By code lockdown, the code must be fully functional and a silent installer is in place. The code freeze milestone date for a NIAPS release is identified in the NIAPS Information Center.
Code Lockdown	Code Lockdown is a NIAPS milestone which occurs after the NIAPS milestone “Code Freeze.” The Code Lockdown milestone is one at which point all code (including bug fixes) for a NIAPS candidate are in place. At this point, the application candidate must be completely functional. No additional code will be received for the candidate after the code lockdown milestone unless it is to fix a security vulnerability or is needed by the Distance Support Lab to allow the product to properly integrate with other applications for a NIAPS release. Other than this, no additional code will be allowed to be received. The code at this point would be considered the final code that would be included on a NIAPS release. The code lockdown milestone date for a NIAPS release is identified in the NIAPS Information Center.
COMPOSE	The Common PC Operating System Environment as it relates to NIAPS provides a common, integrated, standardized Windows software based operating system environment for NIAPS to work in.
Connected Environment	The IT environment onboard a ship or sub when it is in an Radio Frequency (RF) connected state.
Content Only	As it pertains to a NIAPS request type, a "content only" application is a product that has static content which is accessed through the web or through file sharing. A "content only" product has no active code and is usually updated through the NIAPS amendment process. Product examples that are this type of NIAPS request: DoN Instructions (DONI), Navy Engineering Drawing System (NEDS).
Core Application	As it pertains to a NIAPS request type, a "core application" (also known as a "framework application") is a software product that, when used collectively with other core applications, allow NIAPS to function. Core applications used together form the software framework used by the NIAPS engineering team to implement the standard functionality of NIAPS. Product examples that are this type of NIAPS request: Microsoft Internet Information Server (IIS), Microsoft Internet Explorer, Microsoft .NET Framework, Microsoft SharePoint Portal Server, Geo Replicator.
Data	Information used in the logic of an application. In general, data is information stored in a database or in a data oriented file type. Types of data can include (but are not limited to) databases (MS SQL, MS Access, etc.); other raw data (XML, TXT, CSV, etc.)
Data Pass Through Application	As it pertains to a NIAPS request type, a "data pass through" application only use NIAPS as a replication agent for data transfer to applications or systems that reside external to NIAPS. Product examples that are this type of NIAPS request: ICAS, Data Qualifying Engine (DQE).
Disconnected Environment	The IT environment onboard a ship or sub when it is NOT in an Radio Frequency (RF) connected state. The is the IT environment that the NIAPS is built for.
Distance Support (DS)	The Chief of Naval Operations (CNO) approved, United States Fleet Forces (USFF) implemented concept to provide mission and personnel specific data, information, and knowledge within a ship while minimizing off-ship bandwidth requirement for connected and disconnected operations.
Distance Support Innovation Lab (DSIL)	The Distance Support Innovation Lab (DSIL) is responsible for integration, testing and documenting consolidation of the NIAPS releases; research and development for new technology insertion; emergent requirements (technical, operational, programmatic, fleet technology demonstrations and insertions); and customer/Fleet support. The DSIL is located at NSWC Crane, Indiana.
Distance Support Portal (DS Portal)	Provides access to NIAPS software, applications, and system support on board ship. (Note: Does not access off-ship websites). The DS portal is accessible by double-clicking the Distance Support Portal icon.
Distance Support Portal Icon (DS Icon)	An icon that can be pushed to each desktop on a ship from the COMPOSE domain controller on board ship that will provide access to the Distance Support Portal and applications that are hosted within the NIAPS environment.
Executable	An application or code that must be compiled in order to run. For the NIAPS program, the types of code considered (but not limited to) to be executables include: Java Files (e.g., jar, ear, war, etc.) Batch Files (e.g., BAT, etc. Active Server Pages (e.g., ASP, .NET, etc.) Run-time Libraries (e.g., DLL, etc.) Executables (e.g., EXE, etc.)
Framework	The NIAPS "framework" is a supporting architecture of products designed to support and allow various NIAPS products to operate properly. Examples of "framework" products include (but not limited to) SQL Server, Internet Information Server (IIS), antivirus software, backup software, replication software and secure data transport software.
Full Release	A NIAPS Full release is a major NIAPS release version whose version number will ends with ".0" (Ex: NIAPS v3.0). A Full NIAPS version release requires an Alteration Installation Team (AIT) to install (i.e. a ship visit). Typically, full releases result from changes to the underlying NIAPS infrastructure (i.e. framework) software or security posture.
Join NIAPS Request (JNR) Process	The Join NIAPS Request process refers to requests (NIAPS Requests submitted via Dimensions) by product owners to have their products integrated, tested and deployed on a NIAPS release.
Knowledge Management Center (KMC)	See "Amendment Server."
Manual Replication	NIAPS provides for a capability referred to as manual replication. Manual replication is intended for updates that are low priority or are significantly large. This allows the NIAPS System Administrator to download updates during times of optimum bandwidth to lessen the impact on higher priority communications.
Navy Information Application Product Suite (NIAPS)	NIAPS is a suite of applications, all integrated together in a single server. NIAPS can be categorized as a shipboard intranet web-based information system used to support, collect, distribute, and display information in a COMPOSE shipboard environment. This system hosts an intranet that maintains information such as, but not limited to: training courses, maintenance documents and data collection, and morale and welfare information. NIAPS provides content and information to users during times that network access external to the ship is unavailable. Much of the information contained within NIAPS can be updated regularly through a process called data replication or simply "replication." This process can occur both in port and underway; the latter is subject to limitations due to underway operations and communications capabilities. Replication will allow users throughout the ship to have access to the most current information and changes available for the content and applications residing within NIAPS. Other notes of interest related to NIAPS: NIAPS can be fielded in both a NIPRNet and SIPRNet environment It is deployed on to the IT-21 shipboard environment It is configured for a specific ship or hull platform It delivers a knowledge management system that integrates into the framework of a ship's day-to-day work environment. It is designed to use the smallest amount of bandwidth possible. It securely replicates data ship-to-shore or shore-to-ship while at the same time keeping data synchronized and up-to-date.
NIAPS Information Center	The NIAPS Information Center contains all of the information that a prospective NIAPS customer would need to know about the processes and business rules that support NIAPS.
NIAPS Request (NR) Form	The NIAPS Request (NR) form is a web-based form located on the Distance Support website that allows a potential NIAPS customer the ability to submit their product to be considered for inclusion on NIAPS. Also known as a 'Join NIAPS' Request (JNR) form, the form provides all of the information that the various NIAPS action activities will need to evaluate the product for inclusion on a NIAPS release. Filling out and submitting the NR form is the first step in the NIAPS process.
NIAPS Training Support Agent (TSA)	NSWC Crane is tasked to be the NIAPS Training Support Agent (TSA). The NIAPS TSA is responsible for providing NIAPS system administration training, NIAPS user training and providing train-the-trainer services for all shipboard NIAPS products and Distance Support operations. The NIAPS TSA will ensure that adequate training material is available for each product that resides on the NIAPS system. When necessary, the training effort could include training development, coordination, administration and documentation of materials. The NIAPS TSA resides at NSWC Carderock Division, Philadelphia (NAVSEA Philadelphia).
NIAPS Update Request (NUR) Process	The NIAPS Update Request process allows a NIAPS product owner the ability to update and modify their deployed product when warranted. The NUR process is accomplished by submitting an NUR through Dimensions.
Point Release	A NIAPS Point release is a a NIAPS release that occurs between full NIAPS version releases. This type of NIAPS release usually does not require an ship visit by an Alteration Installation Team (AIT) and is usually distributed over the network or via DVD. A Point release is usually installed by the ship's force.
Product (Application) Owner	The individual/Program Office, or "customer," requesting product integration via the Join NIAPS process. The individual who completes the NIAPS Request in Dimensions will be considered the main point of contact throughout the NIAPS process.
Publications	"Publications," as they relate to NIAPS, are comprised of web based content, training materials, ship manuals, technical drawings, human resource data, sensor data, and other data intended to reside on NIAPS. Publications consist of the base information loaded by NSWC Crane onto the server NIAPS rides on. Amendments (changes to the base data) would not be possible without publications (base data). Publications are generated and published by the NIAPS team at NSWC Crane.
Replication	The transfer of data between servers as it pertains to DS and NIAPS. Use of NIAPS applications generates replication files that are transferred from ship-to-shore or shore-to- ship either manually (NIAPS system administrator) or automatically (via an executable file stored on the server NIAPS resides on). This term describes the transfer of data between NIAPS servers afloat and appropriate shore servers (outbound amendments/inbound amendments).
Server Side Executable Application - No companion data	As it pertains to a NIAPS request type, a "server side executable application - no companion data" (also known as a "server side executable only") is a compiled executable that resides and executes only on the server NIAPS resides on. The application candidate does NOT manipulate data and or databases on the server. "Server-side" refers to operations that are performed by the server in a client–server relationship in computer networking. A server-side executable is a software program that runs on a remote server, reachable from a user's local computer or workstation. Operations are performed server-side because they require access to information or functionality that is not available on the client, or require typical behavior that is unreliable when it is done client-side. Server-side operations include the processing and storage of data from a client to the server, which can be viewed by a group of clients. A server-side executable with no companion data is a NIAPS term for server-side executables that do NOT have an associated data store that needs to be tapped into. The totality of the server-side application is just the executable software program itself. A NIAPS product example that is this type of NIAPS request: DS_Update.
Server Side Executable Application - with companion data	As it pertains to a NIAPS request type, a "server side executable application - with companion data" (also known as a "server side executable with data") is a compiled executable that resides and executes only on the NIAPS server and it manipulates data and or databases on the NIAPS server. "Server-side" refers to operations that are performed by the server in a client–server relationship in computer networking. A server-side executable is a software program that runs on a remote server, reachable from a user's local computer or workstation. Operations are performed server-side because they require access to information or functionality that is not available on the client, or require typical behavior that is unreliable when it is done client-side. Server-side operations include the processing and storage of data from a client to the server, which can be viewed by a group of clients. A server-side executable WITH companion data is a NIAPS term for server-side executables that have an associated data store that the server-side software program accesses. Product examples that are this type of NIAPS request: PMS Scheduler (SKED).
Silent Installer/Un-installer	A silent installer/un-installer, also known as single-click or auto installer/un-installer is a delivered executable 'package' that will completely and automatically install/un-install a NIAPS product, attach any databases required of it, create any users required of it, etc. without user intervention. The reason for the silent installer/un-installer is to allow NSWC Crane the ability to do a "replicated rollout", meaning they will put into an amendment the install/un-install package, and generally will either have the executable kick off automatically through replication or will issue an e-alert to have the ITs on board ship start a batch file which calls each product’s installer/un-installer package. The following NIAPS product types require a silent installer/un-installer before they will be allowed to go out on a NIAPS release: Web Based Products Server-side Executables with no data Server-side Executables with data Client Side Products The following NIAPS product types DO NOT require a silent installer/un-installer: Content Only Products Products that will use NIAPS as a Data Pass Through (replication agent) only.
System	Any solution that requires a combination of two or more interrelated, interacting, and/or interconnected hardware, software or firmware to satisfy a requirement of capability; Any equipment of interconnected system or subsystem of equipment that is used in the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission or reception of data or information by the DoD Component.
Web Application	As it pertains to a NIAPS request type, a "web application" is a web based application that is coded in a browser-supported language (such as JavaScript, combined with a browser-rendered markup language like HTML) and is reliant on a common web browser to render the application executable. The web application can be accessed via the server NIAPS sits on or can be accessed over a live network connection such as the Internet. Product examples that are this type of NIAPS request: TORIS, MFOM.