PWS_PDSS_Draft.pdf

Performance Work Statement for

Product Data Systems

Air Force Life Cycle Management Center Technical Services Division

AFLCMC/LZP-Robins

TBD

TO-000 PWS REVISION: 00 2

1. DESCRIPTION OF SERVICES

1.1. Objectives: This Performance Work Statement (PWS) describes the services required to support Department of the Air Force (DAF) Product Data Systems (PDS). These services include systems management, data management, and enterprise migration support required for continued performance of highly specialized technical services at Robins Air Force Base (AFB) supporting product data systems and infrastructure, data management, conversion and migration processes, and transformation initiatives.

1.2. Benefit to United States Air Force: This acquisition will benefit the DAF by providing processes and tools to enable the enterprise division and its customers to acquire, develop, manage, transform, inspect, store, distribute, and maintain technical data.

1.3. Background: The contractor shall provide all labor, supplies, and technical support services necessary to operate and maintain Robins AFB product data hardware and software; to aid Government customers in managing and executing technical data generation, acceptance and sustainment activities, processes, and products within the product data environment; and to support data improvement, cleansing, and migration efforts necessary to prepare data for transition into modernized and/or DAF enterprise-level systems, such as the Enhanced Technical Information Management System (ETIMS), the Technical Order Authoring and Publishing (TOAP) enterprise, solution resulting from the DAF Logistics Capability Initiatives (CI), principally Air Force Product Lifecycle Management (AF-PLM), and other system solutions which may result from system and data center consolidation activities.

AF-PLM is a major initiative designed to establish and implement an Air Force enterprise system which will subsume the majority of the existing Robins product data systems and the data contained within those systems. Since the AF-PLM solution will provide capabilities/functionality similar to those currently supplied by the Robins AFB technical data systems, the level of technical systems and data support required is expected to increase in preparation for AF-PLM implementation, and then decrease as capabilities and data incrementally transition to that implementation and/or other enterprise-level systems.

ETIMS provides the capability for DAF system maintainers to manage their Technical Order (TO) and Electronic TO (eTO) subscriptions and libraries. Much of the data processed and/or managed within the Robins AFB Product Data Systems environments must also reside within the ETIMS in order to satisfy end-user requirements. Portions of the requirements outlined within this PWS are specific to the TO document structure and data loading requirements driven by ETIMS.

TOAP is designated as the organic TO authoring and publishing component of the AF Standard TO Management System. TOAP provides the AF enterprise capability to manage, author, and publish TO publication source content data and enforces authoring and publishing compliance outline in DAF policy documents.

At present, approximately 75,000 active TO documents/increments, comprising an estimated 8,000,000 pages of various sizes; over 17,000,000 engineering data images; over 1,000,000 Computer Aided Design/Computer Aided Manufacturing (CAD/CAM) models and files; and over 5,000,000 part indenture configurations consisting of over 19,000,000 part records are managed at Robins AFB.

Additionally, data owned and managed by DAF organizations at locations other than Robins is actively being migrated for sustainment within the PDS environment at Robins AFB. Services to support product data (TO, engineering, and other product data) systems infrastructure and data management, sustainment, and transformation activities include:

TO-000 PWS REVISION: 00 3

• Technical services to manage, maintain, and administer all computing hardware and software utilized to support the management, creation, sustainment, storage, and distribution of technical and engineering data.

• Technical support to assist the Government in development and execution of digital data support, sustainment, and transformation strategies and processes.

• Technical support necessary to facilitate evaluation and implementation of hardware and software necessary to support transition of technical data systems functionality and data to recently adopted DAF data standards, to newly implemented local system/data environments, and to DAF enterprise-level systems currently in various conceptual, planning, development and/or implementation stages.

• Technical support to establish, enhance and execute processes necessary to discover, establish, and maintain relationships/links between various types of product data (i.e., parts, drawings, TOs).

2. SERVICES SUMMARY:

Performance Objectives PWS Paragraph Performance Threshold

Maintain tech data system availability to all users 1.4.3.3

Maintain system uptime rate of 98.5% or higher monthly. (Based on a 30-day month, 100% system uptime would equate to 720 hours.)

Maintain software licensing compliance 1.4.3.4 Remove or obtain waiver for illegal software products within 15 days of identification.

Development/sustainment of system, system security, and process documentation

1.4.6 Correct identified deficiencies within 15

working days.

Maintain viable system/data backup 1.4.3.5

Ensure execution and validity of tape backup routines at 100%. Full backups shall be accomplished weekly with daily incremental backups accomplished.

