DRAFT_HSFTIC_Work_Load_Indicators.xlsx
XLSX spreadsheet 238 KB Posted
- Attached to
- Human Space Flight Technical Integration Contract (HSFTIC) Federal contract opportunity
- Solicitation number
- 80JSC019R0023
About this file
This document provides details on a forthcoming solicitation for the Human Space Flight Technical Integration Contract (HSFTIC). Key information includes that NASA/JSC plans to issue a Request for Proposal (RFP) on or about November 1, 2019 for the HSFTIC, with proposals due on or about December 11, 2019. The NAICS code is 541715 for research and development in the physical, engineering, and life sciences with a size standard of 1,250 employees. This procurement is a total small business set-aside. The RFP and any associated documents will be available on the Internet at the provided websites. Prospective offerors should monitor the sites and are responsible for downloading solicitation materials. All contractual technical questions must be submitted in writing; telephone questions will not be accepted.
DRAFT HSFTIC Work Load Indicators
View the file
Other files for this federal contract opportunity
Show all 50
Human Space Flight Technical Integration Contract (HSFTIC) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
SOW 1.0 - PM & ADMIN
| Work Load Indicators | |||||
| SOW | SOW Title/Language | Performance Requirements | Products/Deliverables | Approximate Magnitudes | Typical Schedule |
| 1.0 | PROGRAM MANAGEMENT AND ADMINISTRATION | ||||
| In overall performance of contract management and administration of this contract and in carrying out of the SOW, the contractor shall conduct program management, including risk management, in order to develop and deliver the required products and services as defined for HSFTIC. The contractor shall be required to implement the following tasks at the contract level: | |||||
| 1.01 | Technical Direction | ||||
| Performance of the work under this contract is subject to the written technical direction of the NASA Contracting Officer’s Representative (COR), who will be specifically appointed by the NASA Contracting Officer (CO) in writing. “Technical direction” means a directive to the contractor that approves approaches, solutions, designs, or refinements; fills in details or otherwise completes the general description of work or documentation items; shifts emphasis among work areas or tasks; or furnishes similar instruction to the contractor. Technical direction includes requiring studies and pursuit of certain lines of inquiry regarding matters within the general tasks and requirements in the contract SOW. | |||||
| The COR does not have the authority to, and shall not, issue any instructions purporting to be technical direction that: |
(1) Constitutes an assignment of additional work outside the Statement of Work;
(2) Constitutes a change as defined in the “Changes” clause (contract Section I) or Underlimit Changes (Clause H.13);
(3) Constitutes a basis for any increase or decrease in the total estimated contract cost, the fixed fee (if any), or the time required for contract performance;
(4) Changes any of the expressed terms, conditions, or specifications of the contract;
(5) Interferes with the contractor’s rights to perform the terms and conditions of the contract.
| All technical direction shall be issued in writing by the COR. The contractor shall proceed promptly with the performance of the technical direction duly issued by the COR in the manner prescribed above and within the COR’s authority. If, in the contractor’s opinion, any instruction or direction by the COR falls within any of the categories defined above, the contractor shall not proceed but shall notify the CO in writing within 5 days after receiving it and shall request the CO to either issue an appropriate contract modification within a reasonable time or advise the contractor in writing within 30 days that the instruction or direction is rescinded in its entirety or within the requirements of the contract and does not constitute a change under the “Changes” clause of the contract, and that the contractor should proceed promptly with its performance. |
| A failure of the contractor and CO to agree that the instruction or direction is both within the requirements of the contract and does not constitute a change under the “Changes” clause, or a failure to agree upon the contract action to be taken with respect to the instruction or direction, shall be subject to the Disputes clause of this contract. |
| Any action(s) taken by the contractor in response to any direction given by any person other than the CO or the COR shall be at the contractor’s risk. |
| 1.0.2 | The contractor shall develop, maintain and implement a Management Plan in accordance with Data Requirements Description (DRD) HSFTIC-PM-01, Program Management Plan. | ||||
| 1.0.3 | The contractor shall provide a contract Phase-In Plan in accordance with DRD HSFTIC-PM-03, Phase-In Plan. | ||||
| 1.0.4 | The contractor shall provide a Contract Close-Out Plan in accordance with DRD HSFTIC-PR-01, Contract Close-Out Plan. | ||||
| 1.0.5 | The contractor shall conduct Integrated Management Reviews (IMR) for NASA, and provide integrated management review of the contractor’s overall technical, schedule and cost performance in accordance with DRD HSFTIC-PM-02, Integrated Management Review. The reviews shall include the contractor’s vendors and subcontractors. | ||||
| 1.0.6 | The contractor shall provide performance metrics in accordance with DRD HSFTIC-PM-04, Performance Assessment Plan and Performance Assessment Reports. | ||||
| 1.0.7 | The contractor shall provide a SOW Evidence of Completion Matrix in accordance with DRD HSFTIC-PM-11, SOW Evidence of Completion Matrix. | ||||
| 1.0.8 | The contractor shall deliver DRD content that is compatible with the NASA Management Information System (MIS). | ||||
| 1.1 | ISS PROGRAM MANAGEMENT AND ADMINISTRATION | ||||
| The contractor shall provide and maintain program management systems, as outlined below, for the planning, organization, control and reporting of all activities required by this contract, to include all outcomes and deliverable products. | |||||
| 1.1.1 | The contractor shall, in accordance with SAE AS9100, Quality Systems – Aerospace – Model for Quality Assurance in Design, Development, Production, Installation and Servicing, provide work instructions and maintain the ISS Program Master List of work instructions, processes, and procedures in accordance with JWI 1282.1 Organizational Master List, and provide administrative functions for work instructions in accordance with SSP 41170, Configuration Management Requirements. | Maintain and update OA Master List of documents and WIs, maintain master list links, updates. Develop status charts for OA Master List contents for inclusion in QMS semi-annual review | Product - chart submittal to OX for QMS semi-annual review | 4 charts/2 times per year | summer and end of year |
| 1.2 | ISS CERTIFICATION OF FLIGHT READINESS (CoFR) | ||||
| The contractor shall provide an auditable approach and statement of flight readiness for the work performed under this contract in accordance with SSP 50108, ISS Program Certification of Flight Readiness Process Document and with DRD HSFTIC-PM-06, Certification of Flight Readiness (CoFR) Implementation Plan. | |||||
| 1.2.1 | ISS Program CoFR Process: | Establish dates, scope, and details required for each CoFR review. Communicate to the ISS community on behalf of the ISS Program. Develop and distribute ISS Program correspondence for CoFR activities |
Maintain the CoFR Schedule and calendars
Prepare, coordinate, and facilitate ISS org internal CoFR meetings
Prepare, coordinate, and manage ISS Program CoFR meetings
Track and maintain status of open change paper, deviations/waivers, CoFR actions and CoFR Exceptions
Administer CoFR process in accordance with each Org's CoFR Implementation Plan to provide consistent data collection, presentation, and archival of internal CoFR data which includes collecting required data to complete CoFR records
Integrate CoFR documentation at the CAM level, for all ISS Program Offices, for presentation at ISS Program CoFR Reviews.
Coordinate data from each organization into ISS Program CoFR presentation package Product/Service:
Prepare, coordinate, and facilitate the technical content and scope for the reviews (SORR/FRR) supporting every flight event including launch, dock/berth, and return/disposal. Flights will be combined for SORR/FRR when possible. Develop and distribute CoFR Announcement Memos for each SORR and FRR. Maintain distribution lists for accuracy per flight
Develop and publish a CoFR Review Meeting Matrix of high level program milestones that supports the ISS Flight Plan. Develop and publish CoFR milestone schedules for each ISS org corresponding with the ISS Program CoFR Review Meeting Matrix. Schedules will be analyzed weekly for necessary changes and updated only when changes to the Flight Plan are made or review dates are changed by the ISS Program Office
Prepare, coordinate, and facilitate internal SORR Meetings for each ISS org in support of Program SORRs. Include every flight event (i.e., launch, dock/berth, and return/disposal). Compile and integrate presentation packages for ISS Program organization internal SORRs. Compile and archive objective evidence packages including: CoFR endorsement checklist and signed readiness statements for each ISS org. Assume an internal SORR for each flight event for 8-10 organizations.
Create technical presentations of ISS Program Open Change Paper for SORRs, FRRs, Control Boards, SORR Agenda Reviews, FRR Chart Reviews, and IMMTs supporting every flight event including launch, dock/berth, and return/disposal
| Prepare, coordinate, facilitate SORR and FRR meeting services for every flight event (i.e., launch, dock/berth, and return/disposal) in accordance with the requirements listed in Appendix J-7, Meeting Services and prepare a consolidated presentation package | FY18 - 774 | |
| For the ISS CoFR process, the contractor shall: | ||
| A. Manage ISS Program CoFR reviews. | ||
| B. Maintain the ISS Program CoFR schedule and calendar. | ||
| C. Develop and distribute CoFR announcement memorandums. | ||
| D. Develop and distribute ISS Readiness memoranda for the International Partners and Commercial Vehicles. | ||
| E. Maintain CoFR distribution lists. | ||
| F. Perform CoFR meeting logistics. | ||
| 1.2.2 | The contractor shall track and maintain status of open paper, waivers, CoFR actions and CoFR Exceptions. | |
| 1.2.3 | The contractor shall implement the CoFR requirements identified in each NASA Control Account Manager (CAM) CoFR implementation plan and in accordance with SSP 50108, ISS Program Certification of Flight Readiness Process Document, to provide for consistent data collection, presentation, and archival of CoFR data. | |
| 1.2.4 | The contractor shall perform compliance verification audits of each NASA ISS Program Office and ISS Program contractor CoFR Implementation Plans. | |
| 1.2.5 | The contractor shall integrate CoFR documentation at the ISS Program Office CAM level, for all ISS Program Offices, for presentation at the ISS Program CoFR Reviews. | |
| 1.2.6 | The contractor shall collect CoFR documentation from every ISS Program Office into a presentation for the ISS Program CoFR Reviews. |
| 1.3 | ISS RISK MANAGEMENT | |
| The Risk Management function consists of qualitative and quantitative processes and methodologies. | ||
| 1.3.1 | The contractor shall develop, maintain and implement the ISS Program risk management processes and procedures and integrate the identification, quantification, and mitigation of risks across the ISS Program, including the following: | |
| A. Define, maintain and implement the risk management process. | ||
| B. Maintain the ISS Risk Database in accordance with SSP 50175, ISS Risk Management Plan, and NASA Procedural Requirement (NPR) 8000.4, Agency Risk Management Procedural Requirements, integrate all data, and maintain data integrity of the ISS Risk Database and associated linkage with the Management Information System (MIS). | ||
| C. Provide training of risk management principles across the ISS Program community. | ||
| D. Develop and integrate inputs, resolve discrepancies, and provide risk metrics and Integrated Risk Management Application (IRMA) data packages for the Program Risk Advisory Board (PRAB). | quarterly | |
| E. Track liens and threats as related to the ISS Risk Database, and provide Program and Project status, including reports from the ISS Risk Database, provide status of functional area risks (CAMs, i.e. Vehicle Office Manager), track changes, and make updates to risks to reflect the current status. | ||
| Services: |
OE General: Track liens and threats and provide Program and Project status, including reports from the ISS Risk Database, provide status of functional area risks, track changes, and make updates to risks to reflect the current status.
OE: weekly/monthly
| In addition, the contractor shall coordinate liens and threats and facilitate categorization for ISS Vehicle Office risks with the Vechicle Office technical organizations. | OB Specific: Coordinate liens and threats with technical organizations. Facilitate categorization. | Develop and provide liens and threats metrics and data packages for OB for the PRAB | |
| monthly budget planning | every other week |
monthly
| F. Identify safety, mission success, cost, and schedule risks and documentation in the ISS Risk Database, identify new risk initiatives, and provide risk guidance, identify issues, and address concerns. |
| G. Develop and provide ISS risk management techniques in response to NASA Agency risk activities and initiatives including any external/internal audits. |
| H. Integrate and perform qualitative risk assessments of flights, stages, specific operations, specific configurations, and change requests. |
| I. Integrate Program-wide risk inputs for the CoFR/Stage Operations Readiness Review (SORR) and resolve discrepancies, provide risk data by flight and stage, and confirm risk acceptance rationale is documented for open CoFR/SORR risks. |
| J. Facilitate and execute the risk management process for CAM, MSFC HP20/Payload and Mission Operations, and child organization risks. |
| 1.4 | ISS EXPORT CONTROL |
| 1.4.1 | The contractor shall develop, provide, and implement an Export Control Plan (ECP) in accordance with DRD HSFTIC-EC-02, Export Control Plan, and conduct self-audits in accordance with DRD HSFTIC-EC-01, Export Control Audit Results. |
| 1.4.2 | The contractor shall determine classification of all export commodities and whether NASA existing license exceptions or exemptions can be used. |
| 1.4.3 | The contractor shall administer and maintain control logs of export activities consistent with the DRD HSFTIC-EC-02, Export Control Plan and associated export compliance requirements. Export control logs shall include as a minimum, commodities classifications, license information, transaction status, compliance activities and records of process completion for license exceptions or exemptions. |
| 1.5 | ISS PROGRAM SCHEDULE DEVELOPMENT AND INTEGRATION | |
| 1.5.1 | The contractor shall provide overall Program schedule management, analysis, and assessments in accordance with DRD HSFTIC-PC-04, Program Schedules, to support the continued development and operation of the ISS. | This is the overall schedule management effort to ensure the Program scheduling function is executed and schedules are provided to identified organizations per DRD-HSFTIC-PC-04 |
Provide technical inputs to SSP 50489, Mission Integration Template (MIT) document
Services:
Provide schedule management
Provide Schedule Templates and the Combined Milestone Definitions Table to the Book Coordinator to be incorporated into the SSP 50489, Mission Integration Template (MIT) document in support of 1 Change Request (CR) during the year.
Schedule Templates include:
Soyuz Template Progress Template HTV Vehicle Template SpaceX Cargo Vehicle Template Orbital Vehicle Template Increment Template SpaceX Crew Vehicle Template Boeing CST-100 Crew Vehicle Template Sierra Nevada Cargo Vehicle Template (new template to be added to the MIT)
Details for Program schedules are identified in 1.4.1 Schedule Management below
1.5.2 The contractor shall integrate schedule milestone requirements with affected Program providers, and resolve issues with data providers and identify potential schedule impacts and notify affected performing organizations to ensure timely Program awareness and resolution. Included in the above. Included in the above.
| 1.5.3 | ISS Schedule Management | |
| A. The contractor shall develop, maintain, and status Program Flight Schedules and Program level activity schedule products (i.e. Quarterly Program Level Presentations for IMPR, CAM level schedules, etc.). | This is the coordination required to deliver the schedule products |
Integrate schedule milestone requirements with affected Program providers
Resolve issues with data providers
Identify potential schedule impacts
Notify affected performing organizations to ensure timely Program awareness and resolution Services:
Maintain ISS Program schedules OB Schedules:
Attached Payload Forum (APF) schedule OC Schedules:
Visiting Vehicle Level III Schedules Visiting Vehicle Look Ahead Schedules Increment Schedules Team Schedules Manifest MIOCB Look Ahead Schedules Payloads Development Schedule Post Mission Schedule OM Schedules ON Schedules:
Provide updates to the IMS for CRS, CRS-2, and CCP Vehicles (SpX, NG, SNC, Boeing) Maintain CRS/CRS-2/CCP schedules Develop CRS, CRS-2, and CCP 90-day look ahead and behind schedules Develop and maintain HTV flight specific integration schedule Develop Quarterly Program Schedule Presentations (IMPR) Develop Quarterly Program Schedule Presentations (DPMC, SSCB) Develop and present schedule conflict report/analysis to team leads Develop and provide flight specific schedule reports and Performance to Plan reports OZ Schedules
| B. The contractor shall perform schedule trade studies or create ad hoc schedules. | ||||
| C. The contractor shall develop and maintain integrated schedules and project schedules, and report upcoming deliverables and impacts associated with delays. | ||||
| D. The contractor shall develop and maintain integrated schedules and project schedules, and report upcoming scheduled deliverables and impacts associated with delays for each Visiting Vehicle. | Integrated schedule products will be developed on a weekly/monthly basis for each VV. | |||
| Schedule delay impact assessments are performed on a monthly/quarterly basis for each VV | Integrated schedules | |||
| Schedule dalays impact assessments | VVs include Cygnus, Dragon 2, Crew Dragon, DreamChaser, CST-100, and HTV | |||
| 1.5.3.1 | ISS Vehicle Office Environment Control And Life Support System (ECLSS) Project | |||
| The contractor shall develop and maintain (e.g. status and report) an integrated schedule for the ECLSS Project by providing the following tasks: | ||||
| A. Analyze the initial project schedules (developed by other performing organizations) for quality review, critical path identification, and selection of critical high-level milestones for management level tracking. | Task includes ensuring alignment of select and critical milestones/schedule from performing organizations into the ISS Exploration ECLSS Integrated schedule | Products: |
5 /year complex Project Schedule analysis;10/year simple project schedule analysis
Assume:
5 new complex projects; 10 new simple projects
| B. Develop an integrated schedule with milestone links to project schedules maintained by performing organizations. | Development of the ISS Exploration ECLSS integrated schedule based on project life cycle events, and input from project engineers and program personnel. | |
| Products: |
1/month- ISS Exploration ECLSS Integrated Schedule release
Assumed monthly release of integrated schedule C. Provide day-to-day schedule maintenance and development of monthly status and reporting. (e.g., impact of changes to critical milestones in performing organizations’ schedules). Maintain integrated Exploration ECLSS schedules to use in planning meetings. Tasks include attend meetings such as schedule or technical review to obtain data and status from performing organizations, coordination to gather data for schedule updates, posting schedules, and recording actions and tracking closures as follow-up from technical discussions. Products:
1/month: Schedule analysis summary 1/month: Action tracking Service:
1/month schedule support
Assume:
Monthly schedule input from performing organizations
1/month meeting in 1/month action tracking
| D. Develop and maintain reporting for the integrated schedule for management use. | Produce quarterly metric showing if schedule is within parameters for Exploration ECLSS active project | ||
| Integrate quarterly metrics showing if cost and technical with the schedule metric into one table per project Exploration ECLSS active project. Cost and technical inputs will be provided from other team members. | Product: |
4/year -Develop/maintain Schedule metric 4/year - Integrate cost/technical reporting
Only reporting active complex projects 5 active complex projects
E. Provide analysis for special studies (e.g., analyzing, evaluating, documenting, and providing input for reviews and management questions) on the integrated schedule. No further clarification needed Products: 4/year: Special Studies
Assist with 'what-if' scenarios per year for schedule changes and other strategic planning options.
| 1.6 | ISS MEETING SERVICES | |
| The contractor shall provide meeting services for the NASA identified control boards and panels as identified in Section J, Attachment J-7, Meeting Services requirements. | Develop agendas, perform meeting logistics, reproduce and distribute presentation material, and provide summary minutes/action items associated with Program Reviews, Control Boards, Panels, and Near Real Time Operations per contract attachment J-7 |
a. Support TIMs and integration forums to develop ISS positions on integration issues (58)
e. Meeting services to partner VVV WG (96)
Provide meeting services for the TICB, CCP VVIM,CCP VVVWG, CCIM, SNC VVIM; Note: Need to check J-7; Agendas, minutes/summary, MST/EDMS uploading current 106
Meeting agendas, action item lists, minutes FY19 - 2,549 meetings supported per year
TICB 1 per week; 3 hours CCP VVIM & VVVWG; 1 per commercial provider; 2 hours each CCIM & SCN VVIM 1 per week; 2 hours
| 1.7 | ISS NASA REVIEWS | |
| The contractor shall develop and deliver briefing materials and analyses including Program technical, cost, and schedule status, specific safety or risk issues for ISS Program presentations and meetings with internal and external review groups. Examples of these groups include but not limited to : the Aerospace Safety Advisory Panel (ASAP), Human Exploration and Operations Committee of the NASA Advisory Council (NAC), Inspector General (IG), United States (US) Government Accountability Office (GAO), and Cost Assessments Teams. | ||
| 1.8 | ISS PROGRAM REVIEWS, BOARDS, PANELS | |
| The contractor shall provide and present briefing material, data, analyses and technical input for status and decision making at Program reviews, control boards, panels, working groups, and Technical Interchange Meetings (TIMs). | Present results of technical tasks and actions at Program reviews, control boards, panels, working groups |
Conduct meetings, IP teleconferences, and Technical Interchange Meetings (TIMs) to integrate data inputs, identify discrepancies, and obtain agreement for content of presentation and org specific documentation. The contractor shall provide agendas, minutes, discussion and presentation material, action status tracking, and protocols Continuous support through the HSFTIC technical teams to Program Reviews, Boards and Panels identified in the HSFTIC contract
This task is performed by HSFTIC technical organizations and will be tracked as part of their annual work plan
| 1.9 | ISS SPECIAL STUDIES | ||
| The contractor shall perform special studies to address the following: | No further clarification needed | Product/Service = N/A |
General special studies are addressed in the specific technical element AWPs Complex or resource intensive special studies will be requested via IDIQ Task Order
| A. New or changing requirements, |
| B. ISS Vehicle performance improvements, |
| C. Requirement changes, |
| D. Process improvements, |
| E. Reducing operating costs. |
| 1.10 | ISS TECHNICAL WRITING |
| The contractor shall provide technical writers for the ISS Program Science Forum, Program Science Forum - US, ISS Payload Integration Panel and the ISS Program Safety Review Panels. | |
| Provide technical writers for safety panels, including the ISRP, Reliability and Maintainability, and associated meetings such as Special Topics. NOTE: Currently, on meeting day, the technical writer is responsible for managing Web-Ex for the meeting. The tech writer collaborates with the designated safety engineer on meeting minutes. Minutes are not required for OSB, coordination, nor resource meetings. |
Agenda is required for Program Science Forum (PSF)/PSF-US Meeting ISS Program Science Forum working groups include ISS Web Resource Working Group (WRWG), Earth Observation Working Group (EOWG) ISS Web Resource Working Group: Organized and attentive to detail individual capable of taking clear notes in a context of engaged scientific discussion ISS WRWG meeting notes will be organized, detailed and clear in context of engaged Scientific discussion.
ISS Payload Integration Panel (PIP) inputs include technical summary of panel decisions and outbrief for ISSP boards and forums (eg: RICB) Meeting minutes.
Agenda and presentations for PSF & PSF US Meeting Notes for Earth Observation Working Group Meeting Notes for ISS Science Web Resource Working Group
- PIP Technical sumamry
- PIP Outbrief presentations
Average: ISRP: Major: Phase I, II, or III review (1 week); Standard meeting: (1 day); Special Topics:(1 day); TIMs: (1 week). Reliability & Maintainability (2 hours).
- 4 PSF Agenda / year
- 12 PSF US Agendas/year
- 4 PSF Notes / year
- 12 PSF US Notes / year
- 6 EOWG Agenda / year
- 6 EOWG Notes / year
- 6 ISS Web Resource Working Group technical meeting notes /year
- 1 PIP Technical summary / week
- 1 PIP Outbirief presentation / week ISRP Major: Phase I, II, or III review (12/yr); Standard meeting: (175/yr); Special Topics:(80/yr); TIMs: (4/yr). Reliability & Maintainability (48/yr).
- PSF, PSF-US, and EOWG Agendas due 1 week prior to meeting.
- PSF, PSF-US, and EOWG Notes due 1 week after meeting
- ISS WRWG Technical meeting notes due 2 weeks after conclusion of working group
- PIP meets weekly
| 1.11 | ISS MISSION ASSURANCE AND RISK MANAGEMENT PLAN |
| The contractor shall develop, implement, and maintain a Mission Assurance and Risk Management Plan in accordance with NPR 8715.3, NASA General Safety Program Requirements, and DRD HSFTIC-SA-01, Mission Assurance and Risk Management Plan. |
| 1.12 | ISS QUALITY MANAGEMENT |
| A. The contractor shall establish, implement, and maintain a Quality Management System (QMS) that complies with the SAE AS9100, Quality Systems – Aerospace – Model for Quality Assurance in Design, Development, Production, Installation and Servicing. Third party certification and registration is not required. | |
| B. If the contractor is SAE AS9100, Quality Systems – Aerospace – Model for Quality Assurance in Design, Development, Production, Installation and Servicing, registered and subsequently changes registrars, loses registration status, or is put on notice of losing registration status, the contractor shall notify the NASA Contracting Officer within three (3) business days of receiving such notice. |
| 1.13 | ISS AUDIT AND SURVEILLANCE |
| The contractor shall provide access to data, personnel, and facilities for Government audits and surveillance of contractor plans, procedures, and processes when deemed necessary by the Government, and provide written responses to audit and surveillance findings. |
| 1.14 | ISS LESSONS LEARNED | ||
| The contractor shall: | |||
| A. Report lessons learned in accordance with NPR 7120.6, Knowledge Policy on Programs and Projects, and JSC Procedural Requirement (JPR) 2310.1, JSC Organizational Learning Program. | No further clarification needed | Product: |
Contract related lessons learned that would be reported would need to be at the level of importance for multiple projects, programs, or centers B. Collect and document flight and increment lessons learned in the government's repository.
| 1.15 | ISS DOCUMENT MANAGEMENT | |
| 1.15.1 | Book Management, Coordination, and Development | |
| The contractor shall provide document maintenance functions in accordance with SSP 41170, Configuration Management Requirements and SSP 50010, Standards for ISS Program Documentation and DRD HSFTIC-SI-01, ISS Documents Development. The contractor shall maintain specifications electronically in accordance with SSP 41171, Preparation for Program-Unique Specifications or as modified by negotiations with the Partner/Participant. The contractor shall maintain Interface Control Documents/Interface Requirement Documents (ICDs/IRDs) in accordance with SSP 30459, ISS Interface Control Plan. | Products: Document review and/or maintenance per listing in contract attachment xx |
The contractor shall provide book coordinator and book manager functions for the documents listed in Section J, Attachment J-4, Applicable and Reference Document Lists, Table J4-3. Provide book manager or coordinator functions for documents listed in contract attachment. approx 80/yr
| 1.15.2 | ISS Document Quality Assurance | |
| The contractor shall provide NASA and HSFTIC Document Quality Assurance (DQA) in accordance with SSP 50010, Standards for ISS Program Documentation, and SSP 41170, Configuration Management Requirements. | Provide review and update for documents listed in contract attachment xx and ISS Program documents not included in other contracts |
| FY19 - 140 (includes DQA rework counts) | ||||
| 1.16 | ISS ORGANIZATIONAL RECORDS | |||
| The contractor shall develop a data and records management plan in accordance with DRD-HSFTIC-PM-12 Data and Records Management Plan, in the NASA-provided Organizational Records Inventory (ORI) tool. The contractor shall ensure Human Space Flight Programs organization adherence to the established plans for data and records management and retention, in accordance with NPR 1441.1E, NASA Records Management Program Requirements, NRRS 1441.1A, NASA Records Retention Schedules, NPD 1440.6I, NASA Records Management, and JPR 1440.3D, JSC Records Management Procedural Requirements. The contractor shall conduct audits throughout the Human Spaceflight Programs to ensure compliance with Agency, Center, and Program requirements. | One plan required. | |||
| A. The contractor shall track ISS organizational records to ensure records are updated and accurate in the ORI tool and physical records are being kept according to published retention schedules and policy. | Determine that records are updated and accurate in the Organizational Records Inventory and physical records are being kept according to published retention schedules and policy. | quarterly | As required | |
| B. The contractor shall process, distribute, maintain, and track ISS Program Official Correspondence. The contractor shall distribute and track ISS Program reviews and responses to Agency and JSC Work Instructions, Requirements, and Directives. | no input needed here. | 144/year | As required | |
| C. The contractor shall determine export control requirements for incoming correspondence, including faxes, between International Partner countries and the ISS Program. | Determine export control requirements for incoming correspondence, including faxes, between International Partner countries and the ISS Program. | 48/year | As required | |
| D. The contractor shall, in coordination with ISS Program Office management, process NASA and JSC Directives and Requirements, and Document Availability Authorizations per NPR 2200.2 Scientific and Technical Information (STI) Document Availability Authorization, and JSC Action Tracking System actions. | In coordination with ISS Program Office management, process directives, Document Availability Authorizations, and JSC Action Tracking System actions. | 48/year | As required | |
| E. The contractor shall process requests for translation on behalf of ISS Program Manager Office/Human Space Flight Program-Russia, request new translations, and distribute as appropriate. | Process translation requests for OA/OK, request translation, and distribute as appropriate. | 48/year | As required | |
| F. The contractor shall prepare technical and management correspondence, forms, reports, and presentations. | Prepare technical and management correspondence, forms, reports, and presentations. | 48/year | As required | |
| G. The contractor shall distribute ISS correspondence. | Distribute ISS correspondence. | 84/year | As required | |
| H. The contractor shall upload final correspondence packages in ISS Program repository. (i.e Electronic Document Management System (EDMS)). | File final correspondence packages in EDMS. | 84/year | As required | |
| 1.17 | ISS PROGRAM RESERVED | |||
| 1.18 | ISS PROGRAM RESERVED |
| 1.19 | ORION PROGRAM MANAGEMENT AND ADMINISTRATION | ||||
| The contractor shall conduct program management, including risk management, in order to develop and deliver the required products and services as defined for this contract. | monthly | ||||
| The contractor shall provide and maintain program management systems, for the planning, organization, control and reporting of all activities required by this contract, to include all outcomes and deliverable products. | monthly | ||||
| 1.19.1 | The contractor shall provide performance metrics in accordance with DRD HSFTIC-PC-06, Professional Services. | 12 per FY | monthly | ||
| 1.20 | ORION PROGRAM RISK MANAGEMENT | ||||
| The Orion Program requires risk management support to the Program. The contractor shall assess risk content and facilitate coordination and integration at the Program level, including administration of the Program risk system. | monthly | ||||
| The contractor shall perform these requirements as part of Orion Risk Management System. In performing these requirements, the contractor shall: | monthly | ||||
| A. Track, assess risk content, coordinate updates, and facilitate integration and presentation of Program risks at the Program level and at the CAM Program office level (monthly). | 12 per FY | monthly | |||
| B. Develop, document, update, and status the Orion Top Program Risks on a monthly basis. | 12 per FY | monthly | |||
| C. Assist in integration of Orion, Exploration Systems Development (ESD), and Cross-Program Risks and report monthly. | 12 per FY | monthly | |||
| D. Provide Risks Assessments for Monthly Orion Program Planning & Control (PP&C) Program Review (MOPPR) package and MOPPR meeting. | 12 per FY | monthly | |||
| E. Assist in risk analysis of cost, schedule, and technical forecasting. | 12 per FY | monthly | |||
| 12 per FY | monthly | ||||
| F. Update the Risk Register - to inlcude stautus updates, mitigations, and impacts/ closures for each risk ( monthly) (database/internal to Orion program). | 12 per FY | monthly | |||
| G. Update a monthly risk status report, including mitigation statuses. | 12 per FY | monthly | |||
| 1.21 | ORION PROGRAM EXPORT CONTROL | ||||
| 1.21.1 | Assist data originators and Designating Officials with the assessment of Orion Program documentation to determine sensitivity and appropriate markings for export and by interfacing with the JSC Export Services Team to export controlled items. | ||||
| 1.21.2 | The contractor shall determine classification of all export commodities and whether NASA existing license exceptions or exemptions can be used. | approximately 5 per month | monthly | ||
| 1.21.3 | The contractor shall administer and track logs of export activities (via JSC Export Records Database). The contractor shall utilize JSC Export Records Database logs to track as a minimum, commodities classifications, license information, transaction status, compliance activities and records of process completion for license exceptions or exemptions. | approximately 5 per month | monthly | ||
| 1.22 | ORION PROGRAM SCHEDULING | ||||
| 1.22.1 | The contractor shall provide overall Program schedule management, analysis, and assessments in accordance with DRD HSFTIC-PC-05, Orion Program Data Product Deliverables. | 1 prime contractor schedule, 3 subcontractor schedules, 3 non prime schedules | monthly | ||
| 1.22.2 | The contractor shall maintain control and notification schedule milestone requirements, coordinate with affected Program providers, and resolve issues with data providers. The contractor shall identify potential schedule impacts and notify affected performing organizations to ensure timely Program awareness and resolution. | approximately 50 control/notification milestones | monthly | ||
| 1.23 | ORION PROGRAM SCHEDULE MANAGEMENT AND ASSESSMENT | ||||
| The Orion Program requires Scheduling and Schedule Assessment support to the Orion Program. The contractor shall provide scheduling support to the Orion Program and shall interact with Orion Control Account Manager (CAM) management and team staff. In support of scheduling and schedule assessments, the contractor shall: | 1 prime contractor schedule, 3 subcontractor schedules, 3 non prime schedules | monthly | |||
| A. Provide development and integration of Orion Integrated Master Schedule (IMS) for all scope. The Orion IMS shall contain all network logic and all scope required to complete the project. The Orion IMS shall be properly sequenced using predecessor and successor dependencies and mimize the use of constraints. | 1 prime contractor schedule, 3 subcontractor schedules, 3 non prime schedules | monthly | |||
| B. Provide updates, statuses, and maintenance inputs to the Orion IMS, analyze the performance, produce the top 3 critical paths, and make schedule adjustment recommendations to the NASA Program Manager. | 1 prime contractor schedule, 3 subcontractor schedules, 3 non prime schedules | monthly | |||
| C. Perform special runs using program scheduling tools and techniques inserting “what if” scenarios to depict impacts on critical paths. | 1 prime contractor schedule, 3 subcontractor schedules, 3 non prime schedules | monthly | |||
| D. Perform reviews of the Orion Prime Contractors’ schedules and reporting findings to NASA Program Management. | 1 prime contractor schedule, 3 subcontractor schedules, 3 non prime schedules | monthly | |||
| E. Conduct a health assessment on all assigned schedules ensuring scheduling best practices are being followed. | 1 prime contractor schedule, 3 subcontractor schedules, 3 non prime schedules | monthly | |||
| F. Develop, status, report, and document schedules and metrics for designated Orion CAMs. Provide schedule analysis and assessments, and report schedule findings as requested. | 1 prime contractor schedule, 3 subcontractor schedules, 3 non prime schedules | monthly | |||
| G. Review and analyze Orion contractor(s) schedule DRDs for compliance with contractor scheduling DRD requirements. | 1 prime contractor schedule, 3 subcontractor schedules, 3 non prime schedules | monthly | |||
| H. Interface with and provide schedule data to external parties as needed (i.e. twice monthly). | bi weekly | ||||
| 1.24 | ORION MEETING SERVICES | ||||
| 1.24.1 | The contractor shall provide meeting services for the NASA/Orion identified control boards and panels as identified in Section J, Attachment J-7, Meeting Services requirements. | see meeting support table in J-attachment for scope | see meeting support table in J-attachment for frequency | ||
| 1.24.2 | Provide meeting services for performing planning coordination, and execution of Multi-Purpose Crew Vehicle (MPCV) Program meetings, such as MPCV Program Office Control Boards, Panels, Integrated Product Team (IPT) meetings, designated working groups, major Program reviews, Technical Interchange Meetings, ad hoc management meetings, action item tracking, and Program wide communications, as identified in the current version of the MPCV Program Plan, including but not limited to meeting facilitation, scheduling, room and Information Technology (IT) logistical setup, attendance tracking, technical coordination for agenda management, action and decision tracking, maintaining and distributing meeting minutes. | see meeting support table in J-attachment for scope | see meeting support table in J-attachment for frequency | ||
| 1.24.3 | The contractor shall provide administrative and technical writing services for Board meetings as follows: | see meeting support table in J-attachment for scope | see meeting support table in J-attachment for frequency | ||
| A. Provide on-call, ad-hoc technical support. | see meeting support table in J-attachment for frequency | ||||
| B. Provide meeting and agenda pre-coordination (collect, post, and distribute meeting presentations and materials). | see meeting support table in J-attachment for frequency | ||||
| C. Provide support to meeting execution (meeting room telecon and web conference (e.g. WebEx) setup). | see meeting support table in J-attachment for frequency | ||||
| D. Generate technical level meeting minutes including capture and tracking of decisions, actions, and open work. | see meeting support table in J-attachment for frequency | ||||
| E. Create and maintain Problem Reporting and Corrective Action (PRACA) records where applicable. | see meeting support table in J-attachment for frequency | ||||
| F. Transition current set of open actions in to a single action tracking database. | see meeting support table in J-attachment for frequency | ||||
| 1.25 | ORION PROGRAM RESERVED | ||||
| 1.26 | ORION PROGRAM RESERVED | ||||
| 1.27 | GATEWAY PROGRAM MANAGEMENT AND ADMINISTRATION | ||||
| The contractor shall provide program management and administation in order to develop and deliver the required products and services. | |||||
| 1.28 | GATEWAY PROGRAM REVIEWS | ||||
| The contractor shall provide support for Gateway Lifecycle Reviews. The contractor shall provide review integration support for milestone/lifecycle reviews as follows: | Support for Lifeccyle Reviews | Planning meetings, logistics/venue arrangements, tracking and disposition of requests for actions and findings. Terms of reference, agenda, entrance and success critieria | Estimated one lifecycle review per year at the Gateway Program level | Annual | |
| A. Develop of milestone success criteria. | |||||
| B. Provide NPR 7120.5, NASA Space Flight Program and Project Management Requirements, expertise for tailoring and compliance. | |||||
| C. Develop the review Terms of Reference (ToR). | |||||
| D. Coordinate with the Gateway Standing Review Board (SRB). | |||||
| E. Develop and review of associated review documentation, products, and materials. | |||||
| F. Schedule reviews and provide logistics support for each review, including developing agendas and online references. | |||||
| G. Track actions to closure. | |||||
| 1.29 | GATEWAY PROGRAM INTEGRATION MANAGEMENT | ||||
| The contractor shall assist with the development of Gateway Programmatic products, in accordance with NPR 7120.5, NASA Space Flight Program and Project Management Handbook and NPR 7123, NASA Systems Engineering Processes and Requirements for the Gateway Program Integration Management, as well as Program-to-Program activities in support of Lunar Exploration integration of the Gateway, Orion, Human Lander Systems, and Advanced Exploration Systems. The contractor shall write and review Program Management and Program Integration Management plans. | Develop,write, and edit Program plans | Program Plans per MPR 7120.5E | 6 Program Plans per year | Annual | |
| 1.30 | GATEWAY PROGRAM WORK INSTRUCTIONS | ||||
| The contractor shall provide work instructions and maintain the Gateway work instructions within the ISS Program Master List of work instructions, processes, and procedures in accordance with SAE AS9100, Quality Systems – Aerospace – Model for Quality Assurance in Design, Development, Production, Installation and Servicing, and provide administrative functions for work instructions in accordance with SSP 41170, Configuration Management Requirements. | Maintain and update Gateway Master List of documents and WI's, maintain master list links, updates. Develop status charts for Gateway Master List contents for inclusion in QMS semi-annual review. | Chart submitted for QMS semi-annual review | 4 charts/twice per year | Summer and end of year | |
| 1.31 | GATEWAY CERTIFICATION OF FLIGHT READINESS (CoFR) - Reserved | ||||
| 1.31.1 | Gateway Program CoFR Process - Reserved | ||||
| 1.32 | GATEWAY EXPORT CONTROL - Reserved | ||||
| 1.33 | GATEWAY PROGRAM SCHEDULING | ||||
| 1.33.1 | The contractor shall provide overall Program schedule management, analysis, and assessments in accordance with DRD HSFTIC-PC-04, Program Schedules, to support the continued development and operation of the Gateway. | This is the overall schedule management effort to ensure the Gateway Program scheduling function is executed and schedules are provided to identified organizations per DRD-HSFTIC-PC-04. |
Provide technical inputs to SSP 50489, Mission Integration (MIT) document Provide schedule management
Provide Schedule Templates and Combines Milestone Definitions Tables to the Book Coordinator to be incorporated into the SSP 50489, Mission Integration Template (MIT) document in support of 1 Change request (CR) during the year.
Details for Program Schedules are identified in 1.16.6.4 Schedule Management below.
| 1.33.2 | The contractor shall integrate schedule milestone requirements with affected Program providers, and resolve issues with data providers and identify potential schedule impacts and notify affected performing organizations to ensure timely Program awareness and resolution. | Included in the above | Included in the above |
| 1.33.3 | Gateway Schedule Management | ||
| A. The contractor shall perform Special Schedule Trade Studies or create ad hoc schedules. | |||
| B. The contractor shall develop and maintain integrated schedules and project schedules, and report upcoming deliverables and impacts associated with delays. | Develop integrated schedule products on a weekly/monthly basis. Schedule delay impact assessments are performed on a monthly/quarterly basis | Integrated schedules |
Schedule delays impact assessments
| C. Provide day-to-day schedule maintenance and development of monthly status and reporting. (e.g., impact of changes to critical milestones in performing organizations’ schedules). | Development of integrated schedules based on project life cycle events and input from project engineers and program personnel | 1 per month | |
| 1.34 | GATEWAY MEETING SERVICES | ||
| The contractor shall provide meeting services for the NASA identified control boards and panels as identified in Section J, Attachment J-7, Meeting Services requirements. | Develop agendas, perform meeting logistics, reproduce and distribute presentation material and provide summary minutes/action items associated with Program reviews, Control Boards, Panels and Near Time Operations per contract Attachment J-7. |
| Support TIMs and integration forums to develop positions on Gateway issues | Agendas, minutes/summary | 382 hours | ||||
| 1.35 | GATEWAY TECHNICAL WRITING | |||||
| The contractor shall provide technical writers for the Gateway Program Safety Review Panel, Gateway Program Safety Working Group, Gateway Program Reliability and Maintainablity Working Group, and associated meetings for the Gateway Program Safety Review Panel special topics. | Set up of meeting support tools (Web-ex/teleconference), publication of meeting minutes within 15 business days of meeting conclusion. Publication of meeting synopsis within 5 business of meeting execution. | Meeting minutes, Meeting synopsis | 3 meetings per week/8 hours each | 3 days a week | ||
| 1.36 | GATEWAY DOCUMENT MANAGEMENT | |||||
| 1.36.1 | Gateway Book Management, Coordination, and Development | |||||
| The contractor shall provide document maintenance functions for Gateway in accordance with SSP 41170, Configuration Management Requirements, SSP 50010, Standards for ISS Program Documentation, and DRD HSFTIC-SI-01, ISS Documents Development. | ||||||
| 1.37 | GATEWAY PROGRAM REVIEWS, BOARDS, PANELS | |||||
| The contractor shall provide and present briefing material, data, analyses and technical input for status and decision making at Gateway Program reviews, control boards, panels, working groups, and Technical Interchange Meetings (TIMs). | refer to Gateway meeting list. | |||||
| 1.38 | GATEWAY PROGRAM RESERVED | |||||
| 1.39 | GATEWAY PROGRAM RESERVED |
SOW 2.0 - Business Mgmt
| Work Load Indicators | |||||
| SOW | SOW Title/Language | Performance Requirements | Products/Deliverables | Approximate Magnitudes | Typical Schedule |
| 2.0 | BUSINESS MANAGEMENT | ||||
| 2.1 | ISS MANAGEMENT AND BUSINESS ADMINISTRATION | ||||
| The contractor shall provide overall contract management and administration for this contract. | |||||
| The contractor shall perform all business and administrative functions and integrate these functions across all areas of performance. | |||||
| The contractor’s on-going business analysis shall support the Program business process. | |||||
| 2.2 | ISS RESOURCES MANAGEMENT | ||||
| As part of the overall program management for this contract, including risk management, the contractor shall perform the following resources management tasks. | |||||
| 2.2.1 | The contractor shall develop and provide a contract Work Breakdown Structure (WBS), a WBS dictionary, and a program WBS map in accordance with DRD HSFTIC-PC-03, Work Breakdown Structure (WBS) and Dictionary. The contract WBS shall serve as the framework for contract planning, budgeting, cost reporting, Flight Planning Review reporting, schedule resource loading, and schedule status reporting to the Program. Elements of work provided by major subcontractors (as defined in DRD HSFTIC-PC-01, NF533 Monthly Cost Reporting) shall also be identified in the contract WBS. | ||||
| 2.2.2 | The contractor shall develop and maintain a contract financial system which discretely tracks resources by NASA project code and contract WBS and elements of cost including labor, overhead, other direct costs (e.g. travel and subcontracts), and indirect costs. | ||||
| 2.2.3 | The contractor shall support the Government budget process and respond to special requests related to budget impacts. The Program will, in accordance with the budget or special request guidelines and reporting format, specify the format and content of the contractor’s inputs and supporting rationale. | ||||
| 2.2.4 | The contractor shall provide financial reporting in accordance with DRD HSFTIC-PC-01, NF533 Monthly Cost Reporting. | ||||
| 2.2.5 | The contractor shall provide Workforce Reports in accordance with DRD HSFTIC-PC-02, Workforce Reports, to show organization, geographical breakdown and off-site versus on site workforce data. | ||||
| 2.2.6 | The contractor shall develop, implement, and deliver annual work plans per DRD HSFTIC-PM-08, Annual Work Plans. | ||||
| 2.3 | ISS PROGRAM BUDGET | ||||
| 2.3.1 | The contractor shall utilize the NASA Agency, ISS Program, and Johnson Space Center (JSC) Budget databases to accomplish the following: | ||||
| A. Analyze budget, funding trends and financial and budget data for the Program and provide reports and presentations for working meetings, pre-reviews, status reviews, issue resolution, and action item closure in a NASA approved format. | Analyze budget, funding, and contract financial and budget data for ISS Program Vehicle Sustaining Engineering Contract to identify discrepancies, issues, and provide forecasts. Develop reports and presentations for working meetings, pre-reviews, status reviews, issue resolution, and action item closure in an approved format. Integrate and report cost and schedule analysis. |
Provide management and administration of ISS Program Vehicle Sustaining Engineering Contract budget products
Create reports, funding analysis and charts from data collected in other 2.3.1 tasks.
Develop and update monthly Cost Analysis and Variance in SAFE.
Award Fee Reconciliation Expiring Funds Analysis End of Year…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .