TSO_IT_Services_Contract_-_PWS_12032014.doc

Performance Work Statement (PWS)

Technology Services Organization (TSO) Information Technology (IT) Services Contract

Vision Statement 1 Introduction

1.1 Background

1.1.1 Technology Services Organization (TSO)

1.2 Scope

1.2.1 Technology Services Organization (TSO)

1.2.2 On-Call and Surge Support

1.2.3 Optional/Additional Workload

2 General Information

2.1 Key Positions

2.1.1 AROWS Subject Matter Expert (SME)

2.1.2 MCTFS Project Manager

2.1.3 MCTFS Architect

2.1.4 MCTFS Senior Technical Lead

2.1.5 MCTFS Senior Design Specialist

2.1.6 MCTFS Senior Test Specialist

2.1.7 MCTFS Senior Training Specialist

2.1.8 MOL Systems Architect

2.1.9 SSD Master Oracle Database Administrator

2.1.10 SSD DB2 Subject Matter Expert

2.1.11 SSD ADABAS Subject Matter Expert

2.1.12 SSD IT Operations Lead

2.1.13 SSD Application Administrator Subject Matter Expert

2.1.14 SSD Mainframe Technical Support Subject Matter Expert

2.1.15 SSD Storage Management Subject Matter Expert

2.1.16 SSD Red Hat Linux Subject Matter Expert

2.2 Contract Administration

2.2.1 Specific Tasks

2.2.2 Labor Reporting

2.2.3 Work Locations and Hours

2.3 Non-Personal Services

2.4 Privacy Act and HIPPA

2.5 Required Training and Certifications

2.5.1 Annual Training

2.5.2 Security Training and Education

2.5.3 IT Certification

2.6 Travel/Temporary Duty (TDY)

3 Performance Requirements

3.1 Performance Standards and Acceptable Quality Levels

3.2 General Requirements

3.2.1 Program Management

3.2.2 Post-Award Kick-off Meeting

3.2.3 Program Management Plan

3.2.4 Transition

3.2.5 Subcontract Management

3.2.6 Specific Tasks and Workload Distribution

3.2.7 Labor Reporting

3.2.8 Management Reviews

3.2.9 Contract Cost and Performance Reporting

3.2.10 General Requirements Performance Standards and Acceptable Quality Levels

3.2.11 General Requirements Constraints

3.3 High Level Objective (HLO) 1 - Systems Engineering and Integration

3.3.1 HLO1 Tasks

3.3.2 HLO1 Performance Standards and Acceptable Quality Levels

3.3.3 HLO1 Constraints

3.4 HLO2 - Mission Support

3.4.1 HLO2 Tasks

3.4.2 HLO2 Performance Standards and Acceptable Quality Levels

3.4.3 HLO2 Constraints

3.5 HLO3 Systems Operations and Support

3.5.1 HLO3 Tasks

3.5.2 HLO3 Performance Standards and Acceptable Quality Levels

3.5.3 HLO3 Constraints

3.6 HLO4 Cybersecurity

3.6.1 HLO4 Tasks

3.6.2 HLO4 Performance Standards and Acceptable Quality Levels

3.6.3 HLO4 Constraints

3.7 HLO5 Help Desk

3.7.1 HLO5 Tasks

3.7.2 HLO5 Performance Standards and Acceptable Quality Levels

3.7.3 HLO5 Constraints

4 Security and Safety Requirements

4.1 Personnel Security

4.1.1 Eligibility

4.1.2 Command Access Card (CAC) Eligibility

4.1.3 Security Clearances

4.1.4 Access to and Accountability and Safeguarding of Classified Material

4.1.5 IT Levels

4.1.6 Facility Notification

4.1.7 Facility Security Clearance

4.1.8 Security Administrative Assistant (SAA)

4.2 Applicable Directives

5 Government Furnished Equipment and Information

Vision Statement Maintain position as THE Marine Corps business system integrator by enhancing customer service and delivering consistent performance (business value) while sustaining a culture focused on people, processes, and technology.

1 Introduction

The TSO provides information technology support for software development, systems engineering, maintenance, and operations of Financial Management (FM) and Human Resource Management (HRM) Business Mission Area (BMA) systems including integrated Pay & Personnel, Financial Management (FM) and Accounting systems in support of the United States Marine Corps (USMC), Department of the Navy (DON) and Department of Defense (DoD). TSO support activities include functional support for systems, studies, assessments, consulting, program and project management as well as the integration and maintenance of the networks on which supported systems will be operated.

1.1 Background

1.1.1 Technology Services Organization (TSO)

Mission: The TSO provides development, design, production and maintenance support of information technology systems, particularly pay, personnel and accounting systems, for the Marine Corps as well as DoD components, services and agencies.