Maintain contingency capabilities 1.4.3.5 Monthly certify 100% synchronization and availability of critical data transferred to the COOP.

Submit POAM for open/known vulnerabilities 1.4.3.3

Submit POAM for known vulnerbilities in accordance with TO 00-33A-1109. The current requirements are as follows.

Critical/High - 7 calendar days from date of report Medium - 21 calendar days from date of report Low - 60 calendar days from date of report

Execute PDF quality assurance and data load processes 1.4.4.3 Conduct daily quality assurance reviews on 5% of PDF files delivered and

TO-000 PWS REVISION: 00 4

Performance Objectives PWS Paragraph Performance Threshold document results in conjunction with loading of files.

Complete delivery of PDF quality assurance data 1.4.4.3.1

Documents submitted as routine priority loaded within seven (7) working days.

Documents submitted as urgent or emergency priority loaded within 3 working days.

Ensure accuracy of processed IPB part data 1.4.4.4.1

Ensure required data accuracy rate of 98% based on MPL achieved from source IPB content.

3. GOVERNMENT FURNISHED PROPERTY (GFP) AND SERVICES: Contractor will track, secure and account for all GFP/GFM IAW FAR 45 and DFARs 245: The property shall be listed as an attachment. The fillable form is located at http: //dodprocurementtoolbox.com/site/detail/id/26.

3.1. Government Inventory

3.1.1. Government Inventory Reports: The contractor shall perform an inventory of all Government property to include material and equipment not later than thirty (30) calendar days after contract start.

After the initial inventory, the contractor shall inventory annually thereafter (if applicable). Physical Inventory reports shall be submitted to the Government Property Administrator (AFSC/PZIE and/or the PMO). The report shall detail the results of the inventory, any items not accounted for and items that are lost, damaged or destroyed beyond use. (CDRL A001, Technical Report-Study/Services, DI-MISC- 80508B)

3.1.2. Government Furnished Property (Material/Equipment): The contractor shall maintain records evidencing receipt, accountability, preventative maintenance and disposal as defined within the Government property clauses. All furnished Government property shall be included in the attached spreadsheet.

3.1.3. Contractor Responsibility: The contractor shall make recommendations for purchases, as necessary, whenever existing hardware and/or software serviceability must be maintained, expanded or replaced to meet the requirements. (CDRL A001, Technical Report-Study/Services, DI-MISC-80508B) The contractor will be responsible for gathering requirements (maintenance, support level, versioning, etc.), obtaining quotes and executing purchases, and for physical acceptance of procured items.

The contractor shall also recommend for lease or purchase any equipment, furniture, supplies, office space, and any/all other items or services deemed necessary to fulfill the requirements outlined in this PWS. Recommended items are to be acquired through means deemed most advantageous to, and approved by the Government. All software developed under this contract shall be provided with unlimited rights. All equipment acquired, or software acquired, developed or licensed to facilitate processes or meet production requirements shall transfer to the Government at contract completion.

The Government shall have unlimited rights to all noncommercial software developed under this contract. Noncommercial source code for all systems, scripts, software tools, etc., developed under this contract must be thoroughly documented and shall be delivered unencumbered by restrictive markings http://dodprocurementtoolbox.com/site/detail/id/26

TO-000 PWS REVISION: 00 5

to the Government at contract completion or within 30 days after receipt of a request from the Government Program Manager. (CDRL A003, Software Transition Plan, DI-IPSC-81429A /A004, Computer Program End Item Documentation, DI-IPSC-80590B)

Commercial software licenses shall also transfer to the Government at contract completion, or within 30 days after receipt of a request from the Government Program Manager. (CDRL A003, Software Transition Plan, DI-IPSC-81429A)

The Government Program Manager shall approve all development efforts prior to start of development.

All custom-developed noncommercial software shall be properly documented using industry or DAF standard techniques. (CDRL A004, Computer Program End Item Documentation, DI-IPSC-80590B)

3.2. Government Property to be Provided: The Government will provide the contractor access to facilities and the PDS hardware and software necessary to support the tasks. With the exception of COTS software and standard office/supply items, all required technical data support materials currently utilized shall be provided by the Government. Therefore, the contractor shall utilize Government property to fulfill the requirements of this contract whenever possible.

3.3. Base Support: The Government will furnish property incidental to the place of performance including office space and equipment, i.e., computer equipment, software, output device(s), phone/phone line, facsimile equipment, reproduction equipment and office supplies.

3.4. Reporting of Government Property: The Contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with FAR 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause. The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by DFARS 252.245-7005. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/.

3.5. Loss of Government Property

