Attch_7_COM-F_Historical_Workloads.xlsx

XLSX spreadsheet 60 KB Posted

Attached to
COM-F III Federal contract opportunity
Solicitation number
FA4452-18-R-0037
Issued by
Department of the Air Force Air Mobility Command

About this file

From the source

Attch 7 Work Estimates

View the file

Other files for this federal contract opportunity

Other files attached to COM-F III, newest first.
File Type Posted
Additional_2_Q&A_11_Apr_19.xlsx XLSX spreadsheet
Additional_Questions_from_COM-F_Q&A's.xlsx XLSX spreadsheet
Attch_1_PWS_COM-F_III_Amend_02_21_Mar_19.docx DOCX document
Attch_7_Workload_Estimates_MEIS_3_Amend_02.xlsx XLSX spreadsheet
Pre-Proposal_Q&A_to_contractor.xlsx XLSX spreadsheet
RFP_COM-F_III._Amend_02_docx..docx DOCX document
Q&A_from_Draft_RFP.xlsx XLSX spreadsheet
Attch_6_P_and_C._Amendment_01.docx DOCX document
Attch_19_NDA_Amendment_01_COM-F_III.pdf PDF
RFP_COM-F_III._Amendment_01_docx.docx DOCX document
Attch_3_GFP_COM-F.xlsx XLSX spreadsheet
Attch_1_PWS_COM-F_III_15_Mar_19.docx DOCX document
Attch_16_TO_Pricing_Template.xlsx XLSX spreadsheet
Attch_4_Draft_QASP_COM-F_III_15_Mar_19.docx DOCX document
Attch_15_GDSS_TO_Appendix.pdf PDF
CDRL's_1-8_COM-F_III.pdf PDF
Attch_9_IDIQ_Labor_Category_and_Pricing_Template.xlsx XLSX spreadsheet
Attch_14_Strengths_and_Exceedances.docx DOCX document
Attch_5_DD254.pdf PDF
Attch_12_-_PP_Questionaire.docx DOCX document
Attch_8_Labor_Cat_Description.docx DOCX document
Attch_6_P_and_C.docx DOCX document
Attch_13_Teaming_Consent_Letter__.docx DOCX document
Attch_17_COM-F_III_TO_Staffing_Matrix.xlsx XLSX spreadsheet
Attch_11_Client_PP_Authorization.docx DOCX document
Attch_18_Subsequent_Task_Order_Appendices.pdf PDF
Attch_10_PPIS_COM-F_III.docx DOCX document
RFP_COM-F_III.docx DOCX document
Show all 28

On GovTribe

Work with this file on GovTribe

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

Text version

The file's text, extracted by GovTribe without its formatting.

WL Cover Page

GDSS WL

The following are estimates and may increase or decrease due to operational and other factors.
GDSS
Categories:Quantity/Frequency:Notes:
Releases (Major)3/year GDSSDocumented release or patch that requires significant effort and experties i.e. database conversions, OS/Database engine upgrades, major infrastructure upgrades, no service interruption, significant DIACAP review. Minimum 50 software change requests per Release. May require travel. Programs may differentiate releases, examples being major, minor, etc. Releases include GDSS/AVORM/ESM/ACDS/MAC-D.
Releases (Minor)4/year GDSS 5/year AVORM 2/year ACDS/MAC-D 4/year ESM 2/year MSD 2/year EMCFocused release, may involve a web kit, utility change, COTS updates, Patches, etc. May require a concerted effort, Travel unlikely. Fewer than 50 software change requests per Release.
Configuration or small updates50/year GDSS 15/year AVORM 10/year ACDS/MAC-D 20/year ESM 5/year MSD 10/year EMCMinor out of cycle code changes, hot fixes normally replacement of a few .DLL files, SQL or Web packages.
TCNO /IAVA/ Security Patches20/monthCOTS / GOTS / IOS / Hardware security updates. USCYBERCOM mandated 21 day or less of remediation of security patches
Technical Refreshes13 enclaves/at a minimum 2 times per yearUpgrade/change out of system Hardware/OS/utilitities to include servers and appliances. Can occur in conjunction with other activiites such as releases. Multiple fielding events can occur in the same time frame. May involve travel to enclaves not located at Scott.
CCBs92/yearConfiguration Control Board Items include release go/no go decisions, configuration changes to hardware/GOTS/COTS, OS, patches, etc. for implementation in government configuration controlled environments

* Note: Server counts, locations, and software versions may change.

&F

ACAS WL