The TSO provides software development, systems engineering, and technology support to the United States Marine Corps (USMC) and other select DoD customers. The TSO operates as a Government owned, Government operated, Contractor supported (GOGOCS) Integrated Product Team (IPT). The TSO supports a number of business mission areas sponsors within the Marine Corps including the Deputy Commandant, Programs and Resources (P&R) and Deputy Commandant, Manpower and Reserve Affairs (M&RA). The TSO provides systems support for the Defense Finance and Accounting Service (DFAS), the U.S. Navy, and the U.S. Air Force. Additionally, the TSO provides administrative and IT support to other Marine Corps organizations, further referred to as supported organizations, principally located in Indianapolis, Indiana and Kansas City, Missouri, including Marine Corps Pay Requirements Directorate (MCPRD), Marine Corps Disbursing Operations and Systems Section (MCDOSS), and Marine Corps Pay Reconciliation Team.

The primary services to be performed will support the review, analysis, documentation, design, programming, testing and subsequent implementation of change requests. Change requests are principally levied on the TSO through agreements reached with customers during a Configuration Control Board (CCB) or in conjunction with standalone change requests or system discrepancies. Change requests may result from new or modified functional requirements, initiatives associated with improving system performance, changes due to legislation, mandated regulatory changes, and discrepancy resolution necessary to ensure proper system performance.

Marine Corps BMA Functional Area Managers (FAM), Program Managers, System Owners and Functional Managers continuously generate change requests for the TSO throughout the period of performance. These change requests are intended to provide better service to commanders, management headquarters, small unit leaders, and individual Marines through automation of new entitlements or through business process reengineering (BPR) improvements. Contractor support is required to assist the TSO in producing and implementing software and system engineering enhancements related to these change requests, providing customer and infrastructure support, and affecting continuous process improvement. All system changes originate from funded requirements initiated by functional representatives of TSO customers.

All change requests represent increases or decreases to the TSO workload throughout the period of performance. Assuming a full workload at the start of the period, workload increases stem from a number of sources while the major area of change is found in functional and technical change requests. Change primarily begins with law or legislation (e.g. National Defense Authorization Act (NDAA)) and regulatory, policy and procedural requirements (e.g., Joint Staff, DoD, DON, and Commandant of the Marine Corps (CMC), Warfighters, etc.). Other changes result from BPR efforts and technology advances necessary to improve business and technical efficiencies. Finally, the unpredictable nature of overseas contingencies contributes to the variable workload levied upon the TSO.

1.2 Scope

1.2.1 Technology Services Organization (TSO)

The TSO requires contractor services for a myriad of highly complex, Government-designed and Government-owned enterprise business-critical systems. The TSO provides critical technical services for a unique blend of Marine Corps enterprise business systems that cut across the spectrum of technologies and platforms. As a result, a wide variety of technical skills and experience levels are required to support the various programming languages, database platforms, operating systems, hardware, and software. The services to be performed are detailed in Section 3 and categorized as follows:

· General Requirements

· HLO 1 Systems Engineering and Integration

· HLO 2 Mission Support

· HLO 3 Systems Operations and Support

· HLO 4 Cybersecurity

· HLO 5 Help Desk

The services to be performed require a balanced mix of experience including senior, middle, and junior technical staff, subject matter experts, consultants, as well as management and administrative staff, all capable of working within the TSO’s GOGOCS Integrated Product Team (IPT). The Contractor is expected to provide resources with a high degree of specialized technical skills and experience with the enterprise-class business systems, including underlying technologies supported by the TSO. The Contractor must be able to adjust staffing levels to support fluctuating workload at all locations. The Contractor shall match personnel skills to the work or task to optimize resource utilization. A detailed description of each system or environment is provided in Appendix A. TSO supported and supporting systems include:

Enterprise-class Business Systems

· Marine Corps Total Force System Family of Systems

· Marine Corps Total Force System (MCTFS)

· Unit Diary/Marine Integrated Personnel System (UD/MIPS)

· Operational Data Store Enterprise (ODSE)

· Marine Online (MOL)

· W2/W2 Corrections (W2/W2C)

· Document Tracking Management System (DTMS)

· Marine Corps Administrative Analysis Team (MCAAT)

· Marine Cash (MC)

· Management Reports (MNGTRPTS)

· Standard Accounting Budgeting and Reporting System (SABRS)

· Marine Corps Financial Integrated Analysis System (MCFIAS)

· SABRS Management Analysis Retrieval Tool System (SMARTS)

· Program Budget Documentation Database (PBDD)

· Civilian Personnel Information Management System (CPIMS)

· Unfunded Priority List (UPL)

· Current Year Deficiency (CYD) Database

· PORTAL

· Marine Corps Orders Resource System (MCORS)

· Marine Corps Reserve Order Writing System (MROWS)

· Marine Corps Permanent Duty Travel (MCPDT)

· Marine Corps Single Orders Repository (MCSOR)

· Command Legal Action Module (CLAM – formerly MCEAS)

· Navy Reserve Orders Writing System (NROWS)

· Air National Guard Order Writing System (AROWS)

· Air Force Reserve Order Writing System (AROWS-R)

Organization Support Tools

· Business Enterprise System (BES)

· JIRA

· Decision Logic Table-Web (DLT-Web)

· Enterprise Management System (EMS)

· Sharepoint (SP)

· TSO Sustainment Environment

