IAFNOS_Appendix_2_-_Definitions.pdf

PDF 60 KB Posted

Attached to
Integrated AFNet Operations and Services (IAFNOS)
Solicitation number
FA8773-15-R-8007
Issued by

About this file

PWS Appen 2

View the file

Other files

File Type Posted
Atch_2_IAFNOSv1.2_-_Pricing_Table.xlsx XLSX spreadsheet
Amendment_0005.pdf PDF
Atch_2_IAFNOSv1.1_-_Pricing_Table.xlsx XLSX spreadsheet
FA8773-15-R-8007-0004.pdf PDF
3_Apr_Q As.xlsx XLSX spreadsheet
FA8773-15-R-8007-0003.pdf PDF
SF_30_Amend_2_FA8773-15-R-8007.pdf PDF
RFP_QAs_24_Mar_(2).xlsx XLSX spreadsheet
IAFNOS_Appendix_6_-_Certifcations_v1.2.pdf PDF
IAFNOS_Labor_Matrix_v1.1.xlsx XLSX spreadsheet
IAFNOS_PRS_v1.1.pdf PDF
IAFNOS_PWS_v1.2_24Mar15.pdf PDF
Atch_5_PP_Questionnaire_Cover_Letter_26_Mar_15.pdf PDF
IAFNOS_RFP_QAs_24Mar15.xlsx XLSX spreadsheet
FA8773-15-R-8007-0001.pdf PDF
IAFNOS_PWS_23Mar15v1.1.pdf PDF
IAFNOS_Appendix_6_-_Certifcations_v1.1.pdf PDF
Atch_6_PPI_EZ_Source.pdf PDF
Atch_8_Reading_Library_Instructions.pdf PDF
Atch_5_PP_Questionnaire_Cover_Letter.pdf PDF
EZ_Source_Character_Limits.docx DOCX document
Atch_7_DD254.pdf PDF
Draft_RFP_questions17Mar.xlsx XLSX spreadsheet
Atch_3_Relevancy_Matrix.pdf PDF
IAFNOS_Appendix_1_-_Acronyms.pdf PDF
Atch_8_Reading_Library_Instructions.pdf PDF
Atch_7(cont)_DD_Form_254_IAFNOS_Blk_13_Cont_w-attachs.pdf PDF
Atch_3_Relevancy_Matrix.pdf PDF
IAFNOS_Appendix_3_-_Workload.pdf PDF
Atch_2_IAFNOS_-_Pricing_Table.xlsx XLSX spreadsheet
Atch_4_PP_Questionnaire_IAFNOS.pdf PDF
IAFNOS_Appendix_6_-_Certifcations.pdf PDF
Atch_5_PP_Questionnaire_Cover_Letter.pdf PDF
FA8773-15-R-8007_IAFNOS_SF_33.pdf.pdf PDF
Atch_9_IAFNOS_Labor_Matrix.xlsx XLSX spreadsheet
IAFNOS_Exhibit_A_(CDRLS).pdf PDF
IAFNOS_Appendix_5_-_Task_Execution_Location_Matrix.pdf PDF
IAFNOS_PRS.pdf PDF
Atch_6_PPI_EZ_Source.pdf PDF
IAFNOS_Appendix_4_-_Shift_Requirements.pdf PDF
Atch_1_IAFNOS_PWS.pdf PDF
IAFNOS_EZ_Source_PPI_Tool.accdb —
Draft_Section_L-IAFNOS_27_Feb.docx DOCX document
Relevancy_Matrix_26Feb15.docx DOCX document
Draft_Section_M-_IAFNOS_27_Feb.docx DOCX document
Draft_Solicitation_FA8773-15-R-8007.doc DOC document
IAFNOS_Exhibit_A_(CDRLS_Feb_15).pdf PDF
Atch_7_DD_254-IAFNOS.docx DOCX document
Atch_5_PP_Questionnaire_Cover_Letter.doc DOC document
IAFNOS_Appendix_5_-_Task_Execution_Location_Matrix_(FINAL).docx DOCX document
Show 40 more

Latest 50 of 63 listed here. See the rest on GovTribe.

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

IAFNOS Appendix 2

Definitions Air Force Information Networks

(AFIN)

The globally interconnected, end-to-end set of Air Force information capabilities, and associated processes for collecting, processing, storing, disseminating, and managing information on-demand to warfighters, policy-makers, and support personnel, including owned, leased and contracted communications and computing systems and services, software (including applications), data, security services, other associated services, and national security systems.

Air Force Network

(AFNET)

The Air Force’s underlying Non-Secure Internet Protocol Router Network (NIPRNet) portion of the AFIN.

Air Force Network-Secure

(AFNET-S)

The Air Force’s underlying Secure Internet Protocol Router Network (SIPRNet) portion of the AFIN.