The following are estimates and may increase or decrease due to operational and other factors.
ACAS
Categories:Quantity/Frequency:Notes:
Releases (MAJOR)<2/yearDocumented release or patch that requires significant effort and experties i.e. database conversions, OS/Database engine upgrades, major infrastructure upgrades, no service interruption, significant DIACAP review. May require travel. Programs may differentiate releases, examples being major, minor, etc.
Releases (Minor)6/yearFocused release, may involve a web kit, utility change, COTS updates, patches, etc. May require a concerted effort. Travel unlikely.
Configuration or small updates6/yearMinor out of cycle code changes, hot fixes normally replacement of a few .DLL files, SQL or Web packages.
TCNO /IAVA/ Security Patches56/yearCOTS / GOTS / IOS / Hardware security updates. USCYBERCOM mandated 21 day or less of remediation of security patches
Technical Refreshes<2/yearUpgrade/change out of system Hardware/OS/utilitities to include servers and appliances. Can occur in conjunction with other activiites such as releases. Multiple fielding events can occur in the same time frame. ACAS has no hardware and OS upgrades will be accomplished via automated builds once in the cloud.
CCBs14 CCB / year and other CCB type documentationsConfiguration Control Board items include release go/no go decisions, configuration changes to hardware/GOTS/COTS, OS, patches, etc. for implementation in government configuration controlled environments. ACAS does not conduct CCBs (Go/No Go) for application of security patches.

* Note: Server counts, locations, and software versions may change.

&F

GCCS WL

The following may increase or decrease due to operational and other factors.
GCCS
Categories:Quantity/FrequencyNotes:
Releases (MAJOR)<1 per yesr
* AMC activites - GCCS-AF provides primary release documentionDocumented release or patch that requires significant effort and experties i.e. database conversions, OS/Database engine upgrades, major infrastructure upgrades, no service interruption, significant DIACAP review. May require travel. Programs may differentiate releases, examples being major, minor, etc.
Releases (Minor)0Focused release, may involve a web kit, utility change, COTS updates, patches, etc. May require a concerted effort. Travel unlikely.
Configuration or small updates0Minor out of cycle code changes, hot fixes normally replacement of a few .DLL files, SQL or Web packages.
TCNO /IAVA/ Security Patches12/Yr
* AMC activites - GCCS-AF provides primary release documentionWorkstations COTS / GOTS / IOS / Hardware security updates. USCYBERCOM mandated 21 day or less of remediation of security patches
Technical Refreshes0Upgrade/change out of system Hardware/OS/utilitities to include servers and appliances. Can occur in conjunction with other activiites such as releases. Multiple fielding events can occur in the same time frame.
CCBs0Configuration Control Board items include release go/no go decisions, configuration changes to hardware/GOTS/COTS, OS, patches, etc. for implementation in government configuration controlled environments.

* Note: Server counts, locations, and software versions may change.

&F

MEIS 3 WL

The following may increase or decrease due to operational and other factors.
MEIS3
Categories:Quantity/FrequencyNotes:
Releases (MAJOR)0/yearDocumented release or patch that requires significant effort and experties i.e. database conversions, OS/Database engine upgrades, major infrastructure upgrades, no service interruption, significant DIACAP review. May require travel. Programs may differentiate releases, examples being major, minor, etc.
Releases (Minor)0/yearFocused release, may involve a web kit, utility change, COTS updates, patches, etc. May require a concerted effort. Travel unlikely.
Configuration or small updates0/yearMinor out of cycle code changes, hot fixes normally replacement of a few .DLL files, SQL or Web packages.
TCNO /IAVA/ Security Patches0/monthWorkstations COTS / GOTS / IOS / Hardware security updates. USCYBERCOM mandated 21 day or less of remediation of security patches
Technical Refreshes0/per yearUpgrade/change out of system Hardware/OS/utilitities to include servers and appliances. Can occur in conjunction with other activiites such as releases. Multiple fielding events can occur in the same time frame.
CCBs6/yearConfiguration Control Board items include release go/no go decisions, configuration changes to hardware/GOTS/COTS, OS, patches, etc. for implementation in government configuration controlled environments.

* Note: Server counts, locations, and software versions may change.

&F

CAMPS WL