The TSO, in conjunction with the Manpower Information Systems Support Activity (MISSA), is responsible for the facilitation and generation of system enhancements for the Marine Corps Total Force Family of Systems. These systems consist of MCTFS, Unit Diary/Marine Integrated Personnel System (UD/MIPS), Total Force Administrative System/Marine on Line (MOL) and the Operational Data Store Enterprise (ODSE). This is accomplished through a combined effort with the Marine Corps Pay Requirements Directorate, HQMC (P&R) and Manpower Information (MI) Systems Division, MQMC (M&RA).

· System enhancements are subsequently documented in the Functional Requirements Document (FRD). The FRD provides for a maintainable standardized reference of MCTFS functionality for training, future design considerations, and integration of new functionality. The FRD provides a database of business rules upon which MCTFS is built. The FRD is a living document that is updated in conjunction with every major MCTFS software release. Through the utilization of Decision Logic Tables (DLT), File Descriptions, and other technical documentation business rules are identified and captured within the FRD in common English language to make it easily consumable and understandable by the laymen. This includes identifying business rules for each process including a detailed breakout at the basic Type Transaction Code (TTC) level with general business rules defined for called modules. The FRD also documents all generated system advisories as additional general business rules.

· MI Systems Division requires both technical and functional support spanning the entire spectrum of the MCTFS Family of Systems. Functional support includes, but not limited to, analyzing and developing new requirements for the MCTFS Family of Systems, participation in Joint Application Development efforts, etc. Technical support includes maintaining and enhancing the Command Profile and Manpower Performance Indicator application and other in-house technical initiatives.

· MOL Help Desk supports and assists management in the numerous administrative and command processes conducted in Marine Online by the Active Duty and Reserve components of the Marine Corps. Support includes training and technical guidance for each of the over 20 Marine Online Modules covering processes such as Leave, Promotion Recommendations, Composite Score Calculations, MOL Security and many others. The Help Desk consolidates their efforts and forwards issue solutions and enhancements to the Functional Managers for system improvements.

The TSO supports the Marine Corps travel function and Marine Corps travelers through Tier 1 and Tier 2 Help Desk support. Contract services performed include supporting civilian and uniformed Marine (active and reserve) Temporary Additional Duty (TAD) travelers through Marine Corps Defense Travel System (DTS) via voice, email and web. Support includes Marine Corps Reserve unit travel administrators through Marine Reserve Orders Writing System (MROWS) Help Desk services. Support for the Marine Corps travel function includes training, curriculum development, Staff Assist Visits (SAVs) and travel function monitoring & reporting. DTS & MROWS Help Desk services are performed at the MCITC in Kansas City, Missouri.

1.2.2 On-Call and Surge Support

TSO supported systems, on an unspecified but recurring basis, as well as the Marine Corps Enterprise Network (MCEN), Marine Corps Enterprise Information Technology Center (MCITC) & the Marine Corps Enterprise IT Services (MCEITS) where many of the TSO supported systems are hosted, suffer unannounced/unanticipated periods of disruption. Disruption of these Marine Corps business-critical systems and the enterprise functions they support demands immediate resolution. Designated TSO IPT members, both Government and contractor personnel, will participate in and be available to support “On-call” duties should a service disruption require immediate response and resolution. Identification and designation of on-call personnel is task dependent and delineated within Appendix C. Should a service disruption extend beyond a reasonable period (more than 36 hours), TSO government and contract personnel will be expected to both extend (work more than eight (8) hours per day) and adjust work schedules to support service restoration activities. Contractor on-call and surge support is not unique, rather just reflective of an increase in workload and/or adjusted work schedule, and defined as part of the performance requirements in Section 3.

1.2.3 Optional/Additional Workload

The TSO, MISSA, MI and MCPRD require contract services to assist in the Navy’s conversion to a MCTFS Pay Module. Services include tasks identified in Section 3 of this PWS. Initial efforts will culminate in the ability to write the change requests for the development of an implementation utility for the initial load of Navy records to MCTFS. Ultimately, services will include the full range of tasks within Section 3 to ensure MCTFS supports the Navy’s pay needs as well as it serves the Marine Corps needs.

The TSO, in conjunction with Accounting Branch (RFA), P&R Dept and DFAS, require contract services to assist in the Navy’s conversion to a SABRS Military Personnel pay (MilPers) accounting system. Services include tasks identified in Section 3 of this PWS. Services will include the full range of tasks within Section 3 to ensure SABRS supports the Navy’s MilPers accounting needs as well as it serves the Marine Corps needs.

TSO GOGOCS IPT services are continually being sought by existing and new customers. Migration of systems to TSO support is highly variable and typically event driven.

DTS Help Desk support requirement will increase when the Marine Corps Reserve component begins utilizing DTS through the planned Import/Export functionality with MROWS. This implementation and the subsequent addition of ~37,000 Marine Corps Reserve travelers will likely begin during the second half of the base period of performance; therefore additional DTS Help Desk support will be expected.

1.2.3.1 Navy Pay Modification (PayMod) Initiative & Clean Audit Support

