Section_J _Attachment_23_-_Workload_Estimates_v1.5.docx

Section J Attachment 23: Workload Estimate Workload Estimates

These work estimates are representative of anticipated task orders and are a snapshot in time. It should not be assumed that these estimates are for all possible orders. Due to the nature of the tasks, particular work estimates maybe applicable only to certain types of orders. Also, this information is historical. Several changes have occurred and are occurring which would change these estimates.

Software employed C, C++, Java, Python, HTML, FORTRAN, IDL, Enterprise Java, Perl, HTML, XML, Unix scripting, PLSQL, JMS, Solaris, Linux, IDL, Versant, Oracle, gsoap, rogue wave, BEA message queue, XERCES, XALAN, Eclispse, Erwin, Netbeans, SUN Tools (Cluster, JES), Tomcat, JBOSS, Oracle, WDA JMBL, Grads, SSL, Tivoli, AIX, Vis5D, TCL, WDA JMBL, Horace, PHP, ActionScript, JSON, Google Maps API, Google Earth (API, Server, Fusion), Flex, EhCache, Spring, OpenScales, ColdFusion, BlazeDS, JIRA, Struts, Java Script, Open Layers, Windows, SUN Tools (User Management, User Admin, Brokers, Glassfish), TAWS Client, IRIX, CJMTK/ESRI, Hummingbird, VSTK, Antivirus software, SOAP, unix scripting, SSL, AF Portal, Weather decoders, JMD, Storenext, ftp, ssh, Jmeter, CVS, WSDEGRIB, Weblogic, Ksh scripting CORBA, GAIM, IFM, SEEFS, Visual Basic, Kirnshell, Cshell, SQL, Telelogic Synergy, FlexBuilder, MS Visual Studio, suberviersion, Putty, SecureShell, Maven, SCONS, Mecurial, Git, SecureFX, Roxio Studio, Java Studio Enterprise, Grads, JSP, Fortify, SAS, PADS, NetCool, and MS SharePoint Portal with MS Live Communications Server

