GDSS-AVORM_Estimated_Workload.xlsx
XLSX spreadsheet 27 KB Posted
- Solicitation number
- FA4452-17-R-0003
About this file
GDSS estimated workload
View the file
Other files
Show all 24
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
Sheet1
| The following are estimates and may increase or decrease due to operational and other factors. | ||||
| Categories: | Quantity/Frequency: | Scope/Size | Notes: | Program Additional Notes/Comments |
| Agile Team Participation | 250/year | Daily participation in the Agile spiral development process starting from assisting with the requirement definition, prototpe design/validation, and testing. | ||
| Releases (Major) | 3/year GDSS | Minimum 50 software change requests per Release |
Regression Testing Required – At least 2000 Test cases
| 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. Often requires travel. Please estimate the projected number of releases per year. Programs may differentiate releases, examples being major, minor, etc. Normally requires testing, engineering, fielding. | 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 EMC | Fewer than 50 software change requests per Release |
Limited Regression Testing Required - At least 100 Test cases
| Focused release, may involve a web kit, utility change, COTS updates, Patches, etc. May require a concerted effort, Travel unlikely. | ||||
| Configuration or small updates | 50/year GDSS 15/year AVORM 10/year ACDS/MAC-D 20/year ESM 5/year MSD 10/year EMC | Targeted testing, basic system functionality regression testing required | ||
| Minor out of cycle code changes, hot fixes normally replacement of a few .DLL files, SQL or Web packages. Requires testing. | ||||
| Requirements Specification Agreements | 20/year | Estimate and coordination on release content, milestones, risks, etc, involving estimates for engineering, testing, and fielding. | ||
| TCNO /IAVA/ Security Patches | 20/month | Targeted testing, basic system functionality regression testing required | ||
| COTS / GOTS / IOS / Hardware security updates. Requiring testing. | ||||
| Technical Refreshes | 13 enclaves/at a minimum 2 times per year | Targeted testing, basic system functionality regression testing 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. | Travel involved to enclaves not located at Scott. | |||
| Training Classes | At a minmum 10 Training TDY's annually. There are monthly classes held here at Scott - at least 20 per year. | Training classes may be regularly schedule, tied to a release, or dictated by operation need. Programs may want to note the number of TDY's necessary. | ||
| Training Material | 1 difference training guide/created with each release. 5 Specialized guides that need to be kept up to date and new ones created when requested. 12 Client User Manuals that must be updated with each release. 13 Web User Manuals that must be updated with each release. Currently there are 23 CBT's that must be kept up to date and new ones created when requested or a need is identified. | This may include user manuals or CBTs and may be regularly schedule, tied to a release, or dictated by operation need.. | ||
| Level III Technical Support requests | 500/Year | Includes trouble tickets, assistance requests, troublshooting, and overall problem coordination with Level I and II help desks and Level III developer, etc. Normally for operational issues that could not be resolved by Level 2 Technical helpdesk. May be after normal duty hours and require on-site support. Can apply to non-production environments to key events such as testing or training. | ||
| CCBs | 92/year | Configuration Control Board Items - These items include release go/no go decisions, configuration changes to hardware/GOTS/COTS, OS, patches, etc. for implementation in government configuration controlled environments e.g. Production, testing , prototyping. | Each Release (Major, Minor, Configruation, TCNO, and techincal refreshes) will require AISS to install in the government test facility, AISS tested, and then AISS will be given approval to field. | |
| Engineering Request | 50/year | This would be a request to engineer solutions to introduce new technology, functionality, or system enhancement resulting in a white paper or technical proposal. | ||
| Other Projects/Activities | 4/year | Projects outside releases and tech refreshes. Normally requires some form of a paper/proposals, testing , diagrams, fielding , installation plans, and other supporting documents. | ||
| Support Documentation | 20/year | Includes agreements and documents such as IDD, MOA, MOU, SLA, Project support, interface agreements, etc. | ||
| System Documentation | 40/year | Includes ISPs, architecture, topology, connectivity, network, facility, diagrams and related documents. |
| Server counts and locations can be located in the Asset Management Folder. * |
| Software / hardware baselines can be found in the Configuration Management folder.* |
| * Note: Server counts, locations, and software versions may change. |
Sheet2
Sheet3
File details come from the government source that posted it. Updated .