The TSO continues to support the DON’s enterprise business systems modernization and audit compliance efforts. Support includes assessments for extending the MCTFS Family of Systems (FoS) and the Standard Accounting Budgeting and Reporting System (SABRS) to the U.S. Navy and entire DON staff. Should leadership determine migrating to MCTFS and/or SABRS is in the best interests of the DON, the contractor shall provide additional technical and functional resources commensurate with tasks identified in Section 3, as optional workload.

1.2.3.2 DTS Help Desk

The Government anticipates an increase (30%) in DTS/MROWS Help Desk support with the integration of MROWS and DTS supporting Marine Corps Reserve personnel world-wide TAD travel. Increased support requirements will be aligned to the migration of reserve units onto DTS, likely in three increments (10% increase each increment). In addition to the increase in workload, the DTS Help Desk will move to “24x7” support. The DTS Help Desk Guide outlines the drivers for this increased support requirement and is contained in Appendix C.

1.2.3.3 New System Support

The TSO expects to take on additional systems support, however, the number and size of new systems to be supported is unknown. The contractor can expect up to 10% increase in annual workload as a result of new system support. Contractor services required for new system support would be identical to tasks identified in Section 3.

2 General Information

2.1 Key Positions/Personnel – Key Personnel may be required to travel at least quarterly to the Indianapolis site and periodically to customer locations to support testing and JAD sessions.

2.1.1 AROWS Subject Matter Expert (SME)

The AROWS SME is responsible for program activities related to analysis, design

(including fit/gap analysis), documentation, development, and developmental (unit) testing of the Air National Guard Order Writing System. Activities include presenting proposed design options to business users and ANG leadership, generating detailed design documentation, and documenting requirements and designs for reporting and business intelligence. The SME shall have experience in client facing roles with Reserve Order Writing or similar HRM applications (Reserve Pay and Benefits, JTR) and Business Intelligence solutions. The SME must possess an in-depth understanding of Air National Guard Order Writing functionality, and be capable of translating business requirements to detailed functional and technical design.

2.1.2 Marine Corps Total Force System (MCTFS) Project Manager

The MCTFS Project Manager - shall be a working Project Manager overseeing the integrated team using TSO constraints. The MCTFS Project Manager shall ensure an efficient, effective, and economical level of support is provided to the TSO; provide oversight of staff and support activities; oversee review of project deliverables and ensure quality meets or exceeds customer expectations; maintain contract costs; coordinate with the COR and as required fill vacancies; manage overall contract performance and understand the needs and expectations to ensure TSO customer satisfaction. The Project Manager shall have experience providing oversight of large, multi-functional project teams, preferably in a mainframe systems development environment, and planning and managing complex tasks sometimes under tight budget and time constraints. The Project Manager shall have a background in system life cycle development; strong management and leadership, written and oral communications skills; familiarity with industry best practices; and a working knowledge of Government contract and subcontract management.

2.1.3 MCTFS System Architect

The MCTFS System Architect is responsible for developing, communicating, maintaining, and enforcing the MCTFS architecture. The System Architect will be expected to understand solution components and how they inter-operate to support business processes and management information needs. The System Architect will be expected to present proposed design solutions to both technical and functional staff. The System Architect shall be responsible for interface and integration strategies with external systems and processes, including determining, understanding, and maintaining business requirements for those interactions. The System Architect shall be responsible for ensuring compliance with external requirements. The System Architect shall possess extensive knowledge of MCTFS online and batch processes as well as the MCTFS master file structure. The System Architect shall have significant, direct experience deploying and sustaining mainframe information systems. This position requires an individual with extensive mainframe development skills, application knowledge, and business experience with the ability and desire to lead technical solutions.

2.1.4 MCTFS Senior Technical Lead

The MCTFS Senior Technical Lead is responsible for ensuring changes to the system are being incorporated in a technically efficient manner within the MCTFS. Must have extensive mainframe development expertise. Must be able to interpret design specifications, analyze those specifications, incorporate logic into MCTFS computer programs, provide efficient program unit test, and implement that logic into the production mainframe environment. Must be able to ensure functional and technical requirements are incorporated into the logic. The Sr. Technical Specialist shall collect, track, and report test metrics and brief senior leadership on programming status. The Senior Technical Lead shall possess extensive experience with system analysis, design, and programming of information systems in a mainframe environment. Knowledge of integrated pay and personnel systems is strongly desired. The following additional skills and experience are preferred:

• Experience working with mainframe development tools

• Experience in both the batch and online mainframe environments

• Experience with flat file and VSAM data structures.

• Experience with relational databases, specifically DB2

2.1.5 MCTFS Senior Design Specialist

The MCTFS Senior Design Specialist is responsible for activities related to analysis, design and documentation of change requests specific to MCTFS. Must be able to interpret change specifications, analyze those specifications, and incorporate logic into MCTFS documentation for submission to the programming staff. Must be able to ensure functional and technical requirements are incorporated into the design. The MCTFS Senior Design Specialist shall collect, track and report test metrics and brief government Technical Representative and/or TSO customers on design status. The Senior Design Specialist shall extensive experience with system design and analysis of information systems. Knowledge of integrated pay and personnel systems is strongly preferred.

2.1.6 MCTFS Senior Test Specialist