Typical projects started per year (Systems Engineering Para 2.1 and Program Management portions of para 2.2 6 system upgrades and modifications 4 space weather software developments 1-2 weather model software developments 6 software maintenance tasks requiring incremental improvements to existing software

Typical sustainment requirements per year (Appropriate Systems Sustainment portions para 2.3 5-7 task orders including hardware maintenance, software maintenance, network maintenance, property management, license/support agreement management, drawing management, systems administration, system performance measurement, and systems administration

Change Request Activity (snapshot) (System Engineering, System Maintenance para 2.1 and 2.3)

NR = New Requirement Mxn = Maintenance Requirement NOTE: In Jan 2012, change request activity database moved to JIRA.

Technical reviews, technical interface meetings (Systems Engineering Para 2.1.3) 1 per week. Of 1 per week, 1 per month requires prepared briefing

Weather data analysis meetings (Systems Engineering para 2.1.6) During development periods, meetings occur weekly.

Systems engineering analysis (Systems Engineering para 2.1.11) 1 per month

Systems engineering inquiries (Systems Engineering para 2.1.13) 1 per week

Monthly status reports (Program management/systems management para 2.2.1 and 2.2.2) Formal briefing twice per month, once to CORs, once to AFWA/CC Formal briefing financial review – once per month to Government program manager and appropriate Government staff Program management meetings (no briefing) – once per week

Contractor escort requests and access to Contractor designated areas (Program management/Systems management para 2.2.5.2 and 2.2.5.3) Infrequent and for an emergency. Most escort requirements are the contractor escorting installation and repair vendors.

Metrics (Program management/systems management para 2.2.7) The number of metrics is dependent on the number of measured items (i.e., processors). As of Oct 11, approximately 300 metrics in use with most updated monthly

On Call Support (historical) (Systems sustainment para 2.3.2 and para 3.0 Services Summary) Average number of calls per month (all hours): 92 Average on site response required per month: 27

Time Compliance Network Orders (historical) (Systems sustainment para 2.3.4) Monthly average: 29; Monthly range: 10 to 40 Assets affected by TCNOs varies dependent on system configurations and numbers. As of Oct 11, 557 assets affected.

Systems Administration (historical) (Systems sustainment, para 2.3.8) 20 major implementations per year (system upgrades and refreshes) 60 minor releases per year 150 maintenance releases per year (patches or configuration changes) Approximately 5 requests per day or 1000 minor system items per year for assistance with, for example, scripts, and files Approximately once per month system restoration

The following matrix identifies on which hardware/operating systems (OS) the applicable software baseline resides.

CDFS II

X

CDFS II OSE Testbed

X

AFW-WEBS

X

WDA

X

DataPipe

X

X

SWAFS

X

SYS Applications

X

X

The following table identifies the number of server instances per OS categorized by Production or Non-Production.

Number of OS Instances

NOTE: Red Hat Linux High Performance Computing (HPC) HP servers support GTWAPS, Unified Model, and the 16WS specialized models, ensembles, global WRF, and other projects. Red Hat Linux HP servers support AFW-WEBS, CDFS II, SWAFS, SYS APPs, and other non-HPC based functions. The Linux OS are all Red Hat. All Red Hat Linux HP Servers are made up of 460c blades mounted in HP 5000 chassis. The HPC systems are connected by a private InfiniBand circuit that allows the setup of the parallel processing environment required by some of our software baselines. The non-HPC Red Hat Linux HP Servers (i.e., Red Hat Linux HP Servers) are connected by our normal public circuits.

Air Force Weather Consolidated Network Maintenance Tasks (Systems sustainment, para 2.3.9) Install TCNOs Configure routers and switches Receive and inventory hardware Test and evaluate hardware and software Install hardware Load operating systems and software Provide on-call support in rotation with Government Perform security scans Provide input to accreditation documents Develop network diagrams Install network wiring

Decommissioning (historical) (Systems sustainment para 2.3.10) Approximately 300 large components (i.e., servers, racks, etc) removed each year and turned into DRMO

Drawings (historical) (Systems sustainment para 2.3.12) Approximately 500 parts lists and connection drawings per year. Approximately 100 floor layouts and assembly drawings per year.

The above numbers include

· 12 Room Layouts

· 75 New Drawings

· 20 Modified Drawings

· 50 Inactivated Drawings

· 75 New Connection Diagrams

· 15 Modified Connection Diagrams

· 45 Inactivated Connection Diagrams

· 90 New Parts Lists

· 40 Modified Parts Lists

· 80 Inactivated Parts Lists 3D diagrams a new requirement; estimates above do not include.

Estimates include new and modified documents.

Environmental data access assistance (Systems sustainment para 2.3.13) 1 to 2 new requests per week 3 to 4 follow-up requests per week

ATTACHMENT 2

These charts provide historical information from like or similar work. The Government has adjusted the historical information to SEMS III requirements. This information does not represent the Government estimate.

Labor Hours Annual Sustainment Task Order

NOTE: All numbers in table are labor hours.

Sys Engr = Systems Engineering PWS para 2.1 PM/SM = Program Management/Systems Management PWS para 2.2, 4.1.11, 4.3 Sustain = Systems Sustainment PWS para 2.3, 4.1.4, 4.1.5, 4.1.6

Space Weather Analysis and Forecast System Sustainment Task Order

NOTE: All numbers in table are labor hours.

PM/SM = Program Management/Systems Management PWS para 2.2, 4.1.11, 4.3 Sustain = Systems Sustainment PWS para 2.3, 4.1.4, 4.1.5, 4.1.6

Advanced Meteorological Model Development Project Task Order

Systems Engineering para 2.1: 7,300-8100 hours

Program Management/Systems Management para 2.2, 4.1.11, 4.3: 800-900 hours