3.5.1. Definition of Loss of Government Property: “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the contractor and the Government Property Administrator.

3.5.2. Reporting Loss of Government Property: The Contractor shall report loss of Government property in the GFP Module located in PIEE, https://piee.eb.mil/piee-landing/.

3.6. Return or Retention of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the https://piee.eb.mil/ https://dodprocurementtoolbox.com/ https://piee.eb.mil/piee-landing/

TO-000 PWS REVISION: 00 6

Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO.

All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

4. TECHNICAL REQUIREMENTS

4.1. Period and Place of Performance

4.1.1. Contract/Order Period of Performance: The period of performance for the contract/order will extend TBD.

Hours of Operation: Contractor personnel shall perform work during normal business hours Monday - Friday, 0700 - 1700 local time, excluding Government-observed holidays, which currently include:

New Year’s Day Labor Day Martin Luther King Day Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence Day Christmas Day Juneteenth Day

In addition to the days designated as holidays, the Government may observe the following days as Government closure days:

• Any other day designated by Federal Statute

• Any other day designated by Executive Order

• Any other day designated by Presidential Proclamation

• Any other day designated as closure day (e.g. Energy Days) with regard to Robins AFB facilities On Government observed holidays and days designated by Federal Statute, Executive Order, Presidential Proclamation, or as closure days, contractor personnel will typically not be permitted to work within the Robins AFB facilities.

In the event that Robins AFB facilities are closed due to efforts to conserve energy or due to implementation of actions deemed necessary by the Government, the contractor may not be permitted to perform within normal Robins AFB duty locations. However, in the event that an urgent situation arises that requires contractor personnel to rapidly respond and perform during periods of facility closures, access to facilities will be provided by the Government to allow appropriate contract staff members to respond and take necessary preventative, corrective, and/or recovery actions. Situations typically requiring rapid response during facility closure are those associated with critical system failures, with environmental issues carrying the potential to damage essential systems or equipment or to render equipment warranties and/or maintenance invalid, and/or those that that could result in data loss. While Government technical program staff and CORs associated with the program will be responsible for providing the contractor with access to Robins AFB facilities, the Government contracting officer will be responsible for providing direction to the contractor regarding any temporary suspension of performance.

TO-000 PWS REVISION: 00 7

The contractor may be required to perform work under this contract in excess of eight (8) hours per day.

Therefore, normal business hours or alternate business hours may be altered for a specified or indefinite period by the appropriate contract program management staff.

4.1.2. Location: These services will be performed at Robins Air Force Base.

4.2. Contract Data Requirements List(s) (CDRL)

CDRL Title Authority PWS Reference Date of First Submission

A001 Technical Report- Study/Services DI-MISC-80508B

1.4.3.3, 1.4.3.4, 1.4.3.6, 1.4.4.1, 1.4.4.3.1, 1.4.4.4.1, 1.4.5.1, 1.4.6, 3.1.1, 3.1.3, 4.14

As required

A002 Status Report DI-MGMT- 80368A

1.4.3.3, 1.4.3.5, 1.4.4.4.1, 1.4.7

40 days after contract award

A003 Software Transition Plan (STrP) DI-IPSC-81429A 1.4.6, 1.4.8, 3.1.3 As required

A004 Computer Program End Item Documentation

DI-IPSC-80590B 1.4.6, 1.4.8, 3.1.3 As required

A005 Conference Agenda DI-ADMN- 81249A 4.14 As required

A006 Report, Record of Meeting/Minutes DI-ADMN-81505 4.7, 4.14 As required

A007 Program Management Plan DI-MGMT-81797 1.4.7, 4.14.3 As required

A008 Environmental Health and Safety Plan (HSP) DI-ENVR-81375 4.6.3 40 days after contract award

A009 Accident/Incident Report DI-SAFT-81563/T 4.6.2

As required (within 24 hours of incident)

4.2.1. Quality of CDRL Deliverable: There shall be no more than one rejection of any deliverable.

There shall be no more than two total rejection(s) of deliverables per month. The Government will reject a deliverable if one or more technical errors or three or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS, or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within 10 business days of notification of Government rejection.

4.2.2. Receipt of CDRL Deliverable: CDRL deliverables shall be submitted via Wide Area WorkFlow (WAWF) and submitted directly to the MFT member identified on the CDRL. There shall be no more than 1 late submission(s) of deliverables per contract year. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised

TO-000 PWS REVISION: 00 8

delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

5. GENERAL INFORMATION: PRODUCT DATA SYSTEMS SUPPORT