The MCTFS Senior Test Specialist is responsible for MCTFS system test activities. Must be able to write detailed test plans, understand scenario and script development, and requirements traceability for full system integration test. Must be able to ensure functional and technical requirements testing, performance testing, system interface testing, and security testing are planned and executed. The MCTFS Senior Test Specialist shall collect, track and report test metrics and brief government Technical Representative and/or TSO customers on test status.

The MCTFS Senior Test Specialist shall possess extensive experience in system testing of information systems. Knowledge of integrated pay and personnel systems is strongly preferred.

2.1.7 MCTFS Senior Training Specialist

The MCTFS Senior Training Specialist is responsible for the analysis, design, development, testing and fielding of training artifacts, guides, classroom instruction and Computer Based Training (CBT). Ensures quality control checks are built into the successful implementation of training plans, deliverables and strategies. Must understand and translate business requirements and the system configurations/solutions into training artifacts as they relate to MCTFS. Must have demonstrated experience specific to software training development, implementation, and maintenance. The MCTFS Senior Training Specialist shall possess extensive experience with mainframe application development. The MCTFS Senior Training Specialist must have direct experience working within an integrated pay and personnel environment.

2.1.8 Mid-Tier System Architect

The Mid-Tier System Architect is responsible for developing, communicating, maintaining, and enforcing the mid-tier/web-based systems architecture. The Mid-Tier System Architect will understand all solution components and how they inter-operate to support business processes and management information needs. The Mid-Tier System Architect will be expected to present proposed design solutions to both technical and functional staff. The Mid-Tier System Architect shall be responsible for interface and integration strategies with external systems and processes, including determining, understanding, and maintaining business requirements for those interactions. The Mid-Tier System Architect shall be responsible for ensuring compliance with external requirements. The Mid-Tier System Architect shall possess extensive knowledge of online and batch transaction processes as well as the associated file structures. The Mid-Tier System Architect shall possess extensive experience deploying and sustaining mid-tier/x86 information systems. The Mid-Tier Systems Architect must possess extensive Java development skills with the ability to lead technical solution development and implementation. Knowledge and experience operating in a DOD STIG compliant environment and possessing advanced security certifications (i.e. CISSP) preferred.

2.1.9 Master Oracle Database Administrator

The Master Oracle DBA shall assist with the architecture, design, and overall strategic vision and deployment of all Oracle databases under the purview of the TSO. The Master Oracle DBA shall possess extensive direct experience with the design, administration, and management of Oracle databases. This experience shall include databases deployed in support of transactional, reporting, warehousing, archiving, and batch based systems. The Master Oracle DBA shall also possess extensive experience in the administration and operation of the Oracle Real Application Cluster (RAC) technology and the application and utilization of the Oracle Recovery Manager (RMAN). This position requires an individual with extensive database development skills, application knowledge, and business experience with the ability and desire to lead technical solutions.

2.1.10 DB2 Subject Matter Expert (SME)

The DB2 SME shall possess extensive direct experience as a DB2 DBA, preferably in conjunction with a COBOL/CICS interface. The DB2 SME shall possess extensive experience in data modelling with the ability to understand and translate business requirements to database specifications, and then implement those specifications in an efficient database design, SQL tuning and general performance tuning skills. The DB2 SME must possess the ability to mentor junior team members in a distributed work environment in order to build a strong team and be an effective communicator who can research complex technical issues and communicate them in an understandable manner to a variety of audiences. The DB2 SME shall possess direct experience with DB2 Connect configuration experience. Additional experience using Data Studio, DB2 Administration Tool and Mainview, the automation of routine tasks using REXX, in the partitioning and temporal tables and data modeling tools are preferred.

2.1.11 ADABAS Subject Matter Expert (SME)

The ADABAS SME shall have extensive knowledge of ADABAS, Predict, Natural Security, and SAF. The ADABAS SME is responsible for but limited to such tasks as efficient design and implementation of ADABAS databases, the determination of system parameter settings, object sizing, etc. and the performance tuning of all ADABAS database instances and deployments. The ADABASE SME shall possess advanced troubleshooting skills, including utilization of Trim when appropriate, the routine and reliable backup and recovery of all ADABASE databases and datastores as well as the security administration of all such deployments. The ADABAS SME shall possess the ability to understand and translate business requirements to database specifications. The ADABAS SME shall possess direct experience with N2O, configuration experience preferred. The ADABAS SME shall possess the ability to mentor junior team members in a distributed work environment in order to build a strong team. Experience with Natural, installation and configuration of EntireX, Natural Engineer, and/or ApplinX, as well as MQSeries configuration and administration preferred.

2.1.12 IT Operations Lead

The IT Operations (Ops) Lead is responsible for the coordination, scheduling, resource assignment, and tracking of IT service delivery for TSO Operations. The IT Ops Lead shall possess extensive experience with IT operations and IT service delivery. The IT Ops Lead shall possess experience implementing and delivering IT service value utilizing the ITIL management framework. ITIL and/or PMP certification and experience with Remedy preferred.

2.1.13 Applications Administrator Subject Matter Expert (SME)

