Appendix 14 Work Breakdown Structure For Information Management and Communications Support (IMCS)
Appendix 14 Work Breakdown Structure For Information Management and Communications Support (IMCS)
Appendix 14 Work Breakdown Structure For Information Management and Communications Support (IMCS)
Appendix 14
Work Breakdown Structure
For
The costs incurred under this contract should be organized in such a manner to allow the
customer community to see their cost, down to the type of service, activity and task order
level. The goal is to allow each customer to identify where their funds are being
expended to meet their service needs. The expectation is that the customer community
will use this data to understand their communications and technological utilization,
understand what is driving their costs, and identify areas where they see a potential for
improvement. The data will also be used by IT Management to understand the cost
associated with operating, maintaining, sustaining, and responding to service requests for
the various systems used in providing information services to the Kennedy Space Center.
Costs shall be segregated and reported by customer and WBS element to the level of the
WBS as stated below, with the appropriate activity designation reported. This will allow
system and service managers to address system wide costs that support the technical
services across the contract by WBS element. Provisions shall be made to allow costs to
be collected by government provided cost allocation as well as by special projects or
activities that make use of standard contract services that are general in nature and may
benefit multiple customers. In addition, a cost summary shall be provided that sums all
costs to the first level by WBS Element.
Current customers include Shuttle, Constellation, Launch Services, Space Station, Life
Sciences, Institutional, and Center Management and Operations (CMO). Further
breakdown may be required for funding codes and customers which will be reflected in
the work order report and in scheduled monthly reviews.
The WBS is organized by service and work type activities. Work may take place for
specific organization, mail code, service, function, or in a physical location. The type of
work, mail code, and location (site, facility, room) are necessary to schedule/assign work,
are a key component in cost assignment, and will be further defined in a joint managed
Rule Set. Work descriptions in Maximo/Work Order Report must be well documented to
further determine customer charging. Reporting includes the task information and the
resources expended to perform or support the task.
In addition, the monthly work order report will be provided as a supplemental report to
the NF 533 Financial Report (DRD-MS-03), which will be broken out by customers and
provide every work order associated with Direct and any General type of allocation of
hours.
Task Order Services (CLIN 002) shall be presented in the NF 533 format in a separate
volume. Each task shall have its own unique tab which provides all elements of cost for
that particular effort.
This will consist of the various Information Management Support Services within each
Level I WBS.
This will consist of the specific Information Management Support Services within each
Level II WBS.
Every WBS required for reporting will contain the following standard activity work
element. The activity should be identified by a dash and appropriate number.
-1 Operations/Maintenance
Support for day-to-day operations of WBS element. Includes the following: console
manning, system monitoring, mission support, fulfilling PRD requirements, trouble
tickets, validations, maintenance, preventive maintenance, outage management, return-to-
service, maintenance agreements/licenses, service contracts, and training in support of
current systems.
-2 Service Request
Support for all customer driven non-recurring requirements. May involve modifications,
additional services, changes, new equipment, upgrades, minor and major moves, facility
leases and equipment leases.
-3 Sustaining Engineering
Support for changes and modifications to systems to provide additional service capacity,
add features to software to reduce operational risk, replace obsolete hardware and
software, or consolidate services. Predominantly, this would be internally generated
requirements, not associated with a request from a customer.
-4 Systems Engineering
Support for design and requirement analysis, system capacity analysis, design reviews,
operations concept development, systems engineering planning documents, requirements
gathering, project management and Systems Engineering and Integration, evaluation and
testing of COTS software and hardware.
-5 Depot Repair
Support for all repairs to system and system components that are performed at an on-site
repair facility.
14.3 IMCS Level I, and Level II, and Level III WBS Structure
1.1 Phase-In/Phase-Out (Since phase-in occurs prior to contract start, this WBS
only pertains to phase-out activities at the end of the period of performance.)
1.8 Training
1.9 Logistics
Example 1: Replace a broken Paging and Area Warning speaker at the SSPF.
The effort is driven by a Customer Service Request. The XA project code and the work
activity effort would be used to identify and collect costs associated with the activity.
This particular cost would be charged to the CMO Customer and be reflected in their
volume of the 533 as well as the Monthly Work Order Report.
Example 3: Perform major network upgrade to SSPF/2nd Floor (Task Order #5 to CLIN
002):
This is a Task Order under CLIN 002 that will be reported in a separate volume of the NF
533. This Task Order #5 will be reported under separate tab and will be separately
funded.
Example 4: Replace a 24-port network switch with a 48-port network switch in SSPF
because the 24-port switch is nearing full capacity.
This effort would be a Sustaining Engineering effort because the work is associated with
preemptively increasing service capacity. Location Code would be SSPF (or facility
number) and the room number. Based upon this data, the customers associated with the
SSPF (either entire facility or that room) would be assigned the associated cost. The
customer would see their cost and have visibility to the nature of the cost both in their
volume of the 533, and in the Monthly Work Order Report.
There would be several reportable WBS elements associated with this effort:
WBS 3.2.x-4
WBS 3.3.x-4
WBS 3.4.x-4
WBS 3.5.1-4
WBS 3.5.3-4
WBS 3.8.x-4
WBS 3.9.x-4
This effort would be a Systems Engineering effort because the work is associated with
creating engineering planning documents. The customer associated with this work is the
Constellation Program. The customer would see their cost and have visibility to the
nature of the cost both in their volume of the 533, and in the Monthly Work Order
Report.
Example 6: The PRD calls for various transmission assets to be up to support a Shuttle
launch. The transmission planner needs to create Support Documents (SD) for the
technicians to follow.
This effort would be an Operations/Maintenance activity. Based upon this data, the
customers associated with this request would be the Shuttle Program, and would be
assigned the associated cost. The customer would see their cost and have visibility to the
nature of the cost both in their volume of the 533, and in the Monthly Work Order
Report.
Example 7: Repair a broken OIS-D End Instrument (EI) that was removed from Pad A.
This effort would be a Depot Repair activity. Location Code would be Pad A (or facility
number). Based upon this data, the customers associated with the Pad A would be
assigned the associated cost. The customer would see their cost and have visibility to the
nature of the cost both in their volume of the 533 at that WBS and in the Monthly Work
Order Report.