5.1.1.1. Technology Support: The current PDS support environment is described in Appendix B. The contractor shall operate, maintain, and facilitate expanded usage through implementation of new data sets, expansion of the user base, and incorporation of new solutions within the Robins AFB product data environments. While the current hardware infrastructure has been designed to support expanded use and increased storage requirements, the infrastructure components are subject to change to ensure continued viability of the infrastructure to support mission requirements. The contractor shall ensure the product data infrastructure and processes remain viable tools for development, management, storage, sustainment, publication, and distribution of DAF product and technical data. These activities include development of new, or enhancement, or improvement of existing system implementations, and establishment and management of processes to extract, transform, and load data to ensure requirements associated with DAF enterprise-level system implementations are satisfied. The contractor shall provide services necessary to research hardware and software solutions, to provide purchase recommendations to the Government Program Manager, and to implement hardware and software changes within the environment as required. The contractor shall also be responsible for configuration, testing, and implementation of new hardware and/or software applications as necessary, and shall routinely be required to implement changes in the environment as necessary to ensure compliance with mandatory security directives/updates, and to ensure performance parameter requirements are achieved. The contractor shall provide personnel capable of working independently and who possess demonstrated working knowledge of the hardware and software components within the PDS environments to support DAF processes. The contractor shall be responsible for ensuring all training and certifications prerequisite to gaining access to, and performing system support functions requiring elevated access privileges on systems attached to unclassified and classified DAF and stand-alone networks and the supported PDS infrastructure are obtained and maintained by contractor personnel performing duties requiring such certifications.

5.1.1.2. System Support Services: Technical support services include system architect, system administration, and database management services necessary to manage and sustain hardware infrastructure and software components utilized in the capture, storage, maintenance, electronic distribution, transformation, and editorial processes associated with product data, and to ensure system and data contingency infrastructure and operations are implemented, viable, and documented. The following is a list of major software products currently utilized for product data management and supporting processes:

• Technical Data-Product Data Management (TD-PDM) - TD-PDM is a collection of subsystems with Commercial-Off-The-Shelf (COTS) and Government-Off-The-Shelf (GOTS) components based on Product Lifecycle Management (PLM) technology. These subsystems provide users worldwide with single-source access to multiple linked data sources which also support View- On-Demand (VOD) and Print-On-Demand (POD) processes. The system provides storage, management, version control, and configuration management capabilities for electronic product data (TOs, engineering data, et al). TD-PDM is supports over 8,600 users from the .mil network.

These are primarily personnel throughout the DAF community but the user base also includes users from other Department of Defense (DoD) Services and contractor community. TD-PDM serves as the repository for digital engineering drawings and related technical data. These capabilities support DoD logistics business functions, such as maintenance, repair, procurement, TO-000 PWS REVISION: 00 9 and re-engineering by providing worldwide, on-demand access to digital engineering drawings and associated data. See Appendix B for a list of tools and applications used within TD-PDM.

• Technical Order Authoring and Publishing (TOAP) is a collection of COTS and GOTS components providing a complete TO content management, sustainment, and publishing environment. TOAP is the designated DAF organic TO authoring and publishing component which employs workflow-controlled process solutions for TO management and editorial workgroups. TOAP stores and manages document and content components of TOs within a dynamic database repository, tracking changes against baseline TO documents and allowing users to reuse information objects. TOAP enforces authoring and publishing compliance outlined within DAF policy. See Appendix B for a list of tools and applications used within TOAP.

• Secure Technical Order Repository (STOR) - STOR is a classified system and is the overarching system title assigned to the various COTS and GOTS products utilized to provide document content management, process and management workflows, and complex data publishing capabilities for classified TOs. The STOR system also functions as the DAF repository for archive and retention of electronic copies of classified DAF TO and Time Compliance Technical Order (TCTO) documents and associated increments (e.g., changes, supplements). As such, this system is utilized to support weapon system programs throughout the DAF. See Appendix B for a list of tools and applications used within STOR.

5.1.1.3. System Sustainment: The contractor shall manage and sustain the Robins AFB product data infrastructure. This includes the identification, recording, tracking, and resolution of all problems/issues, to include documentation and cause of system downtime (whether hours or unscheduled), and maintenance of a historical database to facilitate rapid identification of common system problems and trend analysis activities. The contractor shall ensure configuration control of COTS and GOTS products, and customized tools/scripts, is maintained, employing tracking and versioning techniques necessary to allow traceability of details associated with modifications/upgrades. The contractor shall document and employ disciplined testing and implementation processes to ensure modifications are implemented with minimal impact to the user community and to prevent degradation of performance and processes.