The SSD AppAd SME, in collaboration with the TSO web development teams, is responsible for the development of the optimal application server configurations required to satisfy the requirements of customer change requests or TSO requests for service. The AppAd SME shall have extensive direct experience in the design, configuration, deployment, and management of Oracle WebLogic, IIS and or Apache web application products in architectures that utilize single instance Microsoft SQL Server, Oracle databases as well as Oracle Real Application Clusters (RAC). Cognos experience is preferred.

2.1.14 Mainframe Technical Support Subject Matter Expert (SME)

The Mainframe Tech Support SME is responsible for activities to ensure the health and stability of the mainframe operating environment. The Mainframe Tech Support SME must possess extensive knowledge of mainframe system resource components and associated performance & monitoring tools to provide real-time and strategic recommendations to address system resource requirements. The Mainframe Tech Support SME is responsible for analyzing the impact of executive software modifications to applications, providing recommendations to negate or minimize impact. The Mainframe Tech Support SME will be expected to understand the interrelations between the operating system and executing applications in order to identify system requirements and improvement opportunities. The Mainframe Tech Support SME must be able to clearly communicate with both application and system programming personnel to analyze and resolve system issues. The Technician must possess an understanding of SMF and RMF records with the ability to develop statistical and analytical processes in order to provide management relevant information. The Mainframe Tech Support SME must also understand SMS and able to provide ACS change recommendations to satisfy business requirements. The Mainframe Tech Support SME must possess experience with disaster recovery principles and operations, and able to provide improvement recommendations.

The Mainframe Tech Support SME shall possess extensive experience supporting and maintaining mainframe environments. This position requires an individual with zOS system programming knowledge to ensure optimal system performance. Knowledge of the MCTFS and SABRS applications, along with DISA procedures and processes is preferred.

2.1.15 Storage Management Subject Matter Expert (SME)

The Storage Management SME is responsible for the daily administration and management of all network based storage devices under the purview of the TSO. This includes the total lifecycle management of initial installation of new systems to the retirement and disposal of old devices in accordance with appropriate directives and regulations. The Storage Management SME shall possess extensive experience in the configuration, management, installation, and administration of storage area networks and fabrics designed to support highly virtualized server environments. The Storage Management SME shall direct experience in the configuration, management, and administration of storage area networks and fabrics designed to support Oracle Real Application Clusters (RAC) and utilize GigE backbone for iSCIS, NFS & CIFS based technologies.

2.1.16 Systems Administration Subject Matter Expert (SME)

The Systems Administration (SysAd) SME is responsible for the daily administration and management of all Linux based hosts under the purview of the TSO. This includes the total lifecycle management of initial installation, retirement and disposal of systems. The SysAd SME shall possess expertise greater or equivalent to that of a Red Hat Certified Engineer. In addition the SysAd SME shall possess extensive direct experience in the administration and configuration of RHL servers, both physical and virtual, in the support of an Oracle database, (both single instance and Real Application Clusters), and WebLogic centric environments. The SysAd SME shall possess extensive direct experience in the management and administration of SysAd servers in a shared storage topology that primarily utilizes GigE backbones and iSCSI, NFS & CIFS based technologies. The SysAd SME shall possess experience in configuring, administrating, and maintaining SysAd servers. Experience with the Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIG), the DoD Information Assurance Certification and Accreditation Process (DIACAP), and the DoD Directive 8500.1 Information Assurance preferred.

2.2 Contract Administration

2.2.1 Specific Tasks

The contractor will be assigned specific tasks via a JIRA ticket. JIRA is a commercial-off-the-shelf (COTS) issues management tool that the Government has tailored to support the formal assignment of specific tasks to the contractor and receipt of task deliverables/completion.

The contractor can expect more than 1500 specific tasks to be assigned annually. Specific tasks are typically associated with Software Development Lifecycle (SDLC) schedule and milestones, however, some specific tasks identify work incrementally (monthly) or for the entire period of performance (annually). Specific tasks, assigned via a JIRA ticket, are used to assign contractor work for all projects types including:

· Designing, programming and/or testing change requests

· Document creation, reviews and/or updates

· Operations and implementation support

· New technology research and analysis

· Project management, process improvement and quality assurance activities

The flexibility of JIRA has allowed the TSO to utilize this tool for a large number of business and IT support functions. The functions supported described in Appendix C documents.

2.2.2 Labor Reporting

An essential component of the TSO’s project and performance management is a robust metrics collection program. TSO uses a labor reporting system (LRS) to record effort (hours) for all employees against every project/activity the organization performs. Currently the TSO utilizes a COTS software-as-a-service product called Replicon TimeBill. Generically this tool is referred to as “LRS-Web”, and is the standard labor reporting and tracking system. In order for TSO to perform sound project and performance management, all TSO employees as well as contractor personnel are expected to record effort (hours) against assigned projects in LRS-Web at least weekly.

2.2.3 Work Locations and Hours

2.2.3.1 Work Locations. TSO contract services work locations currently include:

· Marine Corps Information Technology Center (MCITC) – Kansas City located at 2306 East Bannister Road, Kansas City, Missouri 64131

· BMO Plaza Building located at 135 North Pennsylvania Street, Indianapolis, Indiana 46204