Authorized Service Interruption

(ASI)

Scheduled periods of network, equipment, or system downtime required to perform preventive maintenance actions, software or equipment upgrades or replacement, system reboots, etc.

Backlog A term used to define any incident tickets and change requests that are over 30 days old from its creation date. This does not include change requests or incident tickets that are classified by the Government as "projects" or "awaiting Government/external agency action."

Cyber Orders A general term used to refer to the various types of orders issued for network operations and maintenance (CTOs, CCOs, SPINS, MTOs, etc).

Cyber Tasking Order (CTO)

An operational type order issued to perform specific actions at specific time frames in support of AF and Joint requirements.

Cyberspace Control Order

(CCO)

Used to build/shape the portion of cyberspace to be employed in support of a CCMD operation or in response to adversary actions.

Infrastructure Devices and Technologies

Devices and/or technologies such as network switches, routers, load balancers, accelerators or other devices used to control and move network traffic across a network.

Maintenance Tasking Order

(MTO)

Routine tasks that enhance network security with a medium to low risk associated with the task.

1 | I A F N O S A p p e n d i x 1

Mission Report

(MISREP)

Provided timely reports of mission results and all other intelligence information obtained during post-flight debriefing. It may be used to retransmit or amplify an inflight report and is submitted to the tasking agency, the requesting unit/agency, and to other interested organizations.

Operation Order (OPORD)

A directive issued by a commander to subordinate commanders for the purpose of effecting the coordinated execution of an operation. (JP 5—0)

Operational Readiness

Maintaining hardware and software in a condition so the operational mission can be performed.

Service Catalog An organized and curated collection of any and all business and information technology related services that can be performed by, for, or within an enterprise.

Service Map A mapping of hardware, software and configuration to missions and users that facilitates accurate and efficient impact to missions.

Situational Report

(SITREP)

Used to report operational problems, limiting factors, recommended or intended courses of action, and other items not reported elsewhere. It should only report changes in the situation since submission of last report.

Specific reporting times may be submitted at the originator’s discretion or high headquarters direction.

2 | I A F N O S A p p e n d i x 1

Tiered Support 690 COG units provide hardware and software support according to a tiered structure as follows:

Tier 0. Tier 0 is self-help support accomplished by AFIN users using automated tools provisioned for fixing common issues. 690 COG provides informational content to the automated tools.

Tier 1. Tier 1 support is provided by the Client Service Administrators (CSA)/Client Systems Technicians (CST), and Functional System Administrators (FSA). Tier 1 is the first line of defense and is the initial support level responsible for basic user issues and single systems. 690 COG provides standard operating procedures (SOP) to CSAs, CSTs and FSAs for interaction with Tier 2 support.

Tier 2. Tier 2 support is provided by floor operations (e.g., 24/7/365 crew) within the I-NOSCs, ESUs, and APCs. The 26 NOS and 33 NWS also provide Tier 2 support but are not supported by the IAFNOS contract. Tier 2 is a more in-depth technical support level than Tier 1 providing more experienced and knowledgeable personnel to support of enterprise level systems. Tier 2 personnel are responsible for investigating elevated issues by confirming the validity of the problem and seeking solutions for these issues. Tier 2 also consists of touch maintenance. CFP personnel provide touch maintenance of client systems and APC personnel provide touch maintenance of server systems in the APC. Tier 2 personnel are responsible for assisting Tier 1 technicians with solving technical problems.

Tier 3. Tier 3 support is provided by the personnel within the I-NOSCs, ESUs, and APCs. The 26 NOS, 33 NWS, 38 CYRS and the 92 IOS also provide Tier 3 support but are not supported by the IAFNOS contract. This higher level of support is responsible for handling elevated issues. These organizations are responsible for not only assisting both Tier 1 and Tier 2 personnel, but with the research and development of solutions for new or unknown issues.

Tier 4. Tier 4 support is elevated to non-IAFNOS support provided by the PMOs, Special Maintenance Teams (SMT) and product vendors. This highest level of support is responsible for handling the most difficult or advanced problems. These units are responsible for not only assisting Tier 1, Tier 2 and Tier 3 personnel, but also for the research and development of solutions for new or unknown issues.

Time Compliance Network Order

(TCNO)

A downward-directed operations, security or configuration management-related order issued by USCYBERCOM in an Operational Order (OPORD).

TCNOs do not replace information conditions (INFOCONs), Operational Event/Incident Reports (OPREPs), Situational Reports (SITREPs) or Time Compliance Technical Orders (TCTO). The TCNO provides a standardized mechanism to issue an order.

Two-Person Integrity (TPI)

Is a process using two persons to verify actions.

3 | I A F N O S A p p e n d i x 1

File details come from the government source that posted it. Updated .