(CDRL A001, Technical Report-Study/Services, DI-MISC-80508B)

The contractor shall perform actions necessary to facilitate compliance with DoD-mandated data center consolidation and cloud computing efforts. The contractor shall perform actions necessary to foster the adoption of safe, secure cloud computing options, to include the implementation of organizational cloud computing environments, steps to achieve data center consolidation objectives, and delivery of cloud services. (CDRL A001, Technical Report-Study/Services, DI-MISC-80508B)

The contractor shall provide for the operation and maintenance of the PDS infrastructure, supporting development, conversion, storage, improvement, and use of product data to facilitate business and operations, and maintenance activities until capabilities and data reside in the AF-PLM solution or other enterprise level system(s), and the systems supporting those capabilities are no longer operational at Robins AFB. The contractor shall monitor and manage assigned systems to ensure a 98.5 percent monthly system availability rate (based on a 30-day month, 100 percent system uptime would equate to 720 hours) to all users. Scheduled downtime and downtime caused by external factors (such as power and network outages) shall be documented and tracked, but will not be used to calculate system availability for the purposes of this performance objective. The contractor shall provide support to users from 0700 to 1700 local time. (CDRL A002, Status Report, DI-MGMT-80368A)

TO-000 PWS REVISION: 00 10

Types of services to be performed include:

• Configuring/managing servers, workstations, printers, scanners, and other peripheral devices.

• Configuring, documenting, testing, and implementing new or updated software applications utilized to support technical data processes.

• Installing and configuring operating system and application software packages and updates, and managing system configurations.

• Defining hardware, software, and cloud computing requirements, researching potential solutions, and providing recommendations for purchases and/or upgrades to the Government Program Manager.

• Tracking requirements associated with, and providing cost estimates for, maintenance of systems hardware, software, and sustainment of system support services (such as cloud computing).

• Coordinating and/or executing acquisition of required maintenance agreements in a manner preventing lapse/gaps in maintenance coverage required for systems/processes.

• Tracking assigned hardware and software inventory, ensuring utilization of software licenses does not exceed the availability of valid software licenses.

• Reviewing all Air Force Network Operations (AFNETOPs) task orders (e.g., Time Compliance Network Orders (TCNOs), Information Assurance Vulnerability management (IAVMs), Maintenance Task Orders (MTOs), etc.), determining applicability to the Robins AFB PDS, and implementing those found to be applicable.

• Ensuring Government-mandated security measures are installed and operational on all systems to include contingency environments (e.g., virus protection, firewall, authorization policies, account management, etc.).

• Conducting compatibility testing to ensure continued operation of required product data applications on DAF standard desktop configuration releases.

• Performing software application testing and completing required documentation for submission of required PDS applications to the DAF Evaluated Products List (EPL) program office for subsequent evaluation/approval.

• Coordinating with Government personnel when problems occur.

• Documenting user requirements for reports and queries.

• Reviewing user issues/requests, determining system/software impact, and ensuring timely resolution of user problems.

• Gathering and documenting requirements, supporting processes to obtain approval for, and developing and implementing solutions to automate PDS processes.

• Developing and sustaining documentation associated with PDS implementations, programs, scripts, and other automation tools.

• Providing user training.

• Performing system integration support.

TO-000 PWS REVISION: 00 11

• Establishing and managing user privileges and profiles.

• Tracking and auditing user accounts and passwords.

• Managing system security.

• Performing system backups and restores.

• Establishing and managing system directories.

• Monitoring and tuning the operating system.

• Web design and delivery of electronic data.

• Performing system troubleshooting and point of failure isolation, and determining solutions for system problems.

• Minimizing system downtime, notifying and obtaining approval from the appropriate Government representative in advance of scheduled downtime, and notifying the appropriate Government representative immediately upon discovery of other restrictions to processing or system availability.

• Developing, monitoring, and tuning databases utilized to support storage, product data transformation, configuration management, sustainment, and distribution.

• Developing processes supporting product data transformation, management, sustainment, and distribution.

• Developing and sustaining of tracking applications and other electronic inventory and auditing systems.

• Supporting the PDS applications, contingency environment services, and repositories.

• Assisting the Government in data input/integrity, quality assurance, and data migration processes.

• Participating in testing and implementation of new software releases.

• Identifying system problems to appropriate system points of contact and participating in actions necessary for problem resolution.

• Providing support to system users, resolving user trouble calls, and satisfying requests for assistance or information.

• Reviewing/updating/documenting actions associated with DAF enterprise-level systems, legacy system deconstruction, and data center consolidation/migration.