· As attrition occurs and workspace becomes available the Contractor shall onboard resources in the Government-leased facility in Indianapolis at the BMO Building vice other locations; Currently there are 15-20 workspaces available for contractor use

· Wesley Marsh Center, Building 3280 located on Marine Corps Base (MCB) Quantico at 3280 Russell Rd., Quantico, Virginia 22134

Additionally, the Government accommodates a limited number (10 max) of contractor personnel remotely located in other than the aforementioned locations. The contractor shall coordinate with and receive written approval from the Contractor Officer Representative (COR) prior to onboarding and/or assigning work to a remotely located personnel. Remote locations typically have no direct connection with the Marine Corps network, are safe and secure locations (i.e. personal residence or contractor facility), provided by and/or approved for contractor personnel use.

2.2.3.2 Work Hours. Contract services will be performed during the following hours, by location and/or function:

· Contractor services provided at locations in either the Eastern or Central time zones shall be performed between the 0600-1800, but must be at work between 0900-1500 Eastern Time zone government core hours. This maximizes the communication, coordination and collaboration opportunities across the GOGOCS IPT.

· Contract services provided in support of Help Desk functions shall be provided as follows:

· MOL Help Desk Contract services will be provided Monday-Friday 0700-1700 Central time zone

· MROWS Help Desk Contract services will be provided Monday-Friday from 0730-1600 Central time zone

· DTS Help Desk Contract services will be provided Monday-Friday from 0700-1600 Central time zone

· Contract services associated with the “24x5” Mainframe Operations Section will be provided Sunday-Friday in three (3) shifts from 0700-1530 (1st Shift Mon-Fri), 1500-2330 (2nd Shift Sun-Thu) and 2300-0730 (3rd Shift Sun-Thu) Central Time. The weekly schedule begins with 2nd Shift on Sunday.

The contractor shall provide services on an “on-call” basis as previously described in Section 1.3.2.

The contractor shall adjust individual work schedules to support operational events and schedules such as software releases/implementations, routine and adhoc maintenance windows, hardware installation, version upgrades and patching. Schedule adjustments may also be required due to site closures at other IPT and customer locations resulting from inclement weather, facility unavailability and federal holidays, furloughs or shutdowns.

2.3 Non-Personal Services

The Government shall not supervise contract personnel. Under no circumstances shall the Government assign tasks to or prepare work schedules for an individual contract employee. It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of or give the perception of personal services. If the contractor believes that any actions constitute or are perceived to constitute personal services, it shall be the contractor's responsibility to notify the COR and the Procuring Contracting Officer (PCO) immediately.

2.4 Privacy Act and HIPAA

All services performed relative to the requirements identified in this PWS allow access to unclassified or sensitive information covered by the Privacy Act of 1974 and other DoD and USMC regulations. Some information provided by the Contractor during the application process may be subject to the Health Insurance Portability and Accountability Act (HIPAA).

2.5 Required Training and Certifications

2.5.1 Annual Training

The contractor shall ensure all contractor personnel complete required annual training as determined by the Government training officer. Contractor personnel assigned to perform DON IT functions must receive the requisite information assurance, security awareness, and functional competency training as required by their designated level of access and scope of duties.

The Government does not provide contractors with training, with the exception of DoD and DoN mandated information assurance training that is necessary in order to perform contract support. However, per Information Paper, dated 7 May, 2010 by MCCDC/MCB Quantico Counsel, (Ref: FAR, 5 C.F.R Part 2635), Standards of Ethical Conduct for Employees of Executive Branch, paragraph 2.a., ‘The Government may provide training to contractor personnel ONLY if the training is specifically required by a contract term, or if performance requires unique training that can only be provided by the Government (e.g., training on a new Government software program that could not have been anticipated at the time of award of the contact.’

2.5.2 Security Training and Education

The following are the minimum requirements for security education for all contractor personnel:

· Indoctrination of personnel upon employment by the DON in the basic principles of security

· Orientation of personnel who will have access to classified information or assignment to sensitive duties (including IT duties) at the time of assignment, regarding command security requirements

· On-the-job training in specific security requirements for the duties assigned

· Annual refresher briefings for personnel who have access to classified information

· Counterintelligence briefings annually for personnel who have access to information classified Secret or above

· Special briefings as circumstances dictate

· Debriefing upon termination of access

Security education requirements are locally governed by TSO-wide constraints C1.2, C1.29, C1.39 and Business Operations Division constraint C8.30.

2.5.3 IT Certification

Contractor personnel supporting Information Assurance (IA) functions shall obtain the appropriate DoD-approved IA baseline certification (available at http://iase.disa.mil/index2.html) prior to onboarding and being assigned tasks. No waivers will be authorized. Contractor personnel are required to allow certification authority to release certification information to DoD.

Contractor personnel will have up to 6 months to obtain the appropriate Computing Environment/Operating System qualifications for the functions performed. The contractor shall ensure contractor personnel certifications and qualifications are maintained on the appropriate periodic basis (i.e. annual, every 3 years).

2.6 Travel / Temporary Duty (TDY)

Travel to Government or non-Government CONUS facilities will be required and may require additional coordination due to security requirements (i.e. Visitor Requests). Travel to OCONUS facilities and sites is not anticipated. In addition to previously identified Key Personnel travel, the contractor can expect similar, additional travel requirements for other staff members. All travel requirements (including plans, agenda, itinerary, and dates) shall be pre-approved by the COR (subject to local policy procedures) and are on a cost reimbursable basis. The contractor shall make necessary travel arrangements for contractor personnel. Costs for travel shall be billed in accordance with the regulatory implementation of Public Law 99-234 and FAR 31.205-46 Travel Costs (subject to local policy and procedures; may reference FAR).

3 Performance Requirements

Contract service performance requirements are categorized as General Requirements and High Level Objectives (HLOs) and organized as follows:

1) General Requirements

2) HLO1 System Engineering & Integration

