Sample Task 002 Enterprise Management.pdf
PDF 25 KB Posted
- Attached to
- SOFSA CLS Services Federal contract opportunity
- Solicitation number
- H92254_08_R_0001
- Issued by
- United States Special Operations Command
About this file
Sample Task 002 Enterprise Management
View the file
Other files for this federal contract opportunity
Show all 50
SOFSA CLS Services has more files on GovTribe.
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
Text version
Statement of Objectives (SOO)
For Sample Task 002 Enterprise Management Task
1.0 Background
This Statement of Objectives (SOO) identifies the requirement to provide facilities management including the management processes and key information used by the total government/contractor team for administration of the contractor logistics support services contract. The objective is for the contractor to operate and maintain Government facilities at Blue Grass Station (BGS), Lexington, KY, Blue Grass Army Depot (BGAD), Richmond, KY, and other facilities specified during the period of performance. Adequate facilities, equipment, and personnel must be available during the period of performance of this contract.
The performance of work at other facilities or locations will be based upon approval of the Government.
The requirements of the following sub-paragraphs apply to all facilities and areas located on Government installations or on Government-provided property. The Statement of Objectives (SOO) tasks the contractor to incorporate industry and government best business practices to continuously improve the Special Operations Forces Support Activity Facilities.
2.0 CONTRACT OBJECTIVE:
2.1 Facilities Management
2.1.1 Energy Conservation: The contractor will need to be in compliance with the federal energy management goals outlined in Executive Order 13423 during performance of this contract.
2.1.2 Space Utilization: Effective space utilization in storage areas, administrative office areas, industrial areas, and support operations areas is the responsibility of the contractor.
2.1.3 Infrastructure Improvements: The goal is to reduce administrative space to 100 square feet per person, including the area used for aisles and associated support equipment while still providing enhanced performance with no service interruptions.
2.1.4 Facility Analysis: The determination of where facility improvements are required will be the responsibility of the contractor and to provide recommendation to the Government.
2.1.5 Facility Administrative Tools: The tracking of space currently obligated for customer requirements will be the responsibility of the contractor.
2.1.6 Facility Custodians: Each facility will have a facility custodian to ensure safe operation, maintenance reporting, status tracking, utility conservation, and physical security is being enforced. It is the contractor’s responsibility to assign facility custodians to each facility.
2..1.7 Billable Storage: Monthly lease and utility costs reporting and tracking by building and down to items being stored within the facilities is the responsibility of the contractor.
2..1.8 Emergency preparedness for facilities: The contractor shall develop a plan to identify strategic resources to prepare for, and recover from, in the event of an emergency or disaster.
2.2 SOFSA Network Management: The Special Operations Forces Support Activity network (SOFSANet) (SOFSA local, wide, sub networks, and NIPRNet (.Mil) presence) is the primary network for the sharing of data between authorized persons, inside and outside the SOFSANet. The SOFSANet must be maintained to DoD, USSOCOM, and local SOFSA DAA (Designated Approving Authority) requirements while keeping costs under control and accessibility as high as possible. The SOFSANet has grown dramatically over the past five years without an overall data or hardware strategy. Multiple programs (COTS, GOTS, and internally developed) contain the same or similar data causing data consistency issues, lost labor hours (maintaining the same data in different places), and reporting issues.
2.2.1 The SOFSANet needs a plan for future data growth utilizing fewer systems with a centralized data repository for accessing all cost, schedule, and performance data on all SOFSA projects and Enterprise activities (as referenced in SOO paragraph 2.2).
2.2.2 The contractor is responsible for developing a three-year plan that includes the following:
2.2.2.1 Centralized Data Repository: The contractor is responsible for identifying the COTS, GOTS, or customized application(s) that will comprise a Central Data Repository for all SOFSA cost, schedule, and performance data.
2.2.2.2 The contractor is responsible for describing the solution they have selected for the SOFSA Central Data Repository, cost for the solution, schedule to implement the solution (including replacing existing SOFSANet applications), what reporting tool(s) will be used for “canned” as well as “ad-hoc” reporting, how the transition will not affect daily SOFSA operations, and any training needed for the users to properly operate the new system. The contractor is also responsible for describing how both contractor and Government will access appropriate metrics/reports in order to access contract performance in all areas.
2.2.2.3 Network Availability: The contractor is responsible for describing how they will maintain all network services availability, from the workstation perspective, at 99.99% during Federal workdays between the hours of 0700 and 1700, and at 95% for all other days and hours.
2.2.2.3.1 The contractor should describe how they would approach the above requirements concerning personnel requirements and skill sets, hardware and software configuration, and, if necessary, any outside support required.
2.2.2.4 Network Change Management: The contractor is responsible for describing the network change management process
2.2.2.4.1 Describe what Network Change Management process flows and documentation you would use for the following changes to the SOFSANet; an IAVA, new server, new software, port rule change on the primary firewall, and software upgrade.
2.2.2.5 The contractor is responsible for describing their methodology in implementing DoD, SOCOM regulations and directives for information assurance.
2.2.2.6 Configuration Management: The contractor is responsible for describing their methodology for configuration management of the network.
2.2.2.6.1 The contractor is responsible for describing their methodology for configuration and management for hardware/software.
2.2.2.6.2 Customer Support: The contractor is responsible to provide timely and cost efficient help desk support.
2.3 Data Management and Analysis: Contractor will identify the COTS/GOTS application that will serve to
a) access all pertinent contractual data, b) generate the metrics and reports for contract performance assessment, c) provide insight to the Government as to trends, risks derived from said data, d) recommend risk mitigation strategies/options for Government/Contractor to evaluate for possible action, and e) will serve to identify pertinent performance data to as inputs to fee determination at the task order level.
3.0 Management Objective
3.1 The contractor is responsible for identifying, wherever possible, innovative business processes designed to maximize space, incorporate energy efficient practices, improve infrastructure, analyze trends, and utilize advanced facility administrative tools to document space obligated, current status of facility utilization, planned facility improvements, planned funding for follow on years, and organizational progress desired in this SOO.
3.1.1 The contractor is responsible for identifying an acceptable plan to include the development of proposed metrics for implementing an appropriate level of Government oversight needed for the Facilities Management Plan proposed for this SOO.
3.2 The primary objective is to allow the contractor the maximum flexibility to be innovative in the management the program schedule, performance, risks, warranties, subcontracts, and data to produce an end item that satisfies the government’s performance requirements.
3.2.1 Maintain clear government visibility into the program schedule, performance, and risk.
3.3 Design Review: Using a combination of Network Change Management documentation and meetings with government personnel the contractor shall ensure they have fully informed, and received government approval, for any design change to the SOFSANet.
3.3.1 DAA Review: Throughout the Network Change Management process and meetings with government personnel, the contractor shall keep the DAA fully informed of all changes to the approved SOFSANet baseline configuration.
3.3.2 Cost Control: The contractor is responsible for presenting to the government their annual MIS spending plan no later than three months before the beginning of the Governments fiscal year for review, comments, and approval/disapproval. Throughout the course of the fiscal year, any purchases made against the approved budget will reference the appropriate line number of the budget. Any budget shortfalls or excesses will be reported to the government. Changes to the spending plan will be coordinated Government for approval/disapproval.
3.4 Corporate Investment: During the execution in the Enterprise environment, various tools sets (software, hardware) may enhance performance success. The Government expectation is that industry will have the ability to bring these tools to the Enterprise as long as the Government DAA is made aware of any software/hardware placed on the network.
4.0 Metrics: The metrics proposed for the Enterprise efforts against the PWS will be used to determine the right measures are in place for performance.
File details come from the government source that posted it. Updated .