• Generating system and/or data reports.

• Management and operation of multi-tiered technical help desk environment to support systems and applications within the PDS environment.

• Providing day-to-day user and help desk support for receipt, analysis, corrective action, and tracking of trouble and/or assistance calls received from customers on systems supported.

TO-000 PWS REVISION: 00 12

• Developing and executing plans and actions necessary to facilitate DAF enterprise-level system (e.g., ETIMS, TOAP, and solutions resulting from the DAF Logistics Capability Initiatives) implementation/data migration.

• Providing support services necessary for sustainment of hardware and software utilized in product data capture, conversion, and clean-up, and scanning operations.

• Providing support services for hardware and software utilized in product data quality assurance operations.

• Providing technical system and database support services necessary for successful system operation.

• Providing the skills necessary to establish and maintain web-based access to, and for execution of queries and retrieval of product data from within supported systems and integrated third party commercial repositories.

• Supporting system implementations in both unclassified and classified environments.

5.1.1.4. Software Licensing/Testing: The contractor shall maintain and track all Government-owned software license documentation and media for non-standard software utilized within the PDS environments, shall ensure that all software installed is utilized in accordance with appropriate license agreements, and that software managed is processed for approval and placement on the DAF EPL or within the appropriate certification/authorization and accreditation package. The contractor shall maintain and utilize a software test and evaluation enclave compliant with DAF requirements for performance of software testing. The contractor shall conduct client/server testing in accordance with the most current HQ CCC/Software and Application Certification Assessments (SACA) (or other governing authority) software certification processes and governing Air Force Instructions (e.g., AFI 17- 101). The contractor shall utilize automated tools to perform software usage audits and shall provide quarterly reports to the Government outlining software utilization metrics, and status of EPL approval for COTS and GOTS software not reflected, or approaching expiration on the DAF EPL. (CDRL A001, Technical Report-Study/Services, DI-MISC-80508B)

The contractor shall be responsible for identifying, resolving, and reporting instances of usage of illegal software on assigned systems. Instances of illegal software installation shall be resolved or a waiver submitted for Government approval within 15 days of identification. The contractor shall promptly identify requirements for additional software and/or licenses to the Government Program Manager as required for new capabilities, to resolve licensing issues, and/or to ensure continued support of products under projected configurations of DAF standard desktop and server configurations. (CDRL A001, Technical Report-Study/Services, DI-MISC-80508B)

5.1.1.5. ‘Warm’ Site and System Backup Capabilities: The contractor shall be responsible for backup and restoration, as required, of both system and data files for all systems within the PDS environment. The contractor shall develop and execute all backup-related processes necessary to ensure restoration of systems and data can be accomplished as required. Backup processes shall include the execution of both incremental and full back up routines, with incremental routines executed daily and full back up routines executed weekly, at a minimum. Backup routines shall produce multiple copies of backup media, to allow one copy of backup media to be stored on-site within provided fire-proof containers in the Building 301 classified vault and one copy to be stored within a General Services Administration (GSA) approved container in a Government Program Manager designated building on

TO-000 PWS REVISION: 00 13

Robins AFB. The Government Program Manager/Contracting Officer Representative (COR) will certify on a monthly basis 100 percent synchronization and availability of data transferred to the continuity of operations (COOP).

The contractor shall execute processes necessary for storage and retrieval of both unclassified and classified (up to and including SECRET) PDS backup media according to the Government-approved rotation plan. The contractor must provide personnel appropriately authorized by the Government security manager to courier classified data in order to transport all classified backup media to/from the storage locations.

The hardware and software comprising the current COOP infrastructure is depicted in Appendix B. The contractor shall perform efforts to manage and sustain infrastructure and processes associated with support of the hardware and software required for backup of critical product data at the contingency location. These efforts shall include all actions necessary to ensure continued viability and support of hardware, software, and network connectivity; and those actions necessary for development, sustainment, and execution of plans and processes to perform data replication and periodic data synchronization processes. The contractor shall ensure critical data from the production systems at Robins AFB are replicated within the ‘warm’ site backup systems location daily such that all data for critical systems is available at the ‘warm’ site location. The contractor shall certify successful replication of data (within ‘warm’ site systems and/or on media located at the ‘warm’ site location) on a monthly basis. (CDRL A002, Status Report, DI-MGMT-80368A)