The following may increase or decrease due to operational and other factors.
CAMPS
Categories:Quantity/Frequency:Notes:
Releases (MAJOR)2-3/yearDocumented release or patch that requires significant effort and experties i.e. database conversions, OS/Database engine upgrades, major infrastructure upgrades, no service interruption, significant DIACAP review. May require travel. Programs may differentiate releases, examples being major, minor, etc.
Releases (Minor)2-3/yearFocused release, may involve a web kit, utility change, COTS updates, patches, etc. May require a concerted effort. Travel unlikely.
Configuration or small updates6-10/yearMinor out of cycle code changes, hot fixes normally replacement of a few .DLL files, SQL or Web packages.
TCNO /IAVA/ Security Patches48/yearCOTS / GOTS / IOS / Hardware security updates. USCYBERCOM mandated 21 day or less of remediation of security patches
Technical Refreshes1 -2 or more large refreshes (hardware and software) per yearUpgrade/change out of system Hardware/OS/utilitities to include servers and appliances. Can occur in conjunction with other activiites such as releases. Multiple fielding events can occur in the same time frame.
CCBs35 CCB / year and other CCB type documentationsConfiguration Control Board items include release go/no go decisions, configuration changes to hardware/GOTS/COTS, OS, patches, etc. for implementation in government configuration controlled environments.

* Note: Server counts, locations, and software versions may change.

&F

MAFPS WL

The following may increase or decrease due to operational and other factors.
MAFPS
Categories:Quantity/Frequency:Notes:
Releases (MAJOR)Every other year.Documented release or patch that requires significant effort and experties i.e. database conversions, OS/Database engine upgrades, major infrastructure upgrades, no service interruption, significant DIACAP review. May require travel. Programs may differentiate releases, examples being major, minor, etc.
Releases (Minor)6/yearFocused release, may involve a web kit, utility change, COTS updates, patches, etc. May require a concerted effort. Travel unlikely.
Configuration or small updates12/yearMinor out of cycle code changes, hot fixes normally replacement of a few .DLL files, SQL or Web packages.
TCNO /IAVA/ Security Patches14/year*COTS / GOTS / IOS / Hardware security updates. USCYBERCOM mandated 21 day or less of remediation of security patches
Technical Refreshes2 large refreshes (software) per year; no PMO-planned hardware refreshes; will upgrade hardware when Enclave upgradesUpgrade/change out of system Hardware/OS/utilitities to include servers and appliances. Can occur in conjunction with other activiites such as releases. Multiple fielding events can occur in the same time frame.
CCBs60 CCB / year and other CCB type documentationConfiguration Control Board items include release go/no go decisions, configuration changes to hardware/GOTS/COTS, OS, patches, etc. for implementation in government configuration controlled environments.

* Note: Server counts, locations, and software versions may change.

&F

DMR WL

The following may increase or decrease due to operational and other factors.
DMR
Categories:Quantity/Frequency:Notes:
Releases (MAJOR)<1/yearDocumented release or patch that requires significant effort and experties i.e. database conversions, OS/Database engine upgrades, major infrastructure upgrades, no service interruption, significant DIACAP review. May require travel. Programs may differentiate releases, examples being major, minor, etc.
Releases (Minor)6/yearFocused release, may involve a web kit, utility change, COTS updates, patches, etc. May require a concerted effort. Travel unlikely.
Configuration or small updates3/yearMinor out of cycle code changes, hot fixes normally replacement of a few .DLL files, SQL or Web packages.
TCNO /IAVA/ Security Patches12/yearCOTS / GOTS / IOS / Hardware security updates. USCYBERCOM mandated 21 day or less of remediation of security patches
Technical Refreshes<1/yearUpgrade/change out of system Hardware/OS/utilitities to include servers and appliances. Can occur in conjunction with other activiites such as releases. Multiple fielding events can occur in the same time frame.
CCBs35 CCB / year and other CCB type documentationsConfiguration Control Board items include release go/no go decisions, configuration changes to hardware/GOTS/COTS, OS, patches, etc. for implementation in government configuration controlled environments.

* Note: Server counts, locations, and software versions may change.

&F

MEIS4 WL

