NIAPS Frequently Asked Questions (FAQs)
The process begins by first completing and submitting a NIAPS Information Request. The NIAPS Information Request form is the vehicle a product owner uses to tell the NIAPS action activities that they have a product they would like to have considered for inclusion on a future NIAPS release. Once it is known that there is a product that would like to go out on a NIAPS release, a specific process is then followed to ensure the product meets all the needs for it to be included on a NIAPS release. Below is a high level overview of this process:
The best way is to contact the NIAPS Configuration Management (CM) Team. Start with the team lead who can be reached at 812-854-3604.
The 'Join NIAPS' process is an efficient, comprehensive and timely method both for the Product Owner and the multiple NIAPS action activities who are responsible for assessing each NIAPS Request (NR). The 'Join' process is much more than the submission of a Join NIAPS Request (JNR). The 'Join' process not only includes the submission, receipt and review of the JNR but it also includes other aspects such as product testing (Installation, Functional, Load and Integration testing), training requirements review, certification and accreditation and final approval for inclusion. The process is necessary for all NIAPS product candidates because eventually, it will be part of a NIAPS release that must meet NETWARCOM Certification and Accreditation requirements before it and the the rest of a NIAPS release can be loaded on a hull.
Every version change, no matter what decimal point change it is, requires the submission of either a new NIAPS Request (NR) or the submission of a NIAPS Update Request (NUR) using the NIAPS Dimensions Configuration Management (CM) tool. To determine if an NR or an NUR is needed, contact the NIAPS Configuration Manager. Back to Top
The Department of the Navy Chief Information Officer (DON CIO) provides guidance on software application registration requirements for the DON Application and Database Management System (DADMS) and DoD IT Portfolio Registry (DITPR)-DON. DADMS and DITPR-DON are mandatory and authoritative sources for registering a software application that will be placed onboard a Naval vessel. Registration of mission-critical, mission-essential and mission-support systems in DADMS and DITPR-DON is central to establishing an accurate and reliable enterprise-wide inventory.
When a product owner submits a product to be considered for inclusion on NIAPS, the product owner first identifies to the NIAPS process the type of product they would like to have considered for inclusion. Those product types include:
The following table indicates which of these product types require a DADMS ID. Each applicable product type will be checked during the 'Join NIAPS' process to see if the version being submitted to be included either has an existing DADMS ID or is in the process of getting one established. If the product candidate requires a DADMS ID and it does not have one, it will NOT be allowed to go out on a NIAPS release until one is obtained or evidence is given that obtaining one is in process.
NIAPS TIP: If a DADMS ID is required for a product but it does not yet have one, a DADMS ID should be applied for soon after submitting a NIAPS Request to prevent the product from not being included in a future NIAPS release.
NIAPS TIP: Each change in a product's version number, no matter where the decimal point change occurs in the version number (e.g. v3.0 to v3.1; v3.5 to v3.5.1; v184.108.40.206 to v220.127.116.11), should first be run through the product's Functional Area Manager (FAM) to see if the new version will require a new DADMS ID. If the FAM determines that no new DADMS ID is required and that a current DADMS ID is still applicable, a written record from the FAM indicating this will be required.
More information about DADMS and submitting a DADMS request, visit the DADMS/DITPR-DON section found at the DON CIO site. For information on how to submit a DADMS request, visit the DADMS website. For definitions of the various NIAPS Request types, visit the NIAPS Glossary found in the NIAPS Information Center. Back to Top
The deliverables that will be required are dependent upon the type of NIAPS Request that will be submitted. The NIAPS Configuration Management Lead will discuss the deliverables you will need to submit after the submission of the NIAPS Request. Visit the NIAPS Information Center for the most current NIAPS Deliverables matrix. The matrix identifies, based on NIAPS Request (NR) type, which deliverables are required.
Dimensions is a commercial software Configuration Management (CM) tool produced by Serena Software (hence "Serena" Dimensions). Dimensions will enable NIAPS to transition from a manual CM process to an automated CM process.
The specific name of the NIAPS related Dimensions product is known as DS_NIAPS Dimensions (or simply "Dimensions"). Dimensions will be used to capture and control NIAPS requests (NRs) and associated logistics, technical and training requirements necessary to get products included on a NIAPS release. All status and reporting of NIAPS deliverables will be handled by Dimensions. Notification emails will automatically be generated by Dimensions which act as the demand signal for specific process action points to occur.
The NIAPS Dimensions tool provides tracking capabilities which allows the internal, NIAPS action activities to track and identify the state of a product throughout it NIAPS lifetime. Dimensions' central repository provides the NIAPS action activities with improved access and improved and accurate reporting of all the required deliverables. As a result, this equates to better service and a more timely NIAPS product delivery to the fleet.
Getting access to Dimensions first begins with a product owner submitting a System Access Authorization Request (SAAR) form. The NIAPS Dimensions SAAR form is found in the NIAPS Information Center, specifically in the "NIAPS Document Center" under the "'Join NIAPS' Related" section. As part of the 'Join NIAPS' process, a NIAPS Customer Advocate team member will direct a product owner to this form at the appropriate time in the process.
Once the NIAPS Dimensions SAAR form has been approved by the NIAPS Configuration Manager (CM) at SSC Pacific, the product owner will receive a notice that their access has been approved and they will then be able to proceed to the next step in the 'Join NIAPS' process which is to submit their NIAPS Request (NR). Back to Top
There is educational material made available to product owners who need to fill out a NIAPS Request, submit deliverables into NIAPS Dimensions, etc. The most comprehensive of these documents is the NIAPS Dimensions Application Owner's User Guide. This step-by-step User Guide is designed to show Application Owners how to accomplish all of the tasks necessary to complete the NIAPS process in Dimensions. The User Guide was developed to specifically walk the Application Owner through:
The NIAPS Dimensions Application Owner's User Guide is found in the NIAPS Information Center, in the "NIAPS Document Center" section, specifically in the "NIAPS Dimensions Related" area.
Yes. There is additional education available in the NIAPS Information Center on how to to use Serena Dimensions. The following documents are available:
Sometimes a product owner will decide during the 'Join NIAPS' process that they no longer want to use NIAPS to deploy their product to the fleet. In this case, a call to the NIAPS Configuration Management Team will get the ball rolling. The NIAPS CM Team will coordinate the removal process with you to have the NIAPS Request cancelled in the Dimensions product. Back to Top
A government employee or contractor may submit a NIAPS Request (NR). The resources sponsor for the application or product should designate the individual who will submit the NR. The individual who submits the request will become the primary POC that the NIAPS Configuration Manager, NIAPS Certification and Accreditation Team, NIAPS Testing Team, and NIAPS Training Support Agent will coordinate with for all phases of the NIAPS approval process. Back to Top
A recent Navy mandate to standardize and consolidate IT applications on afloat units is now in affect. The Baseline Allowance Control (BAC) process is a control that is now in place where all applications, that will be part of an afloat unit's IT infrastructure, must now be "BAC" approved before it will be allowed to ride on a NIAPS release. The BAC process was established so that IT capabilities could be managed in a manner that ensures the Fleet only fields and sustains cost effective, secure, and interoperable products and systems that perform with maximum benefit and minimal burden to our war fighters.
The Fleet Functional Area Managers (FAMs), working with the Type Commanders (TYCOMs) have developed a BAC configuration control list that identifies which applications are required and allowed on afloat and submarine units.
"BAC approved" means two things: 1). the FAM Analysis Working Group (AWG) has reviewed and approved an IT product for inclusion on an afloat network; 2). the approved product is listed on the most current BAC listing.
When a product owner first expresses interest in wanting to be included on a NIAPS release, the product owner will be asked several questions, two of which are:
Question 1 is asked to determine the product type. For NIAPS purposes, not all products that want to be included on a NIAPS release need to go through the BAC review/approval process. The type of product (a.k.a. the "NIAPS Request Type") will determine whether or not a BAC review/approval is necessary. The table below identifies which NIAPS Request (NR) types will require BAC review/approval. Definitions for each NIAPS Request type is found in the NIAPS Glossary:
Question 2 is asked to verify if the product has already gone through the BAC process (many already have) and to verify that the most current version of the product is on the most current BAC listing.
A product's versioning will also determine if a product will need to be BAC reviewed/approved. If a product's version number changes and the version number change is the result of a change to the product's form, fit or function, then that product's new version will need to go through both a DADMS review AND a BAC review. If the version change did NOT result in a form, fit or functionality change, then no BAC review/approval is required for the new product version.
All products that currently exist on a NIAPS release or those that want to 'Join' for the first time will go through the BAC process.
Navy Cyber Forces hosts the most current BAC list in their Fleet FAM Public Workspace. The most current BAC list is published as a Microsoft Excel file. The file name will look something like "BAC_v1_12March2012." CAC authentication is required to access the BAC list.
The BAC review/approval process is found in the Navy Cyber Forces Fleet FAM Public Workspace. Once at the site, click the button labeled "BAC Change Request Workflow." This will then reveal the "BAC Change Request Portal." Click the button labeled "Request BAC Change." This will reveal a BAC change request web form. Select the appropriate "Request type," complete the rest of the form and submit the request to get the process started.
You can learn more about the BAC process at the Navy Cyber Forces Fleet FAM Public Workspace. CAC authentication is required to access some educational pieces of the site.
All of the policy and directives that govern the BAC process can be found at the Navy Cyber Forces Fleet FAM Public Workspace. CAC authentication is required to access all of the policy and directives that are cited there.
No Fear Act | FOIA | Security & Privacy
Accessibility/Section 508 | Fraud, Waste & Abuse
Suicide Prevention | Navy Jobs | USA.gov
This is an official United States Navy Website.
Contact Webmaster | Site Map
This US Government system is subject to monitoring. Please review the
The appearance of external hyperlinks does not constitute endorsement by the United States Department of Defense, the United States Department of the Navy and the Space and Naval Warfare Systems Command (SPAWAR) of the linked web sites, or the information, products or services contained therein. For other than authorized activities such as military exchanges and Morale, Welfare and Recreation (MWR) sites, the United States Department of Defense, the Department of the Navy and the Space and Naval Warfare Systems Command does not exercise any editorial control over the information you may find at these locations. Such links are provided consistent with the stated purpose of this DoD web site.
In order to provide our customers with the best information more effectively, the SPAWAR Enterprise Public Website has undergone several recent revisions. We welcome your comments regarding revisions or other issues. Please send us your feedback.