GATES_Estimated_Workload_(corrected).xlsx
XLSX spreadsheet 23 KB Posted
- Solicitation number
- FA4452-17-R-0003
About this file
Corrected GATES workload data
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: | Notes: |
| Releases (MAJOR) | Annually / planning to adapt to agile development so frequency will increase | 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 (Minor) | Quarterly/2/bi-annually | Focused release, may involve a web kit, utility change, COTS updates, Patches, etc. May require a concerted effort, Travel unlikely. |
| Configuration or small updates | Monthly / Primarily based upon Software Problem Reports and trouble tickets | Minor out of cycle code changes, hot fixes normally replacement of a few .DLL files, SQL or Web packages. Requires testing. |
| Requirements Specification Agreements | Anually/Coincides with Major Releases | Estimate and coordination on release content, milestones, risks, etc, involving estimates for engineering, testing, and fielding. |
| Testing Change Requests. | 10 per month / conducted during monthly CCB | Number of tested requests Per/X e.g Baseline Changes Request, Software Problem Reports, Documentation Changes Requests, Interface Change Request. |
| TCNO /IAVA/ Security Patches | 1/monthly | COTS / GOTS / IOS / Hardware security updates. Requiring testing. |
| Technical Refreshes | 1/every 3-5 years | 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. |
| Training Classes | Per request/ less than 10 annually | 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 | 2 per year based on major release | 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 | 10/monthly | 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 | Bi-Monthly | 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. |
| Engineering Request | 2/monthly | 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 | As required by the control, and/or the PM tasking. | 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 | 59 IDDs, 48 MOAs, 58 SLAs; updates occur as often as needed review, update or accept agreements. Update C&A documents or / and ISP as / if needed. | Includes agreements and documents such as IDD, MOA, MOU, SLA, Project support, interface agreements, etc. |
| System Documentation | Maintain ISP. Living document updated per GATES release or system changes. | 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 .