3) HLO2 Mission Support

4) HLO3 Systems Operation & Support

5) HLO4 Cybersecurity

6) HLO5 Help Desk

Appendix C provides the Table of Content for documented constraints. Constraints associated with tasks will be annotated either directly with the task or in a mapped table at the end of each sub-section. Constraint documents have been made available as part to the Electronic Reading Room, downloadable from the ARMDEC SAFE site.

3.1 Performance Standards and Acceptable Quality Levels

Contractor performance will be evaluated on established Performance Standards (PS) and associated Acceptable Quality Levels (AQLs). PSs and associated AQLs measure performance for:

· Timely completion of assigned tasks and tickets – PS1, PS3 and PS4

· Quality of assigned task deliverables – PS2

PSs and associated AQLs are identified for General Requirement and HLO tasks in the following table and defined within each sub-section:

PS3 (AQL3A, B, C, D & E)

PS4 (AQL4A, B & C)

3.2 General Requirements

3.2.1 Program Management

The contractor shall be responsible for determining the staffing, management, organization, authority, responsibility, control, and extent to which the areas of cost, schedule, technical performance, operations maintenance, quality improvement, delivery of products, software development, systems engineering management, and project administration apply to this program. The contractor shall establish clear organizational lines of authority and responsibility to ensure effective management of the resources assigned to the requirement. The contractor must maintain continuity between the operations at all locations where contractor personnel are assigned to perform services on this contract.

3.2.2 Post-Award Kick-off Meeting

The contractor shall participate in a Government scheduled post-award kick-off meeting with the PCO and COR within seven (7) business days of contract award. The meeting will provide an introduction between the contractor and Government personnel who will be involved with the contract. The meeting will provide the opportunity to discuss technical, management, and security issues, travel authorization and reporting procedures to include initial report suspense dates for all recurring program and contract report requirements. The meeting will afford the contractor the opportunity to present the draft Program Management Plan.

3.2.3 Program Management Plan (PMP)

The contractor shall prepare a Program Management Plan (CDRL B001) depicting the contractor’s activities for managing the services performed on this contract to ensure that all scheduled objectives are achieved and quality performance is delivered.

3.2.4 Transition

The contractor shall follow the Transition Plan (CDRL B002), submitted as part of the proposal, and keep the Government fully informed of status throughout the transition period. The incumbent contractor shall, in addition to their ongoing responsibilities with respect to any assigned workload, provide support to the contractor enabling a smooth transition sufficient to understand the underlying system structure, source code, architecture, processes and business rules. Throughout the transition-in/transition-out periods, it is essential that attention be given to minimize interruptions or delays to work in progress that would impact the mission.

3.2.4.1 Transition-In Activities. Transition ensures the incoming contractor personnel is afforded the opportunity to develop a thorough understanding of the existing system life-cycle management processes and system requirements, as well as allow for knowledge transfer with the incumbent contractor. The contractor shall brief the transition plan at the post-award kick-off meeting, based on Government collaboration, and finalize the Transition Plan for the migration of assigned workload within five (5) business days of the kick-off meeting. All transition-in activities will be based on a transition period of no more than ninety (90) calendar days. The transition shall ensure minimum disruption to vital Government business processes. The contractor shall minimize service degradation during and after transition.

Although specifically identified as Transition-In activities, coordinating & performing facility and Common Access Card (CAC) badge issue in Kansas City, and monitoring physical security of assigned spaces and visitor access in Indianapolis, will continue throughout the life of the contract for all employment types (Civ, Mil, Ctr).

3.2.4.2 Transition-Out Activities. The contractor shall provide a draft Transition-out plan for transitioning work from this contract to a follow-on effort. The draft Transition-out plan shall address how the contractor will formally coordinate with the Government and subsequent incoming contractor management and staff in order to transition.

3.2.5 Subcontract Management

The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance on this requirement. The contractor shall describe their processes and procedures for selecting and managing subcontractors. The contractor may add to, or remove subcontractors from their team after notification and approval from the PCO. The contractor will manage work distribution to ensure there are no organizational conflict of interest (OCI) considerations. The contractor shall integrate subcontractors into GOGOCS IPT and the contractor’s program management processes.

3.2.6 Specific Tasks and Workload Distribution

The contractor shall ensure timely and effective…