Routine administration of the system at the ‘warm’ site should typically be accomplished by contract personnel located at Robins AFB utilizing remote administration methods with synchronization of data routinely accomplished via an automated update process. Contractor personnel will be required to perform system support activities in the event of hardware failure or if network connectivity is unavailable, and shall be responsible for backup of the ‘warm’ site equipment. In the event a catastrophe occurs, which results in destruction of the primary systems at Robins, contingency plans to utilize the system at the ‘warm’ site must be in place to allow the ‘warm’ site systems to be utilized for access to critical data. The contractor shall identify to the Government Program Manager the key personnel required to deploy limited system and user support activities for critical technical data systems at the ‘warm’ site location. Key personnel will be considered mission essential (reference paragraph 4.10) and shall be required to travel to, and perform system and user support efforts at the ‘warm’ site location, if able, after catastrophic events.

5.1.1.6. System User Training: The contractor shall provide user training for Government and contractor employees as required by the Government Program Manager. The training shall cover general system functionality and operation, in-depth functional training based on specific user roles/responsibilities, and data maintenance/improvement operations training for those individuals responsible for data configuration, cleansing, and accuracy. ‘Train the Trainer’ type training will be utilized to the extent possible to support a select group of Government and/or contract employees who may provide system support and/or initial and recurring training to system users. (CDRL A001, Technical Report-Study/Services, DI-MISC-80508B)

5.1.1.7. Production Publishing Support: The contractor shall support the production publishing tools and support processes implemented within the TOAP environment, and shall facilitate automation of additional business and sustainment processes within those tools. This includes customization and configuration of systems to support the unique functions of various programs, and to insert and

TO-000 PWS REVISION: 00 14

distribute technology improvements. Prior to development or insertion of new or improved processes or capabilities, the contractor shall gain approval from the Government Program Manager and shall ensure developed capabilities are fully tested and documented (to include installation and operation procedures), and that impacts to the system’s Authority to Operate (ATO) are assessed and addressed via the appropriate processes.

The contractor shall also provide support for the publication toolsets and content management system by resolving issues identified by customers via help desk ticket submission, by executing content management system schema and workflow planning and design, and by scheduling and providing toolset training for customers, to include training on utilization of Government-owned and maintained FrameMaker templates and on proper methods of tagging technical data in Standard Generalized Markup Language (SGML) in order to reduce issues upon data delivery. The contractor shall support product data electronic repository, and publishing systems comprised of relatively complex COTS content, configuration management, and publishing software applications implemented to support military-unique processes and publishing requirements. Contractor shall be knowledgeable of documents governing the configuration control, storage, distribution, creation, and sustainment of military product/technical data and the software tools and processes utilized to compose technical publications from structured/tagged source data. The contractor shall possess the skills necessary to develop and sustain the tools necessary to transform structured/tagged source data and associated graphics files into military- and international- specification compliant output formats utilizing XPP, Live Content, or other COTS publishing environments. The contractor shall evaluate changes to directives governing product data content structure in order to assess impacts to the production publishing toolsets and to the data sustained within the content management and associated data within other technical data management systems.

5.1.1.8. Content Management System Implementation/Support: The contractor shall assist in efforts to expand the implementation of COTS and GOTS technology designed to provide product data content management, sustainment process management, and configuration control capabilities. The contractor shall populate and aid in the sustainment of management data, shall develop and sustain required workflows, provide user and system/database administration training (as required), and shall add and manage system user accounts. The contractor shall be responsible for all system management, sustainment, and configuration management aspects of the content management subsystems. The contractor shall assist the Government in efforts to analyze various content management and associated publishing system interfaces and capabilities, and shall perform efforts necessary to assist the Government in consolidation of those systems, capabilities, and data.

The contractor shall work with the Government technical program staff to determine specific content management system implementation/expansion activities, data migration and workflow requirements, and shall be responsible for gathering and documenting the details and schedules associated with those requirements. Efforts to populate the system with the necessary management data shall include migration of data from legacy sources. Electronic transfer/mapping and automated migration of data shall be utilized to the fullest extent possible. However, some manual entry of data into the system/subsystems may be required.

The contractor will be provided access to obtain the following types of data from Government data sources to aid in population of the content management system:

TO-000 PWS REVISION: 00 15

• A listing of type and quantity of technical data managed, to include other pertinent information about the data such as change or revision level, change or revision date, and managing organization.

• A listing of technical content management and sustainment personnel (if applicable) associated with specific types of technical data.

• Access to Government source data files.

The contractor shall develop and implement a method to ensure data migrated into the system accurately depicts the most current available configuration of the source data utilized to populate the system. This may include comparison of data within multiple data sources. The contractor shall work with Government technical and functional subject matter experts to determine the best sources of data for use within the system.