The following may increase or decrease due to operational and other factors.
MEIS4
Categories:Quantity/Frequency:Notes:
Releases (MAJOR)2-4/yearDocumented release or patch that requires significant effort and experties i.e. database conversions, OS/Database engine upgrades, major infrastructure upgrades, no service interruption, significant DIACAP review. May require travel. Programs may differentiate releases, examples being major, minor, etc.
Releases (Minor)6-10 Releases/YearFocused release, may involve a web kit, utility change, COTS updates, patches, etc. May require a concerted effort. Travel unlikely.
Configuration or small updates50/yearMinor out of cycle code changes, hot fixes normally replacement of a few .DLL files, SQL or Web packages.
TCNO /IAVA/ Security PatchesMonthly / Frequency based upon Software Problem Reports and trouble ticketsCOTS / GOTS / IOS / Hardware security updates. USCYBERCOM mandated 21 day or less of remediation of security patches
Technical RefreshesHardware is refreshed on a 3 year cycle. OS changes generally coincide with hardware refreshes, but can occur anytime required.Upgrade/change out of system Hardware/OS/utilitities to include servers and appliances. Can occur in conjunction with other activiites such as releases. Multiple fielding events can occur in the same time frame.
CCBs125/YearConfiguration Control Board items include release go/no go decisions, configuration changes to hardware/GOTS/COTS, OS, patches, etc. for implementation in government configuration controlled environments.

* Note: Server counts, locations, and software versions may change.

&F

MAFC2 Enclave WL

The following may increase or decrease due to operational and other factors.
MAFC2
Categories:Quantity/Frequency:Notes:
Releases (MAJOR)2-4/yearDocumented release or patch that requires significant effort and experties i.e. database conversions, OS/Database engine upgrades, major infrastructure upgrades, no service interruption, significant DIACAP review. May require travel. Programs may differentiate releases, examples being major, minor, etc.
Releases (Minor)6-10/yearFocused release, may involve a web kit, utility change, COTS updates, patches, etc. May require a concerted effort. Travel unlikely.
Configuration or small updates30/yearMinor out of cycle code changes, hot fixes normally replacement of a few .DLL files, SQL or Web packages.
TCNO /IAVA/ Security PatchesMonthly / Frequency based upon Software Problem Reports and trouble ticketsCOTS / GOTS / IOS / Hardware security updates. USCYBERCOM mandated 21 day or less of remediation of security patches
Technical RefreshesHardware is refreshed on a 3 year cycle. OS changes generally coincide with hardware refreshes, but can occur anytime as required.Upgrade/change out of system Hardware/OS/utilitities to include servers and appliances. Can occur in conjunction with other activiites such as releases. Multiple fielding events can occur in the same time frame.
CCBs50/ yearConfiguration Control Board items include release go/no go decisions, configuration changes to hardware/GOTS/COTS, OS, patches, etc. for implementation in government configuration controlled environments.

* Note: Server counts, locations, and software versions may change.

&F

GATES WL

The following may increase or decrease due to operational and other factors.
GATES
Categories:Quantity/Frequency:Notes:
Releases (MAJOR)Annually / planning to adapt to agile development so frequency will increaseDocumented release or patch that requires significant effort and experties i.e. database conversions, OS/Database engine upgrades, major infrastructure upgrades, no service interruption, significant DIACAP review. May require travel. Programs may differentiate releases, examples being major, minor, etc.
Releases (Minor)Quarterly/2/bi-annuallyFocused release, may involve a web kit, utility change, COTS updates, patches, etc. May require a concerted effort. Travel unlikely.
Configuration or small updatesBi-Monthly / Primarily based upon Software Problem Reports and trouble ticketsMinor out of cycle code changes, hot fixes normally replacement of a few .DLL files, SQL or Web packages.
TCNO /IAVA/ Security Patches8/quarterCOTS / GOTS / IOS / Hardware security updates. USCYBERCOM mandated 21 day or less of remediation of security patches
Technical Refreshes1/every 3-5 yearsUpgrade/change out of system Hardware/OS/utilitities to include servers and appliances. Can occur in conjunction with other activiites such as releases. Multiple fielding events can occur in the same time frame.
CCBsBi-MonthlyConfiguration Control Board items include release go/no go decisions, configuration changes to hardware/GOTS/COTS, OS, patches, etc. for implementation in government configuration controlled environments.

* Note: Server counts, locations, and software versions may change.

&F

Microsoft_Word_Document.docx

FA4452-18-R-0037

COM-F III

Attachment 7

Historical Work Load Data

Attachment 7

Communications, Operations, & Maintenance Functions (COM-F) III IDIQ

Procuring Office: 763d Specialized Contracting Squadron (763 SCONS)

510 POW/MIA Drive

Building P40

Suite E1001

Scott Air Force Base, IL 62225-5420

Requiring Office: HQ AMC Directorate of Operations and Training Division (A6I)

203 West Losey Street

Room 3610

Scott Air Force Base, IL 62225

Project Management Office: 375th Communication Support Squadron (CSPTS)

859 Buchannan Street

Scott Air Force Base, IL 62225

13 Mar 2019 image1.emf

File details come from the government source that posted it.