5.1.1.9. S1000D Specification Data Capabilities: The DAF has mandated that programs acquire Type 2 Interactive Electronic Technical Manuals (IETMs) authored to the international technical data specification S1000D utilizing DAF business rules. Several weapon system programs are currently pursuing transformation of data from legacy formats (SGML, Portable Document Format (PDF), et al) to the S1000D specification structure. The contractor shall perform actions necessary to ensure existing COTS solutions for management and sustainment of S1000D data remain viable, and shall implement and maintain capabilities necessary to facilitate development, receipt, validation, storage, management, sustainment, rendering, and distribution of technical data content authored to the S1000D specification.

The contractor shall review the DAF S1000D business rules and identify deficiencies, limitations, and/or impediments to mission objectives inherent within the business rule document set. The contractor shall work with Government technical program staff and other contractors involved in efforts to mature the DAF business rules and to develop project-level business rules, and shall develop documentation necessary for the Government Program Manager to initiate requests for business rule modifications as required to achieve program objectives.

The contractor shall perform efforts to integrate/implement and/or sustain required S1000D data capabilities (utilizing COTS tools) within the existing Robins AFB content management and publishing environment. The contractor shall work with the Government technical program staff and other customers to develop and document processes and workflows to be utilized by authors, editors, and program/publication managers for the creation, management, sustainment, and delivery of technical information structured in accordance with the S1000D specification. All capabilities and processes developed/implemented shall include measures designed to ensure data introduced and sustained within the S1000D solution set is in compliance with the S1000D specification and the business rules adopted by the DAF and/or specific DAF program.

Review of the DAF business rules and implementation of S1000D support capabilities should be conducted such that, to the greatest extent possible, rendering of multiple output formats can be achieved from a single set of source data. For example, the contractor should evaluate the potential of utilizing existing content management and publishing tools to facilitate automated transformation of existing structured TO content data (SGML) into data type supported by the S1000D specification (XML) and mapping transformed content into S1000D data modules to allow rendering of both page-based and Type 2 output from the same source data.

TO-000 PWS REVISION: 00 16

The contractor shall assist the Government in assessing COTS and GOTS S1000D viewing solutions.

The contractor shall provide services necessary to research available products, determine level of product cybersecurity compliance (as is necessary for operation within DAF environments), assess ability of product to integrate with external systems, and assess functionality of product solution against documented DAF functionality requirements. The contractor shall produce a report detailing the methods utilized for assessment and depicting results of each product assessed.

5.1.1.10. Subject Matter Expert Support: The contractor shall provide personnel who possess the functional and technical expertise necessary to support execution of the Robins AFB PDS Program.

Subject matter expertise shall be provided by the contractor as necessary to perform management activities associated with sustainment of the technical environments, and with the data migration and improvement processes outlined within this PWS. The scope of services to be provided by subject matter expert personnel includes, but is not limited to:

• Gathering and documenting user and technical requirements and translating those requirements into system specifications, data management plans, configuration management plans, test plans/scenarios, life cycle management, and other related documentation.

• Participation in functional and technical meetings, conferences, and reviews related to system and data process requirements.

• Gathering information from users, identifying work problems, and designing system or processes to resolve problems or satisfy data requirements.

• Providing information assurance expertise as it pertains to supported systems, to include support of contingency planning, system security testing, and annual contingency exercises.

• Providing input into functional, process, and data modeling activities in support of planning and analysis efforts.

• Examining and analyzing current and contemplated operations as necessary to develop and implement system, process, and/or data improvements.

• Utilizing data design, proposed system revisions, and test results to ensure functional requirements are met.

• Researching, analyzing, and providing system, functional, security, and data information required to assist the Government technical program staff in satisfying requests for information.

• Gathering and input of data and development of documentation necessary to ensure satisfaction of requirements driven by Configuration Control Board (CCB), portfolio management (via Information Technology Investment Portfolio (ITIPS), certification/authorization and accreditation (via Enterprise Mission Assurance Support Services (eMASS) and/or other designated systems), and National Defense Authorization Act requirements and mandates.

• Provide expertise related to Federal Information Security Management Act (FISMA) compliance requirements.

• Provide expertise necessary for analysis and development of Plan of Action and Milestone (POA&M) documents as required.

TO-000 PWS REVISION: 00 17

• Provide expertise necessary for analysis of military and commercial specifications governing product data, and for assessment of impacts of specification changes to supported systems and data.

• The primary service associated with A&A support is the creation and maintenance of Risk Management Framework (RMF) package to achieve an Authority-To-Operate (ATO) for STOR, TD-PDM, and TOAP systems.